Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Since we are running a mock PCE server, it is important to use the exact endpoint names as this PCE server expects to receive. Therefore, a user needs to make sure that the endpoint names created in previous steps mentioned in reference (*) below, are with these names:(star) UI Operation Guidance for Guilin

  • For Domain A:
    • tranportEp_src_ID_111_1
    • tranportEp_src_ID_111_2
    • tranportEp_src_ID_114_1
  • For Domain B:
    • tranportEp_src_ID_212_1
    • tranportEp_src_ID_214_1
    • tranportEp_src_ID_212_2

...

The recommended way to create the endpoints is doing it manually using the

...

postman collection provided in this wiki page. This postman collection does have the required payloads for each of these endpoints (i.e.

...

networkroutes)

...

. The payloads have correct "next-hop" values for each of these 6

...

endpoints. These "next-hop" values are based on our two topologies.  Included in this postman collection is the URL and the payload required to create 3 logical links that are

...

connecting these 6 endpoints, however, you do not need to create these logical-links manually because SO creates them for you. You only need to do it manually if you are not testing with SO and instead, you are calling SDNC directly (no SO involved). Please see the postman collection for details.


View file
nameNetwork Routes and Logical Links Creation.postman_collection.json
height250


However, if a user needs to create them using the UUI way described in reference (star) below, make sure to use the following values for AN and CN respectively:

(star) UI Operation Guidance for Guilin

  • AN: networkId-providerId-10-clientId-0-topologyId-2-nodeId-10.1.1.1-ltpId-512
  • CN: networkId-providerId-20-clientId-0-topologyId-2-nodeId-10.2.1.2-ltpId-512

After you created the endpoints for AN and CN as stated above, the outcome is a logical-link that gets created in your AAI. Find which “logical-link” is created in your AAI: You can retrieve all of your logical-links by sending a GET request to your AAI:


Among all the logical-links that you have in your AAI, find the logical-link that is created as a result of your UUI creation. This should be the one that has “TsciConnectionLink” as its link-type attribute.

Now the last step is to configure your mock PCE server (PCE.zip), to expect your newly created logical-link “link-name” attribute as a query parameter instead of the mentioned “tranportEp…”. To do so, find the file named config.json included in the following directory of this PCE.zip file: "./moco/Stubs/testcase/gso", and replace the “tranportEp_src_ID_111_1” query parameter with the new logical-link link-name uuid. Then re-run the java file for this mock PCE server to pickup the change.


Note 2: ESR registration of the third-party domain controllers and topology discovery operation

...