VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Filing a support request with VMware To file a support request with VMware, the following knowledge base article provides instructions on how to do so: http://kb.vmware.com/kb/2006985 Which logs should be gathered? VMware’s technical support engineers will look for a certain set of files in order to be able to investigate your issue. This knowledgebase articles gives details on which logs to gather: http://kb.vmware.com/kb/2072796 Since Virtual SAN comprises of multiple ESXi hosts, you will need to capture vmsupport output from all ESXi hosts in the cluster. Certain Virtual SAN logs are captured as trace files by the vm-support scripts. The utility vsanTraceReader is also included in the vm-support, which allows the trace files to be read. You will find it in /usr/lib/vmware/vsan/bin/vsanTraceReader. To dump a VSAN trace into a human readable format, you can use a command similar to the following: /usr/lib/vmware/vsan/bin/vsanTraceReader vsantraces--2014-12-04T03h07m38s822.gz > trace However note that this information is only useful to VMware’s support organization. Also considering capturing vCenter Server logs via vc-support. These will be critical for examining Storage Policy Based Management (SPBM) type issues and also Virtual SAN storage provider (VASA) registration issues. Finally, we may need to capture some RVC command outputs from your RVC server (typically your vCenter server). Here is a useful RVC command to capture the vsan.support_information to a file: /usr/bin/rvc -c "vsan.support_information 1" -c "quit" administrator@vsphere.local:password@hostname > log_location If the host and password are not provided on the command line, you will be prompted for it. VMware KB Article 2064240 provides useful VSAN Observer log gathering information. How to transfer log files to VMware? Once the log bundles have been generated, they need to be sent to VMware Technical Support. The following KB article provides a variety of ways of getting the logs to VMware: http://kb.vmware.com/kb/1008525 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 / 2 7 4
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Appendix A: Useful HP Utilities hpssacli utility While this utility does not come by default on ESXi hosts, it does come pre-bundled if you deploy your ESXi hosts with the ESXi 5.5 U2 HP OEM image that contains, among other things, the hpssacli utility. This tool can be extremely useful for monitoring and troubleshooting issues with your HP storage controller and disk devices. While this appendix is not all-inclusive, it does contain some very useful commands that a Virtual SAN and vSphere administrator could leverage. For a complete list of commands and their usage, please refer to the official HP documentation on the topic: http://h10032.www1.hp.com/ctg/Manual/c04123772.pdf Let’s begin by checking to see if the appropriate software is installed. Here is a list of all HP VIBs that come pre-installed on their OEM image: ~ # esxcli software vib list | grep -i Hewlett char-hpcru 5.5.6.6-1OEM.550.0.0.1198610 Hewlett-Packard PartnerSupported 2014-09-16 char-hpilo 550.9.0.2.3-1OEM.550.0.0.1198610 Hewlett-Packard PartnerSupported 2014-09-16 hp-ams 550.10.0.0-18.1198610 Hewlett-Packard PartnerSupported 2014-09-16 hp-build 5.76.36-1198610 Hewlett-Packard PartnerSupported 2014-09-16 hp-conrep 5.5.0.1-0.0.7.1198610 Hewlett-Packard PartnerSupported 2014-09-16 hp-esxi-fc-enablement 550.2.1.8-1198610 Hewlett-Packard PartnerSupported 2014-09-16 hp-smx-provider 550.03.06.00.23-1198610 Hewlett-Packard VMwareAccepted 2014-09-16 hpbootcfg 5.5.0.02-00.00.11.1198610 Hewlett-Packard PartnerSupported 2014-09-16 hpnmi 550.2.3.5-1198610 Hewlett-Packard PartnerSupported 2014-09-16 hponcfg 5.5.0.4.4-0.3.1198610 Hewlett-Packard PartnerSupported 2014-09-16 hpssacli 2.0.23.0-5.5.0.1198610 Hewlett-Packard PartnerSupported 2014-09-16 hptestevent 5.5.0.01-00.01.4.1198610 Hewlett-Packard PartnerSupported 2014-09-16 scsi-hpdsa 5.5.0.12-1OEM.550.0.0.1331820 Hewlett-Packard PartnerSupported 2014-09-16 scsi-hpsa 5.5.0.74-1OEM.550.0.0.1331820 Hewlett-Packard VMwareCertified 2014-09-16 scsi-hpvsa 5.5.0-88OEM.550.0.0.1331820 Hewlett-Packard PartnerSupported 2014-09-16 So there are quite a few VIBs installed as one can clearly see. The VIBs that we are interested in are the ones that add additional namespaces to ESXCLI on the ESXi hosts. By simply running the esxcli command, we can see some new namespaces that we would typically not find on an ESXi host built from the standard VMware images. 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 / 2 7 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:
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: Diagnostics and Troubleshooting Ref
Page 273: Diagnostics and Troubleshooting Ref
Page 295: Diagnostics and Troubleshooting Ref
show all

VSAN-Troubleshooting-Reference-Manual

Create successful ePaper yourself

Delete template?

Save as template?