Error Message

From the RemoteGroup agent logs (/var/VRTSvcs/log/RemoteGroup_A.log), the following errors are printed when the resource is probed :

2012/02/13 21:44:11 VCS ERROR V-16-10061-3 RemoteGroup:remgrp_res:monitor:Error in connecting to the remote cluster (ip address 192.168.1.10). VCS API call returned with Error Id 256 and Error Message: Cluster login failed. Please verify username and password and try again

2012/02/13 21:45:10 VCS ERROR V-16-10061-3 RemoteGroup:remgrp_res:monitor:Error in connecting to the remote cluster (ip address 192.168.1.10). VCS API call returned with Error Id 256 and Error Message: Cluster login failed. Please verify username and password and try again

 

The error in RemoteGroup_A.log shows that VCS is unable to probe the RemoteGroup resource, because the agent is unable to get the remote service-group's information as it is unable to login to the remote-cluster due to incorrect password:

        RemoteGroup test_service_group (

                IpAddress = "192.168.1.10"

                Username = rguser

                Password = DRFpIPqPSrHPiRI

                GroupName = remote_cluster_group

                VCSSysName = ANY

                ControlMode = MonitorOnly

                )

<\snip>

 

The username/password supplied for the RemoteGroup resource are the credentials that this agent use to login to the remote-cluster to get the state of that group. For an unsecured VCS environment, this user is VCSuser, created using 'hauser' command on the remote-cluster.

Find more details on RemoteGroup in the following link :

https://sort.symantec.com/public/documents/sf/5.0MP3/solaris/html/vcs_users/ch_vcs_config_resources19.html

Reset the password for the user, as mentioned in the RemoteGroup resource configuration, on the remote-cluster and update the encrypted form of the same password in the 'Password' field of the RemoteGroup resource on the local-cluster. Following is the step-by-step procedure to update the same :

1. Change the password for the user 'rguser' in remote-cluster (i.e. cluster-2) :

# hauser -update

Enter Password:

Enter Again:

 

The above command will change the password for the user 'rguser'.

 

2. Update the new password in the RemoteGroup resource configuration in the local cluster (i.e. cluster-2) :

 

    2.1 For doing the same, first we'll need to generate the encrypted form of the new password (using vcsencrypt utility, see VCSENCRYPT(1M) ), which was used in above step :

           Run the following command to generate the encrypted password :

          # vcsencrypt -agent; echo ""         <---- (echo “” will just make the prompt go to the next line. Otherwise, the encrypted password will be printed on the terminal on the same line, the prompt appear)

          Enter Password:    **** Make sure, you enter the same password, you entered in first-step.

          Enter Again:

 

     This will print the encrypted string of the new password on the screen.

     ( e.g. :

       bash-2.05$ vcsencrypt -agent; echo ""

        Enter Password:

        Enter Again:

 

        aoeMfoDoe      <--- Encrypted string

       bash-2.05$

       )

 

    2.2 Change VCS to read-write mode :

          # haconf -makerw

 

    2.3 Copy the encrypted string and use it in the below command to update the password for the RemoteGroup resource :

          # hares -modify Password

 

    2.4 Save the configuration :

          # haconf -dump -makero

 

Now probe the resource again.

Applies To

Two cluster setups (cluster-1 & cluster-2) but Non-GCO configuration.

Local cluster (cluster-1) has a service-group which has RemoteGroup resource configured. This RemoteGroup resource probes and get the status of one of the service-group, configured in cluster-2.

There are other resources in cluster-1 which are dependent on RemoteGroup resource. Hence, all the parent resources in stack, are affected due to RemoteGroup is unable to probe.

RemoteGroup resource is not able to probe, even when manually trying to probe the resource. hastatus -sum shows the RemoteAgent resource under "RESOURCES NOT PROBED" : <snip> -- SYSTEM STATE -- System State Frozen A node-1 RUNNING 0 A node-2 RUNNING 0 … … -- RESOURCES NOT PROBED -- Group Type Resource System D test_service_group RemoteGroup remgrp_res node-1 D test_service_group RemoteGroup remgrp_res node-2 <\snip>