This document explains the process to enable IPv6/Dual stack addressing on a Controller.
Enabling dual stack in a new Controller deployment is straightforward (just add IPv6 address along with IPv4).
However, once a controller is deployed, it cannot be re-provisioned through the workflow. Any changes must be made directly from the appliance context.
If you add a new interface, update WAN IPs, or modify other parameters related to branch association, you must redeploy the workflow templates for the existing branches. After redeployment and committing the changes, the branches will associate with the controller based on the new or updated parameters.
Enable IPv6 on an existing controller
- Add IPv6 address under the WAN interface configuration,
Path: Networking > Interfaces > WAN Interface
- Add the IPv6 Default route in the associated Transport-VR (if the interface IP was assigned by DHCPv6, skip this option, as gateway should be assigned by the DHCP)
Path: Networking > Virtual Routers > Transport-VR (associated to WAN interface)
- Update the IPv6 info in the Controller’s System Site-Config and add a Circuit-Name. This info is pushed to branches as Controller details to connect and form SLA.
Path: Services > SDWAN > System > Site Config (Edit and select the interface where IPv6 was enabled)
This completes the Controller end configuration.
Next, proceed with the redeployment (redeploy workflow templates followed by commit) of existing branches (where IPv6 is already enabled on WAN or this IPv6 information needs to be updated).
If need to oboard a new branch with IPv6 address only, use the following script as a reference (use the actual IPs and Local/Controller IDs as per your setup) ,
From shell execute script,
sudo /opt/versa/scripts/staging.py -w 0 -c6 2001:db8:1::2 -s6 2001:db8:2::2/64 -g6 2001:db8:2::1 -l SDWAN-Branch@org.com -r Controller1-staging@org.com
Here is more information on branch deployment (new onboarding and existing ipv4 deployment) with IPv6 addressing.