Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) SNMP for Max4004
On Tue, Jan 13, 1998 at 07:29:39PM -0600, Brett Hawn wrote:
> Won't happen, Ascend decided that part of the MIB should 'go away', There
> used to be a non-operational oid called doHangUp, but thats since been
> removed.
doHangup was a bit of a strange thing and never really worked on
most platforms anyway. There will be a replacement, see 6.0b release
notes for details. It works by setting the ssnStatusValidFlag in
the sessionTable to invalid:
ssnStatusValidFlag OBJECT-TYPE
SYNTAX INTEGER {
invalid(1),
valid(2)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION "Value indicates whether this entry contains valid
information or not. Setting a valid(2) session to invalid(1)
causes an effective session termination."
::= { sessionStatusEntry 2 }
IMHO this solution is more consistent with the whole enterprise MIB
and the way SNMP works. Hopefully it will then work on every Ascend
box with SNMP, from Pipes upward.
--
Kanther-Line: PGP SSH IDEA MD5 GOST RIPE-MD160 3DES RSA FEAL32 RC4
+-o-+--------------------------------------------------------+-o-+
| o | \\\- Brain Inside -/// | o |
| o | ^^^^^^^^^^^^^^ | o |
| o | Andre' Beck (ABPSoft) beck@ibh-dd.de XLink PoP Dresden | o |
+-o-+--------------------------------------------------------+-o-+
++ 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: