Abstract: A packet is generated at a first network connected device for transmission to a destination network device through a network comprising a plurality of pods. At least two of the plurality of pods are within separate management domains, and generating the packet comprises generating the packet with a first identifier and a second identifier. The first identifier indicates a pod of the plurality of pods in which the destination network connected device is located, and the second identifier indicates an identity of the destination network connected device within the pod of the plurality of pods. The packet is transmitted from the first network connected device to the destination network connected device.

Abstract: A determination is made at a network connected device that a network policy is to be verified. The network policy is applied to network packets sent to an endpoint within a network, and the application of the policy to network traffic can result in at least two outcomes. Another determination is made at the network connected device that a switch is provisionable to host the endpoint. The network connected device provisions a simulated endpoint version of the endpoint at the switch to host the policy. At least one packet is sent to the simulated endpoint via the network connected device for each of the at least two outcomes of the policy. At least one response is received by the network connected device from the simulated endpoint indicating how the policy was applied to each of the packets.

Abstract: Internet Group Management Protocol (IGMP) snooping includes flooding an IGMP query received at a border leaf switch from a multicast router connected to the multicast router to all host devices in a given bridge domain through leaf switches in the bridge domain, and receiving multiple join requests from the connected host devices at the leaf switches. The IGMP snooping also includes consolidating the multiple join requests received at the leaf switches into a multicast groups membership repository to indicate for each leaf switch the multicast group membership of interest in the given bridge domain, and sending the repository to the border leaf switch to enable the border leaf switch to send a consolidated IGMP proxy report on behalf of the leaf switches to the multicast router based on the repository and that indicates the multicast membership of interest in the given bridge domain.

Abstract: An example method for to multicast traffic distribution in a multi-pod network environment is provided and includes provisioning a block of multicast group addresses for broadcast, unknown unicast and multicast (BUM) traffic distribution between pods in the multi-pod network, calculating a hash corresponding to a bridge domain (BD) extending across a plurality of pods in the multi-pod network, the hash being identically calculated at each one of the plurality of pod, indexing with the hash into the block of multicast group addresses designated for inter-pod BUM traffic to derive a global multicast group identical for the broadcast domain across the plurality of pods, and associating a local multicast group at the translator with the derived global multicast group.

Abstract: An inner packet configured with a multicast address and configured to perform a traceroute operation through a network is encapsulated to form an encapsulated packet. The encapsulated packet is sent into a network, the encapsulated packet being forwarded along a multicast tree of the network for the multicast address. A plurality of responses are received from a plurality of network nodes comprising the multicast tree, wherein each response comprises an indication of a node of the plurality of nodes that sends the response and an indication of a node from which the node sending the response received the encapsulated packet.

Abstract: A packet is generated at a first network connected device for transmission to a destination network device through a network comprising a plurality of pods. At least two of the plurality of pods are within separate management domains, and generating the packet comprises generating the packet with a first identifier and a second identifier. The first identifier indicates a pod of the plurality of pods in which the destination network connected device is located, and the second identifier indicates an identity of the destination network connected device within the pod of the plurality of pods. The packet is transmitted from the first network connected device to the destination network connected device.

Abstract: A packet is generated at a first network connected device for transmission to a destination network device through a network comprising a plurality of pods. At least two of the plurality of pods are within separate management domains, and generating the packet comprises generating the packet with a first identifier and a second identifier. The first identifier indicates a pod of the plurality of pods in which the destination network connected device is located, and the second identifier indicates an identity of the destination network connected device within the pod of the plurality of pods. The packet is transmitted from the first network connected device to the destination network connected device.

Abstract: A determination is made at a network connected device that a network policy is to be verified. The network policy is applied to network packets sent to an endpoint within a network, and the application of the policy to network traffic can result in at least two outcomes. Another determination is made at the network connected device that a switch is provisionable to host the endpoint. The network connected device provisions a simulated endpoint version of the endpoint at the switch to host the policy. At least one packet is sent to the simulated endpoint via the network connected device for each of the at least two outcomes of the policy. At least one response is received by the network connected device from the simulated endpoint indicating how the policy was applied to each of the packets.

