VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
vsan.lldpnetmap
If there are non-Cisco switches with Link Layer Discovery Protocol (LLDP) enabled
in the environment, there is an RVC command to display uplink switch
switch port information.
This is extremely useful for determining which hosts are attached to which switches
when the Virtual SAN Cluster is spanning multiple switches. It may help to isolate a
problem to a particular switch when only a subset of the hosts in the cluster is
impacted.
vsan.lldpnetmap 0
2013-08-15 19:34:18 -0700: This operation will take 30-60 seconds ...
+---------------+---------------------------+
| Host | LLDP info |
+---------------+---------------------------+
| 10.143.188.54 | w2r13-vsan-x650-2: vmnic7 |
| | w2r13-vsan-x650-1: vmnic5 |
+---------------+---------------------------+
This is only available with non-Cisco switches that support LLDP. For Cisco switches,
which do not support LLDP but which use their own CDP (Cisco Discovery Protocol),
there is no RVC command.
Network ports and ESXi firewall
These are the network ports used by Virtual SAN.
Name Port Protocol Traffic Type
CMMDS – Cluster Directory Service 12345, 23451 UDP Multicast
RDT – Reliable Datagram Transport 2233 TCP Unicast
VSANVP – VASA Provider 8080 TCP Unicast
VSAN Observer 8010 TCP Unicast
This is important to know in case there are firewalls between the vCenter server
and the ESXi hosts, as you will need to open port 8080 in that case for the VASA
Provider.
It is also important to know in case there are fault domains implemented, and the
ESXi hosts are located in different datacenters (although fault domains are really
designed for rack awareness in Virtual SAN 6.0). In the case where hosts are located
in different datacenters, it is important that port 2233 (for RDT) as well as ports
12345 and 23451 (for CMMDS) is opened between the data centers.
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 1 0 9