Applies To:

Show Versions Show Versions

Release Note: Enterprise Manager version 1.2.2
Release Note

Original Publication Date: 03/01/2007


This release note documents the version 1.2.2 maintenance release of the Enterprise Manager. We recommend this maintenance release only for those customers who want the fixes and enhancements listed in Fixes and enhancements in this release.

This maintenance release is cumulative, and includes all fixes and enhancements released since version 1.2. You can apply the software upgrade to versions 1.0, 1.2, or 1.2.1. For information about installing the software, please refer to Installing the software.


- User documentation for this release
- Supported browsers
- Supported platforms
- Installing the software
     - Setting up a new system
     - Upgrading an existing system
- Fixes and enhancements in this release
- Fixes in prior releases
- Known issues
- Workarounds for known issues

User documentation for this release

In addition to these release notes, the following user documentation is available for this release.

You can find the user guides and the solutions database on the AskF5 Technical Support web site,

Supported browsers

The supported browsers for the Enterprise Manager web interface are:

  • Microsoft® Internet Explorer®, version 6.x.
  • Mozilla® Firefox®, version 1.5x.
[ Top ]

Supported platforms

The 1.2.2 release applies only to the supported platforms listed below; each one provides all minimum system requirements. This release supports the following platforms:

  • Enterprise Manager 500
  • Enterprise Manager 3000
[ Top ]

Installing the software

If you are using a new Enterprise Manager system, the current software is loaded and configured. See Setting up a new system to get started using Enterprise Manager. If you are upgrading an existing Enterprise Manager system, see Upgrading an existing system for instructions on how to download and install Enterprise Manager version 1.2.2.

Setting up a new system

The Enterprise Manager version 1.2.2 was shipped to you installed on the Enterprise Manager 500 or Enterprise Manager 3000 platform. You only need to set up the system in your network, license the system, and connect it to one or more devices that you want to manage.

The Enterprise Manager Quick Start Instructions, which is included with the hardware platform, provides basic instructions for a quick set up and initial configuration of the Enterprise Manager system.

For a more detailed explanation of networking options and setup instructions, see chapter 2, Installation and Setup, and chapter 3, Licensing and Configuring the System in the Enterprise Manager Administrator Guide available at

Important: After you complete the licensing process, you must reboot the Enterprise Manager system in order for the user interface to function properly.

Upgrading an existing system

If you have an existing Enterprise Manager system, you can use the F5 Electronic Software Distribution site to download a new software image. Then, you can use the Enterprise Manager software upgrade wizard to upgrade your Enterprise Manager system. You can upgrade Enterprise Manager version 1.0, 1.2, or 1.2.1, to version 1.2.2.

To download the upgrade

To download the software upgrade, you must create an account at This site uses an F5 single sign-on account for technical support and downloads. After you create an account, you can log on and download the Enterprise Manager 1.2.2 software.

  1. Using a web browser connected to the internet, visit
    The F5 Sign-on screen opens.

  2. In the User Email box, type the email address associated with your F5 technical support account.

  3. In the Password box, type the password.

  4. Click the Login button.
    The Overview screen opens and provides notes about using the Downloads site.

  5. Click the Find a Download button.
    The Product Lines screen opens listing all F5 product families.

  6. Locate the Enterprise Manager product family and click the adjacent Enterprise Manager v1.x link.
    The Product Version screen opens, listing the available download containers for the current product version.

  7. Click the release link for version 1.2.2.
    The End User License Agreement screen opens.

  8. Read the license agreement, and click I Accept to agree to the terms of the agreement.
    The Select a Download screen opens.

  9. Click the EM- link to begin downloading the md5 checksum to your local system.
    The Select Download Method screen opens.

  10. Click an option depending on the method you want to use to download the file.

  11. Click the back button on the browser to return to the Select a Download screen.

  12. Click the EM- link to begin downloading the software image to your local system.
    The Select Download Method screen opens.

  13. Click an option depending on the method you want to use to download the file.

