VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN VSAN Observer command line options --filename -f --port -p --run-webserver -r --force -o --keep-observation-in-memory -k --generate-html-bundle -g --interval -i --max-runtime -m Output file path, for example, /tmp Port number for live statistics. Note: The default port is 8010. Run the live statistics. Apply force. Keep observed statistics in memory even when commands ends. This command allows you to resume later. Generates an HTML bundle after completion. Pass a location. Interval value (in seconds) in which to collect statistics. Note: The default value is 60. Maximum number of hours to collect statistics. This command caps memory usage. Note: The default value is 2. 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 4 2
Diagnostics and Troubleshooting Reference Manual – Virtual SAN 16. Troubleshooting Virtual SAN performance As highlighted in the introduction, VMware recommends using the Virtual SAN Health Services to do initial triage of performance issues. The Virtual SAN Health Services carry out a range of health checks, and may detect issues that can directly impact performance. The Health Services directs administrators to an appropriate knowledge base article depending on the results of the health check. The knowledge base article will provide administrators with step-by-step instruction to solve the problem at hand. Please refer to the Virtual SAN Health Services Guide for further details on how to get the Health Services components, how to install them and how to use the feature for troubleshooting common Virtual SAN issues. Virtual SAN performance expectations Virtual SAN is a fully distributed, scale-out storage system, designed to support the aggregate needs of multiple VMs in a cluster. As such, performance profiles can be different than what is frequently seen with traditional monolithic storage arrays. Virtual SAN is designed to maximize the number of application IOPS in a cluster, while minimizing CPU and memory consumption. As such, it uses a very different design point from arrays that have dedicated CPU and memory. While testing a single application in a VSAN cluster may be reasonable, a full performance picture will not emerge until multiple applications across the cluster are tested. As there is wide variability in supported VSAN configurations (flash devices such as SSDs, IO controllers, magnetic disks for hybrid configurations, etc.) and application workloads (cluster size, working set, read/write mix, IO size) the best advice is to test a proposed production configuration with a workload that is as close to expected as possible. I/O flow In order to successfully troubleshooting performance issues, a certain level of understanding of Virtual SAN internals is required. The intention is not to take a deep-dive into the all of the internal workings of Virtual SAN, but instead give you an appreciation of some of the basic operations. Let’s start with I/O flow. 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 4 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:
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: Diagnostics and Troubleshooting Ref
Page 241: Diagnostics and Troubleshooting Ref
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?