Controller Based WLANs

Remote Telnet or SSH Session from the Controller

Aruba Employee
Q:

How to Remote Telnet or SSH Session from the Controller



A:

Starting from ArubaOS 6.5, an administrator can initiate a remote telnet or SSH session from the controller to a remote host. The host can be a controller or a non-Aruba host.

To initiate a telnet session from the controller to a remote host:
1. Initiate an SSH session to the controller.
2. In the enable mode, execute the telnet <user> <remote-host> [<port-num>] command.
        user: User name of the remote host.
        remote-host: IPv4 or IPv6 address of the remote host.
        port-num: Telnet port number of the remote host. This is an optional parameter.
3. Once successfully connected, the remote host prompts the credentials. Enter the remote host credentials.


To initiate an SSH session from the controller to a remote host:
1. Initiate an SSH session to the controller.
2. In the enable mode, execute the ssh <user-at-host> command.
       user-at-host: Username and IPv4 or IPv6 address of the remote host in the user@host format.
Once successfully connected, the remote host prompts the credentials.

3. Enter the remote host credentials.
To end the remote host session, execute the exit command. The remote host displays the following message:
(remote-host) #exit
Connection closed by foreign host.
(host) #

 

Limitations


This feature has few limitations. They are:

 

  • This feature is supported from the SSH session of the controller only. 
  • There is an inactivity timeout for the CLI sessions. When an administrator initiates a remote session (inner) from the controller’s SSH session (outer), and the remote session takes more time than the inactivity timeout session, the outer session times out although the inner session is active. The administrator has to log back in to the outer session once logged off from the inner session.
  • Designated telnet client control keys do not work for remote telnet sessions. When an administrator initiates a remote telnet session (inner) from the controller’s SSH session (outer), the designated telnet client control keys functions for the outer SSH session only. The administrator should designate unique control keys for each remote telnet sessions.
Version history
Revision #:
2 of 2
Last update:
‎10-18-2016 04:37 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.