ISSUE:


Appliance:


[admin@versa-branch-11: ~] # sudo /opt/versa/scripts/./staging.py -l SDWAN-Branch@Provider.com -r controller-1-staging@Provider.com -n SR110 -c 192.168.17.3 -w 0 -s 192.168.19.11/24 -g 192.168.19.1

 => Setting up staging config

 => Checking if all required services are up

 => Checking if there is any existing config

 => Generating staging config

 => Config file saved staging.cfg

 => Saving serial number

 => Loading generated config into CDB 


admin@versa-branch-11-cli> show interfaces brief | tab

NAME       MAC                OPER  ADMIN  TENANT  VRF     IP                

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

eth-0/0    00:50:56:81:75:1c  up    up     0       global  10.22.5.11/23    

tvi-0/1    n/a                up    up     -       -                        

tvi-0/1.0  n/a                up    up     1       mgmt    10.0.1.22/24                                    <<<Receiving the management IP

vni-0/0    00:50:56:81:82:be  up    up     -       -                        

vni-0/0.0  00:50:56:81:82:be  up    up     1       grt     192.168.19.11/24  

vni-0/1    00:50:56:81:ec:0d  down  down   -       -      


admin@versa-branch-11-cli> show orgs org-services Provider ipsec vpn-profile branch ike history

Local Gateway: 192.168.19.11      Remote Gateway: 192.168.17.3

  Last Known State        : Active                                                                                 <<<IKE is successful

  Last State Timestamp    : 2018-05-18T09:41:15.428401-08:00

  Event History:

   0. Event        : IKE Done

      Timestamp    : 2018-05-18T09:41:15.428404-08:00

      Role         : initiator

      Inbound SPI  : 0xc3d7d3e93b5d0002

      Outbound SPI : 0x3910232bea7e0002


Director:


- Director shows that the deployment has been successful,





SOLUTION:


Please make sure that the global tenant-id on the Controller and the Branch is same,


Controller:

admin@controller-1-cli(config)% show orgs org
org Provider {
....
....
    sd-wan {
        site {
            global-tenant-id            4;                          <<<<Not matching the global-id of the appliance


Appliance:

admin@versa-branch-11-cli(config)% show orgs org
org Provider {
....
....
    }
    sd-wan {
        site {
            global-tenant-id            1;                           <<<<Not matching the global-id of the controller


On the CPE, global tenant id needs to be 4 assuming that on the Controller, the staging VPN profile ins the “Provider” org.


To change this on the CPE, Please do the following on the CPE: 


admin@versa-branch-11-cli>  request erase running-config 


This will delete all the config and restart. Wait for services to come up.Then re-run the staging script as follows: 


[admin@versa-branch-11: ~] # sudo /opt/versa/scripts/./staging.py -l SDWAN-Branch@Provider.com -r controller-1-staging@Provider.com -n SR110 -c 192.168.17.3 -w 0 -s 192.168.19.11/24 -g 192.168.19.1  -gt 4