Active Fabric Manager (AFM) Deployment Guide 2.6

Configure Active Fabric Manager as a Virtual Appliance

Deploy Active Fabric Manager (AFM) as a virtual appliance on a VMware® ESX® virtual machine. This guide describes how to configure AFM as a virtual appliance. Before proceeding, install and configure an ESX host where you plan to run AFM. For additional information about installing and configuring the ESX virtual host machine, refer to the VMware documentation.

NOTE: To deploy AFM using the RPM package manager (RPM) installation instead of the open virtualization format (OVF), refer to RPM Installation.

Prerequisites

NOTE: If you are using the AFM virtual machine (VM) as a syslog and a trivial file transfer protocol (TFTP) or file transfer protocol (FTP) server, the following information is not required.

Before you begin, gather the following information:

Your local or remote DHCP information
Whether you want to use a Telnet or Secure Socket Shell (SSH) session within the fabric
The SNMP community string (by default, it is private for set and public for get)
The Syslog IP addresses (IP address of the remote syslog server)
The TFTP or FTP server address (IP address of the TFTP or FTP server for the Dell Networking operating system software images and configuration files during bare metal provisioning [BMP])
- NOTE: If you are using an FTP server, obtain the user name and password.

If you are using the Active Link Settings option, gather the following OpenManage Network Manager (OMNM) server information:

OMNM server IP address
Communication protocol (HTTP or HTTPS)
User name and password

For more information, refer to OMNM Requirements in the AFM User Guide.

Hardware Requirements

Table 1. Hardware Requirements
Hardware	Requirement
Processor	Intel® Xeon® E5620 2.4Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem
System Type	64-bit operating system
Memory	32GB Memory (8x4GB), 1333MHz Dual Ranked LV RDIMMs for 2 Processors, Advanced ECC
Disk Space	1TB 7.2K RPM SATA 3.5 Hot Plug Hard Drive

Virtual Appliance Requirements

AFM runs as a virtual appliance and requires the following host software:

VMware® vSphere® Hypervisor (ESXi) 5.1 and higher (must meet virtual appliance, port access, and listening port requirements)
- NOTE: VMware® vCenter™ is required for High Availability (HA) and Fault Tolerance (FT).

Deploy the OVF with HA and FT

The following are required to implement High Availability (HA) and Fault Tolerance (FT) using a VMware® ESX® Virtual Machine:

VMware® vCenter™ 5.0 Standard License
ESXi® 5.0 Enterprise Plus License
Dell M1000e chassis (for MXL blade or IOA blade switches)
Shared storage for the OVF

NOTE: By default, the AFM VM CPU is set to 2. To use the HA feature, change the virtual CPU to 1.

Deploy the OVF without HA and FT

The following are required to deploy AFM without HA or FT using a VMware® ESX® Virtual Machine:

VMware® ESXi® 5.0 Open Source License
Servers (rack or blade switch).
- NOTE: To use an MXL blade or IOA blade switches, AFM requires a M1000e blade chassis.
Shared storage for the OVF

Deploy the OVF with HA

When you deploy AFM with HA only using a VMware® ESX® VM, the requirements are as follows:

VMware® ESXi® 5.0 Open Source License
Shared storage for the OVF
- NOTE: By default, the AFM VM CPU is set to 2. To use the HA feature, change the virtual CPU to 1.

AFM Client Browser Requirements

Internet Explorer® 9 and higher
Firefox® 12 and higher

OMNM Requirements

NOTE:

The following is required to use the OMNM feature on the AFM:

OMNM Server Release 5.3 and higher

NOTE: The OMMN server is not installed on the same server as AFM. To activate the performance statistics, login directly as write permission into Dell OMNM web service.

For information on how to install and configure OMNM, refer to the following URL:

http://www.dell.com/support/Manuals/us/en/555/Product/dell-openmanage-network-manager.

NOTE: By default, the web service is disabled in the OMNM server.
1. Navigate to the server installation directory on the OMNN server.
2. Navigate to the installed.properties file at C:\ProgramFiles\Dell\OpenManage\Network Manager\owareapps\installprops\lib
3. Disable the application server and the synergy network management server.
4. Add the following three lines in the installed.properties file:
```
       com.dorado.core.ws.disable=false
                                                com.dorado.core.ws.legacy.soap.enabled=true
                                                oware.webservices.authrequired=false 
                                             
```
5. Enable Resource Monitoring.
6. Start the application server and synergy network management server.

Port Usage

The following table lists the default ports used by the various AFM services. To troubleshoot connectivity issues with the AFM server, use the following table:

Table 2. Ports
Port	Description
20 & 21	FTP
22	SSH and SCP (communication to switches and CLI access to the AFM server)
23	Telnet (communication to switches)
67 & 68	DHCP
69	TFTP
80	AFM server port listening for client connection and requests
8080	OMNM client connection
8089	OMNM web service port
8443	OMNM client HTTPS connection
123	NTP
161	For the SNMP get and set protocol between the AFM server and switch.
162	For the SNMP trap listener between the AFM server and switch.
443	For the HTTPS communication protocol where the AFM takes requests from the client browser.
5432	Database server
8080	TCP/UDP
61616	ActiveMQ

Disabling VMotion on an ESX/ESXi Host

To disable VMotion® on an VMware® ESX/ESXi® host, refer to the VMware documentation at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010376 or search in the VMware knowledge base using the key words “Disabling VMotion® on an ESX/ESXi host”.