Embodiments relate generally to systems and methods for transitioning a system from a tradition network to a Software Defined Network (SDN) enabled network. In some embodiments, the systems and methods may comprise the use of a Path Computation Element (PCE) as a central controller. Smooth transition between traditional network and the new SDN enabled network, especially from a cost impact assessment perspective, may be accomplished using the existing PCE components from the current network to function as the central controller of the SDN network is one choice, which not only achieves the goal of having a centralized controller to provide the functionalities needed for the central controller, but also leverages the existing PCE network components.

Examples disclosed herein relate to reducing flooding of route updates of a dynamic routing protocol. In an example, number of route updates received by a router from each neighbor router may be determined, wherein the router may be present in a network using a dynamic routing protocol. Each neighbor router may be classified into one of a plurality of groups of neighbor routers in such a manner that number of route updates originating from each group of neighbor routers is approximately same. A first route update interval may be determined for each group of neighbor routers for sending a respective first set of future route updates therefrom to the router. The respective first route update interval for sending the respective first set of future route updates may be notified to the respective member routers of each group of neighbor routers.

Technologies are described herein for routing a service request to an appropriate web service. A first service request is routed from a first web service to a second web service. Routing factors associated with the second web service are monitored. A determination is made as to whether the routing factors indicate that the second web service is no longer appropriate for handling service requests. If the routing factors indicate that the first web service is no longer appropriate for handling service requests, then a second service request is routed from the first web service to a third web service. The first web service, the second web service, and the third web service are included in a composite service.

In one example in accordance with the present disclosure, a system may comprise a node accessor to access a first node belonging to a plurality of nodes and an interface determiner to determine a hardware interface associated with the first node. The system may comprise a template determiner to determine a template corresponding to the hardware interface, wherein the template contains a predefined identifier associated with the hardware interface. The system may comprise a network handler to identify a network associated with the predefined identifier associated with the hardware interface; and a network associater to associate each node in the plurality of nodes, including the first node, with a network specified in the template.

Embodiments relate generally to systems and methods for transitioning a system from a tradition network to a Software Defined Network (SDN) enabled network. In some embodiments, the systems and methods may comprise the use of a Path Computation Element (PCE) as a central controller. Smooth transition between traditional network and the new SDN enabled network, especially from a cost impact assessment perspective, may be accomplished using the existing PCE components from the current network to function as the central controller of the SDN network is one choice, which not only achieves the goal of having a centralized controller to provide the functionalities needed for the central controller, but also leverages the existing PCE network components.

A congestion notification method, a related device, and a system, where the method includes receiving, by a network side device, a congestion status of a target network area sent by a radio access network (RAN) congestion awareness function (RCAF) entity, where the target network area is a network area involved in an application service provided by a target application server; and sending, by the network side device, the congestion status of the target network area to the target application server. Hence, an application server may able to learn in time when congestion occurs, and adjust, according to the congestion situation, a related service in an area corresponding to the congestion situation.

Techniques for detecting path failures and reducing packet loss as a result of such failures are described for use within a data center or other environment. For example, a source and/or destination access node may create and/or maintain information about health and/or connectivity for a plurality of ports or paths between the source and destination device and core switches. The source access node may spray packets over a number of paths between the source access node and the destination access node. The source access node may use the information about connectivity for the paths between the source or destination access nodes and the core switches to limit the paths over which packets are sprayed. The source access node may spray packets over paths between the source access node and the destination access node that are identified as healthy, while avoiding paths that have been identified as failed.

A smart process control switch can implement a lockdown routine to lockdown its communication ports exclusively for use by devices having known physical addresses, enabling the smart process control switch to prevent new, potentially hostile, devices from communicating with other devices to which the smart process control switch is connected. Further, the smart process control switch can implement an address mapping routine to identify known pairs of physical and network addresses for each device communicating via a port of the smart process control switch. Thus, even if a new hostile device is able to spoof a known physical address in an attempt to bypass locked ports, the smart process control switch can detect the hostile device by checking the network address of the hostile device against the expected network address for the known pair.

Disclosed are system, methods, and non-transitory computer readable media for accurately calculating a default gateway of an endpoint without probing the endpoint for the configured values to determine the path between network elements. Tracing the path of a flow in a network and displaying that on a user interface is extremely useful for network troubleshooting purposes. In order to find the gateway the flow would take out of the L2 domain, the endpoint's L2 default gateway is required. Usually the L2 gateway for network endpoints is configured on the endpoints themselves and this information cannot be accessed by network controllers (e.g., APIC-EM) directly. In such cases APIC-EM needs to determine the L2 gateway based on the information available to it from the network elements, instead of the endpoints themselves.

Technologies are described herein for routing a service request to an appropriate web service. A first service request is routed from a first web service to a second web service. Routing factors associated with the second web service are monitored. A determination is made as to whether the routing factors indicate that the second web service is no longer appropriate for handling service requests. If the routing factors indicate that the first web service is no longer appropriate for handling service requests, then a second service request is routed from the first web service to a third web service. The first web service, the second web service, and the third web service are included in a composite service.