Unable to probe RVGPrimary resource

Article:TECH177268  |  Created: 2011-12-19  |  Updated: 2012-01-03  |  Article URL http://www.symantec.com/docs/TECH177268
Article Type
Technical Solution

Product(s)

Issue



After a reboot of a node or restart of HAD, RVGPrimary resource is not probed.

Following errors were found in the engine_A.log:

2011/12/09 14:46:30 VCS ERROR V-16-20012-402 (bosmorsp4) RVGPrimary:bmorsprvg-pri:open:RVG attribute not assigned for resource bmorsprvg.
2011/12/09 14:46:31 VCS ERROR V-16-20012-402 (bosmorsp4) RVGPrimary:bmorsprvg-pri:monitor:RVG attribute not assigned for resource bmorsprvg.

Same errors were found in the engine_A.log when attempted to probe the RVGPrimary resource manually :

# hares -probe bmorsprvg-pri -sys bosmorsp4

2011/12/09 14:48:09 VCS INFO V-16-1-50135 User hdez_c fired command: MSG_RES_PROBE bmorsprvg-pri  bosmorsp4  from <IPAddr>
2011/12/09 14:48:09 VCS ERROR V-16-20012-402 (bosmorsp4) RVGPrimary:bmorsprvg-pri:monitor:RVG attribute not assigned for resource bmorsprvg.

The state was shown as 'not probed' in 'hastatus -sum' output:

-- RESOURCES NOT PROBED
-- Group           Type                 Resource             System
E  mors            RVGPrimary           bmorsprvg-pri        bosmorsp4

 

 

 


Error



2011/12/09 14:46:30 VCS ERROR V-16-20012-402 (bosmorsp4) RVGPrimary:bmorsprvg-pri:open:RVG attribute not assigned for resource bmorsprvg.
2011/12/09 14:46:31 VCS ERROR V-16-20012-402 (bosmorsp4) RVGPrimary:bmorsprvg-pri:monitor:RVG attribute not assigned for resource bmorsprvg.
2011/12/09 14:48:09 VCS INFO V-16-1-50135 User hdez_c fired command: MSG_RES_PROBE bmorsprvg-pri  bosmorsp4  from <IPAddr>
2011/12/09 14:48:09 VCS ERROR V-16-20012-402 (bosmorsp4) RVGPrimary:bmorsprvg-pri:monitor:RVG attribute not assigned for resource bmorsprvg.
 

Environment



Linux bosmorsp3 2.6.16.60-0.54.5-smp #1 SMP Fri Sep 4 01:28:03 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 3

The problem occurred after a reboot of anode and after restart of HAD.


Cause



After reviewing the ArgListValues in 'hares -display <RVGPrimary_Resource>', it was found that values for required attributes RVGResourceName and DiskGroup were missing for the affected node.


bmorsprvg-pri ArgListValues          localclus:bosmorsp3  bmorsprvg     bmorsprvg       bmorspdg        0       0       ""      0
bmorsprvg-pri ArgListValues          localclus:bosmorsp4  bmorsprvg     ""      ""      0       0       ""      0   <========





The ArgListValues for a RVGPrimary resource under the Parent Service Group are derived from the associated RVG resource which resides under Child Service Group with the relevant DiskGroup resource. As per the Veritas Volume Replicator Guide, an 'online local hard' Service Group dependency is necessary between RVGPrimary Service Group and RVG Service Group for proper VCS functionality of all resources.

In this case, the configuration file main.cf showed the correct RVGResourceName associated with the RVGPrimary resource, but there was no service group dependency between the service group containing the RVGPrimary resource and the service group containing the associated RVG resource.  Therefore, there is no guarantee, when the VCS engine (HAD) is restarted, that the RVG resource is probed before the RVGPrimary.


Solution



Create an 'online local hard' dependency between the service group containing the RVGPrimary resource and the service group containing the associated RVG resource:

haconf -makerw
hagrp -link <SGofRVGPrimaryResource>  <SGofRVGresource> online local hard

Verify the dependency has been created:

hagrp -dep

Save the config changes to disk:

haconf -dump -makero

Restart HAD on the node that was unable to probe the resource:

hastop -local -force

Verify HAD is stopped on the node:

tail -f /var/VRTSvcs/log/engine_A.log

Restart HAD on the node:

hastart

Verify output of:

tail -f /var/VRTSvcs/log/engine_A.log


 

hastatus -sum
 



Article URL http://www.symantec.com/docs/TECH177268


Terms of use for this information are found in Legal Notices