Abstract: Techniques disclosed herein include features and methods that extend functionality of provider networks including Provider Backbone Bridges (PBB) networks. Techniques include using a portion of information within Ethernet address encapsulation headers for purposes other than identifying source and destination device addresses. The system limits a number of bits in an address header that should be considered by a provider network node when doing an address lookup in forwarding tables of a provider network node, such as by masking the portion of bits or otherwise disregarding that portion of bits during address lookup. The remaining bits in the address field(s) become free bits that can be used for a variety of application purposes, such as flow path selection. By using information fields that already exist in the Mac-In-Mac (MIM) encapsulation header, such Techniques provide additional information without increasing packet size or requiring new protocols.

Abstract: Techniques herein include systems and methods that extend functionality of transport networks including Transparent Interconnect of Lots of Links (TRILL) networks. Techniques include using a portion of information within transport device address encapsulation headers for purposes other than identifying source and destination device addresses. The system masks a portion of bits in an address header for an address lookup in forwarding tables of a transport network node. The remaining bits in the address field(s) become free bits that can be used for a variety of application purposes, such as flow identifier selection. By using information fields that already exist in encapsulation headers, such techniques provide additional information without increasing packet size or requiring new protocols. Embodiments can combine Equal-cost multi-path routing (ECMP) functionality, Reverse Path Forwarding (RPF) checks, and Time to live (TTL) protection at the same time.

Abstract: Methods and apparatus provide for a network device(s) employing tree tracer processing of a data packet(s) and/or a response(s) in order to discover and graphically represent all the paths within a hierarchical tree of network devices for multicast traffic flows. Specifically, a first network device receives a data packet. The data packet provides a multicast target MAC address. The first network device forwards the data packet to a plurality of network devices, where each of the plurality of the network devices belong to a multicast group identified according to the multicast target MAC address. Based on receipt of the data packet, the first network device generates and transmits a first response to a source of the data packet. The first response indicates a placement of the first network device with respect to a hierarchical tree of the plurality of network devices belonging to the multicast group.

Abstract: Techniques disclosed herein include systems and methods for improving efficiency of multicast state generation within Shortest Path Bridging (SPB) networks. Techniques include using an IS-IS TLV structure with new multicast state computation rules for SPB Networks. SPB Networks use a TLV field for the I-SID Address (and equivalent TLV fields defined in different IETF/IEEE drafts) and node nicknames to signal information that is used to compute a multicast state required to provide L2 Services over a given SPB Network. The I-SID Address TLV is set or filled to carry various items of information. These items of information can include Backbone Media Access Control (B-MAC), Virtual Local Area Network Identifier (VID), I-SID[Transmit, Receive Bit], etc.

Abstract: A method, apparatus and computer program product for distribution of routing information used in a transport network is presented. In a transport network having a plurality of edge devices and core devices, a main instance of a protocol is used for shortest path and tree computation. A multicast tree is defined per Virtual Services Network (VSN) to distribute Link State Data Base (LSDB) updates that only apply to members of said VSN. Multicast trees are built using a secondary instance of the control protocol LSDB and wherein each VSN multicast tree represents a separate instance of the secondary instance of the control protocol LSD. LSDB updates are distributed that only apply to members of the VSN using the multicast tree for the VSN.

Abstract: A method, apparatus and computer program product for using Backbone Virtual Local Area Network (BVLAN) as Virtual Routing and Forwarding (VRF) Identifier and shared Backbone Media Access Control (BMAC) tables to implement a Shortest Path Bridging (SPB) Layer 3 (L3) Virtual Services Network (VSN) is presented. For routed traffic, a Layer 3 (L3) Virtual Services Network (VSN) is associated with a unique Virtual Local Area Network Identifier (VLAN_ID) value in a first Shortest Path Bridging (SPB) network for routed traffic. The routed traffic comprises traffic sent over an SPB network interface, traffic received from an SPB interface, or traffic forwarded from a first SPB Network interface to a second SPB Network interface.

Abstract: A method, apparatus and computer program product for providing synchronization of a multi-chassis cluster using SPB I-SID trees is presented. A plurality of network devices are defined for making up a single cluster. Each network device of the cluster is configured with a same cluster Identifier (cluster ID) and each network device of the cluster signals an Service Instance Identifier (I-SID). At least one ISID multicast tree is generated, each one of the at least one multicast tree rooted at one node of the cluster. Cluster synchronization messages are exchanged between the network devices of the cluster using the at least one multicast tree.

