CN109450765B

CN109450765B - Method and device for collecting topology information

Info

Publication number: CN109450765B
Application number: CN201811536560.3A
Authority: CN
Inventors: 顾雷雷
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: Hangzhou H3C Technologies Co Ltd
Priority date: 2018-12-14
Filing date: 2018-12-14
Publication date: 2020-10-27
Anticipated expiration: 2038-12-14
Also published as: CN109450765A

Abstract

The embodiment of the application provides a method and a device for collecting topology information, and relates to the technical field of communication. The method is applied to a main node in an Ethernet Ring Protection Switching (ERPS) ring network, and comprises the following steps: and sending a first NR-RB extension message to enable other nodes in the ERPS ring network to add own node information in the received first NR-RB extension message, forwarding the first NR-RB extension message to a next node, receiving the first NR-RB extension message which is forwarded by a neighbor node and carries the node information of other nodes, generating topology information of the ERPS ring network according to the own node information and the node information of other nodes, and sending a second NR-RB extension message to enable other nodes to acquire the topology information according to the received second NR-RB extension message. By adopting the method and the device, each node in the ERPS ring network can collect the topology information of the ERPS ring network.

Description

Method and device for collecting topology information

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for collecting topology information.

Background

The Ethernet Ring Protection Switching (ERPS) protocol is an Ethernet Ring link layer protocol with high reliability and stability. When the Ethernet ring network is complete, the method can prevent broadcast storm caused by the data loop, and when the Ethernet ring network has link failure, the communication path between each node on the ring network can be recovered quickly, so that the method has higher convergence speed.

An ERPS ring network typically includes a main (Owner) node, a Neighbor (Neighbor) node and at least one Normal (Normal) node. Each node comprises two ports, wherein the port for receiving the NR-RB message can be called a message receiving port, and the port for sending the NR-RB message can be called a message sending port; the neighbor node is a node adjacent to the main node, a Link between the main node and the neighbor node is a loop Protection Link (RPL), two ports on the RPL Link are RPL ports, and other ports are common ports; the link switching of the ERPS loop is realized by the main node and the neighbor nodes through blocking and releasing the RPL ports.

Based on the prior art, each node in the ERPS ring network only stores the node information of the node, but not stores the node information of other nodes, so that network management personnel of the ERPS ring network cannot effectively judge the scale of the current ERPS ring network.

Disclosure of Invention

An object of the embodiments of the present application is to provide a method and an apparatus for collecting topology information, so that each node in an ERPS ring network can collect the topology information of the ERPS ring network. The specific technical scheme is as follows:

in a first aspect, a method for collecting topology information is provided, where the method is applied to a master node in an Ethernet Ring Protection Switching (ERPS) ring network, and the method includes:

sending a first link recovery NR-loop protection link blocking RB extension message, so that when other nodes in the ERPS ring network determine that a first identification field of a received first NR-RB extension message is a first preset value and the first NR-RB extension message does not carry node information of the first NR-RB extension message, adding the node information of the first NR-RB extension message in the received first NR-RB extension message, and forwarding the node information to a next node;

receiving a first NR-RB extension message which is forwarded by a neighbor node and carries node information of other nodes, and generating topology information of the ERPS ring network according to the node information of the neighbor node and the node information of the other nodes;

and sending a second NR-RB extension message, so that when the other nodes determine that a second identification field of the received second NR-RB extension message is a second preset value and the second NR-RB extension message carries node information of the other nodes, the other nodes determine that the second NR-RB extension message carries the topology information and acquire the topology information.

Optionally, the node information includes a node identifier, a port identifier of a packet receiving port, and a port identifier of a packet sending port; the first node in the topology information is a main node, and the last node is a neighbor node;

the method further comprises the following steps:

if the ERPS state is an idle state, port state identifiers of a message receiving port of the first node and a message sending port of the last node in the topology information are set to be in a blocking state, and port state identifiers of other ports in the topology information are set to be in a forwarding state.

Optionally, the method further includes:

receiving a Signal Failure (SF) extension message which is sent by a node when a link fault is detected and carries a third identification field, wherein the SF extension message at least comprises node information of the node, and the node is a common node or a neighbor node;

if the value of the third identification field is determined to be a third preset value, determining a fault link of the node according to the node identification of the node and the topology information of the ERPS ring network, setting the port state identifications of the message receiving port of the first node and the message sending port of the last node in the topology information to be in a forwarding state, and setting the port state identification of the port corresponding to the fault link on the node to be in a blocking state.

In a second aspect, a method for collecting topology information is provided, where the method is applied to a first node in an Ethernet Ring Protection Switching (ERPS) ring network, where the first node is a common node or a neighbor node, and the ERPS ring network further includes a master node, where the method includes:

receiving a RB (radio resource block) extension message which is sent by a main node and blocks a first link recovery NR-loop protection link;

if the first identification field of the received first NR-RB extension message is determined to be a first preset value and the first NR-RB extension message does not carry node information of the first NR-RB extension message, adding the node information of the first NR-RB extension message in the received first NR-RB extension message and forwarding the node information to a next node;

receiving a second link recovery NR-loop protection link blocking RB extension message sent by a main node;

and if the second identifier field of the received second NR-RB extension message is determined to be a second preset value and the second NR-RB extension message carries node information of the second NR-RB extension message, determining that the second NR-RB extension message carries the topology information and acquiring the topology information.

Optionally, the node information includes a node identifier, a port identifier of a packet receiving port, and a port identifier of a packet sending port; the first node in the topology information is a master node, and the last node is a neighbor node, and the method further comprises:

Optionally, before adding node information of itself in the received first NR-RB extension message, the method further includes:

determining the maximum number of node information allowed to be carried by the first NR-RB extended message according to the value of the first identification field;

if the number of the node information currently carried by the first NR-RB extension message is determined to be equal to the maximum number, increasing the value of the first identification field by a preset value, increasing the maximum number of the node information allowed to be carried by the first NR-RB extension message by the preset number, and executing the step of adding the node information of the first NR-RB extension message in the received first NR-RB extension message;

and if the number of the node information carried by the reserved field is determined to be less than the maximum number, executing the step of adding the node information of the first NR-RB extended message.

Optionally, the method further includes:

when the first node detects a link failure, sending an SF extension message carrying a third identification field to a host node, so that when the node receiving the SF extension message determines that the value of the third identification field is a third preset value, determining a failure link of the first node according to the node identification of the first node and the topology information of the ERPS ring network, setting the port state identification of the message receiving port of the first node and the port state identification of the message sending port of the last node in the topology information to be in a forwarding state, and setting the port state identification of the port corresponding to the failure link on the first node to be in a blocking state.

In a third aspect, a device for collecting topology information is provided, where the device is applied to a master node in an Ethernet Ring Protection Switching (ERPS) ring network, and the device includes a sending module, a receiving module, and a generating module:

