Customer Unable To Log On Using Telnet Or Rlogin; Customer Unable To Log On Using Ssh - Avaya 8800 Troubleshooting Manual

Upper layer troubleshooting
• Customer unable to log on by any means (Telnet, rlogin, SSH, and PPP)
• Administrator unable to obtain accounting information from the TACACS+ server
page 460
• Administrator unable to receive trap packets from the Avaya Ethernet Routing Switch
8800/8600
• User unable to login

Customer unable to log on using Telnet or rlogin

If customers are unable to log on using Telnet or rlogin, perform the following steps.
Procedure steps
1. Check whether the TACACS+ server is available and reachable.
2. On the TACACS+ server, check whether the privilege level is set correctly.
3. On the TACACS+ server, check whether the password and user name is configured
4. On the TACACS+ server, check whether the Avaya Ethernet Routing Switch
5. If you can log on to the Avaya Ethernet Routing Switch 8800/8600, check whether
6. Using the output from the previous step, verify whether the key field configured on
7. Also using the output from the preceding step, verify whether the single-connection

Customer unable to log on using SSH

If customers are unable to log on using SSH, perform the following steps.
458 Troubleshooting
on page 461
on page 461
correctly.
8800/8600 IP address is configured in the trust list.
the TACACS+ server configured on the router has the correct IP address using the
following CLI command:
show tacacs server config
OR
using the following ACLI command
show tacacs
the router is the same as that on the TACACS+ server.
option is configured on the router, and if so, whether the TACACS+ server supports
single-connection.
Comments? infodev@avaya.com
on page 460
on
July 2013