Page 2 of 2
Re: Port name is different than "Status Information"
Posted: Tue May 18, 2021 10:55 am
by gsmith
Hi,
That makes sense to me - if the status/description/index numbers of the ports changed on the Cisco side
then Nagios will indeed be confused.
But now Nagios giving critical status of the ports which is not being used or not configured to use. Is there a way, Nagios can detect that these ports are not configured or not being used and changed the status other than critical?
Nagios cannot auto-detect this, but you can delete the ports you don't want monitored in the service configuration.
Let me know if you need anything else.
Thanks
Re: Port name is different than "Status Information"
Posted: Tue May 18, 2021 2:02 pm
by ar0431
That makes sense to me - if the status/description/index numbers of the ports changed on the Cisco side
then Nagios will indeed be confused.
But Nagios should be refresh itself, according to the Cisco side. Nagios should not be confused. It should refresh its data.
But now Nagios giving critical status of the ports which is not being used or not configured to use. Is there a way, Nagios can detect that these ports are not configured or not being used and changed the status other than critical?
Nagios cannot auto-detect this, but you can delete the ports you don't want monitored in the service configuration.
Nagios can detect this. See the following link. only for the reference hint. Through this script you can detect the non configured/ non connected ports.
https://exchange.icinga.com/farid/check ... notconnect
Re: Port name is different than "Status Information"
Posted: Tue May 18, 2021 2:31 pm
by UTE-COT
In your Cisco device did you configure the following line?
snmp-server ifindex persist
The SNMP ifIndex persistence feature provides an interface index (ifIndex) value that is retained and used when the router reboots.
Re: Port name is different than "Status Information"
Posted: Tue May 18, 2021 3:44 pm
by ar0431
Good point.
We added this to our cisco switch for snmp configuration. Let see if it will work. That switch is in production. We can not reboot immediately but during maintenance down time, we will observe that.
Re: Port name is different than "Status Information"
Posted: Wed May 19, 2021 9:15 am
by gsmith
Hi
https://exchange.icinga.com/farid/check ... notconnect is for some other product and is unsupported
for Nagios XI.
Thanks to UTE-COT for the tip on how to have the Cisco switch "hold" the interface index.
Do you need anything else from me, or can I lock this thread?
Thanks