the sending module is configured to send a first link restoration NR-loop protection link blocking RB extension packet, so that when it is determined that a first identifier field of a received first NR-RB extension packet is a first preset value and the first NR-RB extension packet does not carry node information of its own, other nodes in the ERPS ring network add the node information of its own in the received first NR-RB extension packet, and forward the node information to a next node;

when the receiving module receives a first NR-RB extension packet carrying node information of the other node forwarded by a neighboring node, the generating module is configured to generate topology information of the ERPS ring network according to the node information of the master node and the node information of the other node;

the sending module is further configured to send a second NR-RB extension packet, so that when it is determined that a second identifier field of the received second NR-RB extension packet is a second preset value and the second NR-RB extension packet carries node information of itself, the other node determines that the second NR-RB extension packet carries the topology information and obtains the topology information.

the device further comprises a setting module:

when the ERPS state of the master node is an idle state, the setting module sets the port state identifiers of the packet receiving port of the first node and the packet sending port of the last node in the topology information to be in a blocking state, and sets the port state identifiers of other ports in the topology information to be in a forwarding state.

Optionally, the receiving module is further configured to receive an SF extension packet which is sent by a node when a link failure is detected and carries a third identification field, where the SF extension packet at least includes node information of the node, and the node is a common node or a neighboring node;

the setting module is further configured to, when it is determined that the value of the third identification field is a third preset value, determine a faulty link of the node according to the node identifier of the node and the topology information of the ERPS ring network, set the port state identifiers of the packet receiving port of the first node and the packet sending port of the last node in the topology information to a forwarding state, and set the port state identifier of the port corresponding to the faulty link on the node to a blocking state.

In a fourth aspect, a device for collecting topology information is provided, where the device is applied to a first node in an Ethernet Ring Protection Switching (ERPS) ring network, the first node is a common node or a neighbor node, the ERPS ring network further includes a host node, and the device includes a receiving module, an adding module, a sending module, and an obtaining module:

the receiving module is used for receiving a first link recovery NR-loop protection link blocking RB extension message sent by the main node;

the adding module is configured to add node information of the first node to the received first NR-RB extension packet when it is determined that the first identifier field of the received first NR-RB extension packet is a first preset value and the first NR-RB extension packet does not carry node information of the first node, and the sending module is configured to forward the first NR-RB extension packet to a next node;

the receiving module is further configured to receive an RB extension packet blocked by the second link restoration NR-loop protection link sent by the host node;

the obtaining module is configured to determine that the second NR-RB extension packet carries the topology information and obtain the topology information when it is determined that a second identifier field of the received second NR-RB extension packet is a second preset value and the second NR-RB extension packet carries node information of the first node.

Optionally, the node information includes a node identifier, a port identifier of a packet receiving port, and a port identifier of a packet sending port; the first node in the topology information is a main node, the last node is a neighbor node, and the device further comprises a setting module:

when the ERPS state of the first node is an idle state, the setting module sets the port state identifiers of the packet receiving port of the first node and the packet sending port of the last node in the topology information to be in a blocking state, and sets the port state identifiers of other ports in the topology information to be in a forwarding state.

Optionally, the apparatus further includes a determining module and an adding module:

the determining module is configured to determine the maximum number of node information that the first NR-RB extension packet is allowed to carry according to the value of the first identification field;

the adding module is configured to, when it is determined that the number of node information currently carried in the first NR-RB extension packet is equal to the maximum number, increase a value of the first identification field by a preset value, increase the maximum number of node information allowed to be carried in the first NR-RB extension packet by the preset number, and trigger the adding module to perform the step of adding the node information of the first node in the received first NR-RB extension packet;

the determining module is further configured to trigger the adding module to perform the step of adding the node information of the first node in the received first NR-RB extension packet when it is determined that the number of the node information carried in the reserved field is smaller than the maximum number.

Optionally, the sending module is further configured to send, when the first node detects a link failure, an SF extension packet with a third identifier field to a host node, so that when a node that receives the SF extension packet determines that a value of the third identifier field is a third preset value, a failed link of the first node is determined according to a node identifier of the first node and topology information of the ERPS ring network, set a port state identifier of a packet receiving port of the first node and a port state identifier of a packet sending port of a last node in the topology information to a forwarding state, and set a port state identifier of a port corresponding to the failed link on the first node to a blocking state.

In a fifth aspect, a master node is provided, which comprises a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for the memory to complete mutual communication through the communication bus;

a memory for storing a computer program;

a processor for implementing the method steps of the first aspect when executing the program stored in the memory.

In a sixth aspect, a computer-readable storage medium is provided, having stored thereon a computer program which, when being executed by a processor, carries out the method steps of the first aspect.

In a seventh aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method for collecting topology information according to the first aspect.

In an eighth aspect, a network device is provided, which includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete communication with each other through the communication bus;

a memory for storing a computer program;

a processor for implementing the method steps of the second aspect when executing the program stored in the memory.

In a ninth aspect, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when executed by a processor, implements the method steps of the second aspect.

In a tenth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of collecting topology information as described in the second aspect above.

The method and the device for collecting the topology information are applied to the nodes in the ERPS ring network. The master node may send the first link restoration NR-loop protection link blocking RB extension packet, so that when determining that the first identifier field of the received first NR-RB extension packet is the first preset value and the first NR-RB extension packet does not carry node information of its own, the other nodes in the ERPS ring network add the node information of its own in the received first NR-RB extension packet and forward to the next node. The master node may receive a first NR-RB extension packet carrying node information of other nodes forwarded by a neighbor node, generate topology information of the ERPS ring network according to the node information of the master node and the node information of the other nodes, and then send a second NR-RB extension packet, so that when the other nodes determine that a second identifier field of the received second NR-RB extension packet is a second preset value and the second NR-RB extension packet carries the node information of the master node, it is determined that the second NR-RB extension packet carries the topology information, and the topology information is acquired. Therefore, the topology information of the ERPS ring network can be collected in each node in the ERPS ring network, and a network manager of the ERPS ring network can check the topology information of the ERPS ring network through any node, so that the current scale of the ERPS ring network is effectively judged.

Of course, not all advantages described above need to be achieved at the same time in the practice of any one product or method of the present application.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is an architecture diagram of an ERPS ring network according to an embodiment of the present application;

fig. 2 is a schematic diagram of a format of a conventional EPRS protocol packet according to an embodiment of the present application;

fig. 3 is a flowchart of a topology information collection method according to an embodiment of the present application;

fig. 4 is a flowchart of a topology information collection method according to an embodiment of the present application;

fig. 5 is a flowchart of a method for updating topology information according to an embodiment of the present disclosure;

fig. 6 is a flowchart of a method for updating topology information according to an embodiment of the present disclosure;

fig. 7 is a flowchart of an example of a topology information collection method provided in an embodiment of the present application;

