Juniper Networks, Inc.

Microsoft Technology Licensing, LLC

Pankaj Shukla

Sunesh Rustagi

Wen Lin

John E Drake

Manish P Gupta

Roopa Bayar

Satya Ranjan Mohanty

Manish Satyapal Gupta

Apurva Mehta

Pankaj Garg

Ramasamy Ramanathan

Sanjiv Doshi

Manoj Sharma

Sri Sairam Goli

Shrinivasa Kini

Deepak Ojha

Vikram Bobade

Kishore Gummadidala

Ramakanth Gunuganti

A cloud service provider's enterprise edge device and network interface are configured to establish a single tunnel connection with a remote server for delivering data packets to multiple distinct virtual machines on the remote server. The provider's enterprise edge device stores the network address information for each virtual machine and remote server to attach the destination network addresses to the data packet for transmission to the appropriate virtual machine on the remote server. Utilizing a single tunnel to transmit data packets to multiple virtual machines increases scalability at the provider's enterprise edge device and reduces system resources compared to other implementations in which the provider uses a tunnel for each virtual machine on a remote server.

Flexible unnumbered destination tunnels for virtual networks

Data traffic loss in a an Ethernet Ring that is multihomed, in an active-standby manner, to a VPLS transport network (such as a Border Gateway Protocol (BGP) multihomed Ethernet Ring, an MC-LAG multihomed Ethernet Ring, or some other type of active-standby multihomed Ethernet Ring, etc.) (ring) is avoided. The exemplary multihomed ring running Ethernet Ring Protection (ERP) protocol includes a Ring Protection Link (RPL), a first node and a second node linked with a designated border router and a standby border router of the network, respectively. The data traffic loss in the multihomed ring is avoided by (i) receiving an indication that the link between the first node and the designated border router has failed; and (ii) invoking, responsive to the received indication, an ERP Media Access Control (MAC)-flush in the ring, even in the absence of a failed link in the ring and without activating the specified RPL. The ERP MAC-flush causes subsequent data packets from each of the plurality of nodes in the ring to be forwarded to the standby border router via the second node.

Avoiding data traffic loss in a ring multihomed, in an active-standby manner, to a transport network

An example network system includes a layer two (L2) device and a layer three (L3) device. The L2 device includes a control unit is configured to determine a preferred network path from a first L2 network in which the L2 device resides to an intermediate L3 network in which the L3 device resides that couples the first L2 network to a second L2 network having a second L2 device. The control unit includes a management endpoint (MEP) module. The MEP module executes an operations, administration, and management (OAM) protocol to monitor the first L2 network and output an L2 frame in accordance with the OAM protocol to the L3 device to notify the L3 device that it is within the preferred network path. A MEP module of the L3 device executes an OAM protocol that outputs L2 frames to the L2 device indicating the status of the L3 network.

Communicating network path and status information in multi-homed networks

In general, techniques are described for configuring a provider edge (PE) network device of an Ethernet virtual private network (EVPN) to use a common traffic engineering label (e.g., MPLS label) for different EVPN route types associated with the same EVPN. In some examples, the techniques include sending a first layer three (L3) control plane message that indicates a label-switched network protocol label that corresponds to a first EVPN route type, wherein the first L3 control plane message indicates that a first PE network device is reachable in the L2 segment. The techniques may include performing L2 address learning to determine at least one L2 address associated with the layer two segment of the EVPN. The techniques may include sending a second L3 control plane message that indicates the same label included in the first L3 control plane message corresponds to a second EVPN route type.

MPLS label usage in ethernet virtual private networks

MPLS label usage in Ethernet virtual private networks

Avoiding data traffic loss in an ethernet ring multihomed, in an active-standby manner, to a virtual private LAN service transport network

In general, techniques are described for providing control plane messaging in an active-active (or all-active) configuration of a multi-homed EVPN environment. In some examples, the techniques include receiving a control plane message comprising at least one address that identifies that second PE network device. The techniques may include configuring, based at least in part on the control plane message, a forwarding plane of a first PE network device to identify network packets having respective destination addresses that match the at least one address. The techniques may include determining that at least one address of the network packet matches the at least one address that identifies the second PE network device. The techniques may include, responsive to the determination, skipping a decrement of the Time-To-Live (TTL) value of the network packet, and forwarding the network packet to the second PE network device.

