To enable WS-NOC compatibility with an NSP system

Purpose

Perform this procedure to ensure compatibility with a Release 21.12, 22.6, 22.12, 23.6, or 23.12 WS-NOC system in your NSP deployment. NSP release compatibility varies by system type; see the NSP compatibility matrix in the NSP Release Notice for the release combinations that are supported in shared-mode deployments, including any release-specific patches that the WS-NOC may require.

Note: The WS-NOC supports only IPv4, so can be integrated only with an NSP system that uses IPv4 in the client and internal networks.

Note: If integrating with WS-NOC version 21.12 or later, the secure parameter in the nspos block of the configuration file must be set to “true” in order for the NSP and WS-NOC to interoperate, and all other components in the deployment must also be installed in secure mode.

Steps
 
1 

If the secure parameter in the nspos section of the NSP configuration file is set to true, perform the following steps in each data center to enable deprecated TLS version support:

Note: If the NSP cluster VMs do not have the required SSH key, you must include the --ask-pass argument in the nspdeployerctl command, as shown in the following example, and are subsequently prompted for the root password of each cluster member:

nspdeployerctl --ask-pass install --config --deploy

  1. Log in as the root user on the NSP deployer host.

  2. Open the following file using a plain-text editor such as vi:

    /opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/config/nsp-config.yml

  3. Locate the nspos section, which resembles the following:

        nspos:

          secure: true

  4. Edit the section to read as follows:

        nspos:

          secure: true

  5. Save and close the nsp-config.yml file.

  6. Enter the following to put the changes into effect:

    # /opt/nsp/NSP-CN-DEP-release-ID/bin/nspdeployerctl install --config --deploy ↵

2 

Note: In a redundant WS-NOC system, you must perform the steps on each WS-NOC server.

Login to the mnc-fm container on the WS-NOC VM and execute the following command:

docker exec -it mnc-fm bash
3 

Open the /nfmt/instance/nfmt-adapters/config/NfmtAdapter.properties file.

4 

Perform one of the following:

  1. If integrating with a 21.12 WS-NOC system, modify the following attributes to read as follows: 

    EQUIPMENT_ENABLED=true
    SERVICE_ENABLED=true

  2. If integrating with a 22.6 WS-NOC system, modify the following attributes to read as follows:

    EQUIPMENT_ENABLED=true

    SERVICE_ENABLED=true

    FMADAPTER_VERSION=21.6.0-rel

    EQUIPMENTADAPTER_VERSION=22.6.0-rel

    SERVICEADAPTER_VERSION=22.6.0-rel

  3. If integrating with a 22.12 WS-NOC system, modify the following attributes to read as follows:

    EQUIPMENT_ENABLED=true

    SERVICE_ENABLED=true

    FMADAPTER_VERSION=21.6.0-rel

    EQUIPMENTADAPTER_VERSION=22.6.0-rel

    SERVICEADAPTER_VERSION=22.11.0-rel

  4. If integrating with a 23.6 or 23.12 WS-NOC system, modify the following attributes to read as follows:

    EQUIPMENT_ENABLED=true

    SERVICE_ENABLED=true

    FMADAPTER_VERSION=21.6.0-rel

    EQUIPMENTADAPTER_VERSION=23.4.0-rel

    SERVICEADAPTER_VERSION=23.4.0-rel

5 

Copy the file into the following directory. Execute:

mkdir -p /nfmt/config/tempcustom/nfmt/instance/nfmt-adapters/config

cp /nfmt/instance/nfmt-adapters/config/NfmtAdapter.properties /nfmt/config/tempcustom/nfmt/instance/nfmt-adapters/config/

6 

Restart Nfmt-Adapters. Perform one of the following:

  1. If you are integrating a Release 21.12 or 22.6 WS-NOC system, perform the following:

    1. Stop Nfmt-Adapters. Execute:

      pkill -f Nfmt-Adapters

    2. Start Nfmt-Adapters. Execute:

      /umc/plat/script/mngApp startup Nfmt-Adapters

  2. If you are integrating a Release 22.12 or later WS-NOC system, restart NSP-Adapters. Execute:

    pkill -f NSP-Adapters

    Note: The NSP-Adapters process will start automatically.

7 

If the NSP was installed using FQDN, the FQDN of the NSP should be updated in the /<installroot>/config/bench/fqdn.cfg file before integrating with WS-NOC. The format is as follows:

nsp-a;<nsp-a alias>;<nsp-a IPv4 address>

nsp-b;<nsp-b alias>;<nsp-b IPv4 address>

where

nsp-a alias is the alias of the primary NSP cluster

nsp-a IPv4 address is the IPv4 address of the primary NSP cluster

nsp-b alias is the alias of the standby NSP cluster

nsp-b IPv4 address is the IPv4 address of the standby NSP cluster

End of steps