Cisco CRS User Manual

Usage Guidelines
The key name entered must match the key used on the TACACS+ daemon. The key name applies to all servers
that have no individual keys specified. All leading spaces are ignored; spaces within and after the key are not.
If you use spaces in your key, do not enclose the key in quotation marks unless the quotation marks themselves
are part of the key.
The key name is valid only when the following guidelines are followed:
•
The clear-text-key argument must be followed by the 0 keyword.
•
The encrypted-key argument must be followed by the 7 keyword.
The TACACS server key is used only if no key is configured for an individual TACACS server. Keys
configured for an individual TACACS server always override this global key configuration.
Task ID
OperationsTask ID
read, writeaaa
Examples
The following example sets the authentication and encryption key to key1:
RP/0/RP0/CPU0:router(config)# tacacs-server key key1
Related Commands
DescriptionCommand
Specifies an authentication and encryption key shared
between the AAA server and the TACACS+ server.
key (TACACS+), on page 40
Specifies a TACACS+ host.tacacs-server host, on page 99
Cisco IOS XR System Security Command Reference for the Cisco CRS Router, Release 4.1
OL-24740-01 103
Authentication, Authorization, and Accounting Commands
tacacs-server key

Cisco CRS Specifications

General

Operating System	Cisco IOS XR
Product Type	Core Router
Form Factor	Modular Chassis
Dimensions	Varies by chassis type
Weight	Varies by chassis type
Architecture	Distributed
Switch Fabric	Multi-stage
Interface Support	Ethernet, SONET/SDH, OTN
Interfaces/Ports	Varies by line card
Port Density	Varies by line card
Routing Protocol	BGP, IS-IS, OSPF, MPLS
Management	CLI, SNMP
Power Supply	Redundant, hot-swappable
Cooling	Redundant, Hot-swappable Fan Trays
Supported Protocols	IPv4, IPv6, MPLS
Management Interfaces	Ethernet, console
Security Features	ACLs