VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN Verify that everything is functioning in VSAN Observer without the need access to the Internet to download any JavaScript, CSS, or font files. If assistance is needed with launching VSAN Observer, refer to the next section of the manual. My colleague, William Lam, wrote an automated way of setting up offline mode for version 5.5 here: http://www.virtuallyghetto.com/2014/10/automate-vsanobserver-offline-mode-configurations.html. While there are some differences in 6.0, this script is still useful if you want to automate the whole process. Launching VSAN Observer VSAN Observer is launched from the RVC command line using the command vsan.observer. It needs a number of arguments supplied at the command line, and can be run in both live monitoring mode or offline/log gathering mode. Here is the list of options available in version 6.0: --filename, -f : Output file path --port, -p : Port on which to run webserver (default: 8010) --run-webserver, -r: Run a webserver to view live stats --force, -o: Apply force --keep-observation-in-memory, -k: Keep observed stats in memory even when commands ends. Allows to resume later --generate-html-bundle, -g : Generates an HTML bundle after completion. Pass a location --interval, -i : Interval (in sec) in which to collect stats (default: 60) --max-runtime, -m : Maximum number of hours to collect stats. Caps memory usage. (Default: 2) --forever, -e : Runs until stopped. Every --max-runtime intervals retires snapshot to disk. Pass a location --no-https, -n: Don't use HTTPS and don't require login. Warning: Insecure --max-diskspace-gb, -a : Maximum disk space (in GB) to use in forever mode. Deletes old data periodically (default: 5) --help, -h: Show this message To enable live monitoring for a cluster, run the following command. Note that the cluster in this example is called Virtual SAN. vsan.observer ~/computers/Virtual SAN –-run-webserver –-force On a web browser, you can now navigate to the vCenter Server hostname or IP Address and add the port number specified in the output from the previous step. By default the port used by Virtual SAN is 8010. https://vCenterServer_hostname_or_IP_Address:8010 This will bring you initially to the login page. Provide privileged credentials to login: 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 0 2
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Note that in the vSphere 5.5U1 version of VSAN Observer, there was no login page, and http rather than https was used to access the tool. With the 5.5U2 release, the login page was introduced and https is used by default to access the VSAN Observer web browser. Launching VSAN Observer with a non-default port If port 8010 is already in use, or you wish to use a different port for VSAN observer, this procedure will show you how. Keep in mind is that the port that is chosen instead may not be open in the firewall. When RVC is installed on vCenter Server, it automatically adds a firewall rule to open port 8010. But if you wish to use a different port, you will have to create your own firewall rule. Here is an example of creating such a rule on the vCenter Server Appliance. Note that this does not persist through a reboot. Note that initially there is no rule for port 8011: # iptables –list-rules -A port_filter –p tcp –m tcp –dport 22 –j ACCEPT -A port_filter –p tcp –m tcp –dport 902 –j ACCEPT -A port_filter –p udp –m udp –dport 902 –j ACCEPT -A port_filter –p tcp –m tcp –dport 9443 –j ACCEPT -A port_filter –p tcp –m tcp –dport 88 –j ACCEPT -A port_filter –p udp –m udp –dport 88 –j ACCEPT -A port_filter –p tcp –m tcp –dport 2012 –j ACCEPT -A port_filter –p tcp –m tcp –dport 2020 –j ACCEPT -A port_filter –p tcp –m tcp –dport 7444 –j ACCEPT -A port_filter –p udp –m udp –dport 6500 –j ACCEPT -A port_filter –p tcp –m tcp –dport 2014 –j ACCEPT -A port_filter –p tcp –m tcp –dport 514 –j ACCEPT -A port_filter –p udp –m udp –dport 514 –j ACCEPT -A port_filter –p tcp –m tcp –dport 1514 –j ACCEPT -A port_filter –p tcp –m tcp –dport 6501 –j ACCEPT -A port_filter –p tcp –m tcp –dport 6502 –j ACCEPT -A port_filter –p tcp –m tcp –dport 8010 –j ACCEPT -A port_filter –p tcp –m tcp –dport 80 –j ACCEPT -A port_filter –p tcp –m tcp –dport 443 –j ACCEPT # 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 0 3
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: Diagnostics and Troubleshooting Ref
Page 201: Diagnostics and Troubleshooting Ref
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?