Original Publication Date: 08/30/2013
This release note contains information related to downloading and configuring Enterprise Manager Virtual Edition (VE).
Enterprise Manager Virtual Edition (VE) is a version of the Enterprise Manager system that runs as a virtual machine, packaged to run in a VMware® hypervisor environment. Enterprise Manager VE includes all features of Enterprise Manager, running on standard Enterprise Manager platforms.
Enterprise Manager Virtual Edition (VE) is compatible with VMware ESX® 4.0 and 4.1, and VMware ESXi™ 4.0 and 4.1 hosts.
The virtual machine guest environment for Enterprise Manager VE includes these characteristics:
Note: When you use the VMware vSphere client system to deploy Enterprise Manager VE on the ESX or ESXi host system, it is important that you retain the guest environment characteristics as shown here. Modifying these characteristics can produce unexpected results. Also note that the guest environment does not support vmmemctl, the memory balloon driver.
To deploy the Enterprise Manager VE system on a VMware ESX or ESXi server, you perform the following tasks:
After you complete these tasks, you can log in to Enterprise Manager VE system and run the Setup utility. Using the Setup utility, you can perform basic network configuration tasks such as assigning VLANs to interfaces.
There are specific requirements for the host system on which the Enterprise Manager VE system can run.
To successfully deploy and run the Enterprise Manager VE system, the host system must contain the following:
F5 Networks highly recommends that the host system contain CPUs based on AMD-V or Intel-VT technology.
The first steps in deploying Enterprise Manager VE are to download the Zip file to your local system. You can then run the Deploy OVF Template wizard from within VMware vSphere Client. This wizard copies the file to the ESX/ESXi server and configures some network interface settings. Note that the Zip file contains a virtual disk image based on an Open Virtual Format (OVF) template. By following the steps in this procedure, you create an instance of the Enterprise Manager system that runs as a virtual machine on the host system.
Important: Do not modify the configuration of the VMware guest environment. This includes the settings for the CPU, RAM, and network adapters. Doing so can produce unexpected results.
You must power on the Enterprise Manager VE virtual machine.
Enterprise Manager VE needs an IP address assigned to its virtual management port.
Tip: F5 Networks highly recommends that you specify a default route for the virtual management port.
When deploying Enterprise Manager Virtual Edition on a VMware ESX or ESXi host, you should follow these best practices.
|Shared storage for virtual machines||Use NFS for shared virtual machine storage, although all types of VMware-supported storage are acceptable.|
|Redundant system configuration||Run the two units of an active/standby pair on separate physical hosts. You can accomplish this in two ways. You can manually create a virtual machine peer on each host, or, if you are using VMware Dynamic Resource Scheduler (DRS), you can create a DRS rule with the option Separate Virtual Machine that includes each unit of the Enterprise Manager VE redundant system. Note that Enterprise Manager VE does not support VMware Fault Tolerance technology. For information on creating a DRS rule, refer to VMware's vSphere manuals.|
|Live migration||Perform live migration of Enterprise Manager VE virtual machines (using VMware VMotion) on idle Enterprise Manager VE virtual machines only. Live migration of Enterprise Manager VE while the virtual machine is processing traffic could produce unexpected results.|
|VMware DRS environments||In DRS environments, perform live migration of Enterprise Manager VE virtual machines (using VMware VMotion) on idle Enterprise Manager VE virtual machines only. Live migration of Enterprise Manager VE while the virtual machine is processing traffic could produce unexpected results. Disable automatic migrations by adjusting the VMware VMotion DRS Automation Level to Partially Automated, Manual or Disabled on a per-Enterprise Manager VE basis.|
|Resource reservations||Increase the 2GHz default CPU reservation to prioritize Enterprise Manager VE processing if your normal traffic patterns cause Enterprise Manager VE to consistently exceed that reservation. Enterprise Manager VE presents a unique workload when virtualized, compared to other commonly virtualized services. Therefore, Enterprise Manager VE is deployed by default with a 2GHz CPU reservation and a 2GB memory reservation. Together, these reservations prevent system instability on heavily loaded VMware hosts. Note that these reservations should be considered minimal.|
|Time synchronization||Configure all Enterprise Manager VE systems to use an external time synchronization source. You can do this either by configuring NTP within Enterprise Manager VE or by checking the Synchronize guest time with host box within vSphere Client and configuring all VMware hosts to share a single NTP time server or set of related NTP time servers. Note that units within a redundant system configuration must share a common time synchronization source, to prevent inconsistent system behavior.|
|Default route for management port||Define a default route for the virtual management port.|
This release contains the following known issues.
Virtual Edition disk resources (ID 349454)
In certain instances, on an Enterprise Manager Virtual Edition deployment, you may encounter TMM errors due to the way Enterprise Manager uses its database. To help avoid this scenario, set disk resources as a high priority when configuring resources.
Labeling errors (ID 353549)
When you start up Enterprise Manager Virtual Edition, the initial start screen incorrectly displays BIG-IP LTM Virtual Edition even though the system is running Enterprise Manager Virtual Edition.
Media speed messages in log file (ID 354903)
When starting the Enterprise Manager system or when removing an interface from a VLAN, the system logs media-related messages to the file /var/log/ltm. You can ignore these messages.
[ Top ]
For additional information, please visit http://www.f5.com.