To configure the maximum number of policy objects per deployer
Purpose
Perform this procedure to set the maximum number of managed objects that can be distributed by one deployer. This in turn will determine how many deployers are used to distribute a global policy to a given set of NEs.
|
CAUTION Service Disruption |
Contact your Nokia technical support representative before you attempt to modify the nms-server.xml file.
Modifying the nms-server.xml file can have serious consequences that can include service disruption.
Steps
1 |
Log in to the NFM-P main server station as an admin user. |
2 |
Navigate to the /opt/nsp/nfmp/server/nms/config directory. |
3 |
Create a backup copy of the nms-server.xml file. |
4 |
Open the nms-server.xml file using a plain-text editor. |
5 |
Search for the following XML tag: <policyConfig policyDistributionMaxObjectsPerDeployer="10000"/> |
6 |
Change the number as required. An integer value of “0” or less specifies that only one deployer will be used to distribute a policy to all the NE sites. A value of “1” specifies that one deployer will be used per site. The default value is 10,000 managed objects per deployer. Nokia recommends that you configure the value between 2,000 and 100,000. Refer to the section Scaling policy deployments for more information on setting the maximum number of managed objects per deployer. |
7 |
Save and close the nms-server.xml file. |
8 |
Open a console window. |
9 |
Navigate to the /opt/nsp/nfmp/server/nms/bin directory. |
10 |
If the main server is a standalone server, or the primary server in a redundant deployment, enter the following: bash$ ./nmsserver.bash read_config ↵ The main server reads the nms-server.xml file and puts the configuration change into effect. |
11 |
If the main server is the standby server in a redundant deployment, enter the following: bash$ ./nmsserver.bash force_restart ↵ The main server restarts and puts the configuration change into effect. |
12 |
Close the console window. End of steps |