why TSA is not doing take over if primary is powered off physically?

Harishkumar .Pathangay

why TSA is not doing take over if primary is powered off physically?

Hi,

why TSA is not doing take over if primary is powered off physically?

I have TSA setup with domain online and lssam output all online for primary server and offline for standby. My Initial cluster state is proper.

I go and physically power off my primary server. I was expecting a cluster initiated take over by TSA resulting in my standby taking over as primary. Peer Window is 30 sec and HADR_TIMEOUT is 120 sec. I have waited for 20 minutes, but no signs of take over is happening.

I can provide OS system logs etc if needed. But need confirmation on expectation that stand by should take over as primary in case primary node got powered off.

I even have a document from IBM authors, very clearly mentioning this, but my setup is not working the way it should. Any inputs are appreciated.

thanks,

harish p

Venkat D

RE: why TSA is not doing take over if primary is powered off physically?
(in response to Harishkumar .Pathangay)

Hi Harish,

There are certain parameters need to verified and updated to perform failover during shutdown or reboot of the server.

chrsrc -c IBM.PeerNode CritRsrcProtMethod=5

Verify the critical protection value and update it accordingly.

https://www.ibm.com/support/pages/critrsrcprotmethod-and-tsamp-critical-resource-protection

Thanks.

Harishkumar .Pathangay

RE: why TSA is not doing take over if primary is powered off physically?
(in response to Venkat D)

hi,

I apologies for not responding earlier. thanks for your inputs.

Issue is solved, I had peer window time of 30 sec, was not enough. raised it to 180 sec, and works as expected.

thanks,

harish p