Logging in through the console port
When a device becomes a stack member, it establishes a remote connection to a virtual console port on the active controller. Input and output are relayed between the physical console port on the stack member and the virtual console port on the active controller. Because each stack member connects to an independent virtual console port on the active controller, the console ports on multiple stack units may be used simultaneously.
When a stack unit establishes communication with the active controller, it also establishes a remote console session to the active controller. In a normally functioning stack, a console cable may be connected to any of the stack units and provide access to the same commands on the active controller.
To establish a remote console session on a stack unit, enter the
rconsole command followed by the stack unit ID as shown in the following example.
device# rconsole 1
You can terminate a session between stack members in any of these ways:
rconsole connections from stack units to the active controller, the escape sequence and other
methods of terminating the session are not available.
rconsole connections from stack units to the active controller. To see these error messages,
you must connect a console cable to the active controller itself.
The following example shows how to establish a remote console session to a stack
member and obtain status information. Notice that the
show stack command on the stack member displays different information from what is shown when
the
show stack command is entered on the active controller.
A remote console session is established with stack unit 2 in the following example.
device# rconsole 2 Connecting to unit 2... (Press Ctrl-O X to exit) rconsole-2@device# show stack ID Type Role Mac Address Prio State Comment 2 D ICX7650-48F standby 94fd.2e05.1a10 0 local Ready rconsole-2@device# exit rconsole-2@device> exit Disconnected. Returning to local session...