12.2.9 Task 9: Clean up to prevent unexpected access to NNMi

1. (Optional) Either change the value of or comment out the defaultRole parameter in the LDAP configuration file.

   If you change the value of, or comment out, the defaultRole element or parameter in the LDAP configuration file, force NNMi to re-read the LDAP configuration file by running the following command:

   nnmldap.ovpl -reload

2. (Configuring for the mixed mode only) To store user group membership in the NNMi database, reset the user access information in the NNMi database as follows:

   1. Remove any pre-existing user access information. (Delete all rows in the User Accounts view.)

      For details, see Delete a User Account in NNMi Help.

   2. For each NNMi user, create a new object in the User Accounts view for the user name.

      - For the Name field, enter the user name as defined in the directory service.

      - Select the Directory Service Account check box.

      - Do not specify a password.

      For details, see User Account Tasks in NNMi Help.

   3. For each NNMi user, map the user account to one or more NNMi user groups.

      For details, see Map User Accounts to User Groups (User Account Mapping Form) in NNMi Help.

   4. Update incident ownership so that each assigned incident is associated with a valid user name.

      For details, see Manage Incident Assignments in NNMi Help.

3. (Configuring for the external mode only) To rely on the directory service for user group membership, reset the user access information in the NNMi database as follows:

   1. Remove any pre-existing user access information. (Delete all rows in the User Accounts view.)

      For details, see Delete a User Account in NNMi Help.

   2. Update incident ownership so that each assigned incident is associated with a valid user name.

      For details, see Manage Incident Assignments in NNMi Help.

To Page Top