3Com WX3000 When the Device Acts as an SSH Client and the Authentication Type is Publickey

1-31
[device-Vlan-interface1] ip address 10.165.87.137 255.255.255.0
[device-Vlan-interface1] quit
# Establish a connection to the server 10.165.87.136.
[device] ssh2 10.165.87.136
Username: client001
Trying 10.165.87.136 ...
Press CTRL+K to abort
Connected to 10.165.87.136 ...
The Server is not authenticated. Do you continue to access it?(Y/N):y
Do you want to save the server's public key?(Y/N):n
Enter password:
********************************************************************************
* Copyright(c) 2004-2009 3Com Corp. and its licensors. All rights reserved. *
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
********************************************************************************
<device>
When the Device Acts as an SSH Client and the Authentication Type is Publickey
Network requirements
As shown in Figure 1-24, establish an SSH connection between Switch A (SSH Client) and Switch B
(SSH Server) for secure data exchange. The user name is client001 and the SSH server’s IP address is
10.165.87.136. Publickey authentication is required.
Figure 1-24 Network diagram of SSH client configuration when using publickey authentication
Switch B
SSH Server Switch A SSH ClientVLAN-Interfa ce 1
10.165.87.137./24
10.165.87.136./24
VLAN-Interfa ce 1
Configuration procedure
In public key authentication, you can use either RSA or DSA public key. Here takes the DSA public key
as an example.
z Configure Switch B
# Create a VLAN interface on the device and assign an IP address, which the SSH client will use as the
destination for SSH connection.