fig. 8 is a flowchart of a method for updating topology information according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of a topology information collecting apparatus according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a topology information collecting apparatus according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a topology information collecting apparatus according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a topology information collecting apparatus according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a topology information collecting apparatus according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The embodiment of the application provides a method for collecting topology information, which can be applied to an ERPS ring network. Fig. 1 is a schematic diagram of an ERPS ring network according to an embodiment of the present application. The ERPS ring network comprises a main node, a neighbor node, a first common node and a second common node. The host node is connected with a second port of the first common node through a first port; the first common node is connected with the fourth port of the second common node through the third port; the second common node is connected with a sixth port of the neighbor node through a fifth port; the neighbor node is connected with the eighth port of the main node through the seventh port; the link between the main node and the neighbor node is an RPL link, correspondingly, the seventh port and the eighth port are RPL ports, and other ports are common ports. Meanwhile, according to the forwarding direction of the NR-RB packet, the first port, the third port, the fifth port, and the seventh port are packet sending ports, and the second port, the fourth port, the sixth port, and the eighth port are packet receiving ports.

For ease of understanding, the message format according to the present embodiment will be described first.

As shown in fig. 2, it is a schematic diagram of a format of a conventional EPRS protocol message, i.e., an english Ring automatic protection Switching (R-APS) message. As shown in Table I, the description of each field in the R-APS message is as follows:

watch 1

The embodiment of the application expands the NR-RB message to realize the collection and the updating of the topology. First, a Status Reserved (which may be defined as an Enhanced Report (ER) field in this application) is used as an identification field to distinguish a conventional NR-RB message from an NR-RB extended message. For example, after the node receives the NR-RB message, the node may determine whether the ER field in the NR-RB message is 0. And if the ER field is 0, the NR-RB message is a traditional NR-RB message. And if the ER field is not 0, the NR-RB message is an NR-RB extended message. Second, a Reserved field (Reserved 2 field) in the NR-RB extension message is used to carry node information.

Similarly, when a node (hereinafter referred to as a failed node) in the ERPS ring network detects a link failure corresponding to the local first port, the failed node may set the first port to a blocking state, and send an SF message to other nodes through the local second port, so that the master node sets a port (i.e., RPL port) state of a non-failed port in the blocking state to a forwarding state after receiving the SF message, thereby implementing link switching. In the embodiment of the application, the SF message is expanded to realize topology fault notification. First, the ER field is used to distinguish between a conventional SF message and an SF extension message used for topology fault notification. For example, after the node receives the SF message, the node may determine whether the ER field in the SF message is 0. If the ER field is 0, the SF message is the traditional SF message. And if the ER field is not 0, the SF message is an SF extension message. Secondly, a Reserved field (Reserved 2 field) in the SF extension message is used for carrying node information of the failed node. The specific content carried by the NR-RB extension packet and the SF extension packet will be described in detail later.

The following describes in detail a method for collecting topology information provided in an embodiment of the present application with reference to a specific implementation manner, and as shown in fig. 3, the specific steps are as follows:

step 301, sending the first NR-RB extension packet, so that when determining that the first identifier field of the received first NR-RB extension packet is the first preset value and the first NR-RB extension packet does not carry node information of itself, other nodes in the ERPS ring network add the node information of themselves in the received first NR-RB extension packet, and forward to the next node.

In practical application, the master node in the ERPS ring network may send an NR-RB message to other nodes in the ERPS ring network according to a preset sending period, so as to detect whether a link failure occurs in the ERPS ring network.

In this embodiment of the present application, every preset number of sending cycles, the master node may send a first NR-RB extension packet (for convenience of description, hereinafter referred to as an "Integrity Measurement (IM) packet") to a first common node connected to the master node. After the first ordinary node receives the first NR-RB extension message and completes corresponding processing, the first NR-RB extension message after processing is forwarded to the second ordinary node until the neighbor node forwards the first NR-RB extension message to the main node. The first NR-RB extension packet may be used for collecting and updating topology information, in addition to the function of the conventional NR-RB packet. In the embodiment of the present application, an NR-RB extension packet used for topology information collection is defined as a first IM packet.

Specifically, when sending the first IM message, the master node may add its own node information to a Reserved field (e.g., Reserved2) of the first IM message, and of course, may also send the first IM message that does not carry its own node information. In the embodiment of the present application, the example in which the master node sends the first IM packet carrying the node information of the master node is taken as an example for introduction, and other situations are similar to the example. Meanwhile, the master node may further set a first identification field (i.e., an ER field) in the first IM message to a first preset value. Wherein the first preset value is a value other than 0. Subsequently, after receiving the first IM message, the other nodes may add their own node information to the reserved field of the first IM message, thereby implementing the collection of topology information, and the detailed description will be made later on in the specific processing procedure.

For example, as shown in fig. 1, the master node sends a first IM packet to the first general node. And the reserved field of the first IM message carries node information of the main node. As shown in table two, the node information is an example carried in the reserved field of the first IM packet.

Watch two

Serial number	Node identification	Message receiving port	Message sending port
				1	Master node	The eighth port	First port

Step 302, receiving a first NR-RB extension message which is forwarded by a neighbor node and carries node information of other nodes, and generating topology information of an ERPS ring network according to the node information of the neighbor node and the node information of other nodes;

in the embodiment of the present application, the master node may receive the first IM packet forwarded by the neighbor node through the RPL link, and obviously, the reserved field of the first IM packet carries node information of all nodes in the ERPS ring network, that is, the topology information of the ERPS ring network is completely collected. Then, the master node may store the node information of each node carried in the reserved field of the first IM packet locally, thereby obtaining the topology information of the ERPS ring network.

For example, as shown in fig. 1, after passing through a first common node and a second common node, a first IM packet is sent to a master node by a neighboring node, and at this time, node information of all nodes carried in a reserved field of the first IM packet sent by the neighboring node may be stored locally by the master node, so that topology information of the ERPS ring network is obtained according to the node information of all nodes. As shown in table three, the node information is an example carried in the reserved field of the first IM packet.

Watch III

Serial number	Node identification	Message receiving port	Message sending port
				1	Master node	The eighth port	First port
2	First common node	Second port	Third port
				3	Second common node	Fourth port	The fifth port
4	Neighbor node	Sixth port	The seventh port

In addition, for the case that the master node sends the first IM packet without carrying the node information of itself, the master node needs to acquire the node information of itself after receiving the first IM packet with the node information of other nodes forwarded by the neighboring node. Then, the master node may generate topology information of the ERPS ring network according to the node information of the master node and node information of other nodes.

Step 303, sending a second NR-RB extension packet, so that when determining that a second identifier field of the received second NR-RB extension packet is a second preset value and the second NR-RB extension packet carries node information of itself, the other node determines that the second NR-RB extension packet carries topology information and acquires the topology information.

In the embodiment of the present application, a second NR-RB extension packet for topology information synchronization/update is defined as a second IM packet.

Specifically, in this embodiment of the application, after obtaining the topology information of the ERPS ring network, the master node may send a second NR-RB extension packet (hereinafter referred to as a second IM packet for convenience of description) to the first common node, so that after receiving the second IM packet, other nodes store the node information of each node in the topology information carried in the reserved field of the second IM packet, thereby obtaining the topology information of the ERPS ring network. And setting a second identification field (namely an ER field) in the second IM message as a second preset value, wherein the second preset value is a non-0 value.

