Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
3Com Switch Check Suite
Current Version
0.7
Last Release Date
2009-10-15
Owner
Hits
117703
Files:
| File | Description |
|---|---|
| check_3com_alive.pl | 1) check_3com_alive |
| check_3com_health.pl | 2) check_3com_health |
| check_3com_link.pl | 3) check_3com_link |
| check_3com_ensure.pl | 4) check_3com_ensure |
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!
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.
1) check_3com_alive
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.
2) check_3com_health
Checks the following health aspects of the switch:
Fan status, Power Module status, Free Memory, and CPU load
3) check_3com_link
Checks various switch and stack interconnectivity aspects including:
Stack unit failure, Switch stack fabric topology level, Aggregated link status,
and Aggregated link port status.
4) check_3com_ensure
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.
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.
1) check_3com_alive
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.
2) check_3com_health
Checks the following health aspects of the switch:
Fan status, Power Module status, Free Memory, and CPU load
3) check_3com_link
Checks various switch and stack interconnectivity aspects including:
Stack unit failure, Switch stack fabric topology level, Aggregated link status,
and Aggregated link port status.
4) check_3com_ensure
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.
Reviews (4)
bybelgotux, April 21, 2014
Work great with switch 3COM 4500 for me in Centreon 2.5. The graphs work too for CPU, memory an fan.
This script don't work with 3COM 4400 unfortunately.
Regards,
Belgotux
This script don't work with 3COM 4400 unfortunately.
Regards,
Belgotux
bycheper, July 5, 2012
/usr/local/nagios/libexec/check_3com_health.pl -H 172.12.X.X
get this:
3COM_HEALTH CRITICAL - FAN:SNMP ERROR PWR:OK MEM:OK CPU:OK | pwr=100%;100;76;0;100 mem=42%;85;90;0;100 cpu=11%;85;90;0;100
get this:
3COM_HEALTH CRITICAL - FAN:SNMP ERROR PWR:OK MEM:OK CPU:OK | pwr=100%;100;76;0;100 mem=42%;85;90;0;100 cpu=11%;85;90;0;100
We are using a 3Com Switch 5500-EI 52-Port (Software Version 3Com OS V3.03.01s56e) and with check_3com_health.pl we get the following error when checking different switches in our XRN. We have 4 units (1, 2, 5, 6)
[root@NAGIOS libexec]# ./check_3com_health.pl -H 10.11.1.10 -u 2
Use of uninitialized value in hash element at ./check_3com_health.pl line 333.
Argument "" isn't numeric in multiplication (*) at ./check_3com_health.pl line 453.
Use of uninitialized value in sprintf at ./check_3com_health.pl line 467.
Argument "" isn't numeric in multiplication (*) at ./check_3com_health.pl line 453.
Use of uninitialized value in sprintf at ./check_3com_health.pl line 467.
Argument "" isn't numeric in multiplication (*) at ./check_3com_health.pl line 369.
Use of uninitialized value in subtraction (-) at ./check_3com_health.pl line 371.
Use of uninitialized value in subtraction (-) at ./check_3com_health.pl line 371.
Use of uninitialized value in numeric gt (>) at ./check_3com_health.pl line 372.
Use of uninitialized value in sprintf at ./check_3com_health.pl line 375.
Argument "" isn't numeric in multiplication (*) at ./check_3com_health.pl line 407.
Use of uninitialized value in numeric gt (>) at ./check_3com_health.pl line 409.
Use of uninitialized value in addition (+) at ./check_3com_health.pl line 415.
3COM_HEALTH CRITICAL - FAN: U0=0% PWR: U0=0% MEM: U0=100% CPU:OK | fan=0%;100;76;0;100 pwr=0%;100;76;0;100 mem=100%;85;90;0;100 cpu=0%;85;90;0;100
Checking unit 1 works.
[root@NAGIOS libexec]# ./check_3com_health.pl -H 10.11.1.10 -u 1
3COM_HEALTH OK - FAN:OK PWR:OK MEM:OK CPU:OK | fan=100%;100;76;0;100 pwr=100%;100;76;0;100 mem=66%;85;90;0;100 cpu=24%;85;90;0;100
Checking all works(apparently).
[root@NAGIOS libexec]# ./check_3com_health.pl -H 10.11.1.10
3COM_HEALTH OK - FAN:OK PWR:OK MEM:OK CPU:OK | fan=100%;100;76;0;100 pwr=100%;100;76;0;100 mem=66%;85;90;0;100 cpu=21%;85;90;0;100
Any thoughts?
[root@NAGIOS libexec]# ./check_3com_health.pl -H 10.11.1.10 -u 2
Use of uninitialized value in hash element at ./check_3com_health.pl line 333.
Argument "" isn't numeric in multiplication (*) at ./check_3com_health.pl line 453.
Use of uninitialized value in sprintf at ./check_3com_health.pl line 467.
Argument "" isn't numeric in multiplication (*) at ./check_3com_health.pl line 453.
Use of uninitialized value in sprintf at ./check_3com_health.pl line 467.
Argument "" isn't numeric in multiplication (*) at ./check_3com_health.pl line 369.
Use of uninitialized value in subtraction (-) at ./check_3com_health.pl line 371.
Use of uninitialized value in subtraction (-) at ./check_3com_health.pl line 371.
Use of uninitialized value in numeric gt (>) at ./check_3com_health.pl line 372.
Use of uninitialized value in sprintf at ./check_3com_health.pl line 375.
Argument "" isn't numeric in multiplication (*) at ./check_3com_health.pl line 407.
Use of uninitialized value in numeric gt (>) at ./check_3com_health.pl line 409.
Use of uninitialized value in addition (+) at ./check_3com_health.pl line 415.
3COM_HEALTH CRITICAL - FAN: U0=0% PWR: U0=0% MEM: U0=100% CPU:OK | fan=0%;100;76;0;100 pwr=0%;100;76;0;100 mem=100%;85;90;0;100 cpu=0%;85;90;0;100
Checking unit 1 works.
[root@NAGIOS libexec]# ./check_3com_health.pl -H 10.11.1.10 -u 1
3COM_HEALTH OK - FAN:OK PWR:OK MEM:OK CPU:OK | fan=100%;100;76;0;100 pwr=100%;100;76;0;100 mem=66%;85;90;0;100 cpu=24%;85;90;0;100
Checking all works(apparently).
[root@NAGIOS libexec]# ./check_3com_health.pl -H 10.11.1.10
3COM_HEALTH OK - FAN:OK PWR:OK MEM:OK CPU:OK | fan=100%;100;76;0;100 pwr=100%;100;76;0;100 mem=66%;85;90;0;100 cpu=21%;85;90;0;100
Any thoughts?
The scripts like help me to monitor my 3com network.
But, I think is missing just usage commands.
Where can I find it to run and monitor my devices?
Thankyou.
But, I think is missing just usage commands.
Where can I find it to run and monitor my devices?
Thankyou.
