Q: 15
DRAG DROP Drag and drop the properties from the left onto the Cisco SD-WAN components that perform them on the right. 
Drag & Drop
Discussion
vSmart handles both fabric discovery and control plane, vBond is for orchestration, and WAN Edge does ZTP. That's what Cisco recommends, fits with how management and onboarding work. Pretty sure this is right but let me know if you see it different.
vSmart: fabric discovery, control plane. vBond: orchestration. WAN Edge: zero-touch provisioning.
Seen similar on practice-if vBond loses connectivity, ZTP fails and orchestration can't happen. vSmart never does ZTP so careful not to mix those.
Seen similar on practice-if vBond loses connectivity, ZTP fails and orchestration can't happen. vSmart never does ZTP so careful not to mix those.
vSmart: handles fabric discovery, manages control plane. vBond: provides orchestration. WAN Edge: supports ZTP.
But isn't there a catch if vBond is down? ZTP and onboarding won't work at all, so the mapping depends on initial device contact. Not 100% sure since some docs say vManage does management plane too.
But isn't there a catch if vBond is down? ZTP and onboarding won't work at all, so the mapping depends on initial device contact. Not 100% sure since some docs say vManage does management plane too.
vBond: orchestration, WAN Edge: zero-touch, vSmart: fabric discovery and control plane (I think).
Pretty sure: vBond goes with orchestration, WAN Edge for ZTP, vSmart is both fabric discovery and control plane.
Be respectful. No spam.