Optionally, in this embodiment of the application, the node information may include a node identifier, a port identifier of a packet receiving port, and a port identifier of a packet sending port, where a first node in the topology information is a master node, and a last node is a neighbor node, and then, after the master node obtains the topology information of the ERPS ring network, the master node may further identify the port state of each port in the topology information according to the state of the ERPS ring network, and a specific processing procedure is as follows: if the ERPS state of the main node is an idle state, port state identifiers of a message receiving port of the first node and a message sending port of the last node in the topology information are set to be in a blocking state, and port state identifiers of other ports in the topology information are set to be in a forwarding state.

In the embodiment of the present application, if the ERPS state of the master node is an idle state, it indicates that the port state of the RPL port in the ERPS ring network is a blocking state, and the port states of other ports are forwarding states. Therefore, the master node may set the port states of the packet receiving port of the first node (i.e., the RPL port of the master node) and the packet transmitting port of the last node (i.e., the neighbor node) (i.e., the RPL port of the neighbor node) in the topology information to the blocking state, and set the port states of the other packet receiving ports (i.e., the normal ports) and the other packet transmitting ports (i.e., the normal ports) in the topology information to the forwarding state.

For example, as shown in fig. 1, the master node may set the port states of the RPL port of the master node and the RPL ports of the neighbor nodes to a blocking state, and set the port state of the normal port in the topology information to a forwarding state. As shown in table four, the port status of each port in the topology information is shown.

Watch four

Serial number	Node identification	Message receiving port/port status	Message sending port/port status
				1	Master node	Eighth Port/blocking State	First port/Forwarding status
2	First common node	Second port/Forwarding status	Third port/Forwarding status
				3	Second common node	Fourth port/Forwarding status	Fifth port/Forwarding status
4	Neighbor node	Sixth Port/Forwarding State	Seventh Port/blocking State

The embodiment of the application also provides a method for collecting the topology information. The method is applied to common nodes and neighbor nodes in the ERPS ring network. The following describes in detail a method for collecting topology information provided in an embodiment of the present application with reference to a specific implementation manner, and as shown in fig. 4, the specific steps are as follows:

step 401, receiving a first NR-RB extension packet sent by a master node.

In this embodiment of the present application, the first node may receive a first IM packet sent by the host node or forwarded by the previous node, and then may analyze the first IM packet.

Optionally, after receiving the NR-RB packet, the first node may distinguish the type of the NR-RB by determining whether a value of a reserved field of the NR-RB packet is 0 when the master node transmits the NR-RB packet in which the reserved field carries node information of the first node, where if the value of the reserved field is 0, it indicates that the reserved field does not carry node information, the NR-RB packet is an NR-RB packet in a conventional R-APS packet, and the first node may directly forward the NR-RB packet to a next node. If the value of the reserved field is not 0, it indicates that the reserved field carries node information, and the NR-RB packet is an NR-RB packet (i.e., an IM packet) for collecting or updating topology information. In addition, the first node can also judge whether the NR-RB message is an IM message according to the value of an ER field carried in the NR-RB message. The first node judges whether the NR-RB packet is a processing procedure of an IM packet according to a value of an ER field carried in the NR-RB packet, and details will be described later.

Step 402, if it is determined that the first identifier field of the received first NR-RB extension packet is the first preset value and the first NR-RB extension packet does not carry node information of its own, adding node information of its own in the received first NR-RB extension packet and forwarding to the next node.

In this embodiment, the first node may store a local node identifier (for example, a MAC address of the first node) in advance. The first node receives the NR-RB packet, and may determine whether a value of an ER field (i.e., a first identification field) of the NR-RB packet is a first preset value. Wherein the first preset value is a value other than 0. And if the ER field of the NR-RB message is a first preset value, judging that the NR-RB message is an NR-RB extension message. Since the NR-RB extension packet may be the first IM packet or the second IM packet, the first node may query whether node information of the first node exists in a reserved field of the NR-RB extension packet according to a node identifier of the first node. And if the reserved field does not have the node information of the NR-RB, the NR-RB extended message is a first IM message for collecting topology information. Correspondingly, the first node may add its own node information to the reserved field of the first IM packet to obtain the first IM packet carrying the node information of the first node. Then, the first node may send the first IM packet carrying the node information of the first node to the next node.

For example, as shown in fig. 1, the first node may be a first common node, a second common node, or a neighbor node. When the first node is the second normal node, as shown in table five, the node is the node received by the second normal node,

and reserving an example of the node information carried by the field in the first IM message forwarded by the first common node.

Watch five

Serial number	Node identification	Message receiving port	Message sending port
				1	Master node	The eighth port	First port
2	First common node	Second port	Third port

After the second common node receives the first IM packet, the node information of the second common node may be added to the reserved field of the first IM packet. And obtaining a first IM message added with the node information of the second common node, and sending the first IM message added with the node information of the second common node to the neighbor node. As shown in table six, the node information carried in the field is reserved in the first IM packet after the node information of the second common node is added.

Watch six

Serial number	Node identification	Message receiving port	Message sending port
				1	Master node	The eighth port	First port
2	First common node	Second port	Third port
				3	Second common node	Fourth port	The fifth port

After receiving the first IM message forwarded by the second common node, the neighbor node adds the node information of the neighbor node to the reserved field of the first IM message according to the same rule, and forwards the first IM message to the master node.

Step 403, receiving a second NR-RB extension packet sent by the master node.

In this embodiment of the present application, the first node may receive a second IM packet sent by the host node or forwarded by the previous node, and then may analyze the second IM packet.

Step 404, if it is determined that the second identifier field of the received second NR-RB extension packet is the second preset value and the second NR-RB extension packet carries node information of its own, it is determined that the second NR-RB extension packet carries topology information and the topology information is acquired.

In this embodiment, after receiving the NR-RB packet, the first node may determine whether a value of an ER field (i.e., a second identifier field) of the NR-RB packet is a second preset value. Wherein the second preset value is a value other than 0. And if the ER field of the NR-RB message is a second preset value, judging that the NR-RB message is an NR-RB extension message. Since the NR-RB extension packet may be the first IM packet or the second IM packet, the first node may determine whether the reserved field has its own node information according to its own node identifier (for example, the MAC address of the first node). And if the reserved field has the node information of the first node, the NR-RB extended message is a second IM message for synchronizing the topology information. Correspondingly, the first node may store the node information of each node carried in the reserved field to obtain the topology information of the ERPS ring network. The first node may then forward the second IM message to the next node.

For example, as shown in fig. 1, the first node may be a first common node, a second common node, or a neighbor node. When the first node is the second common node, as shown in table seven, the node information carried in the field is reserved in the second IM packet forwarded by the first common node and received by the second common node.

Watch seven

After receiving the second IM packet, the second common node may store the node information of each node carried in the reserved field to obtain the topology information of the ERPS ring network. Then, the second normal node may forward the second IM packet to the neighbor node.

