Active Fabric Controller (AFC) Deployment Guide
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction................................................................................................................5 System Requirements............................................................................................................................5 Recommended Requirements ............................................................................................................. 5 Pre-Installation Procedure...................................................................
Step 3 — Enabling the Controllers............................................................................................... 30 Step 4 — Configuring the Provider Networks .............................................................................30 Step 5 — Enabling the Tenant Workload Configuration using OpenStack................................ 30 Step 6 — Enabling Server High Availability...................................................................................
Introduction 1 This document guides you through the installation, setup, and deployment of the Active Fabric Controller (AFC) software on a single server or on two servers in an active-standby configuration. NOTE: You can install the software on a single server. For resiliency, Dell Networking recommends configuring a dual-server setup for high availability (HA). Install the software using the route processor module (RPM) or the open virtualization format (OVF) image.
Pre-Installation Procedure Before installing the software, perform the following pre-installation steps: 1. Prepare the infrastructure networks. Infrastructure networks support management of the physical infrastructure by the software. A typical OpenStack environment requires two infrastructure networks: a storage network and an OOB network. You can implement these networks as two separate physical L2 networks or as virtual local area networks (VLANs) on the same physical L2 network.
Figure 1. Single-Server Deployment Installing a Dual-Server (Active/Standby) Controller Dell Networking recommends a dual-server controller for resiliency.
Figure 2.
Install AFC using OVF 2 The following sections describe how to install AFC using OVF. You can install the software on a VM running on a hypervisor or on a physical machine. Installing AFC using OVF loads the software image and configure the system to interconnect with your hypervisor environment. NOTE: Regardless of installation type or deployment scenario, you must enable LLDP on all servers and hosts.
Deploying AFC — OVF using vSphere To deploy OVF, follow these steps. 1. Deploy the OVF template. Select File then Deploy OVF Template.... Select Next. Figure 3. Deploy the OVF Template 2. Select the source location. Use the Browse button to select the OVF file. Select Next. Figure 4.
3. The OVF Template Details page displays. If the template details are correct, select Next. If the template details are incorrect, select Back and re-enter your selections. Figure 5. Template Details 4. Rename your VM and choose your inventory location. (Optional) In the Name: field, enter the name of your VM. In the Inventory Location: field, select your inventory location. Select Next. Figure 6. Template Name and Location Options 5. Select the storage location for your VM files. Select Next.
6. Select the virtual disk format. There are three types of disk format: • Thick Provision Lazy Zeroed • Thick Provision Eager Zeroed • Thin Provision (Dell recommended) Select Next. Figure 8. Virtual Disk Formatting 7. Select the network map to use. Select Next. Figure 9.
8. Confirm your OVF selections. Review the options shown in the Deployment settings: field. If your deployment settings are correct, select Finish. Deploying OVF takes several minutes. If your deployment settings are incorrect, select Back and re-enter your selections. Figure 10. Ready to Complete Configuring the AFC VM To configure your virtual machine (VM), follow these steps. 1. Power on your VM from vSphere. Right-click on your VM name and select Power then Power On. Figure 11. Power On the VM 2.
3. Select Device Configuration using the space bar key. Use the tab key to select Save&Quit. To return to the previous screen, select Quit. Figure 12. Device Configuration 4. Select eth0 using the space bar key to configure the IP address. Use the tab key to select Save. To return to the previous screen, select Cancel. Figure 13.
5. Enter the following network configuration details to configure the newtwork. Use the tab key to select OK. • Name: enter eth0. • Device: enter eth0. • Static IP: enter the static IP address. • Netmask: enter the netmask IP address. • Default gateway IP: enter the default gateway IP address. • Primary DNS Server: enter the primary DNS server IP address. • Secondary DNS Server: enter the secondary DNS server IP address. To return to the previous screen, select Cancel.
• Change AFC superuser Password: Changes the AFC default administrative password. The password is case sensitive. • AFC Configuration: Displays the AFC configuration submenu. – Active Node: Displays Active Node options. – Standby Node: Displays Standby Node options. • Logs Configuration: Displays the Logs configuration submenu. – Logs to DB: Exports logs to the database. – Edit log configuration: Edits log configuration information. – Export logs: Exports the logs to the server.
To log in to the AFC main menu, use the same userID (superuser). 1. Use the Up and Down arrow keys to select Show AFC Status. Press Enter. The AFC system status displays. Figure 16. Show AFC Status 2. Press Enter again to return to the main menu. Figure 17. Show AFC Status Display Configuring the AFC Active Node Deploy the OVF and configure the IP address for an Active node installation. To use Active node installation, first configure AFC.
3. The Virtual IP Setting displays. If the virtual IP settings are correct, press Enter. You can change the following settings on this page: • SDNC VIP for this HA setup — select true or false. • SDNC VIP’s base interface • SDNC VIP’s alias interface • SDNC VIP address • SDNC VIP netmask To return to the main menu, press Enter. 4. Select Multicast Configuration to review or change your settings. If the virtual IP settings are correct, press Enter.
Configuring Logs to the Database To log in to the database or edit or export logs, use the following steps. 1. Log in to the DB. Use the Up and Down arrows to select Logs to DB — Requires restart AFC to take effect to log in to the DB. Press Enter. Logs to DB stores three levels of log information to the database — info, warn, and error. The 5MB table can store up to 15K of log records. 2. Edit the log configuration.
3. Shut down the VM. Press Enter to shut down the VM. Installing BMP To install, download and modify the switch firmware, following these steps. 1. Install BMP using the BMP Installation Menu. Use the Up and Down arrows to select BMP Installation. Press Enter. 2. Use the BMP setup wizard to configure your BMP installation. Use the SYSLOG server setup wizard to configure your SYSLOG server.
Upgrading the Switch Firmware To upgrade the switch firmware, following these steps. 1. Download to the latest switch firmware. Use the Up and Down arrows to select Switch Firmware Download. Press Enter. Enter 1, 2, 3 or 4 from the following options: • 1 — MXL • 2 — S4810 • 3 — S4820T • 4 — S6000 Enter the URL location. (Optional) enter a user name and password. The password is case sensitive. Select Enter to download the switch firmware.
Install AFC using RPM 3 The following sections describe how to install AFC using the route processor module (RPM). You can install the software on a VM running on a hypervisor or on a physical machine. Installing AFC using RPM create a new VM disk image and install CentOS 6.4 64–bit with all required packages and system setup. To install on a physical machine, install CentOS 6.4 64–bit with all required packages and system setup. For more information, refer to Installing Software using RPM.
7. Install the following daemons: • dhcpd • xinetd • in.tftpd # use ‘sudo yum install dhcp xinetd tftp-server’ 8. Reboot the system after you complete the package configuration. Installing AFC using RPM After placing the packages in the working directory, run the install_afc.py file. You are prompted to provide any missing configuration values. NOTE: During installation, you can ignore service stopping failures but do not ignore service starting failures.
Running setup_afc.sh NOTE: When you run the setup_afc.sh file, the software disables any current HA configurations. 1. To use a single-server without HA, enter false for Enable SDNC VIP for this HA setup. 2. If prompted, enter the multicast IP address and user plane (UP) port number. The multicast IP address and port number must be unique. If you have a standby-server configuration, the servers must have the same multicast address. You cannot use this address in other HA groups. 3.
5. 26 Enter y to remove all database data and cluster configurations.
Deploying AFC 4 The following sections describe deploying AFC. Installing the Dell OpenStack ML2 Mechanism Driver For more information, refer to the README.md for the ML2 Mechanism Driver at the following link: https://github.com/accessfabric/dellmech Configuring BMP on the Switch BMP detects the software image to determine if an update is required.
Connect to Legacy Networks The server fabric edge ports connect to the legacy switches running traditional L2 and L3 protocols. Regardless of deployment mode, legacy switches cannot use L3 routing in the server fabric. All L2 VLANs that you configure on the legacy switch must also be configured on the server fabric. The controller is notified of the VLANs through the north-bound application programming interface (API). Fabric edge ports that connect to legacy switches are considered uplink ports.
Enabling Active Fabric To set up and configure the fabric, follow these steps. Step 1 — Weaving the Fabric 1. Set up the head nodes (for example, two S4810 switches). 2. Connect the uplinks from all the chassis in the racks controlled by the nodes to the leaf nodes operating as a VLT-like configuration (no VLT protocol required) pair. NOTE: Steps 3 through 5 only apply if you are using MXL blades in an M1000E chassis as leaf nodes in the fabric. 3.
NOTE: Reboot the switch after changing the cam-acl and cam-acl-vlan values. If you do not reboot the switch, the configuration changes do not take effect. If you enable BMP 3.0, use the reload conditional nvram-cfg-change command. You must reload the chassis to upgrade any configuration changes when you have changed the NVRAM content. Step 2 — Enabling the Fabric 1. Start the fabric nodes and configure BMP on the IOMs to connect to the network DHCP server. 2.
