Chapter 4 Managing GSS User Accounts Through a Server
Identifying the Server Host on the GSS
4-20
Cisco Global Site Selector Administration Guide
OL-10410-01
When operating the GSS as a client with a server, the GSS may restrict
user access to all CLI commands. This behavior can occur when you specify an
encryption key on the GSS using the
tacacs-server host
command but do not specify
the same encryption key on the server. In this case, the CLI command
restriction takes place immediately on the GSS once you enter the
aaa authorization
commands
command (see the
“Specifying Authorization of the GSS”
section).
You should first enter the
tacacs-server host
command on the GSS and then
specify the same encryption key on the server
before
you enter the
aaa
authorization commands
CLI command on the GSS. If the GSS fails to
authorize all CLI commands and you are unable to change the encryption key on
the server, power cycle the GSS. Because the CLI commands entered
prior to the power cycle were not saved in the GSS startup-configuration file, you
can regain access to the GSS CLI and redo the configuration.
The syntax for this global configuration command is as follows:
tacacs-server host
ip_or_host
[
port
port
] [
key
encryption_key
]
The arguments and keywords for this global configuration command are as
follows:
•
ip_or_host
—IP address or hostname of the server that you want
to access. Enter an IP address in dotted-decimal notation (for example,
192.168.11.1) or a mnemonic hostname (for example,
myhost.mydomain.com).
•
port
port
—(Optional) TCP port of the server. The default port is
49. You can enter a port number from 1 to 65535.
•
key
encryption_key
—(Optional) Shared secret between the GSS and the
server. If you want to encrypt packet transactions
between the GSS and the server, define an encryption key. If you
do not define an encryption key, the GSS transmits packets to the
server in clear text. The range for the encryption key is 1 to 100 alphanumeric
characters.