Optionally, after obtaining the topology information of the ERPS ring network, the first node may further set the port state of each port in the topology information according to the ERPS state, where the specific processing procedure is as follows: the node information comprises a node identifier, a port identifier of a message receiving port and a port identifier of a message sending port; if the ERPS state of the node is an idle state, port state identifiers of a message receiving port of the first node and a message sending port of the last node in the topology information are set to be in a blocking state, and port state identifiers of other ports in the topology information are set to be in a forwarding state.

In this embodiment, if the ERPS state of the first node is an idle state, it indicates that the port state of the RPL port in the ERPS ring network is a blocking state, and the port states of other ports are forwarding states. Therefore, the first node may set the port states of the packet receiving port of the first node (i.e., the RPL port of the master node) and the packet transmitting port of the last node (i.e., the neighbor node) (i.e., the RPL port of the neighbor node) in the topology information to a blocking state, and set the port states of the other packet receiving ports (i.e., the normal ports) and the other packet transmitting ports (i.e., the normal ports) in the topology information to a forwarding state.

For example, as shown in fig. 1, the second common node may set the port states of the RPL port of the master node and the RPL port of the neighbor node to a blocking state, and set the port states of the common ports in the topology information to a forwarding state. As shown in table eight, the port status of each port in the topology information is shown.

Table eight

Optionally, the first node may further determine, according to a value of the first identifier field, a maximum number of node information that the first NR-RB extension packet is allowed to carry, and if it is determined that the number of node information currently carried by the first NR-RB extension packet is equal to the maximum number, increase the value of the first identifier field by a preset value, increase the maximum number of node information that the first NR-RB extension packet is allowed to carry by the preset number, and add node information of the first node in the received first NR-RB extension packet; and if the number of the node information carried by the reserved field is determined to be less than the maximum number, adding the node information of the first NR-RB extension message into the received first NR-RB extension message.

In this embodiment of the application, a value of the first identification field (i.e., the ER field) may indicate a number of bytes of the reserved field and a maximum number of node information that can be carried by the reserved field. As shown in table nine, the value of the first identification field, the number of bytes of the reserved field, and the maximum number of node information that can be carried by the reserved field are associated. The byte number occupied by the node information of each node is 12 bytes; every time the value of the first identification field is increased by 1, the byte number of the reserved field is increased by 24 bytes, and the maximum number of node information which can be carried by the reserved field is increased by 2; the maximum byte number of the reserved field can be expanded to 744 bytes, and the maximum number of node information which can be carried by the reserved field is 62. In addition, every time the value of the first identification field is incremented by 1, the number of bytes of the reserved field may also be increased by another number of bytes (e.g., 48 bytes), and the embodiment of the present application is not limited.

Watch nine

After the first node obtains the first identification field, the maximum number of node information that can be carried by the reserved field can be determined according to the value of the first identification field. The first node may then determine whether the number of node information carried by the currently reserved field is equal to the maximum number. And if the number of the node information carried by the current reserved field is equal to the maximum number, increasing the value of the first identification field by a preset numerical value, so that the maximum number of the node information allowed to be carried by the reserved field is increased by the preset number, and adding the node information of the first node in the reserved field. And if the number of the node information carried by the current reserved field is less than the maximum number, directly adding the node information of the first node in the reserved field.

For example, the value of the first identification field is 00010, and the number of node information carried by the currently reserved field is 4. The first node determines that the maximum number of node information that can be carried by the reserved field is 4 according to the value of the first identification field, and the number of node information carried by the current reserved field is equal to the maximum number. Then, the first node may increase the value of the first identification field by 1, increase the fourth reserved field by 24 bytes, and add the node information of the first node in the newly increased 24 bytes.

It should be noted that, at this time, the node information of the first node only occupies the first 12 bytes of the 24 bytes newly added to the reserved field. To ensure the integrity of the packet, the first node may set 0 to the last 12 bytes of the 24 bytes added to the reserved field, so as to align the packet.

The embodiment of the application also provides a method for updating the topology information, which is applied to the common node and the neighbor node in the ERPS ring network. The following describes in detail a method for collecting topology information provided in an embodiment of the present application with reference to a specific embodiment, as shown in fig. 5, the specific steps are as follows:

step 501, receiving an SF extension message.

The SF extension message comprises a reserved field, and the reserved field at least carries the node identification of the fault node.

In practice, the failed node may send an SF extension message (hereinafter referred to as a third IM message for convenience of description) to the connected node. And the third IM message comprises a reserved field, and the reserved field at least carries the node identification of the fault node. Meanwhile, the failed node may further set a third identification field (i.e., an ER field) in the SF extension message to a third preset value. Wherein the third preset value is a non-0 value. After receiving the SF message, the first node may determine whether a value of an ER field (i.e., a third identification field) of the SF message is a third preset value. Wherein the third preset value is a non-0 value. And if the ER field of the SF message is a third preset value, judging that the SF message is an SF extension message (namely, a third IM message). Then, the first node may analyze the third IM packet to obtain the node identifier of the failed node carried in the reserved field of the third IM packet.

Optionally, after receiving the SF message, the first node may determine whether a value of a reserved field of the SF message is 0, and if the value of the reserved field is 0, it indicates that the reserved field does not carry the node identifier of the faulty node, where the SF message is a conventional SF message, and the first node may directly forward the SF message to a next node. If the value of the reserved field is not 0, it indicates that the reserved field carries the node identifier of the failed node, and the SF message is an SF extension message (i.e., a third IM message). In addition, the first node may also determine whether the SF message is the third IM message according to a value of a third identification field (i.e., an ER field) carried in the SF message. The first node determines whether the SF message is a processing procedure of a third IM message according to a value of a third identification field carried in the SF message, and details will be described later.

Step 502, according to the node identifier of the failed node and the topology information of the ERPS ring network, determining the failed port of the failed node, setting the port states of the message receiving port of the first node and the message sending port of the last node in the topology information as forwarding states, and setting the port state of the failed port of the failed node as blocking states.

In the embodiment of the present application, after obtaining the node identifier of the failed node carried in the reserved field of the third IM packet, the first node may determine the failed port of the failed node according to the node identifier of the failed node and the topology information of the ERPS ring network. The first node may determine, according to the topology information, that a port on the failed node on one side of the first node is a normal port, and another port is a failed port.

After the first node determines the failure port of the failure node, the port states of the packet receiving port (i.e., the RPL port of the master node) of the first node (i.e., the master node) and the packet sending port (i.e., the RPL port of the neighbor node) of the last node (i.e., the neighbor node) in the topology information may be set to be the forwarding state, and the port state of the failure port of the failure node may be set to be the blocking state. In this way, the technician can determine the failed node and the failed port based on the topology information stored on the first node.

