To enable NSP compatibility with an earlier NFM-P system

Purpose

In an NSP deployment that includes an NFM-P system at an earlier release, you may need to perform specific actions to enable NSP and NFM-P compatibility.

Note: If the NSP uses OAUTH2 authentication, you must apply an NFM-P Service Pack to the older NFM-P system to enable integration of the systems. Ensure that you follow the required Service Pack instructions before you perform this procedure.

Note: NSP release compatibility varies by system type; see the NSP compatibility matrix in the NSP Release Notice for the supported release combinations.

Perform this procedure to enable mixed-release NSP and NFM-P compatibility if your NSP deployment includes an NFM-P system at one of the following releases:

  • 22.11

  • 23.4

  • 23.8

  • 23.11

Note: release-ID in a file path has the following format:

R.r.p-rel.version

where

R.r.p is the NSP release, in the form MAJOR.minor.patch

version is a numeric value

Steps
CAUTION 

CAUTION

Service disruption

Modifying the system configuration may have serious consequences that include service disruption. It is strongly recommended that you perform the procedure only with the assistance of technical support.

Contact your technical support representative before you attempt to perform the procedure.

 
1 

Perform the following steps on each main server station to transfer the patch files for the NFM-P release from the NSP.

Note: In a redundant NFM-P system, it is recommended to perform the steps on the primary main server station first.

  1. Log in as the root user on the station.

  2. Open a console window.

  3. If remote root access is disabled, switch to the designated root-equivalent user.

  4. Enter the following:

    # mkdir -p /opt/nsp/patches ↵

  5. Enter the following:

    # scp -rp address:/opt/nsp/NSP-CN-DEP-release-ID/NSP-CN-release-ID/src/ansible/roles/

    config/files/compatibility/nfmp/NFMP_R_r/* /opt/nsp/patches/ ↵

    where

    address is the address of the NSP deployer host

    R_r is the release of the NFM-P system

  6. If remote root access is disabled, switch back to the root user.

2 

Perform the following steps on each main server station to stop the server.

Note: In a redundant NFM-P system, you must perform the steps on the standby main server station first.

  1. Enter the following to switch to the nsp user:

    # su - nsp ↵

  2. Enter the following:

    bash$ cd /opt/nsp/nfmp/server/nms/bin ↵

  3. Enter the following to stop the main server:

    bash$ ./nmsserver.bash stop ↵

  4. Enter the following:

    bash$ ./nmsserver.bash appserver_status ↵

    The server status is displayed; the server is fully stopped if the status is the following:

    Application Server is stopped

    If the server is not fully stopped, wait five minutes and then repeat this step. Do not perform the next step until the server is fully stopped.

  5. Enter the following to switch back to the root user:

    bash$ su - ↵

3 

If the NFM-P is at Release 22.11, go to Step 6.

4 

If the NFM-P is at Release 23.4 or 23.8, go to Step 7.

5 

If the NFM-P is at Release 23.11, go to Step 8.

6 

Apply the compatibility patch to a Release 22.11 NFM-P system.

Note: In a redundant NFM-P system, you must perform the steps on each main server station.

Perform each action in Table 11-1, Compatibility actions, NFM-P Release 22.11 by executing the commands associated with the action.

To facilitate the command execution, you can copy a command block and paste the block into the console window.

Table 11-1: Compatibility actions, NFM-P Release 22.11

Action and commands

1. Create backup directories

mkdir -p /opt/nsp/patches/backup/alu_orbw

mkdir -p /opt/nsp/patches/backup/nms

mkdir -p /opt/nsp/patches/backup/nspos

2. Back up Orbweaver files

cd /opt/nsp/nms/lib/alu_orbw

cp equipment-model-avro.jar /opt/nsp/patches/backup/alu_orbw/

cp service-model-avro.jar /opt/nsp/patches/backup/alu_orbw/

3. Back up nspos adapter files

cd /opt/nsp/nms/lib/nspos

cp nms_nspos_equipment_model_adapter.jar /opt/nsp/patches/backup/nspos/

cp nms_nspos_model_adapter.jar /opt/nsp/patches/backup/nspos/

cp nms_nspos_service_model_adapter.jar /opt/nsp/patches/backup/nspos/

4. Back up trackedClasses.properties file

cd /opt/nsp/nms/config

cp trackedClasses.properties /opt/nsp/patches/backup/nms

5. Apply compatibility-patch files

cd /opt/nsp/patches

chown nsp:nsp *

cp -p equipment-model-avro.jar /opt/nsp/nms/lib/alu_orbw/

cp -p service-model-avro.jar /opt/nsp/nms/lib/alu_orbw/

cp -p nms_nspos_equipment_model_adapter.jar /opt/nsp/nms/lib/nspos/

cp -p nms_nspos_model_adapter.jar /opt/nsp/nms/lib/nspos/

cp -p nms_nspos_service_model_adapter.jar /opt/nsp/nms/lib/nspos/

cp -p trackedClasses.properties /opt/nsp/nms/config

7 

Apply the compatibility patch to a Release 23.4 or 23.8 NFM-P system.

Note: In a redundant NFM-P system, you must perform the steps on each main server station.

Perform each action in Table 11-2, Compatibility actions, NFM-P Releases 23.4 and 23.8 by executing the commands associated with the action.

To facilitate the command execution, you can copy a command block and paste the block into the console window.

Table 11-2: Compatibility actions, NFM-P Releases 23.4 and 23.8

Action and commands

1. Create backup directories

mkdir -p /opt/nsp/patches/backup/alu_orbw

mkdir -p /opt/nsp/patches/backup/nms

mkdir -p /opt/nsp/patches/backup/nspos

2. Back up Orbweaver files

cd /opt/nsp/nms/lib/alu_orbw

cp equipment-model-avro.jar /opt/nsp/patches/backup/alu_orbw/

cp service-model-avro.jar /opt/nsp/patches/backup/alu_orbw/

3. Back up nspos adapter files

cd /opt/nsp/nms/lib/nspos

cp nms_nspos_equipment_model_adapter.jar /opt/nsp/patches/backup/nspos/

cp nms_nspos_service_model_adapter.jar /opt/nsp/patches/backup/nspos/

4. Back up trackedClasses.properties file

cd /opt/nsp/nms/config

cp trackedClasses.properties /opt/nsp/patches/backup/nms

5. Apply compatibility-patch files

cd /opt/nsp/patches

chown nsp:nsp *

cp -p equipment-model-avro.jar /opt/nsp/nms/lib/alu_orbw/

cp -p service-model-avro.jar /opt/nsp/nms/lib/alu_orbw/

cp -p nms_nspos_equipment_model_adapter.jar /opt/nsp/nms/lib/nspos/

cp -p nms_nspos_service_model_adapter.jar /opt/nsp/nms/lib/nspos/

cp -p trackedClasses.properties /opt/nsp/nms/config

8 

Apply the compatibility patch to a Release 23.11 NFM-P system.

Note: In a redundant NFM-P system, you must perform the steps on each main server station.

Perform each action in Table 11-3, Compatibility actions, NFM-P Release 23.11 by executing the commands associated with the action.

To facilitate the command execution, you can copy a command block and paste the block into the console window.

Table 11-3: Compatibility actions, NFM-P Release 23.11

Action and commands

1. Create backup directories

mkdir -p /opt/nsp/patches/backup/alu_orbw

mkdir -p /opt/nsp/patches/backup/nspos

2. Back up Orbweaver files

cd /opt/nsp/nms/lib/alu_orbw

cp equipment-model-avro.jar /opt/nsp/patches/backup/alu_orbw/

cp service-model-avro.jar /opt/nsp/patches/backup/alu_orbw/

3. Back up nspos adapter files

cd /opt/nsp/nms/lib/nspos

cp nms_nspos_equipment_model_adapter.jar /opt/nsp/patches/backup/nspos/

cp nms_nspos_service_model_adapter.jar /opt/nsp/patches/backup/nspos/

5. Apply compatibility-patch files

cd /opt/nsp/patches

chown nsp:nsp *

cp -p equipment-model-avro.jar /opt/nsp/nms/lib/alu_orbw/

cp -p service-model-avro.jar /opt/nsp/nms/lib/alu_orbw/

cp -p nms_nspos_equipment_model_adapter.jar /opt/nsp/nms/lib/nspos/

cp -p nms_nspos_service_model_adapter.jar /opt/nsp/nms/lib/nspos/

9 

Start each NFM-P main server.

Note: In a redundant NFM-P system, you must perform this step on the primary main server station first.

  1. Enter the following to switch to the nsp user:

    bash$ su - nsp ↵

  2. Enter the following:

    bash$ cd /opt/nsp/nfmp/server/nms/bin ↵

  3. Enter the following to start the main server:

    bash$ ./nmsserver.bash start ↵

  4. Enter the following:

    bash$ ./nmsserver.bash appserver_status ↵

    The server status is displayed; the server is fully initialized if the status is the following:

    Application Server process is running.  See nms_status for more detail.

    If the server is not fully initialized, wait five minutes and then repeat this step. Do not perform the next step until the server is fully initialized.

  5. Close the console window.

End of steps