nnmhadisk.ovpl NNM error (367 Views)
Reply
Frequent Advisor
Abhishek_
Posts: 94
Registered: ‎11-10-2011
Message 1 of 6 (367 Views)

nnmhadisk.ovpl NNM error

Hi,

 

I have installed NNMi in primary node with version 9.23 patch 4

 

OS version: Redhat 6.3

 

Cluster : RHCS

 

 

Shared disk mount point is created

 

Volume group, logical volume has been created and mounted on the shared disk mount point

 

But while copying NNMi database to the shared disk mount point getting the  below error, full permission has been given to all the directories

 

/opt/OV/misc/nnm/ha/nnmhadisk.ovpl NNM -to <HA_mount_point>

 

chac1: cannot set access acl on "/HA_Mount_point/NNM/dataDir/log/nnm/public" : operation not supported.

 

Please advice what is this error and how to rectify it.

Honored Contributor
dieter boschung
Posts: 236
Registered: ‎12-18-2008
Message 2 of 6 (340 Views)

Re: nnmhadisk.ovpl NNM error

Hi Abhishek

 

This is a warning message that the chacl command cannot change the control access list on the directory.

 

This can be safely ignored in this context.It can occur if acls are not supported on the filesystem in use. The "nnmhadisk.ovpl -to /<mount-point>" command copies NNMi runtime files and directories to the shared filesystem. One of the last steps is to make sure the 'public' directory has adequate permissions, the script will ensure it is owned by the group 'nmsgrp' and sets a permission of 4777 . Additionally, it tries to set acls for this object public.

 

I also understand you currently have a case opened with HP support on this subject. If you have further questions, then please refer to your support case.

 

Thanks

Dieter

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Frequent Advisor
Abhishek_
Posts: 94
Registered: ‎11-10-2011
Message 3 of 6 (317 Views)

Re: nnmhadisk.ovpl NNM error

Hi Dieter,

 

Thanks for the information.

 

Need some clarity on below steps.

 

In Deployment reference guide 9.23-- Configuring  NNMi on Primary cluster node

 

Step 9 says unmount the shared disk and deactivate the disk group-- I want to understand why we are doing this unmounting shared disk is fine, why we are deactivating the disk group.

 

Step 13 says by default NNMi starts in locale of the user, what is HA_LOCALE and locale here.

 

 

Honored Contributor
dieter boschung
Posts: 236
Registered: ‎12-18-2008
Message 4 of 6 (313 Views)

Re: nnmhadisk.ovpl NNM error

Hi Abhishek

 

The mounting and umounting of the <HA-Mount> filesystem is under control of the HA manager (RHCS in your case). RHCS will activate the volume group on which the logical volume for the shared filesystem resides automatically on the node where the NNMi resource group is started.

 

Therefore, when you run nnmhaconfigure.ovpl, you only provide the name of the volume group, the name of the logical volume and the mount point. That information is then used to create the <fs> information in the cluster.conf. After the nnmhaconfigure.ovpl script finished, the resources configured for the NNMi resource group will be controlled by the cluster manager. These resources are:

 

- virtual IP address (ip reference)

- volume group name and logical volume name (lvm reference)

- shared filesystem mount point (fs reference)

 

Unmounting the shared filesystem and deactivating the volume group will make sure the RHCS manager can take control over this VG.

 

The HA_LOCALE is also configured into cluster.conf and will be used to start NNMi, this will be "en_US.UTF-8" for most installations, another locale can be used for chinese, korean and japanese systems.

 

Lastly, once the cluster.conf has been setup, your RHCS administrator should not use the 'luci' web interface to manage the NNMi RG. As noted in the NNMi deployment guide, the 'luci' web interface is known to destroy the NNMi RG.

 

Kind regards,

Dieter

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Frequent Advisor
Abhishek_
Posts: 94
Registered: ‎11-10-2011
Message 5 of 6 (299 Views)

Re: nnmhadisk.ovpl NNM error

Hi Dieter,

 

 

Thanks for the detailed information.

 

Now my question is when the resource group, virtual IP, volume group, logical volume and shared file system mount point is created while configuring the RHCS.

 

In that case what exactly the nnmhaconfigure.ovpl does and when we give the same input (virtual IP, volume group, logical volume) in nnmhaconfigure.ovpl it adds these details in cluster.conf file

 

My understanding is that it will provide the inputs to cluster services to start the nnmi services whenever failover happens.

 

I am bit confused, please advise.

Honored Contributor
dieter boschung
Posts: 236
Registered: ‎12-18-2008
Message 6 of 6 (291 Views)

Re: nnmhadisk.ovpl NNM error

Hi Abhishek

 

First of all, the HA cluster must have been setup by your RHCS admin, that includes the basic setup to include 2 or more cluster members, fencing devices etc.

 

Once the basic HA cluster setup has been done, the RHCS admin must start at least these services (refer to your RHCS admin for more information).

- cluster

- ricci

- rgmanager

- modclusterd

 

The nnmhaconfigure.ovpl script takes your input and will add the resources to create the NNMi resource group, it then adds that information to the exising cluster.conf file and then runs the command "cman_tool version -r"

 

This command will connect to the running cluster services and cause it to distribute the change to the other cluster member(s). Again, see your RHCS admin for more details on the cman_tool command.

 

Regards

Dieter

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.