For example, as shown in fig. 1, when a link between a first general node and a second general node fails, the second general node may send a third IM packet to a neighboring node. And the third IM message comprises a reserved field, and the reserved field at least carries the node identification of the second common node. After receiving the third IM packet, the neighboring node may determine that the fourth port of the second common node is a failed port according to the node identifier of the second common node and the locally stored topology information. Then, the neighbor node may set the port states of the RPL port of the master node and the RPL port of the neighbor node to a forwarding state, and set the port state of the fourth port of the second common node to a blocking state. As shown in table ten, after the topology information is updated for the neighboring node, the neighboring node will forward the third IM packet to the master node according to the port status of each port.

Watch ten

Serial number	Node identification	Message receiving port/port status	Message sending port/port status
				1	Master node	Eighth Port/Forwarding State	First port/Forwarding status
2	First common node	Second port/Forwarding status	Third port/Forwarding status
				3	Second common node	Fourth Port/blocking State	Fifth port/Forwarding status
4	Neighbor node	Sixth Port/Forwarding State	Seventh Port/Forwarding State

Based on the same principle, the first common node sends the third IM message to the master node through the second port, so that the master node can determine the link failure between the third port of the first common node and the fourth port of the second common node according to the third IM message forwarded by the neighbor node and the failure information carried in the third IM message sent by the first common node, and set the port identifiers of the third port and the fourth port as blocking.

Step 503, the SF extension packet is sent to the next node.

In this embodiment of the application, after the first node updates the topology information according to the received third IM message, the first node may send the third IM message to the next node, so that the next node updates the topology information according to the received third IM message.

Optionally, when any first node detects a link failure, an SF extension packet carrying a third identification field is sent to the host node, so that when the node receiving the SF extension packet determines that the value of the third identification field is a third preset value, a failure link of the first node is determined according to the node identification of the first node and the topology information of the ERPS ring network, the port state identifications of the packet receiving port of the first node and the packet sending port of the last node in the topology information are set to be in a forwarding state, and the port state identification of the port corresponding to the failure link on the first node is set to be in a blocking state.

In addition, the first node may also set the port states of the packet receiving port of the first node (i.e., the master node) (i.e., the RPL port of the master node) and the packet sending port of the last node (i.e., the neighbor node) (i.e., the RPL port of the neighbor node) in the topology information to a forwarding state, and set the port state of the failed port to a blocking state.

The embodiment of the application also provides a method for updating the topology information, which is applied to the main node in the ERPS ring network. The following describes in detail a method for collecting topology information provided in an embodiment of the present application with reference to a specific implementation manner, and as shown in fig. 6, the specific steps are as follows:

step 601, receiving an SF extension packet which is sent by a node when detecting a link failure and carries a third identification field, where the SF extension packet at least includes node information of a node, and one node is a common node or a neighbor node.

In the embodiment of the application, when a node in the ERPS ring network fails, both the two nodes connected to the node send the third IM message to the ERPS ring network. Or, when a link between two nodes in the ERPS ring network fails, both the two nodes may send the third IM message to the ERPS ring network. Correspondingly, the master node can receive two third IM messages through the common port and the RPL port. And the third IM message comprises a reserved field, and the reserved field at least carries the node identification of the fault node. For each third IM message, the master node may analyze the third IM message to obtain a node identifier of the failed node carried in the reserved field of the third IM message.

For example, as shown in fig. 1, when a link between the first general node and the second general node fails, the first general node may send a third IM packet to the master node through the second port. And the reserved field in the third IM message carries the node identification of the first common node. Similarly, the second common node may also send the third IM packet to the neighboring node through the fifth port. And the neighbor node forwards the received third IM message to the master node, wherein a reserved field in the third IM message carries the node identification of the second common node.

Step 602, if it is determined that the value of the third identification field is the third preset value, determining a fault link of a node according to the node identifier of the node and the topology information of the ERPS ring network, setting the port state identifiers of the message receiving port of the first node and the message sending port of the last node in the topology information to be in a forwarding state, and setting the port state identifier of the port corresponding to the fault link on the node to be in a blocking state.

In the embodiment of the present application, after receiving the SF message, the master node may determine whether a value of an ER field (i.e., a third identification field) of the SF message is a third preset value. Wherein the third preset value is a non-0 value. And if the ER field of the SF message is a third preset value, judging that the SF message is an SF extension message (namely, a third IM message). Then, the master node may analyze the third IM message to obtain a node identifier of the fault node carried in the reserved field in the third IM message. Then, the master node may determine the failure port of the failed node according to the node identifier of the failed node and the topology information of the ERPS ring network, and update the topology information. The processing procedure of determining the fault port of the fault node by the master node according to the node identifier of the fault node and the topology information of the ERPS ring network and updating the topology information is similar to the processing procedure of the step 502.

For example, as shown in fig. 1, after receiving the third IM messages sent by the first and second common nodes, the master node may update the topology information. As shown in table eleven, the port state of each port is updated for the master node with respect to the topology information.

Watch eleven

Serial number	Node identification	Message receiving port/port status	MessageSending port/port status
				1	Master node	Eighth Port/Forwarding State	First port/Forwarding status
2	First common node	Second port/Forwarding status	Third port/blocking state
				3	Second common node	Fourth Port/blocking State	Fifth port/Forwarding status
4	Neighbor node	Sixth Port/Forwarding State	Seventh Port/Forwarding State

Fig. 7 is a flowchart illustrating an example of a topology information collection method according to an embodiment of the present application. As shown in fig. 7, the specific processing procedure is as follows:

step 701: and the main node sends a first NR-RB extension message to the first common node.

The first NR-RB extension message comprises a reserved field, and the current reserved field of the first NR-RB extension message carries node information of the main node.

Step 702, a first common node receives a first NR-RB extension packet sent by a master node.

In step 703, the first normal node adds its own node information to the reserved field of the first NR-RB extension packet, and forwards the first NR-RB extension packet to the second normal node after adding its own node information.

In practical application, the last common node in the ERPS ring network correspondingly processes the received first NR-RB extension packet and forwards the first NR-RB extension packet to the next common node, until the last common node forwards the first NR-RB extension packet to the neighboring node, where the neighboring node correspondingly processes the received first NR-RB extension packet and forwards the first NR-RB extension packet to the host node.

Step 704, the master node receives the first NR-RB extension packet carrying the node information of each node in the ERPS ring network in the reserved field forwarded by the neighboring node, and stores the node information of each node to obtain the topology information of the ERPS ring network.

Step 705, the master node sends a second NR-RB extension packet to the first normal node.

Wherein, the reserved field of the second NR-RB extension packet carries topology information of the ERPS ring network.

Step 706, the first common node receives the second NR-RB extension packet sent by the master node.

And 707, the first common node stores the node information of each node carried in the reserved field, obtains topology information of the ERPS ring network, and forwards the second NR-RB extension packet to the second common node.

In practical application, the last common node in the ERPS ring network obtains the topology information of the ERPS ring network from the received second NR-RB extension packet, and forwards the second NR-RB extension packet to the next common node until the neighbor node obtains the topology information of the ERPS ring network from the received second NR-RB extension packet.

