Alaxala AX2500S, Руководство по устранению неисправностей

Страница: 45 / 136

3 Troubleshooting Functional Failures During Operation
19
3.2.2 Login from a remote terminal is not possible
If a problem occurs during connection to a remote terminal (telnet, FTP, etc.), check the
status according to the following table.
Table 3-2 Problems occurring during connection to a remote terminal and action to take
No. Problem Action
1
Remote connection is not
possible.
Perform the following procedure:
1.
Use the
ping
operation command from a PC or workstation to make
sure that a route for remote connection has been established.
2 Login is not possible. Perform the following procedure:
1.
Make sure that the
line vty
configuration command or
ftp-server
has been set. (For details, see the Configuration
Guides .)
2. Make sure that the terminal you are using has an IP address that is
permitted in the access list for the configuration command
line vty
mode. Also, make sure that
deny
is not specified for the IP address
set in the configuration command access list. (For details, see the
Configuration Guides. )
3. Make sure that the maximum number of users who can log in has not
been exceeded. (For details, see the
Configuration Guides. )
4. Check if there are any terminals for which login operation has not
been completed. (Login is incomplete if the terminal is waiting for
user ID and password entry or if a login attempt has failed.) If such
terminals are present, finish the communication software of those
terminals.
5. Check if there was any event that might have caused connection
from a remote terminal to the Switch to be temporarily lost during a
login attempt.
If a user is logged in and connection from a remote terminal to the
Switch is lost and then restored, the Switch retains the session
information. Due to this, no more users will be able to log in from a
remote terminal until the TCP protocol of the session times out and
the session is disconnected. Although the timeout period of the TCP
protocol varies depending on the status of a remote terminal or the
network, the protocol usually times out after 10 minutes.
3 Key entry is not accepted. Perform the following procedure:
1.
Data transmission might have been interrupted by XON/XOFF flow
control. End the interruption by pressing
Ctrl+Q . If the Switch still
does not accept entry from the keys after this operation, perform
steps 2 and 3.
2. Make sure that the communication software settings are correct.
3. The screen might not be responding because Ctrl+S was pressed.
Press any key.
4 A user remains logged in. Wait until the user is automatically logged out (a maximum of 60 minutes).
If you were editing the configuration, log in to the Switch again and enter
configuration mode to save the configuration, and then finish editing.