To install the upgrade

  1. Using a web browser connected to the same network as the Enterprise Manager system, visit https://<em_address>, where <em_address> is the IP address that you use to log onto the Enterprise Manager web interface.

  2. Sign on to Enterprise Manager as an administrator-level user.

  3. On the navigation pane, expand Enterprise Manager and click Software Images.
    The Software Images screen opens.

  4. Click the Import button.
    The New Image screen opens.

  5. For the File Name setting, click Browse.
    A dialog box opens.

  6. Using the dialog box, browse to the location where you downloaded the EM- file in step 12 of the previous section.

  7. Using the dialog box, click the EM- file name to select it, then click Open.
    The dialog box closes, and a path name appears in the File Name box.

  8. Click Import.
    The Import Progress box indicates the progress toward completing the software import.

  9. When the software import task finishes, click Finished.
    The Software Images screen opens.

  10. In the software image list, click EM v1.2.2.
    The general properties screen opens, displaying details about the software image.

  11. Click Install to start the Software Installation Wizard.

For further instructions on using the Software Installation Wizard, see Chapter 7, Managing Software Images in the Enterprise Manager Administrator Guide available at

[ Top ]

Fixes and enhancements in this release

The 1.2.2 release includes the following fixes and enhancements.

Non-descriptive error message appears when an unauthorized user attempts an upgrade (CR64224, CR69820)
If you log on to Enterprise Manager as a user who does not have administrator rights on a particular managed device, and then attempt to upgrade that device's software, you receive an error message. Previously, the message did not explain that the error resulted from the user having insufficient rights to upgrade the managed device. The new error message is more descriptive and provides steps to take to avoid this error.

External user authentication requires additional steps during configuration (CR67846)
Previously, if you used RADIUS authentication for external users, you needed to perform additional steps to correctly specify a user's roles. You can now use RADIUS authentication with Enterprise Manager without needing to perform additional steps.

Removing device groups from rotating archive schedule not permitted from the Devices: Archives screen (CR68691, CR69811)
On the Devices: Archives screen, the Rotating Archive Schedule table lists the rotating archives that are directly assigned to this device, and the rotating archives that are assigned to the device through a device group. Using the Select boxes, you can remove the current device from a rotating archive schedule. Previously you could not remove a device group from the rotating archive by checking a Select box. We corrected this issue so that you can delete a configuration archive associated with a device group from the Devices: Archives screen.

Change User Password feature does not support mixed case user names (CR68749, CR69824)
You can use the Change User Password feature to change a user's password on multiple managed devices. Previously, if the user name featured mixed case (UserName) instead of a single case (username), the Change User Password task for that user failed. We corrected this issue so that you can use user names with mixed case.

Errors in scheduled and custom configuration archives when upgrading Enterprise Manager (CR69409, CR69546)
We fixed issues related to custom configuration archives and upgrading Enterprise Manager. Previously, when you upgraded Enterprise Manager from version 1.0 to version 1.2, configuration archive schedules that you previously configured quit working upon upgrade. Additionally, if you configured any custom configuration archive schedules on a version 1.0 system, you could not successfully copy the UCS file to the upgraded version 1.2 system. These errors occurred because we enhanced the management options for configuration archive schedules in Enterprise Manager 1.2.

Command line upgrade of Enterprise Manager causes errors (CR69416, CR70671)
The new release fixes an issue where the upgraded version 1.2.x system could not use the UCS file from the version 1.0 system. This error caused the upgrade to fail. With version 1.2.1, you can upgrade Enterprise Manager through the command line without encountering UCS errors.

Open SSL vulnerable to a forged RSA signature (CR69465, CR69825, CR70155)
We included a new OpenSSL package in version 1.2.1 to fix the forged RSA signature vulnerability described in CVE-2006-4339.

Enterprise Manager upgrade retains pending status when other upgrade tasks exist (CR69534)
Previously, if you used Enterprise Manager to perform a self-upgrade from version 1.0 to version 1.2, the task would not start if other upgrade tasks existed, even if the tasks were marked complete. By design, Enterprise Manager cannot start a self-upgrade process if other upgrades are running. In certain cases, some tasks were marked complete on the task list when they were not actually complete.