Control plane messaging in all-active multi-homed ethernet virtual private networks

In general, techniques are described for synchronizing gateway layer two (L2) addresses of routers that cooperate to provide interconnectivity to multiple, separate L2 networks. In one example, a router includes a VPLS module that establishes a VPLS instance to provide L2 connectivity between a local L2 network for the router and a remote L2 network for the router, wherein the router is addressable by a gateway L2 address. A synchronization module receives a gateway L2 address synchronization message that includes an additional gateway L2 address for an additional router. An integrated routing and bridging (IRB) interface of the router receives a L2 PDU from the local L2 network on an attachment circuit for the VPLS instance attached to the interface card, and a forwarding unit routes a layer three (L3) packet carried by the PDU when the PDU has an L2 destination address that matches the additional gateway L2 address.

Synchronizing VPLS gateway MAC addresses

A first network device receives a control message at an interface from a second network device, wherein the first network device and the second network device use a multipoint service that provides layer two (L2) connectivity between L2 networks. The control message specifies one or more L2 addresses of customer network devices that are provided connectivity to an autonomous system by the second network device, wherein the control message identifies the L2 addresses as static L2 addresses that are to be persistently maintained at the first network device as reachable by the interface. In response to receiving the control message and by the first network device, the first network device stores the L2 addresses as persistently maintained static L2 addresses being reachable by the interface at which the control message was received.

Static MAC address propagation in multipoint network services

Techniques are described for supporting metro Ethernet 'E-TREE' service over a packet-switched MPLS network, including a VPLS core, in a manner that allows a service provide to easily integrate with different types of technologies deployed by its various customers. Moreover, the techniques described herein provide increased flexibility with respect to the topology of the roots and leafs of the E-TREE service and, in particular, allow roots and leaf nodes to be coupled to a common router that provides access to the VPLS core. An NNI port of a PE router may process network traffic to provide E-TREE service to a bridged network having both leaf nodes and root nodes process and direct traffic between logical interfaces as changed next hops.

E-tree service having extended shared VLAN learning across VPLS network

An example method includes monitoring a layer two network with a first network device that operates within the network. The method also includes discovering a second network device that operates within the network by receiving an extended continuity check message (CCM) transmitted from the second network device. The extended CCM transmitted from the second network device indicates to other network devices that a service instance is available on the second network device, and includes an indication of one or more network devices from which the second network device has received CCMs for the service instance. The method further includes determining that bidirectional connectivity exists between the first network device and the second network device when the indication includes the first network device as one of the network devices from which the second network device has received CCMs for the service instance.

Enhanced service status detection and fault isolation within layer two networks

In general, techniques are described for preparing a computer network for planned events. A network device comprising a control unit and an interface implements these techniques. The control unit is configured to be a member a maintenance association that verifies connectivity a single service instance. The interface outputs a maintenance message to an additional network device to verify connectivity between the network device and the additional network device. The control unit receives an indication to initiate a planned event capable of disrupting the maintenance association. Prior to the control unit performing the planned event, the interface generates a modified maintenance message indicating that the planned event will be performed by the network device. The interface then transmits the modified outgoing maintenance message to the additional network device to direct the additional network device to avoid detecting the planned event as a connectivity fault.

Preparing for planned events in computer networks

In general, techniques are described for simultaneously testing connectivity to same or different remote maintenance endpoints of the same maintenance association. Specifically, a network device may include a control unit that simultaneously executes both a first and a second maintenance session. The control unit maintains first and second session identifiers that uniquely identifies the first and second maintenance sessions. The control unit receives via the first maintenance session input that specifies parameters for a maintenance message and generates the maintenance message in accordance with the parameters such that the maintenance message includes the first session identifier. The network device also includes an interface card that forwards the maintenance message to another network device in order to determine connectivity between these two network devices. By generating the maintenance message to include the first session identifier, the control unit may upon receiving a response to the maintenance message resolve to which of the maintenance session the response corresponds.

Growing community of inventors

San Jose, CA, United States of America

Pankaj Shukla