VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Keep in mind that ESXCLI can only communicate with one host or ESXi instance at a time. To look at cluster wide information, the Ruby vSphere Console (RVC) should be used. There are lots of ways to display similar information using the ESXCLI. In this reference manual, the focus will be on the best one or two ways to get the information. Ruby vSphere Console - RVC Ruby vSphere Console is a Ruby-based expandable management platform from which you can utilize any API vCenter exposes. It can simply be described as a command-line console UI for VMware ESXi hosts and VMware vCenter Server. The vSphere inventory is presented as a virtual filesystem, allowing you to navigate and run commands against managed entities using familiar shell syntax, such as “cd” to change directory and “ls” to list directory (inventory) contents. RVC has been extended to provide a wealth of useful information about Virtual SAN health and status. RVC is included in both the Windows and Linux versions of vCenter Server since 5.5U1. VSAN Observer VSAN Observer is a monitoring and troubleshooting tool that is available with RVC, and enables analysis of a Virtual SAN Cluster. VSAN Observer is launched from RVC. Its captures low-level metrics from Virtual SAN and presents them in a format that is easily consumable via a web browser. It is a tool that is typically deployed to assist with monitoring and troubleshooting Virtual SAN issues. It monitors Virtual SAN in real-time. Virtual SAN can be examined either from the perspective of physical resources (CPU, Memory, disks) with a wealth of different metrics. It can also be monitored from a virtual machine perspective, allowing resources consumed by the virtual machine to be examined, and whether or not a virtual machine contends with other virtual machines for resources, etc. Two key points here: - VSAN Observer is used for performance troubleshooting - VSAN Observer is built on RVC 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 / 16
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Third party tools As Virtual SAN uses third-party storage I/O controllers and flash devices, it may be necessary to use specific tools provided by these vendors to configure and check status. Using these tools, e.g. MegaCLI from LSI or the hpssacli extension to ESXCLI from HP, you can check the status of the storage controller as well as the disk devices attached to the controller. You can also verify that the cache is configured properly on the controller (e.g. disabled, or set to 100% read, in both cases disabling write cache). You may also find that you PCI-E flash device vendor also supplied tools for checking configuration and status. For example, FusionIO/SanDisk is one vendor that provides such a set of tools. We will look at how to use these tools in various places in this reference manual. Troubleshooting tools summary With this set of tools at your disposal, you should be in a position to monitor, diagnose and troubleshoot Virtual SAN. The vSphere Web Client and ESXCLI commands are covered in the official vSphere documentation, and only the commands relevant to Virtual SAN are covered in this reference manual. The complete official vSphere documentation can be found at the following link: https://www.vmware.com/support/pubs/. This reference manual will focus on all aspects of RVC and VSAN Observer, with a goal of getting the reader to a point where they can confidently troubleshoot Virtual SAN issues. The combination of the vSphere Web Client, ESXCLI, RVC and VSAN Observer represent a very complete and powerful toolset to fully observe the inner workings of Virtual SAN. The remainder of this reference manual will focus on how to use these tools to diagnose and troubleshoot Virtual SAN environments. 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 / 17
Page 1 and 2: Diagnostics and Troubleshooting Gui
Page 3 and 4: Diagnostics and Troubleshooting Ref
Page 15: Diagnostics and Troubleshooting Ref
Page 67 and 68:
Diagnostics and Troubleshooting Ref
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:
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

Create successful ePaper yourself

Delete template?

Save as template?