339
[SwitchA] interface vlan-interface 2
[SwitchA-Vlan-interface2] ip address 192.168.0.2 255.255.255.0
[SwitchA-Vlan-interface2] quit
[SwitchA] quit
3. Connect to the SCP server, download the file remote.bin from the server, and save it locally with
the name local.bin.
<SwitchA> 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 100% 2875 2.8KB/s 00:00
NETCONF over SSH configuration example with
password authentication
Unless otherwise noted, the switch in the configuration example is 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.
• When the device acts as a NETCONF-over-SSH server, only RSA and ECDSA key pairs are
supported.
Network requirements
As shown in Figure 102:
• The switch uses local password authentication.
• The client's username and password are saved on the switch.
Establish a NETCONF-over-SSH connection between the host and the switch, so that you can log in to the
switch to perform NETCONF operations.
Figure 102 Network diagram
Configuration procedure
# Generate RSA key pairs.
<Switch> system-view
To Next Page
Loading...
Need help?
General