Original Publication Date: 08/30/2013
This release note documents the version 3.0.0 release of Enterprise Manager.
You can apply the software upgrade to Enterprise Manager 4000 or Enterprise Manager Virtual Edition (VE) platforms running software versions 2.x.
Enterprise Manager version 3.0.0 supports the following software versions:
The BIG-IP system Configuration utility supports the following browsers and versions:
The following manuals are associated with this release:
If you are using a new Enterprise Manager system, the current software is loaded and configured. For procedures about specifying network options and performing initial configuration, refer to the Enterprise Manager Getting Started Guide.
If you are upgrading an existing system, you must download and install the upgrade. For procedures, refer to the Software Management chapter of the Enterprise Manager Getting Started Guide.
In this release, BIG-IP iHealth is integrated with Enterprise Manager. You can create a task to gather iHealth diagnostics once, or on a regular schedule. The results of the data collection specify any configuration issues, recommended solutions, and any associated links to the AskF5 Knowledge Database for reference.
Starting in this release, Enterprise Manager supports IPv6 IP protocol.
You can now enable and disable virtual servers through Enterprise Manager.
In this release, you can view and manage objects specific to Global Traffic Manager.
You can now compare the configurations of two separate devices.
|ID 325481||Device refresh time for managed devices is reduced by approximately 10% in this release.|
|ID 328550||Enterprise Manager now supports device discovery through IPv6 addresses.|
|ID 337060||The disk space allocated for the statistics database now displays properly after you upgrade Enterprise Manager.|
|ID 337489||The memory consumption issues that previously occurred when Enterprise Manager refreshed a device are resolved in this release.|
|ID 355713, 357838||Enterprise Manager now collects statistics from managed devices, regardless of the device's time zone setting. The workaround described in SOL12845 on the AskF5 Knowledge Base is no longer required.|
|ID 361908||Now, after a device refresh, Enterprise Manager correctly updates the boot location information for the device.|
|ID 371859||Previously, iControl connection handling caused unnecessary log entries, such as getNodeConfig: iControl error: iControl::char*:SOAPException: Cannot convert a struct to a string. This issue is resolved and the superfluous entries are no longer logged.|
|ID 372971||On the Access Control User List screen, the online help no longer specifies the List Web Role and the List Shell Role, since these roles are not applicable.|
|ID 373394, 376753||Enterprise Manager no longer displays an Attack Signature Update Available message in the device list details for managed devices that are not licensed for ASM.|
|ID 373941||The Node Inventory report now consistently displays all nodes for managed devices.|
|ID 374028||The Node Inventory Report previously displayed extra page breaks. This issue is fixed and the report now displays properly.|
|ID 374271, 379732||Previously, when certain conditions were met, the mcpd process on a VIPRION system's secondary blades restarted. This issue is resolved. You can now re-enable statistics collection for any VIPRION system for which you previously disabled it as a workaround for this issue.|
|ID 374389, 374386||In prior releases, there was an issue discovering and managing peer devices with multiple mirroring addresses. This issue is resolved.|
|ID 374598||Enterprise Manager now uses the configured SSL proxy for the DNS lookup during an ASM attack signature file update task.|
|ID 374973||Previously, if Enterprise Manager was left running for more than 50 days, the CPU system alert reported 100% CPU usage. This issue is resolved.|
|ID 375022, 374736||Scheduled reports you have configured are now available when you upgrade from Enterprise Manager version 2.2.0.|
|ID 375183||Previously, after an upgrade, Enterprise Manager was sometimes unable to discover new devices and returned the message "Error found on device 10.60.1.202 (UID: 0): Retrieved  records instead of  from query [SELECT collect_device_certs FROM object_view WHERE uid = 1]". This issue is resolved, and Enterprise Manager now properly discovers new devices after an upgrade.|
|ID 375280||Enterprise Manager now displays managed LTM virtual server devices, even if they do not have an associated LTM pool.|
|ID 375358||Enterprise Manager no longer returns a duplicate entry error when nodes are renamed on the BIG-IP system.|
|ID 376122||Enterprise Manager no longer displays a Cannot find floating self IP message in the device properties screens for a discovered BIG-IP high availability pair.|
|ID 376474, 375942||Previously, when managing BIG-IP devices with similar mirroring configurations, Enterprise Manager sometimes displayed the message Multiple Peers on the device properties screen, even though the device had only one peer. This issue is fixed, and you should no longer see this message.|
|ID 376635, 376459||Previously, the Flapping LTM Node report occasionally timed out when processing a report for a large configuration. This issue is resolved and the report no longer times out.|
|ID 376649, 376426||Previously, if a managed device contained a certificate with a large number of characters for certain fields, Enterprise Manager did not properly refresh the device information and instead, returned an error message. This issue is resolved. Enterprise Manager now properly updates the configuration for those devices.|
|ID 376805||Starting in Enterprise Manager version 3.0.0, all user roles (Administrator, Operator, and Application Editor) can issue tmsh list commands.|
|ID 377386||Enterprise Manager no longer displays a General Error when viewing the device list the first time after performing a reboot.|
|ID 377580||Previously, when using certain versions of Microsoft Internet Explorer, you were not able to access the Enterprise Manager user interface after disabling statistics. This issue is resolved.|
|ID 377919||The emDeviceClockSkew SNMP notification no longer returns extra characters in the object definition.|
|ID 378107, 378173||Device archives no longer display a null time stamp (0000-00-00 00:00:00) after upgrading Enterprise Manager.|
|ID 378325||Enterprise Manager now cleans invalid threshold entries when a device's IP address changes. This eliminates any orphaned entries in the database.|
|ID 378701||You can now successfully trace the mysql (mysqld) process.|
|ID 379315||Previously, after re-licensing a BIG-IP system for unlimited SSL transactions, the SSL TPS utilization graph displayed as Reconfiguring. This issue is resolved.|
|ID 379316||Managed devices licensed for unlimited SSL transactions now properly display SSL TPS utilization.|
|ID 379511||Enterprise Manager can now import and display SSL Certificates, which you can use to configure LDAP and Active Directory authentication.|
|ID 379600||A vulnerability resulting from an SSH misconfiguration on certain platforms has been resolved (CVE-2012-1493).|
|ID 381808||Previously, if an SSL proxy address was configured, Enterprise Manager returned the following error message during a licensing task: Internet Proxy - FAILED to contact license server: Hostname 'activate.F5.com. This issue is resolved. Now, Enterprise Manager properly uses the specified SSL proxy address for the licensing task. You configure an SSL proxy address from the Servers Options screen accessed by clicking Enterprise Management > Options > Servers.|
|ID 383777, 383778||Previously, Enterprise Manager was incorrectly identifying a boot location change when refreshing a multi-blade VIPRION system. This issue is resolved.|
|ID 388128||This release includes an updated version of BIND to address vulnerability CVE-2012-1667.|
|ID 369594||You cannot rename a custom list after you create and save it.||To work around this issue, re-create the custom list by re-selecting the devices from the device list, save the list with the preferred name, and delete the old list.|
|ID 372331||You cannot use both the SSL Proxy and the iControl Proxy simultaneously to manage devices. If you enable both iControl Proxy and SSL Proxy for a managed device, the device will be unreachable.||Enable only the SSL Proxy or the iControl Proxy.|
|ID 376211||In rare instances, you may encounter a failure during an upgrade from Enterprise Manager version 2.x to version 3.0.||If you encounter a failure during an upgrade task, perform the software installation task again.|
|ID 379287||When you use Enterprise Manager to reboot a VIPRION system that has no route from its blade-specific management IP address, the blade reboots as expected, but the reboot task never displays as finished.|
|ID 381167||When using iControl, Enterprise Manager returns a 502 Bad Gateway error. The iControl proxy is not supported for IPv6.||Use an IPv4 self IP address for iControl.|
|ID 381799||If statistics collection is enabled, but the statistics profile you are using does not have all of the metrics selected for collection, the database calculation incorrectly includes the unselected metrics, and allocates space for them. Therefore, the Estimated Statistic Storage Capacity With Current Settings value (located on the Data Storage Options screen for Statistics) displays a number lower than it should. This difference in value is marginal.||If necessary, you can perform your own calculations to get the correct Estimated Statistic Storage Capacity With Current Settings value by taking multiple measurements of this number over the course of two days. View the disk space currently used by the statistics database by clicking System > File System Management > View > Local Statistics Database twice in 24 hours. For example: Disk space used for statistics database: 1GB Disk space used for statistics database: 2GB (24 hours later) Allocated Space for statistics database: 5GB These measurements show that 1GB per day is being used. With 5GB allocated, the storage capacity is 5 days.|
|ID 382231||Currently, the remote statistics database does not support IPv6.||If you want to use a remote database to store statistics, you must use IPv4.|
|ID 383178||Setting the device refresh interval value to less than 60 minutes can prevent threshold alerts from triggering and cause issues displaying statistics graphs.||To avoid this issue, set the refresh interval to 60 minutes (default) or longer.|
|ID 384028||Enterprise Manager might prompt you for a password when you run the qkview utility from the command line.|
|ID 384164||In some cases, configured reports are not emailed as expected.||To work around this issue and receive emailed reports, from the command line, type the following bigstart restart emrptschedd .|
|ID 384161||Configuring Enterprise Manager Virtual Edition (VE) version 3.0.0 in a high availability pair may result in the standby device initiating the ConfigSync process every three minutes.||Configure Enterprise Manager in a high availability pair only when upgrading from version 2.3 to version 3.0, or for physical hardware running version 3.0.0. Do not configure Enterprise Manager version 3.0.0 VE in a high availability pair.|
|ID 384478||When Enterprise Manager is configured in a high availability pair, reports may show a spike in some metrics after configurations are synchronized between the Enterprise Manager systems.|
|ID 388512||If you upgrade to Enterprise Manager version 3.0.0 from version 2.3.0 after importing a BIG-IP version 11.2.0 image, some BIG-IP platforms (1600, 3600, 6900, and 8900) may be listed as unsupported in the install software wizard.||To work around this issue, delete the BIG-IP version 11.2.0 image from Enterprise Manager, and re-import it.|
|ID 388828||When discovering or refreshing a device running BIG-IP LTM version 9.4.x, Enterprise Manager may log (in its /var/log/em file) an iControl exception Unknown method: get_all_software_status.||This message is benign; you can ignore it.|
|ID 389040||After running the bigstart restart command, Enterprise Manager may log messages in the /var/log/em file indicating that MCP is not available.||You can ignore these messages, they are a consequence of the services restarting, and do not indicate a problem on the device.|
|ID 391671||If you delete all but the active boot location from a managed device, Enterprise Manager can no longer install software on that device.||To resolve this issue, you must log on directly to the managed device and create an additional boot location. After you create the additional boot location, you can resume software management from Enterprise Manager. Note: For devices running version 11.x, creating an additional boot location requires that you download and install a software image.|
|ID 405736||Alerts for device configuration synchronization may not function as expected for managed BIG-IP devices running version 11.x.||To verify the configuration synchronization status, log on to the managed device and view the Device Group properties screen for version 11.x-11.2.0 or the Overview screen for version 11.2.1 and later.|
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 on 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.