rconsole
A remote console session is not established.
Privileged EXEC mode
The rconsole command is used primarily to allow the active
controller to establish a remote connection to a unit in the stack.
Member and standby controller stack units can use the rconsole command only
to establish a remote connection to the active controller. By default, a stack
unit's console is automatically redirected to the active controller's console.
If
the user has terminated the rconsole session on a stack member to place the unit
in
local console mode, the rconsole active command can be used to
reconnect to the active controller console, The rconsole command must
be followed by the keyword active when the target unit is the
stack active controller. Attempting to use the unit ID of the active controller
produces an error.
When the rconsole command is
entered from a stack unit other than the active controller, you are prompted to
authenticate with username and password. The username and password are not required
when the command is entered from the active controller.
On stack switchover, all unit consoles require the user to log in again.
By default, an rconsole session times
out after two minutes of inactivity, which is the same default for any CLI session.
The timeout for an rconsole session is controlled by the cli timeout command. If
the cli timeout setting is "0" the rconsole session, like other CLI sessions,
never
times out.
To terminate a session, enter the exit command from the
User EXEC level.
The following example establishes a remote console session from a stack member to the stack active controller. A login username ("johnc" in the example) and password are required.
device# rconsole active
console going online
Press any key to continue..
Press any key to continue...
Connecting to active controller 1 console...(Press Ctrl Shift - x to exit)
Ruckus-ICX login: johnc
Password:
7550-Stack> enable
No password has been assigned yet...7550-Stack#
7550-Stack# show stack
T=7m17.4: alone: standalone, D: dynamic cfg, S: static
ID Type Role Mac Address Pri State Comment
1 S ICX7550-48 active 4cb1.cd20.1f4e 0 local Ready
2 S ICX7550-48 standby 4cb1.cd20.23ae 0 remote Ready
3 S ICX7550-24ZP member 94bf.c43f.c33e 0 remote Ready
active standby
+---+ +---+ +---+
-2/2| 1 |2/1--2/2| 2 |2/1--2/2| 3 |2/1-
| +---+ +---+ +---+ |
| |
|-------------------------------------|
Standby u2 - protocols ready, can failover or manually switch over
Current stack management MAC is 4cb1.cd20.1f4e
slot 2: config = oper = stack-40g
All UP stack ports operate at 40G
In the following example, a remote console session
is established with member stack unit 3. Notice the difference in the device
prompt. The output of the show stack command
is different when entered for a stack member.
ICX7550-48 Router# rconsole 3
Connecting to unit 3... (Press Ctrl-x or type exit to exit)
[MEMBER]rconsole-3@ICX7550-24ZP Router#
[MEMBER]rconsole-3@ICX7550-24ZP Router# show stack
T=3h16m53.3: alone: standalone, D: dynamic cfg, S: static
ID Type Role Mac Address Pri State Comment
3 S ICX7550-24ZP member 94bf.c43f.c33e 0 local Ready
active standby
+---+ +---+ +---+
-2/2| 3 |2/1--2/2| 1 |2/1--2/2| 2 |2/1-
| +---+ +---+ +---+ |
| |
|-------------------------------------|
Current stack management MAC is 94bf.c43f.c33e
slot 2: config = oper = stack-40g/100g
All UP stack ports operate at 40G
[MEMBER]rconsole-3@ICX7550-24ZP Router#
| Release version | Command history |
|---|---|
| 08.0.00a | This command was introduced. |
| 09.0.00 | This command was modified to require authentication when issued from a stack member other than the active controller. |