Abstract: A packet is generated at a first network connected device for transmission to a destination network device through a network comprising a plurality of pods. At least two of the plurality of pods are within separate management domains, and generating the packet comprises generating the packet with a first identifier and a second identifier. The first identifier indicates a pod of the plurality of pods in which the destination network connected device is located, and the second identifier indicates an identity of the destination network connected device within the pod of the plurality of pods. The packet is transmitted from the first network connected device to the destination network connected device.

Abstract: An example network device includes a network interface and a control unit that receives a packet having header information. The control unit includes a forwarding structure having a plurality of entries that each refers to one of a plurality of logical interfaces, a forwarding engine configured to access the forwarding structure to select a first logical interface to which to forward the packet based on the header information, wherein the first logical interface comprises a pseudo-device interface (PDI). The control unit also includes a PDI module that tunnels the packet to an external service complex (ESC) by at least applying a set of metadata to the packet, encapsulating the packet with a header, and forwarding the packet to the ESC via the network interface, and wherein the metadata allows the ESC to determine a set of services to be applied to the packet based on the metadata.

Abstract: A packet is generated at a first network connected device for transmission to a destination network device through a network comprising a plurality of pods. At least two of the plurality of pods are within separate management domains, and generating the packet comprises generating the packet with a first identifier and a second identifier. The first identifier indicates a pod of the plurality of pods in which the destination network connected device is located, and the second identifier indicates an identity of the destination network connected device within the pod of the plurality of pods. The packet is transmitted from the first network connected device to the destination network connected device.

Abstract: A packet is generated at a first network connected device for transmission to a destination network device through a network comprising a plurality of pods. At least two of the plurality of pods are within separate management domains, and generating the packet comprises generating the packet with a first identifier and a second identifier. The first identifier indicates a pod of the plurality of pods in which the destination network connected device is located, and the second identifier indicates an identity of the destination network connected device within the pod of the plurality of pods. The packet is transmitted from the first network connected device to the destination network connected device.

Abstract: A packet is generated at a first network connected device for transmission to a destination network device through a network comprising a plurality of pods. At least two of the plurality of pods are within separate management domains, and generating the packet comprises generating the packet with a first identifier and a second identifier. The first identifier indicates a pod of the plurality of pods in which the destination network connected device is located, and the second identifier indicates an identity of the destination network connected device within the pod of the plurality of pods. The packet is transmitted from the first network connected device to the destination network connected device.

Abstract: A network device may receive network traffic from a first device. The network device may identify, based on the network traffic and a service level agreement, stored by the network device, that a service is to be applied to the network traffic. The network device may send the network traffic to a second device, the second device using a service plane to apply the service to the network traffic. The network device may receive the network traffic from the second device, the network traffic having the service applied by the second device; and send the network traffic, having the service applied by the second device, to a third device.

Abstract: An example network device includes a network interface and a control unit that receives a packet having header information. The control unit includes a forwarding structure having a plurality of entries that each refers to one of a plurality of logical interfaces, a forwarding engine configured to access the forwarding structure to select a first logical interface to which to forward the packet based on the header information, wherein the first logical interface comprises a pseudo-device interface (PDI). The control unit also includes a PDI module that tunnels the packet to an external service complex (ESC) by at least applying a set of metadata to the packet, encapsulating the packet with a header, and forwarding the packet to the ESC via the network interface, and wherein the metadata allows the ESC to determine a set of services to be applied to the packet based on the metadata.

Abstract: A network device may receive network traffic from a first device. The network device may identify, based on the network traffic and a service level agreement, stored by the network device, that a service is to be applied to the network traffic. The network device may send the network traffic to a second device, the second device using a service plane to apply the service to the network traffic. The network device may receive the network traffic from the second device, the network traffic having the service applied by the second device; and send the network traffic, having the service applied by the second device, to a third device.

Abstract: A network device may receive network traffic from a first device. The network device may identify, based on the network traffic and a service level agreement, stored by the network device, that a service is to be applied to the network traffic. The network device may send the network traffic to a second device, the second device using a service plane to apply the service to the network traffic. The network device may receive the network traffic from the second device, the network traffic having the service applied by the second device; and send the network traffic, having the service applied by the second device, to a third device.

Abstract: By using an extended bitmap window and arrival sequence numbers, a multiprocessor system may perform anti-replay checks on incoming packets in a similar order as a single processor system. In one implementation, a device may provide an anti-replay check window that includes an original window and an extension window, the original window being contiguous to the extension window. In addition, the device may receive a packet with an anti-replay sequence number and receive another packet whose anti-replay sequence number is within a range of the original window. In addition, the device may determine if the packet has arrived before the other packet by less than a threshold if the anti-replay sequence number of the packet falls within a range of the extension window. Further, the device may retain the packet if the packet has arrived before the other packet by less than the threshold.

Abstract: An example network device includes a network interface and a control unit that receives a packet having header information. The control unit includes a forwarding structure having a plurality of entries that each refers to one of a plurality of logical interfaces, a forwarding engine configured to access the forwarding structure to select a first logical interface to which to forward the packet based on the header information, wherein the first logical interface comprises a pseudo-device interface (PDI). The control unit also includes a PDI module that tunnels the packet to an external service complex (ESC) by at least applying a set of metadata to the packet, encapsulating the packet with a header, and forwarding the packet to the ESC via the network interface, and wherein the metadata allows the ESC to determine a set of services to be applied to the packet based on the metadata.