Local user accounts not transferred correctly after upgrading to version 1.2 (CR69637)
We corrected an issue where local Enterprise Manager user accounts were not properly carried over to the new system after upgrading Enterprise Manager from 1.0 to 1.2. When you upgrade Enterprise Manager, you no longer need to redefine local user accounts.

Enterprise Manager Administrator Guide incorrectly states managed device compatibility (CR69842)
Previously, in chapter 1 of the Enterprise Manager Administrator Guide, we incorrectly indicated that Enterprise Manager can manage BIG-IP version 9.1.2 and later. In fact, Enterprise Manager can manage BIG-IP version 9.1.1 and later. We updated the Administrator Guide to correctly indicate managed device support.

Cannot upgrade compact flash-only devices managed through self IP address (CR69845)
If you use Enterprise Manager to manage any compact flash-only devices (1000, 2400, and 5100 platforms), and you manage these devices through a self IP address configured on a TMM switch interface instead of through the management interface, you cannot upgrade these managed devices. This occurs because the managed devices do not recognize self IP addresses during the upgrade process, and therefore cannot connect to Enterprise Manager to complete the upgrade. To use Enterprise Manager to upgrade compact flash-only devices, you must manage the devices through the management interface on each managed device. Previously, Enterprise Manager indicated that you could upgrade these devices, even through a TMM switch interface. Now, Enterprise Manager does not include these devices in the list of devices compatible with an upgrade.

Enterprise Manager does not support certificate names that differ in case only (CR69945)
Previously, Enterprise Manager did not differentiate between certificate names that differed only in case. Enterprise Manager now supports certificate names that differ in case only. For example, you can now use both DEFAULT.crt and default.crt. as unique certificate names.

Communication failed error message does not indicate clock skew problem (CR69984, CR70647)
Previously, if there was a difference in system clocks between Enterprise Manager and a managed device, you could receive an error indicating communication failed during tasks such as device discovery. This error did not adequately indicate the nature of the communication problems between the devices. Now, if there is clock skew between Enterprise Manager and a managed device, the error indicates this problem so that you can take steps to synchronize system clocks.

SNMP agent does not support multiple sources per community (CR71411, CR71412, CR71413)
We updated the Enterprise Manager MIB to address SNMP issues. Enterprise Manager now supports sending multiple SNMP traps for the same community string. Additionally, we updated support for alerts specific to the Enterprise Manager 3000 platform.

System services continually restart on an unlicensed partition (CR71799)
Previously, if you installed a version of Enterprise Manager onto an unlicensed boot location, the system services such as emdeviced, swimd, emfiled, discoveryd, emreportd, and emalertd would continually restart, and affect the performance of the system on a licensed partition. This no longer occurs if you install to an unlicensed boot location.

iControl communication issues may affect licensing (CR71959, CR73156)
Previously, errors could occur during within iControl that could cause license dossier or other errors on the Enterprise Manager system. The iControl licensing communications now work without errors.

Remote user automatically created during upgrade task (CR72810)
Previously, if you performed a self-upgrade of an Enterprise Manager system while using remote authentication, the process could create a new user on the Enterprise Manager device. This new user was a temporary user employed by the system during an authentication task to guard against losing communication with managed devices if an error occurred during the upgrade. Now, the system ensures that any temporary users created are deleted once the upgrade process completes.

Re-licensing Enterprise Manager may be required for successful upgrade (CR72922)
We corrected an issue with the license check date that could cause a range of errors during upgrade. Previously, if you originally generated an Enterprise Manager product license on a date prior to October 2, 2006, then upgraded to version 1.2.1 or later, the Web interface indicated that you must activate the license. Also, the console also indicated that the current license was invalid, and displayed status messages indicating that system services were restarting. Additionally, if you attempted to upgrade to version 1.2.1 or later from the command line, the installer displayed a licensing error and stopped.

Determining disk space availability for upgrades if managed device does not support iControl call (CR72959, CR73275)
Previously, if a managed device did not support direct communication to test for available disk space to install a software or hotfix upgrade, Enterprise Manager started the upgrade anyway. Now, Enterprise Manager tests for available disk space for all managed devices prior to starting a software or hotfix upgrade task, and warns if there is not enough disk space to perform an upgrade.

