Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

Statistics Variables

Server statistics counters record the number of certain types of events. The LCI allows you to read these statistics to monitor the performance of your Steel-Belted Radius Carrier server.

Counter Statistics

The statistics counters can be accessed via the LCI by executing the following one line command:

ldapsearch -V 2 -h 127.0.0.1 -p 667 -D “cn=admin,o=radius” -w radius -s sub -T -b “radiusstatus=statistics,o=radius” stattype=typeofstatus

The following sections illustrate the variables displayed for different settings of the stattype parameter.

stattype: server

dn: stattype=server,radiusstatus=statistics,o=radiusobjectclass: topobjectclass: radiusstatusradiusstatus: statisticsstattype: serverstart-time: 2002/05/08 13:29:08up-time: 26188ip-address: 192.168.21.142version: v 2.20.33authentication-threads: 0accounting-threads: 0total-threads: 0max-auth-threads: 100max-acct-threads: 100max-total-threads: 200high-auth-threads: 2high-acct-threads: 0high-total-threads: 2

stattype: authentication

dn: stattype=authentication,radiusstatus=statistics,o=radiusobjectclass: topobjectclass: radiusstatusradiusstatus: statisticsstattype: authenticationaccept: 1reject: 0silent-discard: 0total-transactions: 8invalid-request: 0failed-authentication: 0failed-on-check-list: 0insufficient-resources: 0proxy-failure: 0rejected-by-proxy: 0transactions-retried: 0total-retry-packets: 0

stattype: accounting

dn: stattype=accounting,radiusstatus=statistics,o=radiusobjectclass: topobjectclass: radiusstatusradiusstatus: statisticsstattype: accountingstart: 0stop: 0on: 0off: 0total-transactions: 0invalid-request: 0invalid-client: 0invalid-shared-secret: 0insufficient-resources: 0proxy-failure: 0transactions-retried: 0total-retry-packets: 0

stattype: proxy

dn: stattype=proxy,radiusstatus=statistics,o=radiusobjectclass: topobjectclass: radiusstatusradiusstatus: statisticsstattype: proxyauthentication: 0accounting: 0total-transactions: 0timed-out: 0invalid-response: 0invalid-shared-secret: 0insufficient-resources: 0transactions-retried: 0total-retry-packets: 0proxytransaction: 0

Rate Statistics

Rate statistics are derived from existing counter statistics by taking time into consideration. Overall server rate values calculated for each of these counter statistics consist of the following:

  • Current rate—The rate measured over the most recent rate interval.
  • Average rate—The rate measured since the Steel-Belted Radius Carrier server was started or since the last time statistics were reset to zero.
  • Peak rate—The highest rate observed since the Steel-Belted Radius Carrier server was started or since the last time statistics were reset to zero.

Rate values calculated per NAD client and per Called-Station-ID consist of only current and peak rates.

Note: NAD client and Called-Station-ID specific rate statistics are calculated only if you set the EnhancedRateStats parameter in the radius.ini file to 1.

Additionally, there is a (read-only) time value used in calculations:

  • Rate statistics seconds-per interval—The duration (in seconds) of the interval over which the rate statistics are gathered.

To read overall server rate statistics from the LCI, you must set radiusstatus= statistics and stattype= rate. This results in output such as the following:

