Abstract: Examples described herein relate to a packet processing device that includes a programmable packet processing pipeline that is configured using a virtual switch. In some examples, the programmable packet processing pipeline is to receive configurations from multiple control planes via the virtual switch to configure packet processing actions. In some examples, the virtual switch is to provide inter-virtual execution environment communications. In some examples, the programmable packet processing pipeline is configured using a programming language.

Abstract: Examples described herein relate to a Transport Layer Security (TLS) offload engine to: based on detection of encrypted data unassociated with a previously detected data header: search for one or more data headers; identify at least two candidate data headers for validation; and based on receipt of an indication that the at least two candidate data headers are valid, perform decryption of received data in one or more packets. In some examples, the TLS offload engine is to: based on receipt of an indication that one or more of the at least two candidate data headers is not a valid header, search for two or more other candidate data headers.

Abstract: Methods and apparatus for extending OpenvSwitch (OVS) megaflow offloads to hardware to address hardware pipeline limitations. Under a method implemented on a compute platform including a Network Interface Controller (NIC) having one or more ports and running software including OVS software and a Linux operating system having a kernel including a TC-flower module and a NIC driver a new megaflow is created with a mask in the OVS software employing a subset of microflow fields for a packet. The microflow fields and the megaflow mask is sent to the NIC driver. A new megaflow is implemented in the NIC driver employing a subset of the microflow fields and the NIC driver creates a new hardware flow on the NIC employing a packet match scheme using all the microflow fields. The NIC also programs a NIC hardware pipeline with the new hardware flow using a match scheme that may depend on the available hardware resources, such as the size of a TCAM.

Abstract: According to one embodiment, a method for allocating Internet Protocol (IP) addresses includes receiving, while serving as an active inter-chassis redundancy (ICR) device, a plurality of IP address requests from the third network device for the plurality of client devices. The method further includes responsive to determining a second network device is also serving as the active ICR device, allocating to a client device an IP address selected from a first portion of the commonly shared plurality of IP addresses and not a second portion, wherein the first portion is allocatable only by the first network device while the first network device and the second network device are both serving as active ICR network devices in the ICR system, and wherein the second portion is allocatable only by the second network device while the first and second network devices are both serving as active ICR devices.

Abstract: According to one embodiment, a method for performing reconciliation sync includes a first network device configured as an active inter-chassis redundancy (ICR) device in response to detecting a switchover request while performing a bulk sync transitioning to serving as the standby ICR device and performing a reconciliation sync while serving as the standby ICR device, the reconciliation sync comprises starting a transmission of session records that failed to be transmitted during the bulk sync to the second network device. According to one embodiment, a method for performing reconciliation sync includes a first network device configured as a standby ICR device receiving a plurality of session records from a second network device of the ICR system. The method further includes updating a global version number based on record version numbers of the received plurality of session records, and maintaining local session records based on the received plurality of session records.

Abstract: According to one embodiment, a method for performing reconciliation sync includes a first network device configured as an active inter-chassis redundancy (ICR) device in response to detecting a switchover request while performing a bulk sync transitioning to serving as the standby ICR device and performing a reconciliation sync while serving as the standby ICR device, the reconciliation sync comprises starting a transmission of session records that failed to be transmitted during the bulk sync to the second network device. According to one embodiment, a method for performing reconciliation sync includes a first network device configured as a standby ICR device receiving a plurality of session records from a second network device of the ICR system. The method further includes updating a global version number based on record version numbers of the received plurality of session records, and maintaining local session records based on the received plurality of session records.

Abstract: According to one embodiment, a method for allocating Internet Protocol (IP) addresses includes receiving, while serving as an active inter-chassis redundancy (ICR) device, a plurality of IP address requests from the third network device for the plurality of client devices. The method further includes responsive to determining a second network device is also serving as the active ICR device, allocating to a client device an IP address selected from a first portion of the commonly shared plurality of IP addresses and not a second portion, wherein the first portion is allocatable only by the first network device while the first network device and the second network device are both serving as active ICR network devices in the ICR system, and wherein the second portion is allocatable only by the second network device while the first and second network devices are both serving as active ICR devices.