US10523506B2 - Network configuration method and network device - Google Patents

Network configuration method and network device Download PDF

Info

Publication number
US10523506B2
US10523506B2 US15/667,601 US201715667601A US10523506B2 US 10523506 B2 US10523506 B2 US 10523506B2 US 201715667601 A US201715667601 A US 201715667601A US 10523506 B2 US10523506 B2 US 10523506B2
Authority
US
United States
Prior art keywords
network device
loop link
vlan
vlans
time difference
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US15/667,601
Other versions
US20190044803A1 (en
Inventor
Yi-Ting Lai
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nanning Fulian Fugui Precision Industrial Co Ltd
Original Assignee
Nanning Fugui Precision Industrial Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nanning Fugui Precision Industrial Co Ltd filed Critical Nanning Fugui Precision Industrial Co Ltd
Priority to US15/667,601 priority Critical patent/US10523506B2/en
Assigned to NANNING FUGUI PRECISION INDUSTRIAL CO., LTD. reassignment NANNING FUGUI PRECISION INDUSTRIAL CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LAI, YI-TING
Priority to CN201710776198.6A priority patent/CN109391507B/en
Priority to TW106129850A priority patent/TWI672070B/en
Publication of US20190044803A1 publication Critical patent/US20190044803A1/en
Application granted granted Critical
Publication of US10523506B2 publication Critical patent/US10523506B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0836—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability to enhance reliability, e.g. reduce downtime
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0889—Techniques to speed-up the configuration process
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • H04L43/0864—Round trip delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/48—Routing tree calculation

Definitions

  • the subject matter herein generally relates to network technologies, and more particularly to a network configuration method and a network device.
  • a traditional ring protection switching layout (e.g., Ethernet ring network protection switching) is generally used to switch a faulty link on an Ethernet ring network.
  • the Ethernet ring network usually comprises a master link and a standby link.
  • the standby link When the master link is in a normal working state, the standby link is in a unused state, for example, a data transmission function of the standby link is turned off.
  • the standby link is switched on to ensure the reliability of a network link and protect an Ethernet service of the Ethernet ring network.
  • FIG. 1 illustrates an exemplary embodiment of a network environment comprising multiple network devices
  • FIG. 2 illustrates a block diagram of an exemplary embodiment of functional modules of a network device
  • FIG. 3 illustrates a flowchart of an exemplary embodiment of a network configuration method
  • FIG. 4 illustrates a flowchart of an exemplary embodiment of a VLAN configuration.
  • references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean “at least one.”
  • module refers to logic embodied in computing or firmware, or to a collection of software instructions, written in a programming language, such as, Java, C, or assembly.
  • One or more software instructions in the modules may be embedded in firmware, such as in an erasable programmable read only memory (EPROM).
  • EPROM erasable programmable read only memory
  • the modules described herein may be implemented as either software and/or computing modules and may be stored in any type of non-transitory computer-readable medium or other storage device. Some non-limiting examples of non-transitory computer-readable media include CDs, DVDs, BLU-RAY, flash memory, and hard disk drives.
  • the term “comprising”, when used, means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in a so-described combination, group, series, and the like.
  • FIG. 1 illustrates an exemplary embodiment of a network environment comprising multiple network devices.
  • a network topology network topology 2
  • network topology 2 comprises multiple network devices (e.g., 10 , 20 , and 30 ) which may be forwarding devices, for example, switches, routers, or the like.
  • a first network device 10 , a second network device 20 , and the third network device 30 form a loop link (i.e., a first loop link 2 A).
  • the exemplary embodiment illustrated in FIG. 1 is merely an example and is not intended to be limiting. More network devices may be located in the loop link between the second network device 20 and the third network device 30 , such as a fourth network device, a fifth network device, and on.
  • Each network device 10 , 20 , and 30 comprises multiple ports, types of which can be monitored.
  • the multiple ports may be uplink/downlink ports, IPC/NVR ports connected to a terminal device (e.g., 50 A- 50 D) or a server (e.g., 40 ), or the like.
  • a terminal device e.g., 50 A- 50 D
  • a server e.g., 40
  • data forwarding function of the port is turned off.
  • Each network device may transmit probe packets to the network topology 2 to discover one or more loop links (e.g., the first loop link 2 A) which go through that network device.
  • the network devices may assign ports for the first loop link 2 A.
  • the first network device 10 may assign a first loop link port 10 A and a second loop link port 10 B
  • the second network device 20 may assign a third loop link port 20 A and a fourth loop link port 20 B
  • the third network device 30 may assign a third loop link port 30 A and a sixth loop link port 30 B.
  • FIG. 2 illustrates one exemplary embodiment of functional modules of the network device 10 .
  • the first network device 10 comprises a non-transitory storage medium 100 , at least one processor 200 , and a network configuration system 300 .
  • the network configuration system 300 comprises a detection module 310 , a receiving module 320 , a determining module 330 , a configuration module 340 , and a collecting module 350 .
  • the functions of each of the modules 310 ⁇ 350 are executed by one or more processors (e.g. by the processor 200 ).
  • the non-transitory storage medium 100 can store code and data.
  • the detection module 310 detects a load of the first loop link 2 A to obtain first load information.
  • the first load information comprises a first time difference ⁇ T 1 between the transmitting, by the first network device 10 , of a first probe loop link packet used to bypass the first loop link 2 A and receiving, by the first network device 10 , the first probe loop link packet.
  • the receiving module 320 receives external load information from the other network devices in the first loop link 2 A, for example, second load information and third load information.
  • the second load information is obtained by the second network device 20 through detecting the load of the first loop link 2 A
  • the third load information is obtained by the third network device 30 through detecting the load of the first loop link 2 A.
  • the second load information comprises a second time difference ⁇ T 2 between the transmitting, by the second network device 20 , of a second probe loop link packet used to bypass the first loop link 2 A and receiving, by the second network device 20 , the second probe loop link packet.
  • the third load information comprises a third time difference ⁇ T 3 between the transmitting, by the third network device 30 , of a third probe loop link packet used to bypass the first loop link 2 A and receiving, by the third network device 30 , the third probe loop link packet.
  • the second network devices 20 periodically broadcasts the second load information
  • the third network device 30 periodically broadcasts the third load information.
  • the determining module 330 determines whether the first network device 10 is suitable as an owner node in the first loop link 2 A according to the first load information, the second load information, and the third load information. In the exemplary embodiment, the determining module 330 compares the first time difference ⁇ T 1 with the second time difference ⁇ T 2 , and the third time difference ⁇ T 3 . The first network device 10 is determined as suitable for the role of the owner node upon the condition that the first time difference ⁇ T 1 is not greater than either of the second time difference ⁇ T 2 and the third time difference ⁇ T 3 . The first network device 10 is determined as not being a suitable owner node upon the condition that the first time difference ⁇ T 1 is greater than one of the second time difference ⁇ T 2 and the third time difference ⁇ T 3 .
  • the configuration module 340 configures the first network device 10 as the owner node in the first loop link 2 A upon the condition that the first network device 10 is suitable as the owner node in the first loop link 2 A.
  • Both the second network device 20 and the third network device 30 may be configured as normal nodes, for example, the second network device 20 may be configured as a transit node in the first loop link 2 A, and the third network device 30 may be configured as a neighbor node.
  • the configuration module 340 may configure the second loop link port 10 B as a Ring Protection Link (RPL) port, and block the RPL port.
  • the RPL port is connected to the third network device 30 and forms an environmental protection link with the third network device 30 .
  • the configuration module 340 configures the first network device 10 as an normal node (e.g., transit node, or a neighbor node) in the first loop link 2 A upon the condition that the first network device 10 is not a suitable owner node in the first loop link 2 A.
  • an normal node e.g., transit node, or a neighbor node
  • the first network device 10 is configured as the owner node, and both the second network device 20 and the third network device 30 are configured as the normal nodes in the first loop link 2 A.
  • the collecting module 350 collects all VLANs of the first network device 10 .
  • the configuration module 340 configures the first VLAN as a control VLAN in the first loop link 2 A.
  • the configuration module 340 selects one of the multiple first VLANs as the control VLAN in the first loop link, and configures remaining first VLANs as data VLANs.
  • the configuration module 340 defines a new VLAN as the first VLAN and configures the new VLAN as the control VLAN.
  • the collecting module 350 collects all VLANs of the first network device 10 .
  • the configuration module 340 configures the second VLAN as a data VLAN in the first loop link 2 A.
  • FIG. 3 illustrates a flowchart of an exemplary embodiment of a network configuration method.
  • the network configuration method is provided by way of example, as there are a variety of ways to carry out the method. The method described below can be carried out using the first network device 10 illustrated in FIG. 2 , for example, and various elements of these fingers are referenced in explaining the processing method. The first network device 10 is not to limit the operation of the method, which also can be carried out using other devices.
  • Each step shown in FIG. 3 represents one or more processes, methods, or subroutines, carried out in the exemplary processing method. Additionally, the illustrated order of blocks is by example only and the order of the blocks can change.
  • the network configuration method begins at block S 40 .
  • the first network device probes a first loop link, the first loop link further comprising multiple other network devices, such as a second network device and a third network device.
  • the first network device detects a load of the first loop link to obtain first load information.
  • the first load information comprises a first time difference ⁇ T 1 between the transmitting, by the first network device, of a first probe loop link packet used to bypass the first loop link and receiving, by the first network device, the first probe loop link packet.
  • the first network device receives external load information from the other network devices, for example, second load information from the second network device and third load information from the third network device.
  • second load information is obtained by the second network device through detecting the load of the first loop link
  • third load information is obtained by the third network device through detecting the load of the first loop link.
  • the second load information comprises a second time difference ⁇ T 2 between the transmitting, by the second network device, of a second probe loop link packet used to bypass the first loop link and receiving, by the second network device, the second probe loop link packet.
  • the third load information comprises a third time difference ⁇ T 3 between the transmitting, by the third network device, a third probe loop link packet used to bypass the first loop link and receiving, by the third network device, of the third probe loop link packet.
  • the first network device determines whether the first network device is suitable as an owner node in the first loop link according to the first load information, the second load information and the third load information. If yes, the flowchart goes to block S 44 . If no, the flowchart goes to block S 45 .
  • the first network device compares the first time difference ⁇ T 1 with the second time difference ⁇ T 2 , and the third time difference ⁇ T 3 . It's determined that the first network device is suitable as the owner node upon the condition that the first time difference is not greater than either of the second time difference ⁇ T 2 and the third time difference ⁇ T 3 . It's determined that the first network device is not suitable as an owner node upon the condition that the first time difference is greater than one of the second time difference ⁇ T 2 and the third time difference ⁇ T 3 .
  • the first network device configures the first network device as the owner node in the first loop link upon the condition that the first network device is suitable as the owner node in the first loop link.
  • the first network device configures a RPL port on the first network device and block the RPL port.
  • the RPL port is connected to the third network device and forms an environmental protection link with the third network device.
  • the first network device configures the first network device as a normal node (e.g., transit node, or a neighbor node) in the first loop link.
  • a normal node e.g., transit node, or a neighbor node
  • FIG. 4 illustrates a flowchart of an exemplary embodiment of a VLAN configuration.
  • the first network device collects all VLANs of the first network device.
  • the first network device determines whether all VLANs comprise one or more first VLANs that are present simultaneously in the second network device and in the third network device. If yes, the flowchart goes to block S 48 . If no, the flowchart goes to block S 51 .
  • the first network device determines whether all VLANs comprise only one first VLAN. If yes, the flowchart goes to block S 49 . If no, the flowchart goes to block S 50 .
  • the first network device configures the first VLAN as a control VLAN in the first loop link. The process of auto-configuring control VLAN is terminated.
  • the first network device selects one of the multiple first VLANs as the control VLAN in the first loop link, and configures remaining first VLANs as data VLANs. The process of auto-configuring control VLAN is terminated.
  • the first network device defines a new VLAN as the first VLAN and configures the first VLAN as the control VLAN in the first loop link. The process of auto-configuring control VLAN is terminated.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Environmental & Geological Engineering (AREA)
  • Automation & Control Theory (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

A network configuration method with automatic and periodic reviews of master and standby links can be executed by a first network device which is located in a first loop link, the first loop link also containing second and third network devices. The method comprises detecting a load of the first loop link, receiving second load information from the second network device, and third load information from the third network device. Determining whether the first network device is suitable as an owner node in the first loop link according to the first, second, and third load information, and configuring the first network device as the owner node in the first loop link upon the condition that the first network device is deemed suitable as such.

Description

FIELD
The subject matter herein generally relates to network technologies, and more particularly to a network configuration method and a network device.
BACKGROUND
A traditional ring protection switching layout (e.g., Ethernet ring network protection switching) is generally used to switch a faulty link on an Ethernet ring network. The Ethernet ring network usually comprises a master link and a standby link. When the master link is in a normal working state, the standby link is in a unused state, for example, a data transmission function of the standby link is turned off. In contrast, when the master link becomes faulty, the standby link is switched on to ensure the reliability of a network link and protect an Ethernet service of the Ethernet ring network.
However, configuration operations of the traditional ring protection switching are inefficient, because many functions require complex manual configurations through maintenance teams. In addition, manual configurations may bring manual errors which may result in risks to proper functioning of network.
BRIEF DESCRIPTION OF THE DRAWINGS
Implementations of the present technology will be described, by way of example only, with reference to the attached figures, wherein:
FIG. 1 illustrates an exemplary embodiment of a network environment comprising multiple network devices;
FIG. 2 illustrates a block diagram of an exemplary embodiment of functional modules of a network device;
FIG. 3 illustrates a flowchart of an exemplary embodiment of a network configuration method; and
FIG. 4 illustrates a flowchart of an exemplary embodiment of a VLAN configuration.
 DETAILED DESCRIPTION
It will be appreciated that for simplicity and clarity of illustration, where appropriate, reference numerals have been repeated among the different fingers to indicate corresponding or analogous elements. In addition, numerous specific details are set fourth in order to provide a thorough understanding of the embodiments described herein. However, it will be understood by those of ordinary skill in the art that the embodiments described herein can be practiced without these specific details. In other instances, methods, procedures, and components have not been described in detail so as not to obscure the related relevant feature being described. Also, the description is not to be considered as limiting the scope of the embodiments described herein. The drawings are not necessarily to scale and the proportions of certain parts may be exaggerated to better illustrate details and features of the present disclosure.
It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean “at least one.”
In general, the word “module” as used hereinafter, refers to logic embodied in computing or firmware, or to a collection of software instructions, written in a programming language, such as, Java, C, or assembly. One or more software instructions in the modules may be embedded in firmware, such as in an erasable programmable read only memory (EPROM). The modules described herein may be implemented as either software and/or computing modules and may be stored in any type of non-transitory computer-readable medium or other storage device. Some non-limiting examples of non-transitory computer-readable media include CDs, DVDs, BLU-RAY, flash memory, and hard disk drives. The term “comprising”, when used, means “including, but not necessarily limited to”; it specifically indicates open-ended inclusion or membership in a so-described combination, group, series, and the like.
FIG. 1 illustrates an exemplary embodiment of a network environment comprising multiple network devices. In the exemplary embodiment, a network topology (network topology 2) comprises multiple network devices (e.g., 10, 20, and 30) which may be forwarding devices, for example, switches, routers, or the like. In the exemplary embodiment, a first network device 10, a second network device 20, and the third network device 30 form a loop link (i.e., a first loop link 2A). However, the exemplary embodiment illustrated in FIG. 1 is merely an example and is not intended to be limiting. More network devices may be located in the loop link between the second network device 20 and the third network device 30, such as a fourth network device, a fifth network device, and on.
Each network device 10, 20, and 30 comprises multiple ports, types of which can be monitored. In the exemplary embodiment, the multiple ports may be uplink/downlink ports, IPC/NVR ports connected to a terminal device (e.g., 50A-50D) or a server (e.g., 40), or the like. When a port is monitored to be an uplink port or an downlink port, data forwarding function of the port is turned off.
Each network device (e.g., 10-30) may transmit probe packets to the network topology 2 to discover one or more loop links (e.g., the first loop link 2A) which go through that network device. The network devices (e.g., 10-30) may assign ports for the first loop link 2A. For example, the first network device 10 may assign a first loop link port 10A and a second loop link port 10B, the second network device 20 may assign a third loop link port 20A and a fourth loop link port 20B, and the third network device 30 may assign a third loop link port 30A and a sixth loop link port 30B.
Exemplary embodiments of auto-configuring roles for the multiple network devices (e.g., 10-30) in the first loop link 2A will be described in more detail.
FIG. 2 illustrates one exemplary embodiment of functional modules of the network device 10. The first network device 10 comprises a non-transitory storage medium 100, at least one processor 200, and a network configuration system 300. The network configuration system 300 comprises a detection module 310, a receiving module 320, a determining module 330, a configuration module 340, and a collecting module 350. The functions of each of the modules 310˜350 are executed by one or more processors (e.g. by the processor 200). The non-transitory storage medium 100 can store code and data.
In relation to role configuration, the detection module 310 detects a load of the first loop link 2A to obtain first load information. In the exemplary embodiment, the first load information comprises a first time difference ΔT1 between the transmitting, by the first network device 10, of a first probe loop link packet used to bypass the first loop link 2A and receiving, by the first network device 10, the first probe loop link packet.
The receiving module 320 receives external load information from the other network devices in the first loop link 2A, for example, second load information and third load information. Wherein the second load information is obtained by the second network device 20 through detecting the load of the first loop link 2A, the third load information is obtained by the third network device 30 through detecting the load of the first loop link 2A. In the exemplary embodiment, the second load information comprises a second time difference ΔT2 between the transmitting, by the second network device 20, of a second probe loop link packet used to bypass the first loop link 2A and receiving, by the second network device 20, the second probe loop link packet. The third load information comprises a third time difference ΔT3 between the transmitting, by the third network device 30, of a third probe loop link packet used to bypass the first loop link 2A and receiving, by the third network device 30, the third probe loop link packet. The second network devices 20 periodically broadcasts the second load information, and the third network device 30 periodically broadcasts the third load information.
The determining module 330 determines whether the first network device 10 is suitable as an owner node in the first loop link 2A according to the first load information, the second load information, and the third load information. In the exemplary embodiment, the determining module 330 compares the first time difference ΔT1 with the second time difference ΔT2, and the third time difference ΔT3. The first network device 10 is determined as suitable for the role of the owner node upon the condition that the first time difference ΔT1 is not greater than either of the second time difference ΔT2 and the third time difference ΔT3. The first network device 10 is determined as not being a suitable owner node upon the condition that the first time difference ΔT1 is greater than one of the second time difference ΔT2 and the third time difference ΔT3.
The configuration module 340 configures the first network device 10 as the owner node in the first loop link 2A upon the condition that the first network device 10 is suitable as the owner node in the first loop link 2A. Both the second network device 20 and the third network device 30 may be configured as normal nodes, for example, the second network device 20 may be configured as a transit node in the first loop link 2A, and the third network device 30 may be configured as a neighbor node.
In the exemplary embodiment, the configuration module 340 may configure the second loop link port 10B as a Ring Protection Link (RPL) port, and block the RPL port. The RPL port is connected to the third network device 30 and forms an environmental protection link with the third network device 30.
In the exemplary embodiment, the configuration module 340 configures the first network device 10 as an normal node (e.g., transit node, or a neighbor node) in the first loop link 2A upon the condition that the first network device 10 is not a suitable owner node in the first loop link 2A.
In relation to VLAN configuration, in the exemplary embodiment, the first network device 10 is configured as the owner node, and both the second network device 20 and the third network device 30 are configured as the normal nodes in the first loop link 2A.
Configuration of VLAN Control will be described in more detail.
The collecting module 350 collects all VLANs of the first network device 10.
When all VLANs comprise one first VLAN that is present simultaneously in the second network device 20 and in the third network device 30, the configuration module 340 configures the first VLAN as a control VLAN in the first loop link 2A.
When all VLANs comprise multiple first VLANs, the configuration module 340 selects one of the multiple first VLANs as the control VLAN in the first loop link, and configures remaining first VLANs as data VLANs.
When none of the VLANs comprise the first VLAN, the configuration module 340 defines a new VLAN as the first VLAN and configures the new VLAN as the control VLAN.
Data VLAN configuration will be described in more detail.
The collecting module 350 collects all VLANs of the first network device 10.
When all VLANs comprise a second VLAN that controls data flow to a destination, the configuration module 340 configures the second VLAN as a data VLAN in the first loop link 2A.
FIG. 3 illustrates a flowchart of an exemplary embodiment of a network configuration method. The network configuration method is provided by way of example, as there are a variety of ways to carry out the method. The method described below can be carried out using the first network device 10 illustrated in FIG. 2, for example, and various elements of these fingers are referenced in explaining the processing method. The first network device 10 is not to limit the operation of the method, which also can be carried out using other devices. Each step shown in FIG. 3 represents one or more processes, methods, or subroutines, carried out in the exemplary processing method. Additionally, the illustrated order of blocks is by example only and the order of the blocks can change. The network configuration method begins at block S40.
At block S40, the first network device probes a first loop link, the first loop link further comprising multiple other network devices, such as a second network device and a third network device.
At block S41, the first network device detects a load of the first loop link to obtain first load information. In the exemplary embodiment, the first load information comprises a first time difference ΔT1 between the transmitting, by the first network device, of a first probe loop link packet used to bypass the first loop link and receiving, by the first network device, the first probe loop link packet.
At block S42, the first network device receives external load information from the other network devices, for example, second load information from the second network device and third load information from the third network device. Wherein the second load information is obtained by the second network device through detecting the load of the first loop link, the third load information is obtained by the third network device through detecting the load of the first loop link.
In the exemplary embodiment, the second load information comprises a second time difference ΔT2 between the transmitting, by the second network device, of a second probe loop link packet used to bypass the first loop link and receiving, by the second network device, the second probe loop link packet. The third load information comprises a third time difference ΔT3 between the transmitting, by the third network device, a third probe loop link packet used to bypass the first loop link and receiving, by the third network device, of the third probe loop link packet.
At block S43, the first network device determines whether the first network device is suitable as an owner node in the first loop link according to the first load information, the second load information and the third load information. If yes, the flowchart goes to block S44. If no, the flowchart goes to block S45.
In the exemplary embodiment, the first network device compares the first time difference ΔT1 with the second time difference ΔT2, and the third time difference ΔT3. It's determined that the first network device is suitable as the owner node upon the condition that the first time difference is not greater than either of the second time difference ΔT2 and the third time difference ΔT3. It's determined that the first network device is not suitable as an owner node upon the condition that the first time difference is greater than one of the second time difference ΔT2 and the third time difference ΔT3.
At block S44, the first network device configures the first network device as the owner node in the first loop link upon the condition that the first network device is suitable as the owner node in the first loop link.
In the exemplary embodiment, the first network device configures a RPL port on the first network device and block the RPL port. Wherein the RPL port is connected to the third network device and forms an environmental protection link with the third network device.
At block S45, the first network device configures the first network device as a normal node (e.g., transit node, or a neighbor node) in the first loop link.
FIG. 4 illustrates a flowchart of an exemplary embodiment of a VLAN configuration.
At block S46, the first network device collects all VLANs of the first network device.
At block S47, the first network device determines whether all VLANs comprise one or more first VLANs that are present simultaneously in the second network device and in the third network device. If yes, the flowchart goes to block S48. If no, the flowchart goes to block S51.
At block S48, the first network device determines whether all VLANs comprise only one first VLAN. If yes, the flowchart goes to block S49. If no, the flowchart goes to block S50.
At block S49, the first network device configures the first VLAN as a control VLAN in the first loop link. The process of auto-configuring control VLAN is terminated.
At block S50, the first network device selects one of the multiple first VLANs as the control VLAN in the first loop link, and configures remaining first VLANs as data VLANs. The process of auto-configuring control VLAN is terminated.
At block S51, the first network device defines a new VLAN as the first VLAN and configures the first VLAN as the control VLAN in the first loop link. The process of auto-configuring control VLAN is terminated.
It should be emphasized that the above-described exemplary embodiments of the present disclosure, including any particular embodiments, are merely possible examples of implementations, set fourth for a clear understanding of the principles of the disclosure. Many variations and modifications can be made to the above-described embodiment(s) of the disclosure without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.

Claims (12)

What is claimed is:
1. A network device comprising:
at least one processor;
a non-transitory storage medium coupled to the at least one processor and configured to store one or more programs to be executed by the at least one processor, the one or more programs including instructions for:
probing a first loop link, the first loop link further comprising multiple other network devices;
detecting a load of the first loop link by the network device to obtain a first load message;
receiving a plurality of second load messages respectively from the other network devices, wherein the plurality of second load messages are obtained by the other network devices through detecting the load of the first loop link;
determining whether the network device is suitable as an owner node in the first loop link according to the first load message and the plurality of second load messages;
configuring the network device as the owner node in the first loop link upon the condition that the network device is suitable as the owner node in the first loop link;
collecting all virtual local access networks (VLANs) of the network device;
when the all VLANs comprise one first VLAN that is present simultaneously in each of the multiple other network devices, configuring the first VLAN as a control VLAN in the first loop link;
when the all VLANs comprise multiple first VLANs, selecting one of the multiple first VLANs as the control VLAN in the first loop link, and configuring remaining first VLANs as data VLANs; and
when none of the all VLANs comprise the first VLAN, defining a new VLAN as the first VLAN.
2. The device of claim 1, wherein:
the first load message comprises a first time difference between the transmitting, by the network device, of a first probe loop link packet used to bypass the first loop link and receiving, by the network device, the first probe loop link packet;
the plurality of second load messages comprise second time differences each is a time difference between the transmitting, by a corresponding network device of the other network devices, of a second probe loop link packet used to bypass the first loop link and receiving, by the corresponding network device, the second probe loop link packet;
wherein the determining step further comprises:
comparing the first time difference with each of the second time differences;
determining that the network device is suitable as the owner node upon the condition that the first time difference is not greater than either of the second time differences; and
determining that the network device is not suitable as the owner node upon the condition that the first time difference is greater than one of the second time differences.
3. The device of claim 1, the configuring step further comprise:
configuring a ring protection link (RPL) port on the network device and blocking the RPL port, wherein the RPL port is connected to one of the other network devices and forms an environmental protection link with the one of the other network devices.
4. The device of claim 1, further comprising:
collecting all VLANs of the network device; and
when the all VLANs comprises a second VLAN that controls data flow to a destination, configuring the second VLAN as a data VLAN in the first loop link.
5. A network configuration method, executed by a first network device which locates in a first loop link, wherein the first loop link is further provided with a second network device and a third network device, the method comprising:
detecting a load of the first loop link to obtain first load information;
receiving second load information and third load information, wherein the second load information is obtained by the second network device through detecting the load of the first loop link, the third load information is obtained by the third network device through detecting the load of the first loop link;
determining whether the first network device is suitable as an owner node in the first loop link according to the first load information, the second load information and the third load information;
configuring the first network device as the owner node in the first loop link upon the condition that the first network device is suitable as the owner node in the first loop link;
collecting all virtual local access networks (VLANs) of the first network device;
when the all VLANs comprise one first VLAN that is present simultaneously in the second network device and in the third network device, configuring the first VLAN as a control VLAN in the first loop link;
when the all VLANs comprise multiple first VLANs, selecting one of the multiple first VLANs as the control VLAN in the first loop link, and configuring remaining first VLANs as data VLANs; and
when none of the all VLANs comprise the first VLAN, defining a new VLAN as the first VLAN.
6. The network configuration method of claim 5, wherein:
the first load information comprises a first time difference between the transmitting, by the first network device, of a first probe loop link packet used to bypass the first loop link and receiving, by the first network device, the first probe loop link packet;
the second load information comprises a second time difference between the transmitting, by the second network device, of a second probe loop link packet used to bypass the first loop link and receiving, by the second network device, the second probe loop link packet;
the third load information comprises a third time difference between the transmitting, by the third network device, of a third probe loop link packet used to bypass the first loop link and receiving, by the third network device, the third probe loop link packet;
wherein the determining step further comprises:
comparing the first time difference with the second time difference, and the third time difference;
determining that the first network device is suitable as the owner node upon the condition that the first time difference is not greater than either of the second time difference and the third time difference; and
determining that the first network device is not suitable as the owner node upon the condition that the first time difference is greater than one of the second time difference and the third time difference.
7. The network configuration method of claim 5, wherein the configuring step further comprises:
configuring a ring protection link (RPL) port on the first network device and blocking the RPL port, wherein the RPL port is connected to the second network device or the third network device, and forms an environmental protection link with the second network device or the third network device.
8. The network configuration method of claim 5, further comprising:
collecting all VLANs of the first network device; and
when the all VLANs comprise a second VLAN that controls data flow to a destination, configuring the second VLAN as a data VLAN in the first loop link.
9. A non-transitory storage medium storing executable program instructions which, when executed by a processing system in a first network device, cause the processing system to perform a method comprising:
detecting a load of the first loop link to obtain first load information, wherein the first loop link comprising the first network device a second network device and a third network device;
receiving second load information and third load information, wherein the second load information is obtained by the second network device through detecting the load of the first loop link, the third load information is obtained by the third network device through detecting the load of the first loop link;
determining whether the first network device is suitable as an owner node in the first loop link according to the first load information, the second load information and the third load information;
configuring the first network device as the owner node in the first loop link upon the condition that the first network device is suitable as the owner node in the first loop link;
collecting all virtual local access networks (VLANs) of the first network device;
wherein when the all VLANs comprise one first VLAN that is present simultaneously in the second network device and in the third network device, configuring the first VLAN as a control VLAN in the first loop link;
wherein when the all VLANs comprise multiple first VLANs, selecting one of the multiple first VLANs as the control VLAN in the first loop link, and configuring remaining first VLANs as data VLANs; and
wherein when none of the all VLANs comprise the first VLAN, defining a new VLAN as the first VLAN.
10. The medium of claim 9, wherein:
the first load information comprises a first time difference between the transmitting, by the first network device, of a first probe loop link packet used to bypass the first loop link and receiving, by the first network device, the first probe loop link packet;
the second load information comprises a second time difference between the transmitting, by the second network device, of a second probe loop link packet used to bypass the first loop link and receiving, by the second network device, the second probe loop link packet;
the third load information comprises a third time difference between the transmitting, by the third network device, of a third probe loop link packet used to bypass the first loop link and receiving, by the third network device, the third probe loop link packet;
wherein the determining step further comprises:
comparing the first time difference with the second time difference, and the third time difference;
determining that the first network device is suitable as the owner node upon the condition that the first time difference is not greater than either of the second time difference and the third time difference; and
determining that the first network device is not suitable as the owner node upon the condition that the first time difference is greater than one of the second time difference and the third time difference.
11. The medium of claim 9, the configuring step further comprises:
configuring a ring protection link (RPL) port on the first network device and blocking the RPL port, wherein the RPL port is connected to the second network device or the third network device, and forms an environmental protection link with the second network device or the third network device.
12. The medium of claim 9, further comprising:
collecting all VLANs of the first network device; and
wherein when the all VLANs comprise a second VLAN that controls data flow to a destination, configuring the second VLAN as a data VLAN in the first loop link.
US15/667,601 2017-08-02 2017-08-02 Network configuration method and network device Active 2037-12-14 US10523506B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US15/667,601 US10523506B2 (en) 2017-08-02 2017-08-02 Network configuration method and network device
CN201710776198.6A CN109391507B (en) 2017-08-02 2017-08-31 Network configuration method, computer-readable storage medium, and network device
TW106129850A TWI672070B (en) 2017-08-02 2017-08-31 Network configuration method and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US15/667,601 US10523506B2 (en) 2017-08-02 2017-08-02 Network configuration method and network device

Publications (2)

Publication Number Publication Date
US20190044803A1 US20190044803A1 (en) 2019-02-07
US10523506B2 true US10523506B2 (en) 2019-12-31

Family

ID=65231223

Family Applications (1)

Application Number Title Priority Date Filing Date
US15/667,601 Active 2037-12-14 US10523506B2 (en) 2017-08-02 2017-08-02 Network configuration method and network device

Country Status (3)

Country Link
US (1) US10523506B2 (en)
CN (1) CN109391507B (en)
TW (1) TWI672070B (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5886643A (en) 1996-09-17 1999-03-23 Concord Communications Incorporated Method and apparatus for discovering network topology
US20040103179A1 (en) * 2002-11-26 2004-05-27 Alcatel Canada Inc. Topology management of dual ring network
CN1929442A (en) 2006-08-11 2007-03-14 杭州华为三康技术有限公司 Network node and method for estimating message reception interval time and detective path bandwidth
US20090252030A1 (en) 2008-04-04 2009-10-08 Prakash Kashyap Reducing traffic loss in an eaps system
US20110080915A1 (en) * 2009-10-07 2011-04-07 Calix Networks, Inc. Automated vlan assignment to domain in ring network
US20110158241A1 (en) * 2008-08-28 2011-06-30 Zte Corporation Method and device for transmitting control message based on multi-ring ethernet
CN103378998A (en) 2012-04-27 2013-10-30 中兴通讯股份有限公司 Method and device for Ethernet port loopback detection
US20130286818A1 (en) 2012-04-28 2013-10-31 Huawei Technologies Co., Ltd. Ethernet ring protection switching method, network device and system
US20170085488A1 (en) 2015-09-22 2017-03-23 Brocade Communications Systems, Inc. Intelligent, load adaptive, and self optimizing master node selection in an extended bridge
US20170155522A1 (en) * 2015-11-26 2017-06-01 Fujitsu Limited Communication apparatus and communication system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1251110C (en) * 2002-12-31 2006-04-12 联想(北京)有限公司 Method for node load information transfer and node survival detection in machine group
US10175681B2 (en) * 2014-05-01 2019-01-08 Johnson Controls Technology Company High level central plant optimization
CN106911585B (en) * 2017-04-24 2019-08-13 西安电子科技大学 A Load Balanced Pruning Method for Ring Ethernet

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5886643A (en) 1996-09-17 1999-03-23 Concord Communications Incorporated Method and apparatus for discovering network topology
US20040103179A1 (en) * 2002-11-26 2004-05-27 Alcatel Canada Inc. Topology management of dual ring network
CN1929442A (en) 2006-08-11 2007-03-14 杭州华为三康技术有限公司 Network node and method for estimating message reception interval time and detective path bandwidth
US20090252030A1 (en) 2008-04-04 2009-10-08 Prakash Kashyap Reducing traffic loss in an eaps system
US20110158241A1 (en) * 2008-08-28 2011-06-30 Zte Corporation Method and device for transmitting control message based on multi-ring ethernet
US20110080915A1 (en) * 2009-10-07 2011-04-07 Calix Networks, Inc. Automated vlan assignment to domain in ring network
CN103378998A (en) 2012-04-27 2013-10-30 中兴通讯股份有限公司 Method and device for Ethernet port loopback detection
US20130286818A1 (en) 2012-04-28 2013-10-31 Huawei Technologies Co., Ltd. Ethernet ring protection switching method, network device and system
US20170085488A1 (en) 2015-09-22 2017-03-23 Brocade Communications Systems, Inc. Intelligent, load adaptive, and self optimizing master node selection in an extended bridge
US20170155522A1 (en) * 2015-11-26 2017-06-01 Fujitsu Limited Communication apparatus and communication system

Also Published As

Publication number Publication date
US20190044803A1 (en) 2019-02-07
CN109391507A (en) 2019-02-26
TW201911954A (en) 2019-03-16
TWI672070B (en) 2019-09-11
CN109391507B (en) 2021-11-02

Similar Documents

Publication Publication Date Title
US7969915B2 (en) Technical enhancements to STP (IEEE 802.1D) implementation
CN109104348B (en) Method, system and device for train network data transmission based on CANopen protocol
US20100260040A1 (en) ethernet ring system and a master node and an initialization method thereof
Liang et al. On diagnosis of forwarding plane via static forwarding rules in software defined networks
US20140071812A1 (en) Backup system of ring network and backup method of ring network
KR101318156B1 (en) Method for protection switching in ethernet ring network
EP3029883B1 (en) Network protection method and apparatus, next-ring node, and system
US11171810B1 (en) Misconfigured uplink identification
US9929878B1 (en) Auto detection and prevention of loop, segmentation and traffic outage in a G.8032 ring network
CN102223312B (en) Flow control method and equipment based on link status
JP4729117B2 (en) Edge switch and forwarding table rewriting method
US7920464B2 (en) Method of redundancy of ring network
US9413642B2 (en) Failover procedure for networks
CN102244589B (en) Method and opposite terminal apparatus for processing link fault in virtual switch unit system
CN111464436B (en) Method for solving single-port loop of RSTP (remote station transfer protocol)
US10523506B2 (en) Network configuration method and network device
US10516625B2 (en) Network entities on ring networks
US10382301B2 (en) Efficiently calculating per service impact of ethernet ring status changes
CN102946321B (en) A kind of fault handling method based on IRF network and equipment
EP2898636B1 (en) Method for running a computer network
WO2015120581A1 (en) Traffic loop detection in a communication network
JP6148076B2 (en) Fault detection system, fault detection method, and communication apparatus control program
JP2015162697A (en) Monitoring control system, monitoring device, monitoring control method, and monitoring control program
US20240414179A1 (en) Fault tolerance methodology to detect and recover network uplink fault automatically
CN102281166B (en) Transmission control method and device in Ethernet link

Legal Events

Date Code Title Description
AS Assignment

Owner name: NANNING FUGUI PRECISION INDUSTRIAL CO., LTD., CHIN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LAI, YI-TING;REEL/FRAME:043176/0723

Effective date: 20170616

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FEPP Fee payment procedure

Free format text: SURCHARGE FOR LATE PAYMENT, LARGE ENTITY (ORIGINAL EVENT CODE: M1554); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4