Unsolved
This post is more than 5 years old
17 Posts
0
48553
November 13th, 2015 00:00
False SNMP traps from ESXi hosts "Severity:Critical, Message:Disk Drive Bay x Cable SAS x: Config Error - Assert, Severity: Fatal"
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 three hosts [email notifications which we have set], please suggest what corrective action should be done.
Category: VMware ESX Server
Source: vmwESXEnvHardwareAlert
Host 1 - PowerEdge R820 - iDrac7 2.20.20.20 - bios 2.3.2
Device:X, Service Tag:XXXXXX, Asset Tag:Unknown, Date:11/13/2015, Time:01:13:37, Severity:Critical, Message:Disk Drive Bay 1 Cable SAS A 0: Config Error - Assert, Severity: Fatal, System: 4c4c4544-005a-b4c04f533232, Provider: RawIpmiProvider
Host 2- PowerEdge R820 - iDrac7 2.15.10.10 - bios 2.3.2
Device:X, Service Tag:XXXXXX, Asset Tag:Unknown, Date:11/13/2015, Time:01:33:48, Severity:Critical, Message:Disk Drive Bay 2 Cable SAS A 0: Config Error - Assert, Severity: Fatal, System: 4c4c4544-0030-b7c04f533232, Provider: RawIpmiProvider
Host 3 - PowerEdge R820- iDrac7 2.15.10.10 - bios 2.3.2
Device:X, Service Tag:XXXXXX, Asset Tag:Unknown, Date:11/13/2015, Time:01:32:27, Severity:Critical, Message:Disk Drive Bay 1 Cable SAS A 0: Config Error - Assert, Severity: Fatal, System: 4c4c4544-0038-c3c04f323532, Provider: RawIpmiProvider
DELL-Vijay B
183 Posts
1
November 13th, 2015 14:00
Hi,
This alert vmwESXEnvHardwareAlert 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 302.
You can create a "New Alert Ignore Action" task on this alert source - vmwESXEnvHardwareAlert 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.