vManage protocol that pushes new OS to vEdge

[Steytler]

hey folks - 

What protocols are used from vManage to push a file for an OS upgrade to the controllers and edge devices?  Is it using NETCONF?   I know NETCONF is used to build the vBond and vSmart controllers. That's why when you build on prem, you have to take the "tunnel" command off VPN0 and permit SSH .  But, what is the vManage using to push the OS file to the vEdge?  This info is impossible to find!  Nothing gets into the weeds of what's going on behind the "Green Curtian."

Thanks!!

[svemulap@cisco.com · Accepted solution]

Yes. vManage uses NETCONF port 830.
You can see it in /var/log/nms/vmanage-server.log, when the image push happens.
Example from my lab node:

08-Mar-2022 15:45:58,061 PST INFO [] [DataCollectionManager] (Thread-195) || ******* Requested device 199.99.99.99, Adding to dataCollectionQueue.
08-Mar-2022 15:45:58,078 PST INFO [] [NetConfClient] (device-data-collection-37603) || Connecting to device : 199.99.99.99 Port: 830 user : vmanage-admin
08-Mar-2022 15:45:58,080 PST INFO [] [DeviceActionStatusDAO] (device-action-software_install-7) || isDeviceAlreadyInProgress: count 0
08-Mar-2022 15:45:58,081 PST INFO [] [DefaultActionWorker] (device-action-software_install-7) || Device: 199.99.99.99, action: software_install, actionConfig: {input={vEdgeVPN=0, vSmartVPN=0, data=[{family="csr1000v", version="17.06.02.0.2786.1637700778"}], versionType="vmanage", reboot=false, sync=true}, devices={deviceIP="199.99.99.99", deviceId="CSR-EF6B8B26-C357-F931-02C3-13BF5D59113D", version="17.06.02.0.2786.1637700778", order="0", isNutellaMigration=false}}

HTH

[Steytler]

FANTASTIC - thank you for doing that and posting the results!  VERY helpful!!

[Steytler]

Combing through oodles of documentation I found this guide from 2020 which has very explicit information on what kind of protocol and port is used for every step of the Controller Bringup Process.  It's been 5 days since my original post.  The struggle to find consistent and informative documentation from release to release is mind boggling.  I hope this helps every one.

https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/SDWAN/sdwan-wan-edge-onboarding-deploy-guide-2020nov.pdf