VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Known issue with VASA Providers in version 5.5 There was an issue with VASA storage providers disconnecting from vCenter Server, resulting in no Virtual SAN capabilities being visible when you try to create a VM Storage Policy. Even a resynchronization operation fails to reconnect the storage providers to vCenter. This seems to be predominantly related to vCenter servers which were upgraded to vCenter 5.5U1 and not newly installed vCenter servers. The symptoms are described in the vCenter 5.5 U1b release notes as follows: Under certain conditions, Virtual SAN storage providers might not be created automatically after you enable Virtual SAN on a cluster When you enable Virtual SAN on a cluster, Virtual SAN might fail to automatically configure and register storage providers for the hosts in the cluster, even after you perform a resynchronization operation. vCenter 5.5 U1b, released in June 2014, resolves the issue. If the Virtual SAN storage providers become disconnected, with the latest releases of Virtual SAN one simply needs to do a resynchronization operation. To resynchronize, click the synchronize icon in the Storage Providers tab, found under vCenter Servers > vCenter > Manage, 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 4
Diagnostics and Troubleshooting Reference Manual – Virtual SAN 14. vCenter Server & Cluster Considerations This chapter is designed to cover some additional considerations related to the cluster in general, as well as vCenter server. As highlighted in the introduction, VMware recommends using the Virtual SAN Health Services to do initial triage of cluster issues. The Virtual SAN Health Services carry out a range of cluster health checks, such as verifying that all hosts that are part of the vSphere cluster are part of the VSAN cluster, and vice-versa. The Health Services directs administrators to an appropriate knowledge base article depending on the results of the health check. The knowledge base article will provide administrators with step-by-step instruction to solve the cluster problem at hand. Please refer to the Virtual SAN Health Services Guide for further details on how to get the Health Services components, how to install them and how to use the feature for troubleshooting common Virtual SAN issues. Alarms and Events Virtual SAN 6.0 has some built in default alarms. However Virtual SAN 5.5 does not have any such mechanism enabled by default and requires customers to create their own alarms based on VMkernel Observations (VOBs). Triggering Alarms based on Virtual SAN VOBs vCenter Server 5.5 does not contain any prepopulated alarms for Virtual SAN 5.5. In Virtual SAN 6.0, only a small number of alarms are prepopulated. The VMware ESXi Observation Log (VOBD) does contain system events (termed “observations”) observed by the VMkernel, many of which are Virtual SAN specific. By leveraging VOBs, one can quickly and easily create vCenter Alert mechanisms for Virtual SAN implementations. VOB IDs for Virtual SAN This is a list of VOB IDs for Virtual SAN in version 5.5. VMkernel Observation ID esx.audit.vsan.clustering.enabled esx.clear.vob.vsan.pdl.online esx.clear.vsan.clustering.enabled esx.clear.vsan.vsan.network.available Descriptions Virtual SAN clustering service had been enabled Virtual SAN device has come online. Virtual SAN clustering services have now been enabled. Virtual SAN now has at least one active network configuration. 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 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:
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:
Page 133 and 134: Diagnostics and Troubleshooting Ref
Page 183: Diagnostics and Troubleshooting Ref
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?