Customer Unable To Log On By Any Means (Telnet, Rlogin, Ssh, And Ppp); Administrator Unable To Obtain Accounting Information From The Tacacs+ Server - Avaya 8800 Troubleshooting Manual

Upper layer troubleshooting
3. Check whether the physical connection between the Ethernet Routing Switch
4. If customers use the serial port to connect to the Ethernet Routing Switch
Customer unable to log on by any means (Telnet, rlogin, SSH, and
PPP)
If customers are unable to log on by any means, perform the following steps.
Procedure steps
1. Check whether the TACACS+ server is running well and try restarting the TACACS
2. Check whether TACACS+ and Radius are both enabled on the Ethernet Routing
3. Check whether the TACACS+ server is configured to un-encrypted mode, as the
Administrator unable to obtain accounting information from the
TACACS+ server
If the administrator is unable to obtain accounting information from the TACACS+ server,
perform the following steps.
Procedure steps
1. Check whether accounting is enabled on the Avaya Ethernet Routing Switch
460 Troubleshooting
8800/8600 and the modem is well connected.
8800/8600, ensure the DTE port is used on the Ethernet Routing Switch 8800/8600
side, and the DCE port is used on the customer PC side
+ server.
Switch 8800/8600 using the following CLI commands:
show radius info show tacacs info
OR
using the following ACLI commands:
show radius show tacacs
If TACACS+ failed, Radius may take over the AAA process.
Ethernet Routing Switch 8800/8600 always sends encrypted TACACS+
messages.
8800/8600:
Comments? infodev@avaya.com
July 2013