3Com WX3000 AAA Configuration Examples, Remote Radius Authentication of Telnet/SSH Users

Displaying and maintaining HWTACACS protocol information

To do…	Use the command…	Remarks
Display the configuration or
statistic information about one	display hwtacacs
specific or all HWTACACS	[ hwtacacs-scheme-name [ statistics ] ]
schemes		Available in any view.
Display buffered non-response	display stop-accounting-buffer
	hwtacacs-scheme
stop-accounting requests
	hwtacacs-scheme-name
Clear HWTACACS message	reset hwtacacs statistics { accounting
statistics	authentication authorization all }	Available in user
	reset stop-accounting-buffer
Delete buffered non-response		view.
	hwtacacs-scheme
stop-accounting requests
	hwtacacs-scheme-name

AAA Configuration Examples

Remote RADIUS Authentication of Telnet/SSH Users

The configuration procedure for remote authentication of SSH users by RADIUS server is similar to that for Telnet users. The following text only takes Telnet users as example to describe the configuration procedure for remote authentication.

Network requirements

In the network environment shown in Figure 2-1, you are required to configure the device so that the Telnet users logging into the switching engine are authenticated by the RADIUS server.

z z

z

z

A RADIUS authentication server with IP address 10.110.91.164 is connected to the device.

On the device, set the shared key it uses to exchange messages with the authentication RADIUS server to "aabbcc".

A IMC server is used as the RADIUS server. You can select extended as the server-type in a RADIUS scheme.

On the RADIUS server, set the shared key it uses to exchange messages with the device to "aabbcc," set the authentication port number, and add Telnet user names and login passwords.

The Telnet user names added to the RADIUS server must be in the format of userid@isp-nameif you have configured the device to include domain names in the user names to be sent to the RADIUS server in the RADIUS scheme.

2-26