On Friday 13 March 2009 19:21:31 John Khvatov wrote:
Hi folks,
I'm working to improve python bindings. Already done:
* Session rewritten in C (removed a lot of unsafe transfers from python
to C and vice versa.
* Added exceptions for errors handling
* Reviewed/refactored/rewritten half
Hi,
I have been integrating NetSNMP 5.4.2.1 with quagga-0.99.11 (bgpd).
Based on the referred doc
I wrote
smuxpeer .1.3.6.1.4.1.3317.1.2.2 mypasswordin snmpd.conf
and
smux peer .1.3.6.1.4.1.3317.1.2.2 mypassword in bgpd.conf
but found the error
SMUX_CLOSE
On Fri, 13 Mar 2009 12:00:09 -0700 Tushar wrote:
TG Is the ifStatus down?
TG
TG
TG The interface is not down, but is removed using the command:
right.. but I'm asking about the net-snmp ifStatus.
TG It is not an issue to keep the entry if the vlan interface is down. But
TG the entry
The interface MIB is restricted at present to 10/100/1000 Mbit
ethernet interfaces on Linux. Ethtool now supports 10G and other speeds.
The convention is to check only for 0 and -1 as unknown speeds
diff --git a/agent/mibgroup/if-mib/data_access/interface_linux.c
TG Is there a reason the cache is not invalidated before calling
TG _cache_load()?
Yes.. the old entries are needed to
a) implement 64 bit counters (esp on 32 bit systems)
b) notice when interfaces appear and disappear
If you look at the code, it wouldn't be too to add code to remove
Thanks Robert for the response. I sent a reply few minutes ago when I
had not seen this email.
I will look closer at the net-snmp ifStatus of the interfaces and see
how to use the known_missing flag. IMO, a distinction needs to be made
between interfaces that have ifStatus down vs
Hi Robert,
Looking at the _check_interface_entry_for_updates() function, I realize
now, how the 'missing' interfaces are handled. Sorry about the
confusion on the interface status.
For now, I will post a patch that utilizes the known_missing flag so
that the 'missing' interfaces are not in
