Systems and methods for fronthaul optimization using software defined networking are provided. In one example, a method includes receiving time period information and destination information for a time period from one or more base station entities (BSEs), each BSE configured to implement some functions for layer(s) of a wireless interface used to communicate with UEs. The method further includes determining a configuration of Ethernet switch(es) based on the destination information for the time period and topology information for the Ethernet switch(es). The Ethernet switch(es) are communicatively coupled to the BSE(s) and configured to: receive downlink fronthaul data from the BSE(s), be communicatively coupled to one or more RUs, and forward downlink fronthaul data from the one or more base station entities to the one or more RUs. The method further includes transmitting update(s) for forwarding rules to the Ethernet switch(es) based on the determined configuration for the Ethernet switch(es).

A system and method for fast roaming in one or more enterprise fabric network. The fast roaming involves correlation operations performed in one or more databases managed by control plane of the fabric network to update routing locator entries associated with L2-VNID and L3-VNID in one or more databases when a client moves from behind a first switch to behind a second switch. In some embodiments, the control plane finds the L3-VNID from the L2-VNID. The L3-VNID is used to search for all IP addresses corresponding to a client-MAC. At least new routing locator value that is used in the routing locator entries is provided to the first switch, the second switch, and border nodes associated with the fabric network.

A networking system may include a first network such as a private cloud network and a second network such as a public cloud network. The first network may include a switch coupled to a computing resource. To facilitate a robust and flexible inter-network connection, the networking system may include network connector circuitry having a connector endpoint at the first network and a network connector coupling the connector endpoint to a network element at the second network. A controller for the first network may provide control signals and configuration data to the network connector circuitry to form the connection to the second network and may configure the switch to forward external network traffic to and from the connector endpoint via a switch port directly coupled to the connector endpoint.

A system for efficient routing of an (OAM) frame in an Ethernet switch receives an OAM frame at a first port; building a first classification key dependent on an OAM frame header; classifies in a context of the first port to create a first classification; resolves action dependent on the first classification; modifies the first classification key to create a second classification key; classifies the frame in a context of the second port to create a second classification; sends the second classification key to an OAM engine coupled to the Ethernet switch for modification into a third classification key; receives the third classification key from the OAM engine; modifies the third classification key into a final classification key; modifies the header of the OAM frame with the final classification key; and sends the modified OAM frame to a switching fabric of the Ethernet switch.

A tunnel connection is enabled between a user terminal and a service provider using a simpler network configuration. A communication system 10 includes a user terminal 20, a service provider 30, a carrier network 40 that connects the user terminal 20 and the service provider 30 to each other, and a network control device 50 that controls the carrier network 40. The network control device 50 sets respective virtual tunnel end points (VTEPs) for a POI terminal 46 that is on the carrier network 40 and that is connected to the service provider 30 and for the user terminal 20, and sets a virtual tunnel between the virtual tunnel end points. The user terminal 20 communicates with the service provider 30 via the virtual tunnel.

Cloud based router with policy enforcement. In some implementations, a system is provided. The system includes a plurality of access points. The plurality of access points receive data packets from a plurality of client devices. The system also includes a plurality of tunnel devices coupled to the plurality of access points. The plurality of tunnel devices generate encapsulated packets based on the data packets received by the plurality of access points. The system further includes a plurality of packet forwarding components coupled to the plurality of tunnel devices via a first set of tunnels. The plurality of packet forwarding components receive the encapsulated packets from the plurality of tunnel devices and forward the encapsulate packets. The system further includes a plurality of network access controllers coupled to the plurality of packet forwarding components via a second set of tunnels. The plurality of network access controllers enforce one or more network policies for the plurality of client devices, as the plurality of client devices move between the plurality of access points.

As described herein, a router signals a source device to establish a new stateful communication session with a destination device by changing a network path used by traffic associated with the session. In one example, a router forwards traffic of a first stateful routing session established by the source device along a first path. In response to determining that that the first path should not be used, the router forwards a packet of the first session along a second path. The destination device recognizes the change in path, which causes the destination device to reject the packet, which in turn causes the source device to establish a second stateful routing session. The router forwards subsequent traffic of the second stateful routing session along the second path.

In general, this disclosure describes a programmable network platform for dynamically programming a cloud exchange to provide a layer three (L3) routing instance as a service to customers of the cloud exchange. In one example, a cloud exchange comprises an L3 network located within a data center and configured with an L3 routing instance for an enterprise; and for the L3 routing instance, respective first and second attachment circuits for first and second cloud service provider networks co-located within the data center, wherein the L3 routing instance stores a route to a subnet of the second cloud service provider network to cause the L3 routing instance to forward packets, received from the first cloud service provider network via the first attachment circuit, to the second cloud service provider network via the second attachment circuit.

Example methods and systems for packet handling in a software-defined networking (SDN) environment are disclosed. One example method may comprise detecting an egress application-layer message from a first logical endpoint supported by a first host; and identifying a second logical endpoint supported by the second host for which the egress application-layer message is destined. The method may also comprise generating an egress packet that includes the egress application-layer message and metadata associated with the second logical endpoint, but omits one or more headers that are addressed from the first logical endpoint to the second logical endpoint. The method may further comprise sending the egress packet to the second host to cause the second host to identify the second logical endpoint based on the metadata, and to send the egress application-layer message to the second logical endpoint.

In an example, a network device may receive a L3VPN packet of which an egress label edge router (LER) is the network device, and acquire an adjacency index of an adjacency entry in an adjacency table according to the destination IP address of the inner IP datagram from the L3VPN packet. The network device may acquire a PW extended index of a PW extended entry in a PW extended table and a private network layer-2 header for the inner IP datagram from an adjacency entry having the adjacency index. By using the private network layer-2 header and a public network label, a private network label and a public network layer-2 header in a PW extended entry having the PW extended index, the network device may encapsulate the inner IP datagram into a L2VPN packet and forward the L2VPN packet through a physical egress interface in the PW extended entry.