Manuel resume on BIGIP when It's down and restart.

I think it is: Menu path: Device Management > Traffic Groups > Name > Auto Failback > Disable

Auto Failback is here to avoid that your first BIG-IP in the traffic group member list don't become active after a reboot for example. Maybe it's more familiar to you under the name "preempt".

So the old active member will be in stand-by mode but if the second member failed, it'll become active back.

If I disable Auto-failback , Is scenario will be like this?

normally

BIGIP01 , BIGIP02 --> Active , Active ..respectively

{When BIGIP02 down and restart}

BIGIP01 , BIGIP02 --> Active (b unit 1,2) , Standby ..respectively

{When BIGIP01 down and restart}

BIGIP01 , BIGIP02 --> Standby , Active (b unit 1,2) ..respectively

Spot on.

Hi guys, sorry for the long time since your last question...

I made some tests this morning and I can assure you that without Auto-failback the scenario I gave to you, and resumed by teepan123 is the good one. Even if the order is to have the BIG-IP01 active on a traffic-group, it'll stay standby after a reboot.

Hi guys, sorry for the long time since your last question...

I made some tests this morning and I can assure you that without Auto-failback the scenario I gave to you, and resumed by teepan123 is the good one. Even if the order is to have the BIG-IP01 active on a traffic-group, it'll stay standby after a reboot.

How to do disable Auto-failback with v. 10.2.4 ?

It's available in v10 but not related to Traffic Groups. The setting should be under System > High Availability > Fail Back. See here for more: http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos_management_guide_10_1/tmos_appendix_b_redundancy.html

@What Lies Beneath

I test with 10.2.4 with change setting by using "b db failover.manfailback enable" like in manual

Problem is It will occur standby-standby situation !!!

BIGIP01 , BIGIP02 --> Active , Active ..respectively

{When BIGIP02 down and restart}

BIGIP01 , BIGIP02 --> Active (b unit 1,2) , Standby ..respectively

{When BIGIP01 down and restart}

BIGIP01 , BIGIP02 --> Standby , Standby ..respectively !!!!

This is standby-standby situation -_-

I'd suggest you change the bigDB key back to disable and only change the setting in the GUI and test again.