Configuring HWTACACS 235

Table 2-43 Setting a key for securing the communication with the HWTACACS server

OperationCommand

Configure a key for securing the communication with the accounting, authorization or authentication serverkey { accounting authorization authentication } string

Delete the configurationundo key { accounting authorization authentication }

No key is configured by default.

2.4.8 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 HWTACACS view.

Table 2-44 Setting the username format acceptable to the TACACS server

OperationCommand

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.

2.4.9Setting the Unit of Data Flows Destined for the TACACS Server Perform the following configuration in HWTACACS view.

Table 2-45 Setting the unit of data flows destined for the TACACS server OperationCommand

Set the unit of data flows destined 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 data flows destined for the TACACS serverundo data-flow-format { data packet }

The default data flow unit is byte.

Page 235
Image 235
3Com 10014298 manual Configuring Hwtacacs