Which action should the administrator take to resolve the logging issue?

While troubleshooting a crash event on an ESXi 5.x host, an administrator determines the log files
related to the event are NOT present.
Which action should the administrator take to resolve the logging issue?

While troubleshooting a crash event on an ESXi 5.x host, an administrator determines the log files
related to the event are NOT present.
Which action should the administrator take to resolve the logging issue?

A.
Increase the amount of memory committed to log storage.

B.
Increase the statistic data collection level to 4.

C.
Change the roll-up type to maximum.

D.
Create a persistent scratch location.

Explanation:

Show Hint

Leave a Reply 3

Your email address will not be published. Required fields are marked *

babar.munir

babar.munir

D is correct

VMware recommends that ESXi has a persistent scratch location available for storing temporary data including logs, diagnostic information, and system swap. (This is not a requirement, however.) Persistent scratch space may be provisioned on a FAT 16, VMFS, or NFS partition accessible by the ESXi host.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033696

Reply

BUN

BUN

thanks babar.munir

VMwareは、ログ、診断情報およびシステム スワップを含む一時データの格納のために ESXi が永続的スクラッチの場所を備えておくことを推奨します （ただし、これは必須ではありません）。 永続的スクラッチの領域は、ESXi ホストによってアクセス可能な FAT 16、VMFS または NFS パーティションにプロビジョニングすることができます。

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033696
↓日本語訳版
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2042585

Reply