A replay device includes: multiple transceiver units that transmits and receives a communication frame, each transceiver unit including a register in which at least data indicating a set-up content relating to an operation of a respective transceiver unit is written; a register access unit that is connected with each transceiver unit through an interface; and a control unit that transmits a control message to the register access unit. The control message includes access target information for designating one or more access target transceiver units, and access content information indicating an access content to a register of each access target transceiver unit. The register access unit sets the one or more target transceiver units designated by the access target information, and perform an access to the register of each access target transceiver unit according to the access content.

In exemplary embodiments of the present invention, a router determines whether or not to establish a stateful routing session based on the suitability of one or more candidate return path interfaces. This determination is typically made at the time a first packet for a new session arrives at the router on a given ingress interface. In some cases, the router may be configured to require that the ingress interface be used for the return path of the session, in which case the router may evaluate whether the ingress interface is suitable for the return path and may drop the session if the ingress interface is deemed by the router to be unsuitable for the return path. In other cases, the router may be configured to not require that the ingress interface be used for the return path, in which case the router may evaluate whether at least one interface is suitable for the return path and drop the session if no interface is deemed by the router to be suitable for the return path.

In exemplary embodiments of the present invention, a router determines whether or not to establish a stateful routing session based on the suitability of one or more candidate return path interfaces. This determination is typically made at the time a first packet for a new session arrives at the router on a given ingress interface. In some cases, the router may be configured to require that the ingress interface be used for the return path of the session, in which case the router may evaluate whether the ingress interface is suitable for the return path and may drop the session if the ingress interface is deemed by the router to be unsuitable for the return path. In other cases, the router may be configured to not require that the ingress interface be used for the return path, in which case the router may evaluate whether at least one interface is suitable for the return path and drop the session if no interface is deemed by the router to be suitable for the return path.

Certain aspects of the present disclosure provide a method of operating a service provider network node in a service provider network, comprising: establishing an interface between a control plane processing part and a data plane processing part for routing of control packets at the data plane processing part; at the control plane processing part, generating a control packet for routing through the service provider network; and at the control plane processing part, sending the control packet to the data plane processing part via the interface, to cause the data plane processing part to route the control packet through the service provider network using the one or more routing tables maintained by the data plane processing part in response to receiving the control packet from the control plane processing part via the interface.

In exemplary embodiments of the present invention, a router determines whether or not to establish a stateful routing session based on the suitability of one or more candidate return path interfaces. This determination is typically made at the time a first packet for a new session arrives at the router on a given ingress interface. In some cases, the router may be configured to require that the ingress interface be used for the return path of the session, in which case the router may evaluate whether the ingress interface is suitable for the return path and may drop the session if the ingress interface is deemed by the router to be unsuitable for the return path. In other cases, the router may be configured to not require that the ingress interface be used for the return path, in which case the router may evaluate whether at least one interface is suitable for the return path and drop the session if no interface is deemed by the router to be suitable for the return path.

An example network orchestrator includes processing circuitry and a memory including instructions that, when executed by the processing circuitry, cause the network orchestrator to determine that a branch site of a WAN includes multiple branch gateways. The network orchestrator further determines that devices of a core site of the WAN and devices of the branch site are members of an extended VLAN. The network orchestrator further transmits a first command to a first branch gateway and a first headend gateway to establish a WAN uplink tunnel to forward data traffic of the extended VLAN. The network orchestrator further transmits a second command to a set of branch gateways of the branch gateway cluster to establish intracluster tunnels with the first branch gateway.

Certain aspects of the present disclosure provide a method of operating a service provider network node in a service provider network, comprising: establishing an interface between a control plane processing part and a data plane processing part for routing of control packets at the data plane processing part; at the control plane processing part, generating a control packet for routing through the service provider network; and at the control plane processing part, sending the control packet to the data plane processing part via the interface, to cause the data plane processing part to route the control packet through the service provider network using the one or more routing tables maintained by the data plane processing part in response to receiving the control packet from the control plane processing part via the interface.

A highly parallel programmable packet editing engine with a scalable control infrastructure includes receiving an ingress packet having one or more headers; assigning, by one or more processors, the one or more headers of the ingress packet to a number of zones, wherein each zone is a grouping of adjacent headers that are closely related to one another by information content or processing type; performing, by the one or more processors, offset computations for the one or more headers in a zone concurrently with offset computations of headers assigned to other zones; performing, by the one or more processors, different header operations on the one or more headers concurrently with respective ones of a plurality of editing engines; combining, by the one or more processors, the edited one or more headers at the computed offsets to generate a modified egress packet; and providing, for transmission, the modified egress packet.

A replay device includes: multiple transceiver units that transmits and receives a communication frame, each transceiver unit including a register in which at least data indicating a set-up content relating to an operation of a respective transceiver unit is written; a register access unit that is connected with each transceiver unit through an interface; and a control unit that transmits a control message to the register access unit. The control message includes access target information for designating one or more access target transceiver units, and access content information indicating an access content to a register of each access target transceiver unit. The register access unit sets the one or more target transceiver units designated by the access target information, and perform an access to the register of each access target transceiver unit according to the access content.

A system and method for handling a digital electronic flow between a first and second entity in which a flow policy is determined that is to be applied to the flow and the flow is then directed along a path in accordance with the policy. An ID is supplied for each flow and a tag associated with each flow which indicates the policy to be applied to its associated flow. Flows are also associated with one another, with associated flows having associated policies. In particular the flow may be processed or forwarded. The path may include a graph structure and virtual applications.