The time was a coincidence...he seems to have been caught in a Loss of sync
on the T1 he was coming in on (its count is now 2...one more than at the
midnight checkpoint).
While looking at this in the logs, I found that
1. There is no RADIUS item (Lucent 2.0.1 RADIUS; ComOS 3.8.2) for the
Acct-Termination-Cause
in case of a termination for this reason:
Mon Apr 26 09:26:18 1999
Acct-Session-Id = "38000EF7"
User-Name = "xxx"
NAS-IP-Address = y.y.y.y
NAS-Port = 6
NAS-Port-Type = Async
Acct-Status-Type = Stop
Acct-Session-Time = 1194
Acct-Authentic = RADIUS
Connect-Info = "28800 LAPM/V42BIS"
Acct-Input-Octets = 41410
Acct-Output-Octets = 2493223
Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = z.z.z.z
Acct-Delay-Time = 0
Timestamp = 925143978
And I found that the syslog record is the place to look:
Apr 26 09:26:06 aaa portmaster: port S6 terminated - No Event Identified
Which implies that the syslog is the place to look for users disconnected
due to Loss of sync. (There were a bunch of these, for the calls active at
the time.)
--------
2. Not all "Loss of sync" events terminate calls. I say that somewhat
strongly, since I was once connected via a channel in a T1 which
incremented its Loss of sync count, without being dropped. This may be
specific to CT1 lines (all we could get until recently).
I hope this helps someone (if it doesn't, it just constitutes "noise" on
the mailing list).
--John
John Baxter
General OlympusNet messages to: tcijb@olympus.net
OlympusNet Tech Support for Macintosh: mac-support@olympus.net
(360)385-0464 or (800)896-1751
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>