Unsolved
This post is more than 5 years old
17 Posts
0
43314
false alerts for ESXi host [False SNMP traps from ESXi hosts Severity:Critical, Message:Processor x Status 0: Configuration Error / IERR - Assert / Thermal Trip - Assert
Hi,
We are starting a integration of ESXi hosts with DELL OME. I am receiving false SNMP traps from few of the hosts, the fatal errors are even not visible in DELL OMSA hardware/alert logs
Below example of host [email notifications which we have set], please suggest what corrective action should be done.
Category: VMware ESX Server
Source: vmwESXEnvProcessorAlert
Example host - R730XD, Bios: 1.2.10, iDrac8 2.10.10.10,
Device: x, Service Tag:x, Asset Tag:Unknown, Date:11/13/2015, Time:03:38:11, Severity:Critical, Message:Processor 1 Status 0: Configuration Error - Assert, Severity: Critical, System: 4c4c4544-0036-3510-8032-c7c04f383532, Provider: RawIpmiProvider
Device: x, Service Tag:x, Asset Tag:Unknown, Date:11/13/2015, Time:03:38:09, Severity:Critical, Message:Processor 1 Status 0: IERR - Assert, Severity: Critical, System: 4c4c4544-0036-3510-8032-c7c04f383532, Provider: RawIpmiProvider
Device: x, Service Tag:x, Asset Tag:Unknown, Date:11/13/2015, Time:03:38:10, Severity:Critical, Message:Processor 1 Status 0: Thermal Trip - Assert, Severity: Critical, System: 4c4c4544-0036-3510-8032-c7c04f383532, Provider: RawIpmiProvider
Device: x, Service Tag:x, Asset Tag:Unknown, Date:11/13/2015, Time:03:38:05, Severity:Critical, Message:Processor 2 Status 0: IERR - Assert, Severity: Critical, System: 4c4c4544-0036-3510-8032-c7c04f383532, Provider: RawIpmiProvider
Device: x, Service Tag:x, Asset Tag:Unknown, Date:11/13/2015, Time:03:38:06, Severity:Critical, Message:Processor 2 Status 0: Thermal Trip - Assert, Severity: Critical, System: 4c4c4544-0036-3510-8032-c7c04f383532, Provider: RawIpmiProvider
Device: x, Service Tag:x, Asset Tag:Unknown, Date:11/13/2015, Time:03:38:07, Severity:Critical, Message:Processor 2 Status 0: Configuration Error - Assert, Severity: Critical, System: 4c4c4544-0036-3510-8032-c7c04f383532, Provider: RawIpmiProvider
Thanks
DELL-Vijay B
183 Posts
0
November 13th, 2015 13:00
Hi,
This alert vmwESXEnvProcessorAlert is defined in VMware MIB and hence OMSA might not be listing this. If you look at the details - the enterprise OID will be .1.3.6.1.4.1.6876.4.1 and specific Id will be 308.
You can create a "New Alert Ignore Action" task on this alert source - vmwESXEnvProcessorAlert if you are not interested in monitoring this alert. Refer "Alert Ignore action" section in "Configuring Alert Actions in OpenManage Essentials" whitepaper for more details.
Thanks,
Vijay.