Abstract: A method, apparatus and computer program product for performing multicast Backbone Media Access Channel (BMAC) header transformations is presented. A packet having a header is received at a network node. The header is modified to produce a packet having a modified header by replacing an original value inside the header with a less granular value. The packet having a modified header is forwarded into a transport network.

Abstract: Techniques disclosed herein include systems and methods for extending an IGMP broadcast domain (multicast domain) across a transport network without implementing IGMP snooping within the core of the transport network, yet while providing efficient transport within the core of the transport network. Techniques include dividing a single IGMP interface into multiple IGMP domains or sub-domains. A separate Querier is then elected for each IGMP domain using the single IGMP interface. Edge nodes of the transport network can be configured as the multiple IGMP Queriers, and then re-distribute sender information via a separate routing protocol. Requests can then be sent using the transport network control messaging or routing protocol instead of IGMP snoop messages to advertise multicast data streams in between the multiple IGMP domains (across the transport network). Traffic can then delivered efficiently between isolated access networks of a single Service Layer 2 Network.

Abstract: Techniques disclosed herein include systems and methods for improving multicast traffic operations in a Shortest Path Bridging (SPB) network by conveying bridging domain information of an incoming interface (IIF) when transporting multicast traffic over the SPB network. Techniques disclosed herein include modifying encapsulation packet header information of existing Mac-In-Mac fields to convey additional information that can be interpreted at edge nodes by modifying edge node interpretation of multicast data. Specifically, the value of the I-SID in the BMAC-DA field can be set to be different from the I-SID value in the I-TAG field. Carrying the L2 VSN I-SID value in the I-TAG allows the Egress BEBs to determine which VLAN/L2 VSN/Bridging-Domain of the IIF is in use, and then modify or preserve underlying header information accordingly.

Abstract: A mirroring configuration employs an alternate usage of an existing messaging protocol and mechanism for propagating mirroring control for remote mirroring of data streams. A source routing entity, i.e. a router or switch through which the mirrored stream passes, identifies the stream as available for monitoring. The enabled stream propagates from a source network device, typically from a router port, to a mirroring destination in addition to the addressed destination. A stream identifier emulates an identifier from an alternate usage, such as a multicast group identifier for a multicast protocol, and activates mirroring by inserting the stream identifier in publish and join messages of the multicast protocol.

Abstract: Embodiments herein include systems and methods for providing a mechanism for tunneled data transport within a dual homed access network. A tunnel manager, at a first network connectivity device in a transport network, identifies the transport network configured to interconnect at least two access networks for transporting data traffic between one or more end stations connected to the access networks. The first network connectivity device is coupled to a first access network. The tunnel manager identifies a second network connectivity device. The second network connectivity device is coupled to the first access network to provide the first access network dual homed access to the transport network via the first and second network connectivity devices. The tunnel manager creates a virtual tunnel that connects the first and second network connectivity devices to a third network connectivity device across the transport network.

Abstract: Techniques disclosed herein include systems and methods for extending an IGMP broadcast domain (multicast domain) across a transport network without implementing IGMP snooping within the core of the transport network, yet while providing efficient transport within the core of the transport network. Techniques include dividing a single IGMP interface into multiple IGMP domains or sub-domains. A separate Querier is then elected for each IGMP domain using the single IGMP interface. Edge nodes of the transport network can be configured as the multiple IGMP Queriers, and then re-distribute sender information via a separate routing protocol. Requests can then be sent using the transport network control messaging or routing protocol instead of IGMP snoop messages to advertise multicast data streams in between the multiple IGMP domains (across the transport network). Traffic can then delivered efficiently between isolated access networks of a single Service Layer 2 Network.

Abstract: A network management and monitoring application employs diagnostic messages for confirming network path connectivity and identifying and locating connectivity faults. Diagnostic messages similar to conventional “ping” and “traceroute” messages traverse the network along a prescribed path for which diagnostic feedback is desired. The application receives and analyzes return messages sent from network entities along the path to ascertain connectivity issues on the path. The application receives layer 3 identifiers such as IP addresses, however performs diagnostic operations such as continuity checks based on layer 2 identifiers such as MAC (Media Access Control) identifiers because certain network entities operate on L2 identifiers and would otherwise evade a continuity check based on layer 3 identifiers.

