Ciena Corporation

Piyush Sharma

Waseem Reyaz Khan

Himanshu Shah

Jayant Kumar Bhardwaj

Alwyn Joy George

Atul Vadera

Varun Munjal

Gerard Leo Swinkels

Darek Robert Skalecki

Anurag Prakash

Rajagopalan Kannan

Matthew Yuen

Mukesh Chhabra

Alexander Young

Vineet Gautam

Ritesh Singal

Shalendra Tripathi

Kapil Chopra

Param Preet Singh Dhillon

Anil Dharmshaktu

Sudarshan Sodhani

Risheek Puri

Ramanjit Walia

A node, in a first network, includes circuitry configured to determine a next hop as decided by Border Gateway Protocol (BGP) is an anycast prefix to a Route Reflector (RR) interconnecting the first network with a second network, responsive to the next hop being the anycast prefix to the RR, create a tunnel with a destination based on the anycast prefix, and utilize the tunnel for traffic having the next hop as the anycast prefix to the RR. The anycast prefix is assigned to two or more RRs interconnecting the first network and the second network. A first path is decided by BGP based on a BGP Path Selection Algorithm that is independent of a second path determined by Interior Gateway Protocol (IGP). The first path and the second path can be different, and wherein tunnel is utilized to ensure the traffic always follows the first path.

BGP LU resiliency using an anycast SID and BGP driven anycast path selection

A router is configured to send an advertisement of selective Ethernet Virtual Private Network (VPN) (EVPN) routes based on the Route Types. The router is configured to determine a requirement for a route refresh from a Border Gateway Protocol (BGP) peer for a subset of Route Types of all of the Route Types, send a route refresh message to the BGP peer with an indication of the subset of Route Types, and receive updated routes from the BGP peer only for the subset of Route Types. The indication can be included in a reserved field and payload of the route refresh message. The route refresh message can be defined in RFC 2918.

Advertisement of selective EVPN routes based on route types

Aspects of the subject disclosure may include, for example, a first BGP device establishing a BGP session between the first BGP device and a second BGP device, generating an identifier associated with the second BGP device during establishment of the BGP session, receiving route advertisements from the second BGP device, associating the identifier with the route advertisements, and providing the identifier with the route advertisements to a third BGP device. Other embodiments are disclosed.

Methods, systems, and devices to improve withdrawing border gateway protocol (BGP) routes when a BGP gateway becomes unreachable

A node, in a first network, includes circuitry configured to add a label stack to a packet associated with one of a Layer 2 Virtual Private Network (L2VPN) and a Layer 3 Virtual Private Network (L3VPN), wherein the packet is destined for a second network having at least a pair of Border Gateway Protocol-Label Unicast (BGP-LU) Route Reflector (RR) nodes interconnecting the first network, and wherein the label stack includes an anycast Segment Identifier (SID) for the RR nodes, in Segment Routing, and transmit the packet to the second network. The label stack also includes a BGP-LU label for a destination in the second network. Responsive to isolation of one of the RR nodes, a Point of Local Repair (PLR) node in the first network is configured to implement Topology-Independent Loop-Free Alternate (TI-LFA) for the anycast SID.

Bgp Lu resiliency using an anycast SID and BGP driven anycast path selection

Systems and methods include, in a first Label Edge Router (LER) in a Multiprotocol Label Switching (MPLS) network, creating a primary tunnel with a second LER; creating a Make Before Break (MBB) tunnel with the second LER for the primary tunnel; prior to switching to the MBB tunnel from the primary tunnel, sending an MPLS request to the second LER via the MBB tunnel and receiving an MPLS response from the second LER via the MBB tunnel indicating successfully creation of the MBB tunnel; switching to the MBB tunnel responsive to the successfully creation of the MBB tunnel; and, prior to tearing down the primary tunnel, checking statistics of the MBB tunnel to ensure traffic has moved to the MBB tunnel from the primary tunnel.

Control and data plane synchronization during Make Before Break operations in Multiprotocol Label Switching

A prioritized G.8032 ring switching systems and methods implemented in a node include receiving a defined priority level for each of a plurality of virtual rings at the node, wherein the priority level is one of N levels of priority, N being an integer; and, responsive to a link failure that affects the plurality of virtual rings, performing G.8032 traffic restoration in order based on each of the N levels of priority, wherein each set of the plurality of virtual rings at a same defined priority level are processed concurrently to minimize hardware access. The plurality of virtual rings can be processed concurrently through flushing their Forwarding Databases at a same time for each of the set on a per virtual ring basis. The receiving is via a Ring Automated Protection Switching (R-APS) Protocol Data Unit (PDU) for each virtual ring with the defined priority level included therein.

G.8032 prioritized ring switching systems and methods

A method, implemented in a hybrid network element supporting switching at a plurality of layers, for multilayer resource management between the plurality of layers, includes operating a control plane at Layer N between a plurality of network elements in a network, wherein control plane signaling at the Layer N is processed at each network element in a path for a service in the network; and operating a resource management protocol at Layer N+1 with another network element in the network by injecting and extracting messages from and to the control plane into a data path in the Layer N+1, wherein a service at the Layer N+1 operates over the Layer N, and wherein the resource management protocol messages are processed at an originating network element and a terminating network element and not at intermediate network elements in the path.

Multilayer resource management and arbitration in transport networks

A method for performing an operation at a non-originating node of a connection includes receiving a request for the operation; determining information associated with the connection; and signaling, based on the information and the operation, an originating node to cause the originating node to perform call connection management on the connection. A non-originating node includes a plurality of ports with at least one connection thereon; and a controller communicatively coupled to the plurality of ports and operating a control plane, wherein, for an operation of call connection management on the at least one connection, the controller is configured to: determine information associated with the at least one connection on a link formed by a port; and signal, based on the information and the operation, an originating node of the at least one connection to perform the call connection management on the at least one connection.

Systems and methods for managing call connections from non-originating nodes in networks

A method in a network utilizing a distributed connection-oriented control plane includes signaling a first path for a first connection from a first source node; storing call information for the first connection at any intermediate nodes in the first path; signaling a second path for a second connection from a second source node; checking at any intermediate nodes in the second path if there is absolute route diversity between the first connection and the second connection responsive to a requirement therein; and responsive to detecting a diversity violation at an intermediate node of the any intermediate nodes in the second path, signaling a crankback to the second source node with the call information for the first connection included therein; and recomputing the second path exclusive of the first path based on the call information responsive to receiving the crankback. A network and node are also described.

Systems and methods for diverse connection signaling from disparate source nodes in distributed connection-oriented networks

A method, a network, and a node include computing a path by a source node; sending a message to nodes in the path with associated validation criteria; locally checking the validation criteria at each of the nodes in the path; if the validation criteria is satisfied at the node, forwarding the message to the next node in the path; else there is a validation criteria failure at the node, appending feedback data to the message, converting the message to a validation message, and forwarding the validation message to the next node in the path; and at a destination node, if there are no validation criteria failures, then establishing the connection; else issuing a release message to the source node with all the feedback such that the source node can compute a new path exclusive of nodes where the validation criteria fails.

Growing community of inventors

Gurgaon, India

Piyush Sharma