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, as many transactions can be in progress at any given time.
The following table describes the accounting statistics fields and the possible causes for accounting errors.
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 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 sum of the Starts, Stops, Ons, and Offs totals.
The number of interim accounting packets sent by RADIUS clients to the RADIUS server.
The number of RADIUS accounting packets dropped by RADIUS because the server was flooded with more packets than it could handle.
The number of invalid RADIUS requests made.
Possible Cause: A device is sending incorrectly formed packets to RADIUS. Either there is a configuration error or the device does not conform to the RADIUS standard.
The number of failed accounting requests, where the failure is due to invalid user name or password.
If all accounting transactions are failing, the problem might be that the accounting shared secret entered into the RADIUS client in the Security Console does not match the shared secret entered on the client device.
The number of rejects due to a server resource problem.
The number of requests for which one or more duplicates was received.