Step 708, if the ERPS state of the first common node is the idle state, setting the port states of the packet receiving port of the first node and the packet sending port of the last node in the topology information to be the blocking state, and setting the port states of the other packet receiving ports and the other packet sending ports in the topology information to be the forwarding state.

Of course, when any node in the ERPS ring network determines that the state of the ERPS ring network is the idle state and the topology information of the ERPS ring network is locally stored, the operation of setting the port states of the message receiving port of the first node and the message sending port of the last node in the topology information to be the blocking state and setting the port states of other message receiving ports and other message sending ports in the topology information to be the forwarding state is performed.

The specific processing procedure of steps 701 to 708 is similar to that of steps 301 to 303 and 401 to 404.

Fig. 8 is a flowchart illustrating an example of a method for updating topology information according to an embodiment of the present application. In this example, the link between the first and second regular nodes fails. As shown in fig. 8, the specific processing procedure is as follows:

step 801, a first common node sends a first SF extension message to a host node, and a second common node sends a second SF extension message to a neighbor node.

The first SF extension message includes a reserved field, the reserved field carries a node identifier of the first common node, the second SF extension message includes a reserved field, and the reserved field carries a node identifier of the second common node.

Certainly, the reserved field of the first SF extension packet sent by the first common node may also carry node information of all nodes between the first common node and the master node; the reserved field of the first SF extension message sent by the second common node can carry node information of all nodes between the second common node and the neighbor node; therefore, the master node can determine the fault point according to the locally stored complete topology information of the ERPS ring network and the partial topology information of the ERPS ring network carried by the first SF extension message sent by the first common node and the second common node. Certainly, in the process of forwarding the first SF extension packet, when other common nodes receive the corresponding first SF extension packet, the failure point may also be determined according to locally stored topology information of the complete ERPS ring network and partial topology information of the ERPS ring network carried by the first SF extension packet.

Step 802, the master node receives the first SF extension packet through the first port and receives the second SF extension packet through the eighth port.

Step 803, the master node determines, according to the node identifier of the first common node, the node identifier of the second common node, and the topology information of the ERPS ring network, that the third port of the first common node and the fourth port of the second common node are faulty ports, sets the port states of the packet receiving port of the first node and the packet sending port of the last node in the topology information to a forwarding state, and sets the port states of the third port of the first common node and the fourth port of the second common node to a blocking state.

The specific processing procedure of steps 801 to 803 is similar to that of steps 501 to 503 and steps 601 to 602.

The method and the device for collecting the topology information are applied to the nodes in the ERPS ring network. The master node may send a first NR-RB extension packet to the first node. The first NR-RB extension packet includes a first reserved field, where the first reserved field carries node information of the master node. And after receiving the first NR-RB extension message, the first node adds own node information into the first reserved field and forwards the first NR-RB extension message added with the own node information to the next node. Subsequently, after receiving a first NR-RB extension message which is forwarded by a neighbor node and carries the node information of each node in the ERPS ring network in a first reserved field, the main node stores the node information of each node to obtain the topology information of the ERPS ring network. Then, the main node sends a second NR-RB extension message to the first node. And the second reserved field of the second NR-RB extension message carries node information of each node in the topology information of the ERPS ring network. And after receiving the second NR-RB extension message, the first node stores the node information of each node carried in the second reserved field to obtain the topology information of the ERPS ring network, and forwards the second NR-RB extension message to the second node. Therefore, the topology information of the ERPS ring network can be collected in each node in the ERPS ring network, and a network manager of the ERPS ring network can check the topology information of the ERPS ring network through any node, so that the current scale of the ERPS ring network is effectively judged.

Based on the same technical concept, as shown in fig. 9, an embodiment of the present application further provides a device for collecting topology information, where the device is applied to a master node in an ethernet ring network protection switching ERPS ring network, and the device includes a sending module 910, a receiving module 920, and a generating module 930:

a sending module 910, configured to send a first link restoration NR-loop protection link blocking RB extension packet, so that when it is determined that a first identifier field of a received first NR-RB extension packet is a first preset value and the first NR-RB extension packet does not carry node information of its own, other nodes in the ERPS ring network add node information of its own in the received first NR-RB extension packet, and forward the node information to a next node;

when the receiving module 920 receives a first NR-RB extension packet carrying node information of other nodes forwarded by a neighboring node, the generating module 920 is configured to generate topology information of an ERPS ring network according to the node information of the master node and the node information of other nodes;

the sending module 910 is further configured to send a second NR-RB extension packet, so that when determining that a second identifier field of the received second NR-RB extension packet is a second preset value and the second NR-RB extension packet carries node information of itself, the other node determines that the second NR-RB extension packet carries topology information and acquires the topology information.

Optionally, the node information includes a node identifier, a port identifier of a message receiving port, and a port identifier of a message sending port; the first node in the topology information is a main node, and the last node is a neighbor node;

as shown in fig. 10, the apparatus further includes a setting module 940:

when the ERPS state of the master node is the idle state, the setting module 940 sets the port state identifiers of the packet receiving port of the first node and the packet sending port of the last node in the topology information to be in the blocking state, and sets the port state identifiers of the other ports in the topology information to be in the forwarding state.

Optionally, the receiving module 920 is further configured to receive an SF extension packet which is sent by a node when detecting a link failure and carries a third identification field, where the SF extension packet at least includes node information of a node, and one node is a common node or a neighboring node;

the setting module 940 is further configured to, when it is determined that the value of the third identification field is the third preset value, determine a faulty link of a node according to the node identifier of the node and the topology information of the ERPS ring network, set the port state identifiers of the packet receiving port of the first node and the packet sending port of the last node in the topology information to be in a forwarding state, and set the port state identifier of the port corresponding to the faulty link on the node to be in a blocking state.

Based on the same technical concept, as shown in fig. 11, an embodiment of the present application further provides a device for collecting topology information, where the device is applied to a first node in an ethernet ring network protection switching ERPS ring network, where the first node is a common node or a neighbor node, the ERPS ring network further includes a master node, and the device includes a receiving module 1110, an adding module 1120, a sending module 1130, and an obtaining module 1140:

a receiving module 1110, configured to receive an RB extension packet blocked by a first link restoration NR-loop protection link sent by a host node;

an adding module 1120, configured to add node information of a first node in a received first NR-RB extension packet when it is determined that a first identifier field of the received first NR-RB extension packet is a first preset value and the first NR-RB extension packet does not carry node information of the first node, and a sending module 1130, configured to forward the first NR-RB extension packet to a next node;

the receiving module 1110 is further configured to receive an RB extension packet blocked by the second link restoration NR-loop protection link sent by the host node;

an obtaining module 1140, configured to determine that the second NR-RB extension packet carries topology information and obtain the topology information when it is determined that the second identifier field of the received second NR-RB extension packet is the second preset value and the second NR-RB extension packet carries node information of the first node.

