Pushing An Ssh Client Public Key To An External Server; Enabling Netconf - Cisco ASR 5500 System Administration Manual
Hide thumbs
Also See for ASR 5500:
- Administration manual (410 pages) ,
- Installation manual (192 pages) ,
- Installation procedure overview (6 pages)
Table of Contents
Advertisement
Enabling NETCONF
Pushing an SSH Client Public Key to an External Server
You must push the SSH client public key to an external server to support SSH/SFTP access to that server.
Step 1
From the Exec mode run the push ssh-key command.
host_name
[local]
host_name
[local]
host_name specifies the remote server using its logical host name which must be resolved via DNS lookup. It is expressed
as an alphanumeric string of 1 to 127 characters.
host_ip_address is expressed in IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.
user username specifies a valid username on the external server as an alphanumeric string of 1 to 79 characters.
context context_name specifies a valid context name. The context name is optional. If it is not provided the current
context is used for processing.
Step 2
Repeat Step 1 to support SSH/SFTP access on other external servers.
Step 3
Test SSH client login to an external server.
host_name
local]
Enabling NETCONF
An SSH key is a requirement before NETCONF protocol and the ConfD engine can be enabled in support of
Cisco Network Service Orchestrator (NSO).
Refer to the NETCONF and ConfD appendix in this guide for detailed information on how to enable NETCONF.
ASR 5500 System Administration Guide, StarOS Release 21.5
24
push ssh-key { host_name | host_ip_address } user username [ context context_name ]
#
#
ssh { hostname | ip_address } user username port port_number
#
Getting Started
Advertisement
Table of Contents
Troubleshooting
