Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

statlog.ini File

The statlog.ini initialization file configures the Steel-Belted Radius Carrier statistics log file (yyyymmdd.statlog), which periodically records server statistics to a comma-delimited ASCII file. The statistics log provides a mechanism for creating snapshots of user-selected server statistics.

Note: The statistics per NAD client and per Called-Station-ID are not captured in the statlog file.

  • The first line in a *.statlog file lists all column headings in double quotes (“Date”, “Time”, ...).
  • The first column in a *.statlog file identifies the current date in yyyy-mm-dd format in double-quotes ("2006-02-13"). The *.statlog file uses the local date, not the date in the UTC time zone, when it records date information.
  • The second column in a *.statlog file identifies the current time in hh:mm:ss format in double-quotes ("14:13:22"). The *.statlog file uses the local time, not the time in the UTC time zone, when it records time information.
  • If statistics logging is enabled, a new statistics logging file is created the first time the server is started each day. At midnight, the server closes the old statistics log file and starts a new one with a file name that reflects the new date.
  • If you restart the Steel-Belted Radius Carrier server and a *.statlog file exists for the current day, the server appends new information to the existing *.statlog file. When the server is restarted, the timer for capturing statistics snapshots is restarted; for example, a server configured to record statistics every 10 minutes captures statistics at 14:10:00. If the server is restarted at 14:15:00, it captures system statistics immediately (14:15:00) and 10 minutes thereafter (14:25:00); it does not try to capture statistics at 14:20:00 (10 minutes after the capture before the restart).
  • If you change the order or contents of the list of statistics to be recorded and restart the server, Steel-Belted Radius Carrier detects the change and writes an entry with the new column headers to the current *.statlog file before writing new data records into the file.

    Note: When you change the order or contents of the list of statistics recorded in the *.statlog file, Steel-Belted Radius Carrier creates the statloghdr.dat checkpoint file in the radiusdir directory. Do not modify or delete the statloghdr.dat file.

[Settings] Section

The [Settings] section of statlog.ini (Table 55) specifies whether the statistics log file is enabled, who can access the statistics log file, how frequently the server writes information to the statistics log file, and the number of days statistics log files are retained.

Table 55: statlog.ini [Settings] Syntax

Parameter

Function

Enable

  • If set to 1, the Steel-Belted Radius Carrier server periodically writes statistics information to the yyyymmdd.statlog file.
  • If set to 0, the Steel-Belted Radius Carrier server does not update the yyyymmdd.statlog file.

Default value is 0.

LogFilePermissions

Specifies the owner and access permission setting for the *.statlog file.

Enter a value for the LogFilePermissions setting in owner:group permissions format, where:

  • owner specifies the owner of the file in text or numeric format.
  • group specifies the group setting for the file in text or numeric format.
  • permissions specifies what privileges can be exercised by Owner/Group/Other with respect to the file in text or numeric format.

    For example, user:1007 rw-r- - - - - specifies that the file owner (user) can read and edit the log file, members of group 1007 can read (but not edit) the log file, and other users cannot access the log file.

Interval-Seconds

Specifies the number of seconds that the SBR Carrier server waits before writing new statistics information to the statistics log.

You can enter a value ranging from 10 through 3600 seconds. On Solaris systems, this value ranges from 1 through 3600 seconds.

Default value is 600 seconds (10 minutes).

Note: The written statistics information may become garbled under extreme load when the interval is less than 60 seconds.

Days-To-Keep

Specifies the number of days (in the range 1–365) the statistics log is retained by the Steel-Belted Radius Carrier server. When the specified number of days has elapsed, the statistics log is automatically purged.

Default value is 7 days.

For example:

[Settings]
Enable = 1
;LogfilePermissions = someuser:1007 rw-r- - - - -
;Interval-Seconds = 600
;Days-To-Keep = 7

[Statistics] Section

The [Statistics] section of statlog.ini (Table 56) identifies the statistics you want included in the snapshot. Each entry in this section takes the format Source/Statistic, where Source identifies the LCI statistics container that holds the statistic counter you want and Statistic identifies the statistic by name.

Statistics are written to the log file in the order in which they are listed in the [Statistics] section.

Table 56: statlog.ini [Statistics] Syntax

Parameter

Function

  Source

Specifies the name of the LCI statistics container that holds the specified statistic.

Supported values for Source are:

  • Server
  • Authentication
  • Accounting
  • Proxy
  • Rate
  • KPI

  Statistic

Specifies the name of the statistic you want to record in the log.

