Thanks for that Hector,
Can anyone shed some light on how this MIB is supposed to work, and how it is
that the AscendSNMP code is suddenly not working for some Ascends? It looks a
bit like the relationship between the NAS-Port in the radius request is no
longer an exact map to the SNMP index.
I sure would like to fix this if anyone can tell me enough to do so.
Cheers.
On Jul 15, 8:23pm, Hector Lopez wrote:
Subject: Re: (RADIATOR) Duplicate login control using AscendSNMP
Hi all,
Mike thanks for the help you gave me.
This is the continuation of the problem of duplicate logins using
AscendSNMP.
I think I found out what happens, the problem is that the port number that
radius gets is never correct.
For example the logfile says...
Session for wtpmfm at 207.41.108.20:20108 has gone away
if I do an snmpwalk on the Max I can see that user "wtpmfm" is in the port
93
enterprises.529.12.2.1.3.93 = "wtpmfm"
also, the port 20108 do not exists.
if I do an "snmpget [ip] [community]
iso.org.dod.internet.private.enterprises.529.12.2.1.3.20108" I get:
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
This name doesn't exist: enterprises.529.12.2.1.3.20108
if I do an "snmpget [ip] [community]
iso.org.dod.internet.private.enterprises.529.12.2.1.3.93" I get:
enterprises.529.12.2.1.3.93 = "wtpmfm"
if I do an "snmpget [ip] [community]
iso.org.dod.internet.private.enterprises.529.12.2.1.3.96" I get:
enterprises.529.12.2.1.3.96 = ""
Maybe this means I should never receive the error of "noSuchName" because if
someone had the "port" before then the answer should be blank.
I hope this helps someone figure how the problem can be resolved.
THANKS for your help.
- Original Message -
From: Mike McCauley [EMAIL PROTECTED]
To: Hector Lopez [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, July 16, 1999 10:14 AM
Subject: Re: (RADIATOR) Duplicate login control using AscendSNMP
Hello Hector,
On Jul 15, 8:11am, Hector Lopez wrote:
Subject: Re: (RADIATOR) Duplicate login control using AscendSNMP
Hi Mike,
The principal question I had is why when using AscendSNMP, when
Radiator tries to see if some user is still conected, it almost always
say
"the user has gone away" when most times the user is still
connected.so
I can not control duplicate logins using that method. It would be very
good
if this worked, I think maybe I have something wrong here.
Im sorry I misunderstood your question.
If Radiator is concluding that the session has gone away even when it is
still
up, then there is definitely a problem.
Can you confirm whether you get the "There is no such variable name in
this
MIB" error message even if the user is still online? If so, then either
that
SNMP MIB is not operating in your MAX, or there is some other problem. Can
you
check that please? I guess you have checked that your comminity is
correct.
The next time you see one of these, would you please try runnin ghte
snmpget by
hand like this:
snmpget xx.xx.xx.xx community
.iso.org.dod.internet.private.enterprises.529.12.2.1.3.portnumber
AscendSNMP works
with Ascend Max TNT's also?
Yes.
Does Radiator needs SNMP write access?
No.
Does ucd-snmp need any special
tunning or MIB?
Not usually, just the standard MIBs that get installed with ucd-snmp.
I hope we can help you fix this problem quickly, but please post your
correspondence to the mailing list: Im not the only one working on this
for
you.
Cheers.
This is the output in the logfile when that happens:
DEBUG: Checking if user is still online: AscendSNMP, test,
209.91.199.11,
20219, 275607700
DEBUG: Child reaped
DEBUG: Session for test at 209.91.199.11:20219 has gone away
-Original Message-
From: Mike McCauley [EMAIL PROTECTED]
To: Hector Lopez [EMAIL PROTECTED]
Date: Thursday, July 15, 1999 1:53 AM
Subject: Re: (RADIATOR) Duplicate login control using AscendSNMP
Hi Hector,
Yes, I would probably expect to see the SNMP error you mentioned if the
user
had actually disconnected.
With the Timestamp error, could you post some more information about
when
you
see this error. Perhaps more of the logfile, including the incoming
packet
dumps, and the rest of your config file (no secrets).
Cheers.
On Jul 14, 10:52am, Hector Lopez wrote:
Subject: (RADIATOR) Duplicate login control using AscendSNMP
Hi,
I am trying to set up Radiator to control duplicate logins. I
only
have read access for Radiator in my Max and TNTs.
I have this in my config file for testing it:
SnmpgetProg/usr/bin/snmpget
Client DEFA
