53-1003174-01 February 2014 Brocade Virtual ADX Installation and Deployment Guide Supporting Brocade Virtual ADX version 03.0.00 ® © 2014, Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be trademarks of others. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government. The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that accompany it. The product described by this document may contain open source software covered by the GNU General Public License or other open source license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, and obtain a copy of the programming source code, please visit http:// www.brocade.com/support/oscd. Brocade Communications Systems, Incorporated Corporate and Latin American Headquarters Brocade Communications Systems, Inc. 130 Holger Way San Jose, CA 95134 Tel: 1-408-333-8000 Fax: 1-408-333-8101 E-mail: [email protected] Asia-Pacific Headquarters Brocade Communications Systems China HK, Ltd. No. 1 Guanghua Road Chao Yang District Units 2718 and 2818 Beijing 100020, China Tel: +8610 6588 8888 Fax: +8610 6588 9999 E-mail: [email protected] European Headquarters Brocade Communications Switzerland Sàrl Centre Swissair Tour B - 4ème étage 29, Route de l'Aéroport Case Postale 105 CH-1215 Genève 15 Switzerland Tel: +41 22 799 5640 Fax: +41 22 799 5641 E-mail: [email protected] Asia-Pacific Headquarters Brocade Communications Systems Co., Ltd. (Shenzhen WFOE) Citic Plaza No. 233 Tian He Road North Unit 1308 – 13th Floor Guangzhou, China Tel: +8620 3891 2000 Fax: +8620 3891 2111 E-mail: [email protected] Document History Title Publication number Summary of changes Date Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 New Document February 2014 Contents Preface Brocade resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Chapter 1 Brocade Virtual ADX Overview Brocade Virtual ADX features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Brocade Virtual ADX Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Typical deployment topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Tools supported on Virtual ADX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 cURL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 VMware tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Chapter 2 Brocade Virtual ADX Licensing License types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Software license terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Obtaining and installing a license file. . . . . . . . . . . . . . . . . . . . . . 6 Deleting a license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Using a trial license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Syslog and trap information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Chapter 3 Brocade Virtual ADX Installation on ESX host Brocade Virtual ADX in the ESX host environment . . . . . . . . . . . . . . 11 Brocade Virtual ADX Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Brocade Virtual ADX download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Brocade Virtual ADX installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Brocade Virtual ADX installation validation . . . . . . . . . . . . . . . . . . . . 16 Hardware checksum offload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Hardware checksum offload process . . . . . . . . . . . . . . . . . . . . . 18 Brocade Virtual ADX technical help . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Chapter 4 Brocade Virtual ADX Installation on KVM Host Brocade Virtual ADX in the KVM host environment . . . . . . . . . . . . . 19 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 i Configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Brocade Virtual ADX Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Brocade Virtual ADX download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Installing Virtual ADX VM on KVM host . . . . . . . . . . . . . . . . . . . . . . . 20 Installing Virtual ADX using virsh command . . . . . . . . . . . . . . . 21 Installing V-ADX using Virtual Machine Manager GUI . . . . . . . . 22 Powering on the V-ADX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Shutting down the V-ADX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Configuring the guest OS IP address . . . . . . . . . . . . . . . . . . . . . 29 Chapter 5 Installing Brocade Virtual ADX on Citrix XenServer Brocade Virtual ADX on XenServer: overview . . . . . . . . . . . . . . . . . . 31 Brocade Virtual ADX on XenServer: prerequisites . . . . . . . . . . . . . . 31 System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Configuration requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Brocade Virtual ADX download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Brocade Virtual ADX on XenServer: installation . . . . . . . . . . . . . . . . 33 Brocade Virtual ADX on XenServer: installation validation . . . . . . . 42 VLAN configuration using OpenvSwitch. . . . . . . . . . . . . . . . . . . . . . . 43 Mapping a XenCenter Network to an ovs-bridge . . . . . . . . . . . . 43 Mapping XenCenter VM Virtual Interfaces to ovs-ports . . . . . . 43 Configuring VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Displaying ovs-bridge and ovs-port information. . . . . . . . . . . . . 44 Removing OVS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Chapter 6 Brocade Virtual ADX Basic Network Settings Configuration Brocade Virtual ADX root password . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Setting the root password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Brocade Virtual ADX system port IP address . . . . . . . . . . . . . . . . . . 47 Brocade Virtual ADX console access via Guest OS SSH. . . . . . . . . . 48 Configuring Brocade Virtual ADX managment port IP address 49 Chapter 7 Brocade Virtual ADX Server Load Balancing Deployments Brocade Virtual ADX common SLB deployments and configurations51 Server Load Balancing in One-arm topology without VLAN tagging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Server Load Balancing in One-arm topology with VLAN tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Server Load Balancing in In-line topology . . . . . . . . . . . . . . . . . 56 Server Load Balancing in Hot-Standby HA topology . . . . . . . . . 57 Global Server Load Balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . 58 ii Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter 8 Brocade Virtual ADX Upgrade Brocade Virtual ADX Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Upgrading Brocade Virtual ADX using a new OVA file . . . . . . . . 59 Upgrading Brocade Virtual ADX using CLI and management port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Upgrading Brocade Virtual ADX using Console and system port (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Chapter 9 Brocade Virtual ADX Troubleshooting Brocade Virtual ADX troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . 61 Appendix A Configuration files guest.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 guest_ovs.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 iii iv Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Preface Document conventions This section describes text formatting conventions and important notice formats that may be used in this document. Text formatting The following text formatting conventions may be used in the flow of the text to highlight specific words or phrases. Format Description bold text Identifies command names Identifies keywords Identifies the names of user-manipulated GUI elements Identifies text to enter at the GUI or CLI italic text Provides emphasis Identifies variables and modifiers Identifies paths and Internet addresses Identifies document titles code Identifies CLI output Identifies command syntax examples Command syntax conventions Convention Description bold text Identifies command names, keywords, and command options. italic text Identifies variables. [] Syntax components displayed within square brackets are optional. { x | y |z } A choice of required parameters is enclosed in curly braces separated by vertical bars. You must select one. x|y A vertical bar separates mutually exclusive elements. <> Nonprinting characters, for example, passwords, are enclosed in angle brackets. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 v Brocade resources Convention Description ... Repeat the previous element. For example, member [member...]. \ Indicates a “soft” line break in command examples. If a backslash separates two lines of a command input, enter the entire command at the prompt without the backslash. Notes, cautions, and warnings The following notices and statements may be used in this document. They are listed below in order of increasing severity of potential hazards. NOTE A note provides a tip, guidance or advice, emphasizes important information, or provides a reference to related information. ATTENTION An Attention statement indicates potential damage to hardware or data. CAUTION A Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware, firmware, software, or data. DANGER A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations. Brocade resources To get up-to-the-minute information, go to http://my.brocade.com to register at no cost for a user ID and password. Release notes are available at http://my.brocade.com. White papers, online demonstrations, and data sheets are available through the Brocade website at: http://www.brocade.com/products-solutions/products/index.page Select Application Delivery Switches on this page to navigate to the relevant product information. vi Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Getting technical help Getting technical help For product support information and the latest information on contacting the Technical Assistance Center, go to http://www.brocade.com/services-support/index.html Contact Brocade Support 24x7 Use one of the following methods to contact the Brocade Technical Assistance Center. Online Telephone Email Preferred method of contact for non-urgent issues: Required for Sev 1-Critical and Sev 2-High issues: [email protected] • My Cases through • Continental US: MyBrocade • Software downloads & licensing tools • Knowledge Base Please include: • • • Europe, Middle East, Africa, • and Asia Pacific: +800-AT FIBREE (+800 28 34 27 • 1-800-752-8061 33) Problem summary Serial number Installation details Environment description • For areas unable to access toll free number: +1-408-333-6061 • Toll-free numbers are available in many countries. Document feedback Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. You can provide feedback in two ways: • Through the online feedback form in the HTML documents posted on http://www.brocade.com • By sending your feedback to [email protected] Provide the publication title, part number, and as much detail as possible, including the topic heading and page number if applicable, as well as your suggestions for improvement. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 vii Document feedback viii Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter Brocade Virtual ADX Overview 1 The Brocade Virtual ADX Application Delivery Switch (Brocade Virtual ADX) is a software solution, which enables the Brocade ServerIron ADX system software to run as a virtual machine on supported hypervisor platforms. In this way, the Brocade Virtual ADX emulates a proprietary Brocade ServerIron ADX system on platforms implemented with the x86 architecture. The Brocade Virtual ADX is shipped as a Virtual Appliance for the VMware ESX ,KVM and Xen hypervisors. You can run the Virtual Appliance after requesting and procuring the hardware resources from the respective host running the hypervisor. For ESX, you can configure and manage the Virtual Appliance using a vSphere Client. You can deploy the Virtual ADX on a single subnet or multiple subnets. You can also deploy the Virtual ADX as a stand-alone appliance or in a high availability pair. Brocade Virtual ADX features The Brocade Virtual ADX supports all of the essential features for ensuring the optimized delivery of application traffic so that you can deliver Server Load Balancing as a service. NOTE For the latest list of supported features and the download instructions, refer to the release notes relevant to your software release version. Brocade Virtual ADX Interfaces The Brocade Virtual ADX has five virtual NICs by default. During the installation process, you will see these ports identified by the following names. • System: This is a Guest OS (Linux) management port. You can use this port to get console access to the Brocade Virtual ADX via SSH or for upgrades and restarts. Use this port where interaction with the guest OS is required. The Brocade Virtual ADX VM uses the CentOS 6.2 Linux distribution as the Guest OS. NOTE You will use the system port for interacting with the Guest OS for system management functions. Use this port only as described in this guide. You can encounter unexpected and unsupported behavior arising from other uses. • Management: This is a management port for the Brocade Virtual ADX software. You can use this port to access the Brocade Virtual ADX Web GUI interface, SNMP and other management functions. You cannot access the Guest OS using this port. By default, the management port has an IP address of 192.168.100.100. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 1 1 Brocade Virtual ADX Interfaces • VADX_DATA_PG1 to VADX_DATA_PG3: These are data ports for the Brocade Virtual ADX software used for processing Layer 2 through Layer 7 data traffic. You can use these ports to access the Brocade Virtual ADX management functions also. You cannot use these ports to access the Guest OS. The Guest OS sees the five Brocade Virtual ADX ports as eth0-4. The Guest OS uses only eth0 (System port). Eth1-4 are not controlled by the Guest OS. These ports are used by the Brocade Virtual ADX software. For example, if you execute the following command at the Linux console, you will see only one port displayed in the output similar to the one shown here. [root@VirtualADX ~]# ifconfig | grep eth eth0 Link encap:Ethernet HWaddr 00:0C:29:2F:4A:0D The Brocade Virtual ADX software does not see eth0 (System port). The Brocade Virtual ADX software controls eth1 to eth4 and names them as follows. Eth1 is "interface mgmt 1" Eth2 is "interface ethernet 1" Eth3 is "interface ethernet 2" Eth4 is "interface ethernet 3" You must configure these ports only via the Brocade Virtual ADX interface commands. Virtual ADX (config)#show interface brief Port 1 2 3 mgmt1 Link Up Up Up Up State Forward Forward Forward Forward Dupl Full Full Full Full Speed None None None 1G Trunk None None None None Tag No No No No Priori level0 level0 level0 level0 MAC Name 000c.292f.4a21 000c.292f.4a2b 000c.292f.4a35 000c.292f.4a17 Figure 1 shows the naming conventions for the Brocade Virtual ADX interfaces. FIGURE 1 2 Brocade Virtual ADX interfaces. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Typical deployment topologies 1 In Figure 1, IP1, IP2 and IP3 are all in the management network subnet. IP1 is used to access the ESX host, typically via a vSphere client. IP2 is used to access the Guest OS inside the Brocade Virtual ADX virtual machine. IP3 (Brocade Virtual ADX management port IP) is used to access the Web GUI interface of the Brocade Virtual ADX. In addition, IP3 also supports Telnet and SSH. Note that Web GUI interface of Brocade Virtual ADX can also be accessed via the data ports of the Brocade Virtual ADX if proper IP connectivity is provided. NOTE Brocade Virtual ADX virtual port adapters have the capability to run at 10G speeds due to which the operational speed is displayed as 10G, irrespective of the speed of physical NIC. However, the physical NIC can be capable of 1G speed only. Hence, the actual throughput will be limited by the speed of physical NIC. Typical deployment topologies You can deploy the Brocade Virtual ADX on a single subnet or multiple subnets. You can also deploy the Brocade Virtual ADX as a stand-alone appliance. You can deploy the Brocade Virtual ADX in In-line and One-arm topologies. For detailed information, refer to the Deployment section in this guide. Tools supported on Virtual ADX Virtual ADX supports the following external tools: cURL cURL is a command line tool for transferring data using URL syntax. For further information about cURL, refer to http://curl.haxx.se/. You can run cURL from the Brocade Virtual ADX console. For example: 1. Power on and login to the Brocade Virtual ADX VM. 2. Enter the following command to access the Brocade Virtual ADX console. [user@VirtualADX ~]# vadx-console 3. Run cURL. The following examples show different usages of cURL. To specify the IP address of a real server, enter a command such as: [user@VirtualADX ~]# curl 172.21.1.10 % Total % Received % Xferd 0 Hi 0 3 3 0 0 Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 1352 0 --:--:-- --:--:-- --:--:-- 3000 To specify a specific HTML page, enter a command such as: [user@VirtualADX ~]# curl http://10.21.1.10/index.html % Total % Received % Xferd Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Average Speed Time Time Dload Upload Total Spent Time Current Left Speed 3 1 Tools supported on Virtual ADX 0 hi 3 0 3 0 0 1108 0 --:--:-- --:--:-- --:--:-- 3000 To specify cURL options (requires the use of quotes), enter a command such as: [user@VirtualADX ~]# curl "http://172.21.1.10/index.html --local 1234" % Total % Received % Xferd 0 hi 0 3 3 0 0 Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 1165 0 --:--:-- --:--:-- --:--:-- 3000 NOTE If the cURL command specifies more than one word, then these words must be enclosed in quotes. NOTE cURL should be run from the Brocade Virtual ADX console only. Using cURL from the Linux shell may cause unpredictable behavior. NOTE Brocade Virtual ADX currently supports the use of cURL for: - HTTP protocol only - IPv4 addresses only VMware tools VMware Tools is a suite of utilities that improves management of the virtual machine. The CentOS 6.2 Linux distribution enables installation of the VMware tools. The VMware tools are not installed by default. To install the VMware tools: • Deploy the OVA • After logging in, navigate to the Linux shell and run the script using the command “/root/install-tools” For more information on the VMware tools, refer to the VMware documentation. 4 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter Brocade Virtual ADX Licensing 2 This chapter decribes how to generate, obtain and install Brocade Virtual ADX licenses. License types Brocade and its suppliers grant to you a limited, non-exclusive, non-transferable, non-assignable, license to use the licensed features, either software or hardware or both, solely for internal purposes and solely for the purposes set forth in the Product documentation. The license(s) obtained by you through execution of License Agreement(s) are subject to the NSO policies located at www.brocade.com and may include additional limitations. For additional information, please reference your quote and invoice as well as www.brocade.com. The following license types are supported on Brocade Virtual ADX: • Trial license – a trial license enables demonstration and evaluation of a single Brocade Virtual ADX instance. A trial license is valid for 60 days and may be renewed once. A trial license is restricted to the system that it is first deployed on. • Perpetual license – a perpetual (non-expiring) license applies to a single Brocade Virtual ADX instance. It does not require renewal. A perpetual license is not restricted to the system that it is first deployed on; it is an entitlement to deploy an instance of Brocade Virtual ADX. Support and software upgrades are not included with a perpetual license, but can be obtained by paying an annual support fee. • Term license - a term license applies to a single Brocade Virtual ADX instance for a specific duration such as one, three or five years. A term license is not restricted to the system that it is first deployed on; it is an entitlement to deploy an instance of Brocade Virtual ADX. Support and software upgrades are not included with a term license, but can be obtained by paying an annual support fee. NOTE The Brocade Virtual ADX Version 03.0.00 term license is the same as a perpetual license. One, three and five-year term licenses will be available with later releases. • Developer license - a developer license applies to a single Brocade Virtual ADX instance in a non-production environment. A developer license supports a maximum throughput of 1 Mbps. Brocade Virtual ADX is supplied with a developer license. NOTE After installing a Brocade Virtual ADX instance, use the show license command at the Privileged EXEC level of the CLI, to view the developer license details. NOTE The license on one instance of the high availability (HA) pair is not transferred to the other instance. Each instance requires its own license. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 5 2 Brocade Virtual ADX Licensing Software license terminology • Entitlement certificate – The proof-of-purchase license certificate is an electronic file. It is generated when the order is confirmed. The information pertaining to the confirmed order is emailed as an instruction together with the license certificate. NOTE The software download is a separate process in addition to the license purchase. User has to input the unique serial number to activate the Virtual ADX software. • License file – The file produced by Brocade, contained within the entitlement certificate when the order is confirmed. The file is uploaded to the Brocade Virtual ADX instance and controls access to a licensed feature or feature set. • serial-number – This is a number that uniquely identifies the Brocade Virtual ADX instance. The unique serial-number is used to validate the proof-of-purchase and the software license for the Brocade Virtual ADX. • Licensed feature – Any feature or set of features that require a valid software license in order to operate on the Brocade Virtual ADX. Obtaining and installing a license file The license entitlement is issued to the customer along with an email message for further instruction, when the customer confirms the purchase of the Virtual ADX license or request a license. The serial-number must be added, using the the serial-number command, to the Brocade Virtual ADX instance after it is first installed. Subsequently, the serial number can be retrieved using the show serial-number command. The license key is contained within a license file, which is downloaded to the customer’s PC, where the file can then be transferred to a TFTP server and then uploaded to the Brocade Virtual ADX instance. Obtaining a license file Complete the following steps to generate and obtain a license for Brocade Virtual ADX: 1. After your Virtual ADX order is confirmed, you will receive the entitlement certificate e-mail message with the order details, together with your unique serial number and instruction to download the specific Virtual ADC software from My Brocade. 2. Refer to the section in the entitlement certificate e-mail message on Instruction for Downloading the Software and Documentation to download and install the Virtual ADX software from My Brocade. 3. After installing your Brocade Virtual ADX instance, use the serial-number command at the Privileged EXEC level of the CLI, to add the serial number to your Brocade Virtual ADX instance. For example: Virtual ADX# serial-number ABC12345678 Syntax: serial-number string The string variable specifies the unique serial number of your Brocade Virtual ADX instance. This 11 character, alphanumeric string is contained in the license entitlement e-mail message. 6 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX Licensing 2 4. Use the show serial-number CLI command on your Brocade Virtual ADX to verify that the serial number has been added to the instance. This serial number is used to validate your Virtual ADX software license. Virtual ADX# show serial-number Serial-Number: ABC12345678 Syntax: show serial-number 5. Download the unique license file from the entitlement certificate by saving the file from the e-mail attachment to your PC. 6. Install your license file (Refer to “Installing a license file”). 7. Verify your license file installation (Refer to “Verifying the license file installation”). Installing a license file Copy the license file to a TFTP server to which the Brocade Virtual ADX has access and then use TFTP to copy the file to the license database of the Brocade Virtual ADX instance. To copy a license file from a TFTP server to the license database on the Brocade Virtual ADX instance, enter a command such as the following at the Privileged EXEC level of the CLI: Virtual ADX# copy tftp file 10.1.1.1 lic.xml license Syntax:copy tftp file IP_address license_filename_on_host license The IP_address variable is the address of the IPv4 TFTP server. The license_filename_on_host variable is the filename of the license file. Verifying the license file installation To display information about all software licenses in the license database, use the show license command. For example: Virtual ADX# show license Index 1 2 Package Name VADX-LIC-DEV VADX-LIC-10M Serial-Number ABC12345678 ABC12345678 LicenseType Developer normal Status active active LicensePeriod Bandwidth unlimited 1 Mbps unlimited 10 Mbps To display detailed information about a particular license, for example the VADX-LIC-DEV listed above, enter the following command. Virtual ADX# show license 1 Syntax:show license index-number The index-number variable specifies the index number of a particular license as shown in the output of an unqualified show license command. TABLE 1 Output from the show license command This field... Displays... Index The license hash number that uniquely identifies the license. Package Name The package name for the license. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 7 2 Brocade Virtual ADX Licensing TABLE 1 Output from the show license command (Continued) This field... Displays... Serial-Number The serial number of the Brocade Virtual ADX instance. Use the show serial-number command at the Privileged EXEC level of the CLI to retrieve the serial number of your Brocade Virtual ADX instance. License Type Indicates whether the license is normal (perpetual), term (specified duration), trial (temporary) or developer (non-production license). Status Indicates the status of the license: Invalid – A license is invalid when the LID doesn’t match the serial number of the device for which the license was purchased. • Active – The license is valid and in effect on the device. • Inactive – For trial licenses only, this indicates that the trial license has expired. • License Period If the license type is trial (temporary), this field will display the number of days the license is valid. If the license type is normal (perpetual) or developer, this field will display “unlimited”. If the license type is term (specified duration), this field will display the license term i.e. one, three or five years. Bandwidth Indicates the licensed throughput level, measured in Mbps. NOTE For information about managing Brocade Virtual ADX licenses using the Brocade Virtual ADX web interface, refer to the Brocade Virtual ADX Graphical User Interface Guide. Deleting a license A license will remain in the license database until it is deleted. To delete a license, enter commands such as the following at the Privileged EXEC level of the CLI. Use the show license command to identify the index number of the license that you want to delete. Virtual ADX# show license Index 1 2 Package Name VADX-LIC-DEV VADX-LIC-10M Serial-Number ABC12345678 ABC12345678 LicenseType Developer normal Status active active LicensePeriod Bandwidth unlimited 1 Mbps unlimited 10 Mbps Use the following command to delete the license with index number “1”. Virtual ADX# license delete 1 This command immediately removes the license with index number “1“, from the license database. The licensed feature will continue to run as configured until the software is reloaded, at which time the feature will be disabled and removed from the system. Syslog messages are generated when the license is deleted. Syntax: license delete index_number The index_number variable specifies the index number of the license that you want to delete, as shown in the output of an unqualified show license command. 8 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX Licensing 2 Using a trial license A trial license enables demonstration and evaluation of a single Brocade Virtual ADX instance. The trial license is valid for a period of up to 60 days, and is renewable for an additional 60 days if required. A licensed feature operating under a trial license has the same functionality (CLI and show commands) as it does when operating under a normal license. To access the trial license and software, please go to my.brocade.com. What happens when a trial license expires A trial license will expire when it exceeds the specified expiration time or date. The countdown starts when the trial license is installed on the Brocade Virtual ADX instance. When the license expires, the CLI commands related to the licensed feature will no longer be available from the CLI. NOTE Trial licenses are not cumulative. The new license replaces the current license. To purchase the Brocade Virtual ADX production license, please contact your Brocade representative. Console, and Syslog messages for trial license expiration Twenty days prior to the date that a trial license is set to expire and each day until the last day, the following warning message will appear daily on the console. On the day that the license will expire, the warning message will appear every two hours. Syslog messages will also be generated. SYSLOG: <12>Jan 1 00:00:00 License: Package VADX-LIC-TRL with SERIAL-NUMBER ABC12345678 will expire in 2 days, use license delete to remove it. When the license has expired, the following message will appear on the console. Syslog messages will also be generated. SYSLOG: <13>Jan 1 00:00:00 License: Package VADX-LIC-TRL with SERIAL-NUMBER ABC12345678 has expired. Renewing or extending a trial license A trial license can be extended, once by another trial license of the same type, or by a normal license of the same type. To avoid any interruptions to the network, obtain and install the second trial license before the first license expires. When extended by another trial license, the duration is not cumulative. The countdown starts when the trial license is installed. To extend the license, you must contact your Brocade representative. Syslog and trap information The following Syslog messages are supported for Brocade Virtual ADX licensing. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 9 2 Brocade Virtual ADX Licensing TABLE 2 Syslog messages Message level Message Explanation Informational License: Package package_name with SERIAL-NUMBER serial_number is added Indicates that the license package has been added. Informational License: Package package_name with SERIAL-NUMBER serial_number is removed Indicates that the license package has been deleted. Warning License: Package package_name with SERIAL-NUMBER serial_number will expire in number days/hours, use license delete to remove it. The trial license is about to expire. This message will begin to display 20 days before the expiration date, and every 2 hours on the last day that the license will expire. Notification License: Package package_name with SERIAL-NUMBER serial_number has expired The trial license has expired. SNMP traps are also provided when a license is added, deleted or about to expire. 10 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter Brocade Virtual ADX Installation on ESX host 3 This section describes how to download and install the Brocade Virtual ADX Application Delivery Switch (Brocade Virtual ADX) on ESX host. You will learn about the prerequisites, the download location and other information to get started. Brocade Virtual ADX in the ESX host environment In a typical setup, where you are connected to the ESX Host from a PC running a vSphere client, you will install the Brocade Virtual ADX as a Virtual Appliance (VA) on the ESX Host. The Brocade Virtual ADX will run as a guest on the ESX Host. Brocade Virtual ADX Prerequisites You will need an x86 server running the ESX hypervisor from VMware. The recommended minimum resources required by the Brocade Virtual ADX are shown below. Software • VMware Hypervisor ESX version 4.0 or later • VMware vSphere Client version 4.0 or later Hardware • • • • 2 GHz, Dual-core, 64-bit x86 CPU 4 GB RAM 40 GB disk space Network adaptor with 2 physical ports NOTE By default, the Brocade Virtual ADX requests and reserves the following hardware resources from the ESX host during configuration. 2 Virtual CPUs (minimum 2) 2 GB RAM 20 GB disk space 5 Virtual ports If you need help with obtaining and installing the ESX hypervisor and the vSphere client, contact VMware. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 11 3 Brocade Virtual ADX download Brocade Virtual ADX download You can download a copy of the Brocade Virtual ADX software. Use the following steps to complete the download. 1. Go to my.brocade.com and login. 2. Click on My Account in the upper right hand corner of the page. NOTE Skip steps 3 and 4 if you have already requested and been granted access. 3. Click on Request Special Site Access in the My Site Access section of the page. 4. Enter the access code provided with your certificate of entitlement in the input box next to the Submit button on the screen, and click on Submit. The system will show a message that the access you requested has been added to your account, and the access profile will be listed in the Current Site Access section. 5. Click on Downloads on the main page. 6. Click on Application Delivery Controllers or Network Functions Virtualization from the Download by dropdown list. 7. Click on Virtual ADX in the Product Name area. 8. Navigate the folder and click on the downloadable Virtual ADX file based on the requested hypervisor support. 9. Select the OVA file link and follow the prompts to start the download and save the file. 10. If you are upgrading, select the .gz file link and follow the prompts to download and save the file. Brocade Virtual ADX installation Use the following steps to complete the installation and deployment. NOTE This section assumes that you are directly connected to the ESX host. If you are connecting to the host through a vCenter, you will need to login to the vCenter server. Please refer to documentation from VMware for further details. 1. Setup the VMware ESX server in preparation for installing the Brocade Virtual ADX. NOTE Use the recommended resource requirements or better to avoid unexpected results. Brocade provides some preconfigured values with the Brocade Virtual ADX. 2. Start the vSphere client. If you do not have a vSphere client, you may use a web browser to login to the host machine and download and install a vSphere client. You will need the IP address or name for the ESX host. 3. Login to the ESX host machine using appropriate credentials. 12 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX installation 3 4. Create the required vSwitches and port groups to be associated with the Brocade Virtual ADX virtual NICs. NOTE If you have already configured the required port groups, proceed to step 5. a. Click on the Configuration tab. b. Select Networking in the Hardware area. c. Click on Add Networking. d. Select Connection Type as Virtual Machine (radio button). Click Next e. Select the pNIC port to assign to the vSwitch. Click Next. f. Enter a Network Label of your choice. NOTE The Brocade Virtual ADX is preconfigured to connect its three data ports with VADX_DATA_PG1, VADX_DATA_PG2, VADX_DATA_PG3. Brocade recommends you use these labels while creating port groups. g. Under VLAN ID (Optional), enter the same VLAN ID as the Brocade Virtual ADX data port connected to this port group. If that data port is a tagged member of more than one VLAN, select All (4095) from the dropdown menu. Click Next Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 13 3 Brocade Virtual ADX installation h. Click Finish. You will see a screen similar to the one shown. 5. Deploy Brocade Virtual ADX. a. From the File menu, choose Deploy OVF Template. b. Follow instructions from the wizard to install from local copy of the OVA file. c. Uniquely name the VM and select ESX host (if using a vCenter). NOTE ESX host selection is required only if you are connecting to the vCenter and not directly connecting to the ESX host. d. 14 Reserve minimum storage and compute resources for this instantiation of the Brocade Virtual ADX. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX installation 3 e. Connect the Brocade Virtual ADX to the vSwitch. f. In the left pane, click on the VM. Click on the Summary tab and click on Edit Settings in the Commands area. g. On the Hardware tab of the window that pops up, select a Network Adapter and click Connect at power on in the Device Status area. h. Repeat the above step for each of the remaining Network Adapters. NOTE Brocade Virtual ADX supports Layer 2 switching of broadcast and unknown unicast packets so you must connect the three data ports to three distinct vSwitches to avoid network loops. If you plan to connect the data ports to the same vSwitch, then you must use different VLANs for each data port. You must take the same care when deploying multiple instantiations of the Brocade Virtual ADX on the same ESX host. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 15 3 Brocade Virtual ADX installation validation The following is a typical vSphere screenshot for a deployed and powered on Brocade Virtual ADX. NOTE The ESX host associates a default port group (VM Network) with all the Virtual ADX interfaces. You must create different port group associations before you deploy the Virtual Appliance because the default association by the ESX host could lead to undesirable results (loops). If Brocade has assigned alternate port group names, you may use them or modify them to suit your needs. Brocade Virtual ADX installation validation You can execute the following steps to ensure that the Brocade Virtual ADX is installed correctly. Power on and access the Virtual Machine from the vSphere client. 1. In the left pane, select the Brocade Virtual ADX VM that you installed. 2. From the Summary tab, click Power On in the Commands area. You can also right click the VM in the left pane and follow the dropdown menu to Power On. 3. Click on the Console tab. 16 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Hardware checksum offload 3 You should see the following output (or similar) on your screen. Welcome to Brocade Virtual ADX: Virtual ADX login: Enter root at the prompt. You do not require a password for logging in at this point. You should see the following prompt. VirtualADX> Execute the following commands. VirtualADX>serial-number ser_num VirtualADX>show serial-number The output of the second command should be the value of the ser_num you entered. NOTE The serial number is also your entitlement information for support. Please make a note of it for your records. You will receive this information from Brocade at the time of order fulfilment. NOTE By default there is no password and you are logged in as root. Brocade recommends that you set a password as soon as possible. NOTE You will need to enter Ctrl-Alt to get cursor control back from the vSphere console. Hardware checksum offload On select hypervisors it may be possible to improve Virtual ADX performance by offloading the hardware checksum calculation to the network adapter. This functionality is disabled by default as not all network adapters support the checksum calculation. Once you have determined that your network adapter supports the checksum calculation, you can enable the functionality on the Brocade Virtual ADX to further optimize performance. To enable the functionality, enter the following command in configuration mode. VirtualADX(config)#server hw-csum-offload Syntax: [no] server hw-csum-offload Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 17 3 Brocade Virtual ADX technical help Hardware checksum offload process The hardware checksum offload process in depicted in Figure 2. FIGURE 2 Hardware checksum offload process NOTE Check the network adapter manual to know if it supports the hardware checksum offload functionality. Brocade Virtual ADX technical help Go to http://www.brocade.com/services-support/index.page for the latest contact information. NOTE Please ensure that you have your entitlement information (serial number) available. 18 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter Brocade Virtual ADX Installation on KVM Host 4 This section describes how to download and install the Brocade Virtual ADX Application Delivery Switch (Brocade Virtual ADX) on KVM host. You will learn about the prerequisites, the download location and other information to get started. Brocade Virtual ADX in the KVM host environment Kernel-based Virtual Machine (KVM) is an open source virtualization solution for Linux on x86 hardware, with hardware virtualization extensions. The environment setup involves the installation and configuration of KVM on the KVM host and then deploying the Virtual ADX. Configuration overview The configuration task involves configuring the KVM hypervisor and the Virtual ADX VM. The hypervisor configuration involves setting up the network interfaces (Vports) and the properties of the VM. This configuration is managed by the KVM Virtual Machine Management tool or shell commands. The VM properties include memory size allocation, disk space allocation, virtual CPUs allocation, and so on. Brocade Virtual ADX Prerequisites The recommended minimum resources required by the Brocade Virtual ADX are shown below. Software • KVM host 0.10.0 or higher Hardware • • • • • Host CPU supporting virtual technology such as Intel VT or AMD-V. Minimum 2 virtual CPUs Minimum 2GB RAM Minimum 8GB disk space Five virtual ethernet ports Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 19 4 Brocade Virtual ADX download NOTE There must be five virtual ethernet ports defined for a Virtual ADX VM. Out of this, the first interface as defined in Virtual ADX VM becomes eth0 and is used to access to the guest VM. The second interface becomes the management interface of the Virtual ADX. The third, fourth and fifth interfaces can be used as data or HA. Brocade Virtual ADX download You can download a copy of the Brocade Virtual ADX software. Use the following steps to complete the download. 1. Go to my.brocade.com and login. 2. Click on My Account in the upper right hand corner of the page. NOTE Skip steps 3 and 4 if you have already requested and been granted access. 3. Click on Request Special Site Access in the My Site Access section of the page. 4. Enter the access code provided with your certificate of entitlement in the input box next to the Submit button on the screen, and click on Submit. The system will show a message that the access you requested has been added to your account, and the access profile will be listed in the Current Site Access section. 5. Click on Downloads on the main page. 6. Click on Application Delivery Controllers or Network Functions Virtualization from the Download by dropdown list. 7. Click on Virtual ADX in the Product Name area. 8. Navigate the folder and click on the downloadable Virtual ADX file based on the requested hypervisor support. 9. Select the qcow2 file link and follow the prompts to start the download and save the file. 10. If you are upgrading, select the .gz file link and follow the prompts to download and save the file. Installing Virtual ADX VM on KVM host This section describes the steps involved in hosting the Virtual ADX VM on the KVM host and the configurations required on the hypervisor, prior to deploying the VM. Before installing V-ADX on KVM host, ensure the following: • The machine needs to support either Intel VT or AMD-V chipsets. The BIOS needs to have Virtualization Technology enabled. To check whether your system processor supports KVM, you can run the following command: grep -E 'vmx|svm' /proc/cpuinfo 20 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Installing Virtual ADX VM on KVM host 4 • Install the KVM package and bridge utilities. You can use either bridges or OVS bridges to transport the traffic to the Virtual ADX on the KVM host. The setup is to have five ports on the Virtual ADX to have access to the outside network through four physical ports on the KVM host. For information on this, refer KVM documentation. • If SR-IOV is used, turn on VT-d to support Virtualization Technology for Directed I/O in the BIOS. You can deploy Virtual ADX on a KVM host in the using virsh shell command or Virtual Machine Manager GUI. Installing Virtual ADX using virsh command To deploy V-ADX using virsh command, execute the following steps: 1. Copy the sample VM configuration file (guest.xml) and the Virtual ADX qcow2 image (virtualadx_img.qcow2) to a directory, for example, </home/user_name> on the KVM host. NOTE For Open vSwitch (OVS) deployment, use guest_ovs.xml file. Refer Appendix A Configuration files for the contents of the configuration files. 2. Log on to the KVM host and change to the directory </home/user_name>. 3. In the VM configuration file, change domain name from <name>__Virtual_ADX__</name> to <name>virtual_adx</name>. You can specify the name of your choice. (For the purpose of illustration, let us keep the name as virtual_adx, throughout this document section). 4. Modify the target device name if this is not the first Virtual ADX deployed. This is to ensure that each V-ADX has a unique target name for each network port. For example, the first V-ADX will have target name of eth0-guest1, eth0-manage1, eth1-client1, eth2-server1 and eth3-HA1. For the second Virtual ADX deployed, it should be eth0-guest2, eth0-manage2, eth1-client2, eth2-server2, and eth3-HA2 (i.e.; change <target dev='eth0-guests1'/> to <target dev='eth0-guests2'/>). NOTE If you do not need to identify ports in V-ADX in the output of the ovs-vsctl show command, you can remove them from the guest.xml file. When you start V-ADX, the KVM host will automatically create unique sequentially increasing target names in the OVS, starting from vnet0, vnet1, etc. Each V-ADX will have five virtual ports created in the OVS. Therefore, the first V-ADX will have target name ranging from vnet0 to vnet4 and the second Virtual ADX will have target names ranging from vnet5 to vnet9 and so on. 5. Change image name from <source fiile=’/image_directory/your_virtual_adx_qcow_file.qcow2’> to <source file=’/home/user_name/virtualadx_img.qcow2’>. You can specify the image name of your choice (For the purpose of illustration, let us keep the name as virtualadx_img.qcow2, throughout this document section). If the KVM host uses OVS, add <virtualport type='openvswitch'/> to all five interface entries. For example, <interface type=’bridge’> <source bridge='br0'/> Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 21 4 Installing Virtual ADX VM on KVM host <virtualport type='openvswitch'/> <target dev='eth0-manage1'/> <model type=’e1000’/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> NOTE Ensure that all five interfaces have no duplicated PCI address entry. The first interface entry must have the pci configuration <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>. 6. Create bridges and OVS ports on the KVM host to enable traffic to the Virtual ADX. NOTE The sample configuration files provided in Appendix A Configuration files uses four source bridges (br0 to br3). You can change them to use your available bridges. 7. Define the KVM guest VM by entering the virsh define guest.xml shell command. Based on the given guest VM configuration file “guest.xml”, the Universally Unique Identifier (UUID) and five MAC addresses starting with “52:54:00” will be generated and stored in /etc/libvirt/qemu/virtual_adx.xml file. To check whether the guest VM is defined, enter the virsh list –all shell command. If the guest VM is defined, the V-ADX name which you assigned will be displayed in shut off state, in the list displayed. Installing V-ADX using Virtual Machine Manager GUI To deploy V-ADX image using Virtual Machine Manager GUI, execute the following steps: 1. Copy the Virtual ADX qcow2 image (virtualadx_img.qcow2) to a directory, for example, </home/user_name> on the KVM host. 2. Log on to the KVM host and open the Virtual Machine Manager application from Application > System Tools in Linux. Alternately, you may run the virt-manager shell command. 22 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Installing Virtual ADX VM on KVM host 4 3. Click Create new virtual machine button. The New VM dialog box is displayed. FIGURE 3 Create a new VM - Step 1 4. Enter the name of the new guest VM and select Import existing disk image radio button. Then, click Forward button to navigate to the next step. FIGURE 4 Create a new VM - Step 2 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 23 4 Installing Virtual ADX VM on KVM host 5. Enter the complete path to the V-ADX qcow2 image. Alternately, you can use the Browse button and then click Browse Local to select the V-ADX qcow2 image. Click Open to insert the complete path. 6. Select Linux as the OS type and Red Hat Enterprise Linux 6 as the Version. Then, click Forward to go to next step. NOTE If you see a pop up message indicating that the Disk qcow2 image is already in use by another guest, select “no” to the question “Do you really want to use the disk?”. Then, select the one that is not in use. FIGURE 5 24 Create a new VM - Step 3 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Installing Virtual ADX VM on KVM host 7. 4 Set the memory to “2048 MB” and number of CPUs to “2”. Click Forward button to navigate to the next step. FIGURE 6 Create a new VM - Step 4 8. Select the Customize configuration before install checkbox and click Finish button. The virtual machine configuration details are displayed, which you can edit before creating the VM. FIGURE 7 Create a new VM - Step 5 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 25 4 Installing Virtual ADX VM on KVM host 9. Select Processor tab from the left menu and click Copy host CPU configuration in the right panel to copy CPU configuration from the KVM host. Then, click Apply. NOTE This allows V-ADX to use the CPU configuration, which might speed up the processing speed in the guest OS. Ensure thet the features that you copied match with the features supported on your host CPU. You may skip this step if you are not sure. If you change the configuration while the VM is running, it will not be applied until the next time when the guest VM is rebooted. 10. Select Disk from the left menu. From the Advanced Options in the right panel, select “IDE” as the disk bus and “qcow2” as the storage format. FIGURE 8 26 Create a new VM - Step 6 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Installing Virtual ADX VM on KVM host 4 11. To change the network setting for eth0 of the V-ADX, select the NIC from the left menu. The NIC configuration is display on the right panel. FIGURE 9 Create a new VM - Step 7 12. Select Specify shared device name from the Source device dropdown and assign a name to the bridge (example: br0) in the Bridge name field. 13. Form the Device model field, select the model as e1000 and click Apply. NOTE You can select only the e1000 interface. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 27 4 Installing Virtual ADX VM on KVM host 14. Click the Add Hardware button below the left menu. The Add New Virtual Hardware dialog box is displayed. FIGURE 10 Create a new VM - Step 8 15. Select Network tab on the left menu and then select the host device from the Host device drop down. Alternately, you can select Specify shared device name form the Host device drop down and then enter the name in the Bridge name field. 16. Select the device model as e1000, from the Device model dropdown and then click Finish. 17. Repeat step 11 to Step 16 to configure all the NICs. Then, click Apply. 18. Click Begin Installation on top of the left menu to create the virtual ADX VM. To check whether the guest VM is defined, run the virsh edit <domain_name> command to view the VM configuration. The default editor in virsh is vi. To change it, setup the environment variables $VISUAL or $EDITOR to the editor which you want to use. Powering on the V-ADX You can start the newly deployed V-ADX in any of the following ways: • virsh command: Run the virsh start vadx_domain_name, where vadx_domain_name is the name of the guest that you specified in the xml configuration file. • Virtual Machine Manager: In Linux, open the Virtual Machine Manager application from Application > System Tools. The newly deployed V_ADX will be listed in the guest VM list. Right click on V-ADX and select Open to access to the console and select Virtual Machine > Run, to run the VM. 28 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Installing Virtual ADX VM on KVM host 4 Shutting down the V-ADX You can shut down the V-ADX in any of the following ways: • virsh command: Run the virsh shutdown <vadx_domain_name> where vadx_domain_name is the name of the guest that you specified in the xml configuration file. • Virtual Machine Manager: In Linux, open the Virtual Machine Manager application from Application > System Tools. The newly deployed V_ADX will be listed in the guest VM list. Right click on V-ADX and select Open to access to the console and select Virtual Machine > Shutdown > Shutdown, to shut down the VM. Configuring the guest OS IP address After powering on the V-ADX for the first time, execute the following steps from the Virtual Machine Manager console, to configure the guest OS IP address. 1. Login as root user using the login name “root” and the password “password”. 2. Setup the IP address and net mask for the eth0 of the Virtual ADX using vi/etc/sysconfig/network-scripts/ifcfg-eth0. Make sure it has the following variables are available. ONBOOT=yes DEVICE=eth0 BOOTPROTO=static IPADDR=10.24.137.178 Change the IP address and net mask as applicable for your network environment. This eth0 interface will be used to remotely access the V-ADX. To access the console, click Console radio button from the View menu. Click anywhere in the console window and enter any key to see the console output. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 29 4 30 Installing Virtual ADX VM on KVM host Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter Installing Brocade Virtual ADX on Citrix XenServer 5 This section describes how to download and install the Brocade Virtual ADX on the Citrix XenServer hypervisor platform. You will learn about the installation prerequisites, download location, and other information to get started. Brocade Virtual ADX on XenServer: overview Citrix XenServer is a widely-deployed, open-source virtualization platform for managing cloud, server and desktop virtual infrastructures. XenServer includes the Xen hypervisor, the enterprise-ready XAPI toolstack and integrations for cloud, storage and networking solutions. The following tables describe XenServer platform limitations. TABLE 3 XenServer Virtual Machine(VM) Limits Compute Virtual CPUs per VM 16 Memory RAM per VM 128 GB Networking Virtual NICs per VM 7 TABLE 4 Compute XenServer Host Limits Logical processors per host 1604 Virtual CPUs per host (Linux VMs) 12000 Concurrent VMs per host (Linux VMs) 650 Memory RAM per host 1 TB Networking Physical NICs per host 16 Virtual NICs per host 512 VLANs per host 800 VLANs per physical NIC 1019 Brocade Virtual ADX on XenServer: prerequisites System requirements You will need an x86 server running the XenServer hypervisor from Citrix and a XenCenter client installed on a Windows-based machine. The recommended minimum resources required by Brocade Virtual ADX are shown below. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 31 5 Brocade Virtual ADX download Hardware The list of server hardware currently certified and supported for use with Citrix XenServer can be found at http://hcl.vmd.citrix.com/. The server hardware will require the following minimum resources: 4GB RAM 40GB disk space (One instance of Brocade Virtual ADX VM and XenServer) 2 physical ethernet port NOTE Brocade Virtual ADX will require the following resources: 2 virtual CPUs 2GB RAM 20GB disk space 5 virtual ethernet ports (Refer to Brocade Virtual ADX Interfaces for further information on virtual port requirements.) Software • Citrix XenServer hypervisor version 6.2.0 or higher • Citrix XenCenter client version 6.2. Configuration requirements Enable e1000 vNICs on the XenServer system You must complete the following, once-off procedure to enable e1000 vNICs on the XenServer machine before deploying Brocade Virtual ADX. 1. Use the following command to rename “/usr/lib/xen/bin/qemu-dm” to “/usr/lib/xen/bin/qemu-dm.orig”. [root@xenserver ~]# mv /usr/lib/xen/bin/qemu-dm /usr/lib/xen/bin/qemu-dm.orig 2. Create a new “/usr/lib/xen/bin/qemu-dm” file with the following contents: #!/bin/bash oldstring=$@ newstring=${oldstring//rtl8139/e1000} exec /usr/lib/xen/bin/qemu-dm.orig $newstring 3. Execute the following command: [root@xenserver ~]# chmod 755 /usr/lib/xen/bin/qemu-dm Brocade Virtual ADX download Use the following steps to download a copy of the Brocade Virtual ADX software. 1. Go to my.brocade.com and login. 2. Click on My Account in the upper right hand corner of the page. 32 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX on XenServer: installation 5 NOTE Skip steps 3 and 4 if you have already requested and been granted access. 3. Click on Request Special Site Access in the My Site Access section of the page. 4. Enter the access code provided with your certificate of entitlement in the input box next to the Submit button on the screen, and click on Submit. The system will show a message that the access you requested has been added to your account, and the access profile will be listed in the Current Site Access section. 5. Click on Downloads on the main page. 6. Click on Application Delivery Controllers or Network Functions Virtualization from the Download by dropdown list. 7. Click on Virtual ADX in the Product Name area. 8. Navigate the folder and click on the downloadable Virtual ADX file based on the requested hypervisor support. 9. Select the OVA file link for your host environment and follow the prompts to start the download and save the file. 10. If you are upgrading, select the .gz file link and follow the prompts to download and save the file. Brocade Virtual ADX on XenServer: installation XenServer supports the following network backends to provide virtual switch functionality on the hypervisor: • Linux Bridging (LB) • OpenvSwitch (OVS) Linux Bridging supports an access port equivalent that can accept traffic on only one VLAN. If you choose the Linux Bridging backend, a Virtual ADX port can be part of only one VLAN. OpenvSwitch supports additional VLAN features when compared to Linux Bridging; it supports trunk ports which can accept tagged traffic on multiple VLANs. If you want to configure ports on more than one VLAN you need to choose the Openvswitch backend. Use the following steps to complete the installation and deployment. 1. Choose the network backend via SSH login or the XenCenter Console. Use the following command to select the Linux Bridging network backend. [root@xenserver ~]# xe-switch-network-backend bridge Use the following command to select the Openvswitch network backend. [root@xenserver ~]# xe-switch-network-backend openvswitch NOTE These commands will only become effective after a server reboot. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 33 5 Brocade Virtual ADX on XenServer: installation OpenvSwitch is a multi-layer software switch that is well suited to function as a virtual switch in virtual machine environments. Brocade Virtual ADX requires configuration of the following OVS entities: • ovs-bridge - An ovs-bridge represents an ethernet switch with one or more “ports” and can be considered equivalent to a vSwitch on the VMware ESX Server. • ovs-port - An ovs-port represents a port within an ovs-bridge; it logically corresponds to a port on a physical ethernet switch. For further information about the ovs-bridge and ovs-port entities, refer to “VLAN configuration using OpenvSwitch” on page 43 2. Start the XenCenter client. NOTE XenCenter client can be downloaded free from www.citrix.com/xenserver/download. You must be registered on the Citrix site to download the XenCenter client. 3. Create the XenServer “networks” required by the Brocade Virtual ADX VM. • Brocade Virtual ADX VM requires a minimum of five virtual interfaces. • XenServer does not support the concept of port groups. A "network" on the XenCenter GUI is equivalent to a vSwitch on vSphere from VMware and is used to bind a Brocade Virtual ADX virtual interface. • XenServer creates a “Network” for each physical NIC on the host on bootup. These networks are named Network 0 for NIC0, Network 1 for NIC1 etc., as shown in the figure below. These networks are used: • When deploying the Brocade Virtual ADX VM eth0 and eth1 interfaces • For data ports that need connectivity to a physical NIC • A XenServer "External Network" must be created and used for a data port that needs a physical NIC connection and to be on a single vlan. 34 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX on XenServer: installation a. 5 Select the xenserver on left panel as shown in the figure below. Then select the Networking tab. FIGURE 11 XenCenter: Server Networks Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 35 5 Brocade Virtual ADX on XenServer: installation b. Click Add Network. FIGURE 12 XenCenter: New Network type Brocade Virtual ADX uses two of the four network types supported on the XenServer platform: • Single-Server Private Network • External Network Single-Server Private Network - This type of network has no physical NIC connectivity and is used to establish an internal virtual switch for connecting the virtual interfaces of VMs on the XenServer host. Create a “Single-Server Private Network” for each Brocade Virtual ADX data port that does not need physical NIC connectivity. If none of the three Brocade Virtual ADX data ports require physical NIC connectivity, then create three networks of this type; one for each data port. NOTE For a data port that does not need physical NIC connectivity but needs to be on one or more VLANs, create a “Single-Server Private Network” and use the OVS configuration for VLAN support described in “VLAN configuration using OpenvSwitch” on page 43. External Network - This type of network is equivalent to a VLAN access port on a hardware switch. An “External Network” passes traffic over the VLAN it is configured with and provides connectivity to a physical NIC. Create an “External Network” for each Brocade Virtual ADX data port that needs to be on a single VLAN and connected to a physical NIC. NOTE If a data port needs to be on more than one VLAN with physical NIC connectivity, it needs to use a default network (Network 0, Network 1, etc.) created by XenServer on bootup and to use the OVS configuration for VLAN support described in “VLAN configuration using OpenvSwitch” on page 43. 36 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX on XenServer: installation c. Select the type of network that you want to create and click Next to provide a Name and Description for the new network. FIGURE 13 d. 5 XeCenter: New Network name After entering a name and description for the new network, click Next. i. If you are creating a Single-Server Private Network (Step 3.c above), the following window will display showing the network that you have just created. If you need to add another network, return to Step 3. If you have created all the networks required by the Brocade Virtual ADX VM, proceed to Step 4. FIGURE 14 XenCenter: Server Networks - new single-server network Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 37 5 Brocade Virtual ADX on XenServer: installation ii. If you are creating an External Network (Step 3.c above), the following window will display. Choose the physical NIC this network will connect with and specify the VLAN ID. FIGURE 15 i. XenCenter: External Network configuration Click Finish. The following window will display showing the new external network that you have just created. If you need to add another network, return to Step 3. FIGURE 16 XenCenter: Server Networks - new external network 4. Deploy Brocade Virtual ADX. 38 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX on XenServer: installation a. Right click on the XenServer listed on the left panel and select Import as shown below. FIGURE 17 b. 5 XenCenter: Import network The Import window displays. Select the OVA file and click Next. FIGURE 18 XenCenter: Select OVA file Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 39 5 Brocade Virtual ADX on XenServer: installation c. Select the default options until you arrive at the Networking section. In the Networking section you will map the the Brocade Virtual ADX VM’s virtual network interfaces to the XenServer Target Networks. d. Map the Brocade Virtual ADX virtual network interfaces to XenServer host networks, as shown in the Import OVF/OVA Package window below: i. Select one of the XenServer default networks for Ethernet 1. (eth0 on Brocade Virtual ADX) If the XenServer host has only one physical NIC, choose Network 0. ii. Select one of the XenServer default networks for Ethernet 2. (eth1 on Brocade Virtual ADX) Again, if the XenServer host has only one physical NIC, choose Network 0, so that eth1 and eth0 share Network 0. iii. Select a network created in Step 3 above, for each of the three data ports. FIGURE 19 40 XenCenter: Map networks e. Click Next, and select the default options until the Transfer VM Settings section. f. In the Transfer VM Settings section select the Network through which the XenServer host can connect to the OVA file location and provide a static IP address if that network does not have a DHCP server running. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX on XenServer: installation 5 NOTE The static IP address is only needed until the Brocade Virtual ADX VM deployment completes. It is not related to the eth0 or eth1 IP assignments. FIGURE 20 XenCenter: Transfer VM settings g. Click Next. h. Complete the rest of the deployment with default options and click Finish. XenServer automatically generates locally administered MAC addresses for the virtual interfaces as specified in the OVA file. Locally administered addresses are MAC addresses with the second least-significant bit of the most significant byte set. Locally administered MAC addresses are typically assigned by a user to devices that lack a manufacturer-specific encoding known as the Organizationally Unique Identifier (OUI). Typically, manufacturers "burn-in" MAC addresses in which the first three octets indicate the device manufacturer. The locally administered MAC addresses generated by XenServer will not clash with addresses from hardware devices on your network. XenServer generates MAC addresses at random, based on the VM.otherconfig:mac-seed parameter of the VM and the device number of the virtual interface (a sequence number for the VIF in the range 0 - 6). NOTE A particular combination of a MAC seed and device number always results in the same MAC address. Therefore, if you remove a virtual interface from a VM and recreate it later, the new virtual interface will get the same MAC address as before. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 41 5 Brocade Virtual ADX on XenServer: installation validation MAC addresses can also be assigned manually after completing the Brocade Virtual ADX VM deployment. To assign MAC addresses manually, select the Networking tab, and modify the virtual network interfaces properties as shown below. FIGURE 21 XenCenter: Manual assignment of Brocade Virtual ADX VM MAC addresses Brocade Virtual ADX on XenServer: installation validation You can execute the following steps to ensure that the Brocade Virtual ADX is installed correctly: 1. Power on and login to the Brocade Virtual ADX VM. 2. Enter the following command to access the Brocade Virtual ADX console: [user@VirtualADX ~]# vadx-console 3. Use the show interfaces command to verify that three data ports and a management port are configured. For example: [user@VirtualADX ~]# show interface brief Port 1 2 3 mgmt1 42 Link Up Up Up Up State Forward Forward Forward Forward Dupl Full Full Full Full Speed 1G 1G 1G 1G Trunk None None None None Tag No No No No Priori level0 level0 level0 level0 MAC Name 7698.1515.bc52 863a.8bd5.ed4f faef.f725.15c7 fa2d.4b10.6b02 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 VLAN configuration using OpenvSwitch 5 VLAN configuration using OpenvSwitch The Openvswitch(OVS) network backend supports configuration of ports on multiple VLANs. Once the Brocade Virtual ADX VM is booted and OVS chosen as the network backend, you can use OVS CLIs to confgure VLANs on the Brocade Virtual ADX ports via SSH login or the XenCenter Console. ifconfig will list the ovs-bridges and ovs-ports created on the XenServer host that correspond to the “Networks” and “Virtual network interfaces” configured on the XenCenter GUI. The default networks on XenCenter (Network 0, Network 1 etc.) correspond to ovs-bridges (xenbr0, xenbr1 etc.). Other newly-created networks also correspond to ovs-bridges and are named xapi0, xapi1, xapi2 etc. The virtual interfaces of VMs correspond to ovs-ports and are named vif1.1, vif1.2, vif2.1 etc. For example, were a virtual interface is named “vif1.2” the number “1” identifies the VM and remains the same for all virtual interfaces belonging to a particular VM, while the number “2” identifies the interface index within the VM. Mapping a XenCenter Network to an ovs-bridge Use the following OVS commands to identify the ovs-bridge corresponding to a network on the XenCenter GUI: 1. The following command takes the Network name specified in the XenCenter GUI as input and lists the network uuid. [root@xenserver ~]# xe network-list name-label=<network-name> 2. Input the network uuid into the following command to list the ovs-bridge corresponding to the XenCenter GUI Network. [root@xenserver ~]# ovs-vsctl -- --columns=name find interface external_ids:xs-network-uuid=<network uuid> Mapping XenCenter VM Virtual Interfaces to ovs-ports Use the following OVS commands to identify the ovs-ports corresponding to the Brocade Virtual ADX VM’s virtual interfaces created on the XenCenter GUI. 1. The following command takes the VM name specified on the XenCenter GUI as input and lists the VM’s uuid. [root@xenserver ~]# xe vm-list name-label=sivadx-centos-xvda | grep uuid 2. Input the VM uuid into the following command to list the ovs-ports corresponding to Brocade Virtual ADX Virtual Interfaces configured on the XenCenter GUI [root@xenserver ~]# ovs-vsctl -- --columns=name find interface external_ids:xs-vm-uuid=<VM uuid> Configuring VLANs Once you have identified the ovs-bridge and ovs-port mappings, you can configure VLANs on ovs-ports corresponding to the Brocade Virtual ADX data ports. OVS supports the following VLAN modes on ovs-ports: Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 43 5 VLAN configuration using OpenvSwitch • trunk - a trunk port carries packets on one or more specified VLANs. A packet that ingresses on a trunk port is in the VLAN specified in its 802.1Q header or VLAN 0 if the packet has no 802.1Q header. A packet that egresses through a trunk port will have an 802.1Q header if it has a non-zero VLAN ID. Any packet that ingresses on a trunk port tagged with a VLAN that the port does not trunk is dropped. • access - an access port carries packets on exactly one specified VLAN. Packets egressing on an access port do not have an 802.1Q header. Any packet with an 802.1Q header and a non-zero VLAN ID that ingresses on an access port is dropped, regardless of whether the VLAN ID in the header is the access port’s VLAN ID. • native-tagged - a native-tagged port resembles a trunk port, with the exception that a packet without an 802.1Q header that ingresses on a native-tagged port is in the ‘‘native VLAN’’ (specified in the tag field). • native-untagged - a native-untagged port resembles a native-tagged port, with the exception that a packet that egresses on a native-untagged port in the native VLAN will not have an 802.1Q header. To configure a VLAN trunk port, use the following command. [root@xenserver ~]# ovs-vsctl set port <vifx.y> trunks=< vlan-id1, vlan-id2, vlan-id3, vlan-id4,…> To configure a VLAN access port, use the following command. [root@xenserver ~]# ovs-vsctl set port <vifx.y> tag=<vlan-id> To configure a native-tagged port, use the following command. [root@xenserver ~]# ovs-vsctl set port <vifx.y> tag=<Native vlan-id> To configure a native-untagged port, use the following command. [root@xenserver ~]# ovs-vsctl set port <vifx.y> trunks=< vlan-id1, vlan-id2, vlan-id3, vlan-id4,…> Displaying ovs-bridge and ovs-port information Use the following commands to display information about ovs-bridges and ovs-ports. [root@xenserver ~]# ovs-vsctl show [root@xenserver ~]# ovs-vsctl list bridge [root@xenserver ~]# ovs-vsctl list bridge <ovs-bridge name> [root@xenserver ~]#ovs-vsctl list port [root@xenserver ~]# ovs-vsctl list port <ovs-port name> [root@xenserver ~]# ovs-vsctl get port <ovs-port name> tag [root@xenserver ~]# ovs-vsctl get port <ovs-port name> trunks Removing OVS ports The following commands remove ovs-ports. [root@xenserver ~]# ovs-vsctl remove port <ovs-port name> tag <vlan-id> [root@xenserver ~]# ovs-vsctl remove port <ovs-port name> trunks [<vlan-id1> <vlan-id2> <vlan-id3> <vlan-id4>…] 44 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 VLAN configuration using OpenvSwitch Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 5 45 5 46 VLAN configuration using OpenvSwitch Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter Brocade Virtual ADX Basic Network Settings Configuration 6 This section describes how to configure the Brocade Virtual ADX Application Delivery Switch (Brocade Virtual ADX) from Brocade. You will learn how to change the root password for console access, assign an IP address to the Guest OS (system) port, access the Brocade Virtual ADX console via SSH, and assign an IP address to the Brocade Virtual ADX management port. Brocade Virtual ADX root password The initial installation will let you login as root without a password. You must set a password for the root login. Setting the root password You have to be at the Linux prompt to set the root password. From the Brocade Virtual ADX console, execute the following to get to the Linux console and set the root password. VirtualADX> Ctrl-y m [root@Virtual ADX ~]# passwd Changing password for root New password: Reenter new password: Password for root changed by root [root@Virtual ADX ~]# vadx-console The last command will get you back to the Brocade Virtual ADX console. NOTE To get cursor control back from the vSphere console, press Ctrl-Alt. The system will prompt you for a stronger password as appropriate. Brocade Virtual ADX system port IP address Assigning the system port IP address You can assign the system port an IP address as root. You will use this mostly for console access and software upgrades. Execute the following commands to assign the IP address. [root@Virtual ADX ~]# ifconfig eth0 10.24.142.70 netmask 255.255.240.0 [root@Virtual ADX ~]# route add default gw 10.24.128.1 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 47 6 Brocade Virtual ADX console access via Guest OS SSH NOTE You can save the changes by editing the /etc/sysconfig/network-scripts/ifcfg-eth0 file to include the following lines. onboot=yes device=eth0 bootproto=static ipaddr=10.24.142.70 netmask=255.255.240.0 gateway=10.24.128.1 You must reboot the system for these changes to take effect. IP addresses are for illustration purposes only. You can use addresses relevant to your deployment. Although Linux ifconfig command will show eth0 to eth4, please note that eth1 to eth4 are not controlled by Linux. Do not perform any IP address configuration on these ports. Brocade Virtual ADX console access via Guest OS SSH You must have the root password and the system port IP address setup to access the Brocade Virtual ADX console using SSH. You can use one of the popular terminal emulation programs to initiate the session. The following screenshots highlight the initiation and interaction with a Brocade Virtual ADX machine (VADX-1) with a system port address of 10.24.142.70. NOTE You may get to the Linux prompt when connecting through SSH. Use the vadx-console command to get to the Brocade Virtual ADX console. Telnet and AAA services are not supported for console access. 48 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX console access via Guest OS SSH 6 Configuring Brocade Virtual ADX managment port IP address The Brocade Virtual ADX has a default IP address on the management port of 192.168.100.100. You can use this IP address to access the Web GUI application of the Brocade Virtual ADX and to perform various other management functions such as opening a CLI session via Telnet/SSH and SNMP. You can change the IP address to the management port from a Brocade Virtual ADX CLI session. Enter the following commands in the Brocade Virtual ADX console to configure this IP address. Virtual ADX(config)#int management 1 Virtual ADX(config-if-mgmt-1)#ip address 10.24.142.80/20 To configure routes for this interface refer to the section Configuring the management port in the Brocade Virtual ADX Administration Guide . Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 49 6 50 Brocade Virtual ADX console access via Guest OS SSH Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter Brocade Virtual ADX Server Load Balancing Deployments 7 Brocade Virtual ADX common SLB deployments and configurations You can deploy the Brocade Virtual ADX in One-arm and In-line topologies. In the following sections, you will see some examples of these deployments. In the network diagrams shown below, the system and management ports of the Brocade Virtual ADX are connected to a separate vSwitch that provides connectivity to the management network. The system and management ports of the Brocade Virtual ADX do not belong to any VLAN so these ports can receive only untagged traffic. In the example below, the management network is in VLAN 10, hence the port group on the vSwitch is configured to be in VLAN 10. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 51 7 Brocade Virtual ADX common SLB deployments and configurations Server Load Balancing in One-arm topology without VLAN tagging Deploying the Brocade Virtual ADX in the One-arm topology The data ports of the Brocade Virtual ADX, "interface ethernet 1" and "interface ethernet 2" (eth1 and eth2), are untagged members of VLAN 100 and 200 respectively. The corresponding port groups on the vSwitch to which eth1 and eth2 are connected are also configured to be in VLAN 100 and VLAN 200 respectively. The real servers RS1 and RS2 are inside the ESX host. These and other real servers could be inside or outside the ESX host. The vSwitch must be configured to be in the non-promiscuous mode. FIGURE 22 52 Deploying SLB in One-arm topology without VLAN tagging Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX common SLB deployments and configurations 7 Configuring SLB in One-arm topology without VLAN tagging Virtual ADX#config term Virtual ADX(config)#vlan 100 Virtual ADX(config-vlan-100)#untag eth 1 added untagged port ethe 1 to port-vlan 100. Virtual ADX(config-vlan-100)#router-interface ve 1 Virtual ADX(config-vlan-100)#int ve 1 Virtual ADX(config-vif-1)#ip address 192.168.1.9 255.255.255.0 Virtual ADX(config-vif-1)#exit Virtual ADX(config)#vlan 200 Virtual ADX(config-vlan-200)#untag eth 2 added untagged port ethe 2 to port-vlan 200. Virtual ADX(config-vlan-200)#router-interface ve 2 Virtual ADX(config-vlan-200)#int ve 2 Virtual ADX(config-vif-2)#ip address 192.167.1.9 255.255.255.0 Virtual ADX(config-vif-2)#exit Virtual ADX(config)#server real rs1 192.168.1.10 Virtual ADX(config-rs-rs1)#port http Virtual ADX(config-rs-rs1)#exit Virtual ADX(config)#server real rs2 192.167.1.10 Virtual ADX(config-rs-rs2)#port http Virtual ADX(config-rs-rs2)#server virtual v1 192.166.1.10 Virtual ADX(config-vs-v1)#port http Virtual ADX(config-vs-v1)#bind http rs1 http rs2 http Virtual ADX(config-vs-v1)#wr mem Write /opt/ADX/conf/startup-config in progress. Write /opt/ADX/conf/startup-config done. Virtual ADX(config-vs-v1)# Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 53 7 Brocade Virtual ADX common SLB deployments and configurations Server Load Balancing in One-arm topology with VLAN tagging Deploying SLB in One-arm topology with VLAN tagging The example below shows the use of VLAN tagging on the Brocade Virtual ADX to support two or more VLANs using just one data port on the Brocade Virtual ADX. The data port eth1 is a tagged member of two VLANs 100 and 200. The port group to which eth1 is connected is configured to be in VLAN 4095. Using VLAN tagging on eth1 eliminates the need to use other data ports on the Brocade Virtual ADX. The vSwitch must be configured to be in the non-promiscuous mode. FIGURE 23 54 Deploying SLB in One-arm topology with VLAN tagging Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX common SLB deployments and configurations 7 Configuring SLB in One-arm topology with VLAN tagging Virtual ADX#config term Virtual ADX(config)#vlan 100 Virtual ADX(config-vlan-100)#tag eth1 added tagged port ethe 1 to port-vlan 100. Virtual ADX(config-vlan-100)#router-interface ve 1 Virtual ADX(config-vlan-100)#int ve 1 Virtual ADX(config-vif-1)#ip address 192.168.1.9 255.255.255.0 Virtual ADX(config-vif-1)#exit Virtual ADX(config)#vlan 200 Virtual ADX(config-vlan-200)#tag eth 1 added tagged port ethe 1 to port-vlan 200. Virtual ADX(config-vlan-200)#router-interface ve 2 Virtual ADX(config-vlan-200)#int ve 2 Virtual ADX(config-vif-2)#ip address 192.167.1.9 255.255.255.0 Virtual ADX(config-vif-2)#exit Virtual ADX(config)#server real rs1 192.168.1.10 Virtual ADX(config-rs-rs1)#port http Virtual ADX(config-rs-rs1)#exit Virtual ADX(config)#server real rs2 192.167.1.10 Virtual ADX(config-rs-rs2)#port http Virtual ADX(config-rs-rs2)#server virtual v1 192.166.1.10 Virtual ADX(config-vs-v1)#port http Virtual ADX(config-vs-v1)#bind http rs1 http rs2 http Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 55 7 Brocade Virtual ADX common SLB deployments and configurations Server Load Balancing in In-line topology Deploying SLB in In-line topology FIGURE 24 Deploying SLB in In-line topology. Configuring SLB in an In-line topology Virtual ADX#config term Virtual ADX(config)#vlan 100 Virtual ADX(config-vlan-100)#untag eth 1 added untagged port ethe 1 to port-vlan 100. Virtual ADX(config-vlan-100)#router-interface ve 1 Virtual ADX(config-vlan-100)#int ve 1 Virtual ADX(config-vif-1)#ip address 192.168.1.9 255.255.255.0 Virtual ADX(config-vif-1)#exit Virtual ADX(config)#server real rs1 192.168.1.10 Virtual ADX(config-rs-rs1)#port http Virtual ADX(config-rs-rs1)#exit Virtual ADX(config)#server real rs2 192.168.1.11 Virtual ADX(config-rs-rs2)#port http Virtual ADX(config-rs-rs2)#server virtual v1 192.166.1.10 Virtual ADX(config-vs-v1)#port http Virtual ADX(config-vs-v1)#bind http rs1 http rs2 http Virtual ADX(config-vs-v1)#show server bind 56 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Brocade Virtual ADX common SLB deployments and configurations 7 Server Load Balancing in Hot-Standby HA topology NOTE Hot-Standby HA configuration illustrated in the following section is only for ESX. FIGURE 25 SLB Deployment in Hot-Standby HA Topology. vSwitch vSwitch System Management System Management tag 0 v1 ge 1 d v1 Physical Switch (L2/L3) v1 d ge tag 1 Mgmt tag Virtual ADX Mgmt tag d ge v9 99 d ( (HA ) v4 09 5) ge 0 v1 ge tag d vSwitch vSwitch A) (H 5) 99 v409 v9 ( d e g tag v10 0 RS1 v20 ESX host Virtual ADX Data port 0 Data port RS2 ESX host Configuring SLB on the Active Brocade Virtual ADX Virtual ADX-A#config term Virtual ADX-A(config)#vlan 100 Virtual ADX-A(config-vlan-100)#untag eth 1 added untagged port ethe 1 to port-vlan 100. Virtual ADX-A(config-vlan-100)#exit Virtual ADX-A(config)#ip address 192.168.1.9 255.255.255.0 Virtual ADX-A(config)#server real rs1 192.168.1.10 Virtual ADX-A(config-rs-rs1)#port http Virtual ADX-A(config-rs-rs1)#exit Virtual ADX-A(config)#server real rs2 192.168.1.11 Virtual ADX-A(config-rs-rs2)#port http Virtual ADX-A(config-rs-rs2)#server virtual v1 192.168.1.12 Virtual ADX-A(config-vs-v1)#port http Virtual ADX-A(config-vs-v1)#bind http rs1 http rs2 http If the vSwitch is in the non-promiscuous mode, execute the following. Virtual ADX-A(config-vs-v1)#vlan 999 Virtual ADX-A(config-vlan-999)#untag eth 3 added untagged port ethe 3 to port-vlan 999. Virtual ADX-A(config-vlan-999)#server backup eth 3 000c.292a.095c vlan 999 Make sure the virtual switch is configured in non-promiscuous mode. Reload required. Please write memory and then reload or power cycle. Virtual ADX-A(config-vlan-999)# If the vSwitch is in the promiscuous mode, execute the following. Virtual ADX-A(config-vs-v1)#vlan 999 Virtual ADX-A(config-vlan-999)#untag eth 3 added untagged port ethe 3 to port-vlan 999. Virtual ADX-A(config-vlan-999)#server backup eth shared-mac Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 3 000c.292a.095c vlan 999 57 7 Brocade Virtual ADX common SLB deployments and configurations Make sure the virtual switch is configured in promiscuous mode. Reload required. Please write memory and then reload or power cycle. Virtual ADX-A(config-vlan-999)# Configuring SLB on the Standby Brocade Virtual ADX Virtual ADX-B#config term Virtual ADX-B(config)#vlan 100 Virtual ADX-B(config-vlan-100)#untag eth 1 added untagged port ethe 1 to port-vlan 100. Virtual ADX-B(config-vlan-100)#exit Virtual ADX-B(config)#ip address 192.168.1.13 255.255.255.0 Virtual ADX-B(config)#server real rs1 192.168.1.10 Virtual ADX-B(config-rs-rs1)#port http Virtual ADX-B(config-rs-rs1)#exit Virtual ADX-B(config)#server real rs2 192.168.1.11 Virtual ADX-B(config-rs-rs2)#port http Virtual ADX-B(config-rs-rs2)#server virtual v1 192.168.1.12 Virtual ADX-B(config-vs-v1)#port http Virtual ADX-B(config-vs-v1)#bind http rs1 http rs2 http If the vSwitch is in the non-promiscuous mode, execute the following. Virtual ADX-B(config-vs-v1)#vlan 999 Virtual ADX-B(config-vlan-999)#untag eth 3 added untagged port ethe 3 to port-vlan 999. Virtual ADX-B(config-vlan-999)#server backup eth 3 000c.292a.095c vlan 999 Make sure the virtual switch is configured in non-promiscuous mode. Reload required. Please write memory and then reload or power cycle. Virtual ADX-B(config-vlan-999)# If the vSwitch is in the promiscuous mode, execute the following. Virtual ADX-B(config-vs-v1)#vlan 999 Virtual ADX-B(config-vlan-999)#untag eth 3 added untagged port ethe 3 to port-vlan 999. Virtual ADX-B(config-vlan-999)#server backup eth 3 000c.292a.095c vlan 999 shared-mac Make sure the virtual switch is configured in promiscuous mode. Reload required. Please write memory and then reload or power cycle. Virtual ADX-B(config-vlan-999)# Global Server Load Balancing Global Server Load Balancing (GSLB) is a common deployment topology used to manage traffic across one or more datacenters or sites. These sites are often distributed geographically. In this release of the Brocade Virtual ADX, a Brocade GSLB controller configured on an ADX device can now recognize a Brocade Virtual ADX instance as participating in a GSLB site, further increasing the availability of the entire application across datacenters. The GSLB controller can communicate with the Brocade Virtual ADX site as well as other ADX sites at the same time. NOTE The Brocade Virtual ADX currently supports GSLB site-specific functionalities only. RTT is not supported in this release. For steps to configure GSLB Controller and site, refer to the ServerIron ADX Global Server Load Balancing Guide. 58 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter Brocade Virtual ADX Upgrade 8 Brocade Virtual ADX Upgrade You can upgrade Brocade Virtual ADX using one of three methods. • Using a New OVA file • Using the Brocade Virtual ADX CLI • Using Linux and the Brocade Virtual ADX CLI Upgrading Brocade Virtual ADX using a new OVA file 1. Save your existing configuration. NOTE Skip this step if you do not want to apply your existing configuration to the new installation. a. Execute the write memory command from the Brocade Virtual ADX console to save the configuration files such as startup-config and others. Virtual ADX(config)#write memory Write /opt/ADX/conf/startup-config in progress. Write /opt/ADX/conf/startup-config done. Virtual ADX(config)# b. Zip up the files in and under the /opt/ADX/openscripts/ directory. c. Copy the zipped files and the /opt/ADX/conf/startup-config file using scp. 2. Download the new SSx.ova file and follow instructions for a new install. NOTE Skip the next step if you did not save your existing configuration. 3. Copy the saved files to the relevant locations in the Guest OS directory structure from the system console after the installation is complete using scp. Upgrading Brocade Virtual ADX using CLI and management port 1. Download the .gz file from the my.brocade.com site, from the appropriate folder in the Downloads section of the main page. NOTE For detailed instructions on downloading, refer to the Installation section of this guide. 2. Copy the zipped file to the primary or secondary image location using the tftp command. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 59 8 Brocade Virtual ADX Upgrade Virtual ADX# copy tftp file tftp-server-IP Virtual-ADX-gzip-file primary | secondary 3. Enter Ctrl-y m to get to the Linux console. 4. Reboot the Virtual Machine from the Linux prompt to complete the upgrade. [root@VirtualADX misc]# reboot [root@VirtualADX misc]# Broadcast message from root@VirtualADX (/dev/pts/3) at 17:39 ... The system is going down for reboot NOW! [root@VirtualADX misc]# Upgrading Brocade Virtual ADX using Console and system port (Linux) 1. Download the .gz file from the my.brocade.com site from the appropriate folder, in the Downloads section of the main page. NOTE For detailed instructions on downloading, refer to the Installation section of this guide. 2. From the Linux console, copy the downloaded zipped file to the /opt/ADX/misc directory using the SCP command. 3. Change to the /opt/ADX/misc directory, and issue tar xvf Virtual-ADX-gzip-file. [root@VirtualADX ~]# cd /opt/ADX/misc [root@VirtualADX misc]# tar xvf Virtual-ADX-gzip-file 4. Issue the ./install_vadx.sh primary | secondary command to upgrade the image to either the Primary or Secondary image location. [root@VirtualADX misc]# ./install_vadx.sh primary | secondary 5. Reboot the Virtual Machine from the Linux prompt to complete the upgrade. [root@VirtualADX misc]# reboot [root@VirtualADX misc]# Broadcast message from root@VirtualADX (/dev/pts/3) at 17:39 ... The system is going down for reboot NOW! [root@VirtualADX misc]# 60 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Chapter Brocade Virtual ADX Troubleshooting 9 Brocade Virtual ADX troubleshooting Question: I cannot see the cursor on the screen. How do I get cursor control back? If you are in the vSphere console, press Ctrl-Alt to get back cursor control. Question: I have set up my system and am getting a data loop. What can I do? You must associate a different port group for each of the three data ports, eth1, eth2, and eth3. Edit the Virtual Machine properties to ensure that you follow the notes listed in the installation section of this guide. You may also be able to correct this situation by using different VLANs for each port. Question: My system has become unresponsive. Is there something I can do to restart? You can use Ctrl-y l to get a list of all the processes or Ctrl-y m to get to the Linux console to restart the Virtual Machine, if needed. After entering Ctrl-y l, you can select “mp” to get back to the Brocade Virtual ADX CLI session. From the Linux console, you can use the ps -ef command to identify the unresponsive screen utility, which spawned the Brocade Virtual ADX process. Among the processes listed in the output, you will see an output similar to what you see below. root 2151 1 0 01:07 ? 00:00:00 SCREEN -d -m /opt/ADX/bin/task_mgr 2 Use the kill -9 command with the PID to terminate the unresponsive process. Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 61 9 62 Brocade Virtual ADX troubleshooting Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 Appendix Configuration files A guest.xml Following is the content of the guest.xml file. <domain type='kvm'> <name>__Virtual_ADX__</name> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='rhel6.4.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='image_directory/your_sw_adx_qcow_file.qcow2'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <source bridge='br0'/> <target dev='eth0-guests1'/> <model type=’e1000’/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type=’bridge’> <source bridge='br0'/> <target dev='eth0-manage1'/> <model type=e1000/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </interface> <interface type='bridge'> <source bridge='br1'/> <target dev=’eth1-client1'/> Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 63 A guest_ovs.xml <model type=e1000/> <address type='pci' domain='0x0000' bus='0x00' </interface> <interface type='bridge'> <source bridge='br2'/> <target dev='eth2-server1'/> <model type='e1000'/> <address type='pci' domain='0x0000' bus='0x00' </interface> <interface type='bridge'> <source bridge='br3'/> <target dev=’eth3-HA1'/> <model type=’e1000’/> <address type='pci' domain='0x0000' bus='0x00' </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <sound model='ich6'> <address type='pci' domain='0x0000' bus='0x00' </sound> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' </memballoon> </devices> </domain> slot='0x08' function='0x0'/> slot='0x09' function='0x0'/> slot='0x0a' function='0x0'/> slot='0x04' function='0x0'/> slot='0x02' function='0x0'/> slot='0x06' function='0x0'/> guest_ovs.xml Following is the content of the guest_ovs.xml file. <domain type='kvm'> <name>__Virtual_ADX__</name> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='rhel6.4.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> 64 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 guest_ovs.xml A <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='image_directory/your_sw_adx_qcow_file.qcow2'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <source bridge='br0'/> <target dev='eth0-guests1'/> <virtualport type='openvswitch'/> <model type=’e1000’/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type=’bridge’> <source bridge='br0'/> <target dev='eth0-manage1'/> <virtualport type='openvswitch'/> <model type=’e1000’/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </interface> <interface type='bridge'> <source bridge='br1'/> <target dev=’eth1-client1'/> <virtualport type='openvswitch'/> <model type=’e1000’/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </interface> <interface type='bridge'> <source bridge='br2'/> <target dev='eth2-server1'/> <virtualport type='openvswitch'/> <model type=’e1000’/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </interface> <interface type='bridge'> <source bridge='br3'/> <target dev=’eth3-HA1'/> <virtualport type='openvswitch'/> <model type=’e1000’/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <sound model='ich6'> Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01 65 A guest_ovs.xml <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> 66 Brocade Virtual ADX Installation and Deployment Guide 53-1003174-01
© Copyright 2024 ExpyDoc