Statistics for the Server are:

  • Accounting-Threads
  • Authentication-Threads
  • Proxy-Threads
  • High-Acct-Threads
  • High-Acct-Threads-Since-Reset
  • High-Auth-Threads
  • High-Proxy-Threads
  • High-Auth-Threads-Since-Reset
  • High-Total-Threads
  • High-Total-Threads-Since-Reset
  • High-Proxy-Threads-Since-Reset
  • Max-Acct-Threads
  • Max-Auth-Threads
  • Max-Total-Threads
  • Max-Proxy-Threads
  • Total-Threads
 

Authentication statistics are:

  • Accept—Specifies the total number of Access-Accept responses sent from SBR Carrier to NAD
  • Dropped-Packet—Specifies the total number of RADIUS authentication requests dropped by SBR Carrier because the flood queue is exceeded
  • Failed-Authentication—Specifies the total number of failed authentication requests that are rejected because the username, password, or shared secret is invalid
  • Failed-On-Check-List—Specifies the total number of requests that are authenticated by SBR Carrier but did not meet the checklist requirements
  • Insufficient-Resources—Specifies the total number of authentication requests that are rejected due to a problem in internal (such as memory) or pooled (such as IP addresses and concurrency slots) resources
  • Invalid-Request—Specifies the total number of invalid RADIUS authentication requests received by SBR Carrier. Invalid requests are caused by one of the following reasons:
    • NAD sends incorrectly formed packets to SBR Carrier.
    • NAD does not conform to the RADIUS standard.
  • Proxy-Failure—Specifies the number of times a proxy RADIUS authentication packet has failed because of one of the following reasons:
    • The proxy RADIUS server is not able to find a target server.
    • All targets in a proxy realm are in fast-fail mode.
  • Reject—Specifies the total number of Access-Reject responses sent from SBR Carrier to NAD
  • Rejected-By-Proxy—Specifies the number of authentication reject responses received from the proxy RADIUS target server
  • Silent-Discard—Specifies the number of authentication requests that are silently discarded by the realm-selection script, or because of unknown clients, unknown request types, malformed requests, unavailable CST, or phantom creation failure. The silent discard also occurs when no shared secret is configured for the client, or if the request does not match the defined length or contains an invalid Message-Authenticator size.

    Note: The Reject counter is not incremented if the Silent-Discard counter is incremented.

  • Total-Retry-Packets—Specifies the total number of duplicate authentication requests received by SBR Carrier
  • Total-Transactions—Specifies the total number of authentication requests received by SBR Carrier irrespective of whether the requests are accepted, rejected, or silently discarded
  • Transactions-Retried—Specifies the number of authentication requests for which duplicates are received by SBR Carrier
 

Accounting statistics are:

  • Dropped-Packet—Specifies the total number of RADIUS accounting packets dropped by SBR Carrier because the flood queue is exceeded
  • Insufficient-Resources—Specifies the total number of accounting requests that are silently discarded because of a problem in internal or pooled resources, or database (Oracle or JDBC plug-ins) configuration failure. The database configuration failure is caused by one of the following reasons:
    • The RADIUS server is unable to read the product attribute of a client.
    • The dictionary attribute of a client is missing or invalid.
    • The database attribute type is not consistent with the dictionary attribute type.
  • Invalid-Client—Specifies the total number of accounting requests that are silently discarded because the clients are unknown
  • Invalid-Request—Specifies the total number of invalid RADIUS accounting requests received by SBR Carrier. Invalid requests are caused by one of the following reasons:
    • NAD sends incorrectly formed packets to SBR Carrier.
    • NAD does not conform to the RADIUS standard.
  • Invalid-Shared-Secret—Specifies the total number of accounting requests silently discarded because the shared secret entered is incorrect
  • Interim—Specifies the total number of Accounting-Interim requests received by SBR Carrier
  • Off—Specifies the total number of Accounting-Off requests received by SBR Carrier
  • On—Specifies the total number of Accounting-On requests received by SBR Carrier
  • Proxy-Failure—Specifies the number of times a proxy RADIUS accounting packet has failed due to one of the following reasons:
    • The proxy RADIUS server is not able to find a target server.
    • All targets in a proxy realm are in fast-fail mode.
  • Start—Specifies the total number of Accounting-Start requests received by SBR Carrier
  • Stop—Specifies the total number of Accounting-Stop requests received by SBR Carrier
  • Total-Retry-Packets—Specifies the total number of duplicate accounting requests received by SBR Carrier
  • Total-Transactions—Specifies the total number of Accounting-Start, Accounting-Stop, Accounting-Interim, Accounting-On, and Accounting-Off requests received by SBR Carrier
  • Transactions-Retried—Specifies the number of accounting requests for which duplicates are received
 

