Alcatel-Lucent 7950 SR, System Management Manual

Page: 28 / 462

Authentication, Authorization, and Accounting
Page 28 7950 SR OS System Management Guide
Accounting
When enabled, RADIUS accounting sends command line accounting from the router to the
RADIUS server. The router sends spar
s using UDP packets at port 1813 (decimal).
The router issues an accounting request packet for each event requiring the activity to be
recorded by the RADIUS server. The RADIUS server acknowledges each accounting request
by sending an accounting response after it has processed the accounting request. If no
response is received in the time defined in the timeout parameter, the accounting request must
be retransmitted until the configured retry count is exhausted. A trap is issued to alert the NMS
(or trap receiver) that the server is unresponsive. The router issues the accounting request to
the next configured RADIUS server (up to 5).
User passwords and authentication keys of any type are never transmitted as part of the
accounting request.
RADIUS Accounting
Accounting tracks user activity to a specified host. When RADIUS accounting is enabled, the
server is responsible for receiving accounting requests and returning a response to the client
indicating that it has successfully received the request. Each command issued on the router
generates a record sent to the RADIUS server. The record identifies the user who issued the
command and the timestamp.
Accounting can be configured independently from RADIUS authorization and RADIUS
authentication.
Accounting
The OS allows you to configure the type of accounting record packet that is to be sent to the
server when specified events occur on the device. The accounting
record-type
parameter indicates whether accounting start and stop packets be sent or just stop
packets be sent. Start/stop messages are only sent for individual commands, not for the
session.
When a user logs in to request access to the network using Telnet or SSH, or a user enters a
command for which accounting parameters are configured, or a system event occurs, such as a
reboot or a configuration file reload, the router checks the configuration to see if
accounting is required for the particular event.