Juniper Networks, Inc.

128 Technology, Inc.

Scott A McCulley

Anna Yungelson

Abilash Menon

Jacob Dionne

Robert F Penfield

Jisheng Wang

Kaushik Adesh Agrawal

Prashant Kumar

Jie C Jiang

Greg Schrock

Gorakhanath Kathare

Yogesh B G

Michael Baj

Hadriel S Kaplan

Thomas E Sullivan

Francisco Jose Mendez Cirera

Techniques are described for monitoring application performance in a computer network. For example, a network management system (NMS) includes a memory storing path data received from a plurality of network devices, the path data reported by each network device of the plurality of network devices for one or more logical paths of a physical interface from the given network device over a wide area network (WAN). Additionally, the NMS may include processing circuitry in communication with the memory and configured to: determine, based on the path data, one or more application health assessments for one or more applications, wherein the one or more application health assessments are associated with one or more application time periods for a site, and in response to determining at least one failure state, output a notification including identification of a root cause of the at least one failure state.

Predicting network issues based on historical data

Application service level expectation health and performance

One function of a communications network, or of nodes in such a network, is to gather data that is useful in assessing network performance, and quantifying metrics of node and/or network performance. Various embodiments disclosed herein improve the ability of nodes and networks to gather such data, and quantify metrics of node and/or network performance by selectively marking existing network traffic, and in preferred embodiments without having to dilute network traffic by generating and transmitting dummy data packets.

In-line performance monitoring

Techniques are disclosed for session-based routing of multipoint Open Systems Interconnection (OSI) Model Layer-2 (L2) frames of an L2 network extended over Layer-3 (L3) networks. In one example, L2 networks connect a source device to an ingress router and receiver devices to egress routers. An L3 network connects the ingress and egress routers. The ingress router receives, from the source device, a multipoint L2 frame destined for the receiver devices. The ingress router forms, for each egress router that is connected to at least one multipoint receiver device, a unicast L3 packet for the L2 frame and forwards the unicast L3 packet to the egress router. Each egress router generates, in response to receiving the unicast L3 packet, the multipoint L2 frame and forwards, to the receiver devices, the multipoint L2 frame.

Point-to-multipoint Layer-2 network extension over Layer-3 network

Point-to-multipoint layer-2 network extension over layer-3 network

Routing packets by a router involves establishing a first flow configured for forwarding the packets from a first ingress interface to a first egress interface of the router; determining a condition to modify the first flow; deactivating the first flow; establishing a second flow configured for forwarding the packets from at least one of (1) the first ingress interface to a second egress interface, (2) a second ingress interface to the first egress interface, or (3) a second ingress interface to a second egress interface; and activating the second flow.

Flow modification including shared context

Techniques are disclosed for session-based routing within Open Systems Interconnection (OSI) Model Layer-2 (L2) networks extended over Layer-3 (L3) networks. In one example, L2 networks connect a first client device to a first router and a second client device to a second router. An L3 network connects the first and second routers. The first router receives, from the first client device, an L2 frame destined for the second client device. The first router generates an L3 packet comprising an L3 header specifying L3 addresses of the first and second routers, a first portion of metadata comprising L2 addresses for the first and second client devices, and a second portion of metadata comprising L3 addresses for the first and second client devices, and forwards the L3 packet to the second router. The second router recovers the L2 frame from the metadata and forwards the L2 frame to the second client device.

Layer-2 network extension over layer-3 network using layer-2 metadata

Techniques are disclosed for session-based routing within Open Systems Interconnection (OSI) Model Layer-2 (L2) networks extended over Layer-3 (L3) networks. In one example, L2 networks connect a first client device to a first router and a second client device to a second router. An L3 network connects the first and second routers. The first router receives, from the first client device, an non-session-based L2 frame destined for the second client device. The first router forms an L3 packet comprising an L3 header specifying L3 addresses of the first and second routers and a protocol selected based on an L3 service for the L2 frame, a payload comprising the L2 frame, and metadata comprising a session identifier distinctly identifying the L2 frame, and forwards the L3 packet to the second router. The second router recovers the L2 frame from the payload and forwards the L2 frame to the second client device.

Layer-2 network extension over Layer-3 network using encapsulation

Layer-2 network extension over layer-3 network using encapsulation

A routing method checks a network path selected for transmitting a stream of packets between a first routing node and a second routing node in a computer network. The stream of packets complies with a first transport protocol. The method forwards, from the first routing node toward the second routing node, a set of handshake packets. The set of handshake packets includes change information indicating a change in the transport protocol for a plurality of the packets in the stream. The method modifies the plurality of packets in the stream ('modified packets'). Specifically, the method modifies the first transport protocol header in the plurality of packets in the stream to have a second transport protocol header of a second transport protocol. This modification preferably does not increase the packet size of each of modified packets.

Method and apparatus for managing routing disruptions in a computer network

Embodiments of the present invention provide for continuity of 'stateful' routing sessions in the presence of source network address translation (NAT). Specifically, a stateful routing session may be moved from one routing path to another routing path, e.g., due to a routing change in the communication network, where the routing paths have different source NAT status. For example, the stateful routing session may be moved from a path having no source NAT to a path having source NAT, from a path having source NAT to a path having no source NAT, or from paths having different source network address translations. When a stateful routing session is moved from an existing routing path to a new routing path, the routers detect the routing change based on the change in source NAT status using a special link monitoring protocol. Upon detecting the change in source NAT status, session metadata is included in at least the first packet forwarded following detection of the change in source NAT status so that the stateful routing session can continue without interruption.

Growing community of inventors

Groton, MA, United States of America

Scott A McCulley