trying to understand what are the parameter/output From debug SNMP timers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-31-2002 02:07 AM - edited 02-20-2020 10:27 PM
Hi All
I am trying to understand what are the parameter/output
From the debug SNMP timers
Output SNMP timers :
*Dec 31 11:56:27: SNMP: HC Timer 632DDE28 fired
*Dec 31 11:56:27: SNMP: HC Timer 632DDE28 rearmed, delay = 5000
*Dec 31 11:56:32: SNMP: HC Timer 632DDE28 fired
*Dec 31 11:56:32: SNMP: HC Timer 632DDE28 rearmed, delay = 5000
*Dec 31 11:56:37: SNMP: HC Timer 632DDE28 fired
*Dec 31 11:56:37: SNMP: HC Timer 632DDE28 rearmed, delay = 5000
*Dec 31 11:56:38: SNMP: HC Timer 70B54A70 fired
*Dec 31 11:56:38: SNMP: HC Timer 70B54A70 rearmed, delay = 20000
70B54A70 , 632DDE28 „² what this number means.
5000 , 20000 „² why I have different delay time ( does it means that I have delay for SNMP request )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2003 07:32 AM
The debug messages you are seeing are related to High-Capacity (HC) timers, which manage updates to 64-bit (HC) snmp counters as defined in RFC2233.
The "fired" and "rearmed" messages indicate when each of these timers
updates ("fired") the HC snmp counters, and when they should fire next
(the "rearmed" messages). Higher speed interfaces require updates more often than lower speed interfaces, so you see two examples of that in your debug messages - 5000 ms updates vs 20000 ms update.
The numbers that are in the messages (i.e. 632DDE28 ) are internal references to the timer that has fired.
These messages do not indicate any delay in SNMP message processing, but normal SNMP operation of HC counters.
