Returning To Administrator Mode From Configuration Command Mode Is Not Possible - Alaxala AX6700S series Troubleshooting Manual

3. Troubleshooting Functional Failures During Operation
Table 3-5: Problems occurring during connection to a remote terminal and action to take
No. Problem
1 Remote connection is not
possible.
2 Login is not possible.
3 Key entry is not accepted.
4 A user remains logged in.
3.3.3 Returning to administrator mode from configuration command mode is
not possible
If you cannot return to administrator mode from configuration command mode, resolve the
problem by using either of the following methods.
(1) When connected to a console
Use the following procedure to forcibly log out the target user:
1. Use the
Execution example
(config)# $show sessions
operator console admin 1 Jan 6 14:16
28
Perform the following procedure:
1. Use the
for remote connection has been established.
2. After the "connection established" message is displayed, if it takes time
before the prompt appears, communication with the DNS server might not be
possible. (If communication with the DNS server is not possible, it takes
about five minutes before the prompt appears. This time is a general estimate
and varies depending on the network status.)
Perform the following procedure:
1. Make sure that the terminal you are using has an IP or IPv6 address that is
permitted in the access list for the configuration command
Also, make sure that
configuration command access list. (For details, see the Configuration
Guide.)
2. Make sure that the maximum number of users who can log in has not been
exceeded. (For details, see the Configuration Guide.)
If the number of login users has reached the maximum and if connection from
a remote terminal to the Switch is lost and then restored, 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. Use the
make sure that a protocol for which access to the Switch is prohibited is not
used. (For details, see the manual Configuration Command Reference.)
4. Use the
that the RADIUS or TACACS+ authentication is not set. (For details, see
3.3.4 Login authentication using RADIUS/TACACS+ is not possible.)
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 respond because Ctrl + S was pressed. Press any key.
Either wait for the user to be automatically logged out, or log in again and delete
the login user by using the
configuration, the editing has not been finished and the configuration might have
not been saved. Log in to the Switch again and enter configuration mode to save
the configuration, and then finish editing.
command to check the login number of the target user.
show sessions
Action
command from a PC or workstation to make sure that a route
ping
is not specified for the IP or IPv6 address set in the
deny
configuration command in
transport input
aaa authentication login
command. If the user was editing the
killuser
Login number of the target user
line vty
mode to
line vty
configuration command to make sure
mode.