VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Upgrade path when not enough resources in the cluster A common question is what is the recommended upgrade path for customers who have overcommitted and do not have enough free space to do a full evacuation, for example 3 node clusters? The vsan.v2_ondisk_upgrade has an option called allow-reduced-redundancy. It should be noted that there are risks associated with this approach but unfortunately there is no other way to do the upgrade. For a portion of the upgrade, virtual machines will be running without replica copies of the data, so any failure during the upgrade can lead to virtual machine downtime. When this option is used, the upgrade deletes and creating disk groups one at a time, on each host, and then allows the components rebuild once the on-disk format is at v2. When the operation has completed on the first host, it is repeat for the next host and so on until all hosts in the cluster are running on-disk format v2. However administrators need to be aware that their virtual machines could be running unprotected for a period during this upgrade. 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 7 8
Diagnostics and Troubleshooting Reference Manual – Virtual SAN 13. Troubleshooting the VASA Provider Introduction to VASA Provider VASA is shorthand for vSphere Storage APIs for Storage Awareness. It was initially designed to allow storage arrays to integrate with vCenter for management functionality via server-side plug-ins called a storage providers (or vendor provider). In the case of Virtual SAN, the storage provider is placed on the ESXi host. Initially the storage capabilities handled by VASA in vSphere 5.0 were very simplistic. There was a single capability associated with a LUN/datastore. In Virtual SAN, there are multiple capabilities associated with the Virtual SAN datastore. The storage provider is responsible for surfacing up a set of predefined capabilities. In the case of Virtual SAN, each ESXi host can provide this information. In Virtual SAN, a subset of capabilities around availability, provisioning and performance are surfaced up to vCenter Server. The capabilities can be viewed in various places in the vSphere web client, including on the Virtual SAN datastore view. The storage provider, one on each ESXi host participating in the Virtual SAN Cluster, provide out-of-band information about the underlying storage system, in this case Virtual SAN. If there isn’t at least one of these providers on the ESXi hosts communicating to the SMS (Storage Monitoring Service) on vCenter Server, then vCenter will not be able to display any of the capabilities of the Virtual SAN datastore, which means that administrators will be unable to build any further storage policies for virtual machine deployments However, VMs already deployed using VM Storage Policies are unaffected if the storage provider has issues. To verify that the storage provider is online, navigate to the vCenter server, select the Manage tab, and then select the storage provider. The Status should show Online and the Active/Standby state should show one Virtual SAN Provider as Active. In the case of a host failure, a standby storage provide will assume the active state to enable the continuous surfacing up of the storage capabilities to vCenter. The following screenshot shows a Virtual SAN cluster with 3 ESXi hosts. All hosts have a storage provider, but only one is active. The other two are in standby. Should the host that currently has the online storage provider fail, another host will bring its provider online. 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 7 9
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: Diagnostics and Troubleshooting Ref
Page 177: Diagnostics and Troubleshooting Ref
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?