Displaying Accounting Statistics
Accounting statistics provide information such as the number of transaction starts and stops and the reasons for rejecting attempted transactions. The start and stop numbers rarely match, because many transactions can be in progress at any given time.
To display accounting statistics using the Web GUI:
Select RADIUS Configuration > Statistics > System.
The System Statistics page (Figure 258) appears.
Select the server entry for which you want to view the accounting statistics from the Server list and select Accounting from the View list.
The System Statistics page (Figure 259) displays accounting statistics for the selected server.
Table 117 describes the accounting statistics fields and describes the possible causes for accounting errors.
Optionally, select the Auto Refresh (seconds) check box and select a time period for refreshing the display from the drop-down list. Default value is 2 seconds.
By default, the auto-refresh feature is enabled.
You can click the Refresh button to refresh the display.
Optionally, click Clear All Statistics to clear all accounting statistics.
SBR Carrier calculates the rate of accounting requests as they are received from the socket and displays all the incoming requests from the client in Accounting Request statistics. Other statistics information such as Rejects are measured as the incoming requests are processed. If a request is not processed immediately and is handled by the flood queue, the processing will be delayed and this will be reflected in the Accounting statistics for that time period.
Table 117: Accounting Statistics
The current, average, and peak number of transactions in which a dial-in connection was started following a successful authentication.
The current, average, and peak number of transactions in which a dial-in connection was terminated.
The sum of the start, stop, on and off totals.
The number of Accounting-On messages received, indicating that a RADIUS client has restarted.
The number of Accounting-Off messages received, indicating that a RADIUS client has shut down.
The number of interim accounting packets received.
The number of RADIUS accounting packets dropped by Steel-Belted Radius Carrier because the server was flooded with more packets than it was able to handle.
The number of invalid RADIUS requests made.
Invalid requests can be a result of a device sending incorrectly formed packets to Steel-Belted Radius Carrier because it is incorrectly configured, or because the device does not conform to the RADIUS standard.
The number of requests discarded due to a server resource problem.
The number of times that proxy RADIUS forwarding failed.
The number of requests for which one or more duplicates was received.
Total Retry Packets
The number of duplicate packets received.