Netconf Over Ssh Configuration Example - HP MSR Series Configuration Manual

.++++++++++++++++++++++++++++++++++++++++++++++++++*
........+......+.....+......................................+
...+.................+..........+...+.
Create the key pair successfully.
# Enable the SCP server.
[RouterB] scp server enable
# Assign an IP address to GigabitEthernet 2/0/1. The client uses this address as the destination
for SCP connection.
[RouterB] interface gigabitethernet 2/0/1
[RouterB-GigabitEthernet2/0/1] ip address 192.168.0.1 255.255.255.0
[RouterB-GigabitEthernet2/0/1] quit
# Create a local device management user client001.
[RouterB] local-user client001 class manage
# Set the password to aabbcc in plain text for the local user client001.
[RouterB-luser-manage-client001] password simple aabbcc
# Authorize the local user client001 to use the SSH service.
[RouterB-luser-manage-client001] service-type ssh
# Assign the user role network-admin to the local user client001.
[RouterB-luser-manage-client001] authorization-attribute user-role network-admin
[RouterB-luser-manage-client001] quit
# Configure the SSH user client001. Specify the service type as scp and the authentication
method password for the user.
[RouterB] ssh user client001 service-type scp authentication-type password
2. Assign an IP address to GigabitEthernet 2/0/1 on the SCP client.
<RouterA> system-view
[RouterA] interface gigabitethernet 2/0/1
[RouterA-GigabitEthernet2/0/1] ip address 192.168.0.2 255.255.255.0
[RouterA-GigabitEthernet2/0/1] quit
[RouterA] quit
3. Connect to the SCP server, download the file remote.bin from the server, and save it locally to
the file local.bin.
<RouterA> scp 192.168.0.1 get remote.bin local.bin
Username: client001
Press CTRL+C to abort.
Connecting to 192.168.0.1 port 22.
The server is not authenticated. Continue? [Y/N]:y
Do you want to save the server public key? [Y/N]:n
client001@192.168.0.1's password:
remote.bin

NETCONF over SSH configuration example

Unless otherwise noted, devices in the configuration examples are in non-FIPS mode.
When you configure NETCONF-over-SSH on a device that operates in FIPS mode, follow these
restrictions and guidelines:
•
The modulus length of the key pair must be 2048 bits.
100% 2875
429
2.8KB/s 00:00