Optionally, the node information includes a node identifier, a port identifier of a message receiving port, and a port identifier of a message sending port; as shown in fig. 12, the apparatus further includes a setting module 1150, where the first node in the topology information is a master node and the last node is a neighbor node:

when the ERPS state of the first node is the idle state, the setting module 1150 sets the port state identifiers of the packet receiving port of the first node and the packet sending port of the last node in the topology information to be in the blocking state, and sets the port state identifiers of other ports in the topology information to be in the forwarding state.

Optionally, as shown in fig. 13, the apparatus further comprises a determining module 1160 and an adding module 1170:

a determining module 1160, configured to determine, according to a value of the first identifier field, a maximum number of node information that is allowed to be carried by the first NR-RB extension packet;

an adding module 1170, configured to, when it is determined that the number of node information currently carried in the first NR-RB extension packet is equal to the maximum number, increase a value of the first identification field by a preset value, increase the maximum number of node information allowed to be carried in the first NR-RB extension packet by the preset number, and trigger the adding module 1120 to perform a step of adding the node information of the first node in the received first NR-RB extension packet;

the determining module 1160 is further configured to trigger the adding module 1120 to perform the step of adding the node information of the first node in the received first NR-RB extension message when it is determined that the number of the node information carried in the reserved field is smaller than the maximum number.

Optionally, the sending module 1130 is further configured to send, when the first node detects a link failure, an SF extension packet with a third identifier field to the host node, so that when the node receiving the SF extension packet determines that the value of the third identifier field is a third preset value, the node receiving the SF extension packet determines a failed link of the first node according to the node identifier of the first node and the topology information of the ERPS ring network, set the port state identifiers of the packet receiving port of the first node and the packet sending port of the last node in the topology information to be in a forwarding state, and set the port state identifier of the port corresponding to the failed link on the first node to be in a blocking state.

The method for collecting the topology information provided by the embodiment of the application is applied to the nodes in the ERPS ring network. The master node may send a first NR-RB extension packet to the first node. The first NR-RB extension packet includes a first reserved field, where the first reserved field carries node information of the master node. And after receiving the first NR-RB extension message, the first node adds the node information of the first node in the first reserved field and forwards the first NR-RB extension message added with the node information of the first node to the second node. Subsequently, after receiving a first NR-RB extension message which is forwarded by a neighbor node and carries the node information of each node in the ERPS ring network in a first reserved field, the main node stores the node information of each node to obtain the topology information of the ERPS ring network. Then, the main node sends a second NR-RB extension message to the first node. And the second reserved field of the second NR-RB extension message carries node information of each node in the topology information. And after receiving the second NR-RB extension message, the first node stores the node information of each node carried in the second reserved field to obtain the topology information of the ERPS ring network, and forwards the second NR-RB extension message to the second node. Therefore, the topology information of the ERPS ring network can be collected in each node in the ERPS ring network, and a network manager of the ERPS ring network can check the topology information of the ERPS ring network through any node, so that the current scale of the ERPS ring network is effectively judged.

The embodiment of the present application further provides a network device, as shown in fig. 14, which includes a processor 1401, a communication interface 1402, a memory 1403 and a communication bus 1404, wherein the processor 1401, the communication interface 1402, and the memory 1403 are communicated with each other via the communication bus 1404,

a memory 1403 for storing a computer program;

the processor 1401, when executing the program stored in the memory 1403, is configured to implement the following method steps:

the method further comprises the following steps:

Optionally, the method further includes:

The embodiment of the present application further provides a network device, as shown in fig. 15, which includes a processor 1501, a communication interface 1502, a memory 1503, and a communication bus 1504, where the processor 1501, the communication interface 1502, and the memory 1503 complete communication with each other through the communication bus 1504,

a memory 1503 for storing a computer program;

the processor 1501, when executing the program stored in the memory 1503, implements the following method steps:

Optionally, the method further includes:

The communication bus mentioned in the network device may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.

The communication interface is used for communication between the network device and other devices.

The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.

The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other Programmable logic devices, discrete Gate or transistor logic devices, or discrete hardware components.

In yet another embodiment provided by the present application, a computer-readable storage medium is further provided, in which a computer program is stored, and the computer program, when executed by a processor, implements the steps of any one of the above-mentioned topology information collection methods.

In yet another embodiment provided by the present application, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method for collecting topology information of any of the above embodiments.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A method for collecting topology information is applied to a main node in an Ethernet Ring Protection Switching (ERPS) ring network, and comprises the following steps:

2. The method of claim 1, wherein the node information comprises a node identifier, a port identifier of a packet receiving port, and a port identifier of a packet sending port; the first node in the topology information is a main node, and the last node is a neighbor node;

the method further comprises the following steps:

3. The method of claim 2, further comprising:

4. A method for collecting topology information is characterized in that the method is applied to a first node in an Ethernet Ring Protection Switching (ERPS) ring network, the first node is a common node or a neighbor node, the ERPS ring network further comprises a main node, and the method comprises the following steps:

5. The method of claim 4, wherein the node information comprises a node identifier, a port identifier of a packet receiving port, and a port identifier of a packet sending port; the first node in the topology information is a master node, and the last node is a neighbor node, and the method further comprises:

6. The method of claim 4, wherein before adding node information of itself to the received first NR-RB extension message, the method further comprises:

7. The method of claim 5, further comprising:

8. The device for collecting topology information is applied to a master node in an Ethernet Ring Protection Switching (ERPS) ring network, and comprises a sending module, a receiving module and a generating module:

9. The apparatus of claim 8, wherein the node information comprises a node identifier, a port identifier of a packet receiving port, and a port identifier of a packet sending port; the first node in the topology information is a main node, and the last node is a neighbor node;

the device further comprises a setting module:

10. The apparatus according to claim 9, wherein the receiving module is further configured to receive an SF extension packet which is sent by a node when detecting a link failure and carries a third identification field, where the SF extension packet at least includes node information of the node, and the node is a normal node or a neighboring node;

11. The utility model provides a collection device of topology information, its characterized in that, the device is applied to first node in the ethernet ring protection switching ERPS looped netowrk, first node is ordinary node or neighbor node, still include the host node in the ERPS looped netowrk, the device includes receiving module, adds module, sending module and acquisition module:

12. The apparatus of claim 11, wherein the node information comprises a node identifier, a port identifier of a packet receiving port, and a port identifier of a packet sending port; the first node in the topology information is a main node, the last node is a neighbor node, and the device further comprises a setting module:

13. The apparatus of claim 11, further comprising a determining module and an adding module:

14. The apparatus according to claim 12, wherein the sending module is further configured to send, when the first node detects a link failure, an SF extension packet with a third identifier field to a master node, so that when a node that receives the SF extension packet determines that a value of the third identifier field is a third preset value, a failed link of the first node is determined according to a node identifier of the first node and topology information of the ERPS ring network, a port state identifier of a packet receiving port of the first node and a port state identifier of a packet sending port of a last node in the topology information are set to be in a forwarding state, and a port state identifier of a port corresponding to the failed link on the first node is set to be in a blocking state.