AIX

AIX

Connect with fellow AIX users and experts to gain knowledge, share insights, and solve problems.

 View Only
  • 1.  HACMP failover takes long time and it fails

    Posted Tue May 20, 2008 04:38 AM

    Originally posted by: SystemAdmin


    Hi All,
    I need a help regarding the error which iam facing on HACMP failover..
    OSlevel on both the nodes are at 5300-07-01 and the HACMP version installed on both the nodes is 5.4 .

    When we do a HA failover test on the secondary node it takes long time to move the resource group ie approximately 45 minutes and it fails ..

    becoz of this applications deployed get effected ..

    When we raise a software call they found that there is a bug with 5300-07-01 level and to fix this we need to install a efix ..

    Could any one tell whether installing this efix will provide a permanent solution or shall i get a down time to upgrade the oslevel to upperlevel 5300-08-01 and do the failover test ..


  • 2.  Re: HACMP failover takes long time and it fails

    Posted Tue May 20, 2008 04:45 AM

    Originally posted by: SystemAdmin


    If you are going for stability I would not go to TL8 as it hasn't been out long yet. You are a few SP's behind though. If I were you I would stay at TL7 and update to SP3 as long as that includes your fix. If it doesn't go to TL7 SP3 and apply the eFix after, but the eFix is not a permanent thing. You would have to remove it before patching AIX at a later date.

    Hopefully TL7 SP3 includes the full fix.

    Cheers,

    Sam

    Message was edited by: sam_rudland

    Message was edited by: sam_rudland


  • 3.  Re: HACMP failover takes long time and it fails

    Posted Tue May 20, 2008 10:25 AM

    Originally posted by: SystemAdmin


    Many Thanks Sam


  • 4.  Re: HACMP failover takes long time and it fails

    Posted Thu May 22, 2008 02:55 PM

    Originally posted by: SystemAdmin


    What version of HACMP 5.4 are you using. There was a bug with HACMP 5.4.0.2 which is fixed in 5.4.1 which may address your issue. We ran into an instance when getting into a config_to_long event which would cause the cluster to go into an error state. We since upgraded to HACMP 5.4.1 and had the issue resolved.