Page 1 of 1
uplink_bandwidth_ifstatus on HyperV VM
Posted: Wed Feb 05, 2014 4:40 pm
by rlevick
uplink_bandwidth_ifstatus is working on my physical machines, but not a migrated Hyper-V VM. For the check command check_snmp_ifstatus!"11"!75!95 I get a CRITICAL: 11 is physically DOWN response. Should I use an identifier other than 11 on a VM?
Re: uplink_bandwidth_ifstatus on HyperV VM
Posted: Wed Feb 05, 2014 4:48 pm
by tmcdonald
The interfaces could be different on a VM than on the physical host. Have you done a snmpwalk on the host?
Re: uplink_bandwidth_ifstatus on HyperV VM
Posted: Thu Feb 06, 2014 10:09 am
by rlevick
According to the snmpwalk, the production ehternet is ifalias.23. When I run the command manually, it works. If I change the <server>.cfg, I get an error on the console (Return code of 13 is out of bounds).
# /usr/local/nagios/libexec/check_snmp_ifstatus.pl -H 10.xx.xx.xx -C publicxxxxxxx -v 2 -i "23" -w 75 -c 95
OK: 23 is UP at 200Mbps. RX=1.819Mbps (0.9%), TX=46.23Kbps (0.02%)|RXbps=1818541;150000000;190000000;0;200000000 TXbps=46227;150000000;190000000;0;200000000 RXpct=0.9%;75;95;0;100 TXpct=0.02%;75;95;0;100 elapsed=193s;171
Re: uplink_bandwidth_ifstatus on HyperV VM
Posted: Thu Feb 06, 2014 10:34 am
by rlevick
I got it. I removed the iftraffic_if23_10.xx.xx.xx file from /tmp. Since I ran the command manually as root, the console could not overwrite the file.
Re: uplink_bandwidth_ifstatus on HyperV VM
Posted: Thu Feb 06, 2014 12:14 pm
by abrist
Eureka! Anything else, or should we lock it up?