Last Modified: Jun 20, 2019
See more info
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, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Opened: May 25, 2017
The REST framework's 'gossip' mechanism does not appear to run between VIPRION blades in a device service cluster.
Gossip being enabled on the non-primary VIPRION blade interferes with communication between the primary and the remote peer.
-- 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.
The system no longer enables Gossip sync on non-primary VIPRION blades.
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.