During onboarding, Versa Director shows the first branch-connect notification for a new CPE, but no later staged branch-connect notification appears. Which troubleshooting area should be investigated first?
The correct answer is B. Versa branch lifecycle notifications are generated at different stages of onboarding. The first notification indicates that the branch connected using factory-default configuration. After that notification, Versa Director pushes the staging configuration to the branch and requests a reboot. After rebooting with staging configuration, the branch should connect again to the Controller, and a later branch-connect notification should appear.
If this later staged connection notification does not appear, Versa's troubleshooting guidance says to debug either the data path or IPsec connectivity from the branch to the Controller. This makes sense because the branch must have working transport reachability and IKE/IPsec establishment toward the Controller before it can continue the SD-WAN lifecycle.
Analytics disk usage, LDAP authentication, and URL filtering are not part of the branch staging control path. They may affect monitoring, user identity, or security inspection after the site is operational, but they do not explain why the branch stops after the initial factory-default onboarding notification.
Cordell
1 day ago