Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*The\s+polling\s+process\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*The\s+polling\s+process\s*$/: 4 ]

Total 4 documents matching your query.

1. The polling process (score: 1): Author: erik nilsson <erik AT NETMAN DOT SE>; Date: Thu, 11 Feb 1999 11:41:59 +0100; When configuring the SNMP polling parameters we have decreased the polling intervall to 2min with the same time out (2 sec) and retry count (3) as default. Our network includes approx 500 interfaces; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-02/msg00221.html (12,031 bytes)
2. Re: The polling process (score: 1): Author: Leslie Clark <lclark AT US.IBM DOT COM>; Date: Thu, 11 Feb 1999 07:07:15 -0500; You got it. Add to what you have demonstrated the information that netmon can only have about 10 outstanding queries at a time. Too short a polling cycle and too high a timeout/retry, and only a few; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-02/msg00222.html (13,699 bytes)
3. The polling process (score: 1): Author: Anthony Philipp <philipt AT NATIONWIDE DOT COM>; Date: Thu, 11 Feb 1999 09:42:58 -0500; I believe the Netview polling process actually doubles the timeout value for each subsequent retry. If you have a timeout of 2 seconds, the first retry will wait 4 seconds, the next retry will wait 8; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-02/msg00225.html (12,737 bytes)
4. Re: The polling process (score: 1): Author: Leonard Bocock <leonard.bocock AT NZ.UNISYS DOT COM>; Date: Fri, 12 Feb 1999 11:34:11 +1200; I recommend you either; - Put MLM's out there if the WAN typology supports this or - write an event ruleset to call a shell script which pings the node a few times to make sure the node down trap is; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-02/msg00242.html (13,014 bytes)

Current List: 1 - 4
Page: [1]