Proxy statistics are:

  • Accounting—Specifies the total number of accounting requests forwarded from the proxy server to the target RADIUS server
  • Authentication—Specifies the total number of authentication requests forwarded from the proxy server to the target RADIUS server
  • Insufficient-Resources—Specifies the number of proxy requests that are failed or discarded due to one of the following reasons:
    • Memory allocation failed while the proxy response was being parsed
    • Socket error occurred while the proxy response was being received
    • No IP addresses were available in the IP pool while the proxy response was being parsed
  • Invalid-Response—Specifies the number of invalid proxy RADIUS responses received from the target server. Invalid responses are caused by one of the following reasons:
    • The target RADIUS server sends incorrectly formed packets to SBR Carrier.
    • The target RADIUS server does not conform to the RADIUS standard.
    • The message authenticator is invalid.
  • Invalid-Shared-Secret—Specifies the number of proxy responses that are dropped because the signature is invalid
  • Timed-Out—Specifies the number of proxy requests that failed despite several retry attempts
  • Total-Retry-Packets—Specifies the total number of proxy retries made by the proxy server
  • Total-Transactions—Specifies the total number of authentication and accounting requests that are forwarded from the proxy server to the target RADIUS server
  • Transactions-Retried—Specifies the number of proxy requests for which one or more transmission retries are made
 

Statistics for the Rate are:

  • Acct-Start-Average-Rate
  • Acct-Start-Current-Rate
  • Acct-Start-Peak-Rate
  • Acct-Stop-Average-Rate
  • Acct-Stop-Current-Rate
  • Acct-Stop-Peak-Rate
 
  • Auth-Accept-Average-Rate
  • Auth-Accept-Current-Rate
  • Auth-Accept-Peak-Rate
  • Auth-Reject-Average-Rate
  • Auth-Reject-Current-Rate
  • Auth-Reject-Peak-Rate
  • Auth-Request-Average-Rate
  • Auth-Request-Current-Rate
  • Auth-Request-Peak-Rate
 

Statistics for the Rate are:

  • Proxy-Acct-Fail-Proxy-Average-Rate
  • Proxy-Acct-Fail-Proxy-Current-Rate
  • Proxy-Acct-Fail-Proxy-Peak-Rate
  • Proxy-Acct-Request-Average-Rate
  • Proxy-Acct-Request-Current-Rate
  • Proxy-Acct-Request-Peak-Rate
  • Proxy-Auth-Rej-Proxy-Average-Rate
  • Proxy-Auth-Rej-Proxy-Current-Rate
  • Proxy-Auth-Rej-Proxy-Error-Average-Rate
 
  • Proxy-Auth-Rej-Proxy-Error-Current-Rate
  • Proxy-Auth-Rej-Proxy-Error-Peak-Rate
  • Proxy-Auth-Rej-Proxy-Peak-Rate
  • Proxy-Auth-Request-Average-Rate
  • Proxy-Auth-Request-Current-Rate
  • Proxy-Auth-Request-Peak-Rate
  • Proxy-Fail-Badresp-Average-Rate
  • Proxy-Fail-Badresp-Current-Rate
  • Proxy-Fail-Badresp-Peak-Rate
  • Proxy-Fail-Badsecret-Average-Rate
  • Proxy-Fail-Badsecret-Current-Rate
  • Proxy-Fail-Badsecret-Peak-Rate
 
  • Proxy-Fail-Missingresr-Average-Rate
  • Proxy-Fail-Missingresr-Current-Rate
  • Proxy-Fail-Missingresr-Peak-Rate
  • Proxy-Fail-Timeout-Average-Rate
  • Proxy-Fail-Timeout-Current-Rate
  • Proxy-Fail-Timeout-Peak-Rate
  • Proxy-Retries-Average-Rate
  • Proxy-Retries-Current-Rate
  • Proxy-Retries-Peak-Rate
 

Key Performance Indicators (KPI) statistics are:

  • KPI/Challenge-Objects—Specifies the number of challenge cache objects used by SBR Carrier at a given time
  • KPI/Max-Challenge-Objects—Specifies the configured challenge cache objects maximum limit
  • KPI/High-Challenge-Objects-Since-Reset—Specifies the peak number of challenge cache objects in use since the start of SBR Carrier or since the statistics reset

For example:

