I will slightly modify my question. Where are information used for IF-MIB table taken from?
Regards Josef Ridky Associate Software Engineer Core Services Team Red Hat Czech, s.r.o. ----- Original Message ----- | From: "Josef Ridky" <jri...@redhat.com> | To: "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> | Cc: net-snmp-coders@lists.sourceforge.net | Sent: Friday, May 26, 2017 8:37:11 AM | Subject: Re: Antw: IF-MIB::ifOperStatus wtih ifup/ifdown commands | | | ----- Original Message ----- | | From: "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> | | Sent: Friday, May 26, 2017 8:13:37 AM | | | | I don't know whether this is fixed already, but in net-snmp-5.4.2.1 there | | is | | the problem that after restarting the network stack, bonding and bridge | | devices appear twice (with the same name), but with different status... | | | | This issue was reported from net-snmp-5.7.3 | | Josef | | | >>> Josef Ridky <jri...@redhat.com> schrieb am 25.05.2017 um 15:12 in | | >>> Nachricht | | <87738501.15716165.1495717967019.javamail.zim...@redhat.com>: | | > Hi, | | > | | > I would like to ask you for your opinion/hint about this report: | | > | | > ------- BEGIN ------- | | > Description of problem: | | > SNMP IF-MIB::ifOperStatus doesn't report correct status of NIC if it is | | > brought down with ifdown command | | > | | > Steps to Reproduce: | | > 1. Install net-snmp | | > 2. Bring down network interface using ifdown | | > 3. Execute $snmpwalk -v 2c -c public localhost interface | | > | | > Actual results: | | > net-snmp reports incorrect ifOperStatus | | > | | > Expected results: | | > net-snmp should reports correct ifOperStatus | | > | | > Additional info: | | > | | > [root@dhcp5-123 ~]# ifdown eth0 | | > Device 'eth0' successfully disconnected. | | > | | > [root@dhcp5-123 ~]# snmpwalk -v2c -c public localhost | | > .1.3.6.1.2.1.2.2.1.2 | | > IF-MIB::ifDescr.1 = STRING: lo | | > IF-MIB::ifDescr.2 = STRING: ens3 | | > IF-MIB::ifDescr.3 = STRING: virbr0 | | > IF-MIB::ifDescr.4 = STRING: virbr0-nic | | > IF-MIB::ifDescr.5 = STRING: eth0 | | > | | > [root@dhcp5-123 ~]# snmpwalk -v2c -c public localhost | | > .1.3.6.1.2.1.2.2.1.8 | | > IF-MIB::ifOperStatus.1 = INTEGER: up(1) | | > IF-MIB::ifOperStatus.2 = INTEGER: up(1) | | > IF-MIB::ifOperStatus.3 = INTEGER: down(2) | | > IF-MIB::ifOperStatus.4 = INTEGER: down(2) | | > IF-MIB::ifOperStatus.5 = INTEGER: up(1) | | > | | > ------- End ------- | | > | | > I have found, that in case, the LAN cable is physically unplugged, than | | > ifOperStatus is correct. | | > However, when are used ifup/ifdown commands, than ifOperStatus is wrong. | | > | | > Do you have any workaround or hint how can be this issue solved? | | > | | > Regards | | > | | > Josef Ridky | | > Associate Software Engineer | | > Core Services Team | | > Red Hat Czech, s.r.o. | | > | | > | | > ------------------------------------------------------------------------------ | | > Check out the vibrant tech community on one of the world's most | | > engaging tech sites, Slashdot.org! http://sdm.link/slashdot | | > _______________________________________________ | | > Net-snmp-coders mailing list | | > Net-snmp-coders@lists.sourceforge.net | | > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders | | | | | | | | | | | | ------------------------------------------------------------------------------ | Check out the vibrant tech community on one of the world's most | engaging tech sites, Slashdot.org! http://sdm.link/slashdot | _______________________________________________ | Net-snmp-coders mailing list | Net-snmp-coders@lists.sourceforge.net | https://lists.sourceforge.net/lists/listinfo/net-snmp-coders | ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
