For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

habib_Khan's avatar
habib_Khan
Icon for Nimbostratus rankNimbostratus
Feb 13, 2014

F5 config help needed

Hi All,

Can we have the LB automatically switch over from .164 to .165 when 3306 is not working BUT do not automatically switch back to .164 when 3306 comes back? We want to manually switch it back when we are ready. Bascially we want only one way redundancy from primary server to secondary server.

Below is the config. Basically as priority is high on .164 the traffic is on it, but if i 3306 is down on .164 and if i increase priority on .165 it becomes primary and when .164 service comes up it should ot take over.

[root@LB02:Active] config b virtual vip-X.X.32.177_3306 VIRTUAL ADDRESS X.X.32.177 UNIT 1 | ARP enable | (cur, max, limit, tot) = (40, 51, 0, 18960) | (pkts,bits) in = (432.5M, 503.3G), out = (419.6M, 447.6G) +-> VIRTUAL vip-X.X.32.177_3306 SERVICE mysql | PVA acceleration none | (cur, max, limit, tot) = (40, 51, 0, 18960) | (pkts,bits) in = (432.5M, 503.3G), out = (419.6M, 447.6G) | requests (total) = 0 +-> POOL pool-X.X.32.177_3306 LB METHOD round robin MIN/CUR ACTIVE MEMBERS 1/2 | (cur, max, limit, tot) = (40, 50, 0, 18893) | (pkts,bits) in = (425.9M, 500.5G), out = (419.6M, 447.6G) +-> POOL MEMBER pool-X.X.32.177_3306/10.33.86.164:mysql active,up | | session enabled priority 2 ratio 1 | | (cur, max, limit, tot) = (40, 50, 0, 18893) | | (pkts,bits) in = (425.9M, 500.5G), out = (419.6M, 447.6G) | | requests (total) = 0 +-> POOL MEMBER pool-X.X.32.177_3306/10.33.86.165:mysql active,up | session enabled priority 1 ratio 1 | (cur, max, limit, tot) = (0, 0, 0, 0) | (pkts,bits) in = (0, 0), out = (0, 0) | requests (total) = 0

 b pool pool-X.X.32.177_3306 list

pool pool-X.X.32.177_3306 { min active members 1 monitor all tcp members { X.X.X.164:mysql { priority 2 } X.X.X.165:mysql { priority 1 } } }

2 Replies

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Feb 13, 2014

    Looks like you're already using priority group activation, so all you need to do is change your TCP monitor to use manual resume. It's one of the settings within the TCP monitor configuration.

    Manual Resume: Displays whether the system automatically changes the status of a resource to Enabled at the next successful monitor check. If you set this option to Yes, you must manually re-enable the resource before the system can use it for load balancing connections. The default is No.

•Yes: Specifies that you must manually re-enable the resource after an unsuccessful monitor check.

•No: Specifies that the system automatically changes the status of a resource to Enabled at the next successful monitor check.
  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    Feb 13, 2014

    Habib,

    One option. On your Pool Member monitor (TCP in this case I think), you could create a custom one and set Manual Resume to Yes. This means that when a pool member is marked down by a monitor and then comes back up it isn't automatically enabled but kept in a disabled state. You would need to manually enable it.

    LTM log would report something like:

    Pool /Common/test member /Common/test_node:80 monitor status up awaiting man resume.

    Hope this helps, possibly.

    N