Abstract:
A network device may receive IPv6 fragments of a flow. Source and/or destination port information may be encoded into an upper sixteen bits of an identification number of an IPv6 fragment header of each of the IPv6 fragments. The network device may extract the source and/or destination port information from the IPv6 fragments, and may perform a spoof check of the IPv6 fragments. The network device may drop any of the IPv6 fragments that fail the spoof check, to generate remaining IPv6 fragments, and may translate the remaining IPv6 fragments into IPv4 fragments based on the source and/or destination port information. The network device may forward the IPv4 fragments toward an IPv4 cloud network.
Abstract:
A device receives network information associated with a network and server information associated with one or more server devices, wherein the network is associated with a network device and the one or more server devices. The device generates, based on the network information and the server information, an encapsulation profile for a tunnel encapsulation path and a route profile for the tunnel encapsulation path. The device provides, to the network device, the encapsulation profile for the tunnel encapsulation path and the route profile for the tunnel encapsulation path, and provides, to the one or more server devices, the encapsulation profile for the tunnel encapsulation path. The tunnel encapsulation path is provided between the network device and the one or more server devices, via the network, based on the encapsulation profile for the tunnel encapsulation path and the route profile for the tunnel encapsulation path.
Abstract:
A network device that includes a plurality of packet processing components may receive traffic associated with one or more services. The network device may store state information for each of the plurality of packet processing components, while the plurality of packet processing components are receiving the traffic. The state information may include state configuration information and/or internal storage information. The state information may be stored using a data structure that is internal to the network device and external to the packet processing component. The network device may detect an error that prevents the packet processing component from processing at least a portion of the traffic. The network device may execute, based on detecting the error that prevents the packet processing component from processing at least the portion of the traffic, a recovery procedure that uses the state information to reset the packet processing component to an operational state.
Abstract:
A network device receives multicast packets that include information identifying destinations in the network, identifies next hops associated with the destinations, and populates a cache with the destinations and addresses of the identified next hops. The network device receives a particular multicast packet that includes information identifying particular destinations included in the cache, identifies one or more next hops for the particular destinations from the cache, and forwards the particular multicast packet to the identified one or more next hops to permit the identified one or more next hops to forward the multicast packet toward the particular destinations.
Abstract:
A network device may receive IPv6 fragments of a flow. Source and/or destination port information may be encoded into an upper sixteen bits of an identification number of an IPv6 fragment header of each of the IPv6 fragments. The network device may extract the source and/or destination port information from the IPv6 fragments, and may perform a spoof check of the IPv6 fragments. The network device may drop any of the IPv6 fragments that fail the spoof check, to generate remaining IPv6 fragments, and may translate the remaining IPv6 fragments into IPv4 fragments based on the source and/or destination port information. The network device may forward the IPv4 fragments toward an IPv4 cloud network.
Abstract:
A network device that includes a plurality of packet processing components may receive traffic associated with one or more services. The network device may store state information for each of the plurality of packet processing components, while the plurality of packet processing components are receiving the traffic. The state information may include state configuration information and/or internal storage information. The state information may be stored using a data structure that is internal to the network device and external to the packet processing component. The network device may detect an error that prevents the packet processing component from processing at least a portion of the traffic. The network device may execute, based on detecting the error that prevents the packet processing component from processing at least the portion of the traffic, a recovery procedure that uses the state information to reset the packet processing component to an operational state.
Abstract:
A network device receives a packet with a multicast nexthop identifier, and creates a mask that includes addresses of egress packet forwarding engines, of the network device, to which to provide the packet. The network device divides the mask into two portions, generates two copies of the packet, provides a first portion of the mask in a first copy of the packet, and provides a second portion of the mask in a second copy of the packet. The network device also forwards the first copy of the packet to an address of a first egress packet forwarding engine provided in the first portion of the mask, and forwards the second copy of the packet to an address of a second egress packet forwarding engine provided in the second portion of the mask.