Bug ID 544531: ConfigSync does not work in Virtual Edition configurations provisioned with a single NIC and single IP.

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2

Fixed In:
12.1.0, 12.0.0 HF3

Opened: Sep 08, 2015
Severity: 3-Major

Symptoms

ConfigSync does not work in Virtual Edition (VE) configurations provisioned with a single NIC and single IP.

Impact

You will be unable to to enable ConfigSync, or to synchronize configurations among the devices in a Device Group.

Conditions

This occurs when using BIG-IP VE v12.0.0 for Microsoft Azure and Amazon AWS when provisioned with a single NIC and a single IP address.

Workaround

None.

Fix Information

You can configure ConfigSync Only (there is no support of network failover, but it should be selected and disabled when creating the Device Group), for BIG-IP VE provisioned with a single NIC and a single IP address using the following steps: Steps to configure ConfigSync in Azure VE provisioned with a single NIC and a single IP address - configure configsync-ip in each VE/device - run "tmsh modify cm device <bigipX> configsync-ip <self-ip>" in each VE/device - in the master VE/device, run the following tmsh cmd-line: - to add all other VEs/devices to the trust-domain - run "tmsh modify cm trust-domain Root ca-devices add { <peer-mgmt-ip> } name <bigipX> user <user> password <password>" for each VE/device - to create a new device group for all VEs/devices - run "tmsh create cm device-group <device-group> devices add { <all-device-names-separated-by-space> } type sync-failover auto-sync enabled network-failover disabled - run "tmsh run cm config-sync to-group <device-group>" to initially sync-up configs among devices in device-group - Use version 12.0.0 HF1 EHF14 and later images. - Use a static private IP address provided by Azure Virtual Network. - Set db-var 'provision.1nicautoconfig' to be 'disable' before beginning. * No support of network failover when setting up ConfigSync in Azure. - A typical setup is as follows: - Configure configsync-ip in each VE/device. - In each VE/device, run the command: tmsh modify cm device <bigipX> configsync-ip <self-ip>. - In the master VE/device, complete the following steps at the tmsh command line: - To add all other VEs/devices to the trust-domain, complete the following steps at the tmsh command line for each VE/device: - Run the command: tmsh modify cm trust-domain Root ca-devices add { <peer-mgmt-ip> } name <bigipX> user <user> password <password>. - To create a new device group for all VEs/devices: - Run the command: tmsh create cm device-group <device-group> devices add { <all-device-names-separated-by-space> } type sync-failover auto-sync enabled network-failover disabled. - To initially sync-up configs among devices in device-group, run the command: tmsh run cm config-sync to-group <device-group>.

Behavior Change