NFM-P system upgrade restrictions

Description

CAUTION Service Disruption

An NFM-P upgrade does not preserve all non-default settings in configuration files such as nms-server.xml.

If an NFM-P configuration file contains non-default settings that you want to retain after an upgrade, contact technical support for assistance before the upgrade.

CAUTION Data Loss

At the beginning of a main server upgrade, specific NFM-P configuration and log files are copied to a time-stamped directory in the installation directory, and specific directories below the installation directory are deleted.

If you create or modify a file under the main server installation directory, you risk losing the file during an upgrade unless you first back up the file to a location that is unaffected by the upgrade.

CAUTION Upgrade failure

An NFM-P main server upgrade fails if each main server in the system is not fully initialized and functional before the upgrade.

Before you attempt to upgrade a main server, you must ensure that the initialization of each main server in the NFM-P system is complete.

The following restrictions apply to an NFM-P system upgrade.

• A redundant system upgrade requires a network-management outage and must be performed only during a scheduled maintenance period of sufficient duration.

Note: An NFM-P server upgrade applies a default set of file permissions to each directory below the main or auxiliary server installation directory. If you change the file permissions of a directory below the main server installation directory and want the permissions to be in effect after an upgrade, you must re-apply the permissions after the upgrade.