Nagios Support Forum

Hi Team,

We are facing one issue on interface state status information in nagios. we have core switch that is have configured with vlan and some other configuration.

in the below output port-channel10 (##) Ethernet1/40 (##) Ethernet1/41 these both are having issue and its genuine. But port-channel11 Ethernet1/35 (#) Ethernet1/36 both are showing down which up. we have checked in switch level also both ethernet are up and working fine.

Below is command for this.

$USER1$/check_interface_table_v3t.pl -H XXXX -h XXXX -C XXXXX -2 -f --64bits --nodetype cisco -r -e unrouted,Null,Stack,FastEthernet,Uncontrolled,Controlled --alias --et Vlan -t 45 --warning-traffic 97,1000,1000 --critical-traffic 99,5000,5000 -css nagiosxi --perfdatadir /usr/local/nagios/var/spool/perfdata/ --snmp-retries=5 --perfdataservicedesc process-service-perfdata-file-bulk --tp ifAdminStatus,ifOperStatus --cp 1



CRITICAL - 11 change(s): ifOperStatus - port-channel10 (#[MGT] to UCS-VOIP#) Ethernet1/40 (##) Ethernet1/41 (#[P#) ifAdminStatus - Vlan52 (### 4th users LR ###) Vlan54 (### 6th users LR ###) Vlan76 (### 4th VOIP LR ###) Vlan78 (### 6th VOIP LR ###) port-channel11 (##) port-channel4089 (#[P2P] #) Ethernet1/35 (#) Ethernet1/36 (#[) <a href=/interfacetable_v3t/tables/BLNX9K01-Interfacetable.html target=_self>[details]</a>

can anybody reply on this.

Hi,

One question. Is this consistently showing down or is this an intermittent issue ( happening on and off)? If you are not sure, you can run a state history report on the service to find out.

I'm not familiar with this specific plugin, but it does provide debug output. Can run the plugin directly from the command line with the verbose option added.

-v, --verbose Verbose mode. Can be specified multiple times to increase the verbosity (max 5 times). Verbose levels are INFO, DEBUG, TRACE1, TRACE2, and DUMP

Lastly, have you tried using the Switch and Router Wizard in Nagios XI on this device?

Best Regards,
Benjamin

Hi @informatica,

One more suggestion with this plugin, it looks like it keeps status information in a file in the /tmp folder. I would recommend deleting that file, and see if that clears the error.