Forum Discussion

joagmv's avatar
joagmv
Level 4
12 years ago

Group vxfen keeps offline in VCS 5.1

  Hi all!   We have started to setting io fencing up in our VCS in customized mode (using 3 CP servers). In VCS 6.0 everything works just fine but in VCS 5.1 (SP1RP2) the group vxfen keeps offl...
  • mikebounds's avatar
    12 years ago

    Amit is right in that CoordPoint type is of type None (persistent resource).  Normally for a persistent resource you put a phantom resource in the group so that you have a resource than can be online or offline so the group can be online and without this the group cannot be online.  However I have looked at the examples in 5.1 and 6.0 bundled agents guide and neither example has a phantom resource in the group.

    So is you added a phantom resource to the group, then you would be able to online the group (and if you added AutoStartList group attribute, then it will auto online on boot), but I am perplexed as to why the examples do not include a phantom resource, especially as the manual does reflect they are aware of the issue - see extract from CoordPoint agent in bundled agents guide

     

    AutoStartList attribute
    AutoStartList is a service group attribute that needs to be populated with a
    system list. The VCS engine brings up the specified service group on the nodes
    in the list.
    AutoStartList is not a required attribute for the service group that contains the
    CoordPoint resource. The CoordPoint resource is a persistent resource and when
    a service group is configured with this type of resource, it cannot be brought
    online.
    Specifying the AutoStartList with a system list does not change the behavior of
    the service group. The service group will be reflected in OFFLINE status itself,
    irrespective of the AutoStartList attribute.
     

     

    So this is saying the group is expected to be OFFLINE, so I don't know why it shows as online in your 6.0 cluster, which I think is what you are saying.

    Mike