To upgrade a Release 22.9 or later NFM-P single-user GUI client

Purpose

The following steps describe how to upgrade the Release 22.9 or later NFM-P software on a single-user GUI client station in a standalone or redundant NFM-P deployment.

Note: The main server to which the client connects must be upgraded and running when you perform the procedure.

Note: If you are not the original installer of the client software, you require the following user privileges on the client station:

Note: A leading bash$ in a CLI command line represents the RHEL prompt, and is not to be included in the command.

Steps
 
1 

Log in to the client station.

2 

Close the client GUI, if it is open.

3 

Use a browser to open the NSP sign-in page.

4 

Enter the required login credentials and click SIGN IN. The NSP UI is displayed.

5 

If one of the following is true, perform the following steps.

  • The client is configured to connect to only one NFM-P system.

  • The client is configured to connect to multiple NFM-P systems, and you do not want to keep the current client version.

Note: If the client is configured to connect to multiple NFM-P systems, and after the upgrade you select a non-upgraded system in the Server drop-down list of the client, you are prompted to downgrade the client. A client downgrade erases the multiple-system client configuration. If you want to preserve the Server drop-down options, do not downgrade the client.

  1. Double-click on the NSP NFM-P Client desktop icon.

  2. Go to Step 8.

6 

Perform the following steps if the following conditions are true:

  • The client is configured to connect to multiple NFM-P systems.

  • You want to keep the current client version for connection to a system that is not yet upgraded.

  • The system is the first of the multiple NFM-P systems to be upgraded.

If the conditions are true, you must remove the upgraded system from the configuration on the client station, and must not use the desktop icon to open the client.

  1. On a Windows station:

    1. Open the Registry Editor.

    2. Navigate to the following key:

      Computer\HKEY_CURRENT_USER\SOFTWARE\JavaSoft\Prefs

    3. Select and delete the IP address or hostname of each upgraded NFM-P main server.

    4. Close the Registry Editor.

    5. Edit the following file to remove the <j2ee and <systemMode lines for the upgraded NFM-P system.

      install_dir\nms\config\nms-client.xml

      where install_dir is the client installation directory

    6. Edit the following file to replace all occurrences of the upgraded system, if present, with the IP address or hostname of a system that is not yet upgraded:

      Note: It is recommended to use the address or hostname of the system that is to be upgraded last.

      Note: For a redundant system, you must replace both main server addresses or hostnames.

      install_dir\nms\bin\locallaunch.jnlp

    7. Right-click the desktop icon, select Properties, and change the name on the General tab to the IP address or hostname of a different NFM-P system.

      Note: It is recommended to use the address or hostname of the system that is to be upgraded last.

    8. From the Java Control Panel, clear the Java cache of any entries for the recently upgraded system.

    9. Right-click the client desktop icon, select Properties, and change the name on the General tab to the IP address or hostname of a different NFM-P system.

    10. Install a new client instance.

    Note: You must specify a new client installation location, and not the current location.

  2. On a RHEL station:

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

      ~/.java/.userPrefs/prefs.xml

    2. Select and delete the IP address or hostname of each upgradedNFM-P main server.

    3. Save and close the file.

    4. Edit the following file to remove the <j2ee and <systemMode lines for the upgraded NFM-P system.

      install_dir/nms/config/nms-client.xml

      where install_dir is the client installation directory

    5. Edit the following file to replace all occurrences of the upgraded system, if present, with the IP address or hostname of a system that is not yet upgraded:

      Note: It is recommended to use the address or hostname of the system that is to be upgraded last.

      Note: For a redundant system, you must replace both main server addresses or hostnames.

      install_dir/nms/bin/locallaunch.jnlp

    6. Edit the desktop icon file to replace each occurrence of the upgraded system with the IP address or hostname of a system that is not yet upgraded.

      Note: It is recommended to use the address or hostname of the system that is to be upgraded last.

    7. From the Java Control Panel, clear the Java cache of any entries for the recently upgraded system.

    8. Install a new client instance.

    Note: You must specify a new client installation location, and not the current location.

7 

If the client is configured to connect to multiple NFM-P systems, and the upgraded system is not the first to be upgraded, perform the following steps.

  1. For a Windows client:

    1. Edit the following file to add <j2ee and <systemMode lines for each main server in the upgraded NFM-P system:

      new_install_dir\nms\config\nms-client.xml

      where new_install_dir is the installation directory of the new client installed in Step 6

    2. Use the new client desktop icon to open the GUI for the upgraded system.

  2. For a RHEL client:

    1. Edit the following file to add <j2ee and <systemMode lines for each main server in the upgraded NFM-P system:

      new_install_dir/nms/config/nms-client.xml

      where new_install_dir is the installation directory of the new client installed in Step 6

    2. Use the new client desktop icon to open the GUI for the upgraded system.

8 

A form like the following is displayed.

Figure 16-2: Do you want to run this application?
Do you want to run this application?

Click Run.

The panel shown in Figure 16-3, Updating... is displayed.

Figure 16-3: Updating...
Updating...
9 

Click Update client.

The client upgrade begins, and the panel shown in Figure 16-4, Updating... is displayed. The panel uses separate bars to indicate the overall and current task progress.

Figure 16-4: Updating...
Updating...
10 

If the client is installed on Mac OS X, perform the following steps.

  1. Open a console window.

  2. Navigate to the following directory:

    /Applications/NFMPclient.IP_address.app/Contents/Resources/nms/bin

  3. Enter the following:

    chmod +x nmsclient.bash ↵

11 

If you are not currently logged in, the splash screen shown in Figure 16-5, Waiting for user authentication opens, and the NSP sign-in page is displayed.

Enter the required login credentials on the NSP sign-in page and click SIGN IN. The NSP UI is displayed, and the client GUI opens.

Figure 16-5: Waiting for user authentication
Waiting for user authentication
12 

Verify that the GUI is operational and correctly displayed.

End of steps