2-26Displaying and maintaining HWTACACS protocol informationTo do… Use the command… RemarksDisplay the configuration orstatistic information about onespecific or all HWTACACSschemesdisplay hwtacacs[ hwtacacs-scheme-name [ statistics ] ]Display buffered non-responsestop-accounting requestsdisplay stop-accounting-bufferhwtacacs-schemehwtacacs-scheme-nameAvailable in any view.Clear HWTACACS messagestatisticsreset hwtacacs statistics { accounting |authentication | authorization | all }Delete buffered non-responsestop-accounting requestsreset stop-accounting-bufferhwtacacs-schemehwtacacs-scheme-nameAvailable in userview.AAA Configuration ExamplesRemote RADIUS Authentication of Telnet/SSH UsersThe configuration procedure for remote authentication of SSH users by RADIUS server is similar to thatfor Telnet users. The following text only takes Telnet users as example to describe the configurationprocedure for remote authentication.Network requirementsIn the network environment shown in Figure 2-1, you are required to configure the device so that theTelnet users logging into the switching engine are authenticated by the RADIUS server.z A RADIUS authentication server with IP address 10.110.91.164 is connected to the device.z On the device, set the shared key it uses to exchange messages with the authentication RADIUSserver to "aabbcc".z A IMC server is used as the RADIUS server. You can select extended as the server-type in aRADIUS scheme.z 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-name if youhave configured the device to include domain names in the user names to be sent to the RADIUSserver in the RADIUS scheme.