What is global NFM-P system configuration?

Introduction

The NFM-P may require a configuration change to meet specific operational requirements. You can use the procedures in this section to configure global NFM-P settings, functions, and preferences.

Graceful NFM-P system shutdown and startup

CAUTION Service Outage

Stopping the NFM-P software on a station, or rebooting a station that hosts NFM-P software, may have serious consequences that can include a complete network management outage.

You must perform such service-affecting actions only as directed by the NSP documentation or technical support, and only during a scheduled maintenance period.

Low-level maintenance that is not described in this section, for example, applying a RHEL OS patch to the NFM-P component stations, may require that you stop and start each station.

Stopping a standalone NFM-P system creates a network management outage that must be considered in the planning for a maintenance activity that requires such action.

In a redundant NFM-P system, you can avoid such an outage by performing the orderly shutdown and startup of the components described in Workflow: redundant NFM-P shutdown and restart.

Global GUI-client updates

The NFM-P auto-client update function allows you to reconfigure multiple GUI clients using one central configuration. See the NSP Installation and Upgrade Guide for client update configuration information, and How do I modify the base configuration of all GUI clients? for information about using the auto-update function to push an update to all GUI clients.