How do I add a controller?
Perform this procedure to define an optical controller to NSP.
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
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.
| |
|
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
1 |
|
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
2 |
|
Cross Launch Service URL |
Specifies the cross launch service URL for physical links
2 |
|
SRLG Minimum Value |
Specifies the minimum numeric SRLG value for the controller |
|
SRLG Maximum Value |
Specifies the maximum numeric SRLG value for the controller |
Notes:
When NSP and WaveSuite are integrated in a non-shared mode configuration (standalone), Push Data To NSP Store must be set to ‘Yes’ to populate optical information in NSP’s Assurance dashboards. When NSP and WaveSuite are integrated in a shared-mode configuration, Push Data To NSP Store must be set to ‘No’ to prevent duplicate upload of optical inventory. In an HA/DR deployment, this parameter must be reconfigured after a WS-NOC switchover.
|
4 |
Click Create. The controller is added and the IP/Optical Coordination features become available.
If you need to modify or delete the controller after it has been added, select the controller and then click on Edit or Delete in the More menu.
End of steps |