Abstract: Techniques disclosed herein include systems and methods for improving efficiency of multicast state generation within Shortest Path Bridging (SPB) networks. Techniques include using an IS-IS TLV structure with new multicast state computation rules for SPB Networks. SPB Networks use a TLV field for the I-SID Address (and equivalent TLV fields defined in different IETF/IEEE drafts) and node nicknames to signal information that is used to compute a multicast state required to provide L2 Services over a given SPB Network. The I-SID Address TLV is set or filled to carry various items of information. These items of information can include Backbone Media Access Control (B-MAC), Virtual Local Area Network Identifier (VID), I-SID[Transmit, Receive Bit], etc.

Abstract: A method and apparatus for routing multicast data across multiple multicast routing domains connected by a shortest path bridging (SPB) network is presented. A Shortest Path Bridging (SPB) edge router of an SPB network connected to a PIM network is configured as a Rendezvous Point (RP). A message is received at the RP, and in response, the RP forms a first data structure including multicast sender information. The RP floods the SPB network with a second message containing the first data structure, allocates an Identifier (ISID) to the multicast stream, and sends a second data structure with sender information. An edge router with multicast receive interest responds with the second data structure with multicast receive interest information. As a result, a receiver in a second network has knowledge of devices in a first network such that multicast traffic is able to be routed between different networks connected to the SPB network.

Abstract: Techniques disclosed herein include systems and methods for providing a scalable solution to transmit edge IP Multicast sender information in a Shortest Path Bridging (SPB) network. Control information is exchanged between Ingress Backbone Edge Bridges and Egress Backbone Edge Bridges using Multicast Flow Specific and type-length-value (TLV) structures, or other control messages, to announce available multicast streams at ingress nodes within the SPB network. Such exchanges of control messages trigger sending SPB specific Intermediate System To Intermediate System (IS-IS) TLV control message with path computation information via IS-IS control messages. This second set of control messages is exchanged within the SPB network and includes source-specific multicast stream information that is used by Backbone Core Bridges to establish a multicast forward state and compute multicast forwarding paths. Multicast data traffic can then be transmitted through the SPB network using a one-to-many distribution model.

Abstract: A method, apparatus and computer program product for resolving conflicting unicast advertisements in transport network is presented. A particular Backbone Virtual Local Area Network (BVLAN) as a first BVLAN (BVLAN1) on a first network device in a transport network. The first network device receives a first message from a second network device advertising a first Backbone Media Access Channel (BMAC) on a first BVLAN (BMAC1,BVLAN1). The first network device receives a second message from a third network device advertising the (BMAC1,BVLAN1). The (BMAC1,BVLAN1) is assigned to the device of the second network device and the third network device having a lower Identifier (ID) value, wherein the ID value comprises one of the group comprising an Intermediate System to Intermediate System (ISIS) system ID and a Shortest Path Bridging (SPB) bridge ID.

Abstract: Techniques disclosed herein include systems and methods for improving multicast traffic operations in a Shortest Path Bridging (SPB) network by conveying bridging domain information of an incoming interface (IIF) when transporting multicast traffic over the SPB network. Techniques disclosed herein include modifying encapsulation packet header information of existing Mac-In-Mac fields to convey additional information that can be interpreted at edge nodes by modifying edge node interpretation of multicast data. Specifically, the value of the I-SID in the BMAC-DA field can be set to be different from the I-SID value in the I-TAG field. Carrying the L2 VSN I-SID value in the I-TAG allows the Egress BEBs to determine which VLAN/L2 VSN/Bridging-Domain of the IIF is in use, and then modify or preserve underlying header information accordingly.

Abstract: An OAM link trace message is sent from a source node to a target node in a link state protocol controlled Ethernet network. The link trace message uses an 802.1ag format except, as a destination address, it uses either the unicast Ethernet MAC node ID of the target node or the multicast destination address of the service instance. Network topology verification in a link state protocol controlled Ethernet network checks the link state protocol database at a node to ascertain the control plane topology view of at least part of the network. One or more Ethernet OAM commands from the node are executed to ascertain the data plane topology view of the same part of the network. The control plane topology view of the network is compared to the data plane topology view of the network to see if they match. An error is flagged if they do not match.