Bug ID 666505: Gossip between VIPRION blades

Last Modified: Jan 24, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: May 25, 2017
Severity: 2-Critical

Symptoms

The REST framework's 'gossip' mechanism does not appear to run between VIPRION blades in a device service cluster.

Impact

Gossip being enabled on the non-primary VIPRION blade interferes with communication between the primary and the remote peer.

Conditions

-- VIPRION systems. -- Configured with device service clustering and a high availability (HA) group. -- The REST framework's 'gossip' mechanism is configured on the non-primary blade.

Workaround

None.

Fix Information

The system no longer enables Gossip sync on non-primary VIPRION blades.

Behavior Change

Previously, when The REST framework's 'gossip' mechanism was enabled on the non-primary VIPRION blade, it interfered with communication between the primary and the remote peer. Now, the 'gossip' mechanism is disabled on the non-primary blade, so communication between the primary and the remote peer is not impacted.