Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: (ASCEND) SNMP for Max4004

The SNMP disconnect of a session is absolutely available. The variable, ssnActiveValidFlag, is in the session MIB attached:
ssnActiveValidFlag  OBJECT-TYPE
	SYNTAX		INTEGER {
			    invalid(1),
			    valid(2)
			}
	ACCESS		read-write
	STATUS		mandatory
	DESCRIPTION	"All entries will be valid(2).
                         Refer to ssnStatusValidFlag for more information.
                         Setting a vaild(2) session as invalid(1) causes
                         an effective session termination."
	::= { sessionActiveEntry 3 }

 
Ken 
-----Original Message-----
From:	Brett Hawn [SMTP:blh@texas.net]
Sent:	Tuesday, January 13, 1998 5:30 PM
To:	Daniel; ascend-users@bungi.com
Subject:	Re: (ASCEND) SNMP for Max4004

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.


On Tue, Jan 13, 1998 at 02:46:32PM -0800, Daniel made some electrons appear in the following form:
> Hi there,
> 
> I am working on a Perl script which can hangup a user using SNMP. Can
> anyone show me which SNMP object I should use?
> 
> Thanks
> 
> Daniel
> 
> ++ Ascend Users Mailing List ++
> To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd:	<http://www.nealis.net/ascend/faq>

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

session.mib

Follow-Ups: