3Com Switch 8800 Configuration GuideChapter 40 AAA and RADIUS/TACACS+ Protocol Configuration40-27Table 40-32 Set a key for securing the communication with the TACACS+ serverOperation CommandConfigure a key for securing thecommunication with the accounting,authorization or authentication serverkey { accounting | authorization |authentication } stringDelete the configuration undo key { accounting | authorization| authentication }No key is configured by default.40.4.7 Setting the Username Format Acceptable to the TACACS ServerUsername 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 removethe 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 serverOperation CommandSend username with domain name user-name-format with-domainSend username without domain name user-name-format without-domainBy 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 ServerPerform the following configuration in TACACS+ view.Table 40-34 Set the unit of data flows destined for the TACACS serverOperation CommandSet the unit of data flowsdestined for the TACACS serverdata-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 dataflows destined for the TACACSserverundo data-flow-format { data | packet }The default data flow unit is byte.