rate-statistics-seconds-per-interval: 1auth-request-current-rate: 0auth-request-average-rate: 0auth-request-peak-rate: 7auth-accept-current-rate: 0auth-accept-average-rate: 0auth-accept-peak-rate: 1auth-reject-current-rate: 0auth-reject-average-rate: 0auth-reject-peak-rate: 0acct-start-current-rate: 0acct-start-average-rate: 0acct-start-peak-rate: 0acct-stop-current-rate: 0acct-stop-average-rate: 0acct-stop-peak-rate: 0proxy-auth-request-current-rate: 0proxy-auth-request-average-rate: 0proxy-auth-request-peak-rate: 0proxy-acct-request-current-rate: 0proxy-acct-request-average-rate: 0proxy-acct-request-peak-rate: 0proxy-fail-timeout-current-rate: 0proxy-fail-timeout-average-rate: 0proxy-fail-timeout-peak-rate: 0proxy-fail-badresp-current-rate: 0proxy-fail-badresp-average-rate: 0proxy-fail-badresp-peak-rate: 0proxy-fail-badsecret-current-rate: 0proxy-fail-badsecret-average-rate: 0proxy-fail-badsecret-peak-rate: 0proxy-fail-missingresr-current-rate: 0proxy-fail-missingresr-average-rate: 0proxy-fail-missingresr-peak-rate: 0proxy-retries-current-rate: 0proxy-retries-average-rate: 0proxy-retries-peak-rate: 0proxy-auth-rej-proxy-current-rate: 0proxy-auth-rej-proxy-average-rate: 0proxy-auth-rej-proxy-peak-rate: 0proxy-acct-fail-proxy-current-rate: 0proxy-acct-fail-proxy-average-rate: 0proxy-acct-fail-proxy-peak-rate: 0proxy-auth-rej-proxy-error-current-rate: 0proxy-auth-rej-proxy-error-average-rate: 0proxy-auth-rej-proxy-error-peak-rate: 0proxy-transaction-current-rate: 0proxy-transaction-average-rate: 0proxy-transaction-peak-rate: 0

To read rate statistics per NAD client from the LCI, you must set radiusstatus=rate_stats_by_nas and also input the NAD name for which rate statistics should be displayed. This results in output such as the following:

dn: nasname=TEST-NAS,radiusstatus=rate_stats_by_nas,o=radiusobjectclass: topobjectclass: radiusstatusradiusstatus: rate_stats_by_nasnasname: TEST-NASnasipaddr: 10.212.98.76auth-request-current-rate: 101auth-accept-current-rate: 101auth-reject-current-rate: 0auth-dropped-current-rate: 0acct-total-requests-current-rate: 102acct-start-current-rate: 102acct-stop-current-rate: 0acct-interim-current-rate: 0acct-dropped-current-rate: 0proxy-auth-request-current-rate: 0proxy-acct-request-current-rate: 0 proxy-total-request-current-rate: 0proxy-fail-timeout-current-rate: 0auth-request-peak-rate: 101auth-accept-peak-rate: 101auth-reject-peak-rate: 0auth-dropped-peak-rate: 0acct-total-requests-peak-rate: 102acct-start-peak-rate: 102acct-stop-peak-rate: 0acct-interim-peak-rate: 0acct-dropped-peak-rate: 0proxy-auth-request-peak-rate: 0proxy-acct-request-peak-rate: 0proxy-total-request-peak-rate: 0proxy-fail-timeout-peak-rate: 0

To read rate statistics per Called-Station-ID from the LCI, you must set radiusstatus=stats_by_calledstationid and also input the string representing Called-Station-ID for which rate statistics should be displayed. This results in output such as the following:

dn: called-station-id=00-10-A4-23-19-C0,radiusstatus=stats_by_calledstationid, o=radiusobjectclass: topobjectclass: radiusstatusradiusstatus: stats_by_calledstationidcalled-station-id: 00-10-A4-23-19-C0auth-request-current-rate: 101auth-accept-current-rate: 101auth-reject-current-rate: 0auth-dropped-current-rate: 0acct-total-requests-current-rate: 102acct-start-current-rate: 102acct-stop-current-rate: 0acct-interim-current-rate: 0acct-dropped-current-rate: 0proxy-auth-request-current-rate: 0proxy-acct-request-current-rate: 0proxy-total-request-current-rate: 0proxy-fail-timeout-current-rate: 0auth-request-peak-rate: 101auth-accept-peak-rate: 101auth-reject-peak-rate: 0auth-dropped-peak-rate: 0acct-total-requests-peak-rate: 102acct-start-peak-rate: 102acct-stop-peak-rate: 0acct-interim-peak-rate: 0acct-dropped-peak-rate: 0proxy-auth-request-peak-rate: 0proxy-acct-request-peak-rate: 0proxy-total-request-peak-rate: 0proxy-fail-timeout-peak-rate: 0

Modified: 2017-03-07