Cdr File Format - Extreme Networks Summit WM User Manual

NOTE
CDRs' file format and file types in the Summit WM20 Controller are identical to the Summit WM100/1000
Controller. For more information, see the Summit WM User Guide.
The CDR directory in the Summit WM100/1000 Controller contains eight subdirectories - one directory
for each day of the week and an additional working directory. You can backup and copy CDRs for the
previous seven days as the new records are being created for the current day in the working directory.
Each subdirectory can contain a maximum of 48 files. The maximum size of each file is 500 MB, and the
maximum time that a file can remain open is 30 minutes.
The CDR files are saved with .dat extension.

CDR file format

A CDR file contains a sequence of CDR records. The file is a standard ASCII text file. Records are
separated by a sequence of dashes followed by a line break. The individual fields of a record are
reported one per line, in "field=value' format.
The following table describes the records that are displayed in a CDR file.
NOTE
Most of the CDR records are typical RADIUS server attributes. For more information, refer to the user manual of your
RADIUS server.
Table 28: CDR Records and their description
CDR Records
Acct-Session-ID
User-Name
Filter-ID
Acct-Interim-Interval
Session-Timeout
Class
Acct-Status-Type
Acct-Delay-Time
Summit WM User Guide, Software Version 5.3
Description
A unique CDR ID
The name of the user, who was authenticated.
The name of the filter list for the user.
The number of seconds between interim accounting updates.
The maximum number of seconds of service to be provided to
the user before termination of the session.
This field is copied from the Access-Accept message sent by
the RADIUS server during authentication.
Indicates whether this Accounting-Request marks the
beginning of the user service (Start) or the end (Stop).
Indicates how many seconds the client tried to authenticate
send this record for, and can be subtracted from the time of
arrival on the server to find the approximate time of the event
generating this Accounting-Request.
289