Abstract: A packet is generated at a first network connected device for transmission to a destination network device through a network comprising a plurality of pods. At least two of the plurality of pods are within separate management domains, and generating the packet comprises generating the packet with a first identifier and a second identifier. The first identifier indicates a pod of the plurality of pods in which the destination network connected device is located, and the second identifier indicates an identity of the destination network connected device within the pod of the plurality of pods. The packet is transmitted from the first network connected device to the destination network connected device.

Abstract: An example method for to multicast traffic distribution in a multi-pod network environment is provided and includes provisioning a block of multicast group addresses for broadcast, unknown unicast and multicast (BUM) traffic distribution between pods in the multi-pod network, calculating a hash corresponding to a bridge domain (BD) extending across a plurality of pods in the multi-pod network, the hash being identically calculated at each one of the plurality of pod, indexing with the hash into the block of multicast group addresses designated for inter-pod BUM traffic to derive a global multicast group identical for the broadcast domain across the plurality of pods, and associating a local multicast group at the translator with the derived global multicast group.

Abstract: An inner packet configured with a multicast address and configured to perform a traceroute operation through a network is encapsulated to form an encapsulated packet. The encapsulated packet is sent into a network, the encapsulated packet being forwarded along a multicast tree of the network for the multicast address. A plurality of responses are received from a plurality of network nodes comprising the multicast tree, wherein each response comprises an indication of a node of the plurality of nodes that sends the response and an indication of a node from which the node sending the response received the encapsulated packet.

Abstract: At a data switching device in a data center, it is detected whether a host has connected to a cloud computing network of which the data switching device and the data center are components. The detection is performed without directly communicating with the host. The data switching device determines properties of the host and generates a message comprising data representative of the properties of the host. The message is sent from the data switching device to a node in the cloud computing network that is configured to manage components of the cloud computing network associated with the host.

Abstract: Systems, methods, and non-transitory computer-readable storage media for dynamic host configuration protocol (DHCP) relay functionality in overlay networks. A system on a overlay network fabric can first receive a DHCP request from a host device, the system including a tunnel endpoint (TEP) configured to connect the host device to the overlay network fabric via a tunnel. The system then enables a relay agent information option for relaying the DHCP request with sub-options inserted into the DHCP request, and inserts information into to the sub-options in the DHCP request to yield a modified DHCP request. Here, the information can include an address of the system and an interface of a circuit associated with the system, etc. Next, the system forwards the modified DHCP request to a destination DHCP server based on an address of the destination DHCP server associated with the DHCP request.

Abstract: At a data switching device in a data center, it is detected whether a host has connected to a cloud computing network of which the data switching device and the data center are components. The detection is performed without directly communicating with the host. The data switching device determines properties of the host and generates a message comprising data representative of the properties of the host. The message is sent from the data switching device to a node in the cloud computing network that is configured to manage components of the cloud computing network associated with the host.

Abstract: Disclosed herein in an example embodiment is a multicast policy infrastructure that allows administrators to integrate location awareness for a particular multicast stream when it is being forwarded to an intended user. The infrastructure provides more flexibility by allowing multicast call admission control, access control, and other multicast policies to be based on the location or conditions where the host/user is receiving the multicast stream. A multicast policy can also provide additional mechanisms such as transcoding services, compression services, etc. based on the host/user location. As will be demonstrated in example embodiments herein, location awareness can include connectivity media (wired or wireless), physical location of user, and/or signal strength (and/or effective bandwidth).

Abstract: Disclosed herein in an example embodiment is a multicast policy infrastructure that allows administrators to integrate location awareness for a particular multicast stream when it is being forwarded to an intended user. The infrastructure provides more flexibility by allowing multicast call admission control, access control, and other multicast policies to be based on the location or conditions where the host/user is receiving the multicast stream. A multicast policy can also provide additional mechanisms such as transcoding services, compression services, etc. based on the host/user location. As will be demonstrated in example embodiments herein, location awareness can include connectivity media (wired or wireless), physical location of user, and/or signal strength (and/or effective bandwidth).