How do I add a controller?

See Chapter 3, IP/Optical Coordination compatibility table for information on T-API/WS-RC/WS-NOC controllers’ version supported in IP/Optical Coordination.

IP/Optical Coordination supports the addition, modification and deletion of optical controllers. Nokia's Model-Driven Mediation (MDM) platform is required in order to enable this functionality, as are adaptors that correspond to the supported controller types. See the NSP Installation and Upgrade Guide for more information about installing WS-RC and T-API adaptors.

The addition, modification, and deletion of optical controllers is supported both when WS-NOC is integrated with the NSP and when WS-NOC is deployed as an independent system. If integrated, the WS-NOC server must be restarted whenever the associated NSP cluster is restarted. As an independent system, the WS-RC security certificate must be installed on the MDM server. After WSRC certificates are copied to the MDM server, retrieve the password using the following command:

kubectl get secret -n nsp-psa-privileged nsp-tls-truststore-pass-nspdeployer -ojsonpath="{.data..truststore-pass}" | base64 -d

Login to the MDM server and import the certificate using the following command:

/opt/nsp/os/jre/bin/keytool -alias nfmt -file /<path_where_WSRC_cert_is_imported>/certificate.pem -import -keystore /opt/nsp/os/ssl/nsp.truststore -storepass <password_from_kubectl_get_secret>

1	Open IP/Optical Coordination, Controller and Simulator.
2	Click Add and choose Add Controller. The Create Controller page opens.
3	Configure the required parameters: Parameter Description Identification Name Specifies the name of the controller Description Describes the controller Vendor Specifies the controller's vendor Domain Specifies the domain(s) managed by the controller IP Address Specifies the IP address of the controller Port Specifies the port used in REST communications Re-sync Frequency (minute) Specifies the time, in minutes, to re-sync Secured Connection Specifies whether the Cross domain resource control to MDM connection will be secured Push Data To NSP Store Specifies whether data will be pushed to the NSP store Controller Parameters Controller Type Specifies the type of controller Controller Version Specifies the controller version Protocol Type Specifies the protocol type used for communication Protocol Version Specifies the version of the protocol to be used for communication Mediation Parameters User Name Specifies the user name Password Specifies the password Port Specifies the port used in REST communications Base URL Specifies the endpoint used in REST communications Idle Timeout (seconds) Specifies, in seconds, the rest idle timeout Retries Specifies the number of retries Authentication Server IP Address Specifies the IP address of the server that authenticates all requests Secured Connection Specifies whether the MDM to WS-NOC connection is secured Additional Parameters Cross Launch URL Specifies the cross launch URL for physical links Cross Launch Service URL Specifies the cross launch service URL for physical links SRLG Minimum Value Specifies the minimum numeric SRLG value for the controller SRLG Maximum Value Specifies the maximum numeric SRLG value for the controller
4	Click CREATE. The controller is added.
5	As required, modify the controller by hovering over More and clicking Edit .
6	As required, delete the controller by hovering over More and clicking Delete . End of steps

Note: When a controller is added, an NE policy and a mediation policy are created. If the IP/Optical Coordination database is dropped, the controller will be deleted, but these policies will remain on the NSP host and MDM servers. The policies must be deleted before the controller can be re-added.