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

Forum Discussion

Yonatan_Talmor's avatar
Yonatan_Talmor
Icon for Nimbostratus rankNimbostratus
Aug 19, 2017

forwarding IP VS: TCP resets

Hello This is a 2nd thread on an unresolved issue. I hope this case justifies a new thread due to the change of focus on the issue, from when originally asked to where it stands now. If unaccepted, ...
application delivery
big-ip
LTM
stan_piron's avatar
stan_piron
Icon for Cumulonimbus rankCumulonimbus
Aug 20, 2017

Hi,

before answering, I have a question:

Do you really require bridge mode?

when I read your question, I understood that hosts are in a VLAN, FWSM in another VLAN and you configured a VLAN group with these show VLANs.

with this kind of configuration, I should have created a new network instead of trying to configure this weird configuration.

In the previous thread, Chris Grant answered Bridge is difficult to troubleshoot... and it is true : You are wasting your time to configure something you can do differently!

Now, let's try to solve the issue anyway.

Your problem may be a loop problem between Active / Standby members if the VLAN group is not well configured. try to disable one of both network interfaces on the standby member...

As I remember when I've done it 10 years ago,

  • you may create a Forwarding (Layer-2) VS instead of Forwarding IP.
  • The VLAN group must have 
    Bridge In Standby
    option unchecked if 
    Transparency Mode
    is opaque.
  • The VLAN group should have 
    Bridge In Standby
    option checked if 
    Transparency Mode
    is Transparent or translucent.