Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Sun Integrated Lights Out Manager (ILOM) Alarm check
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
Please, issue a 'perldoc check_ilom.pl' for more information.
Sorry for the lack of updates to this plugin. SUN continually decides to completely overhual the SNMP tables for ilom devices. I finally put in support request asking them kindly to stop making so many changes. I have had to hack this script numerous times over the past few months to keep it working with new firmwares released by SUN. In the new version, 1.3, you'll find some cheap tricks that may help getting this to work with your hardware. Our collection of ILOM based SUN hardware is not incredibly diverse, but I can do my best to help you with the hardware that you may have.
This script, out of the box, is configured to support SUN T5120's, x4150's and x4250's.
The biggest change came recently when we upgraded to ILOM firmware version 3.
SUN-PLATFORM-MIB::sunPlatEquipmentLocationName is now completely useless, and I've switched to using ENTITY-MIB::entPhysicalName, however this will ONLY work on firmwares upgraded to v3. So, if you're like me and can't upgrade all firmwares at once (who can?!), you'll need to tell this script which SNMP table to use for $alarmnamesoid by architecture, or by which machines you've upgraded and which ones you haven't... Look at what I've done for x4150's in this script to see what I'm talking about. If you're really in a bind, you'll just have to create two check commands, one referring to the old version, one to the new one ... SORRY! BLAME SUN!
Alternatively, you could just setup SNMPTT and rely on the SNMP traps sent by the ILOM interfaces ....
Sorry for the lack of updates to this plugin. SUN continually decides to completely overhual the SNMP tables for ilom devices. I finally put in support request asking them kindly to stop making so many changes. I have had to hack this script numerous times over the past few months to keep it working with new firmwares released by SUN. In the new version, 1.3, you'll find some cheap tricks that may help getting this to work with your hardware. Our collection of ILOM based SUN hardware is not incredibly diverse, but I can do my best to help you with the hardware that you may have.
This script, out of the box, is configured to support SUN T5120's, x4150's and x4250's.
The biggest change came recently when we upgraded to ILOM firmware version 3.
SUN-PLATFORM-MIB::sunPlatEquipmentLocationName is now completely useless, and I've switched to using ENTITY-MIB::entPhysicalName, however this will ONLY work on firmwares upgraded to v3. So, if you're like me and can't upgrade all firmwares at once (who can?!), you'll need to tell this script which SNMP table to use for $alarmnamesoid by architecture, or by which machines you've upgraded and which ones you haven't... Look at what I've done for x4150's in this script to see what I'm talking about. If you're really in a bind, you'll just have to create two check commands, one referring to the old version, one to the new one ... SORRY! BLAME SUN!
Alternatively, you could just setup SNMPTT and rely on the SNMP traps sent by the ILOM interfaces ....
Reviews (1)
byomegamsx, June 13, 2019
Paste this at line 117:
elsif ($archtype eq "x86-4170") {
@alternating_alarms = ("/SYS/FB/FM0/OK", "/SYS/FB/FM1/OK", "/SYS/FB/FM2/OK", "/SYS/FB/FM3/OK", "/SYS/OK");
# ENTITY-MIB::entPhysicalName
$alarmnamesoid=".1.3.6.1.2.1.47.1.1.1.1.7";
}
elsif ($archtype eq "x86-4170") {
@alternating_alarms = ("/SYS/FB/FM0/OK", "/SYS/FB/FM1/OK", "/SYS/FB/FM2/OK", "/SYS/FB/FM3/OK", "/SYS/OK");
# ENTITY-MIB::entPhysicalName
$alarmnamesoid=".1.3.6.1.2.1.47.1.1.1.1.7";
}
