2V0-620 · Question #42
An administrator reports that the System Event log data is only available for 24 hours when reviewing the Hardware Status tab. Which condition could be responsible for the loss of data?
The correct answer is A. A Reset event log was executed. System Event Log data loss in the vSphere Hardware Status tab is most commonly caused by a Reset event log command that wipes the BMC/IPMI log buffer.
Question
An administrator reports that the System Event log data is only available for 24 hours when reviewing the Hardware Status tab. Which condition could be responsible for the loss of data?
Options
- AA Reset event log was executed.
- BThe statistical collection level was set to a value of 1.
- CThe boot disk of the host is corrupt.
- DSyslog has been configured at the vCenter Server level.
How the community answered
(49 responses)- A76% (37)
- B14% (7)
- C4% (2)
- D6% (3)
Why each option
System Event Log data loss in the vSphere Hardware Status tab is most commonly caused by a Reset event log command that wipes the BMC/IPMI log buffer.
The IPMI/BMC System Event Log has a fixed-size hardware buffer; when a Reset event log command is executed - either manually or by an automated process - all prior entries are erased, explaining why data is only available from the preceding 24 hours. This reset operation directly clears the event history stored on the host's baseboard management controller, not a software-layer log.
The statistical collection level controls vCenter performance metric granularity and retention intervals, not the availability of hardware IPMI/BMC System Event Log data.
A corrupt boot disk would impair host services broadly but would not selectively limit System Event Log entries to a 24-hour window.
Configuring Syslog at the vCenter Server level routes software-layer messages to an external destination but has no effect on the hardware BMC System Event Log displayed in the Hardware Status tab.
Concept tested: IPMI BMC System Event Log reset behavior in vSphere
Source: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.monitoring.doc/GUID-A60D0A54-8A16-4A83-9DC8-67B73ABE3F05.html
Topics
Community Discussion
No community discussion yet for this question.