Bug ID 461592: VXLAN traffic is not processed on a standby device.

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4

Fixed In:
11.6.0, 11.5.1 HF5

Opened: May 09, 2014
Severity: 3-Major
Related AskF5 Article:
K83781504

Symptoms

If the device is completely in a standby mode, it does not process VXLAN traffic.

Impact

The standby device does not process VXLAN traffic.

Conditions

An HA pair is configured with VXLAN tunnels and requires processing of VXLAN traffic on the standby device.

Workaround

None.

Fix Information

A new BigDB variable iptunnel.configsync controls the ConfigSync behavior on the standby device. If the variable is set to 'disable', the tunnel objects are not synchronized across the HA pair which allows setting the local address of the tunnel to a non-floating self address. The user has to configure the tunnel objects on both the active and the standby devices. This enables both devices to process VXLAN traffic. Note: The variable needs to be modified on both the active and the standby devices prior to creating any tunnels. By default, the variable is set to 'enable'.

Behavior Change