VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN VCG check summary There are obviously quite a few tasks to do to bring the configuration that was used as an example up to a supported state. Hosts that appear in the server section of the VCG, e.g. HP DL380 G7, don’t necessarily mean that they are supported for Virtual SAN. HP DL380 G7 hosts do not support any of the controllers necessary to run Virtual SAN. G8 servers would be required from HP to support Virtual SAN. Ensure that the controller is supported. The HP 410i controllers in this example will need to be replaced with a different model that appears on the VCG at the time of writing, perhaps a HP 420i. Ensure that the controller used is configured with a supported mode, either pass-through or RAID-0. This should be done at deployment, as changing to a new mode may involve an ESXi reinstall. Ensure that the driver is supported for Virtual SAN. The async driver that is installed as part of the HP customized ISO is also not supported at the time that this research was done, so this will need to be changed for a supported inbox driver. Ensure that the flash device or SSD is supported. The Fusion-IO PCI-E card is on the VCG but while the driver is running a supported version, the firmware will need to be upgraded to make it supportable. Using tools from third party vendors can help to quickly retrieve driver and firmware information about the third party’s product When choosing flash devices for cache, consider both performance (writes per second) and endurance (TBW/DWPD) characteristics of the drives. When choosing flash devices for capacity in all-flash configuration, consider the endurance characteristics of the drives. These devices do not need to be as high performing as the flash devices used at the cache layer. When choosing magnetic disks for hybrid configurations, consider performance characteristics (RPM) of the drives. These are exactly the sorts of checks that would need to be made against the VCG to verify that you have a configuration that supports Virtual SAN. 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 / 50
Diagnostics and Troubleshooting Reference Manual – Virtual SAN 5. Virtual SAN software components This section aims to provide a brief overview of some of the Virtual SAN software components. Many of these components are not necessary to understand for day-today use of Virtual SAN. However when it comes to troubleshooting, you may see them referenced from time to time in logs, RVC commands and especially VSAN Observer outputs. Therefore, for completeness sake, a brief overview is provided. Local Log Structured Object Management - LSOM LSOM works at the physical disk level, both flash devices and magnetic disks. It handles the physical storage for Virtual SAN components on the local disks of the ESXi hosts. It also handles the read caching and write buffering for the components. Distributed Object Manager - DOM DOM is responsible for the creation of virtual machine storage objects from local components across multiple ESXi hosts in the Virtual SAN cluster by implementing distributed RAID. It is also responsible for providing distributed data access paths to these objects. There are 3 roles within DOM; client, owner and component manager. Client: Provides access to an object. There may be multiple clients per object depending on access mode. Owner: Coordinates access to the object, including locking and object configuration and reconfiguration. There is a single DOM owner per object. All objects changes and writes go through the owner. Typically the client and owner will reside on the same host, but this is not guaranteed and they may reside on different hosts. Component Manager: Interface for LSOM and the physical disks. A node’s DOM may play any of the three roles for a single object Cluster Level Object Manager - CLOM CLOM ensures that an object has a configuration that matches its policy, i.e. stripe width or failures to tolerate, to meet the requirements of the virtual machine. Each ESXi host in a Virtual SAN cluster runs an instance of clomd, which is responsible for the policy compliance of the objects. CLOM can be thought of as being responsible for the placement of objects and their components. 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 / 51
Page 1 and 2: Diagnostics and Troubleshooting Gui
Page 3 and 4: Diagnostics and Troubleshooting Ref
Page 49: Diagnostics and Troubleshooting Ref
Page 101 and 102:
Diagnostics and Troubleshooting Ref
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:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?