We are monitoring Network Switches with NSMP v3. After the reboot of the Network Switch, there is a issue of port names.
Please see the screen shot. It giving us different port name under "service" column than under the "Status Information" column.
How we can resolve it. Which port name/interface name is correct?
Let me know if you need more information.
Port name is different than "Status Information"
Port name is different than "Status Information"
You do not have the required permissions to view the files attached to this post.
Re: Port name is different than "Status Information"
Hi,
Looking at our Network Switch/Router configuration wizard: it appears that a port's number, name and description are generally available from the
network device manufacturer.
You can use the Core Config Manager to examine each service, this should reveal the OID
it is monitoring. Then you can talk to the device manufacturer to make sure you have the
latest MIB file for your device. The MIB file translates the OID number to textual information.
Once you verify the OID/MIB then you can rename the service as required via the CCM.
Was there a firmware upgrade to the network device?
Thanks
Looking at our Network Switch/Router configuration wizard: it appears that a port's number, name and description are generally available from the
network device manufacturer.
You can use the Core Config Manager to examine each service, this should reveal the OID
it is monitoring. Then you can talk to the device manufacturer to make sure you have the
latest MIB file for your device. The MIB file translates the OID number to textual information.
Once you verify the OID/MIB then you can rename the service as required via the CCM.
Was there a firmware upgrade to the network device?
Thanks
You do not have the required permissions to view the files attached to this post.
Re: Port name is different than "Status Information"
Thank you for your reply. This switch is a Cisco switch. There was no firmware update. It was a simple reboot on the switch. Is Nagios using old MIB for Cisco switches??
Re: Port name is different than "Status Information"
Nagios is using the following command. Is this command using MIB? How we can update Cisco MIB on Nagios?
check_xi_service_ifoperstatusnag!18!-v3 -u '' -A '' -x 'AES' -X '' -a 'SHA' -l 'authPriv'
check_xi_service_ifoperstatusnag!18!-v3 -u '' -A '' -x 'AES' -X '' -a 'SHA' -l 'authPriv'
Re: Port name is different than "Status Information"
What is that "index number 18"?? Where that come from? There is no index numbering on Cisco switches?
Re: Port name is different than "Status Information"
HI,
Thank you for your reply. This switch is a Cisco switch. There was no firmware update. It was a simple reboot on the switch. Is Nagios using old MIB for Cisco switches??
The MIBs Nagios uses are typically in /usr/share/snmp/mibs, you can add more current and more specific MIBs
to this directory.
Nagios is using the following command. Is this command using MIB? How we can update Cisco MIB on Nagios?
check_xi_service_ifoperstatusnag!18!-v3 -u '' -A '' -x 'AES' -X '' -a 'SHA' -l 'authPriv'
All options beyond the first, are arguments that must follow the snmpget command line parameters.
General options
-m MIB[:...] load given list of MIBs (ALL loads everything)
-M DIR[:...] look in given list of directories for MIBs
(default: $HOME/.snmp/mibs:/usr/share/snmp/mibs)
What is that "index number 18"?? Where that come from? There is no index numbering on Cisco switches?
Usage ./check_ifoperstatnag: <interface index> <snmpget options>
Check_ifoperstatus requires that the first argument be the interface index that this interface can be found at
under the remote devices snmp tree. This should always be a positive integer, or zero.
All options beyond the first, are arguments that must follow the snmpget command line parameters.
Thank you for your reply. This switch is a Cisco switch. There was no firmware update. It was a simple reboot on the switch. Is Nagios using old MIB for Cisco switches??
The MIBs Nagios uses are typically in /usr/share/snmp/mibs, you can add more current and more specific MIBs
to this directory.
Nagios is using the following command. Is this command using MIB? How we can update Cisco MIB on Nagios?
check_xi_service_ifoperstatusnag!18!-v3 -u '' -A '' -x 'AES' -X '' -a 'SHA' -l 'authPriv'
All options beyond the first, are arguments that must follow the snmpget command line parameters.
General options
-m MIB[:...] load given list of MIBs (ALL loads everything)
-M DIR[:...] look in given list of directories for MIBs
(default: $HOME/.snmp/mibs:/usr/share/snmp/mibs)
What is that "index number 18"?? Where that come from? There is no index numbering on Cisco switches?
Usage ./check_ifoperstatnag: <interface index> <snmpget options>
Check_ifoperstatus requires that the first argument be the interface index that this interface can be found at
under the remote devices snmp tree. This should always be a positive integer, or zero.
All options beyond the first, are arguments that must follow the snmpget command line parameters.
Re: Port name is different than "Status Information"
I can not see any cisco mib file which Nagios is using.
After the reboot of cisco switch, why nagios giving the wrong names?
Why Nagios get confuse after the reboot of switch.
[root@vsatmnagios01 ~]# ls -l /usr/share/snmp/mibs/
AGENTX-MIB.txt IF-MIB.txt NAGIOS-NOTIFY-MIB.txt RMON-MIB.txt SNMPv2-SMI.txt
BRIDGE-MIB.txt INET-ADDRESS-MIB.txt NAGIOS-ROOT-MIB.txt SCTP-MIB.txt SNMPv2-TC.txt
DISMAN-EVENT-MIB.txt IP-FORWARD-MIB.txt NET-SNMP-AGENT-MIB.txt SMUX-MIB.txt SNMPv2-TM.txt
DISMAN-SCHEDULE-MIB.txt IP-MIB.txt NET-SNMP-EXAMPLES-MIB.txt SNMP-COMMUNITY-MIB.txt SNMP-VIEW-BASED-ACM-MIB.txt
DISMAN-SCRIPT-MIB.txt IPV6-FLOW-LABEL-MIB.txt NET-SNMP-EXTEND-MIB.txt SNMP-FRAMEWORK-MIB.txt TCP-MIB.txt
EtherLike-MIB.txt IPV6-ICMP-MIB.txt NET-SNMP-MIB.txt SNMP-MPD-MIB.txt TRANSPORT-ADDRESS-MIB.txt
HCNUM-TC.txt IPV6-MIB.txt NET-SNMP-PASS-MIB.txt SNMP-NOTIFICATION-MIB.txt TUNNEL-MIB.txt
HOST-RESOURCES-MIB.txt IPV6-TCP-MIB.txt NET-SNMP-TC.txt SNMP-PROXY-MIB.txt UCD-DEMO-MIB.txt
HOST-RESOURCES-TYPES.txt IPV6-TC.txt NET-SNMP-VACM-MIB.txt SNMP-TARGET-MIB.txt UCD-DISKIO-MIB.txt
IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt IPV6-UDP-MIB.txt NETWORK-SERVICES-MIB.txt SNMP-USER-BASED-SM-MIB.txt UCD-DLMOD-MIB.txt
IANAifType-MIB.txt ISILON-MIB.txt NOTIFICATION-LOG-MIB.txt SNMP-USM-AES-MIB.txt UCD-IPFWACC-MIB.txt
IANA-LANGUAGE-MIB.txt ISILON-TRAP-MIB.txt RFC1155-SMI.txt SNMP-USM-DH-OBJECTS-MIB.txt UCD-SNMP-MIB.txt
IANA-RTPROTO-MIB.txt LM-SENSORS-MIB.txt RFC1213-MIB.txt SNMPv2-CONF.txt UDP-MIB.txt
IF-INVERTED-STACK-MIB.txt MTA-MIB.txt RFC-1215.txt SNMPv2-MIB.txt
After the reboot of cisco switch, why nagios giving the wrong names?
Why Nagios get confuse after the reboot of switch.
[root@vsatmnagios01 ~]# ls -l /usr/share/snmp/mibs/
AGENTX-MIB.txt IF-MIB.txt NAGIOS-NOTIFY-MIB.txt RMON-MIB.txt SNMPv2-SMI.txt
BRIDGE-MIB.txt INET-ADDRESS-MIB.txt NAGIOS-ROOT-MIB.txt SCTP-MIB.txt SNMPv2-TC.txt
DISMAN-EVENT-MIB.txt IP-FORWARD-MIB.txt NET-SNMP-AGENT-MIB.txt SMUX-MIB.txt SNMPv2-TM.txt
DISMAN-SCHEDULE-MIB.txt IP-MIB.txt NET-SNMP-EXAMPLES-MIB.txt SNMP-COMMUNITY-MIB.txt SNMP-VIEW-BASED-ACM-MIB.txt
DISMAN-SCRIPT-MIB.txt IPV6-FLOW-LABEL-MIB.txt NET-SNMP-EXTEND-MIB.txt SNMP-FRAMEWORK-MIB.txt TCP-MIB.txt
EtherLike-MIB.txt IPV6-ICMP-MIB.txt NET-SNMP-MIB.txt SNMP-MPD-MIB.txt TRANSPORT-ADDRESS-MIB.txt
HCNUM-TC.txt IPV6-MIB.txt NET-SNMP-PASS-MIB.txt SNMP-NOTIFICATION-MIB.txt TUNNEL-MIB.txt
HOST-RESOURCES-MIB.txt IPV6-TCP-MIB.txt NET-SNMP-TC.txt SNMP-PROXY-MIB.txt UCD-DEMO-MIB.txt
HOST-RESOURCES-TYPES.txt IPV6-TC.txt NET-SNMP-VACM-MIB.txt SNMP-TARGET-MIB.txt UCD-DISKIO-MIB.txt
IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt IPV6-UDP-MIB.txt NETWORK-SERVICES-MIB.txt SNMP-USER-BASED-SM-MIB.txt UCD-DLMOD-MIB.txt
IANAifType-MIB.txt ISILON-MIB.txt NOTIFICATION-LOG-MIB.txt SNMP-USM-AES-MIB.txt UCD-IPFWACC-MIB.txt
IANA-LANGUAGE-MIB.txt ISILON-TRAP-MIB.txt RFC1155-SMI.txt SNMP-USM-DH-OBJECTS-MIB.txt UCD-SNMP-MIB.txt
IANA-RTPROTO-MIB.txt LM-SENSORS-MIB.txt RFC1213-MIB.txt SNMPv2-CONF.txt UDP-MIB.txt
IF-INVERTED-STACK-MIB.txt MTA-MIB.txt RFC-1215.txt SNMPv2-MIB.txt
Re: Port name is different than "Status Information"
Hi,
That is why I was wondering if there was a firmware upgrade on the switch, since nothing changed
on the Nagios server. Do you know why the switch was re-booted? If there wasn't a firmware
upgrade is it possible the security on the switch was changed?
Thanks
That is why I was wondering if there was a firmware upgrade on the switch, since nothing changed
on the Nagios server. Do you know why the switch was re-booted? If there wasn't a firmware
upgrade is it possible the security on the switch was changed?
Thanks
Re: Port name is different than "Status Information"
This switch was rebooted due to the power outage. However, I delete that monitoring from Nagios and then rerun the wizard. Now miss-matching of the names have been resolved. But this is not a good way.
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?
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?
Re: Port name is different than "Status Information"
I think when Cisco switch reboot. It change/reset the status/description/index numbers of the ports. But Nagios was still using the old data/index numbers. That is why Nagios complaining about ports.