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

Muhammad_Irfan1's avatar
Dec 15, 2014

Failover from active ltm to passive ltm on the basis of interface down.

I have 2 LTM 5000s v11.4.1. Working in Active passive. There are two Nexus 5548P also working in active passive. Its fully mesh connection means active switch is connected to both active and passive F5 same for switch02 connected to both F5 LTM.

 

Is there some way that LTM fail over to standby LTM on the basis of if any interface of Active ltm goes down? Like in cisco we track an interface and decrement from HSRP to fail over to another side. Can we fail over on the basis of interface down in F5?

 

I saw some failover on the basis of trunks but not interfaces.

 

11 Replies

  • I saw some failover on the basis of trunks but not interfaces.

     

    you can create trunk with one interface member.

     

    • Muhammad_Irfan1's avatar
      Muhammad_Irfan1
      Icon for Cirrus rankCirrus
      Creating trunk on 1 interface member then what will be that interface on the cisco switch? Trunk or etherchannel? As I understand f5 tagged interface = cisco trunk and f5 trunk = cisco etherchannel isn't it?
    • nitass_89166's avatar
      nitass_89166
      Icon for Noctilucent rankNoctilucent
      you do not need 802.3ad because there is only one interface. if there is 802.3q, you just configure the same on both sides.
    • Muhammad_Irfan1's avatar
      Muhammad_Irfan1
      Icon for Cirrus rankCirrus
      If i add tagged interface into trunk during production will it stop traffic? as it is already trunk on the switch.
  • I saw some failover on the basis of trunks but not interfaces.

     

    you can create trunk with one interface member.

     

    • Creating trunk on 1 interface member then what will be that interface on the cisco switch? Trunk or etherchannel? As I understand f5 tagged interface = cisco trunk and f5 trunk = cisco etherchannel isn't it?
    • nitass's avatar
      nitass
      Icon for Employee rankEmployee
      you do not need 802.3ad because there is only one interface. if there is 802.3q, you just configure the same on both sides.
    • If i add tagged interface into trunk during production will it stop traffic? as it is already trunk on the switch.