User guide
1. To connect to a target device or appliance console, open your SSH client and enter the
following values in the provided text fields:
• <zone1/username>:
Specify the highest level zone for which you have access rights. If a zone is
not specified for the username, the top level zone is assumed. If you do not
have access to this zone, the connection attempt fails.
• <zone2/targetdevicename>@ (to connect to a target device)
-or-
<zone2/appliancename>@ (to connect to an appliance console)
If the appliance resides in a zone below your highest level zone, specify a
zone. If a zone is not specified, it is assumed that unit belongs to the zone
specified for the username. If the unit does not reside in this zone, the
connection attempt fails.
• host name or IP address of the DSView server
NOTE: If DS Zones are not enabled, you do not need to specify a zone for the username or appliance. For more
information about zones, see DS Zones on page 249.
To connect to a target device using the Linux or Unix SSH command, enter a
command in the following format:
<zone1/username>:<zone2/target device name>@<host name or IP address of
DSView server>
For example, a command to open an SSH session to a target device may look like this:
ssh -p 4122 zone 1 /jsmith:zone 2 /Boston@ 172.30.1 9.1 0 1
To connect to an appliance console using the Linux or Unix SSH command, enter a
command in the following format:
<username>:<appliance name:>@<host name or IP address of DSView server>
For example, a command to open an SSH session to an appliance console may look
like this:
ssh -p 4122 zone 1 /jsmith:zone 2 /ACS_ Lab:@1 72.3 0 .19.101
NOTE: The colon is used to delimit different arguments; however, if a colon is contained within the name, then a
double backslash may be used as an escape sequence to include the colon in the name. For example, if the
username is “sanders:”, a command to open an SSH session to a target device may look like this:
ssh -p 4122 zone1/sanders\\::zone2/Boston:5@172.26.5.100
2. If a user SSH key has been configured, the session is automatically authenticated based on
the key. The user SSH key must be stored on the DSView server specified in See "To
Chapter 14: SSH Passthrough Sessions 225