A virtual switch for packet switching includes an ingress traffic steering manager executing on circuitry and coupled to receive packets from multiple virtual machines or containers, multiple data plane providers, each data plane provider having a data path coupled to selectively receive the packets from the ingress traffic steering manager, and wherein the ingress traffic steering manager classifies the received packets and selects available data paths based on the classification of the packets and a set of distribution rules.

A path computation element (PCE) central controller (PCECC) comprising a memory comprising executable instructions and a processor coupled to the memory and configured to execute the instructions. Executing the instructions causes the processor to receive a request to compute a path through a network, the request comprising a plurality of computational tasks, divide the computational tasks into a plurality of groups of computational tasks, transmit at least some of the plurality of groups of computational tasks to a plurality of path computation clients (PCCs) for computation by the PCCs, and receive, from the PCCs, computation results corresponding to the plurality of groups of computational tasks.

The disclosure relates to technology for supporting a virtual switch to change data plane providers on a framework supporting multiple data plane providers. A processing device receives a request to change a first data plane provider, where the virtual switch is configured with a topology on the first data plane provider to use a flow management protocol. The virtual switch includes network interfaces connected to ports to enable communication among entities attached to the network interfaces by forwarding data packets within a first datapath of the first data plane. In response to the change, the network interfaces are disconnected, the first datapath is removed and a second datapath is created. The virtual switch is then configured to operate with the second datapath while retaining the flow management protocol and the topology, such that the entities communicate by forwarding data packets within the second datapath on the second data plane.

Techniques disclosed herein provide an approach for providing throughput resilience during link failover when links are aggregated in a link aggregation group (LAG). In one embodiment, failure of a link in the LAG may be detected, and a Transmission Control Protocol/Interact Protocol (TCP/IP) stack notified to ignore packet losses and not perform network congestion avoidance procedure(s) for one round-trip timeout (RTO) period. In a virtualized system in particular, a virtual switch may be configured to generate events in response to detected link failures and notify TCP/IP stacks of a hypervisor and/or virtual machines (VMs) of the link failures. In turn, the notified TCP/IP stacks of the hypervisor and/or VMs may ignore packet losses and not perform network congestion avoidance procedure(s) for one RTO period.

The present disclosure relates to systems and methods for detection of a failed communication link and rerouting network traffic around the failure. One embodiment of a system consistent with the present disclosure may comprise a communication subsystem in communication with the data network and configured to transmit information to a recipient. The system may also include a confirmatory signal subsystem configured to generate a confirmatory signal. The confirmatory signal may be inserted into a stream of data to be transmitted to the recipient through a first communication path. Upon detection of a disruption in the confirmatory signal, a failover subsystem configured to reroute the stream of network data to be transmitted to the recipient through a second communication path. The second communication path may comprise one or more physical connections in the network that are distinct from the first communication path.

A method involves setting a link aggregation control protocol (LACP) link state for all links in a first service node to STANDBY to put at least one multiplexer in the first service node in a WAITING state to disable frame collection at the redundant service node and setting the LACP link state for all links in a second service node to SELECTED to put at least one multiplexer in the second service node in a COLLECTING/DISTRIBUTING state to enable frame collection at the primary service node.

A method for routing a redirected request message is disclosed. The method may be implemented in a Diameter signaling router (DSR) including a plurality of message processors. The method includes applying ingress message processing to a Diameter request message received from a peer node and forwarding the Diameter request message to a Diameter redirect agent in accordance to the ingress message processing. The method further includes receiving, from the Diameter redirect agent, a redirection notification message containing redirection information and modifying the Diameter request message to include the redirection information. The method also includes applying the ingress message processing to the modified Diameter request message within the DSR.

An apparatus includes a destination edge device configured to receive a first validation packet according to a switch fabric validation protocol. The destination edge device is configured to validate multiple data paths through a distributed switch fabric from a source edge device to the destination edge device based on the first validation packet. The destination edge device is configured to send, in response to receiving the first validation packet, a second validation packet to a peripheral processing device. The destination edge device is also configured to send the second validation packet according to a validation protocol different from the first validation protocol.

A method, a network, and a network element use dynamic packet traffic performance adjustment techniques. In an exemplary embodiment, the dynamic resizing techniques utilize different packet connections providing connectivity to same sites between which bandwidth resizing is needed. Each of the packet connections has a separate and independent bandwidth profile that governs an amount of traffic that is dispatched over each packet connection. A network element sourcing traffic into the packet connections uses bridge functionality that dispatches client traffic onto all of the packet connections or an individual packet connection. This effectively means that the transport network bandwidth utilization is only consumed by a single packet connection, i.e., the packet connection-A (even through there are multiple configured). The network element sinking the traffic selects from a single active packet connection.

Due to interference that typically occurs in the ISM band, it may be necessary for one or more network devices to switch to an alternative channel. A list of one or more alternate network channels may be generated by a coordinating/gateway device based on the energy level and a distance from a primary network channel. The alternate network channel list may be distributed to neighbor devices and, in the event of interference, link loss, and/or a channel switch notification, the neighbor devices may automatically switch to the first alternate network channel in the list.