Service stitching – EPIPE/ELINE services

Service stitching algorithm for Epipe services

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

Algorithm

Stitching Criteria

route-target 

sites must have inverse matching route-target values and inverse matching local/remote ac values

service-name 

matching service-name

evi 

sites must have matching evi values and inverse matching local/remote ac values

local 

a single site with 2 access interfaces

vcid 

site's tunnel binding must have matching vcid

Note: Route-target and evi algorithms are for EVPN-EPIPE and outside the scope of this document. Service stitching with the other 3 algorithms are documented below.

Service stitching with service-name algorithm

Services which are to be stitched with service-name algorithm should have same service names on the end sites.

 
1 

Stitch the Epipe service created on MD NE using the following API:

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

BODY:

    { 
       "input":{ 
       "service-type":"eline", 
       "algorithm":"service-name",
       "sites":["92.168.96.190","92.168.96.46"]
       }
    }

RESPONSE:

    { 
       "response": { 
          "status": 0, 
          "startRow": 0, 
          "endRow": 0, 
          "totalRows": 1, 
          "data": "Successfully submitted to Job Manager for Service Stitch processing with Job Name: eline_service-name-1726659802472", 
          "errors": null 
       } 
    } 

2 

Ensure the service gets listed in the NSP Service Management in 'Unknown' state.

End of steps

Service stitching with local algorithm
 
1 

Stitch the Epipe service created on MD NE using the following API:

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

BODY:

    { 
       "input":{ 
       "service-type":"eline", 
       "algorithm":"local",
       "sites":["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:"eline_local-1726669622177", 
          "errors": null 
       } 
    } 

2 

Ensure the service gets listed in the NSP Service Management in 'Unknown' state.

End of steps

Service stitching with vcid algorithm 
 
1 

Stitch the Epipe service created on MD NE using the following API.

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

BODY:

    { 
       "input":{ 
       "service-type":"eline", 
       "algorithm":"vcid",
       "sites":["92.168.96.190","92.168.96.46"]
       }
    }

RESPONSE:

    { 
       "response": { 
          "status": 0, 
          "startRow": 0, 
          "endRow": 0, 
          "totalRows": 1, 
          "data": "Successfully submitted to Job Manager for Service Stitch processing with Job Name: eline_vcid-1725863475919", 
          "errors": null 
       } 
    } 

2 

Ensure the service gets listed in the NSP Service Management in 'Unknown' state.

End of steps