Non-SCCP devices hang after hotfix install (CR73104)
Previously, if you used Enterprise Manager to install a hotfix on a system without a Switch Card Control Processor (SCCP), the hotfix process caused the non-SCCP device (such as systems that contain Compact Flash cards) to hang after installation. This problem resulted when Enterprise Manager created the /.sccp_hard_reboot file on the managed device. Now, Enterprise Manager correctly identifies SCCP and non-SCCP devices during the hotfix install task.

Changeset wizard does not immediately indicate when all objects of a class are deleted (CR73129)
Previously, if you deleted all the objects of a certain class (for example, pools) on a managed device, this information was not immediately visible in the Enterprise Manager Changeset wizard. Now, when you delete all objects of a certain class, the class name is removed from the Changeset wizard after a device refresh, ensuring that you do not add an empty class definition to a changeset.

Devices that cannot communicate back to Enterprise Manager flagged (CR73257)
Enterprise Manager can discover devices in the network that do not have a direct connection back to Enterprise Manager. This situation can occur through the use of NATs or because of configurations that send communications from a managed device to Enterprise Manager through a route other than the default management route. Now, during the discovery process, Enterprise Manager tests for a direct route from a BIG-IP version 9.4 or later managed device to Enterprise Manager, and warns if the configuration does not provide a direct connection to the Enterprise Manager system. The device list now notes which devices do not have a direct connection back to Enterprise Manager. These flagged devices are not compatible with upgrade tasks that you can configure in Enterprise Manager. To use Enterprise Manager to upgrade these devices, you must ensure that there is a direct route between a managed device and Enterprise Manager.

Compact flash-only devices not managed through the management interface flagged (CR73259)
Enterprise Manager can discover compact-flash only devices managed through TMM switch interfaces. Because these interfaces cannot function during an Enterprise Manager-initiated upgrade task, Enterprise Manager now flags these compact-flash only devices in the device list and on the device properties screen. These flagged devices are not compatible with upgrade tasks that you can configure in Enterprise Manager. To use Enterprise Manager to upgrade these devices, you must manage the devices through each device's management interface.

Time zone may be inaccurate after managed device upgrade (CR73272)
Previously, if you upgraded a managed device from BIG-IP version 9.1.1 to 9.1.2, or from BIG-IP version 9.1.1 to 9.2.4, and the device had a time zone setting other than Pacific Standard Time (PST), the time zone setting reverted to PST upon upgrade. Now, when you use Enterprise Manager to upgrade managed devices, Enterprise Manager maintains the correct time zone settings on managed devices.

