Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Interface\s+Availability\s+on\s+Routers\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Interface\s+Availability\s+on\s+Routers\s*$/: 4 ]

Total 4 documents matching your query.

1. Interface Availability on Routers (score: 1): Author: Ken Guettler <Ken.Guettler AT maryville DOT com>; Date: Thu, 27 Apr 2000 13:40:19 -0500; Does anyone have suggestions on providing interface availability data for Cisco routers. The remote polling from NetView has not been very accurate due to heavy network traffic and router utilization; /usr/local/webapp/mharc-adsm.org/html/nv-l/2000-04/msg00382.html (11,286 bytes)
2. RE: Interface Availability on Routers (score: 1): Author: "Joel A. Gerber" <joel.gerber AT usaa DOT com>; Date: Thu, 27 Apr 2000 13:56:37 -0500; Since you have Essentials, check out the Availability reports that it has. They're pretty "primitive", and Essentials has to poll the device just like NetView, so it may not be any more reliable. As; /usr/local/webapp/mharc-adsm.org/html/nv-l/2000-04/msg00383.html (12,285 bytes)
3. RE: Interface Availability on Routers (score: 1): Author: "Boyles, Gary P" <gary.p.boyles AT intel DOT com>; Date: Thu, 27 Apr 2000 13:43:00 -0700; Ken, One thing which has helped minimize the false-reports for us on NetView NT... is to set the ping timeouts to something like: 1st = 5 sec, 2nd = 30 sec, 3rd = 7 sec. The thought behind this is to; /usr/local/webapp/mharc-adsm.org/html/nv-l/2000-04/msg00387.html (13,117 bytes)
4. RE: Interface Availability on Routers (score: 1): Author: elig AT bezeq DOT com; Date: Sun, 30 Apr 2000 11:42:53 +0200; You might need to adopt a "reactive" approach. The routers will send Netview interface-down traps if you configure your SNMP statements properly. You can then run an automatic script based on these t; /usr/local/webapp/mharc-adsm.org/html/nv-l/2000-04/msg00414.html (11,856 bytes)

Current List: 1 - 4
Page: [1]