Forum Discussion

Sams_88783's avatar
Sams_88783
Icon for Nimbostratus rankNimbostratus
Mar 09, 2010

Failover active states not updating with 9.3.1

Hi Julian,

 

 

I am facing the same problem.

 

Earlier both the units showing status as correct but now both are showing as Active.

 

I had done some changes and Sync the config but no luck

 

Its correctly detectcing the config change as well sync status

 

The version which my device is running 9.3.1

 

Please help

 

 

Regards

 

Sumod
management
microsoft
scom
  • Julian_Balog_34's avatar
    Julian_Balog_34
    Historic F5 Account
    Mar 10, 2010
    Sumod,

     

     

    What is the version of the F5 Management Pack that you have? (You can check the HKEY_LOCAL_MACHINE\Software\F5Networks\ManagementPack: Version and Build registry keys). Can you also check the big3d version on the BIG-IP device? You can run the following command:

     

     

    strings /usr/sbin/big3d | grep "big3d Version"

     

     

    Normally the fail-over state on the device should have been updated if you had the config change done. We'll have to run a repro scenario with 9.3.1 devices, to see if there might by any specific problems related to the platform, for getting the config updates. We do know about some, which have been recently fixed, while querying device config from 9.3.1, but still the fail-over state update should have happened.

     

     

    Our next release of the F5 Management Pack will address the problem of the automatic update of the fail-over state with redundant pair device configurations, but we could probably work around your issue even before that. You can also try to run the "Force F5 Device to Standby" task from the SCOM console on the device that you would expect it should show up as stand-by.

     

     

    Let us know and we'll try to repro the problem on our end and hopefully come up with a solution.

     

     

    Thanks!

     

    Julian