Techniques are disclosed for providing a Software Defined Networking (SDN) controller with real-time or near-real time visibility of the operation of data center fabrics to determine whether the DCI was properly configured. For example, an SDN controller receives high-level configuration data that describes a desired state of a network managed by the SDN controller at a high level of abstraction. The SDN controller applies a transformation function to the high-level configuration data to generate a low-level configuration data for network devices configured to implement the desired state of the network. SDN controller configures the SDN controller as a peer to the network devices to obtain one or more routes exchanged between the network devices. The SDN controller sends the low-level configuration data to the network devices to cause the network devices to implement the desired state of the network.

In one embodiment, a first label-distribution-protocol (LDP) session is established between a first interface of a first computing device and a second computing device, while a second LDP session is established between a second interface and the second computing device. The method may further comprise receiving a request from a third computing device to subscribe to a multicast group, storing an association between a first label, the multicast group, and the first interface, and sending, to the second computing device via the first LDP session, an indication that the first label is associated with the multicast group. Further, the method may include receiving a request from a fourth computing device to subscribe to the multicast group, storing an association between a second label, the multicast group and, the second interface, and sending, via the second LDP session, an indication that the second label is associated with the multicast group.

A Software Defined Networking (SDN) controller controls multicast traffic in an SDN domain and one or more non-SDN domains imbedded in the SDN domain.

Some embodiments provide a method for configuring an edge computing device to implement a logical router belonging to a logical network. The method configures a datapath executing on the edge computing device to use a first routing table associated with the logical router for processing data messages routed to the logical router. The method configures a routing protocol application executing on the edge computing device to (i) use the first routing table for exchanging routes with a network external to the logical network and (ii) use a second routing table for exchanging routes with other edge computing devices that implement the logical router.

Some embodiments provide a method for an edge computing device in a first datacenter that implements a logical network gateway for processing data traffic for a particular LFE between the first datacenter and multiple other datacenters. For each particular other datacenter, the method stores a record that maps logical network addresses for DCNs connected to the particular LFE and operating in the particular datacenter to a group of TEP addresses corresponding to logical network gateways that handle data traffic for the particular LFE between the particular datacenter and the other datacenters, including the first datacenter. Upon receiving a data message for the particular LFE from a host computer in the first datacenter, the method uses a destination address of the data message to identify one of the groups of TEP addresses. The method encapsulates the data message with one of the TEP addresses from the identified group of TEP addresses.

Systems and methods for monitoring network traffic. A server may receive data packets originated from a first remote computer system, the data packets having a destination of a second remote computer system. The server may determine a user of the first computer system and, based thereon, identify network traffic monitoring tools configured to connect to the server through respective distinct network addresses. The server may determine a routing path for the packets including a sequence of network addresses including the respective distinct addresses of the identified network traffic monitoring tools and a second network address corresponding to the second computer system. The second network address may be ordered after the respective distinct addresses of the identified network traffic monitoring tools in the sequence. The server may send, according to the routing path, the packets to the identified network traffic monitoring tools and the second computer system.

This disclosure describes various methods, systems, and devices related to dynamic service node discovery in a network. In an example method, a service node generates a discover message including a discovery field. The discovery field indicates an identifier of the service node. The service node further transmits the discovery message to an intermediary node.

This disclosure provides systems and methods for routing and topology management of computer networks with steerable beam antennas. A network controller can generate an input graph for a first time period. The input graph can have a plurality of vertices each representing a respective moving node and a plurality of edges each representing a possible link between a pair of moving nodes. The input graph also can include corresponding location information for each of the moving nodes during the first time period. A solver module can receive information corresponding to the input graph, a maximum degree for each vertex in the input graph, and a set of provisioned network flows. The solver module can determine a subgraph representing a network topology based on the input graph, the maximum degree for each vertex in the input graph, and the set of provisioned network flows, such that a number of edges associated with each vertex in the subgraph does not exceed the maximum degree for each vertex.

Techniques for avoiding single points of failure in routing components of an SDN are disclosed. In some aspects, control nodes that provide routing management services are assigned zone identifiers. The control nodes having one zone identifier can be on separate processes and/or physical hardware from control nodes having a different zone identifier. Workloads, such as virtual machines or containers, can establish routing sessions such as Border Gateway Protocol as a Service (BGPaaS) routing sessions using different zone identifiers to ensure that separate control nodes provide routing management services for the primary and secondary compute nodes associated with a high availability service. These techniques in this way facilitate high availability by ensuring that a control node is not a single point of failure for the high availability service provided by the primary and secondary compute nodes.

Techniques for utilizing Software-Defined Networking (SDN) controllers and network border leaf nodes of respective cloud computing networks to configure a data transmission route for a multicast group. Each border leaf node may maintain a respective external sources database, including a number of records indicating associations between a multicast data source, one or more respective border leaf nodes disposed in the same network as the multicast data source, and network capability information. A border leaf node, disposed in the same network as a multicast data source, may broadcast a local source discovery message to all border leaf nodes in remote networks to which it is communicatively coupled. A border leaf node may also communicate network capability information associated with one or more remote networks to a local SDN controller. The SDN controller may utilize the network capability information to configure a data transmission route to one or more destination nodes.