After you configure one or more F5® devices in your network and determine how you want to incorporate Enterprise Manager™, you can perform specific tasks to complete the initial setup of your Enterprise Manager and discover devices in your network.
You specify the initial configuration settings from the Setup Utility Platform screen.
|To use Enterprise Manager in a high availability configuration||Select the Config Sync and High Availability check boxes, and select an option for the Failover Method setting|
|If you are not using Enterprise Manager in a high availability configuration||Clear the Config Sync and High Availability check boxes|
Using Enterprise Manager™ in a high availability configuration (optional) is different than a BIG-IP®device service clustering configuration. The main function of Enterprise Manager in a high availability configuration is to provide a warm backup of an active system. A warm backup is a standby peer system on which you duplicate the configuration information of the active Enterprise Manager, and can perform all of the functions of its peer, but requires manual intervention to maintain the integrity of the backup configuration information.
When Enterprise Manager is configured for high availability, you back up the Enterprise Manager configuration (including device, alert, archive, certificate, and software repository information) to a standby system. In the event that the active system becomes unavailable, you can fail over to that system.
The high availability features for Enterprise Manager are not the same as the device service clustering feature associated with a BIG-IP system. Before using Enterprise Manager in a high availability configuration, it is important to review these considerations and details.
|You must use Enterprise Manager only in active-standby mode for high availability.||When you specify the high availability settings during the initial configuration, use the active-standby configuration and not the active-active configuration.|
|The high availability system for Enterprise Manager works differently than the device service clustering feature for the BIG-IP system. Enterprise Manager does not automatically synchronize, in real time, user-configured or scheduled tasks (such as a software installation or archiving tasks). After a failover, the newly active system maintains the last known configuration before any user-initiated or scheduled task if the systems were properly synchronized.||For a successful failover, you must run a ConfigSync operation after each major configuration change.|
|Enterprise Manager contains all of the configuration details for managed devices in your networks, so there is more information to synchronize with its peer. Therefore, the ConfigSync process for an Enterprise Manager high availability configuration is considerably longer than a similar synchronization process on a BIG-IP device. The ConfigSync task might display as complete before the process has finished.||To verify synchronization after you start a ConfigSync task, check the status of the target device to which you are copying the configuration. If a maintenance task appears in the task list, the ConfigSync task is not complete.|
|If a task is running during a failover, the task does not continue when the standby peer becomes the active peer.||If you discover a task was running at the time you ran the ConfigSync task, you must re-start that task on the peer when it becomes active.|
|You cannot make configuration changes to Enterprise Manager when it is in standby mode, such as adding devices, importing software, or configuring alerts on the standby device. If you attempt to make a configuration change to Enterprise Manager when it is in standby mode, you will receive an error.||To ensure that you do not initiate tasks on a standby system, check for an Active or Standby status message in the upper left corner of the screen.|
Before configuring Enterprise Manager as a high availability system, you must license the system and then, on the same network, configure self IP addresses and a gateway or route. You must also be aware of the differences between a high availability configuration for Enterprise Manager and the device service clustering configuration for BIG-IP.
Before you can use Enterprise Manager™ to manage devices in your network, you must add the devices to the device list. For BIG-IP® devices in your network, you can use the discovery process to search specific IP addresses or IP subnets in your network, and add those devices to Enterprise Manager. Discovery is the process by which Enterprise Manager successfully logs on to available devices with an administrator user name and password that you supply. If Enterprise Manager succeeds in logging on to devices that it discovers, it adds those devices to the list on the Device List screen.
You can discover devices either by scanning your network for specific IP addresses, or importing a file that contains a list of all of the IP addresses, user names, and passwords for the devices you want to discover.
After you license and perform initial configuration for Enterprise Manager™, you can scan your network to discover F5® devices.
Discovering devices is the first step toward device management.
|Address List||Select this option if you know the IP addresses specific of the devices that you want Enterprise Manager to discover.|
|Subnet||Select this option if you want Enterprise Manager to use the IP address and netmask of the subnet to scan your network for devices to discover.|
After you license and perform initial configuration for Enterprise Manager, you can discover F5 devices.
If you have a large number of devices, instead of typing the information required to scan your network, you can import a file in comma-separated values format (CSV) from your local system that contains the IP addresses, user names, and passwords of the devices that you want to discover.
If a managed device cannot communicate with Enterprise Manager, the Device List page displays the message, Device cannot contact EM, in the Details column next to a device name. If this occurs, you can troubleshoot potential issues from the command line of the managed device.