VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Checking the Virtual SAN network is operational When the Virtual SAN network has been configured, these commands will check its state. Using the following ESXCLI commands, an administrator can check which VMkernel Adapter is used for Virtual SAN, and what attributes it contains. First, various ESXCLI and RVC commands verify that the network is indeed fully functional. Then various ESXCLI and RVC commands demonstrate to an administrator how to troubleshoot any network related issues with Virtual SAN. This will involve verifying that the vmknic used for the Virtual SAN network is uniformly configured correctly across all hosts, checking that multicast is functional and verifying that each host participating in the Virtual SAN cluster can successfully communicate to one another. esxcli vsan network list This is a very useful command as it tells you which VMkernel interface is being used for the Virtual SAN network. In the output below (command and output identical in ESXi 5.5 and 6.0), we see that the Virtual SAN network is using vmk2. This command continues to work even if Virtual SAN has been disabled on the cluster and the hosts no longer participate in Virtual SAN. There are some additional useful pieces of information such as Agent Group Multicast and Master Group Multicast. ~ # esxcli vsan network list Interface VmkNic Name: vmk2 IP Protocol: IPv4 Interface UUID: ccf01954-68f4-3e5f-cb3a-001b21168828 Agent Group Multicast Address: 224.2.3.4 Agent Group Multicast Port: 23451 Master Group Multicast Address: 224.1.2.3 Master Group Multicast Port: 12345 Multicast TTL: 5 This provides useful information such as which VMkernel interface is being used for Virtual SAN traffic. In this case it is vmk2. However, also shown are the multicast addresses. There is the group multicast address and port. Port 23451 is used for the heartbeat, sent every second by the master, and should be visible on every other host in the cluster. Port 12345 is used for the CMMDS updates between the master and backup. Once we know which VMkernel port Virtual SAN is using for network traffic, we can use some additional commands to check on its status. 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 2
Diagnostics and Troubleshooting Reference Manual – Virtual SAN esxcli network ip interface list Now that we know the VMkernel adapter, we can use this command to check items like which vSwitch or distributed switch that it is attached to, as well as the MTU size, which can be useful if jumbo frames have been configured in the environment. In this case, MTU is at the default of 1500. ~ # esxcli network ip interface list vmk0 vmk1 vmk2 Name: vmk2 MAC Address: 00:50:56:61:3d:e1 Enabled: true Portset: DvsPortset-0 Portgroup: N/A Netstack Instance: defaultTcpipStack VDS Name: vds01 VDS UUID: e6 98 23 50 11 e3 dd 59-e9 8c a6 99 bb 0b 2f c8 VDS Port: 1308 VDS Connection: 1384090857 MTU: 1500 TSO MSS: 65535 Port ID: 50331661 ~ # This output is almost the same on ESXi 5.5 and 6.0, although 6.0 does include some additional “Opaque Network” information. The Maximum Transmission Unit size is shown as 1500, so this VMkernel port is not configured for jumbo frames, which require an MTU of somewhere in the region on 9,000. VMware does not make any recommendation around the use of jumbo frames. Testing to date has revealed no noticeable improvement in Virtual SAN performance by using jumbo frames. However, jumbo frames are supported for use with Virtual SAN should there be a requirement to use them. esxcli network ip interface ipv4 get –i vmk2 This is another useful command as it displays information such as IP address and netmask of the VMkernel interface used for Virtual SAN. The command and output are identical between ESXi 5.5 and 6.0. With this information, an administrator can now begin to use other commands available at the command line to check that the Virtual SAN network is working correctly. ~ # esxcli network ip interface ipv4 get -i vmk2 Name IPv4 Address IPv4 Netmask IPv4 Broadcast Address Type DHCP DNS ---- ------------ ------------- -------------- ------------ -------- vmk2 172.32.0.4 255.255.255.0 172.32.0.255 STATIC 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 3
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: Diagnostics and Troubleshooting Ref
Page 101: Diagnostics and Troubleshooting Ref
Page 153 and 154:
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

Create successful ePaper yourself

Delete template?

Save as template?