Abstract: A disaggregated network element of an optical transport network, addressable at a single IP address, includes an active management and control unit (MCU) communicatively coupled to a standby MCU by physical cables and multiple tributary units, each of which performs a function in a data plane that carries user traffic and is communicatively coupled to both MCUs by respective physical cables. The MCUs host respective copies of configuration information for the network element and synchronize the information between them. In response to a loss of communication between the MCUs, a tributary unit designated as a witness tributary unit is consulted to determine the status of the MCUs, after which actions are taken to provide control plane redundancy. In response to a failure of an MCU, a backup copy of the configuration information is stored on the witness tributary unit and subsequently synchronized with a copy stored on the remaining MCU.

Abstract: Disclosed is a method of commissioning a tributary blade in a disaggregated network system, including assigning a port ID to a port of an MCU, mapping to a port map a virtual slot ID to the port ID, receiving a registration request from a tributary blade, and assigning the virtual slot ID to the tributary blade. Disclosed is a method of determining whether a mis-cabling condition exists, including determining the whether a virtual slot ID is mapped to a port ID in a port map. Disclosed is a disaggregated network system including an MCU, a first and second tributary blade coupled to the MCU at a first and second port. The MCU is operable to assign a first and second virtual slot ID to the first and second tributary blades. The MCU is operable to map a first and second virtual slot ID to a first and second port ID.

Abstract: Disclosed is a method of commissioning a tributary blade in a disaggregated network system, including assigning a port ID to a port of an MCU, mapping to a port map a virtual slot ID to the port ID, receiving a registration request from a tributary blade, and assigning the virtual slot ID to the tributary blade. Disclosed is a method of determining whether a mis-cabling condition exists, including determining the whether a virtual slot ID is mapped to a port ID in a port map. Disclosed is a disaggregated network system including an MCU, a first and second tributary blade coupled to the MCU at a first and second port. The MCU is operable to assign a first and second virtual slot ID to the first and second tributary blades. The MCU is operable to map a first and second virtual slot ID to a first and second port ID.

Abstract: A method and system for breaking loops in an Ethernet network that supports connectionless and connection-oriented Ethernet. A loop-breaking protocol may be used to detect a loop among a plurality of network elements and to identify a port to block in order to break the loop. The network elements may stop the flow of connectionless Ethernet traffic, while continuing to allow connection-oriented Ethernet traffic to pass. The loop-breaking protocol may be further configured to analyze and understand connection-oriented Ethernet within the network so that connection-oriented Ethernet paths are accounted for during loop detection and prevention.

Abstract: Methods and systems are provided for managing an Ethernet ring protection switching (ERPS) protocol in an Ethernet network. The method includes receiving an administrative data packet at a first network element; determining whether the administrative data packet contains an ERPS membership setting from a second network element; when the administrative data packet contains the ERPS membership setting from the second network element, comparing an ERPS membership setting at the first network element to the ERPS membership setting from the second network element; and performing an action when the ERPS membership setting at the first network element is different than the ERPS membership setting from the second network element.

Abstract: Methods and systems are provided for migrating loop-breaking protocols in an Ethernet network. The method includes selecting a virtual local area network (VLAN) implementing a multiple spanning tree protocol (MSTP) from a plurality of VLANs operating on the Ethernet network, the MSTP having a spanning tree with a root network element coupled to a first branch of network elements; disabling a virtual network link in the VLAN; migrating a first leaf network element of the first branch in the VLAN by disabling the MSTP and enabling an Ethernet ring protection switching (ERPS) protocol on the first leaf network element; migrating the root network element in the VLAN after the first leaf network element by disabling the MSTP and enabling the ERPS protocol on the root network element; and enabling the virtual network link after migrating the first leaf network element and the root network element.

Abstract: Methods and systems are provided for migrating loop-breaking protocols in an Ethernet network. The method includes selecting a virtual local area network (VLAN) implementing a multiple spanning tree protocol (MSTP) from a plurality of VLANs operating on the Ethernet network, the MSTP having a spanning tree with a root network element coupled to a first branch of network elements; disabling a virtual network link in the VLAN; migrating a first leaf network element of the first branch in the VLAN by disabling the MSTP and enabling an Ethernet ring protection switching (ERPS) protocol on the first leaf network element; migrating the root network element in the VLAN after the first leaf network element by disabling the MSTP and enabling the ERPS protocol on the root network element; and enabling the virtual network link after migrating the first leaf network element and the root network element.

