Nortel Networks Corporation

Rpx Clearinghouse LLC

Rockstar Consortium US LP

Rockstar Bidco, LP

Extreme Networks, Inc.

Constellation Technologies, LLC

Other

Avaya Inc.

Paul Unbehagen

Nigel Lawrence Bragg

David Allan

Dinesh Mohan

Roger Lapuh

Srikanth Keesara

Karthik S Gopalakrishnan

Greg J Landry

Zenon Kuc

John Mead

Vasile Radoaca

Praveen Muley

Peter J Ashwood-Smith

Peter Ashwood Smith

Mohnish Anumala

Malcolm Betts

Bruno Germain

Shobhan Lakkapragada

Guoli Yin

Gerald Smallegange

Yin Guoli

Paul Knight

Embodiments generally relate to enabling configuration in networks. In one embodiment, a method includes receiving a message from an edge configuration device, wherein the message contains shortest path bridging (SPB) configuration information. The method also includes performing an intermediate system-to-intermediate system (IS-IS) configuration in response to receiving the message.

Enabling configuration in networks

Embodiments generally relate to enabling encapsulation in networks. In one embodiment, a method includes receiving a message from an edge configuration device, wherein the message contains shortest path bridging (SPB) configuration information. The method also includes performing provider backbone bridge (MAC-in-MAC) encapsulation in response to receiving the message.

Performing MAC-in-MAC encapsulation using shortest path bridging configuration information

Nodes on an Ethernet network run a link state protocol on the control plane and install shortest path forwarding state into their FIBs to allow packets to follow shortest paths through the network without requiring MAC header replacement at each hop through the network. When a node learns an IP address, it will insert the IP address into its link state advertisement to advertise reachability of the IP address to the other nodes on the network. Each node will add this IP address to its link state database. If a packet arrives at an ingress node, the ingress node will read the IP address, determine which node on the link state protocol controlled Ethernet network is aware of the IP address, and construct a MAC header to forward the packet to the correct node. The DA/VID of the MAC header is the nodal MAC of the node that advertised the IP address. Unicast and multicast IP forwarding may be implemented.

IP forwarding across a link state protocol controlled ethernet network

Embodiments generally relate to message transmission in networks. In one embodiment, a method includes enabling a user to provide shortest path bridging (SPB) configuration information. The method also includes receiving the SPB configuration information from the user. The method also includes sending the SPB configuration information to an edge server device.

Message transmission in networks

The present invention facilitates automatic discovery of VPN-related information, which relates to the existence or association of VPNs as supported by provider edge devices in a core network. In particular, the Border Gateway Protocol (BGP) is used to facilitate the automatic discovery, and the provider edge devices are capable of subsequently and automatically triggering Label Distribution Protocol (LDP) processes to facilitate signaling over LDP sessions within the core network.

Autodiscovery for virtual networks

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.

Continuity check management in a link state controlled ethernet network

Techniques for routing data between network area are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for routing data between layer 2 network areas of backbone bridges comprising the steps of receiving data at a network element containing an internally terminated Network to Network Interface (NNI) for a plurality of network areas, identifying a destination address associated with the data, determining a network area of the plurality of network areas associated with the data, and performing one or more data flow treatments associated with the data using the internally terminated Network to Network Interface (NNI).

Techniques for routing data between network areas

Nodes on a link state protocol controlled Ethernet network implement a link state routing protocol such as IS-IS. Nodes assign an IP address or I-SID value per VRF and then advertise the IP addresses or I-SID values in IS-IS LSAs. When a packet is to be forwarded on the VPN, the ingress node identifies the VRF for the packet and performs an IP lookup in customer address space in the VRF to determine the next hop and the IP address or I-SID value of the VRF on the egress node. The ingress node prepends an I-SID or IP header to identify the VRFs and then creates a MAC header to allow the packet to be forwarded to the egress node on the link state protocol controlled Ethernet network. When the packet is received at the egress node, the MAC header is stripped from the packet and the appended I-SID or IP header is used to identify the egress VRF. A customer address space IP lookup is then performed in the identified VRF on the egress node using the information in the client IP header to determine how to forward the packet. Customer reachability information within a VPN may be exchanged between VRFs using iBGP, or directly by using link state protocol LSAs tagged with the relevant I-SID.

