Juniper Networks, Inc.

Western Digital Technologies, Inc.

Roblox Corporation

Ravi I Singh

Raveendra Torvi

Yakov Rekhter

Yimin Shen

Kireeti Kompella

John E Drake

Harish Sitaraman

Abhishek Deshmukh

Amit Shukla

Junan Chen

Adrian John Farrel

Shraddha Hegde

Bernd Lamberts

Remmelt Pit

Zhaohui Zhang

Chandrasekar Ramachandran

Jeffrey R Hobbet

Alia Karin Atlas

Ronald Paul Folkes

Vikas Ganapati Hegde

Minjie Dai

Vishnu Pavan Kumar Beeram

Evan Richardson

Ahmed R Darwish

Navaneetha Krishnan V

Ashwin Sampath

Brian Pane

Lan Wei

David Stahl

A processing application stored on a processing server receives a request to join an application server from a client device. The processing application identifies a targeted application server from a set of application servers, a private internet protocol (IP) address for the targeted application server, and a port number associated with the targeted application server. The processing application generates a token based at least in part on the private IP address for the targeted application server. The processing application maps the private IP address to a virtual IP (VIP) address. The processing application transmits the VIP address, the private IP address, the port number, and the token to the client device.

Online game network demultiplexer with denial-of-service prevention

An approach to exchanging information between data storage devices (DSDs) within a secure data center and an external fleet health manager (FHM) application includes querying one or more DSDs for data to be analyzed, including providing a unique query identifier, whereby a particular DSD responsively provides (i) a device identifier identifying itself, (ii) a random key code for authentication and integrity purposes, (iii) the data to be analyzed, and (iv) the query identifier for the FHM application to verify. The FHM application can then digitally sign a corrective action payload, using the key code from the particular DSD, including the query identifier and the device identifier and a recommended corrective action, and transmit the signed corrective action payload to the data center for application to the particular DSD, whereby the DSD can execute pre-defined fundamental repair action operation(s) corresponding to the corrective action for in-situ repair.

Fleet health management corrective action communication exchange

Techniques are disclosed for service-based tunnel selection for forwarding network traffic. In one example, a network device obtains, based on service parameters associated with a network service, a service-specific tunnel selection scheme. The tunnel selection scheme identifies a primary mapping mode for mapping the network service to a primary transport tunnel and fallback mapping modes for mapping the network service to fallback transport tunnels. The primary mapping mode is categorized according to a first type comprising tunnel colorization, while the fallback mapping modes are categorized according to types other than tunnel colorization. In response to determining that the network service cannot be mapped to the primary transport tunnel according to the primary mapping mode, the network device, maps, based on the fallback mapping modes, the network service to the fallback transport tunnels. The network device forwards network traffic associated with the network service via the fallback transport tunnels.

Service-based tunnel selection scheme for mapping services to tunnels

Techniques are described for managing a plurality of requests for a change in bandwidth for a resource reservation label switched path ('LSP') of a ring network. For example, a method may include receiving, by a network device and from an egress network device of a ring network, a resource reservation request message to establish a multipoint-to-point (MP2P) ring label switched path (LSP). The method may also include modifying, by the network device, the resource reservation request message to specify a request for a change in bandwidth for a segment from the network device to the egress network device of the MP2P ring LSP. The method may also include sending, by the network device and to a downstream network device along the MP2P ring LSP, the modified resource reservation request message.

Bandwidth management for resource reservation label switched path of a ring network

This disclosure is related to devices, systems, and techniques for controlling a flow of network traffic between two or more devices. For example, a network device includes a control unit, a forwarding unit including a forwarding manager including a server configured to store a tunnel hierarchy structure, and a packet processor. The packet processor is configured to receive, via an interface card of a set of interface cards, a packet including a packet header. The forwarding manager is configured to parse the packet header in order to identify a service corresponding to the packet, wherein the service is associated with a service color, identify, based on the tunnel hierarchy structure, a set of tunnels, wherein each tunnel of the set of tunnels is associated with a tunnel color, and determine whether at least one tunnel of a set of tunnels associated with the tunnel color is in an online state.

Mapping services to tunnels in order to forward packets using a network device

Techniques are described for signaling a resource reservation point-to-multipoint (P2MP) label switched path (LSP) in a ring network. For example, the techniques include sending a single resource reservation request message without the ingress needing to send multiple resource reservation request messages, one for each leaf network device of the P2MP ring LSP. The resource reservation request message includes a leaf identification object from which network devices of a P2MP ring LSP may explicitly or implicitly identify themselves as prospective leaf network devices of the P2MP ring LSP. A network device determined to be a leaf network device may send a resource reservation response message back to the ingress network device of the P2MP ring LSP and send a modified resource reservation request message (if explicit) and/or the same resource reservation request message (if implicit) to a next hop network device along the P2MP ring LSP.

Resource reservation techniques for point-to-multipoint tunnels on a ring network

