How do I manage the 400 ZR managed alien solution?

This procedure describes how to use NSP to initiate link creation, after which the WS-NOC provides the required parameter values using T-API. This feature allows for automated provisioning of 400 ZR links utilizing T-API to communicate the following 4 coherent parameters between NSP and WS-NOC:

 
1 

Manage the WS-NOC controller using shared mode. See the NSP Installation and Upgrade Guide for more information about enabling WS-NOC compatibility. The NSP automatically discovers optical services when the WS-NOC controller is successfully managed.

2 

Install the T-API adaptor. See How do I add a controller?.

3 

Download the nsp-cdc-intent-types-cam.zip artifact file for the current release from Nokia Electronic Delivery service. Included in the archive is a readme.txt file that contains pre-configuration instructions that must be followed before using and installing the artifact.

4 

Manage two 7750 SR 400G ZR/ZR+ nodes in NSP.

5 

Import and configure the 400 ZR intent by performing the following steps:

  1. Open Artifacts.

  2. Click IMPORT & INSTALL, select the nsp-cdc-intent-types-rel-cam.zip artifact file, and click IMPORT & INSTALL.

  3. Open Device Management, Configuration Intent Types.

  4. Click png1.png IMPORT, select nsp-cdc-zr-endpoint-intent, and click Import.

  5. Wait for the intent to initialize and the Status to display “Successful”.

  6. Open Device Management, Configuration Templates.

  7. Click png1.png TEMPLATE.

  8. Click Basic Info and enter “nsp-cdc-zr-template” as the value for Template Name.

  9. In Configuration Intent Type, click png1.png INTENT TYPE.

  10. Select nsp-cdc-zr-endpoint-intent and click ADD.

  11. Click Release. The Life Cycle should display “released”.

The following parameters are displayed for Coherent Optics:

  • DWDM Frequency

  • Compatibility Mode

  • Tx Target Power

The parameter settings for Coherent Optics are automatically set by the intent.

6 

Create two CDLs between the 7750 SR 400G ZR/ZR+ nodes. See How do I manually create cross-domain links? for more information.

Upon CDL creation, an LLI is discovered for the nodes in the “Planned” state.

7 

Assign the ICM template for the 400 ZR intent.

  1. Open IP/Optical Coordination, Link Layer Interconnect.

  2. Click More png13.png for a discovered 400 ZR LLI and choose Assign ICM Template (this option is only available for LLIs in the “Planned” or “Deployment Failed” states). The Assign ICM Template form opens with the endpoint data automatically filled in along with the default 400 ZR template name nsp-cdr-zr-template.

  3. In the Assign ICM Template form, if required, you can enter the name of a custom 400 ZR ICM template. Otherwise, the default will be used.

  4. Click CONFIRM. The NSP deploys the template to the selected 400 ZR node endpoints.

Upon successful deployment, the LLI lifecycle state changes from “Planned” to “Deployed”.

In the Link Layer Interconnect table view, Central Frequency and Profile ID are displayed for each LLI.

You can select an LLI and click on the IP endpoint to view values for ICM Template Name, Deployment Status, Central Frequency, and Transmit Power. These values are set by NSP based on events received from WS-NOC. Under Connected Optical Domain, the Profile ID is displayed along with a timestamp of the last update.

8 

Verify successful deployments under ICM Deployments for each of the LLI node endpoints. See the NSP User Guide for more information about auditing ICM deployments.

Note: If the deployment fails, the LLI still displays in the “Discovered” state and the ICM deployment must be debugged.

9 

If the LLIs are stuck and are not moving to a “Deployed” state, you can Click More png13.png for a discovered 400 ZR LLI, choose Assign ICM Template, and enable the No Template option. This is intended to push the LLI through the deployment deadlock.

End of steps