VMware 4817V62 Administration Guide - Page 69

Collecting Log Files, Set Verbose Logging, Collect vSphere Log Files - 5 1 client download

Page 69 highlights

Chapter 5 Configuring Hosts and vCenter Server Procedure 1 From the vSphere Client connected to a vCenter Server system or ESX/ESXi host, select Administration > Export Diagnostic Data. 2 If the vSphere Client is connected to a vCenter Server system, specify the host whose logs you want to export and the location for storing the log files. 3 If the vSphere Client is connected to an ESX/ESXi host, specify the location for the log files. 4 Click OK. Collecting Log Files VMware technical support might request several files to help resolve technical issues. The following sections describe script processes for generating and collecting some of these files. Set Verbose Logging You can specify how verbose log files will be. Procedure 1 Select Administration > vCenter Server Settings. 2 Select Logging Options. 3 Select Verbose from the pop-up menu. 4 Click OK. Collect vSphere Log Files You can collect vSphere log files into a single location. Select from the options: Procedure n To view the viclient-*.log files, change to the directory, %temp%. n If you are running the vSphere Client connected to a vCenter Server system, download the log bundle. The log bundle is generated as a .zip file. By default, the vpxd logs within the bundle are compressed as .gz files. You must use gunzip to uncompress these files. n From the vCenter Server system, select Start > Programs > VMware > Generate vCenter Server log bundle. You can use this to generate vCenter Server log bundles even when you are unable to connect to the vCenter Server using the vSphere Client. The log bundle is generated as a .zip file. By default, the vpxd logs within the bundle are compressed as .gz files. You must use gunzip to uncompress these files. Collect ESX Log Files Using the Service Console You can collect and package all relevant ESX system and configuration information, a well as ESX log files. This information can be used to analyze the problems. Procedure u Run the following script on the service console: /usr/bin/vm-support The resulting file has the following format: esx--.tgz VMware, Inc. 69

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364

Procedure
1
From the vSphere Client connected to a vCenter Server system or ESX/ESXi host, select
Administration
> Export Diagnostic Data.
2
If the vSphere Client is connected to a vCenter Server system, specify the host whose logs you want to
export and the location for storing the log files.
3
If the vSphere Client is connected to an ESX/ESXi host, specify the location for the log files.
4
Click
OK
.
Collecting Log Files
VMware technical support might request several files to help resolve technical issues. The following sections
describe script processes for generating and collecting some of these files.
Set Verbose Logging
You can specify how verbose log files will be.
Procedure
1
Select
Administration > vCenter Server Settings
.
2
Select
Logging Options
.
3
Select
Verbose
from the pop-up menu.
4
Click
OK
.
Collect vSphere Log Files
You can collect vSphere log files into a single location.
Select from the options:
Procedure
n
To view the
viclient-*.log
files, change to the directory,
%temp%
.
n
If you are running the vSphere Client connected to a vCenter Server system, download the log bundle.
The log bundle is generated as a
.zip
file. By default, the vpxd logs within the bundle are compressed
as
.gz
files. You must use
gunzip
to uncompress these files.
n
From the vCenter Server system, select
Start > Programs > VMware > Generate vCenter Server log
bundle
.
You can use this to generate vCenter Server log bundles even when you are unable to connect to the
vCenter Server using the vSphere Client.
The log bundle is generated as a
.zip
file. By default, the vpxd logs within the bundle are compressed
as
.gz
files. You must use
gunzip
to uncompress these files.
Collect ESX Log Files Using the Service Console
You can collect and package all relevant ESX system and configuration information, a well as ESX log files.
This information can be used to analyze the problems.
Procedure
u
Run the following script on the service console:
/usr/bin/vm-support
The resulting file has the following format:
esx-
<date>
-
<unique-xnumber>
.tgz
Chapter 5 Configuring Hosts and vCenter Server
VMware, Inc.
69