How do I configure auto-assigned service ID ranges and uniqueness checking?
Purpose
CAUTION Service Disruption |
Modifying the NFM-P system configuration can have serious consequences that include service disruption.
Contact technical support before you attempt to modify the server configuration.
CAUTION Misconfiguration risk |
You must configure each main server in the NFM-P system using the same values, as described in the procedure; otherwise, a potentially service-affecting configuration mismatch exists.
If you perform the procedure, ensure that you perform the procedure on each main server station.
By default, the NFM-P performs uniqueness checking to verify that a service ID that is to be auto-assigned is not currently associated with a service in the NFM-P managed network. Service creation using auto-assigned service IDs can take considerable time, and consume system resources unnecessarily, if the NFM-P manages a large number of services.
To avoid such a scenario, you can configure a range of service IDs for auto-assignment, and disable the uniqueness checking for the specified range.
Perform this procedure to :
-
configure the system-wide default minimum and maximum values for auto-assigned service IDs
-
disable or enable the uniqueness checking of service IDs during service creation
Note: When uniqueness checking is disabled for a range, a value in the range cannot be used as a service ID for the following. or an error is logged and the service creation fails:
-
service created using a range policy, if the ranges in the range policy and server configuration overlap to any extent
Note: The order in which you configure the main servers is unimportant, but you must perform the procedure on each main server before you attempt automatic service creation using the specified service ID range.