UNKNOWN: No usable interface speed available 64: 0 32: 0

[solarmon]

Hi,

I'm trying to graph the VLAN interfaces of a HP Procurve switch using the check_iftraffic64.pl script.

However, it is returning the following message:

UNKNOWN: No usable interface speed available 64: 0 32: 0

What does this mean, and is VLAN interface monitor supported?

Thank you for your help.

[mbellerue]

We will need the command and service definitions. If you could post those here that would be great. Or if you just want to PM your system profile over to me and let me know the name of the service, I can check it out.

As to whether this script supports checking VLANs, it looks like it works off of SNMP, so I would imagine that if the remote system is presenting VLAN information via SNMP, you should be able to view it.

[solarmon]

Hi the check_iftraffic64.pl script can be found at:

https://exchange.nagios.org/directory/P ... 64/details

And I created a check command using the following:

$USER1$/check_iftraffic64.pl -H $HOSTADDRESS$ -C $ARG1$ -i $ARG2$

Is this enough details for you?

I'll also PM you the system profile.

Thank you.

[mbellerue]

That's perfect, thank you!

Another question. It looks like you use this plugin pretty heavily. Are all of your checks failing with the specified error, or is it just a few specific services that are failing? If it's just a few, could I get a couple of service names? I will focus on those.

[solarmon]

Hi @mbellerue

Apologies in the delay in response.

I am looking to use it heavily. It will be monitoring our switches. I would like to monitor the vlan interfaces, as well as the physical ethernet interfaces.

For the physical ethernet interfaces it is obviously fine, but I am getting this error/issue for vlan interfaces.

Please let me know if you need any other details.

Thank you.

[mbellerue]

Excellent, thank you for the information! I've been looking over the code for this plugin, and I can't immediately see why VLANs wouldn't be supported, unless they show up as some other kind of interface name than the physical interfaces.

For example, you have EDGE-02 (abbreviating so as to not out your infrastructure), and service description 1/1/10 Bandwidth - iftraffic64. From what I can tell of the command, it's checking an interface named 10. Probably the 10th port on the switch.

I do see some VLAN checks, though not with the iftraffic64 script. The VLAN names are vlan#####. I'm wondering if the script is getting hung up on the fact that an interface name would be a string rather than an int? Is it possible to create a test VLAN that only has a number as its name? Or conversely, could you name a physical interface with an alpha-numeric name? If we could do one of those two things, we could test the iftraffic64 script against the test interface.

[solarmon]

@mbellerue

For that example, the interface is named '1/1/10' based on which hardware module/slot it is in.

These physical interfaces are not an issue. The problem I have is with the virtual VLAN interfaces - for example, VLAN interface vlan1311.

These interfaces are in a HP Layer 3 switch.

Are you able to test against a Layer 3 switch to verify whether the script can get interfaces stats from a VLAN interface.

Thank you.

[benjaminsmith]

Hi @solarmon,

Michael is out of the office today, so I'm helping out.

1. Can you run the check command directly from the plugin directory in Nagios and add the debug option -d, and post the full output of the error message?

See: Nagios XI - How To Test Check Commands From The Command-line

2. It's possible that the VLAN interface does not use the same OID as the physical interface. In this case, the script may need to be modified to work.

https://serverfault.com/questions/54050 ... p-procurve

Thanks.

[solarmon]

Hi @benjaminsmith

I used the "-d 4" debug option and ran the check command on one of the vlan interfaces, below is the debug output:

Code: Select all

[nagios@<NAGIOS HOST> ~]$ /usr/local/nagios/libexec/check_iftraffic64.pl -H <IP ADDRESS> -C <community>-i 16778517 -d 4
DEBUG ENABLED at level: 4
INTERFACE DESCR: 16778517
BYTE COUNTER max_value: 1.84467440737096e+19
SNMP:
ver: 2
community: <community>
port: 161
USING INT#: 16778517
OID's:
IfOperStatus: 1.3.6.1.2.1.2.2.1.8.16778517
IfSpeed: 1.3.6.1.2.1.31.1.1.1.15.16778517
IfSpeed32: 1.3.6.1.2.1.2.2.1.5.16778517
InOctets: 1.3.6.1.2.1.31.1.1.1.6.16778517
InOctets32: 1.3.6.1.2.1.2.2.1.10.16778517
OutOctets: 1.3.6.1.2.1.31.1.1.1.10.16778517
OutOctets32: 1.3.6.1.2.1.2.2.1.16.16778517
RESULTS:
Operational Status: 1
Interface Speed (64bit): 0 Mbits
Interface Speed (32bit): 0 bits
In Bytes (64bit): 0
In Bytes (32bit): 0
Out Bytes (64bit): 0
Out Bytes (32bit): 0
USING 64 THEN 32 bit VALUES:
(Interface speed not provided on command line, determine from host)
Bad 64bit speed value: 0
Bad 32bit speed value: 0
UNKNOWN: No usable interface speed available 64: 0 32: 0

Thank you for the link. I will also try to get support from our switch vendor regarding the SNMP monitoring of the VLAN interfaces.

Thank you.

[benjaminsmith]

Hello @solarmon,

Thanks for posting the debug output from the command. Can run an SNMP walk command against the device, and post the full output?

Code: Select all

snmpwalk -v 2c -c public <ip address>