Monitoring connectivity in ring networks
A system, method, and device for monitoring the connectivity of a network that has been configured in a ring topology, such as an Ethernet ring network. The ring network includes a plurality of nodes, each with first port and a second port for forwarding CC messages to respective neighbor nodes, and an MEP for forming and processing the CC messages. Of the plurality of network nodes, neighbor nodes are selected as CC forwarding nodes and, after a database on each node has been configured, the selected nodes begin sending CC messages to each other via the ring network, beginning with transmission to a non-selected node. If a selected node fails to receive an expected CC message, it transmits a fault notification and ceases sending CC messages. The network then reselects CC message forwarding nodes, which begin forwarding CC messages until another fault is detected or the network is otherwise reconfigured.
1. In a network comprising a plurality of nodes configured in a ring topology, a method comprising:
selecting from the plurality of nodes a first pair of neighboring CC (connectivity check) message generating nodes, wherein at least one node of the first pair of nodes comprises a port that is down or designated as a blocked or backup port;
generating CC messages in each of the selected CC message generating nodes and forwarding them to the respective other CC generating node; and
determining if a fault in the network has occurred;
wherein at least one node of the plurality comprises an MEP (maintenance end point) and is not in the selected first pair of neighboring CC message generating nodes, and further comprising configuring the non-selected at least one node to not generate CC messages.
2. The method of claim 1 , wherein the network is an Ethernet network.
3. The method of claim 2 , wherein selecting a first pair of CC message generating nodes comprises executing an STP (spanning tree protocol) routine.
4. The method of claim 3 , wherein the CC messages are generated in a respective MEP (maintenance end point) associated with each selected CC message generating node.
5. The method of claim 4 , wherein each of the plurality of nodes comprises an MEP, and further comprising configuring each MEP in a non-selected node to not generate CC messages.
6. The method of claim 5 , further comprising configuring each MEP in a non-selected node not to process CC messages received in their respective node.
7. The method of claim 1 , wherein determining if a fault has occurred comprises failing to receive in a selected node at least one expected CC message generated by its neighbor node.
8. The method of claim 7 , wherein failing to receive at least one expected CC message comprises receiving a CC message from a node other than its neighbor node.
9. The method of claim 7 , wherein failing to receive at least one expected CC message comprises failing to receive a predetermined number of such CC messages in a predetermined time period.
10. The method of claim 1 , further comprising, upon determining that a fault in the network has occurred, transmitting a fault notification.
11. The method of claim 10 , wherein the fault notification is transmitted by broadcasting to all other nodes in the plurality of nodes.
12. The method of claim 10 , further comprising selecting from the plurality of nodes a second pair of neighboring CC (connectivity check) message generating nodes, wherein at least one node of the second pair of nodes comprises a port that is down or designated as a blocked or backup port.
13. The method of claim 12 , further comprising ceasing to generate CC messages in the first pair of selected nodes.
14. A node for use in an Ethernet ring network, comprising:
a first port and a second port for communicating with respective neighbor nodes in the ring network;
a network interface for determining whether either the first port or the second port is a down port or designated as a blocked or backup port;
an MEP (maintenance end point) for generating CC (connectivity check) messages if either the first port or the second port is determined to be a down port or designated as a blocked or backup port, wherein the MEP is arranged to not generate CC messages if the network interface determines that neither the first port nor the second port is a down port or designated as a blocked or backup port;
a controller for controlling at least the network interface and the MEP; and
a memory device in communication with the controller.
15. The node of claim 14 , wherein the MEP is further arranged to not process received CC messages if the network interface determines that neither the first port nor the second port is a down port or designated as a blocked or backup port.
16. The node of claim 15 , further comprising a fault notification generator for generating a fault notification in the event that the node fails to receive an expected CC message from a neighbor node.
17. The communication system of claim 16 , wherein the memory device comprises a PDB (permanent database) for storing the MAC (media access control) address of neighbor nodes.
18. A communication system comprising a plurality of nodes, wherein each node comprises:
a first port and a second port for communicating with respective neighbor nodes in the ring network;
a network interface for determining whether either the first port or the second port is a down port or designated as a blocked or backup port;
an MEP (maintenance end point) for generating CC (connectivity check) messages if either the first port or the second port is determined to be a down port or designated as a blocked or backup port wherein the MEP is arranged to not generate CC messages if the network interface determines that neither the first port nor the second port is a down port or designated as a blocked or backup port;
a controller for controlling at least the network interface and the MEP; and
a memory device in communication with the controller, the memory device comprising a PDB (permanent database) for storing the MAC (media access control) address of neighbor nodes.
19. The communication system of claim 18 , wherein the plurality of nodes is logically configured in a ring topology.