VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Virtual SAN Provider network port requirements For the Virtual SAN storage providers to be visible on the vSphere client, port 8080 needs to be opened over TCP in both directions between the vCenter Server and the ESXi hosts. If there is a firewall between the ESXi hosts and vCenter Server, it will need to accommodate this requirement. Examine the security profile of any ESXi host participating in a Virtual SAN Cluster to see the provider service. It appears as vsanvp in both the incoming and outgoing connections, as shown below: 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 8 2
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Testing if port 8080 is open between vCenter and ESXi The following is a quick test to verify that port 8080, used by the Virtual SAN storage provider, is open between the vCenter server and ESXi hosts. It uses the utility telnet that is available on most Linux and Windows distributions. However, on Windows, you may have to enable it as it is turned off by default in the Windows Features. You only need the Telnet Client as shown below: Next step is to simply open a command window and telnet to the IP address of the ESXi host and provide the port as an argument, i.e. telnet 8080 If the screen goes blank, this indicates a successful connection and the host is listening on that port for connections. If nothing happens and the connection simply sits there trying to connect, then the host is not listening on that port, or there is something sitting between the vCenter and the ESXi hosts that are blocking the connection (e.g. firewall). This is a quick and simple test to ensure that the ports are open and vCenter can connect to them. 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 8 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:
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:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132: Diagnostics and Troubleshooting Ref
Page 181: Diagnostics and Troubleshooting Ref
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?