Nagios Support Forum

How can i monitor NIC bonding as i have observed some issue with current configuration i have active back configuration on most of servers
m using the below command for monitoring

check_xi_service_ifoperstatus!public!4!-v 2 -p 161

Can you provide us with a little bit more information? What are the issues that you observed with current configuration? What is the output of the check that you expect to see vs the output you actually see?

lmiltchev wrote:Can you provide us with a little bit more information? What are the issues that you observed with current configuration? What is the output of the check that you expect to see vs the output you actually see?

I have NIC bonding for eth0,1,2,3 below is the device status which shows that there is trafic at the ports but still i have alert for NIC

COMMAND: /usr/local/nagios/libexec/check_ifoperstatus -H hcrbt1 -C public -k 6 -v 2 -p 161
OUTPUT: OK: Interface eth0 (index 6) is up.

How can i identify the value of k in the check command for the interface ??

[nagios@HNRBT8 network-scripts]$ cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo:623479332 3992595 0 0 0 0 0 0 623479332 3992595 0 0 0 0 0 0
eth0: 209780 2802 0 0 0 0 0 66 13223 68 0 0 0 0 0 0
eth1:11524804154 88555698 0 0 0 0 0 64 18010791661 62646621 0 0 0 0 0 0
eth4: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
eth5: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
eth2: 193306 2772 0 0 0 0 0 129 4357 21 0 0 0 0 0 0
eth3:331677009 3412327 0 0 0 0 0 127 4427 22 0 0 0 0 0 0
sit0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
bond0:11856481163 91968025 0 0 0 0 0 191 18010796088 62646643 0 0 0 0 0 0
bond1: 403086 5574 0 0 0 0 0 195 17580 89 0 0 0 0 0 0

Run the snmpwalk command against that host and it should show you the index number in it's output.

tgriep wrote:Run the snmpwalk command against that host and it should show you the index number in it's output.

Code: Select all

snmpwalk hcrbt1 -c public -v 2c |grep bond0

[root@nagiosxi ~]# snmpwalk hcrbt1 -c public -v 2c |grep bond0
IF-MIB::ifDescr.9 = STRING: bond0
Timeout: No Response from hcrbt1
Can you suggest how can i fix this.
Let me know if i can disable this from populating on the operation center as after acknowledgement as well it is there on operation center.

The snmpwalk did run and return the index number of 9 that that you would use in the check_ifoperstatus command -f option.
Try that and it should work for you.

tgriep wrote:The snmpwalk did run and return the index number of 9 that that you would use in the check_ifoperstatus command -f option.
Try that and it should work for you.

I am using the below command :
./check_ifoperstatus -H hnrbt1 -C public -k 6 -v 2 -p 161
issue was resolved as i changed the value of -k n as form output of snmpwalk
[root@nagiosxi libexec]# snmpwalk hcrbt1 -c public -v 2c |grep eth0
IF-MIB::ifDescr.2 = STRING: eth0

Where n=2

Is this above logic correct.

Yes, the logic is correct. You can use the snmpwalk command to find the Index number and use that in the -k option.
Another way is to run the Network Switch / Router Wizard against that device and it should pick up the interfaces and set them up for you to be monitored on the system without manually creating the checks.

tgriep wrote:Yes, the logic is correct. You can use the snmpwalk command to find the Index number and use that in the -k option.
Another way is to run the Network Switch / Router Wizard against that device and it should pick up the interfaces and set them up for you to be monitored on the system without manually creating the checks.

Again i Have observed similar issue with some solaris node can you suggest how can i fix it.

Attaching screenshot for your referance :

ericssonvietnam wrote:Again i Have observed similar issue with some solaris node can you suggest how can i fix it.

Attaching screenshot for your referance :

Attachments

nic.PNG

The error you are receiving is caused by SNMP on the remote machine not responding, at least not in time. This can be caused by any of the following

• IP routing problem
  Firewall Problem
  SNMP not responding in a timely fasion
  Incorrect SNMP community string
  UDP packets being blocked or dropped

If it is a timeout, you can change the command to wait longer but this is not likely the case as the default is 15 seconds, however you can add the following to the command to up it to 30 seconds