Abstract: Methods and systems are provided for managing an Ethernet ring protection switching (ERPS) protocol in an Ethernet network. The method includes receiving an administrative data packet at a first network element; determining whether the administrative data packet contains an ERPS membership setting from a second network element; when the administrative data packet contains the ERPS membership setting from the second network element, comparing an ERPS membership setting at the first network element to the ERPS membership setting from the second network element; and performing an action when the ERPS membership setting at the first network element is different than the ERPS membership setting from the second network element.

Abstract: Systems and methods for tunneling GCC0 bytes over an OTN transport network are disclosed. The method includes receiving, at a first network element, a first data frame comprising a set of management bytes and a set of data bytes, determining whether the set of management bytes should be tunneled, and, in response to determining that the management bytes should be tunneled, sending, to a second network element, a second data frame comprising the set of management bytes and the set of data bytes.

Abstract: A method and system for breaking loops in an Ethernet network that supports connectionless and connection-oriented Ethernet. A loop-breaking protocol may be used to detect a loop among a plurality of network elements and to identify a port to block in order to break the loop. The network elements may stop the flow of connectionless Ethernet traffic, while continuing to allow connection-oriented Ethernet traffic to pass. The loop-breaking protocol may be further configured to analyze and understand connection-oriented Ethernet within the network so that connection-oriented Ethernet paths are accounted for during loop detection and prevention.

Abstract: Systems and methods for tunneling GCC0 bytes over an OTN transport network are disclosed. The method includes receiving, at a first network element, a first data frame comprising a set of management bytes and a set of data bytes, determining whether the set of management bytes should be tunneled, and, in response to determining that the management bytes should be tunneled, sending, to a second network element, a second data frame comprising the set of management bytes and the set of data bytes.

Abstract: A network element includes an ingress interface, a VSP queue, and a switch fabric (SWF). The ingress interface includes a first virtual subport (VSP) and a second VSP. The first VSP is configured to receive data traffic. The VSP queue is coupled to the second VSP such that data traffic transmitted to the VSP queue is transmitted from the network element via the second VSP. The SWF is configured to receive data traffic from the first VSP, determine whether an intended recipient of the data traffic is associated with the second VSP, and hairpin the data traffic to the VSP queue when the SWF determines that the intended recipient is associated with the second VSP.

Abstract: A network element includes a first customer edge port (CEP) coupled to a customer network, a first and a second flood domain. The first and second flood domain each include one or more provider network ports associated with a provider network. The first CEP is configured to peer spanning tree protocol (STP) data units across a network, and receive and transmit a data unit to a first STP processing instance associated with the first CEP. The first STP processing instance is configured to determine whether the data unit is associated with the first or second flood domain, and forward the data unit to the determined flood domain. The network element includes a second CEP coupled to the customer network and the first flood domain. The second CEP is configured to tunnel STP data units across the provider network, receive and forward a second data unit to the first flood domain.

Abstract: A network element coupled to a communication network is described. The network element includes multiple switching units. The switching units may be configured to independently implement a Spanning Tree Protocol (xSTP) processing in a completely distributed manner including each of the switching units independently calculating an external spanning tree for the network element in the communication network. The network element may act as a single bridge to other network elements in a bridging domain of the communication network.

Abstract: A network element includes a first customer edge port (CEP) coupled to a customer network, a first and a second flood domain. The first and second flood domain each include one or more provider network ports associated with a provider network. The first CEP is configured to peer spanning tree protocol (STP) data units across a network, and receive and transmit a data unit to a first STP processing instance associated with the first CEP. The first STP processing instance is configured to determine whether the data unit is associated with the first or second flood domain, and forward the data unit to the determined flood domain. The network element includes a second CEP coupled to the customer network and the first flood domain. The second CEP is configured to tunnel STP data units across the provider network, receive and forward a second data unit to the first flood domain.

Abstract: A network element coupled to a communication network is described. The network element includes multiple switching units. The switching units may be configured to independently implement a Spanning Tree Protocol (xSTP) processing in a completely distributed manner including each of the switching units independently calculating an external spanning tree for the network element in the communication network. The network element may act as a single bridge to other network elements in a bridging domain of the communication network.

Abstract: A network element includes an ingress interface, a VSP queue, and a switch fabric (SWF). The ingress interface includes a first virtual subport (VSP) and a second VSP. The first VSP is configured to receive data traffic. The VSP queue is coupled to the second VSP such that data traffic transmitted to the VSP queue is transmitted from the network element via the second VSP. The SWF is configured to receive data traffic from the first VSP, determine whether an intended recipient of the data traffic is associated with the second VSP, and hairpin the data traffic to the VSP queue when the SWF determines that the intended recipient is associated with the second VSP.