Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

YUECHU's avatar
YUECHU
Icon for Altostratus rankAltostratus
Jan 11, 2024

F5 After the active/standby switchover, the host interface is down

HI        F5 Performs an active/standby switchover after upgrade 15.1.10. Everything is normal before the switchover. After the switchover, the interface of the active device is down, and the interf...
application delivery
YUECHU's avatar
YUECHU
Icon for Altostratus rankAltostratus
Jan 14, 2024

is F52600 (version 15.1.5.1 --> 15.1.10.2)

Device physical interface down  ，Restore after disabling enable it

PhatANhappy's avatar
PhatANhappy
Icon for MVP rankMVP
Jan 16, 2024

Which physical interface?

 

  • YUECHU's avatar
    YUECHU
    Icon for Altostratus rankAltostratus
    Jan 16, 2024

    sorry , is 6 According to the above statement, the interface is down (6)

     

    • PhatANhappy's avatar
      PhatANhappy
      Icon for MVP rankMVP
      Jan 17, 2024

      Without more details of your configuration - it makes it very difficult to troubleshoot.
      Please goto network (1) - self ips (2) and check your configration for proper traffic group configuration.  

      I use my naming convention to call out purpose.   i.e. -
      LoadBalancerName-Vlan-Self = traffic-group -local only <---this is suspect is what you have and is causing the error.   This as a self - belong to the individual f5 and will not failover it stays the same.
      LoadBalancerTG-Vlan-FLOAT = traffic group that is responable for failover - hence will float from one side of a ha pair to another, i suspect you are missing one or more of these.

      I drew some lines on mine -and colorcoded them to show you the selfs - and the floats and the traffic groups etc. 

      • YUECHU's avatar
        YUECHU
        Icon for Altostratus rankAltostratus
        Jan 17, 2024

        Thank you very much for your help😀, because this problem occurred at the customer's site, so there is no relevant information at present. The configuration of self-ipd is no problem. Because according to the fault scenario, two 2600s, A is the active device, B is the standby device, after the upgrade, (the standby device is upgraded first), the active/standby switchover (B becomes the active device), and then the upgrade (A becomes the standby device), an active/standby switchover will occur, and services are normal. The customer expects the active/standby status of the two F5s to be the same as before the upgrade. Therefore, I manually switched again, and then (B became the standby device again) After A became the primary device, the interface (that is, 6 in the figure you sent to me) went down, and the service went down. The subsequent recovery state is what I said, disable, then enable, then restore.

        I'm sorry if what I said was a little convoluted.