When device credentials are being checked: Hi,Were trying to get to the bottom of CSCwb79704 - Playbook is able to run (UI or API) with wrong device credentials.Neha investigated it and saw that the credential check happens only when the new configuration is new and does not exist on the device, however, when it is already exists on the device, credential check is not performed as no config is pushed to the device. Is this logic part of NSO? Is it documented somewhere?Thanks,Mirel.
Hi Mirel,Yes , NSO checks for credentials only when there is a difference.When the config already exists on the NSO then it does not perform the operation since there is no diff.Thanks and Regards,Nishad Subair,Thanks for the confirmation. Is this documented in any NSO guide/wiki/doc?In the cdet CSCwb79704, user is trying to configure the attached service and we see that the service gets configured even if he passes wrong credentials for the devices. I am not completely sure what the service is trying to configure here, but it works with wrong device credentials even for the first time. From NCA playbook, we have verified that the credentials entered by the user are being set in NSO. Can you please take a look and let us know if device cred check is expected here or not. Hi Neha,I am not sure if the config is being pushed to the device here, looking at the template. To confirm, can you provide the complete NSO logs with xpath trace and trace enabled on the device? Or provide the setup with error.NSO throws an error only when there is an attempt to connect to the device. NSO can connect to device either via device config push or user trying to connect/sync-from/sync-to manually using the command on device tree. Device config push can be done via service or pushing the config on device from NSO.Please look at NSO getting started guide or the development guide for more info about NSO device manager throwing errors.ThanksSahithiHi Sahithi,Please find below the NSO details, where service has been installed. you can take a look at the logs and also try doing some configurations if needed. Also providing the payload for the config that user has tried to do here:NSO: 172.20.200.70admin/Cwork123!Devices: xrv9k-1 : 192.168.6.50 admin/cisco123xrv9k-2 : 192.168.6.51 admin/cisco123Config:"params": {"config": {"tailf-ncs:services": {"lowlatencypolicies:lowlatencypolicies": [{"devices": [{"name": "xrv9k-2","tailend": [{"color": 3000,"forward-class": 1,"ipaddress": "10.3.0.4","tailendname": "xrv9k-1"}]}],"name": "test"}]}},"nso_instance": "nso101","operation": "configure","path": "/ncs:services/lowlatencypolicies:lowlatencypolicies"Please let me know, if you need anything else from my side.As discussed on the call, NSO exhausts all methods of authentication before throwing connection refused error.Please check NSO guides for more on this behavior.Will be closing the ticket as there is no issue on NSO or TSDN CFP.ThanksSahithi