During onboarding, Versa Director shows the first branch-connect notification for a new CPE, but no later staged branch-connect notification appears…

In the Versa onboarding process, the "first branch-connect" notification in Versa Director signifies the successful completion of ZTP Stage 1, where the branch CPE has connected to the staging server. The subsequent "staged branch-connect" notification indicates the successful completion of Stage 2, where the CPE has established a control connection to the Versa Controller. The absence of this second notification strongly implies a failure during Stage 2. This stage is critically dependent on IP connectivity and successful IPsec tunnel establishment between the branch and the Controller. Therefore, investigating this data path is the logical first step.

A. Versa Analytics disk usage relates to log storage and would not prevent the initial control plane connection between a branch and a Controller.

C. LDAP authentication is used for administrative user access to Versa Director, not for the device's automated onboarding process.

D. The URL filtering database is a security feature downloaded after the device is fully onboarded and operational; it is not a factor in initial connectivity.

Versa Networks, "VOS™ Zero Touch Provisioning Deployment Guide," Version 22.2.1, Chapter: Troubleshooting ZTP, Section: Stage 2 Failures, p. 45. (This section identifies connectivity issues between the branch and Controller as the primary cause of Stage 2 failures.)

Versa Networks, "Versa Secure SD-WAN Troubleshooting Guide," Version 21.2.3, Section: Onboarding and Provisioning Issues, Subsection: Device Stuck After Staging Server Connection. (This document outlines troubleshooting steps that prioritize checking firewall rules, routing, and IPsec logs for the branch-to-Controller path.)