21.12 Configuring NNMi to allow level 2 operators to delete nodes and incidents
By default, NNMi permits NNMi administrators to create, edit, or delete nodes or incidents in NNMi. You can configure accounts assigned to the NNMi Operator Level 2 (L2) User Group to have the ability to delete nodes or incidents. You can achieve this by using one of the following methods:
-
(Recommended) Elevate the privileges of the required L2 users to delete the required nodes or incidents. This can be done using the NNMi web console. For more information, see the NNMi Admin help.
-
Configure NNMi to globally enable L2 users to delete nodes or incidents. This can be done by overriding the default privileges by modifying certain NNMi property files.
- Important
-
Use the override method only for global enablement. Once enabled, you cannot control L2 user access privileges in the NNMi web console.
To enable L2 users to edit or delete nodes, their associated incidents, or both, follow these steps:
-
Edit the following file:
-
Windows: %NNM_PROPS%\nms-topology.properties
-
Linux: $NNM_PROPS/nms-topology.properties
-
-
Append the following lines as required:
-
To enable L2 users to delete nodes, append the following line:
permission.override.com.hp.nnm.DELETE_OBJECT=com.hp.nnm.ADMIN,com.hp.nnm.LEVEL2
-
To enable L2 users to delete incidents, append the following line:
permission.override.com.hp.nnm.incident.DELETE=com.hp.nnm.ADMIN,com.hp.nnm.LEVEL2
-
-
Save the file.
-
Restart NNMi.
ovstop ovstart
When making file changes under HA, you must make the changes on both nodes in the cluster. For an NNMi that uses an HA configuration, if the change requires you to stop and restart the NNMi management server, you must place the nodes in maintenance mode before running the ovstop and ovstart commands.