The best solution I found was to create a new ssh key, then copy this key into all my devices ssh folders. I have encountered various SSH errors as I got into NSO recently. A potential work-around could be to disable radius/tacacs in the router if possible.įrom the NSO side a work-around has been proved successful is to use a "proxy" to connect to the device - in this example uses the NSO server localhost as proxy:ĭevices authgroups group asr9k-2-via-localhost default-map remote-name remote-password ĭevices device asr9k-2-via-localhost address 127.0.0.1 port 22ĭevices device asr9k-2-via-localhost authgroup asr9k-2-via-localhost device-type cli ned-id cisco-ios-xr protocol sshĭevices device asr9k-2-via-localhost state admin-state unlockedĭevices device asr9k-2-via-localhost ned-settings cisco-iosxr proxy remote-connection sshĭevices device asr9k-2-via-localhost ned-settings cisco-iosxr proxy proxy-prompt (For example: ".*" for prompt user-pc:~$ >ĭevices device asr9k-2-via-localhost ned-settings cisco-iosxr proxy remote-address ĭevices device asr9k-2-via-localhost ned-settings cisco-iosxr proxy remote-port 22ĭevices device asr9k-2-via-localhost ned-settings cisco-iosxr proxy remote-name ĭevices device asr9k-2-via-localhost ned-settings cisco-iosxr proxy remote-password Presuming this is the issue, it has been fixed in later releases so if you can upgrade that may resolve the issue. ![]() ![]() Yes, this behavior has been seen with a specific version or XR 6.5.2.
0 Comments
Leave a Reply. |