Implementation of VPNs over a link state protocol controlled Ethernet network

Ethernet OAM MEPs are automatically configured in a link state protocol controlled Ethernet network. A node operating in the link state protocol controlled Ethernet network receives a Link State PDU (LSP) containing a TLV having a MEP associated with the Ethernet MAC node ID of a second node in the link state protocol controlled Ethernet network, where the path between the first and second node includes a plurality of links. The node updates a forwarding table to indicate an association between the MEP ID and a Ethernet MAC node ID of the second node. An Ethernet OAM maintenance endpoint is produced in a link state protocol controlled Ethernet network by hashing a Sys-ID to produce a MEP; storing the MEP in a TLV; and forwarding the TLV over the link state protocol controlled Ethernet network in an LSP.

Automatic MEP provisioning in a link state controlled ethernet network

Multicast capabilities of a link state protocol controlled network are used to accelerate the flooding advertisement of topology change notifications within portions of the network. This flooding mechanism may be particularly efficient in a network with a large number of two-connected nodes such as a ring network architecture. A control plane specific multicast group address is used when flooding topology change notifications, and a process such as reverse path forwarding check is used as an additional control on forwarding of the notification to prevent looping of control plane packets. Two-connected nodes insert a forwarding entry into their FIB to enable frames containing the control message to be forwarded via the data plane on to the downstream node so that propagation of the control message along a chain of two-connected nodes may occur at data plane speeds.

Failure notification in a network having serially connected nodes

Routes may be installed across multiple link state protocol controlled Ethernet network areas by causing ABBs to leak I-SID information advertised by BEBs in a L1 network area into an L2 network area. ABBs will only leak I-SIDs for BEBs where it is the closest ABB for that BEB. Where another ABB on the L2 network also leaks the same I-SID into the L2 network area from another L1 network area, the I-SID is of multi-area interest. ABBs will advertise I-SIDs that are common to the L1 and L2 networks back into their respective L1 network. Within each L1 and L2 network area, forwarding state will be installed between network elements advertising common interest in an ISID, so that multi-area paths may be created to span the L1/L2/L1 network areas. The L1/L2/L1 network structure may recurse an arbitrary number of times.

Method and apparatus for exchanging routing information and the establishment of connectivity across multiple network areas

MPLS networks offering PW or VPLS services may be interconnected with Ethernet networks implemented according to 802.1or 802.1Qay. The MPLS network may be a core and offer services to the Ethernet access networks, or vise-versa. Additionally, a mixture of different types of access networks may be interconnected by an MPLS core or an Ethernet core. Both network interworking and service interworking are provided. OAM fault detection may be implemented via maintenance entities extending across the network or end to end depending on the combination of networks and services offered by the networks.

Method and apparatus for interworking ethernet and MPLS networks

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 using 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. A method of 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. It then executes one or more Ethernet OAM commands from the node 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.

Continuity check management in a link state controlled Ethernet network

Routes may be installed across multiple link state protocol controlled Ethernet network areas by causing ABBs to leak I-SID information advertised by BEBs a L1 network area into an L2 network area. ABBs will only leak I-SIDs for BEBs where it is the closest ABB for that BEB. Where another ABB on the L2 network also leaks the same I-SID into the L2 network area from another L1 network area, the I-SID is of multi-area interest. ABBs will advertise I-SIDs that are common to the L1 and L2 networks back into their respective L1 network. Within each L1 and L2 network area, forwarding state will be installed between network elements advertising common interest in an ISID, so that multi-area paths may be created to span the L1/L2/L1 network areas. ABBs may summarize BEB multicast trees such that the set of trees for a given I-SID transiting the ABB is condensed into a common tree. The L2 network may further be implemented as a second layer implemented using a L1/L2/L1 network structure, so that the L1/L2/L1 network structure may recurse an arbitrary number of times.

Growing community of inventors

Apex, NC, United States of America

Paul Unbehagen