MENU
You are onboarding a branch with one WAN and one LAN interface. After a successful branch activation, the branch is not able to reach the Versa Controller. You realize that the WAN gateway IP address originally entered under the Device Bind Data menu in Versa Director is incorrect. Which action will you perform to solve the problem?
The correct action is to update the WAN gateway IP address in Device Bind Data and onboard the branch appliance again. Device Bind Data supplies site-specific values, such as WAN interface addressing and gateway information, that are merged with the workflow and template configuration during onboarding. If the wrong WAN gateway is entered, the branch may activate successfully from a workflow perspective, but the resulting WAN routing configuration is incorrect. As a result, the branch cannot establish proper transport reachability to the Controller. Versa troubleshooting documentation explains that, after establishing transport connectivity from a branch to a Controller, at least one WAN interface must be available, and the branch then establishes IKE-based IPsec connectivity to the Controller. If that IKE/IPsec connectivity fails, the Controller-facing ptvi interface remains down.
Changing the configuration only from the Appliance context is not the best answer because the incorrect value originated in the bind-data source used for provisioning. Modifying it manually from the branch CLI is also not recommended because the device is managed by Versa Director and template-driven configuration. Resetting the device does not automatically discover or ''ping'' the correct gateway. The correct remediation is to fix the bind data and repeat onboarding so the branch receives the correct generated configuration.
Currently there are no comments in this discussion, be the first to comment!