VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN vmkping The vmkping is a simple command that will verify if all of the other ESXi hosts on the network are responding to your ping requests. The command and output are identical on both ESXi 5.5 and 6.0. ~ # vmkping -I vmk2 172.32.0.3 PING 172.32.0.3 (172.32.0.3): 56 data bytes 64 bytes from 172.32.0.3: icmp_seq=0 ttl=64 time=0.186 ms 64 bytes from 172.32.0.3: icmp_seq=1 ttl=64 time=2.690 ms 64 bytes from 172.32.0.3: icmp_seq=2 ttl=64 time=0.139 ms --- 172.32.0.3 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.139/1.005/2.690 ms While it does not verify multicast functionality, it can help with isolating a rogue ESXi host that has network issues. You can also examine the response times to see if there is any abnormal latency on the Virtual SAN network. One thing to note – if jumbo frames are configured, this command will not find any issues if the jumbo frame MTU size is incorrect. This command by default uses an MTU size of 1500. If there is a need to verify if jumbo frames are successfully working end-to-end, use vmkping with a larger packet size option as follows: ~ # vmkping -I vmk2 172.32.0.3 -s 9000 PING 172.32.0.3 (172.32.0.3): 9000 data bytes 9008 bytes from 172.32.0.3: icmp_seq=0 ttl=64 time=0.554 ms 9008 bytes from 172.32.0.3: icmp_seq=1 ttl=64 time=0.638 ms 9008 bytes from 172.32.0.3: icmp_seq=2 ttl=64 time=0.533 ms --- 172.32.0.3 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.533/0.575/0.638 ms ~ # Consider adding -d to the vmkping command to test if packets can be sent without fragmentation. vsan.cluster_info Of course the difficulty with using many of the above commands is that they need to be run on a per ESXi node basis. There are some commands in RVC to help get a more cluster centric view of the network configuration. One of these is vsan.cluster_info. /localhost/ie-datacenter-01/computers> vsan.cluster_info 0 Host: cs-ie-h01.ie.local Product: VMware ESXi 6.0.0 build-2305723 VSAN enabled: yes Cluster info: Cluster role: backup Cluster UUID: 529ccbe4-81d2-89bc-7a70-a9c69bd23a19 Node UUID: 545ca9af-ff4b-fc84-dcee-001f29595f9f Member UUIDs: ["54188e3a-84fd-9a38-23ba-001b21168828", "545ca9af-ff4b-fc84-dcee-001f29595f9f", "5460b129-4084-7550-46e1-0010185def78", "54196e13-7f5f-cba8-5bac-001517a69c72"] (4) Node evacuated: no Storage info: Auto claim: no Checksum enforced: no 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 4
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Disk Mappings: SSD: HP Serial Attached SCSI Disk (naa.600508b1001c61cedd42b0c3fbf55132) - 186 GB, v1 MD: HP Serial Attached SCSI Disk (naa.600508b1001c16be6e256767284eaf88) - 136 GB, v1 MD: HP Serial Attached SCSI Disk (naa.600508b1001c64816271482a56a48c3c) - 136 GB, v1 MD: HP Serial Attached SCSI Disk (naa.600508b1001c388c92e817e43fcd5237) - 136 GB, v1 MD: HP Serial Attached SCSI Disk (naa.600508b1001ccd5d506e7ed19c40a64c) - 136 GB, v1 MD: HP Serial Attached SCSI Disk (naa.600508b1001c79748e8465571b6f4a46) - 136 GB, v1 MD: HP Serial Attached SCSI Disk (naa.600508b1001c2ee9a6446e708105054b) - 136 GB, v1 MD: HP Serial Attached SCSI Disk (naa.600508b1001c3ea7838c0436dbe6d7a2) - 136 GB, v1 FaultDomainInfo: Not configured NetworkInfo: Adapter: vmk2 (172.32.0.1) The last piece of information from this command is the network information, which tells you the VMkernel adapter and the IP address. This single command displays this information for every host in the Virtual SAN cluster. esxcli network ip neighbor list Switching back to ESXCLI, this next command is a very quick way of checking to see if all Virtual SAN hosts are actually on the same network segment. In this configuration, we have a 4-node cluster, and this command returns the ARP (Address Resolution Protocol) entries of the other 3 nodes, including their IP addresses and their vmknic (Virtual SAN is configured to use vmk2 on all hosts in this cluster). The command and output are identical in ESXi 5.5 and 6.0. ~ # esxcli network ip neighbor list -i vmk2 Neighbor Mac Address Vmknic Expiry State Type ---------- ----------------- ------ -------- ----- ------- 172.32.0.1 00:50:56:68:63:fa vmk2 1081 sec Unknown 172.32.0.2 00:50:56:6d:cb:3b vmk2 1081 sec Unknown 172.32.0.3 00:50:56:6c:45:63 vmk2 1081 sec Unknown ~ # esxcli network diag ping To get even more detail regarding the Virtual SAN network connectivity between the various hosts, ESXCLI provides a powerful network diagnostic command in both ESXi 5.5 & 6.0. This command checks for duplicates on the network, as well as round trip times. Here is an example of one such output, where the VMkernel interface is on vmk2 and the remote Virtual SAN network IP of another host on the network is 172.32.0.3: ~ # esxcli network diag ping -I vmk2 -H 172.32.0.3 Summary: Duplicated: 0 Host Addr: 172.32.0.3 Packet Lost: 0 Recieved: 3 Roundtrip Avg MS: 263 Roundtrip Max MS: 371 Roundtrip Min MS: 185 Transmitted: 3 Trace: Detail: Dup: false 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 5
Page 1 and 2:
Diagnostics and Troubleshooting Gui
Page 3 and 4:
Diagnostics and Troubleshooting Ref
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54: Diagnostics and Troubleshooting Ref
Page 103: Diagnostics and Troubleshooting Ref
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295:
show all

VSAN-Troubleshooting-Reference-Manual

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?