Systems and methods for a self-healing carrier ethernet topology
First Claim
1. A method for self-healing Carrier Ethernet, comprising:
- statically provisioning a first and second Ethernet path between a plurality of nodes interconnected in one of a ring and a linear chain topology, wherein one of the plurality of nodes comprises a head-end node configured to provide switching on the first and second paths for local and external network traffic;
provisioning a management channel comprising a distinct path from the first and second path based on a Virtual Local Area Network Identifier;
transmitting data from a source node on the first path;
periodically generating distinct Continuity Check Messages (CCMs) by the plurality of nodes on the management channel;
monitoring the distinct CCMs to determine a failure condition within a path comprising failure to receive a plurality of the distinct CCMs;
responsive to the failure condition, transmitting a CCM with a Remote Defect Indicator (RDI) to the source node, wherein the CCM message with the RDI is generated at a node of the plurality of nodes located on a receive side of a failed primary path; and
switching data from the first path to the second path responsive to the CCM with the Remote Defect Indicator, wherein each of the plurality of nodes switches the data to the second path upon reception at each of the plurality of nodes of the CCM with the Remote Defect Indicator;
wherein the CCMs are multicast by each of the plurality of nodes, and the one of the ring and linear chain topology are operable to constrain the multicast CCMs to traversing the one of the ring and linear chain without modification of the multicast CCMs.
6 Assignments
0 Petitions
Accused Products
Abstract
Systems and methods for self-healing Ethernet topologies which are compatible with PBT, which use standards-based protocols, which do not self-configure, and which use Ethernet OAM are provided. Interconnected nodes are configured with a primary and secondary path which is determined by VLANs, MPLS label, Provider Backbone Bridge Traffic Engineering (PBB-TE) VLAN ID (VID), Frame Relay (FR), Asynchronous Transfer Mode (ATM) Virtual Circuits (VCs), and the like. One or more head-end nodes are designated for terminating each path and for performing cross-connects between the primary and secondary paths. IEEE 802.1ag Continuity Check Messages (CCM) are transmitted by all nodes on both the primary and secondary routes. Responsive to a loss of a predetermined number of CCM messages, traffic is switched to the secondary route. In non-fault conditions, both the paths for the primary and secondary routes can carry traffic.
-
Citations
19 Claims
-
1. A method for self-healing Carrier Ethernet, comprising:
-
statically provisioning a first and second Ethernet path between a plurality of nodes interconnected in one of a ring and a linear chain topology, wherein one of the plurality of nodes comprises a head-end node configured to provide switching on the first and second paths for local and external network traffic; provisioning a management channel comprising a distinct path from the first and second path based on a Virtual Local Area Network Identifier; transmitting data from a source node on the first path; periodically generating distinct Continuity Check Messages (CCMs) by the plurality of nodes on the management channel; monitoring the distinct CCMs to determine a failure condition within a path comprising failure to receive a plurality of the distinct CCMs; responsive to the failure condition, transmitting a CCM with a Remote Defect Indicator (RDI) to the source node, wherein the CCM message with the RDI is generated at a node of the plurality of nodes located on a receive side of a failed primary path; and switching data from the first path to the second path responsive to the CCM with the Remote Defect Indicator, wherein each of the plurality of nodes switches the data to the second path upon reception at each of the plurality of nodes of the CCM with the Remote Defect Indicator; wherein the CCMs are multicast by each of the plurality of nodes, and the one of the ring and linear chain topology are operable to constrain the multicast CCMs to traversing the one of the ring and linear chain without modification of the multicast CCMs. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A self-healing Carrier Ethernet ring, comprising:
-
a plurality of nodes interconnected in a ring topology; a head-end node comprising one of the plurality of nodes; a primary Ethernet path between each of the plurality of nodes and the head-end; a protect Ethernet path between each of the plurality of nodes and the head-end; a management path between each of the plurality of nodes and the head-end, wherein the management path is distinct from the primary and protect paths; means for detecting a failure in the primary and protect path using the management path comprising failure to receive a predetermined number of Continuity Check Messages (CCMs) at a predetermined interval, wherein the predetermined number of consecutive CCMs and the predetermined interval are selected to provide a failure detection in less than a prescribed time required for recovery; wherein each of the plurality of nodes is configured to switch from the primary path to the protect path responsive to detecting the failure; primary Virtual Local Area Networks (VLANs) comprising statically provisioned VLANs between each of the plurality of nodes and the head-end node; and protected VLANs comprising statically provisioned VLANs between each of the plurality of nodes and the head-end node; wherein the primary path comprises the primary VLANs and the protect path comprises the protect VLANs. - View Dependent Claims (12, 13, 14, 15)
-
-
16. A logical tree topology providing a self-healing Ethernet topology, comprising:
-
a plurality of head-end nodes; a plurality of nodes, wherein each node is connected to each of the plurality of head-nodes through a dedicated primary and protect Ethernet path; a management channel based on a Virtual Local Area Network Identifier connected to each of the plurality of head-nodes and nodes, wherein multicast Continuity Check Messages (CCMs) are generated and monitored by the plurality of head-end nodes and the plurality of nodes on the management path for failure denoted by failure to receive a predetermined number of consecutive CCMs at a predetermined interval, wherein the predetermined number of consecutive CCMs and the predetermined interval are selected to provide a failure detection in less than a prescribed time required for recovery, wherein the management path is a distinct path from the primary and protect path; and wherein each of the plurality of nodes is configured to switch from the primary path to the protect path responsive to CCM message with an RDI flag; wherein the logical tree topology is operable to constrain the path of the multicast CCMs by dictating that the multicast CCMs are received at a particular port and broadcast at another particular port at each of the plurality of head-nodes and nodes. - View Dependent Claims (17, 18, 19)
-
Specification