* This is the VOP Radius mailing list *
OK,
 I was looking for some mib but what you are saying is what we have the READ COMM = 
xxxxx under the snmp options set to. Correct ?

-Butch

*********** REPLY SEPARATOR  ***********

On 8/21/2003 at 11:32 AM Erik Tijburg wrote:

>* This is the VOP Radius mailing list *
>What ever one you set in the box.
>
>Erik
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>On Behalf Of Butch Andrews
>Sent: Thursday, August 21, 2003 11:35 AM
>To: [EMAIL PROTECTED]
>Subject: [VOPRadius] Simultaneous login limit exceeded!
>
>
>* This is the VOP Radius mailing list *
>If switching over to SNMP what community string would be correct for
>Ascend Max MX60's?
>-Butch
>
>*********** REPLY SEPARATOR  ***********
>
>On 8/21/2003 at 10:41 AM Terry Trumbo wrote:
>
>>* This is the VOP Radius mailing list *
>>Under the clients tab. Edit one of your clients and you should see snmp
>>option there.
>>
>>Terry
>>
>>-----Original Message-----
>>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]
>>On Behalf Of Joe
>>Sent: Thursday, August 21, 2003 8:20 AM
>>To: [EMAIL PROTECTED]
>>Subject: [VOPRadius] Simultaneous login limit exceeded!
>>
>>
>>* This is the VOP Radius mailing list *
>>Where exactly are you enabling SNMP?
>>
>>Joe
>>----- Original Message -----
>>From: "Terry Trumbo" <[EMAIL PROTECTED]>
>>To: <[EMAIL PROTECTED]>
>>Sent: Wednesday, August 20, 2003 8:25 PM
>>Subject: [VOPRadius] Simultaneous login limit exceeded!
>>
>>
>>> * This is the VOP Radius mailing list *
>>> The only way I have found to get around this is use SNMP. Probably
>not
>>
>>> the best way but it does work.
>>>
>>> Terry
>>> ----- Original Message -----
>>> From: "Benjamin Tompkins" <[EMAIL PROTECTED]>
>>> To: <[EMAIL PROTECTED]>
>>> Sent: Wednesday, August 20, 2003 6:52 PM
>>> Subject: [VOPRadius] Simultaneous login limit exceeded!
>>>
>>>
>>> > * This is the VOP Radius mailing list *
>>> > I am experiencing the same problem without using watchdog packets.
>I
>>
>>> > can
>>> go
>>> > back and verify in the logs that we have received stop packets for
>>> > the users, sometimes the session referenced in the simultaneous
>>> > login is a
>>few
>>> > days old. I haven't reported the problem yet, but was planning on
>>looking
>>> > into it deeper tomorrow.
>>> >
>>> > Benjamin Tompkins
>>> > Blue One Communications, Inc.
>>> >
>>> >
>>> > The following seems to be occurring several times a day now: Using
>>> > watchdog packets a customer hangs up with a clean "45" code then
>>> > another watchdog packet is logged and as you can see from the
>sample
>>
>>> > log
>>2
>>> > hours and 24 minutes later they try to log in and are blocked with
>>> > Simultaneous login limit exceeded! Has anyone run into this
>problem?
>>
>>> > The important points are bold and underlined.
>>> >
>>> > Thanks for any help.
>>> >
>>> > (Debug   :01220) 8/20/2003 9:15:53 Add.Info: Nas=65.163.35.6
>>(ID:<none>),
>>> > Port=20107, User=emstt
>>> >  Acct SQL: INSERT INTO Accounting (LogDate, LogTime, UserName,
>>> NasIPAddress,
>>> > NasPortID, FramedProtocol, FramedAddress, AcctStatusType,
>>> > AcctDelayTime, AcctInputOctets, AcctOutputOctets, AcctSessionTime,
>>> > AcctInputPackets, AcctOutputPackets, AcctTerminateCause,
>>> > NasPortType, ConnectInfo) VALUES
>>> >
>>>
>>('2003-08-20','09:15:53','emstt','65.163.35.6',20107,'PPP','65.163.68.4
>1
>>','W
>>> > atchDog',9,800975,3334693,5133,21554,8374,'1','Async',24000)
>>> >  8232C53C0108656D73747400040641A3 .2.<..emstt...A.
>>> >   (  1) User-Name = [6]"emstt\000"
>>> > (Debug   :01220) 8/20/2003 9:18:48 Add.Info: Nas=65.163.35.6
>>(ID:<none>),
>>> > Port=20107, User=emstt
>>> >  Upd_User_State: Found User emstt nas_ip: 65.163.35.6 nas_port:
>>> > 20107 newstate:End  Acct SQL: INSERT INTO Accounting (LogDate,
>>> > LogTime, UserName,
>>> NasIPAddress,
>>> > NasPortID, FramedProtocol, FramedAddress, AcctStatusType,
>>> > AcctDelayTime, AcctInputOctets, AcctOutputOctets, AcctSessionTime,
>>> > AcctInputPackets, AcctOutputPackets, AcctTerminateCause,
>>> > NasPortType, ConnectInfo) VALUES
>>> >
>>>
>>('2003-08-20','09:18:48','emstt','65.163.35.6',20107,'PPP','65.163.68.4
>1
>>','S
>>> > top',0,801747,3335740,5317,21585,8386,'45','Async',24000)
>>> >  2BA6974C0108656D73747400040641A3 +..L..emstt...A.
>>> >   (  1) User-Name = [6]"emstt\000"
>>> > (Debug   :01220) 8/20/2003 9:18:53 Add.Info: Nas=65.163.35.6
>>(ID:<none>),
>>> > Port=20107, User=emstt
>>> >  Acct SQL: INSERT INTO Accounting (LogDate, LogTime, UserName,
>>> NasIPAddress,
>>> > NasPortID, FramedProtocol, FramedAddress, AcctStatusType,
>>> > AcctDelayTime, AcctInputOctets, AcctOutputOctets, AcctSessionTime,
>>> > AcctInputPackets, AcctOutputPackets, AcctTerminateCause,
>>> > NasPortType, ConnectInfo) VALUES
>>> >
>>>
>>('2003-08-20','09:18:53','emstt','65.163.35.6',20107,'PPP','65.163.68.4
>1
>>','W
>>> > atchDog',10,801730,3335732,5313,21583,8385,'1','Async',24000)
>>> >  083E90DA0108656D7374740002071F04 .>....emstt.....
>>> >  Create User: nas_ip: 65.163.35.7 nas_port: 20414 name: emstt
>>> newstate:Auth
>>> >  update_user: nas_ip: 65.163.35.7 nas_port: 20414 name: emstt
>>> newstate:Auth
>>> >  2F2F34314133323330432F656D737474 //41A3230C/emstt
>>> > 2F0108656D73747400021231B5313000 /..emstt...1.10.
>>> >   (  1) User-Name = [6]"emstt\000"
>>> > (Debug   :01220) 8/20/2003 11:42:02 Add.Info: Nas=65.163.35.7
>>(ID:<none>),
>>> > Port=20414, User=emstt
>>> >   ( 33) Proxy-State =
>>[43]"VPRR00365.163.35.7:20414/1//41A3230C/emstt/"
>>> >   (  1) User-Name = [6]"emstt\000"
>>> >  SQL Query: SELECT UserName, Password, ServiceType, SessionLimit,
>>> IdleLimit,
>>> > StaticIP, Netmask, FramedRoute, FilterID, PortLimit, SpeedLimit,
>>> > Analog, Digital, ExpirationDate, Profiles FROM Authentication WHERE
>
>>> > UserName = 'emstt'
>>> > (Debug   :01300) 8/20/2003 11:42:02 User emstt is already online on
>>NAS
>>> > 65.163.35.6:20107
>>> > (Reject  :01300) 8/20/2003 11:42:02 Invalid Attempt:
>>> > [65.163.35.7:20414] emstt - Simultaneous login limit exceeded!
>>> >
>>> >
>>> >
>>> > **
>>> > To leave this list, send an email to [EMAIL PROTECTED]
>>> > and put the word "LEAVE" in the BODY of the email.
>>>
>>>
>>> **
>>> To leave this list, send an email to [EMAIL PROTECTED] and
>
>>> put the word "LEAVE" in the BODY of the email.
>>
>>
>>**
>>To leave this list, send an email to [EMAIL PROTECTED] and
>>put the word "LEAVE" in the BODY of the email.
>>
>>
>>**
>>To leave this list, send an email to [EMAIL PROTECTED]
>>and put the word "LEAVE" in the BODY of the email.
>
>
>
>
>**
>To leave this list, send an email to [EMAIL PROTECTED]
>and put the word "LEAVE" in the BODY of the email.
>
>
>**
>To leave this list, send an email to [EMAIL PROTECTED]
>and put the word "LEAVE" in the BODY of the email.




**
To leave this list, send an email to [EMAIL PROTECTED]
and put the word "LEAVE" in the BODY of the email.

Reply via email to