Techniques are described for detecting egress network devices of a point-to-multipoint (P2MP) label switched path (LSP). For example, a network device may include one or more processors configured to identify a P2MP LSP for receiving multicast traffic from a multicast source for a specific multicast group for which the network device has an interested receiver, wherein the network device is to be an egress network device of the P2MP LSP; and send, to an ingress network device of the P2MP LSP, a P2MP egress identification message to add the network device as an egress network device of the P2MP LSP, wherein the one or more processors are further configured to output the P2MP egress identification message into a multipoint-to-point (MP2P) ring LSP for which the ingress network device of the P2MP LSP is a sole egress network device of the MP2P ring LSP.

Detecting egresses of a point-to-multipoint label switched path in a ring network

Techniques are described for varying a bandwidth constraint at one or more hops along a path of a sub-label-switched path (sub-LSP) of a multi-path label-switched path (MP-LSP). The techniques include computing, by an ingress router, a plurality of paths for a plurality of sub-LSPs of a MP-LSP and outputting, by the ingress router, for each path of the plurality of paths, a respective resource reservation request message to establish a respective sub-LSP of the plurality of sub-LSPs, each respective resource reservation request message including an indication of an explicit route, a tunnel identifier indicating the MP-LSP, an identifier for the respective sub-LSP, an indication of a per-hop bandwidth constraint that corresponds to a respective incoming per-hop bandwidth constraint of the plurality of incoming per-hop bandwidth constraints, and one or more instructions to modify the indication of the per-hop bandwidth constraint.

Varying a per-hop-bandwidth constraint in multi-path label switched paths

The disclosed computer-implemented method for verifying the functionality of network paths may include (1) constructing, at a source node within a network, a test packet that uniquely identifies a network path whose functionality is unverified, (2) sending the test packet to a target node within the network via the network path in an attempt to verify the functionality of the network path, (3) receiving, back from the target node, the test packet sent to the target node via the network path, and then (4) verifying, at the source node, the functionality of the network path based at least in part on the test packet received back from the target node. Various other methods, systems, and computer-readable media are also disclosed.

System and method for verifying the functionality of network paths

In some examples, a network device of a network comprises a first component configured to store a plurality of next hop instructions corresponding to respective logical or physical network structures of the network. The network device also comprises a second component configured to send, to the first component, a message that identifies an association of the plurality of next hop instructions, wherein the first component is further configured to modify, in response to receiving the message, each of the plurality of next hop instructions.

Next hop instruction associations for forwarding unit programming within a network device

In general, techniques are described for decapsulating and forwarding VPLS frames in a hybrid PE router space. In one example, a method includes sending a first control plane message that includes first configuration information to a first PE router, the first control plane message comprising a request that the VPLS frames include a control word when forwarded to the first PE router. The first PE router may receive from a second PE router a second L3 control plane message that includes second configuration information for forwarding VPLS frames to the second PE router, the second L3 control plane message not comprising a request to include the control word when forwarded to the second PE router. The method may include configuring a forwarding plane of the first PE router to process VPLS frames that are received from the second PE router without processing the VPLS frames to remove the control word.

Control word decapsulation in a hybrid BGP-VPLS network

In general, techniques are described for a path computation delay timer for multi-protocol label switched networks. As an example, an ingress network device configured to act as an ingress for a label switched path (LSP) may perform the techniques. The ingress network device comprises an interface and a processor. The interface may receive a message indicating an error along the LSP. The processor may delay an operation performed to configure a replacement LSP to be used in place of the LSP in order to provide time during which a cause of the error along the LSP is able to be determined. When the cause of the error is determined to be a failure of a network device supporting operation of the LSP, the processor may further perform the operation to configure the replacement LSP with the ingress network device such that the replacement LSP avoids the failed network device.

Path computation delay timer in multi-protocol label switched networks

Techniques are described for generating a No-Acknowledgement (NACK) message if the installation of a route for a label-switched path at a router has failed or is likely to fail. In some examples, a network device includes at least one processor and at least one module operable by the at least one processor to: receive a request to forward network packets for an LSP; responsive to receiving the request, initiate configuration of at least one forwarding unit of the network device to forward network packets for the LSP; generate a NACK message that indicates the at least one forwarding unit is not configured to forward the network packets for the LSP; and terminate based at least in part on the NACK message, the configuration of the at least one forwarding unit for the LSP.

Readiness detection for data plane configuration of label-switched paths

In one example, a stitching point routing device, which stitches a previous segment of an end-to-end label-switched path (LSP) to a next segment of the end-to-end LSP, includes network interfaces configured to receive packets via the previous segment and send packets via the next segment, and one or more processors configured to determine whether the next segment supports entropy labels, determine whether a packet received from the previous segment is encapsulated by a label stack including an entropy label, when the next segment does not support entropy labels and when the packet is encapsulated by the label stack including the entropy label, remove the entropy label from the label stack, when the next segment supports entropy labels and when the packet is not encapsulated by the label stack including the entropy label, add an entropy label to the label stack, and forward the packet along the next segment.

Growing community of inventors

San Jose, CA, United States of America

Ravi I Singh