To configure CoordPoint agent to monitor coordination points

1. Ensure that your VCS cluster has been properly installed and configured with fencing enabled.
2. Create a parallel service group vxfen and add a coordpoint resource to the vxfen service group using the following commands:

   # haconf -makerw
   # hagrp -add vxfen
   # hagrp -modify vxfen SystemList galaxy 0 nebula 1
   # hagrp -modify vxfen AutoFailOver 0
   # hagrp -modify vxfen Parallel 1
   # hagrp -modify vxfen SourceFile "./main.cf"
   # hares -add coordpoint CoordPoint vxfen
   # hares -modify coordpoint FaultTolerance 1
   # hares -modify coordpoint Enabled 1
   # haconf -dump -makero

3. Verify the status of the agent on the VCS cluster using the hares commands. For example:

   # hares -state coordpoint

   The following is an example of the command and output::

   # hares -state coordpoint

   # Resource    Attribute   System   Value
   coordpoint   State        galaxy   ONLINE
   coordpoint 		State								nebula   ONLINE

4. Access the engine log to view the agent log. The agent log is written to the engine log.

   The agent log contains detailed CoordPoint agent monitoring information; including information about whether the CoordPoint agent is able to access all the coordination points, information to check on which coordination points the CoordPoint agent is reporting missing keys, etc.

   To view all such information in the engine log, change the dbg level for that node using the following commands:

   # haconf -makerw

   # hatype -modify Coordpoint LogDbg 10

   # haconf -dump -makero

   The agent log can now be viewed at the following location:

   /var/VRTSvcs/log/engine_A.log