Thanks Wes for the acceptance. I was under the impression that I need
to get the approval here before I submit the patch on
net-snmp.org/patches. Will submit to both the places the next time. :)
- Tushar
Wes Hardaker wrote:
>>>>>> On Fri, 17 Apr 2009 08:26:13 -
Folks,
Any comments on the patch below? Without the patch, traps for events
such as linkup/down are seen multiple times upon reconfig on SIGHUP.
Many thanks,
- Tushar
Tushar Gohad wrote:
> On a SIGHUP, clear_mteTTable() clears trigger_table_data but the
> mteTrigger entries
On a SIGHUP, clear_mteTTable() clears trigger_table_data but the
mteTrigger entries remain registered in the POST_READ_CONFIG callbacks
table. This causes multiple trap notifications for the same event when
a SIGHUP is issued to snmpd.
The patch below makes sure that the callbacks for the mteT
Hello folks,
The following patch uses the known_missing flag to make sure that the
transient interfaces that are known to have gone away are not sent in
response to GET* requests. If it is an acceptable solution to the
missing-interfaces-being-displayed-by-snmpwalk problem, I will post it
to
tri->colnum);
+else {
+requests->requestvb->type = SNMP_NOSUCHINSTANCE;
+rc = SNMP_ERR_NOERROR;
+}
+
if (rc) {
if (MFD_SKIP == rc) {
requests->requestvb->type = SNMP_NOSUCHINSTANC
nterfaces are not in response to the GET* requests.
Many thanks,
- Tushar
Tushar Gohad wrote:
>
> 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
> h
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 interfaces
>
> 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
> TG> IF-MIB::ifName.36 = STRING: eth0.100 <=== stale entry
>
> Is the ifStatus down?
>
The interface is not down, but is removed using the command:
'vconfig rem eth0.100'
so it is non-existent.
> TG> Is there a reason the cache is not invalidated before calling
> TG> _cach
Folks,
Does the ifTable cache have the DONT_FREE_BEFORE_LOAD and
DONT_FREE_EXPIRED flags set on purpose? (Reference:
agent/mibgroup/if-mib/ifTable/ifTable_data_access.c:149).
These flags are causing stale VLAN interface entries being reported.
# snmpwalk localhost ifName
IF-
Hello folks,
The attached patch adds write support for the ipForwarding and
ipDefaultTTL objects to net-snmp. The patch should be applied on top of
the latest net-snmp SVN tree.
Any feedback is welcome.
Thanks,
- Tushar Gohad
Index: net-snmp/README.agent-mibs
11 matches
Mail list logo
