Service stitching – L3 VPN services

Service stitching algorithm for L3 VPN services 

The following are the service stitching algorithm for L3 VPN services with their stitching criteria:

Algorithm

Stitching Criteria

route-target

Full mesh: sites must have inverse matching route-target values

Hub and spoke: sites must have inverse matching route-target values. If the 'hub' site is stitched after the 'spoke' sites, the spoke sites will be merged to the hub site's service. When the algorithm detects the need for one site to be merged, the info will be persisted to the nsp db. In the event of a pod restart, the service merge will resume after the pod is up.

service-name 

matching service-name

L3 VPN service stitching with route-target algorithm
 
1 

Stitch the L3 VPN service created on MD NE using the following API:

POST: (https://{{server}}/restconf/data/nsp-service-intent:stitchservices)

BODY: 

{ 
    "input":{ 
        "service-type":"l3vpn", 
        "algorithm":"route-target", 
        "sites":["92.168.96.46","92.168.96.190"] 
    } 
}

RESPONSE:

{ 
    "response": { 
        "status": 0, 
        "startRow": 0, 
        "endRow": 0, 
        "totalRows": 1, 
        "data": "Successfully submitted to Job Manager for Service Stitch processing with Job Name: L3 VPN_route-target-1726726571515", 
        "errors": null 
    } 
}
2 

Once the L3 VPN service stitching is successful, ensure the service gets listed in the NSP Service Management in 'Unknown' state.

End of steps