You must perform basic system setup and activate a license on at lease three iWorkflow™ systems before you can configure a high availability
Configuring iWorkflow™ as part of a high availability (HA)
cluster ensures that you do not lose application delivery management capability
because one iWorkflow system fails.
Important: You should designate one of the iWorkflow devices in the HA
cluster as the lead device. Once you create the cluster, make configuration changes
only to that device and let the automatic synching process work.
Important: Do not confuse the iWorkflow HA cluster you create in this
process with a BIG-IP device cluster. Although the concept is similar, this process
creates a cluster of iWorkflow devices. BIG-IP HA cluster configuration is a
Important: To synchronize properly, the iWorkflow systems must be running
the same version of software. The exact configuration in terms of virtual hardware
is not required; however, the systems should have comparable resources. This is
required because, in the event of a fail over, the peer must be able to maintain the
process requirements for both systems. This is especially important in terms of disk
space and data collection.
Important: The devices that you add as HA peers must be in an unconfigured
state. That is, you should complete only the basic setup tasks. Specifying
configuration details beyond those covered in the licensing and initial
configuration process is likely to complicate the synching process.
Important: You can either operate the iWorkflow system in standalone mode,
or as part of a three-peer cluster. Other configurations are not supported at this
If discovery of the newly configured iWorkflow system fails, a
Delete button displays. Verify the correct self IP
address and credentials. Then click the Delete button to
remove the incorrect information, and re-type the self IP address, user name, and