Which configuration step is taken on vManage after WAN Edge list is uploaded to support the on-boarding process before the device comes online?
Which configuration step is taken on vManage after WAN Edge list is uploaded to support the on-boarding process before the device comes online?
Before a WAN Edge device can be fully onboarded and come online, it must be set as valid after uploading the WAN Edge list to vManage. This step ensures that the device is authorized and ready to be managed by the network controllers. Completing this action signifies that the device is approved and prepared for the onboarding process, in line with how WAN Edge devices are validated and managed in a Cisco SD-WAN environment.
Correct answer is C, https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/system-interface/vedge-20-x/systems-interfaces-book/configure-devices.html in this document it states in section Upload WAN Edge Router Authorized Serial Number File To upload the WAN edge router authorized serial number file to Cisco vManage and then download it to controllers in the network: From the Cisco vManage menu, choose Configuration > Devices. Click WAN Edge List, and click Upload WAN Edge List. Under Upload WAN Edge List screen: Click Choose File and select the WAN edge router authorized serial number file you received from Cisco PnP. To automatically validate the routers and send their chassis and serial numbers to the controllers, ensure that the Validate the uploaded vEdge List and send to controllers check box is selected. If you do not select this option, you must individually validate each router in Configuration > Certificates > WAN Edge List. Click Upload. A list of routers in the network is displayed in the router table, with details about each router.
It's a poorly written question, because C and D are both required steps. Sending the list to the vSmart controllers is necessary, but it can be done without onboarding the devices at this time. Setting the devices as valid is what tells the vSmart to onboard those devices as soon as they come online.
D Question says: "to !!!support!!! the on-boarding process !!!before!!! the device comes online". 'Support' and 'before online' says to us that device must be staged, since it is not online (doesn't send traffic), but we must control it (hence, support it). We can do that if we stage device and send list to controllers. When we validate device, it comes online (and question says before it comes online).
C is the correct answer. The list has to be validated first before being sent to the other controllers.
D is correct
correct answer D
C is correct
vManage version 20.9 Configuration > Devices > Upload WAN Edge List Validate the uploaded vEdge List and send to controllers (there's only one option, not two)
I go with C See Page 18 https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/SDWAN/sdwan-wan-edge-onboarding-deploy-guide-2020nov.pdf
To fully onboard the device, the device state must be moved from staging to valid. In vManage under Configuration > Certificates > WAN Edge List, select the WAN Edge device(s) and change the state to valid under the Validity column and click Send to Controllers.
D Question says: "to !!!support!!! the on-boarding process !!!before!!! the device comes online".
C. Set the device as valid (to !!!support!!! the on-boarding process !!!before!!! the device comes online"). See the document linked below by CCNPCollab1297.
https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/SDWAN/sdwan-wan-edge-onboarding-deploy-guide-2020nov.pdf : Technical Tip: A WAN Edge device within staging state will establish only control connections with the SD-WAN controllers. No data plane connections are established across WAN Edge devices. To fully onboard the device, the device state must be moved from staging to valid. In vManage under Configuration > Certificates > WAN Edge List, select the WAN Edge device(s) and change the state to valid under the Validity column and click Send to Controllers.
It is asking for a configuration task on vManage, so that would be C The whitelist will be shared automatically with other controllers. No need to configure anything for that.
WAN Edge devices have to be known and authorized by all the SD-WAN controllers before allowing the device onto the network. D seems to be correct for me.
Yes you are right, but they need to be validated before, you can use the checkbox when uploading the list into the vManage, or you go to devices and validate them one by one and then you will share the valid list to the controllers. That is why when you do a show valid-vedges on the vSmart you will only see the ones that are valid and no the whole list.
I am not sure vBond will be able to orchestra the devices with vmanage with having known the list. So the answer is very clear to me.
I’d say C seems to be the likely answer based on Sky_Soul’s link.
C https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/SDWAN/sdwan-wan-edge-onboarding-deploy-guide-2020nov.pdf Page 76 Technical Tip: If Validate the uploaded vEdge List and send to controllers is not selected when the provisioning file is uploaded in vManage, the WAN Edge devices will be in imported into vManage and the device will be in an Invalid state and not shared to the other SD-WAN controllers. In order to join the overlay, each WAN Edge device must be changed to a Valid state, and the updated to other SD-WAN controllers in the deployment.