I have some questions about the caching of hrSWRunTable. According to what I
see in the code (as mentioned by David) the hrSWRunTable is already being
cached. However, when I query the nsCache I'm not seeing it there:
jorhett@sj2-noc01 ~$ snmpwalk -c (snip) -v 2c localhost nsCache
NET-SNMP-AGENT-MIB::nsCacheDefaultTimeout.0 = INTEGER: 5
NET-SNMP-AGENT-MIB::nsCacheEnabled.0 = INTEGER: false(2)
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.2.2 = INTEGER: 30
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4 = INTEGER: 5
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4.24.4 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4.24.7 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4.31.1 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4.31.3 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4.32 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4.34 = INTEGER: 30
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4.35 = INTEGER: 15
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4.36 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.4.37 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.5 = INTEGER: 5
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.5.29 = INTEGER: 5
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.5.30 = INTEGER: 5
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.6 = INTEGER: 5
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.6.13 = INTEGER: 5
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.6.19 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.6.20 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.7 = INTEGER: 5
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.7.5 = INTEGER: 5
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.7.7 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.10.7.2 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.16.1.1 = INTEGER: 60
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.104.1.1 = INTEGER: 30
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.104.1.2 = INTEGER: 30
NET-SNMP-AGENT-MIB::nsCacheTimeout.1.3.6.1.2.1.104.1.3 = INTEGER: 30
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.2.2 = INTEGER: cached(4)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4.24.4 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4.24.7 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4.31.1 = INTEGER: cached(4)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4.31.3 = INTEGER: cached(4)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4.32 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4.34 = INTEGER: cached(4)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4.35 = INTEGER: cached(4)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4.36 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.4.37 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.5 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.5.29 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.5.30 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.6 = INTEGER: empty(3)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.6.13 = INTEGER: empty(3)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.6.19 = INTEGER: empty(3)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.6.20 = INTEGER: empty(3)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.7 = INTEGER: empty(3)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.7.5 = INTEGER: empty(3)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.7.7 = INTEGER: empty(3)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.10.7.2 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.16.1.1 = INTEGER: expired(5)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.104.1.1 = INTEGER: empty(3)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.104.1.2 = INTEGER: empty(3)
NET-SNMP-AGENT-MIB::nsCacheStatus.1.3.6.1.2.1.104.1.3 = INTEGER: cached(4)
So if this is being cached, why doesn't it show up in the cached table? And
how can I adjust the timeout for this data?
Also, I'm wondering if there was any effort to put the cache timeouts in the
configuration, to avoid having to do snmpset commands every time we start snmpd.
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source and other
randomness
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
