until an acknowledgement is received from the accounting database engine by the RAS
device. wait-start is particularly important when the tracked event can cause a loss of
connectivity with the accounting database.
is being tracked. The where-to-send-the-information argument can be either of the following
locations:
defined by the tacacs-server host ip-address command.
defined by the radius-server host ip-address command. The current Cisco
implementation does not support the command accounting feature.
command began and when it ended for the user that initiated the command. The second line logs
to the database when the user's connection began and when it ended. In the last statement, any
system-level events, such as a reload or configuration change, are tracked by start and end time.
before the event is allowed to start. The key issue here is that if the event is a reload of the router,
it is imperative that the event be logged and acknowledged before the router reloads. If the
message is missed or lost in transmission, the event would go unrecorded.
RADIUS server. In addition, the records that are to be tracked should be recorded to the router
with the AAA accounting commands.
double-edged sword. The more accounting, the more resources are used to accomplish the
accounting. It is generally recommended that the stop-only argument be used if an elapsed time
is not needed.
treatment of AAA within the confines of the BCRAN class is intended to give the student a
basic understanding of AAA. All AAA software engines can provide the same or similar
functionality; it is impossible to describe the intricacies of an individual software suite as the
standard for AAA.
Router(config)#aaa accounting connection start-stop tacacs+
Router(config)#aaa accounting system wait-start tacacs+