Title: RE: (RADIATOR) SNMP session check for Cisco ISDN (Sync PPP) users

Hello Hugh,

I used to have the same problem and changed the MIB path(.iso.org.dod.internet.private.enterprises.9) to its numerical value (.1.3.6.1.4.1.9) in NAS.pm .

I do not get any noSuchName error anymore...

But this did not make any sense to me!!!

Regards,

Tuncay Margilic
Siemens Business Sevices
System Admin.


-----Original Message-----
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 19, 2000 2:39 AM
To: Nikos Aslanakis; [EMAIL PROTECTED]
Subject: Re: (RADIATOR) SNMP session check for Cisco ISDN (Sync PPP)
users



Hello Nikos -

On Sat, 19 Feb 2000, Nikos Aslanakis wrote:
> We have a problem when radiator tries to double check a Cisco NAS using SNMP
> for an ISDN user.
> While it checks correctly all the NAS ports that are used for Async
> connections (analog dialup), when it tries to check the ports that are used
> for ISDN connections (normally ports 20000 and up), it fails allowing the
> same user to be connected twice.
>
> When I run snmpget from the command line for  the ISDN ports, I get the
> following response:
>
> #  /usr/local/bin/snmpget 195.66.100.149 xxxx
> .iso.org.dod.internet.private.enterprises.9.2.9.2.1.18.20101
> EError in packet
> Reason: (noSuchName) There is no such variable name in this MIB.
> This name doesn't exist: enterprises.9.2.9.2.1.18.20022
>
> This happens ONLY for the ISDN users. For the PSTN users snmpget works
> normally, correctly checking the Ciscos for double login attempts.
>

Yes - this is a well-known problem with Cisco's. If anyone can tell us how to
correlate the accounting attributes to an SNMP query for ISDN ports (or anything
else for that matter) we'll fix it.

regards

Hugh

--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody

===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to