Applies To:

Show Versions Show Versions

Manual Chapter: Enterprise Manager Overview
Manual Chapter
Table of Contents   |   Next Chapter >>

Overview of Enterprise Manager

Enterprise Manager™ is an appliance that helps you streamline the administrative tasks associated with managing multiple network devices. These administrative tasks include: performance monitoring, software installation and upgrades, configuration archival and restoration, certificate monitoring, security policy management, software image storage, and user account management. Enterprise Manager works in many types of network topologies, including those in multi-tiered configurations containing multiple firewalls.

You can use Enterprise Manager to manage networks with devices running the following software.

  • BIG-IP® system version 9.3 and later
  • BIG-IP® Local Traffic Manager™ Virtual Edition (VE) version 10.2 and later
  • BIG-IP® Secure Access Manager™ version 8.0 and later
  • WANJet® version 5.0 and later
  • Enterprise Manager™ version 1.0 and later
Note: Although Enterprise Manager works with previous software releases, we recommend that you upgrade your managed devices to the current software version to ensure optimal performance.

Additional resources and documentation for Enterprise Manager

You can access all of the following Enterprise Manager™ documentation from the AskF5™ Knowledge Base located at http://support.f5.com/. The procedures and examples described in all documentation and online help are written for administrator-level users with full access (non-restricted) privileges to Enterprise Manager.

Document Description
Enterprise Manager™ Getting Started Guide This guide provides you with the basic concepts and tasks required to set up your Enterprise Manager and start managing devices.
Enterprise Manager™: Monitoring Network Health and Activity This guide contains information to help use iHealth for diagnostics purposes, track certificates, create alerts for events, run reports, and manage statistics storage.
Enterprise Manager™ Administrator Guide This guide provides information about the basic concepts of device management,user management, as well as information specific to Application Security Manager policy management.
Platform Guide: Enterprise Manager™ 4000 These guides include Enterprise Manager system hardware platform specifications, installation instructions, and important environmental warnings.
Release notes Release notes contain information about the current software release, including a list of associated documentation, a summary of new features, enhancements, fixes, known issues and available workarounds, as well as installation and upgrade instructions.
Solutions and Tech Notes Solutions are responses and resolutions to known issues. Tech Notes provide additional configuration instructions and how-to information.

About incorporating Enterprise Manager into your network

You incorporate Enterprise Manager™ into your network as you would any F5 Networks device. However, because it requires bilateral communication with each device for successful management, Enterprise Manager must have open communication with your devices and be able to translate a device's IP address into an address it can use. The most common network configurations for address translation are:

Tiered network, BIG-IP® Local Traffic Manager™ performs address translation
Where a device manages load balances requests for multiple devices and translates the IP addresses for those devices through a firewall
Tiered network, a SNAT performs network translation
Where a device (located in front of Enterprise Manager) load balance requests for multiple devices, and a SNAT translates the IP addresses for those devices

Ports required for two-way communication

For Enterprise Manager to properly manage devices, the following ports are open by default to allow for the required two-way communication.

Open Port Purpose
443 For communication between managed devices and the Enterprise Manager system, for the purpose of device management.
4353 For communication between Enterprise Manager and a managed device's big3d agent, for the purpose of statistics collection.
3306 For communication between Enterprise Manager and a remote statistics database, for the purpose of storing and reporting statistics.

About best practices for management network topology

Device communication and management is performed through the following interfaces.

Traffic Management Microkernel (TMM) interfaces
For each of the following processes, you must dedicate a TMM interface to perform:
  • Application traffic and load balancing
  • Communication between Enterprise Manager and managed devices
  • Communication between systems in a high availability configuration (for both static and floating self IP address support)
Management (MGMT) interface
Used by F5 devices for administrative traffic and for the Always-On Management (AOM) subsystem, which enables you to manage a system remotely using SSH or serial console, even if the host is powered down. Devices do not forward user application traffic, such as traffic slated for load balancing, through this interface.
Tip: Place the Enterprise Manager system on a management subnet that is separate from traffic management to keep device management and communication independent from traffic management activities.
Illustration of example management network topology
Specifying the IP address of your DNS server
You must specify the IP address of your DNS server for communication to the F5® file servers and for SMTP email notification.
  1. On the Main tab, click System > Configuration > Device > DNS.
  2. In the DNS Lookup Server List area, in the Address field, type the IP address of your DNS server(s).
  3. Click the Add button.
  4. Click Update to save the changes.
Verifying DNS resolution
After you specify the IP address of your DNS server, you can verify that the address properly resolves.
  1. Log in to the command line as root.
  2. Type the dig <domain> command. For example, to query MX and siterequest.com, you would type dig siterequest.com mx. The result to this query should appear similar to this example, indicating that Enterprise Manager™ is able to resolve the email exchanger. ; << >> DiG 9.2.2 << >> siterequest.com mx ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16174 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;siterequest.com. IN MX ;; ANSWER SECTION: siterequest.com. 86400 IN MX 10 mail.siterequest.com. ;; Query time: 65 msec ;; SERVER: 172.16.100.1#53(172.16.100.1) ;; WHEN: Mon Nov 8 14:32:07 2011 ;; MSG SIZE rcvd: 51
Table of Contents   |   Next Chapter >>

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)