[Statistics]
Server/Authentication-Threads
Server/Accounting-Threads
Server/Total-Threads
Server/Max-Acct-Threads
Server/Max-Auth-Threads
Server/Max-Total-Threads
Server/High-Auth-Threads
Server/High-Acct-Threads
Server/High-Total-Threads
Server/High-Acct-Threads-Since-Reset
Server/High-Auth-Threads-Since-Reset
Server/High-Total-Threads-Since-Reset

Authentication/Accept
Authentication/Reject
Authentication/Silent-Discard
Authentication/Total-Transactions
Authentication/Dropped-Packet
Authentication/Invalid-Request
Authentication/Failed-Authentication
Authentication/Failed-On-Check-List
Authentication/Insufficient-Resources
Authentication/Proxy-Failure
Authentication/Rejected-By-Proxy
Authentication/Transactions-Retried
Authentication/Total-Retry-Packets

Accounting/Start
Accounting/Stop
Accounting/Interim
Accounting/On
Accounting/Off
Accounting/Total-Transactions
Accounting/Dropped-Packet
Accounting/Invalid-Request
Accounting/Invalid-Client
Accounting/Invalid-Shared-Secret
Accounting/Insufficient-Resources
Accounting/Proxy-Failure
Accounting/Transactions-Retried
Accounting/Total-Retry-Packets

Proxy/Authentication
Proxy/Accounting
Proxy/Total-Transactions
Proxy/Timed-Out
Proxy/Invalid-Response
Proxy/Invalid-Shared-Secret
Proxy/Insufficient-Resources
Proxy/Transactions-Retried
Proxy/Total-Retry-Packets

Rate/Auth-Request-Current-Rate
Rate/Auth-Request-Average-Rate
Rate/Auth-Request-Peak-Rate
Rate/Auth-Accept-Current-Rate
Rate/Auth-Accept-Average-Rate
Rate/Auth-Accept-Peak-Rate
Rate/Auth-Reject-Current-Rate
Rate/Auth-Reject-Average-Rate
Rate/Auth-Reject-Peak-Rate
Rate/Acct-Start-Current-Rate
Rate/Acct-Start-Average-Rate
Rate/Acct-Start-Peak-Rate
Rate/Acct-Stop-Current-Rate
Rate/Acct-Stop-Average-Rate
Rate/Acct-Stop-Peak-Rate
Rate/Proxy-Auth-Request-Current-Rate
Rate/Proxy-Auth-Request-Average-Rate
Rate/Proxy-Auth-Request-Peak-Rate
Rate/Proxy-Acct-Request-Current-Rate
Rate/Proxy-Acct-Request-Average-Rate
Rate/Proxy-Acct-Request-Peak-Rate
Rate/Proxy-Fail-Timeout-Current-Rate
Rate/Proxy-Fail-Timeout-Average-Rate
Rate/Proxy-Fail-Timeout-Peak-Rate
Rate/Proxy-Fail-Badresp-Current-Rate
Rate/Proxy-Fail-Badresp-Average-Rate
Rate/Proxy-Fail-Badresp-Peak-Rate
Rate/Proxy-Fail-Badsecret-Current-Rate
Rate/Proxy-Fail-Badsecret-Average-Rate
Rate/Proxy-Fail-Badsecret-Peak-Rate
Rate/Proxy-Fail-Missingresr-Current-Rate
Rate/Proxy-Fail-Missingresr-Average-Rate
Rate/Proxy-Fail-Missingresr-Peak-Rate
Rate/Proxy-Retries-Current-Rate
Rate/Proxy-Retries-Average-Rate
Rate/Proxy-Retries-Peak-Rate
Rate/Proxy-Auth-Rej-Proxy-Current-Rate
Rate/Proxy-Auth-Rej-Proxy-Average-Rate
Rate/Proxy-Auth-Rej-Proxy-Peak-Rate
Rate/Proxy-Acct-Fail-Proxy-Current-Rate
Rate/Proxy-Acct-Fail-Proxy-Average-Rate
Rate/Proxy-Acct-Fail-Proxy-Peak-Rate
Rate/Proxy-Auth-Rej-Proxy-Error-Current-Rate
Rate/Proxy-Auth-Rej-Proxy-Error-Average-Rate
Rate/Proxy-Auth-Rej-Proxy-Error-Peak-Rate

KPI/Challenge-Objects
KPI/Max-Challenge-Objects
KPI/High-Challenge-Objects-Since-Reset

Modified: 2018-01-11

Previous Page Next Page