Supporting HA data synchronization for BIG-IP frameworks: MCP and REST Framework

The ha-sync script supports HA data synchronization for the following BIG-IP frameworks: MCP and REST Framework.

Unless specifically setting the HA sync target via the --target (or -t) option parameter, the ha-sync script will perform HA synchronization for all supported platforms. By default, the order of HA synchronization is: * MCP config-sync * REST framework gossip/sync.

The order of the HA sync targets can be altered via the --target (or -t) option parameter, for example:

ha-sync -H 10.192.228.78 -t rest mcp

where the HA sync targets are executed in the order specified with the -t option parameter.

MCP

By default, the MCP HA configuration-sync is included in the default HA sync workflow by the ha-sync script. Otherwise it can be specified (or singled out) with the --target mcp (or -t mcp) option parameter of the ha-sync script, for example:

ha-sync -H 10.192.228.78 -t mcp

Unless the --force (or -f) option is specified, the ha-sync would perform an incremental MCP config-sync. With the --force (or -f) option a full config-sync is performed. Depending on use case scenarios and BIG-IP configurations, one or the other could be invoked. A full config-sync would perhaps take considerably longer to complete.

The default HA device group name assumed in the MCP config-sync is HA_GROUP. This can be specified via the --devicegroup (or -D) option parameter.

REST Framework

By default, the REST Framework gossip/sync is included in the default HA sync workflow by the ha-sync script. Otherwise it can be specified (or singled out) with the --target rest (or -t rest) option parameter of the ha-sync script, for example:

ha-sync -H 10.192.228.78 -t rest

When the --force (or -f) option is specified, the ha-sync script also copies the REST Framework storage from the local device to the remote HA peer.