Users can change Enterprise Manager address to an invalid address on device property screen (CR73601)
In previous version, users could arbitrarily change the address that a managed device uses to communicate with Enterprise Manager (from the device's general properties screen). Users can still make changes to the address, but Enterprise Manager now checks to confirm that any changes to the Enterprise Manager address are valid.

Unnecessary partition information added to Enterprise Manager database (CR73702)
Previously, Enterprise Manager version 1.2.0 created an entry in its database for an additional Common administrative partition each time it refreshed certain managed devices running BIG-IP software earlier than version 9.4. Although Enterprise Manager did not actually create new partitions on these managed devices, the additional entries in the database would cause Enterprise Manager to take too long to refresh the device information, and could result in an automatic reboot of the managed device. This was an issue only on BIG-IP systems that did not support administrative partitions. BIG-IP version 9.4.0 is the earliest version that supports administrative partitions. This version of Enterprise Manager fixes this issue and removes any extraneous partition information from the Enterprise Manager database to alleviate the symptoms caused by this issue.

[ Top ]

Fixes in prior releases

The current release includes the fixes and enhancements that were distributed in prior releases, as listed below. (Prior releases are listed with the most recent first.)

Version 1.2

The 1.2 release included the following fixes.

EM Maintenance Task message in the task list when a managed device reboots (CR55042)
When a software upgrade task completes, a managed device reboots. On the task details screen for the upgrade task, Enterprise Manager correctly indicates that a device is rebooting. Previously, a device reboot resulted in an EM Maintenance Task message appearing in the task list. This message no longer appears in the task list when a device reboots.

Certificate expiration dates affected by time zone discrepancies (CR55157)
Previously, the certificate expiration dates reported on certificate list screens might have been inaccurate, due to complexities in time related calculations involving daylight saving time. Daylight saving time no longer affects time zone calculations when checking certificate expiration dates.

BIOS warning message no longer appears during startup (CR57741)
Previously, a benign BIOS warning message Award Preboot Agent Installation Failed appeared when you initially powered up the system. We corrected the BIOS so that this message no longer appears.

Progress indicator for software image imports may be inaccurate (CR59085)
Previously, when the system imported a software image, the progress bar occasionally continued to indicate 0% progress. When this occurred, you needed to cancel the process and re-import the software image.

Downgrading managed device may prevent browser access to the device through Enterprise Manager (CR60512)
Previously, ff you used Enterprise Manager to install an earlier software version on a managed device, and then attempted to open that device's Configuration utility using the Launch link on the device properties screen, the web browser could not connect to the device. The Launch link now works with devices on which you installed an earlier software version.

Internet Explorer Security window bypassed when downloading device export data (CR64842)
We corrected an issue where if you attempt to download device export data in CSV format, you must manually permit the browser to download the CSV file to your local system. When using Internet Explorer version 6.x, if you opt not to download the file when you receive the Security Alert window, the Enterprise Manager system sends the file to your local system anyway. The system now adheres to browser security warnings.

System can exceed the maximum pinned archives setting in a deploy changeset task (CR65109)
When you deploy a changeset, you can choose to create a rollback UCS archive for target systems. Previously, Enterprise Manager saved UCS archives created during a changeset deploy task as pinned archives, which previously could exceed the limits you set on pinned archives on the Rotating Archives Options screen. The system now saves UCS archives as rotating archives during a deploy task.

Enterprise Manager 3000 system rebuilds the RAID configuration after an unclean shutdown (CR65451)
Previously, if an Enterprise Manager 3000 system completely lost power or was otherwise abruptly restarted (as opposed to a normal, clean system restart), the RAID controller rebuilt the RAID array when the system is booted up next. An abrupt shutdown no longer starts the RAID rebuild process.

Back button quits working after UCS restore (CR65464)
Previously, if you used Enterprise Manager to restore a UCS archive to a single device, the Back button on the device properties screen no longer opened the device list screen. The Back button now functions properly after a UCS archive restore.

Two or more unique sets of managed device pairs cannot share the same IP address (CR67607)
Although Enterprise Manager can manage redundant systems, it previously could not properly manage two unique redundant systems if these pairs use the same IP address for peer communication. To manage redundant systems with Enterprise Manager version 1.2, you must ensure that each redundant system uses a unique IP address for peer communication. The version 1.2.1 upgrade fixes this issue.

Command line upgrade of Enterprise Manager causes errors (CR69416)
We updated the Enterprise Manager version 1.2 release image to EM- The new release fixes an issue where the upgraded version 1.2 system could not use the UCS file from the version 1.0 system. This error caused the upgrade to fail. If you want to upgrade an Enterprise Manager system to version 1.2, ensure that you download the latest version from Enterprise Manager 1.2.1 also fixes this issue.

[ Top ]

Known issues

The following items are known issues in the current release. Known issues are cumulative, and include all known issues for a release.

Hourglass cursor does not always appear when system is busy (CR55043, CR64461)
Usually, the cursor on the web interface changes to an hourglass to indicate that the system is busy. This may not always occur on certain screens. See the status banner at the top of the screen to determine the state of system activity.

Managing externally authenticated devices requires additional steps (CR62513)
If managed devices in your network use an external authentication protocol (RADIUS, LDAP, or Active Directory), you must follow certain rules when discovering and managing these devices. If you use an external user name for device discovery, this user must exist on the managed device. Once you discover this device, you can manage this device by logging on as admin to Enterprise Manager. If you log on to Enterprise Manager with any other user name, you must ensure that this user name exists on the managed device (in the external authentication user list) in order to avoid authentication errors. This is currently an issue only with BIG-IP versions 9.1.1, 9.2.0, 9.2.2, 9.2.3. To fix the issue, you can apply hotfix HF68471 to version 9.2.3 managed devices, or upgrade managed devices to version 9.2.4.

Changeset modification options are limited (CR66262)
If you open the changeset properties screen, and then make changes to the changeset, you must save the changeset before verifying your changes. If the verification subsequently fails, you cannot revert to the previously valid changeset. Because of this limitation, we recommend that you create a duplicate of a valid changeset before you modify it. Additionally, because no Cancel button exists on the changeset properties screen, if you want to cancel changes from the changeset properties screen, you must open the changeset list by clicking Changesets in the navigation pane.

The Deploy Device Configuration wizard causes an error if you return to Step 1 of the wizard (CR66887)
If you use the Deploy Device Configuration wizard to configure a deploy task using a device configuration that you specify in the wizard, then return to the Step 1 wizard screen to view or change the source, the Changeset Text screen appears instead of the Device Configuration Source screen. Because you cannot edit the changeset text, you must re-configure the task. To avoid this error, do not use the Back button to return to the Step 1 wizard screen after you have configured object class and object instance data for the deploy task.

Communications interval with managed devices changed after upgrade (CR67510)
When you upgrade Enterprise Manager from version 1.0 to 1.2, the default refresh interval that controls how often Enterprise Manager communicates with each managed device resets to the 60 minute default. After you upgrade, you may want to check or change the default refresh interval on the Device Options screen.

Upgrading Enterprise Manager resets remote authentication settings (CR67521)
If you upgrade Enterprise Manager from version 1.0 to version 1.2, the user authentication settings are reset. If you upgrade Enterprise Manager, ensure that you re-configure user authentication settings.

Audit logs are turned off by default (CR67610)
The Enterprise Manager Audit logs are disabled by default. To activate the audit logs, see the workaround for instructions on how to enable audit logging for the Enterprise Manager system.

Single sign-on for Launch Pad feature is only compatible with BIG-IP 9.4 or later or Enterprise Manager 1.2 or later (CR67769)
If you use the Launch link on the Launch Pad screen to open a managed device's Configuration utility, Enterprise Manager can use a single sign-on to automatically authenticate your user ID to managed devices running BIG-IP version 9.4 or later, or Enterprise Manager version 1.2. or later. If you use the Launch link to open managed devices running earlier software versions, you must re-enter your user name and password to open a managed device's Configuration utility.

Changeset with network route requires self IP addresses on target devices (CR67773)
Using the changeset feature, you can deploy device configuration data from one managed device to another. Although this configuration data can include network routing information, routes typically require that you configure self IP address in order to work properly. Enterprise Manager can successfully deploy a changeset with network routes to a target device only if the self IP addresses required by the network route already exist on the target device. Because self IP addresses are unique to each device, they are not usually deployed using a changeset. If you need to deploy a changeset with network route information, we recommend that you deploy VLANs to the target device, then manually configure the appropriate self IP addresses on the target device. Once you configure the self IP addresses, you can then deploy routes to the target device using changesets.

Reboot and Install locations can appear incorrectly on the Task Details screen (CR67833)
On the Task Review screen of the Software Upgrade Wizard you can select a different Boot Location or Install Location for devices in the upgrade task. However, if you select a new location for either setting, then click the View link to see the details for a device, the new settings do not appear on the Task Details screen. If you return to the Task Review screen, the settings you selected appear correctly.

Column sorting does not work properly on boot locations screen (CR68313)
On the Devices: Boot Locations screen, a table details the software version installed, the number of hotfixes installed, and the state of the boot location. However, if you click a column heading to sort the information, the system may not re-sort the information.

Install Log does not appear for a self upgrade task (CR68642)
When you use Enterprise Manager to perform an upgrade on itself, the Install Log (which normally displays entries logged on the managed device during the install task) appears empty on the Task Details screen for the Enterprise Manager upgrade task.

Rebooting a device displays a Pending in the Task List (CR68689)
If you use Enterprise Manager to reboot a device, the Device Reboot task appears in the Task List. However, in the Task List, the state of the task is Pending, even while the reboot is proceeding normally. Additionally, if you open the Task Details screen for this task, the Start Time, End Time, and Total Time fields display In Progress instead of the actual times.

Confirmation dialog box for rotating archive tasks is incorrect (CR68690)
If you attempt to remove a device group from a rotating archive schedule, a dialog box appears to confirm the action. Instead of referring to the device group, this dialog box refers to a device. If you click OK, the device group is removed from the rotating archive schedule.

Confirmation dialog box for deleting a hotfix is incorrect (CR68704)
If you attempt to remove a hotfix image from the hotfix repository, a dialog box appears to confirm the action. Instead of referring to the hotfix, this dialog box refers to a generic image. If you click OK, the hotfix you selected for deletion is removed from the hotfix repository.

Administrative partitions not supported by Enterprise Manager system (CR69024)
With this release, Enterprise Manager introduces support of administrative partitions. Administrative partitions are logical containers containing a defined set of BIG-IP system objects, and are used for access control purposes. We plan to introduce this feature in an upcoming BIG-IP system release. The access control features are compatible only with BIG-IP network object classes, and not Enterprise Manager object classes. Although you can create an administrative partition in Enterprise Manager, the access control properties are not available for Enterprise Manager object classes.

In an Enterprise Manager 3000 system power supply failure, the software does not correctly indicate which power supply failed (CR69241)
The Enterprise Manager 3000 platform features redundant power supplies. If one power supply fails, an audible alarm sounds. If you run the system_check -d or bp platform command from the command line, the failed power supply is not correctly identified. In a power supply failure scenario, the software always reports that power supply 2 is failing. To determine which power supply has failed, look at the power supply LED indicator on the rear of the Enterprise Manager device. If the green LED on a power supply is lit, this indicates that the power supply is working properly.

Uninstall packages for hotfixes conflict with hotfixes imported to the hotfix repository (CR71962)
If you import certain hotfixes for BIG-IP 9.1.2, these hotfixes may not appear in the hotfix list. Because you can import uninstall-hotfix packages to the hotfix repository in Enterprise Manager, this may corrupt the hotfix list. If you import an uninstall package for a hotfix, it replaces the original hotfix in the list. This is only an issue for five hotfixes: <hotfix names needed> for BIG-IP 9.1.2.

Upgrade status inaccurate when Enterprise Manager not connected directly to a managed device (CR72473)
If you use Enterprise Manager to discover and manage a device through a NAT or virtual server instead of directly through the device's management interface, this may affect the status report of an upgrade task for the device. When you upgrade a device through a NAT or virtual server, the upgrade status may appear to stall for a long time even though it is working properly.

Shell access not copied by Copy User Access wizard (CR73871)
When you use the Copy User Access wizard to copy user account permissions from a remotely-authenticated Enterprise Manager system to a BIG-IP system, the user access settings for shell access are not copied correctly. To correctly copy these settings, you must set this on the User Access settings screen on the managed device.

DNS resolution issues on managed device affects management communication (CR74910)
If the DNS settings on a managed device is configured to access an unavailable DNS server, this adversely affects communication between Enterprise Manager and a managed device due to DNS lookup timeouts on the managed device. Simple communication commands may time out and cause tasks such as device discovery or a device refresh to fail in Enterprise Manager. If you encounter unexpected time out warnings when performing management tasks, ensure that the DNS server specified in the managed device's DNS settings is accessible and functioning properly.

Incorrect peer IP configuration and discovery or refresh errors for redundant systems (CR75066)
When managing BIG-IP redundant systems, Enterprise Manager may not correctly discover or refresh a device in the redundant system if the managed device is incorrectly configured so that the peer IP address (primary or secondary) is actually a self IP address. If this occurs, a DaemonException error indicating a duplicate entry appears in the log file. If you encounter this error or cannot discover a device (or refresh information for a device) in a redundant system, ensure that the peer IP addresses on the managed devices are correctly configured.

Version 1.0 Known Issues

The following items are known issues in the version 1.0 release, and they still apply to the current release.

Setting the Alert History default record display to over 500 records may cause errors (CR53731)
When you set the alert defaults, if you set the alert history list to display over a maximum of 500 records, JavaScript errors may result (due to memory errors on the system where the browser is running) when you attempt to view the Alert History list. To avoid this error, on the Alert Options screen, set the Maximum History Entries value to 500 or less.

Device Address box on the Device Detail screen changes colors (CR55060)
On the Device Detail screen, the Device Address box that indicates the IP address may appear yellow or white if you view it using some Mozilla-based browsers. The color of the box does not affect the functionality, nor indicate any specific state.

Modifying devices that are currently involved in a running task may cause incorrect banner displays (CR55464)
When a device is involved in a task, Enterprise Manager locks the device to prevent a user from making changes to a device while it is being updated. If you attempt to make changes to this device, a status banner may appear and hide the device locked warning at the top of the screen. To restore the device locked warning, refresh the screen.

Back button may not work properly on the Device Boot Location screen (CR55860)
If you perform a device reboot from the Device Boot Location screen and then encounter an error, the Back button on the screen may quit working on Internet Explorer browsers. If you encounter this error, use the navigation pane to navigate back to the Device List screen.

Deleting a large list of devices takes a long time and provides no deletion status (CR56478)
When you delete several devices from the device list screen, the screen does not immediately refresh if one or more of the devices is unreachable. The system does not display any status messages while Enterprise Manager attempts to communicate with these devices. Although the system may appear unresponsive for a long time, you can navigate to other screens to perform management tasks.

Changing an Enterprise Manager system from a redundant pair to a single device forces a standby state (CR56543)
If you use the System Platform screen to configure the Enterprise Manager system as a redundant pair, then change the system back to a single device, the device changes to standby mode which prevents further configuration tasks. To correct this issue, reboot the device.

ConfigSync operations fail if there is a clock skew of over 600 seconds between peer systems (CR56619)
If the clock skew between the peer devices in a managed device pair is greater than 600 seconds, any ConfigSync operations initiated though Enterprise Manager fail. To prevent this ensure that the system clocks of the redundant pair are within 600 seconds of each other. See the workaround for instructions on how to check the system time on managed devices.

ConfigSync indicator in the top left corner of the screen may be inaccurate for Enterprise Manager redundant pairs (CR56666)
If you run a configuration synchronization on a pair of Enterprise Manager devices from the Device Properties screen, the ConfigSync status indicated in the top left of the screen does not update properly until you click an option on the navigation pane.

Task List screen may feature incorrect status reports for tasks running during an Enterprise Manager system reboot (CR56814)
If the Enterprise Manager system reboots during a software installation task, the task is cancelled, but the progress bar on the Task List screen may not properly reflect the cancelled status. Although the task is marked Finished, the status bar displays the percentage complete at the time of the Enterprise Manager reboot.

[ Top ]

Workarounds for known issues

The following section describes the workarounds for the corresponding known issues listed in the previous section.

Checking the system clock of a managed device pair (CR56619)

This workaround describes how to check the system clock of a device in a redundant system.

  1. Log on to the command console of the BIG-IP system.

  2. At the command prompt, type date and press Enter.
    The system clock information appears.

  3. Note the system clock information and repeat these steps on the device's peer.

Enabling audit logging for the Enterprise Manager system (CR67610)

This workaround describes how to enable audit logging on the Enterprise Manager system.

  1. Log on to the web interface of the Enterprise Manager system.

  2. In the navigation pane, expand System, and click Logs.
    The System Logs screen opens.

  3. On the menu bar, click Options.
    The Options screen opens.

  4. In the Audit Logging table, for the Audit setting, select Enable.

  5. Click Update.
    Audit logging is now enabled for the Enterprise Manager system. You can check the audit log by clicking Audit on the menu bar.

[ Top ]

Was this resource helpful in solving your issue?

NOTE: Please do not provide personal information.

Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)