This article provides procedure to onboard branch using IPv6. It can also be used as reference if IPv6 onboarding does not happens as expected. The steps are similar to IPv4 onboarding with slight differences here and there. This article assumes that user is already familiar with branch onboarding using ipv4.  

This document is based on R2.S2.2.

The difference between ipv4 and ipv6 onboarding is that instead of using IPv4 in the wan side we will be using IPv6 address on Controller and Branch WAN interfaces.

Note: Versa does not support IPv6 as Overlay.  

  1. Create parent organization as usual – same as onboarding using ipv4.

 

  1. Onboard controller

 

 

 

 

 

 

 

 

 

 

 

IPv6 address is specified here. IPv4 address also can be configured if required. 

 

Once controller is onboarded successfully, you will similar output like below:

admin@Controller1-cli> show interfaces brief

NAME         MAC                OPER  ADMIN   TENANT  VRF                 IP

------------------------------------------------------------------------------------------

eth-0/0       52:54:00:4c:b6:0b  up    up      0       global              10.192.135.3/16

tvi-0/2      n/a                up    up      -       -

tvi-0/2.0    n/a                up    up      1       org-Control-VR      10.0.128.1/32

tvi-0/3      n/a                up    up      -       -

tvi-0/3.0    n/a                up    up      1       org-Control-VR      10.0.192.1/32

tvi-0/4      n/a                up    up      -       -

tvi-0/4.0    n/a                up    up      2       org-sub-Control-VR  10.1.0.1/32

tvi-0/5      n/a                up    up      -       -

tvi-0/5.0    n/a                up    up      2       org-sub-Control-VR  10.1.64.1/32

tvi-0/602    n/a                up     up     -       -

tvi-0/602.0  n/a                up    up      1       org-Control-VR      169.254.0.2/31

tvi-0/603    n/a                up    up      -       -

tvi-0/603.0  n/a                up    up      1       Analytics-VR        169.254.0.3/31

vni-0/0       52:54:00:59:b5:3e  up    up      -       -

vni-0/0.0     52:54:00:59:b5:3e  up    up      1       org-Control-VR      192.168.1.3/24

vni-0/1       52:54:00:a7:d0:ed  up    up      -       -

vni-0/1.0     52:54:00:a7:d0:ed  up    up      1       wan-Transport-VR    2001:1::1/64

 

  1. Create sub organization. 

 

  1. Create post-staging template

 

IPv6 Static checkbox is marked as we wanted to use IPv6 for onboarding. LAN side also will have IPv6 address. 

 

 

Routing, Split Tunnels and Inbound NAT are not touched. In Services tab, check NGFW. 

 

 

  1. Create device group. 

  1. Onboard branch. 

 

Ensure desired IPv6 addresses are filled in properly. 

 

 

  1. On branch, go to shell mode and execute the script in directory - /opt/versa/scripts

 

sudo ./staging.py -w 0 -c6 2001:1::1 -s6 2001:2::2/64 -g6 2001:2::1 -l SDWAN-Branch@org.com -r Controller1-staging@org.com

 

  1. You will see similar output like below if branch is successfully onboarded. 

admin@Branch1-cli> show interfaces brief

NAME       MAC                OPER  ADMIN   TENANT  VRF                 IP

----------------------------------------------------------------------------------------

eth-0/0     52:54:00:08:05:be  up    up      0       global              10.192.135.5/16

ptvi2      n/a                up    up      2       org-sub-Control-VR  10.1.64.1/32

tvi-0/4    n/a                up    up      -       -

tvi-0/4.0  n/a                up    up      2       org-sub-Control-VR  10.1.0.103/32

tvi-0/5    n/a                up    up      -       -

tvi-0/5.0  n/a                up    up      2       org-sub-Control-VR  10.1.64.103/32

vni-0/0     52:54:00:e7:b7:d4  up    up      -       -

vni-0/0.0   52:54:00:e7:b7:d4  up    up      2       wan-Transport-VR    2001:2::2/64

vni-0/1    52:54:00:23:cc:f2  up     up     -       -

vni-0/1.0   52:54:00:23:cc:f2  up    up      2       org-sub-LAN-VR      2002:1::1/64