Re: (ASCEND) Re: SNMP Interface representation

To: Peter Lalor <plalor@infoasis.com>
Subject: Re: (ASCEND) Re: SNMP Interface representation
From: Phillip Vandry <vandry@Mlink.NET>
Date: Thu, 27 Nov 1997 09:54:43 -0500 (EST)
cc: ascend-users@bungi.com
In-reply-to: Your message of "Wed, 26 Nov 1997 17:44:58 EST." <v03130308b0a27fb2afd0@[206.40.74.6]>
Sender: owner-ascend-users@max.bungi.com

> I totally agree with this methodology. I don't care about the switched
> connections. I care about the nailed ones.

I would point out that I am also interested in some of the switched
(ISDN) connections (maybe this is not the case for you). The
dedicated ones. In the event that their connection briefly drops, they
should be assigned the same interface when they reconnect.

> The routine around here is: Max resets (pick a reason). Tech finds what T1
> profiles moved where and tells our SNMP bandwidth graphing app about it.
> Repeat.

Well, there are ways to find the dynamically assigned interface
ascociated with each connection, but:

- They are very expensive, involving many SNMP queries including (I think, if
I remember correctly) some walks.
- They have often given incorrect answers in the past due to bugs.

It's possible to build such automation into your software if it's made up
of Perl or TCL scripts, but not necesarily for sommercial stuff.

-Phil
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

References:

(ASCEND) Re: SNMP Interface representation

From: Peter Lalor <plalor@infoasis.com>

Prev by Date: Re: (ASCEND) Max 5.0Ap36
Next by Date: Re: (ASCEND) my idiocy knows no bounds
Prev by thread: (ASCEND) Re: SNMP Interface representation
Next by thread: Re: (ASCEND) Re: SNMP Interface representation
Index(es):
- Main
- Thread