Network nodes in a ring network

Patent metadata

Field	Value
Publication number	US-10567195-B2
Application number	US-201515763772-A
Country	US
Kind code	B2
Filing date	Sep 30, 2015
Priority date	Sep 30, 2015
Publication date	Feb 18, 2020
Grant date	Feb 18, 2020

Abstract

According to an example method, it is determined that a first network node in a ring network is claimed by a first managing device and a second network node in the ring network is claimed by a second managing device. The ring network includes a single link to a customer network. The second network node is then isolated from the first network node. A separate linear network is formed including the second network node. Upon reset of the second network node to an unclaimed status, the second network node is claimed by the first managing device.

First claim

What is claimed is:

1. A method comprising:
determining, by a first network node in a ring network, that the first network node is managed by a first managing device and a second and a third network nodes in the ring network are managed by a second managing device, wherein the ring network has a first link to a customer network, and wherein the second managing device is configured to manage the ring network;
in response to the determination, isolating the first network node from the ring network by disabling, by the first network node, flow of data traffic between the first network node, and the second and third network nodes;
forming a separate second link to the customer network in response to the isolation wherein the first and second links are not part of the ring network; and
resetting the first network node to remove association with the first managing device; and
joining the ring network under management of the second managing device.

2. The method of claim 1 , wherein joining the ring network under management of the second managing device comprises sending a status message comprising a claimed device identifier associated with the first network node.

3. The method of claim 1 , further comprising:
in response to determining that the second network node is managed by the first managing device, dropping a status message from the second network node.

4. The method of claim 3 , further comprising initiating the isolation of the first network node in response to dropping the status message.

5. The method of claim 3 , wherein the status message is a Continuity Check Message (CCM) of an Ethernet Ring Protection Switching (ERPS) protocol.

6. The method of claim 1 , wherein isolating the first network node comprises maintaining exchange of management traffic between the first network node, and the second and third network nodes.

7. The method of claim 6 , wherein the first network node joins the ring network under management of the second managing device based on the management traffic between the first network node, and the second and third network nodes.

8. The method of claim 1 , wherein resetting the first network node comprises receiving a reset command via the second link to the customer network.

9. The method of claim 1 ,
wherein resetting the first network node comprises deleting a claimed device identifier corresponding to the first managing device.

10. The method of claim 1 , further comprising comparing a first claimed device identifier of the first network node with a second claimed device identifier of a second network node, wherein the first and second claimed device identifiers correspond to the first and second managing devices, respectively.

11. A first network node in a ring network, comprising
a hardware controller configured to:
determine that the first network node is managed by a first managing device, and a second and a third network nodes in the ring network are managed by a second managing device, wherein the ring network has a first link to a customer network, and wherein the second managing device is configured to manage the ring network;
in response to the determination, isolate the first network node from the ring network by disabling, by the first network node, flow of data traffic between the first network node, and the second and third network nodes; and
form a separate second link to the customer network in response to the isolation, wherein the first and second links are not part of the ring network; and

a ring module configured to:
reset the first network node to remove association with the first managing device; and
join the ring network under management of the second managing device.

12. The first network node of claim 11 , wherein joining the ring network under management of the second managing device comprises sending a status message comprising a claimed device identifier associated with the first network node.

13. The first network node of claim 12 , wherein the status message is a Continuity Check Message (CCM) of an Ethernet Ring Protection Switching (ERPS) protocol.

14. The first network node of claim 11 , wherein the hardware controller is further configured to maintain exchange of management traffic between the first network node, and the second and third network nodes.

15. The first network node of claim 11 , wherein the ring module is further configured to reset the first network node in response to receiving a reset command via the second link to the customer network.

16. A non-transitory machine readable storage medium comprising instructions that when executed cause a computer to:
determine, by a first network node in a ring network, that the first network node is managed by a first managing device, and a second and a third network nodes in the ring network are managed by a second managing device, wherein the ring network has a first link to a customer network and a single ring protection link owner, and wherein the second managing device is configured to manage the ring network;
in response to the determination, isolate the first network node from the ring network by disabling, by the first network node, flow of data traffic between the first network node, and the second and third network nodes;
form a separate second link to the customer network in response to the isolation, wherein the first and second links are not part of the ring network,
reset the first network node to remove association with the first managing device; and
join the ring network under management of the second managing device.

17. The non-transitory machine readable storage medium of claim 16 , wherein isolating the first network node from the first network node comprises:
maintaining exchange of management traffic between the first network node, and the second and third network nodes.

18. The non-transitory machine readable storage medium of claim 16 ,
wherein resetting the first network node comprises deleting a claimed device identifier corresponding to the first managing device.

19. The non-transitory machine readable storage medium of claim 16 , wherein isolating the first network node comprises maintaining exchange of management traffic between the first network node, and the second and third network nodes.

20. The non-transitory machine readable storage medium of claim 16 , wherein resetting the first network node comprises receiving a reset command via the second link to the customer network.

Assignees

• Hewlett Packard Entpr Dev Lp

Inventors

• Murray Christopher

Classifications

• H04L41/0654

  using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437) · CPC title

• H04L43/0811

  by checking connectivity · CPC title

• H04L69/40

  for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title

• H04L12/437 Primary

  Ring fault isolation or reconfiguration {(for SDH/SONET ring networks H04J3/085)} · CPC title

• H04L41/12

  Discovery or management of network topologies · CPC title