------=_NextPart_000_0068_01BFC58D.D74AD710
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
this is what i use in the script just insert the ip address of the nas i
always star wit a1 as the added part of the id if you have to use it again
changed to b2 or c3 ..... as it will not do right if it repeats itself
----- Original Message -----
From: "NCKCN" <ttuttle@nckcn.com>
To: <emerald@iea-software.com>
Sent: Wednesday, May 24, 2000 2:30 PM
Subject: Re: [Emerald] Radius will not acknowledge STOP account record
> Paul,
>
> Thanks. This must be what has happened. I do need to track the online
time.
> Do you have a copy of the scripts you use to accomplish this?
>
>
> -----------------------------------------------------------------
> Thanks,
> TKT
> -----------------------------------------------------------------
>
> ----- Original Message -----
> From: "Paul Bennett" <pbennett@tnns.net>
> To: <emerald@iea-software.com>
> Sent: Wednesday, May 24, 2000 2:27 PM
> Subject: Re: [Emerald] Radius will not acknowledge STOP account record
>
>
> > we run into this a lot when a machine needs to be rebooted here is what
i
> > have found
> >
> > when the nas restarts it reuses session id #'s in the calls tables and
> when
> > the start records are deleted each night the sessionid's are recorded
> > correctly as a new call then whenm the stop record comes in it sees one
> > there with the same id and gets rejected there fore the call never gets
> > stopped in the eyes of the calls table we ussually just del the calls
> > assoiated with that nas when ever this happens that way there are no
> > duplicates in the calls tables or you can run a script th modify the
> > existing session ids for that nas if you need to keep track of time
online
> >
> >
> > ----- Original Message -----
> > From: "TKT" <ttuttle@nckcn.com>
> > To: "Emerald Discussion" <emerald@iea-software.com>
> > Sent: Wednesday, May 24, 2000 1:39 PM
> > Subject: [Emerald] Radius will not acknowledge STOP account record
> >
> >
> > > This is an odd development today. We had to take one of our NASs, 3Com
> > Total
> > > Control, off-line because of electrical power work. When we restarted
> the
> > > NAS, having changed nothing in the NAS, nothing in Radius nor anything
> in
> > > SQL; RadiusNT/Emerald refuses to acknowledge any users' disconnects
even
> > > though a STOP record is sent. SNMP Concurrency will not work either.
If
> I
> > > point that NAS to our old "reliable" RADIUS backup, everything works
> > > perfectly. I have restarted the NAS, RadiusNT and SQL server, and
still
> > when
> > > anyone dials into that NAS, disconnects as usual, RadiusNT/Emerald
will
> > keep
> > > them listed with an AccountStatus of 1 and not let them connect again
> > until
> > > I manually clear them from the Emerald on-line. I have included the
> > > Accounting log and Authentication log I recorded to illustrate. When I
> > > dialed in and disconnected the NAS shows the connection as gone, but
> > > RadiusNT/Emerald holds the connection open forever.
> > >
> > > Auth Log...
> > >
> > > radrecv: Request from host cefd3c14 (tcm-belleville) code=1, id=121,
> > > length=96 User-Name = "testboy"
> > > Challenge-Response =
> > > "\003V\026\352\351\275\371\365\374\035!\303\323[v>d"
> > > NAS-Identifier = 206.253.60.20
> > > NAS-Port = 267
> > > Acct-Session-Id = "17432578"
> > > User-Service = Framed-User
> > > Framed-Protocol = PPP
> > > Caller-Id = ""
> > > NAS-Port-DNIS = "5057"
> > > NAS-Port-Type = Async
> > > May 23 19:14:40 2000 [INFO]: SQL Statement: {CALL RadGetConfigs(2489)}
> > > Checking for duplicate logins.
> > > May 23 19:14:40 2000 [INFO]: SQL Statement: {CALL
> > RadCheckOnline('testboy')}
> > > May 23 19:14:40 2000 [INFO]: testboy found on-line 0 time(s).
> > > Sending Ack of id 121 to cefd3c14 (tcm-belleville) User-Service =
> > > Framed-User
> > > Framed-Protocol = PPP
> > > Session-Timeout = 18000
> > > Idle-Timeout = 900
> > > Class = "IEAS1\00424892\0019"
> > > Resp Time: 32 Auth: 28/6 -> 34 Acct: 76/0/0 -> 76
> > >
> > > radrecv: Request from host cefd3c14 (tcm-belleville) code=1, id=123,
> > > length=96 User-Name = "testboy"
> > > Challenge-Response =
> "\003\202\332\313\351W\305\032\372'o/\223\0278Oq"
> > > NAS-Identifier = 206.253.60.20
> > > NAS-Port = 265
> > > Acct-Session-Id = "17301506"
> > > User-Service = Framed-User
> > > Framed-Protocol = PPP
> > > Caller-Id = ""
> > > NAS-Port-DNIS = "5057"
> > > NAS-Port-Type = Async
> > > Checking for duplicate logins.
> > > May 23 19:15:13 2000 [INFO]: SQL Statement: {CALL
> > RadCheckOnline('testboy')}
> > > May 23 19:15:13 2000 [INFO]: testboy found on-line 1 time(s).
> > > May 23 19:15:13 2000 [INFO]: SQL Statement: {CALL
> > > RadCheckOnlineSNMP('testboy')}
> > > Sending Reject of id 123 to cefd3c14 (tcm-belleville) May 23 19:15:13
> 2000
> > > [NOTICE]: User: testboy already logged onto system 1 time(s).
> > > Resp Time: 16 Auth: 32/8 -> 40 Acct: 85/0/0 -> 85
> > >
> > > Acct Log...
> > > radrecv: Request from host cefd3c14 (tcm-belleville) code=4, id=200,
> > > length=116 Class = "IEAS1\00424892\0019"
> > > User-Name = "testboy"
> > > NAS-Identifier = 206.253.60.20
> > > Acct-Status-Type = Start
> > > Acct-Session-Id = "17432578"
> > > Acct-Delay-Time = 0
> > > Acct-Authentic = RADIUS
> > > User-Service = Framed-User
> > > NAS-Port-Type = Async
> > > NAS-Port = 267
> > > Caller-Id = ""
> > > NAS-Port-DNIS = "5057"
> > > Framed-Protocol = PPP
> > > Framed-Address = 209.42.75.184
> > > Sending Accounting Ack of id 200 to cefd3c14 (tcm-belleville)
> > > Resp Time: 0 Auth: 28/6 -> 34 Acct: 77/0/0 -> 77
> > >
> > > radrecv: Request from host cefd3c14 (tcm-belleville) code=4, id=201,
> > > length=152 Class = "IEAS1\00424892\0019"
> > > User-Name = "testboy"
> > > NAS-Identifier = 206.253.60.20
> > > Acct-Status-Type = Stop
> > > Acct-Session-Id = "17432578"
> > > Acct-Delay-Time = 0
> > > Acct-Authentic = RADIUS
> > > User-Service = Framed-User
> > > NAS-Port-Type = Async
> > > NAS-Port = 267
> > > Caller-Id = ""
> > > NAS-Port-DNIS = "5057"
> > > Framed-Protocol = PPP
> > > Framed-Address = 209.42.75.184
> > > Acct-Session-Time = 4
> > > Acct-Terminate-Cause = User-Request
> > > Acct-Input-Octets = 329
> > > Acct-Output-Octets = 272
> > > Acct-Input-Packets = 13
> > > Acct-Output-Packets = 12
> > > Sending Accounting Ack of id 201 to cefd3c14 (tcm-belleville)
> > > Resp Time: 0 Auth: 28/7 -> 35 Acct: 78/0/0 -> 78
> > > ===========
> > >
> > > Any ideas? Why is the STOP record, that works for all other NAS's, not
> > > updating the calls table.
> > >
> > >
> > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > > Thanks,
> > > TKT
> > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > >
> > >
> > > For more information about this list (including removal) go to:
> > > http://www.iea-software.com/support/maillists/liststart
> >
> >
> > For more information about this list (including removal) go to:
> > http://www.iea-software.com/support/maillists/liststart
>
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
------=_NextPart_000_0068_01BFC58D.D74AD710
Content-Type: application/octet-stream;
name="UpdateSessionIDs_afterTSReboot.SQL"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="UpdateSessionIDs_afterTSReboot.SQL"
update Calls
set AcctSessionID='d4' + AcctSessionID
WHERE NASIdentifier ='xxx.xxx.xxx.xxx'
------=_NextPart_000_0068_01BFC58D.D74AD710--