01-31-2013 01:33 AM
Solved! Go to Solution.
01-31-2013 04:49 AM
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 attributeAutoStartList is a service group attribute that needs to be populated with asystem list. The VCS engine brings up the specified service group on the nodesin the list.AutoStartList is not a required attribute for the service group that contains theCoordPoint resource. The CoordPoint resource is a persistent resource and whena service group is configured with this type of resource, it cannot be broughtonline.Specifying the AutoStartList with a system list does not change the behavior ofthe 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
01-31-2013 02:44 AM
Have you tried to online the vxfen group (hagrp -online vxfen -any) and it fails, or are you just saying it is not starting automatically. Could you most extract from /etc/VRTSvcs/conf/config/main.cf to showing vxfen group - it be just that AutoStart or AutoStartList is not set correctly.
Mike
01-31-2013 04:14 AM
Yeah, I tried almost everything. The config is:
01-31-2013 04:24 AM
i think CoordPoint type is of type None. Try 'hatype -dispaly CoordPoint | grep Operations'.
01-31-2013 04:47 AM
It is of type None:
01-31-2013 04:49 AM
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 attributeAutoStartList is a service group attribute that needs to be populated with asystem list. The VCS engine brings up the specified service group on the nodesin the list.AutoStartList is not a required attribute for the service group that contains theCoordPoint resource. The CoordPoint resource is a persistent resource and whena service group is configured with this type of resource, it cannot be broughtonline.Specifying the AutoStartList with a system list does not change the behavior ofthe 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
01-31-2013 04:54 AM
Really, a service group is not ONLINE or OFFLINE if there are no non-persistent resources in the group, so I guess it could show ONLINE as well as OFFLINE, but it does normally show as OFFLINE. So you could either ignore the OFFLINE state (and only worry if resource is in a faulted state) or add a phantom resource (which you may want to check with Symantec first as vxfen group may be classed as a special group which you shouldn't change).
Mike
01-31-2013 05:49 AM
It makes sense because the resource Phantom is defined in the clusters which have vxfen ONLINE :)
I did not notice about this agent in the config. It is probable to configure more clusters this weekend, so I will post the results.
Thanks Amit and Mike, today I learned a new feature of VCS :)
02-01-2013 12:11 AM
Tested and worked!!! Defining the resource phantom resolved the "problem".