Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Using UCSM package cisco-ucs-cli-3.3 I am trying to sync the configuration from a newly upgraded fabric. Below is the command line failure and after that is the log in ncs-java-vm.log. What I believe is happening is that the SSH client in NSO does ...
I've enabled the internal NSO ssh server on port 2024 and can login just fine. What I'd like to do is use preshared SSH keys instead of password to authenticate that connection. what configuration do i need to make this work?admin connected from 12...
Does anyone have a working example of a curl call to UCS Director REST API. Requests using the REST API browser seem to work but I have yet to replicate that on the command line. No amount of escaping seems to work. Neither GET nor POST etc etc.An...
Creating a vnic template appears to only like the default VLAN. Below is the XML and below that is the result: Error while performing vNIC template add task.1802 : is not a permitted VlanHas anyone else experienced this issue? What am I missing ...
A call like the following does not drill down into the entire config of the device:curl -u nsouser:nsouser http://127.0.0.1:8080/api/config/devices/device/ucsm011/config/org/service-profile/<service-profile>I have to do something like this in order t...
Found a workaround for the time being by simply proxying to the host NSO is running on. Not a solution but works for now.
set devices authgroups group jumphost umap nsouser remote-name localadmin
set devices authgroups group jumphost umap nsouser ...
Issue appears to be present in earlier versions as well (below version 4.6.1.3)
nsouser@ncs> request devices fetch-ssh-host-keys
fetch-result {
device pirl
result failed
info internal error
}
Finally got around to retesting this. Turns out if you generate a key with a comment containing spaces NSO will call it a bad key.
BAD: ssh-keygen -C ‘NSO SSH Key' -t rsa -f ./scripts/.ssh/id_rsa -N ''
vs
GOOD: ssh-keygen -C 'NSO-SSH-Key' -t r...
Upgraded to 4.6.1 and have the exact same issue: Presented a bad key.There is some basic issue where the service either doesnt find the key in the right place or thinks it is invalid.
Thanks for the suggestions Roque!No help with upped logging but here is my ssh -vvv result. Looked online quite a bit to see if there is an issue with public key mismatch or permissions or something like that but no help there. I decided to compare...