Single-Connection - Cisco CRS User Manual

Authentication, Authorization, and Accounting Commands

single-connection

To multiplex all TACACS+ requests to this server over a single TCP connection, use the single-connection
command in TACACS host configuration mode. To disable the single TCP connection for all new sessions
that use a separate connection, use the no form of this command.
single-connection
no single-connection
Syntax Description
This command has no keywords or arguments.
Command Default
By default, a separate connection is used for each session.
Command Modes
TACACS host configuration
Command History
Release
Release 3.6.0
Usage Guidelines
The single-connection command allows the TACACS+ server to handle a greater number of TACACS
operations than would be possible if multiple TCP connections were used to send requests to a server.
The TACACS+ server that is being used must support single-connection mode for this to be effective; otherwise,
the connection between the network access server and the TACACS+ server locks up or you can receive
unauthentic errors.
Task ID
Task ID
aaa
Examples
The following example shows how to configure a single TCP connection to be made with the TACACS+
server (IP address 209.165.200.226) and all authentication, authorization, accounting requests to use this TCP
connection. This works only if the TACACS+ server is also configured in single-connection mode. To configure
the TACACS+ server in single connection mode, refer to the respective server manual.
RP/0/RP0/CPU0:router(config)# tacacs-server host 209.165.200.226
RP/0/RP0/CPU0:router(config-tacacs-host)# single-connection
OL-24740-01
Modification
This command was introduced.
Operations
read, write
Cisco IOS XR System Security Command Reference for the Cisco CRS Router, Release 4.1
single-connection
97