Alcatel-Lucent OmniSwitch AOS Release 6 Manual page 77

Logging Into the Switch
Note. You can only use a host name instead of an IP address if the DNS resolver has been configured and
enabled. If not, you must specify an IP address. See
Note. Use of the cmdtool OpenWindows support facility is not recommended over Secure Shell connec-
tions with an external server.
The following command establishes a Secure Shell interface from the local OmniSwitch to IP address
11.133.30.135:
-> ssh 11.133.30.135
login as:
Note. If Secure Shell is not enabled on a switch, use the ssh enable command to enable it.
You must have a login and password that is recognized by the IP address you specify. When you enter
your login, the device you are logging in to, will request your password as shown here:
-> ssh 11.133.30.135
login as: rrlogin1
rrlogin1's password for keyboard-interactive method:
Once the Secure Shell session is established, you can use the remote device specified by the IP address on
a secure connection from your OmniSwitch.
Note. The login parameters for Secure Shell session login parameters can be affected by the
session login-attempt
The following drawing shows an OmniSwitch, using IP address 11.233.10.145, establishing a Secure Shell
session across a network to another OmniSwitch, using IP address 11.133.30.135. To establish this session
from the console in the figure below, you would use the CLI commands shown in the examples above.
Once you issue the correct password, you are logged into the OmniSwitch at IP address 11.133.30.135.
Console
To view the parameters of the Secure Shell session, issue the
-> who
OmniSwitch AOS Release 6 Switch Management Guide
and session login-timeout
OmniSwitch
11.233.10.145
Secure Shell Session between Two OmniSwitches
Chapter 1, "Managing System Files,"
CLI commands.
who command. The following will display:
July 2010
Using Secure Shell
for details.
OmniSwitch
11.133.30.135
page 2-15