3Com Check Suite

3Com Check Suite

The suite consists of four scripts (described below).  All scripts rely on Perl's Net::SNMP library to check various aspects of 3Com switches which support the Huawei-3Com(H3C) iso::enterprise.a3com.jv-mib.huawei SNMP standard.

I have tested them on 4500 & 5500 family switches successfully.


Checks to make sure that all units in a stack are available.  

It is meant to be used as a host check_command to allow for more effective

parent/topology testing.  If a single unit fails the entire stack will be deemed down.  

For example, if you have two units stacked and your Nagios server and Web server

are plugged into Unit 1 and the DNS server is plugged into Unit 2. If Unit 2 fails,

even though Nagios would still be able to ping/communicate with the switch via Unit 1 Nagios will consider the switch down and will correctly alert you that the switch is having problems instead of the DNS server.


Checks the following health aspects of the switch:

Fan status, Power Module status, Free Memory, and CPU load


Checks various switch and stack interconnectivity aspects including: Stack unit failure, Switch stack fabric topology level, Aggregated link status, and Aggregated link port status.


Designed to check various configuration settings. Unsaved Configuration - notifies you if changes on the switch stay unsaved for too long. STP Enabled/Disabled - As great as spanning tree is, more than one 3Com technician has recommended that we always disable STP because of the many unintentional problems it can cause.

IGMP Enabled/Disabled - Like STP, while good intentioned often enabling IGMP causes more problems than it solves. Note: I would not recommend running this test more often than every hour or day considering these parameters will only change if someone manually modifies the switch configuration. I primarily use it for the Unsaved Configuration test.  There is nothing worse than losing the config changes of six months ago due to a power outage of yesterday. (3Dec09: I have discovered that 3Com doesn't always correctly update the timestamps when the config is saved via the web.  Saving the config via the command line seems to always work.)

A final note for Nagios 3.0 users: I have disabled ePN on these scripts due to a memory leak problem with ePN.

(http://tracker.nagios.org/view.php?id=71 and http://tracker.nagios.org/view.php?id=92)

If this issue is resloved you can re-enable ePN by removing the "# nagios: -epn" line.