2-38
Controlling Management Access to the ProCurve Secure Router
Using the AAA Subsystem to Control Management Access
For example, the following command creates a group called tacacs and enters
the TACACS+ group configuration mode context:
ProCurve(config)# aaa group server tacacs+ tacacs
ProCurve(config-sg-tacacs+)#
Use the following command to add TACACS+ servers to the group:
Syntax: server <hostname | A.B.C.D>
Either replace <hostname> with the TACACS+ server’s hostname or replace
<A.B.C.D> with the server’s IP address.
The following example adds two servers to the tacacs group:
ProCurve(config-sg-tacacs+)# server 192.168.1.1
ProCurve(config-sg-tacacs+)# server 192.168.7.101
ProCurve(config-sg-tacacs+)# exit
You must use the tacacs-server command to define TACACS+ servers before
you can add them to a group. If you add a server to a group but the server is
not defined by a tacacs-server command, the router simply bypasses that
server in the group.
The Secure Router OS does not save empty TACACS+ groups. When the last
server is removed from a group, the Secure Router OS automatically deletes
the group.
Configure Global Settings for TACACS+ Servers
You can configure global settings that will be applied to all TACACS+ servers
defined on the router. However, if you configure specific settings for a
TACACS+ server, those settings override the global settings.
To configure global settings, you use the tacacs-server command, but you do
not specify a particular server. Instead, you use the following commands:
Syntax: tacacs-server key <key>
Syntax: tacacs-server packet maxsize <size>
Syntax: tacacs-server timeout <seconds>
To Next Page
Loading...
Need help?
General
