VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Troubleshooting a multicast configuration issue As mentioned, a common issue is that the Virtual SAN Cluster is configured across multiple physical switches, and while multicast has been enabled on one switch, it has not been enabled across switches. In this case, the cluster forms with two ESXi hosts in one partition, and another ESXi host (connected to the other switch) is unable to join this cluster. Instead it forms its own Virtual SAN cluster in another partition. Remember that the vsan.lldpnetmap command seen earlier can assist in determining network configuration, and which hosts are attached to which switch. Symptoms of a multicast misconfiguration issue Other than the fact that the Virtual SAN Cluster status displays a network misconfiguration issue, there are some other telltale signs when trying to form a Virtual SAN Cluster that multicast may be the issue. Assume at this point that the checklist for subnet, VLAN, MTU has been followed and each host in the cluster can vmkping every other host in the cluster. If there is get a network misconfiguration detected when the cluster is formed, the next symptom you will observe is that each ESXi host forms its own Virtual SAN cluster, with itself as the master. It will also have a unique network partition id. This symptom suggests that there is no multicast between any of the hosts. However if there is a situation where a subset of the ESXi hosts form a cluster, and another subset form another cluster, and each have unique partitions with their own master, backup and perhaps even agent nodes, this may very well be a situation where multicast is enabled in-switch, but not across switches. In situations like this, Virtual SAN shows hosts on the first physical switch forming their own cluster partition, and hosts on the second physical switch forming their own cluster partition too, each with its own “master”. If you can verify which switches the hosts in the cluster connect to, and hosts in a cluster are connected to the same switch, then this may well be the issue. 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 1 6
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Troubleshooting a MTU/jumbo frames mismatch An MTU mismatch can be hard to locate. In Virtual SAN, the cluster will not report any misconfiguration issue if only jumbo frames are misconfigured. That is because the packets used to check that the cluster is working from a network perspective do not utilize jumbo frames to do their checks. In fact, Virtual SAN simply sends a heartbeat, the size of which depends on the number of hosts in the cluster. This means that the heartbeat may be much less than 1500 MTU. Therefore, a situation may arise where the cluster reports that network status is normal, but any attempt to deploy a virtual machine on Virtual SAN will fail. The check that the MTU size is set correctly, use the following ESXCLI commands: esxcli network ip interface list ~ # esxcli network ip interface list vmk0 vmk1 vmk2 vmk2 Name: vmk2 MAC Address: 00:50:56:61:3d:e1 Enabled: true Portset: DvsPortset-1 Portgroup: N/A Netstack Instance: defaultTcpipStack VDS Name: ie-vds-04 VDS UUID: 83 d4 3e 50 ae 27 78 5d-1d 27 2d ff 5a 34 64 85 VDS Port: 18 VDS Connection: 1525799189 Opaque Network ID: N/A Opaque Network Type: N/A External ID: N/A MTU: 1500 TSO MSS: 65535 Port ID: 50331661 Here is how to check the MTU setting on a standard switch: esxcli network vswitch standard list ~ # esxcli network vswitch standard list vSwitch0 Name: vSwitch0 Class: etherswitch Num Ports: 4352 Used Ports: 4 Configured Ports: 128 MTU: 1500 CDP Status: listen Beacon Enabled: false Beacon Interval: 1 Beacon Threshold: 3 Beacon Required By: Uplinks: vmnic0 Portgroups: VM Network, Management Network 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 1 7
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:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66: Diagnostics and Troubleshooting Ref
Page 115: Diagnostics and Troubleshooting Ref
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?