Hewlett Packard Enterprise Development LP

Vijeesh Erankotte Panayamthatta

Venkatavaradhan Devarajan

Celestian K Sebastian

Anoop Govindan Nair

Saurabh Mohan

Prasanth Gopinathan Nair Saraswathyamma

A first ingress interface on a switch receives a first control packet for establishing a Transmission Control Protocol (TCP) session and selects a first engine running on a first line card in the switch. A second ingress interface receives a second control packet and selects the same first engine. Data associated with the TCP session received by the first or second ingress interface subsequent to establishing the TCP session is to be forwarded to the first engine. The first ingress interface receives a third control packet and sends, to the selected first engine, a notification indicating the TCP session which is to be tracked. The first or second ingress interface receives a fourth packet with a payload associated with the TCP session and forwards, to the selected first engine, a copy of the fourth packet, thereby facilitating a plurality of engine instances to support application identification.

Asymmetric application identification detection on switches

Examples disclosed herein relate to a method comprising receiving, at a first label manager of a first network device, a first request to allocate a first label for a first route prefix for a first protocol, wherein the first network device and a second network device are part of a virtualized network device. The method includes receiving, at a second label manager of the second network device, a second request to determine the first label for the first route prefix for the first protocol, wherein the second request originates from the first label manager and determining, at the second label manager, the first label for the first route prefix for the first protocol. The method includes transmitting, the first label to the first label manager and transmitting, by the first label manager, the first label to a label management protocol corresponding to the first protocol, in response to the first request.

Using labels in a virtualized device environment

This disclosure is directed to a method, system, and device for disabling links within a computer network based on a loop link priority parameter. The method includes detecting a loop in a network in a network communication device having multiple interfaces associated with different priorities. The device may transmit a first network packet as a loop check packet outbound from the network communication device via a first interface port. The device may then receive a second network packet (which may be the first outbound packet returning inappropriately to the device) as an inbound network communication via a second interface port. If the device identifies return of a sent loop check packet, it may disable one of the first interface port or the second interface port based on a comparison of loop link priority parameters to remove the loop in the network.

Link priority for loop-protect

In some examples, a software-defined network (SDN) controller determines a link aggregation (LAG) configuration for a node in the SDN that is controlled by the SDN controller. The LAG configuration is based on hardware capability information and dynamic network traffic information of the SDN. The SDN controller can further instruct the node to forward traffic in accordance with the LAG configuration.

Growing community of inventors

Bengaluru, India

Vijeesh Erankotte Panayamthatta