We have 4 PM-3's that have worked nicely for our dialup users
since December 1996 (except for the initial modem problems) and now we
would like to replace our MAXen (which we use for our dedicated customers)
with PM3's. The one thing that concerns the bizniz ppl is that we have
scripts now that generate reports from the detail file that show the
percentage of online time a user has spent in multilink. This is trivial
with Ascend's VSA 'Ascend-Multilink-Id' but Livingston provides no
mechanism to do this. RADIUS was, as we all know, developed by
Livingston... the chair of the RADIUS working group and author of the IETF
RADIUS draft (and later RFC), Carl Rigney (who also works for Livingston)
gave us this:
5.11. Acct-Multi-Session-Id
Description
This attribute is a unique Accounting ID to make it easy to link
together multiple related sessions in a log file. Each session
linked together would have a unique Acct-Session-Id but the same
Acct-Multi-Session-Id. It is strongly recommended that the Acct-
Multi-Session-Id be a printable ASCII string.
A summary of the Acct-Session-Id attribute format is shown below.
The fields are transmitted from left to right.
0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | String ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
50 for Acct-Multi-Session-Id.
Length
>= 3
String
The String field SHOULD be a string of printable ASCII characters.
Acct-Link-Count is another nice ATTRIB that would come in quite handy for
us.
I am for the moment adapting a script I had previously used to prevent and
report concurrent logins to check start and stop records to give a
"time in multilink" total for a given user but would still prefer to have
the actual accounting record.
Anyone else?
Scott VanRavenswaay
Network Administrator
DFW Internet Services, Inc.