Abstract: A method for measuring latency of a data packet attributable to transit of the data packet through a distributed gateway includes transmitting, from a first virtual machine of a plurality of virtual machines executing different instances of a gateway, a ping request to each of the other virtual machines. A ping reply is received at the first virtual machine in association with each of the transmitted ping requests, and the first virtual machine measures a round-trip transit (RTT) time between transmission of each one of the ping requests and receipt of the corresponding ping response. The method further provides for publishing a latency statistic for the distributed gateway that is generated based on an aggregation of the RTT times measured by the first virtual machine.

Abstract: A method for measuring latency of a data packet attributable to transit of the data packet through a distributed gateway includes transmitting, from a first virtual machine of a plurality of virtual machines executing different instances of a gateway, a ping request to each of the other virtual machines. A ping reply is received at the first virtual machine in association with each of the transmitted ping requests, and the first virtual machine measures a round-trip transit (RTT) time between transmission of each one of the ping requests and receipt of the corresponding ping response. The method further provides for publishing a latency statistic for the distributed gateway that is generated based on an aggregation of the RTT times measured by the first virtual machine.

Abstract: Aspects of the embodiments are directed to forming a virtual machine management (VMM) domain in a heterogeneous datacenter. Aspects can include mapping an endpoint group to multiple VMM domains, each VMM domain associated with one or more virtual machine management systems of a single type that each share one or more management system characteristics; instantiating a virtual switch instance, the virtual switch instance associated with a the VMM domain; and instantiating the endpoint group mapped to the VMM domain as a network component associated with the virtual switch instance.

Abstract: The techniques presented herein use dynamic endpoint group (EPG) binding changes to facilitate cross-tenant resource sharing. A first node of a multi-tenant software defined network determines that an application on a first endpoint has initiated operation and needs temporary access to resources located at a second endpoint. The first and second endpoints are associated with first and second tenants, respectively, that are logically segregated from one another by the software defined network. The first node dynamically changes an initial EPG binding associated with the first endpoint to a second EPG binding that enables the first endpoint to temporarily directly access the resources at the second endpoint. The first node subsequently determines that the application on the first endpoint no longer needs access to the resources located at a second endpoint and, as such, changes the second EPG binding associated with the first endpoint back to the initial EPG binding.

Abstract: The techniques presented herein use dynamic endpoint group (EPG) binding changes to facilitate cross-tenant resource sharing. A first node of a multi-tenant software defined network determines that an application on a first endpoint has initiated operation and needs temporary access to resources located at a second endpoint. The first and second endpoints are associated with first and second tenants, respectively, that are logically segregated from one another by the software defined network. The first node dynamically changes an initial EPG binding associated with the first endpoint to a second EPG binding that enables the first endpoint to temporarily directly access the resources at the second endpoint. The first node subsequently determines that the application on the first endpoint no longer needs access to the resources located at a second endpoint and, as such, changes the second EPG binding associated with the first endpoint back to the initial EPG binding.

Abstract: In one embodiment, line cards of packet switching or other network devices are configured for terminating pseudowires. Typically, this includes multiple line cards being configured for terminating a same pseudowire, which allows the corresponding pseudowire traffic to be received by any one of these multiple line cards. Each of these pseudowire-terminating line cards is typically configured to apply one or more features to a pseudowire packet. Examples of these features include, but are not limited to: Access Control List, Quality of Service, Netflow, and Lawful Intercept. For a received packet to be sent out one of these pseudowires, a two-stage lookup operation can be used to first identify the pseudowire over which to forward the packet; and a second lookup operation based on the pseudowire to identify forwarding information corresponding to a path through a network over which a corresponding pseudowire is configured.

Abstract: A Multicast Listener Discovery (MLD) protocol query and/or report snooping process is modified to appropriately map secondary PVLAN identifiers to corresponding primary PVLAN identifiers, thereby accommodating other system elements that are otherwise unaware of primary/secondary PVLAN distinctions. Special cases are also accommodated where reverse path forwarding (RPF) checks in support of multicast operation might otherwise fail due to primary/secondary PVLAN distinctions. Additional steps are taken to ensure that PVLAN information properly accounts for changes in configuration and/or location of various network hosts.

Abstract: In one embodiment, line cards of packet switching or other network devices are configured for terminating pseudowires. Typically, this includes multiple line cards being configured for terminating a same pseudowire, which allows the corresponding pseudowire traffic to be received by any one of these multiple line cards. Each of these pseudowire-terminating line cards is typically configured to apply one or more features to a pseudowire packet. Examples of these features include, but are not limited to: Access Control List, Quality of Service, Netflow, and Lawful Intercept. For a received packet to be sent out one of these pseudowires, a two-stage lookup operation can be used to first identify the pseudowire over which to forward the packet; and a second lookup operation based on the pseudowire to identify forwarding information corresponding to a path through a network over which a corresponding pseudowire is configured.

Abstract: A Multicast Listener Discovery (MLD) protocol query and/or report snooping process is modified to appropriately map secondary PVLAN identifiers to corresponding primary PVLAN identifiers, thereby accommodating other system elements that are otherwise unaware of primary/secondary PVLAN distinctions. Special cases are also accommodated where reverse path forwarding (RPF) checks in support of multicast operation might otherwise fail due to primary/secondary PVLAN distinctions. Additional steps are taken to ensure that PVLAN information properly accounts for changes in configuration and/or location of various network hosts.