You might want to create a table to test with, parse your historical
detail logs and put them into the table.  This will help you determine
how big your table(s) will be and how well the db will perform
queries.

I'm in the process of deciding what to keep in our db.  Currently a
table that keeps less information than you list will hit the maximum
size limit for a MySQL table (4G) with about 6 months of data.
Obviously this will depend on how many NASes you have, but it's
something to consider.

You might also consider doing conversions on historical data rather
than using what Radiator logs to MySQL, e.g. an IP address can be 
converted and stored as a bigint.

It would be great to see what others can come up with to help 
determine a more-or-less ideal starting point for Radiator-to-
MySQL, or for the most efficient conversion of flatfiles to
a database.  Here's what I have so far:

CREATE TABLE detail (
  rec_id bigint NOT NULL AUTO_INCREMENT,
  uid int NOT NULL DEFAULT '0',                 # uid
  uname char(9) NOT NULL DEFAULT 'nouser',      # User-Name
  nas_ident bigint NOT NULL,                    # NAS-Identifier
  session_time int NOT NULL DEFAULT '0',        # Acct-Session-Time
  ip bigint NOT NULL,                           # Framed-Address
  clid bigint NOT NULL DEFAULT '0',             # Caller-Id
  called_num bigint NOT NULL DEFAULT '0',
  ts int NOT NULL,                              # Timestamp of Stop record
  start_time TIMESTAMP(14) NOT NULL,
  stop_time TIMESTAMP(14) NOT NULL,
  num_in_ml int,
  ml_id int,
  input_octets int,
  output_octets int,
  xmit_rate int,
  recv_rate int,
  modem_port int,
  modem_slot int,
  nas_port_type char(8),                        # could be converted to int
  PRIMARY KEY (rec_id),
  INDEX ip (ip),
  INDEX uid (uid),
  INDEX uname (uname),
  INDEX nas_ident (nas_ident)
);




On Thu, 15 Apr 1999, Ray Brighenti wrote:

 >Hi,
 >
 >For those out there who record their Radius Accounting to a database which
 >records do you really need to keep(or perhaps which ones are really no use)
 >We are using Ascend Maxs.
 >
 >I had a look through the Ascend description of accounting attributes and
 >this is what I came up with (Keeping in mind I want to be able to use the
 >data for troubleshooting, tracking and anything else I can pull useful
 >stats from).
 >
 >Any comments/opinions would be great.
 >
 >User-Name = Of course
 >NAS-Identifier = Yes
 >NAS-Port = Yes
 >NAS-Port-Type = Yes
 >Acct-Status-Type = Yes
 >Acct-Delay-Time = Dunno is this useful?
 >Acct-Session-Id = Yes
 >Acct-Authentic = Yes (we have some staff/test accounts set up in the Max)
 >Caller-Id = Yes
 >Client-Port-DNIS = Yes
 >Framed-Protocol = Yes
 >Framed-Address = Yes
 >Timestamp = Yes
 >Acct-Input-Octets = Yes
 >Acct-Output-Octets = Yes
 >Acct-Input-Packets = No - If you have the above two I assume you don't need
 >this
 >Acct-Output-Packets = No - Or this
 >Ascend-Disconnect-Cause = Yes - Trouble shooting
 >Ascend-Connect-Progress = Yes - As above
 >Ascend-Xmit-Rate = Yes
 >Ascend-Data-Rate = Yes
 >Ascend-PreSession-Time = No
 >Ascend-Pre-Input-Octets = No
 >Ascend-Pre-Output-Octets = No
 >Ascend-Pre-Input-Packets = No
 >Ascend-Pre-Output-Packets = No
 >Ascend-First-Dest = Dunno what use is this?
 >Ascend-Modem-PortNo = Yes
 >Ascend-Modem-SlotNo = Yes


===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to