If a peer object has auto-initialization enabled, the BIG-IP system will
automatically create outbound connections to the active pool members in the specified pool using
the configuration of the specified transport-config. For auto-initialization to attempt to create
a connection, the peer must be included in a route that is attached to a router instance. For
each router instance that the peer is contained in, a connection will be initiated. The
auto-initialization logic will verify at a configurable interval if the a connection exists
between the BIG-IP and the pool members of the pool. If a connection does not exist, it will
attempt to reestablish one.
The first auto-intialization attempt will occur at least one auto-initialization-interval delay
from when the object is loaded or changed in the TMM.
If the router instance is not included in any virtual servers, connection auto-initialization
will not start. Once the router instance has been included in an enabled virtual server,
auto-initialization will begin and will remain running for those peers used by routes attached to
the router instance even if the router instance is removed from the virtual server.
If a peer with auto-initialization enabled, is used in multiple router instances, a separate
connection will be established for each router instance.
The auto-initialization logic will only attempt to create connections to enabled pool members.
If the pool member is marked down by an external monitor it will be ignored unless an inband
monitor is also attached.
If mirroring is enabled on the router instance, the active device will initialize outgoing
connections. The new outgoing connections will be mirrored to the standby device.