Original Publication Date: 08/30/2013
This release note documents the version 3.1.0 virtual edition release of Enterprise Manager.
Enterprise Manager Virtual Edition (VE) is compatible with:
The virtual machine guest environment for Enterprise Manager VE includes these characteristics:
This following documentation is associated with this release:
When deploying Enterprise Manager Virtual Edition, 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.|
|High availability configuration||Run the two systems of high availability 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 performing tasks 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 4GB 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 high availability 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.|
For additional information, please visit http://www.f5.com.
You can find additional support resources and technical documentation through a variety of sources.
Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.
AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
The F5 DevCentral community helps you get more from F5 products and technologies. You can connect with user groups, learn about the latest F5 tools, and discuss F5 products and technology.