Forum Discussion

CKFR_356853's avatar
CKFR_356853
Icon for Nimbostratus rankNimbostratus
Sep 10, 2018

Active was down, Standby took over, then Active went up, conflict happened.

Hello,

I have an issue with my Active/Standby F5 devices.

Active node (F5_A) lost its network connection.

Standby node (F5_B) took over as Active.

After 10 minutes, F5_A went back online. So, I have Active/Active devices.

Everything failed because of this case. I had to force to Standby F5_B to be able to be online again.

Why does this conflict happened?

This article is what we have setup right now, except, we use Network Failover because they are located in different location.

http://itadminguide.com/configure-high-availability-activestandby-of-big-ip-f5-ltms/

Auto failback is disabled on both devices.

I saw this logs when F5_A went back online. I am not sure about the behavior of it once it went back.

Sep  7 22:39:12 f5_B notice sod[7345]: 010c007e:5: Not receiving status updates from peer device /Common/f5_A (10.41.253.44) (Disconnected).
Sep  7 22:39:12 f5_B notice sod[7345]: 010c006d:5: Leaving Standby for Active (best load): NextActive:.
Sep  7 22:39:12 f5_B notice sod[7345]: 010c0053:5: Active for traffic group /Common/only_4751.
Sep  7 22:39:12 f5_B notice sod[7345]: 010c006d:5: Leaving Standby for Active (best load): NextActive:.
Sep  7 22:39:12 f5_B notice sod[7345]: 010c0053:5: Active for traffic group /Common/prefer_4751.
Sep  7 22:39:12 f5_B notice sod[7345]: 010c006d:5: Leaving Standby for Active (best load): NextActive:.
Sep  7 22:39:12 f5_B notice sod[7345]: 010c0053:5: Active for traffic group /Common/prefer_MDR.
Sep  7 22:39:12 f5_B notice sod[7345]: 010c006d:5: Leaving Standby for Active (best load): NextActive:.
Sep  7 22:39:12 f5_B notice sod[7345]: 010c0053:5: Active for traffic group /Common/traffic-group-1.
Sep  7 22:39:12 f5_B notice sod[7345]: 010c0019:5: Active
Sep  7 22:49:10 f5_B notice sod[7345]: 010c007f:5: Receiving status updates from peer device /Common/f5_A (10.41.253.44) (Online).
Sep  7 22:49:10 f5_B notice tmm1[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32771 for traffic-group /Common/only_4751 established.
Sep  7 22:49:10 f5_B notice tmm3[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32769 for traffic-group /Common/only_4751 established.
Sep  7 22:49:10 f5_B notice tmm2[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32768 for traffic-group /Common/only_4751 established.
Sep  7 22:49:10 f5_B notice tmm[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32770 for traffic-group /Common/only_4751 established.
Sep  7 22:49:10 f5_B notice tmm[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32771 for traffic-group /Common/prefer_4751 established.
Sep  7 22:49:10 f5_B notice tmm2[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32769 for traffic-group /Common/prefer_4751 established.
Sep  7 22:49:10 f5_B notice tmm1[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32770 for traffic-group /Common/prefer_4751 established.
Sep  7 22:49:10 f5_B notice tmm3[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32768 for traffic-group /Common/prefer_4751 established.
Sep  7 22:49:10 f5_B notice tmm3[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32769 for traffic-group /Common/prefer_MDR established.
Sep  7 22:49:10 f5_B notice tmm1[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32771 for traffic-group /Common/prefer_MDR established.
Sep  7 22:49:10 f5_B notice tmm2[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32768 for traffic-group /Common/prefer_MDR established.
Sep  7 22:49:10 f5_B notice tmm[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32770 for traffic-group /Common/prefer_MDR established.
Sep  7 22:49:10 f5_B notice tmm3[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32770 for traffic-group /Common/traffic-group-1 established.
Sep  7 22:49:10 f5_B notice tmm1[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32768 for traffic-group /Common/traffic-group-1 established.
Sep  7 22:49:10 f5_B notice tmm2[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32771 for traffic-group /Common/traffic-group-1 established.
Sep  7 22:49:10 f5_B notice tmm[21172]: 01340001:5: HA Connection with peer 10.70.1.236:32769 for traffic-group /Common/traffic-group-1 established.
application delivery
availability
fail over
LTM
  • youssef1's avatar
    youssef1
    Icon for Cumulonimbus rankCumulonimbus
    Sep 10, 2018

    Hi,

     

    Of course you need to check "network failover", as you told your equipment are located in different location so I suppose you don't use serial cable. you use HA (Network failover trough you HA vlan).

     

    I think that communication trough F5_A and F5_B trough the HA vlan did not work, probably a network problem between the 2 members trough the vlan that you set for network failover.

     

    I advise you to add an additional vlan and/or use admin network additional. as if there is a network problem through your HA vlan you will still be able to communicate through another network or management interface.

     

    Hope it will help you.

     

    regards,