Applies To:

Show Versions Show Versions

Release Note: Enterprise Manager version 1.0.0
Release Note

Original Publication Date: 03/01/2007

Summary:

This release note documents the 1.0 version feature release of the Enterprise Manager. To review the features introduced in this release, see New features and fixes in this release.

For information about installing the software, please refer to Installing the software.

Contents:

- User documentation for this release
- Supported browsers
- Supported platforms
- Supported F5 systems
- Installing the software
- New features in this release
- Known issues
- Workarounds for known issues
     - Deleting core dump files (CR57791)


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, http://tech.f5.com.

[ Top ]


Supported browsers

The supported browsers for the Enterprise Manager web interface are:

  • Microsoft® Internet Explorer®, version 6.0 and later.
  • Netscape Navigator®, version 7.1 and later, and other browsers built on the same engine, such as Mozilla, Firefox, and Camino.
[ Top ]

Supported platforms

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

  • Enterprise Manager 500

[ Top ]


Supported F5 systems

The Enterprise Manager 1.0 system can discover and manage certain F5 systems in your enterprise network. This release is compatible with the following F5 system:

  • BIG-IP systems version 9.1.1 or later.
[ Top ]

Installing the software

The Enterprise Manager version 1.0 was shipped to you installed on the Enterprise Manager 500 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 http://tech.f5.com.

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

[ Top ]

New features in this release

This release includes the following new features.

Device discovery
Enterprise Manager can automatically discover F5 Networks devices in the network, and automatically add them to a central device list, where you can perform a variety of remote device management tasks.

Software image management
You can use Enterprise Manager to store multiple software or hotfix images, and deploy them to one or more managed devices in the network.

Archive and restore device configurations
Enterprise Manager can archive and store multiple device configurations, allowing you to regularly back up stable device configurations for use in system restore situations.

Configure custom alerts
In order to monitor certain management tasks in the network, you can configure custom alerts to notify of certain network management events.

Certificate monitoring
You can use Enterprise Manager to view certificates and expiration dates on all managed devices. You can combine this with the custom alerting feature to notify users in the network of certificate expirations.

[ Top ]
 

Known issues

The following items are known issues in the current release.

Devices that Enterprise Manager cannot contact during discovery do not appear in the results list (CR53581, CR54996)
When you start a device discovery task, Enterprise Manager scans a subnet or an addresses that you specify. If a Enterprise Manager cannot contact a device within the address range you specify, this device does not appear in the discovery results list, and the list does not correctly indicate how many devices were contacted.

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.

The Cancel Pending Items button appears available even if it is not (CR54060)
When you start a software upgrade task with multiple jobs, you can cancel jobs that have not yet started by clicking the Cancel Pending Items button. However, when the last job starts, the Cancel Pending Items button remains available even though you cannot cancel a job at this point.

Status filtering and column sorting do not work together (CR54628)
On object list tables, if you click a Column Filter button at the top of a column to filter the list, the list changes to display only those items you selected from the filter list. However, if you then attempt to sort the table by clicking a column heading, the filter resets and displays all records, including those you previously filtered out of the table display.

EM Maintenance Task message appears in the task list when a managed device is rebooting (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. However, on the Task List screen, a device reboot results in an EM Maintenance Task message appearing in the task list.

The system does not change the mouse cursor to indicate that the system is busy when refreshing a device (CR55043)
If you refresh a device on the device list screen by clicking the Update Status button, the cursor does not change to an hourglass to indicate that a task is running. To check on the status of a refresh task, look at the text at the top of the screen.

The 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.

Certificate expiration dates may not appear accurately due to time zone discrepancies (CR55157)
Depending on the time zone that you are in, the certificate expiration dates reported on certificate list screens may be inaccurate, due to complexities in time related calculations involving daylight saving time. This discrepancy should not affect custom alerts you configure for certificate expirations because these alerts are based on days and not hours or minutes.

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.

Changing a managed device host name or re-authenticating the device may result in missing information on task properties screen (CR55552)
While viewing a device properties screen, if that device's host name changes, or if a user re-authenticates the device with the Enterprise Manager system, then the device properties information may not appear correctly, even if you refresh the screen. To see the new host name information, open the Device List screen, then click the device name to re-open the device properties screen.

Navigation buttons are disabled for guest users (CR55766)
If you log on to the Enterprise Manager system as a guest-level user, certain navigational buttons, such as the Back button on Certificate Properties or Task Properties screen are disabled. To navigate as a Guest user, you can use options on the navigation pane and menu bars.

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.

Device refresh can result in a device lock (CR56461)
If you initiate a device refresh on one or more devices, the Select boxes adjacent to these devices on the device list screen become unavailable until the refresh task completes.

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.

Enterprise Manager does not prevent users from selecting corrupt hotfixes and software to managed devices (CR56622)
When configuring a software upgrade or hotfix installation task, Enterprise Manager permits a user to select an image that is corrupt. Although the system prevents a user from installing corrupt software, a user cannot determine which software is corrupt from the software or hotfix installation wizard. To prevent this scenario, ensure that you check the integrity of the software on the Software or Hotfix list screens, and remove any corrupt images prior to starting a software or hotfix installation. See the workaround for instructions on how to find and remove corrupt software.

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.

BIG-IP Global Traffic Manager archives do not work properly with Enterprise Manager (CR56783)
Although the wideip.conf configuration archive files contain much of the same information of a .ucs configuration archive files, Enterprise Manager is not compatible with the sync groups utilized by GTM systems. Because of the way sync groups automatically maintain the configurations of GTM systems, they may overwrite archives that you restore using Enterprise Manager.

The 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.

Deleting an Enterprise Manager system user account or SNMP trap destination restarts system processes (CR57791)
If you delete an object such as an SNMP destination or user account, this removes the entry from the database. However, these actions cause the Enterprise Manager system processes to restart, and result in core dumps appearing in the /shared/core directory on the Enterprise Manager system. We recommend that you avoid deleting users or SNMP trap destinations while other tasks are running because these tasks will be interrupted when a system process restarts. See the workaround for instructions on how to remove core dump files after deleting an SNMP destination or user account.


Workarounds for known issues

The following sections describe 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 pair.

  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.

Removing corrupt software images (CR56622)

This workaround describes how to remove corrupt software images from the software list.

  1. On the Main tab of the navigation pane, expand Enterprise Management and click Software.
    The Software Images screen opens.

  2. Click the Column Filter button in the Image Status list.
    A menu appears below the Image Status column heading.

  3. From the Column Filter menu, select Corrupt.
    The table changes to display only software images that are corrupt.

  4. Make a note of any corrupt software so that you have a list of software that you need to re-import.

  5. Check the Select box next to each corrupt software image.

  6. Below the list, click Delete.

Note: If you need to remove corrupt hotfix images, then after step 1, on the menu bar click Hotfixes to open the Hotfix Images screen.

Deleting core dump files (CR57791)

This workaround describes how to delete core dump files that appear after you delete a user account or SNMP trap destination.

  1. Log on to the command console of the Enterprise Manager system.

  2. Navigate to the /shared/core directory and type ls at the command prompt to check if any core files exist.

  3. In the Configuration utility, delete the users or SNMP trap destination.

  4. In the /shared/core directory, type the following command to delete all core dump files:
    rm -f *.core.*
[ 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)