VSAN-Troubleshooting-Reference-Manual

Recommendations

Info

Diagnostics and Troubleshooting Reference Manual – Virtual SAN VSAN Disks (deep-dive) – Device level stats: PhysDisk One final additional set of graphs available in the VSAN Disks (deep-dive) views is the PhysDisk charts. This view is giving physical disk statistics, and you might have guessed from the name of the graphs. IOPS and Tput (throughput) should be well understood at this stage. Both reads and writes are shown separately. DiskLatency (ms) DAVG – This is the average response time (latency) in milliseconds per command being sent to the device KAVG – This is the amount of time the command spends in the VMkernel. GAVG – This is the response time, as it is perceived by the guest operating system. This is calculated with the formula: DAVG + KAVG = GAVG RDLAT – Read Latency WRLAT – Write Latency 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 2 6
Diagnostics and Troubleshooting Reference Manual – Virtual SAN Navigating VSAN Observer – PCPU The PCPU tab shows overall CPU usage and also per component CPU usage statistics of Virtual SAN. This view shows CPU usage from an overall host perspective, as well as specifically from the view of Virtual SAN wordlets and networking worldlets. A worldlet can be considered a process that does some work on behalf of Virtual SAN. A single worldlet can at most occupy a single physical CPU core. The 100% mark in the graphs refers to a percentage of that limit. If the utilization of a Virtual SAN worldlet is getting close to 100% then CPU is likely a bottleneck for Virtual SAN performance. However, even when the utilization is not yet maxed out, a significant utilization (>10%) of readyTime indicates CPU contention between Virtual SAN and other uses of physical CPUs on the host (e.g. running VMs). Looking at overall CPU consumption of the host should confirm this picture. Some of the graphs visible on this view are: Client – amount of CPU consumed by client worldlets; client is the component which accesses an object on behalf of a VM. CompServer – amount of CPU consumed by component server worldlets. This provides the network front-end for accessing an object. Owner – amount of CPU consumed by owner worldlets. The owner is the storage head and co-ordinates that can do I/O to an object. Owner communicates to the component manager to access a leaf on the object’s RAID tree. LSOMLOG – amount of CPU consumed by LSOMLOG worldlets. PLOG – amount of CPU consumed by PLOG worldlets 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 2 7
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: Diagnostics and Troubleshooting Ref
Page 225: Diagnostics and Troubleshooting Ref
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?