3Com Switch 8800 Configuration Guide Chapter 40 AAA and RADIUS/TACACS+ Protocol Con
figuration
40-27
Table 40-32 Set a key for securing the communication with the TACACS+ server
Operation Command
Configure a key for securing the
communication with the accounting,
authorization or authentication server
key { accounting | authorization |
authentication } string
Delete the configuration undo key { accounting | authorization
| authentication }
No key is configured by default.
40.4.7 Setting the Username Format Acceptable to the TACACS Server Username is usually in the “userid@isp-name” format, with the domain name following
“@”.
If a TACACS server does not accept the username with domain name, you can remove
the domain name and resend it to the TACACS server.
Perform the following configuration in TACACS+ view.
Table 40-33 Set the username format acceptable to the TACACS server
Operation Command
Send username with domain name user-name-format with-domain
Send username without domain name user-name-format without-domain
By default, each username sent to a TACACS server contains a domain name.
40.4.8 Setting the Unit of Data Flows Destined for the TACACS Server Perform the following configuration in TACACS+ view.
Table 40-34 Set the unit of data flows destined for the TACACS server
Operation Command
Set the unit of data flows
destined for the TACACS server
data-flow-format data { byte | giga-byte |
kilo-byte | mega-byte }
data-flow-format packet { giga-packet |
kilo-packet | mega-packet | one-packet }
Restore the default unit of data
flows destined for the TACACS
server undo data-flow-format { data | packet }
The default data flow unit is byte.