
6-10 Configuring TACACS+ Accounting on an Interface
LX Series Configuration Guide
RADIUS accounting can be used when a subscriber logs in to an
asynchronous port via an IP interface. In order to enable
RADIUS accounting for an IP interface, RADIUS accounting must
be configured for the LX unit. For more information, see “Setting
Up RADIUS” on page 2-19.
X To enable RADIUS accounting on the IP interface
Execute the radius accounting enable command in
Interface Command Mode:
Example Intf 1-1:0 >>radius accounting enable
Configuring TACACS+ Accounting on
an Interface
TACACS+ Accounting allows you to log user account information
to a remote server in a per-client file. For more information
about TACACS+ accounting, see See Appendix B, “About
RADIUS and TACACS+ Accounting”on page page B-1.
X To enable TACACS+ accounting on the IP interface
Execute the tacacs+ accounting enable command in
Interface Command Mode:
Example Intf 1-1:0 >>tacacs+ accounting enable
Configuring Fallback on an IP Interface
Fallback Authentication can be used as a mechanism for
authenticating users when the configured authentication method
(for example, LDAP, RADIUS, TACACS+, or RSA SecurID) fails
because the authentication server is unreachable. When a user
logs in via Fallback, his or her username/password combination
is validated against the LOCAL security database for the LX unit.
The LX unit will make three attempts to log in the user via LDAP,
RADIUS, TACACS+, or RSA SecurID before it implements
Fallback. After the third login attempt, the username/password
combination will be validated against the LOCAL security
database for the LX unit.
Comentarios a estos manuales