How to Monitor VMware vSphere Distributed Switches

dudelaptop179631226It’s not uncommon for different teams to be managing the virtual switch and physical switch configurations. This can make it very difficult to troubleshoot unless each configuration parameter has been gone through manually. There have been enhancements to the vSphere Distributed Switch over the past few years to address these operational challenges.

vSphere 5.0 introduced support for Link Layer Discovery Protocol (LLDP); an earlier version of vSphere had support for Cisco Discovery Protocol (CDP). CDP is supported for both Standard and Distributed vSwitches, whereas LLDP is supported only for Distributed vSwitches. Both discovery protocols provide information about neighbor network devices, such as the device ID, software version, timeout, and so on. CDP is Cisco proprietary, so there are obvious incompatibility issues when using network devices from other vendors. LLDP is a vendor-neutral discovery protocol.

The Network Health Check feature was introduced with vSphere 5.1. This feature detects any misconfiguration of VLAN, MTU and NIC Teaming parameters across the virtual switch and the connected physical switch (access layer switch). When enabled, layer 2 Ethernet frames are exchanged across the ESXi host uplinks each minute to detect misconfiguration. In order for this feature to operate correctly, there should be at least two uplinks configured on the vDS and at least two ESXi hosts using the vDS. This feature is not enabled by default and can only be enabled using the vSphere Web Client.

Port mirroring is the capability of a network switch to send a copy of network traffic seen on one switch port to another switch port that may have a network-monitoring device connected. Port mirroring is sometimes referred to as Switch Port Analyzer (SPAN) on Cisco switches. The vSphere Distributed Switch provides a similar port mirroring function. A port-mirroring session is configured with a destination and once configured, the vDS will copy the network traffic to the destination. Port-mirroring sessions may be created between virtual machines on the same ESXi host, virtual machines on different ESXi hosts, from a source VLAN to a destination port, from a source port to a destination IP address or from a source port to a destination uplink. This feature can assist in troubleshooting or debugging network issues in the virtual infrastructure.

NetFlow is a networking protocol that collects IP traffic information as records and sends them to a collector for traffic analysis. It gives visibility into traffic between virtual machines on the same ESXi host, virtual machines on different ESXi hosts and virtual machine to physical infrastructure network traffic. NetFlow support gives an administrator the ability to monitor network traffic while assisting with network forensics, to include intrusion detection, compliance monitoring and more. This feature can help to give real insight to the virtual networking piece of the virtual infrastructure.

ABOUT THE AUTHOR
Rebecca Fitzhugh is a VMware Certified Instructor and consultant whose primary focus is on VMware virtual infrastructure products as well as the vCloud and Horizon suites. Prior to becoming an instructor and consultant, she served five years in the United States Marine Corps where she assisted in the build-out and administration of multiple enterprise networks residing on virtual infrastructure. Packt Publishing recently published her book, “vSphere Virtual Machine Management.”

This is an excerpt from the Global Knowledge white paper, VMware vSphere Distributed Switches.

Related Courses
VMware vSphere: Install, Configure, Manage [V6.0]
VMware vSphere: Optimize and Scale [V6.0]

In this article

Join the Conversation

1 comment

  1. Ed Reply

    HI Rebecca,

    You mentioned in your post that Port-mirroring sessions may be created between virtual machines on different ESXi hosts…

    How is this done? I haven’t been able to get it to work for VMs that are located on different hosts (due to the underlying nature of the vDS). Port mirroring works fine with the VMs are on the same host, but when they are on different hosts, it’s a no go.

    I work in an environment where there are a number of VMs that need to be monitored and due to the SPAN limitation, it’ causing high CPU utilization on all of the hosts because I have to put a DRS rule in place to keep all VMs on the same hosts.