DR setup not functioning properly when primary server got shutdown

[Sridhar_sri]

HI All,
I have made a DR setup between two node which are in different subnet. When there is a problme with respect to NIC card in primary server, there is an alert shown in the secondary server and hence my service group which is made as Global is brought successfully in the secondary server.

Where as when my primary server got shut down unexpectedly , my secondary server , remote cluster status shows the VCS heart beat as dead , but the alert which has to come as like as my earlier case is not coming . THe authority of the service group also holds with 0.

Can anyone suggest a solution for this problem.

With regards,
Sri.

[Gaurav_S]

Hello,

What sort of alert you are getting ? Have you configured a SMTP/SNMP notification or is it VCS self generated alert in engine_A.log ?


Gaurav

[Sridhar_sri]

HI gaurav,
                    when  my NIC card fails i am getting an alert in my secondary cluster as shown below

I am expecting this alert to come for Primary server shutdown scenario also. As because, when this alert comes when i click the Take action button it  shows me the App serivce group with a check box option as shown below.



THis makes me the APP service group to come ONLINE.

Hope now u understand which alert i am expecting.

More over while searching in google i came to knw that this is a known issue w.r.t VCS 5.0 (for it from VCS 5.0 Release notes) This was mentioned in relase notes

51031 Unable to automatically fail over global group %s remotely because local
cluster does not have Authority for the group.

If that is the case , will that be solved when i patch VSF HA 5.0 MP3 RP1 patch in my sol servers ?


So can you please provide me a solution or can you confirm is that a known issue with VSF HA 5.0 ?

Note : I have tried by giving OnlineLocal Hard / Firm dependency between APp and APp_Rep service groups which i have configured.

Ur help is much appreciated.

With regards,
Sri

[Gaurav_S · Accepted solution]

Hello Sri,

This is a known issues & is still open... so even MP3 doesn't fix this for now.... Might be an upcoming release may have fix for this....



Gaurav

[Sridhar_sri]

Thanks Gaurav , for your valuable reply within short time span.

[Sridhar_sri]

HI,
     Could you please confirm this is applicable for both MP3 and RP1(Rolling patch 1) ?

I mean this issue has not been fixed in RP1 patch also ?


Thanks,
Sri
        

[Gaurav_S]

Not fixed....

Gaurav

[Sridhar_sri]

Thanks Gaurav , For double confirming it...