Virtual ADX 03100 InstallGuide

53-1003241-01
July 2014
Brocade Virtual ADX

Installation and Deployment Guide
Supporting Brocade Virtual ADX version 03.1.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.
Contents
Preface..................................................................................................................................... 7
Document conventions......................................................................................7
Text formatting conventions.................................................................. 7
Command syntax conventions.............................................................. 7
Notes, cautions, and warnings.............................................................. 8
Brocade resources............................................................................................ 9
Contacting Brocade Technical Support.............................................................9
Document feedback........................................................................................ 10
Brocade Virtual ADX Overview..................................................................................................11

Brocade Virtual ADX features......................................................................... 11
Brocade Virtual ADX Interfaces...................................................................... 11
Typical deployment topologies........................................................................12
Tools supported on Virtual ADX......................................................................12
cURL................................................................................................... 12
Brocade Virtual ADX Installation on ESX host........................................................................... 15

Brocade Virtual ADX in the ESX host environment.........................................15
Brocade Virtual ADX Prerequisites................................................................. 15
Software.............................................................................................. 15
Hardware ............................................................................................15
Brocade Virtual ADX download.......................................................................16
Brocade Virtual ADX installation..................................................................... 16
Brocade Virtual ADX installation validation..................................................... 20
Additional interfaces........................................................................................21
Adding and removing interfaces..........................................................21
Displaying interface information.......................................................... 22
TCP checksum offload.................................................................................... 23
Hardware checksum offload process.................................................. 23
Incoming packets................................................................................ 24
Outgoing packets................................................................................ 24
Enabling or disabling TCP checksum offload......................................24
Brocade Virtual ADX technical help................................................................ 25
VMware tools.................................................................................................. 25
Brocade Virtual ADX Installation on KVM Host..........................................................................27

Brocade Virtual ADX in the KVM host environment........................................ 27
Configuration overview....................................................................................27
Brocade Virtual ADX Prerequisites................................................................. 27
Software.............................................................................................. 27
Hardware ............................................................................................27
Brocade Virtual ADX download.......................................................................28
Installing Virtual ADX VM on KVM host.......................................................... 29
Installing Virtual ADX using virsh command....................................... 29
Installing Brocade Virtual ADX using Virtual Machine Manager
GUI................................................................................................ 30
Powering on the Brocade Virtual ADX................................................ 36
Brocade Virtual ADX Installation and Deployment Guide 3

53-1003241-01
Shutting down the Brocade Virtual ADX........................................... 36
Configuring the guest OS IP address............................................... 37
Additional interfaces......................................................................................37
Adding and removing interfaces........................................................37
Displaying interface information........................................................ 39
TCP checksum offload.................................................................................. 39
Incoming packets.............................................................................. 40
Outgoing packets.............................................................................. 40
Enabling or disabling TCP checksum offload................................... 40
Brocade Virtual ADX Installation on Citrix XenServer.............................................................. 41

Brocade Virtual ADX on XenServer: overview.............................................. 41
Brocade Virtual ADX on XenServer: prerequisites....................................... 41
System requirements........................................................................ 41
Configuration requirements...............................................................42
Brocade Virtual ADX download.....................................................................42
Brocade Virtual ADX on XenServer: installation........................................... 43
Brocade Virtual ADX on XenServer: installation validation........................... 51
VLAN configuration using OpenvSwitch....................................................... 51
Mapping a XenCenter Network to an ovs-bridge.............................. 52
Mapping XenCenter VM Virtual Interfaces to ovs-ports.................... 52
Configuring VLANs............................................................................52
Displaying ovs-bridge and ovs-port information................................ 53
Removing OVS ports........................................................................ 53
Additional interfaces......................................................................................53
Adding and removing interfaces........................................................53
Displaying interface information........................................................ 55
TCP checksum offload.................................................................................. 55
Incoming packets.............................................................................. 56
Outgoing packets.............................................................................. 56
Enabling or disabling TCP checksum offload................................... 56
Brocade Virtual ADX Basic Network Settings Configuration.................................................... 57

Brocade Virtual ADX root password..............................................................57
Setting the root password................................................................. 57
Brocade Virtual ADX management port IP address......................................57
Brocade Virtual ADX console access via Guest OS SSH.............................58
Configuring Brocade Virtual ADX managment port IP address........ 58
Brocade Virtual ADX CLI Access.............................................................................................59

Overview....................................................................................................... 59
Accessing Brocade Virtual ADX....................................................................59
Hypervisor management software.................................................... 59
Network access to the guest OS.......................................................60
Network access to Brocade Virtual ADX...........................................60
Navigating a console CLI session.................................................................61
Single IP address for Management Port....................................................... 62
Accessing Linux console from Brocade Virtual ADX Management
Interface ..................................................................................................62
Executing Linux application commands from Virtual ADX Management
Interface ..................................................................................................62
Linux console access command .................................................................. 63
Configuration Commands ............................................................................ 64
Show commands ..........................................................................................64
Notifications ..................................................................................................65
4 Brocade Virtual ADX Installation and Deployment Guide

53-1003241-01
Brocade Virtual ADX Upgrade.................................................................................................. 67
Brocade Virtual ADX Upgrade........................................................................ 67
Upgrading Brocade Virtual ADX using a new OVA file....................... 67
Upgrading Brocade Virtual ADX using existing binaries..................... 67
Upgrading Brocade Virtual ADX using CLI and management port..... 68
Upgrading Brocade Virtual ADX using Linux console and
management port.......................................................................... 68
Copying the current configuration onto a new target virtual ADX
VM................................................................................................. 69
Brocade Virtual ADX Server Load Balancing Deployments........................................................ 71

Brocade Virtual ADX common SLB deployments and configurations.............71
Server Load Balancing in One-arm topology without VLAN tagging...71
Server Load Balancing in One-arm topology with VLAN tagging........73
Server Load Balancing in In-line topology...........................................74
Server Load Balancing in Hot-Standby HA topology.......................... 75
Global Server Load Balancing............................................................ 76
Brocade Virtual ADX Troubleshooting.......................................................................................77

Brocade Virtual ADX troubleshooting..............................................................77

53-1003241-01
53-1003241-01
Preface
● Document conventions......................................................................................................7
● Brocade resources............................................................................................................ 9
● Contacting Brocade Technical Support.............................................................................9
● Document feedback........................................................................................................ 10
Document conventions
The document conventions describe text formatting conventions, command syntax conventions, and
important notice formats used in Brocade technical documentation.
Text formatting conventions

Text formatting conventions such as boldface, italic, or Courier font may be used in the flow of the text
to highlight specific words or phrases.
Format Description
bold text Identifies command names
Identifies keywords and operands
Identifies the names of user-manipulated GUI elements
Identifies text to enter at the GUI
italic text Identifies emphasis

Identifies variables and modifiers
Identifies paths and Internet addresses
Identifies document titles
Courier font Identifies CLI output

Identifies command syntax examples
Command syntax conventions

Bold and italic text identify command syntax components. Delimiters and operators define groupings of
parameters and their logical relationships.
Convention Description
bold text Identifies command names, keywords, and command options.
italic text Identifies a variable.

53-1003241-01
Notes, cautions, and warnings
Convention Description
value In Fibre Channel products, a fixed value provided as input to a command
option is printed in plain text, for example, --show WWN.
[] Syntax components displayed within square brackets are optional.

Default responses to system prompts are enclosed in square brackets.
{x|y|z} A choice of required parameters is enclosed in curly brackets separated by

vertical bars. You must select one of the options.
In Fibre Channel products, square brackets may be used instead for this
purpose.
x|y A vertical bar separates mutually exclusive elements.
<> Nonprinting characters, for example, passwords, are enclosed in angle

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

Notes, cautions, and warning statements may be used in this document. They are listed in the 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 a stronger note, for example, to alert you when traffic might be
interrupted or the device might reboot.
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.

53-1003241-01
Brocade resources
Brocade resources
Visit the Brocade website to locate related documentation for your product and additional Brocade
resources.
You can download additional publications supporting your product at www.brocade.com. Select the
Brocade Products tab to locate your product, then click the Brocade product name or image to open the
individual product page. The user manuals are available in the resources module at the bottom of the
page under the Documentation category.
To get up-to-the-minute information on Brocade products and resources, go to MyBrocade. You can
register at no cost to obtain a user ID and password.
Release notes are available on MyBrocade under Product Downloads.
White papers, online demonstrations, and data sheets are available through the Brocade website.
Contacting Brocade Technical Support

As a Brocade customer, you can contact Brocade Technical Support 24x7 online, by telephone, or by e-
mail. Brocade OEM customers contact their OEM/Solutions provider.
Brocade customers
For product support information and the latest information on contacting the Technical Assistance
Center, go to http://www.brocade.com/services-support/index.html.
If you have purchased Brocade product support directly from Brocade, use one of the following methods
to contact the Brocade Technical Assistance Center 24x7.
Online Telephone E-mail
Preferred method of contact for non- Required for Sev 1-Critical and Sev support@brocade.com
urgent issues: 2-High issues:
Please include:
• My Cases through MyBrocade • Continental US: 1-800-752-8061
• Problem summary
• Software downloads and licensing • Europe, Middle East, Africa, and
• Serial number
tools Asia Pacific: +800-AT FIBREE
(+800 28 34 27 33) • Installation details
• Knowledge Base
• For areas unable to access toll • Environment description
free number: +1-408-333-6061
• Toll-free numbers are available in
many countries.
Brocade OEM customers

If you have purchased Brocade product support from a Brocade OEM/Solution Provider, contact your
OEM/Solution Provider for all of your product support needs.
• OEM/Solution Providers are trained and certified by Brocade to support Brocade® products.
• Brocade provides backline support for issues that cannot be resolved by the OEM/Solution Provider.

53-1003241-01
Document feedback
• Brocade Supplemental Support augments your existing OEM support contract, providing direct
access to Brocade expertise. For more information, contact Brocade or your OEM.
• For questions regarding service levels and response times, contact your OEM/Solution Provider.
Document feedback
To send feedback and report errors in the documentation you can use the feedback form posted with
the document or you can e-mail the documentation team.
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 www.brocade.com.
• By sending your feedback to documentation@brocade.com.
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.

53-1003241-01
Brocade Virtual ADX Overview
● Brocade Virtual ADX features......................................................................................... 11

● Brocade Virtual ADX Interfaces...................................................................................... 11
● Typical deployment topologies........................................................................................12
● Tools supported on Virtual ADX......................................................................................12
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.
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 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 four virtual NICs by default. The first virtual NIC assigned to the Brocade
Virtual ADX is used as the management interface to access the guest OS (Linux) and the management
functions of the Brocade Virtual ADX. The subsequent virtual NICs are used as data interfaces by the
Brocade Virtual ADX for Layer 4 and Layer 7 forwarding.
The management interface is named mgmt1 on the guest OS. You can configure this interface from the
guest OS. This interface is also visible to the Brocade Virtual ADX software with the same name. The
data interfaces are not visible to the guest OS because the Brocade Virtual ADX software controls these
interfaces.
NOTE
Guest OS, Linux and CentOS are used interchangeably in this document.
In the Brocade Virtual ADX software, the data interfaces are named as follows.

53-1003241-01
Typical deployment topologies
• interface mgmt 1: This interface is mgmt1 in the guest OS.

• interface ethernet 1: This interface is not visible to the guest OS.
The data interfaces in the Brocade Virtual ADX software are numbered in the order that the virtual
NICs are added. You must configure the data interfaces only through the Brocade Virtual ADX
interface commands. The following command on the Brocade Virtual ADX displays the state of the
interfaces.
Virtual ADX (config)#show interface brief

Port Link State Dupl Speed Trunk Tag Priori MAC Name
1 Up Forward Full 10G None No level0 000c.292f.4a21
2 Up Forward Full 10G None No level0 000c.292f.4a2b
3 Up Forward Full 10G None No level0 000c.292f.4a35
mgmt1 Up Forward Full 1G None No level0 000c.292f.4a17
You can add or remove data interfaces from the Brocade Virtual ADX. Refer to Additional interfaces
on page 21 for information on adding and removing interfaces. The minimum and maximum
numbers of data interfaces are 1 and 8 respectively. A minimum of two virtual NICs must be assigned
to the Brocade Virtual ADX.
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 Brocade Virtual ADX Server Load
Balancing Deployments.
Tools supported on Virtual ADX

Brocade Virtual ADX supports the following cURL tool.
cURL
The cURL command line tool is for transferring data using URL syntax. For further information about
cURL, refer to http://curl.haxx.se/.
When 10 successive cURL transactions to an IP address are successful, the Brocade Virtual ADX can
initiate subsequent cURL sessions to the same IP address after waiting approximately two minutes.
However, the Brocade Virtual ADX can initiate cURL sessions for other IP addresses immediately.
NOTE
The Brocade Virtual ADX supports a maximum of 10 cURL sessions simultaneously.
You can run cURL from the Brocade Virtual ADX console. For example:

53-1003241-01
Brocade Virtual ADX Overview
1. Power on and login to the Brocade Virtual ADX VM.

2. Enter the following command to access the Brocade Virtual ADX console.
[user@Virtual ADX ~]# 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 similar to the following.
[user@Virtual ADX ~]# curl 172.21.1.10

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 3 0 3 0 0 1352 0 --:--:-- --:--:-- --:--:-- 3000
Hi
To specify a specific HTML page, enter a command similar to the following.
[user@Virtual ADX ~]# curl http://10.21.1.10/index.html

0 3 0 3 0 0 1108 0 --:--:-- --:--:-- --:--:-- 3000
hi
To specify cURL options (requires the use of quotes), enter a command similar to the following.
[user@Virtual ADX ~]# curl "http://172.21.1.10/index.html --local 1234"

0 3 0 3 0 0 1165 0 --:--:-- --:--:-- --:--:-- 3000
hi
NOTE
If the cURL command specifies more than one word, then these words must be enclosed in quotes.
NOTE
The cURL tool 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 and IPv4 addresses only.

53-1003241-01
cURL

53-1003241-01
Brocade Virtual ADX Installation on ESX host
● Brocade Virtual ADX in the ESX host environment.........................................................15

● Brocade Virtual ADX Prerequisites................................................................................. 15
● Brocade Virtual ADX download.......................................................................................16
● Brocade Virtual ADX installation..................................................................................... 16
● Brocade Virtual ADX installation validation..................................................................... 20
● Additional interfaces........................................................................................................21
● TCP checksum offload.................................................................................................... 23
● Brocade Virtual ADX technical help................................................................................ 25
● VMware tools.................................................................................................................. 25
This section describes how to download and install the 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
By default, the Brocade Virtual ADX requests and reserves the following hardware resources from the
ESX host during configuration.

53-1003241-01
Brocade Virtual ADX download
• 2 Virtual CPUs (minimum 2)

• 4 Virtual ports (minimum of 2, one management port and one data port)
NOTE
The minimum memory requirement is dependent on the Brocade Virtual ADX licenses. For more
information on minimum memory requirements for the licenses, refer to the Brocade Virtual ADX
Licensing Guide.

You can download a copy of the Brocade Virtual ADX software. Use the following steps to complete
the download.
1. Go to http://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 Brocade 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.

53-1003241-01
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.
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 .

53-1003241-01
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) Reserve minimum storage and compute resources for this instantiation of the Brocade
Virtual ADX.

53-1003241-01
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
For further information about adding or removing interfaces, refer to Additional interfaces on
page 21.
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.
The following is a typical vSphere screenshot for a deployed and powered on Brocade
Virtual ADX.

53-1003241-01
Brocade Virtual ADX installation validation
NOTE
The ESX host associates a default port group (VM Network) with all the Brocade 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.
You should see the following output (or similar) on your screen.
Welcome to Brocade Virtual ADX:

Virtual ADX login:

53-1003241-01
Additional interfaces
Enter root at the prompt. You do not require a password for logging in at this point. You should see
the following prompt.
Virtual ADX>
Execute the following commands.
Virtual ADX>enable
Virtual ADX#serial-number ser_num
Virtual ADX#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 fulfillment.
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.
You can add up to five additional interfaces to the default configuration (four interfaces).
Adding and removing interfaces

Use these steps to add or remove interfaces in an ESX host environment.
1. Shut down the Brocade Virtual ADX.
NOTE
Failure to perform a shutdown prior to adding or removing interfaces, will cause unexpected
behaviour on Brocade Virtual ADX .
2. In the left pane, right-click your Brocade Virtual ADX VM and select Edit Settings to add or remove
an interface as shown in the figure below.

53-1003241-01
Displaying interface information
FIGURE 1 ESX: Add or remove an interface
NOTE
Interfaces must be added in interface number order i.e. 4, 5, 6, 7, 8 and removed in reverse order
i.e. 8, 7, 6, 5, 4. Adding or removing interfaces in any other order will generate a random order of
interfaces on the VM. To ensure proper functioning on the Brocade Virtual ADX, disable (rather than
remove) an interface from the middle of the configured range of interfaces.
3. If you want to add or remove another interface, return to Step 2.
NOTE
Brocade Virtual ADX supports a maximum of nine interfaces. Adding more than nine interfaces will
generate a random order of interfaces on the VM and interfere with normal processing on Brocade
Virtual ADX.
4. Power on and access the Brocade Virtual ADX from the vSphere client to confirm that the interfaces
are now added or removed.
A vSwitch in trunk mode will not cause network loops. To avoid looping in other cases, add one
vSwitch only to each interface.

Use the following steps and commands to display interface information.
1. Logon to your Brocade Virtual ADX.
2. To display information about the interfaces available on a device use the following command.
Virtual ADX# show interface brief
1 Up Forward Full 10G None No level0 000c.2973.098c
2 Up Forward Full 10G None No level0 000c.2973.0996
3 Up Forward Full 10G None No level0 000c.2973.09a0
4 Up Forward Full 10G None No level0 000c.2973.09aa
5 Up Forward Full 10G None No level0 000c.2973.09b4
6 Up Forward Full 10G None No level0 000c.2973.09be
7 Up Forward Full 10G None No level0 000c.2973.09c8
8 Up Forward Full 10G None No level0 000c.2973.09d2
mgmt1 Up Forward Full 10G None No level0 000c.2973.0982

53-1003241-01
TCP checksum offload
To display information about a specific interface, enter a command such as the following:
Virtual ADX# show interface 6
10GigabitEthernet6 is up, line protocol is up

MAC address is 000c.29e9.ee22 (bia 000c.29e9.ee22)
Configured speed auto, actual 10Gbit, configured duplex fdx, actual fdx
Member of L2 VLAN ID 1, port is untagged, port state is FORWARDING
STP configured to ON, priority is level0, flow control enabled
mirror disabled, monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
MTU 1500 bytes, encapsulation ethernet
IPv6 is disabled
300 second input rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
300 second output rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
2 packets input, 120 bytes, 0 no buffer
Received 0 broadcasts, 0 multicasts, 2 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants, DMA received 2 packets
0 packets output, 0 bytes, 0 underruns
Transmitted 0 broadcasts, 0 multicasts, 0 unicasts
0 output errors, 0 collisions, DMA transmitted 0 packets

TCP checksum offload improves performance by offloading 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.
NOTE
For details of where checksum calculation is performed, when virtual and physical NICs have different
TCP checksum offload settings, refer to the hypervisor documentation.
Hardware checksum offload process

The hardware checksum offload process is depicted in the following figure.

53-1003241-01
Incoming packets
FIGURE 2 Hardware checksum offload process
NOTE
Check the network adapter manual to know if it supports the hardware checksum offload functionality.
Incoming packets
Use the VMXNET3 driver which supports incoming packet checksum offload.
Brocade Virtual ADX relies on the network adapter to verify the TCP, UDP and IP checksums for
incoming packets. If the network adapter does not support checksum verification, the Brocade Virtual
ADX software does the checksum verification.
NOTE
If the network adapter returns a TCP, UDP or IP checksum error, the Brocade Virtual ADX software
will also verify the incoming packet, because it is possible that an undetermined fault on the network
adapter caused it to return the checksum error.
Outgoing packets
Use the VMXNET3 driver, which supports outgoing packet checksum offload.
By default, TCP checksum offload is disabled and checksum calculation is performed by the Brocade
Virtual ADX software.
Enabling or disabling TCP checksum offload

Ensure that your network adaptor supports checksum offload prior to enabling TCP checksum offload.

53-1003241-01
Brocade Virtual ADX technical help
1. Enter the configure command to access global configuration mode.

Virtual ADX# configure terminal
2. Use the following command to enable TCP checksum offload.
Virtual ADX(config)# server hw-csum-offload
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.
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 /root/install-tools command.
For more information on the VMware tools, refer to the VMware documentation.

53-1003241-01
VMware tools

53-1003241-01
Brocade Virtual ADX Installation on KVM Host
● Brocade Virtual ADX in the KVM host environment........................................................ 27

● Configuration overview....................................................................................................27
● Brocade Virtual ADX Prerequisites................................................................................. 27
● Installing Virtual ADX VM on KVM host.......................................................................... 29
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 Brocade Virtual ADX.
Configuration overview
The configuration task involves configuring the KVM hypervisor and the Brocade Virtual ADX VM. The
hypervisor configuration involves setting up the network interfaces 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
• 4 GB RAM

53-1003241-01
• Network adaptor with 2 physical ports
By default, the Brocade Virtual ADX requests and reserves the following hardware resources from the
KVM host during configuration.
• 2 virtual CPUs
• 20GB disk space
• 4 virtual ethernet ports
NOTE
Licensing Guide.
NOTE
There must be four virtual ethernet ports defined for a Brocade Virtual ADX VM. Out of this, the first
interface as defined in Brocade Virtual ADX VM becomes mgmt1. This interface is used to access to
the guest VM, and becomes the management interface of the Brocade Virtual ADX. The other
interfaces can be used as data or HA.

You can download a copy of the Brocade Virtual ADX software. Use the following steps to complete
the download.
NOTE
hypervisor support.
9. Select the qcow2 file link and follow the prompts to start the download and save the file.

53-1003241-01
Installing Virtual ADX VM on KVM host
Installing Virtual ADX VM on KVM host

This section describes the steps involved in hosting the Brocade Virtual ADX VM on the KVM host and
the configurations required on the hypervisor, prior to deploying the VM.
Before installing Brocade Virtual 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
• Install the KVM package and bridge utilities. You can use either bridges or OVS bridges to transport
the traffic to the Brocade Virtual ADX on the KVM host. The setup is to have four ports on the
Brocade Virtual ADX to have access to the outside network through three 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 Brocade 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 Brocade Virtual ADX using virsh command, execute the following steps:
1. Copy the sample VM configuration file and the Brocade Virtual ADX qcow2 image to a directory, for
example, /home/user_name on the KVM host.
NOTE
For Open vSwitch (OVS) deployment, use the guest_ovs.xml file.
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 Brocade Virtual ADX deployed. This is to ensure
that each Brocade Virtual ADX has a unique target name for each network port.
For example, the first Brocade Virtual ADX will have target name of mgmt1-manage1, eth1-client1,
eth2-server1 and eth3-HA1. For the second Brocade Virtual ADX deployed, it should be mgmt1-
manage2, eth1-client2, eth2-server2, and eth3-HA2 (i.e.; change <target dev='mgmt1-manage1'/> to
<target dev='mgmt1-manage2'/>).
NOTE
If you do not need to identify ports in Brocade Virtual ADX in the output of the ovs-vsctl show
command, you can remove them from the guest.xml file. When you start Brocade Virtual ADX, the
KVM host will automatically create unique sequentially increasing target names in the OVS, starting
from vnet0, vnet1, etc. Each Brocade Virtual ADX will have four virtual ports created in the OVS.
Therefore, the first Brocade Virtual ADX will have target name ranging from vnet0 to vnet3 and the
second Brocade Virtual ADX will have target names ranging from vnet4 to vnet7 and so on.
5. Change image name from
<source fiile=’/image_directory/your_virtual_adx_qcow_file.qcow2’> to

53-1003241-01
Installing Brocade Virtual ADX using Virtual Machine Manager GUI
<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 four interface entries. For
example,
<interface type=’bridge’>
<source bridge='br0'/>
<virtualport type='openvswitch'/>
<target dev='mgmt1-manage1'/>
<model type=’e1000’/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
NOTE
Ensure that all four 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'/>.
NOTE
For further information about adding or removing interfaces refer to Additional interfaces on page 21
6. Create bridges and OVS ports on the KVM host to enable traffic to the Brocade Virtual ADX.
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 four
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 Brocade Virtual ADX name which you assigned will be displayed in shut off state, in
the list displayed.
Installing Brocade Virtual ADX using Virtual Machine Manager GUI

To deploy Brocade Virtual ADX image using Virtual Machine Manager GUI, execute the following
steps:
1. Copy the Brocade Virtual ADX qcow2 image 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.
3. Click Create new virtual machine button. The New VM dialog box is displayed.

53-1003241-01
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.
5. Enter the complete path to the Brocade Virtual ADX qcow2 image. Alternately, you can use the
Browse button and then click Browse Local to select the Brocade Virtual 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.

53-1003241-01
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.
7. Set the Memory to 2048 MB and CPUs to 2 . Click Forward button to navigate to the next step.
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.

53-1003241-01
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 Brocade Virtual ADX to use the CPU configuration, which might speed up the processing
speed in the guest OS. Ensure that 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.

53-1003241-01
11.To change the network setting for mgmt1 of the Brocade Virtual ADX, select the NIC from the left
menu. The NIC configuration is display on the right panel.

53-1003241-01
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.From the Device model field, select the model as e1000 or virtio and click Apply.
14.Click the Add Hardware button below the left menu. The Add New Virtual Hardware dialog box is
displayed.

53-1003241-01
Powering on the Brocade Virtual ADX
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 or virtio from the Device model dropdown and then click Finish.
17.Repeat step 11 to Step 16 to configure all the NICs. Then, click Apply.
NOTE
For further information about adding or removing interfaces refer to Additional interfaces on page 21
18.Click Begin Installation on top of the left menu to create the Brocade 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 Brocade Virtual ADX

You can start the newly deployed Brocade Virtual 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
Brocade Virtual ADX and select Open to access to the console and select Virtual Machine >
Run , to run the VM.
Shutting down the Brocade Virtual ADX

You can shut down the Brocade Virtual ADX in any of the following ways:

53-1003241-01
Configuring the guest OS IP address
• virsh command: Run the virsh shutdownvadx_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 Brocade Virtual 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 Brocade Virtual ADX for the first time, execute the following steps from the Virtual
Machine Manager console, to configure the guest OS IP address.
1.
NOTE
You must set a root password to use certain services, for example, access using SSH.
Login as root user using the login name "root".
2. Setup the IP address and netmask for the mgmt1 of the Brocade Virtual ADX using vi/etc/sysconfig/
network-scripts/ifcfg-mgmt1 . Make sure it has the following variables available.
NOTE
The Brocade Virtual ADX supports DHCP. By default, DHCP is enabled on mgmt1. If there is a
DHCP server available, it will assign the IP address to the Brocade Virtual ADX.
ONBOOT=yes
DEVICE=mgmt1
BOOTPROTO=static
IPADDR=x.x.x.x
NETMASK=x.x.x.x
GATEWAY=x.x.x.x
TYPE=ETHERNET
Change the IP address and netmask as applicable for your network environment. This mgmt1
interface will be used to remotely access the Brocade Virtual 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.

Use the following steps to add or remove interfaces in a KVM host environment.
1. Shutdown the Brocade Virtual ADX.

53-1003241-01
a) in Linux, open the Virtual Machine Manager application from Application > System
Tools.
b) Right click on Brocade Virtual ADX in the guest VM list and select Open to access to the
console.
c) Select Virtual Machine > Shutdown > Shutdown, to shut down the VM.
NOTE
behavior on Brocade Virtual ADX.
2. Select Show Virtual Hardware Details > Add Hardware to add or remove an interface as shown
in the figure below.
FIGURE 11 KVM: Add or remove an interface
NOTE
3. If you want to add or remove another interface, return to Step 2.

53-1003241-01
NOTE
Virtual ADX.
4. Power on and access the Brocade Virtual ADX to confirm that the interfaces are now added or
removed.


No port name
IPv6 is disabled

network adapter.

53-1003241-01
Incoming packets
NOTE
Incoming packets
TCP checksum offload may be applied to incoming packets.
SR-IOV
Use the ixgbevf driver which supports incoming packet checksum offload.
When checksum verification is not performed by the virtual network adaptor, the Brocade Virtual ADX
software does the checksum verification.
Non SR-IOV
Outgoing packets


53-1003241-01
Brocade Virtual ADX Installation on Citrix XenServer
● Brocade Virtual ADX on XenServer: overview................................................................ 41

● Brocade Virtual ADX on XenServer: prerequisites..........................................................41
● Brocade Virtual ADX on XenServer: installation............................................................. 43
● Brocade Virtual ADX on XenServer: installation validation............................................. 51
● VLAN configuration using OpenvSwitch......................................................................... 51
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.
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.
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
Brocade Virtual ADX will require the following resources:

53-1003241-01
Software
• 2 virtual CPUs
• 20GB disk space
• 4 virtual ethernet ports
NOTE
Licensing Guide.
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

Use the following steps to download a copy of the Brocade Virtual ADX software.
NOTE

53-1003241-01
Brocade Virtual ADX on XenServer: installation
hypervisor support.
9. Select the OVA file link for your host environment and follow the prompts to start the 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 Brocade 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.
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 51.
2. Start the XenCenter client.

53-1003241-01
NOTE
XenCenter client can be downloaded free from http://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 four virtual interfaces.
NOTE
For information about adding or removing interfaces, refer to Additional interfaces on page 21.
• 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 mgmt1 interface
‐ 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.
a) Select the xenserver on left panel as shown in the figure below. Then select the
Networking tab.
FIGURE 12 XenCenter: Server Networks
b) Click Add Network .

53-1003241-01
FIGURE 13 XenCenter: New Network type
Brocade Virtual ADX uses two of the four network types supported on the XenServer
platform:
• 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 51.
• 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 51.
c) Select the type of network that you want to create and click Next to provide a Name and
Description for the new network.

53-1003241-01
FIGURE 14 XenCenter: New Network name
d) After entering a name and description for the new network, click Next .
1. 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 15 XenCenter: Server Networks - new single-server network
2. 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.

53-1003241-01
FIGURE 16 XenCenter: External Network configuration
3. 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 17 XenCenter: Server Networks - new external network
4. Deploy Brocade Virtual ADX.

a) Right click on the XenServer listed on the left panel and select Import as shown below.

53-1003241-01
FIGURE 18 XenCenter: Import network
b) The Import window displays. Select the OVA file and click Next .
FIGURE 19 XenCenter: Select OVA file
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.

53-1003241-01
d) Map the Brocade Virtual ADX virtual network interfaces to XenServer host networks, as
shown in the Import OVF/OVA Package window below:
1. Select one of the XenServer default networks for Ethernet 1 (mgmt1 on Brocade Virtual
ADX). If the XenServer host has only one physical NIC, choose Network 0 .
2. Select a network created in Step 3 above, for each of the three data ports.
FIGURE 20 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.
NOTE
The static IP address is only needed until the Brocade Virtual ADX VM deployment
completes. It is not related to the mgmt1 IP assignment.

53-1003241-01
FIGURE 21 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.
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.

53-1003241-01
Brocade Virtual ADX on XenServer: installation validation
FIGURE 22 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@Virtual ADX ~]# vadx-console
3. Use the show interfaces command to verify that three data ports and a management port are
configured. For example:
[user@Virtual ADX ~]# show interface brief
1 Up Forward Full 1G None No level0 7698.1515.bc52
2 Up Forward Full 1G None No level0 863a.8bd5.ed4f
3 Up Forward Full 1G None No level0 faef.f725.15c7
mgmt1 Up Forward Full 1G None No level0 fa2d.4b10.6b02
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.
The ifconfig command lists 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.

53-1003241-01
Mapping a XenCenter Network to an ovs-bridge
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:
• 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.

53-1003241-01
Displaying ovs-bridge and ovs-port information
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>...]

Use the following steps to add or remove interfaces in a XenServer host environment.
1. Shutdown the Brocade Virtual ADX.
a) Open Citrix XenCenter.
b) Right click on Brocade Virtual ADX in the guest VM list.
c) Select Virtual Machine > Shutdown > Shutdown, to shut down the VM.

53-1003241-01
NOTE
behaviour on Brocade Virtual ADX .
2. Open Citrix XenCenter and select the Brocade Virtual ADX VM from the left menu as shown in the
figure below.
FIGURE 23
3. On the Networking tab, select Add Interface to add an interface or Remove Interface to remove
an interface.
NOTE
Virtual ADX.
4. To add or remove another interface, return to Step 3.
NOTE
5. Verify that the interfaces have been added or removed, by opening Citrix XenCenter again,
selecting the Brocade Virtual ADX VM from the left menu and viewing the available interfaces on
the Networking tab.
A vSwitch in trunk mode will not cause network loops. To avoid looping in other cases, add one
vSwitch only to each interface.

53-1003241-01


No port name
IPv6 is disabled

network adapter.
NOTE

53-1003241-01
Incoming packets
Incoming packets
Brocade Virtual ADX uses e1000 vNICs on the XenServer platform. e1000 vNICs do not support
incoming checksum vierification. The Brocade Virtual ADX software performs TCP checksum
verification on incoming packets.
Outgoing packets


53-1003241-01
Brocade Virtual ADX Basic Network Settings Configuration
● Brocade Virtual ADX root password................................................................................57

● Brocade Virtual ADX management port IP address........................................................57
● Brocade Virtual ADX console access via Guest OS SSH...............................................58
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.
Virtual ADX> 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
The system will prompt you for a stronger password as appropriate.
Brocade Virtual ADX management port IP address

By default, DHCP is enabled on the management (mgmt1) port. If there is a DHCP server available, it
will assign the IP address to the Brocade Virtual ADX.
As root, you can assign an IP address to the management port. You will use this mostly for console
access and software upgrades. Execute the following commands to assign the IP address.
[root@Virtual ADX ~]# ifconfig mgmt1 x.x.x.x netmask x.x.x.0

[root@Virtual ADX ~]# route add default gw x.x.x.1

53-1003241-01
Brocade Virtual ADX console access via Guest OS SSH
You can save the changes by editing the/etc/sysconfig/network-scripts/ifcfg-mgmt1 file

to include the following lines.
IPADDR=x.x.x.x
NETMASK=x.x.x.0
GATEWAY=x.x.x.1
TYPE=ETHERNET
ONBOOT=yes
NOTE
You must reboot the system for these changes to take effect or enter the service network restart
command after making network-related changes.
IP addresses are for illustration purposes only. You can use addresses relevant to your deployment.
Although Linux ifconfig command displays mgmt1, it does not display eth1 to eth3 because they 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 an address of 10.24.142.7 and port number of 2222.
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.
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.
To configure routes for this interface, refer to the Brocade Virtual ADX Administration Guide .

53-1003241-01
Brocade Virtual ADX CLI Access
● Overview......................................................................................................................... 59
● Accessing Brocade Virtual ADX......................................................................................59
● Navigating a console CLI session................................................................................... 61
● Single IP address for Management Port......................................................................... 62
● Accessing Linux console from Brocade Virtual ADX Management Interface .................62
● Executing Linux application commands from Virtual ADX Management Interface ........ 62
● Linux console access command .................................................................................... 63
● Configuration Commands .............................................................................................. 64
● Show commands ............................................................................................................64
● Notifications ....................................................................................................................65
Overview
This section describes how to access the Brocade Virtual ADX command line interface (CLI) and the
Brocade Virtual ADX guest OS (Linux).
Accessing Brocade Virtual ADX

You can access the Brocade Virtual ADX CLI and guest OS through the following.
• Hypervisor management software. This method does not require network connectivity to the Brocade
Virtual ADX console or the guest OS.
NOTE
This software may not be user-friendly due to limited terminal emulation facilities on hypervisor
management tools.
• Network access to the guest OS.
• Network access to the Brocade Virtual ADX.
A single management IP address is shared between the Brocade Virtual ADX and Linux so that you
can connect directly to the CLI when the default Telnet or SSH port is used. For more information on
single management IP address, refer to Single IP address for Management Port on page 62.
Hypervisor management software

You can access a Brocade Virtual ADX CLI session via hypervisor management software such as
vSphere Client on ESX and VMM on KVM. For information about installing Brocade Virtual ADX on
specific hypervisors, refer to Brocade Virtual ADX Installation on ESX host, Brocade Virtual ADX
Installation on KVM Host and Installing Brocade Virtual ADX on Citrix XenServer.

53-1003241-01
Network access to the guest OS
After installation, the Brocade Virtual ADX console lands in the guest OS console. This is a Linux bash
shell. Use the vadx-console command to switch the console to a Brocade Virtual ADX CLI session
where Brocade Virtual ADX commands can be issued. Use Ctrl+y+m to switch back to the Linux shell.
Switch to a Brocade Virtual ADX CLI session from the Linux shell
[root@VirtualADX ~]# vadx-console
Virtual ADX>
Switch to the Linux shell from a Brocade Virtual ADX CLI session
Virtual ADX> ctrl+y+m
[root@VirtualADX ~]#
Network access to the guest OS

You can open an SSH connection to the guest OS on port 2222 after configuring an IP address on the
management port (mgmt1). For further information about configuring an IP address on the
management port, refer to Brocade Virtual ADX console access via Guest OS SSH on page 58.
When an SSH connection is established, you see a Linux bash shell console. Use the vadx-console
command to switch the console to a Brocade Virtual ADX CLI session where Brocade Virtual ADX
commands can be issued. Use Ctrl+y+m to switch back to the Linux shell.
Switch to a Brocade Virtual ADX CLI session from the Linux shell
[root@VirtualADX ~]# vadx-console
Virtual ADX>
Switch to the Linux shell from a Brocade Virtual ADX CLI session
Virtual ADX> ctrl+y+m
NOTE
Only one active Brocade Virtual ADX console CLI session is allowed at any time. A new session
terminates an existing session and the following message will be seen on the terminating session.
Virtual ADX>
[remote detached]
Network access to Brocade Virtual ADX

You can bypass the guest OS and open a direct CLI session with the Brocade Virtual ADX by opening
a Telnet or SSH connection using an IP address configured on the Brocade Virtual ADX. You can use
the management (mgmt1) port IP address or any data port IP address. For further information on
configuring Brocade Virtual ADX IP addresses, refer to the Brocade Virtual ADX Administration Guide.
Use the show ip interface command to view configured IP address information on the Brocade Virtual
ADX.
Virtual ADX# show ip interface
Interface IP-Address OK? Method Status Protocol
Eth 1 11.1.1.1 YES manual up up
Eth mgmt1 10.24.138.146 YES manual up up
This type of CLI session does not involve the guest OS. The Telnet or SSH connection lands directly
in the Brocade Virtual ADX CLI session; not the Linux bash shell. To access Linux shell, use the linux-
console command.

53-1003241-01
Navigating a console CLI session
Switch to the Linux shell from a Brocade Virtual ADX CLI session (Telnet)
telnet@Virtual ADX# linux-console
Entering linux-console mode (session ID: 4)...
[root@VirtualADX ADX]# vadx-console
telnet@Virtual ADX#
NOTE
The Telnet or SSH connection must be authenticated when using the linux-console command.
Otherwise, you will see the following error.
telnet@Virtual ADX#linux-console
Error: For linux-console access, re-login with username/password
telnet@Virtual ADX#
For information on setting up the authentication username and password, refer to the Brocade Virtual
ADX Administration Guide.
Use the show who command to view details about your current CLI session. For example:
telnet@Virtual ADX> show who
Console connections:
established, in config mode
6 minutes 23 seconds in idle
1 established, client ip address 10.70.42.27
you are connecting to this session
2 closed
Telnet connection (outbound):
3 closed
1 closed
2 closed
User:
global: manager
Context: default manager Default Current
telnet@Virtual ADX>
The Brocade Virtual ADX can also be accessed and configured via a web user interface. For more
information, refer to the Brocade Virtual ADX Graphical User Interface Guide.
Navigating a console CLI session

When you are connected to a Brocade Virtual ADX CLI session via the console, you can use keyboard
shortcuts to switch between the management process (MP) and barrel process (BP) .
TABLE 1 Navigating a console CLI session: keyboard shortcuts
Keyboard shortcut Function
Ctrl+y+1 Switch to management process console
Ctrl+y+[2..n] Switch to BP console. Ctrl+y+2 will switch to BP 1.
Ctrl+y+m Switch to Linux shell console. Use the vadx-console

command to go back to Brocade Virtual ADX CLI
session.
Ctrl+y+l List the available process consoles. Highlight the

required entry to switch to that console.
For further information about logging into a BP, refer to the Brocade Virtual ADX Administration Guide.

53-1003241-01
Single IP address for Management Port
Single IP address for Management Port

In order to eliminate the redundancy of reserving two IP address for each ADX device (the IP address
owned by operating system and the IP address owned by the Virtual ADX management interface), this
feature enables the use of single IP address, routing table and ARP table between the Virtual ADX
and Linux guest OS. A single NIC interface is shared between the Virtual ADX management interface
and Linux kernel.
A typical deployment will have four interfaces which include three data ports and one management
port. You can add more data ports based on the requirement.
The Linux interface can be configured in the following three ways (in the order of preference):
• Enable DHCP for configuring IP address and default gateway.
When the Linux boots up, the management interface (mgmt1) gets the IP address and gateway
through the DHCP server. Later on, when the Virtual ADX management interface comes up, it reads
the IP address, MAC address, ARP table and route table from the Linux kernel.
• Edit the /etc/sysconfig/network-scripts/ifcfg-mgmt1 script for configuring static IP addresses and
default gateway. Restart the network interface after editing the above script to retain the port
configuration across the reboots.
• Use ifconfig commands. Reconfigure the port after every reboot.
For more information on configuration commands, refer section Using the Management Port in the
Brocade Virtual ADX Administration Guide.
Accessing Linux console from Brocade Virtual ADX Management

Interface
Authorized users connected to Brocade Virtual ADX management interface via Telnet or SSH can
access the Linux console. As an authorized user, you can access the Linux console using the key
combination "ctrl + y + m" method when connected via a console. When connected through SSH or
Telnet, use the linux-console command. The Linux console considers /opt/ADX/ as the current
working directory. Access is provided only to those users who have provided credentials (username
and password) during the Telnet/SSH login. All user activities are captured using event logs. Session
management functions such as displaying the currently active session, configuring the idle time out
and terminating the active session can be managed from the Brocade Virtual ADX management
interface.
Executing Linux application commands from Virtual ADX

Management Interface
The Virtual ADX CLI supports some Linux commands in privileged mode for your convenience. Use
"Ctrl+c" to interrupt the execution of Linux commands. Following is a list of supported commands:

53-1003241-01
Linux console access command
TABLE 2 List of to be supported Linux commands on Virtual ADX CLI
Linux Command Description
grep Used to search text. It searches the given file for the line
which contains the matching string or words.
more Command to view the contents of a text file, one full

screen at a time.
less Program similar to more, but allows both backward and

forward movement in the file.
cat Reads and display the contents of a file
curl A client to get documents and files from a server or send

documents to a server, using any of the supported
protocols (HTTP, HTTPS, FTP, GOPHER, DICT,
TELNET, LDAP or FILE).
The operands are as per Linux application commands.

Example :
Virtual ADX# grep -i "RS_COUNT" tmpl/predef/GenericLB.xml
<variableName>RS_COUNT</variableName>
<repeater count="RS_COUNT">
<repeater count="RS_COUNT">
Linux console access command

• Accessing Linux console: Execute the linux-console command in privileged more to enter into the
Linux console. When the Linux console mode is accessed, an informational syslog is logged and an
informational banner is displayed.
Virtual ADX# linux-console
Entering Linux console mode (Session ID: 1)...
[root@VirtualADX ADX]#
• Terminate a Linux console session: Execute the following command to terminate an ongoing Linux
console session.
Virtual ADX# linux-console terminate 1
Syntax: linux-console terminate session-id

session-id is the Session ID of the Linux console as displayed in the output from the show linux-
console active-sessions command.
• Terminate a Linux CLI execution: Execute the following command to terminate an ongoing Linux
CLI execution.
Virtual ADX# linux-cli terminate 1
Syntax: linux-cli terminate session-id

session-id is the Session ID of the Linux CLI as displayed in the output from the show linux-cli
active-sessions command.

53-1003241-01
Configuration Commands
Configuration Commands
• Disable Linux console Access: Execute the following command to disable the Linux console
access.
Virtual ADX(config)# linux-console disable
Syntax: [no] linux-console disable

When the Linux console access is disabled, all the active sessions will be terminated.
• Linux console Idle Timeout configuration : Execute the following command to configure the idle
timeout for Linux console access
Virtual ADX(config)# linux-console idle-timeout 60
Syntax: [no] linux-console idle-timeout duration in minutes

Duration in minutes is the argument. The default value is 10 minutes and maximum value is 1440
minutes.
• Linux CLI execution Idle Timeout configuration : Execute the following command to configure
the idle timeout for Linux CLI execution.
Virtual ADX(config)# linux-cli idle-timeout 60
Syntax: [no] linux-cli idle-timeout duration in minutes

Duration in minutes is the argument. The default value is 10 minutes and maximum value is 1440
minutes.
Show commands
Execute the show linux-console active-sessions command to displays the list of active Linux
console sessions
ADX(config)# show linux-console active-sessions
Session ID User Start Time Terminal
1 admin Mar 26 18:15:20 2014 Telnet
2 user1 Mar 26 19:10:40 2014 Telnet
3 user2 Mar 26 20:00:11 2014 SSH
This command has no argument. In the output displayed, Session ID identifies a particular Linux
console session. User is the name of the user who initiated a Linux console. Start Time is the starting
time of the console access.
Execute the show linux-cli active-sessions command to display the list of active Linux CLI execution
sessions:
ADX(config)# show linux-cli active-sessions
Session ID User Start Time Terminal Command
1 Console User Mar 26 18:15:20 2014 Console “grep”
1 admin Mar 26 18:15:20 2014 Telnet “curl http://10.37.53.179

<http://10.37.53.179/> ”
2 user1 Mar 26 19:10:40 2014 Telnet “cat eventlog-bp00 | more”
3 user2 Mar 26 20:00:11 2014 SSH “cat eventlog-mp | less”

53-1003241-01
Notifications
In the output displayed, Session ID identifies a Linux CLI execution session. User is the name of the
user who executed Linux CLI. Start Time is the starting time of the Linux CLI execution.
Notifications
Following are the notifications provided:
• When you initiate a Linux console:
Linux-console initiated (sessionID: 3) from Telnet, src IP IP Address, src MAC MAC
Address
• When you exits Linux console:

Linux console closed by user abc(Session ID: num
• When the Linux console access is enabled:

Linux console access enabled by user abc
• When the Linux console access is disabled:

Linux console access disabled by user abc
• When the Linux console is inactive for more than configured idle-timeout:
Inactive linux-console (session ID: num) terminated
• When you forcefully terminate an active Linux console session:

Linux-console (Session ID: num) accessed by user xyzis forcefully terminated by
user abc
NOTE
To access Linux console, additional information like SSH/Telnet clients IP address and MAC address
can be provided in the logs (if available).

53-1003241-01
Notifications

53-1003241-01
Brocade Virtual ADX Upgrade
● Brocade Virtual ADX Upgrade........................................................................................ 67
Brocade Virtual ADX Upgrade

You can upgrade Brocade Virtual ADX using one of three methods.
• Using a New OVA file
• Using existing binaries
• Using the Brocade Virtual ADX CLI
• Using Linux and the Brocade Virtual ADX CLI
• Copying the current configuration onto a new target Virtual ADX VM
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 existing binaries

To upgrade Brocade Virtual ADX using existing binaries, complete the following steps.
1. Copy the new ssrbin03100.tar.gz to the misc directory using SCP.
scp –P 2222 ssrbin03100dev.tar.gz root@<VM IP ADDRESS>:/opt/ADX/misc
VM IP ADDRESS is the IP address of the management port (Linux) on the Virtual ADX.
2. On the Virtual ADX VM, go to the /opt/ADX/misc directory.

53-1003241-01
Upgrading Brocade Virtual ADX using CLI and management port
3. Un-tar the .gz file using the following command:

tar –xvf ssrbin03100.tar.gz
The following files will appear in the un-tar folder.

• SSB03100dev
• SSR03100dev
• igb_uio03100dev.ko
• install_vadx.sh
• task_mgr03100dev
• virtualadx-init03100dev
4. Run the install script to update your binaries.
./install_vadx.sh <primary/secondary>
NOTE
It is mandatory to enter primary or secondary.
5. Reboot your VM. The new binaries are part of the image now.
Upgrading Brocade Virtual ADX using CLI and management port

1. Download the .gz file from the http://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.
Virtual ADX# copy tftp file 10.10.10.1 ssrbin03100.tar.gz
primary
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@Virtual ADX misc]# reboot
[root@Virtual ADX misc]#
Broadcast message from root@Virtual ADX
(/dev/pts/3) at 17:39 ...
The system is going down for reboot NOW!
[root@Virtual ADX misc]#
Upgrading Brocade Virtual ADX using Linux console and management

port
1. Download the .gz file from the http://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

53-1003241-01
Copying the current configuration onto a new target virtual ADX VM
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]#

Complete the following steps to copy the current configuration onto a new target virtual ADX VM.
1. Run the ./backup.sh <tar file name> in the folder /opt/ADX/tools
NOTE
You can choose the tar file name of your choice. A tar file with the given name is generated.
./backup.sh vadx_3.1_backup generates a tar file called vadx_3.1_backup.tar.gz
2. Copy the tar file on to the target VM in the /opt/ADX/tools directory, where the configuration is to be
copied.
3. Use the ./restore.sh <copied tar file name> to copy the configuration on to the new VM.
./restore.sh vadx_3.1_backup
NOTE
By using the above steps, you effectively copy the entire relevant configuration on to the new VM.
The following folders are excluded as they do not pertain to a new VM installation.
• /opt/ADX/bin
• /opt/ADX/log
• /opt/ADX/tools
• /opt/ADX/pcap
• /opt/ADX/eventlog-mp
• /opt/ADX/evenlog-bpX, where X is the BP number. The number of files will be equal to the number
of BPs

53-1003241-01

53-1003241-01
Brocade Virtual ADX Server Load Balancing Deployments
● Brocade Virtual ADX common SLB deployments and configurations.............................71
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 mgmt1 port of the Brocade Virtual ADX is connected to a
separate vSwitch that provides connectivity to the management network. The mgmt1 port of the
Brocade Virtual ADX does not belong to any VLAN so this port can receive only untagged traffic. In the
example below, the management network is in VLAN 10 configured on the vSwitch.
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.

53-1003241-01
Configuring SLB in One-arm topology without VLAN tagging
FIGURE 24 Deploying SLB in One-arm topology without VLAN tagging
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)#server real rs1 192.168.1.10
Virtual ADX(config-rs-rs1)#port http
Virtual ADX(config-rs-rs1)#exit
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)#

53-1003241-01
Server Load Balancing in One-arm topology with VLAN tagging
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 25 Deploying SLB in One-arm topology with VLAN tagging
Configuring SLB in One-arm topology with VLAN tagging

Virtual ADX(config-vlan-100)#tag eth1
added tagged port ethe 1 to port-vlan 100.
Virtual ADX(config-vlan-200)#tag eth 1
added tagged port ethe 1 to port-vlan 200.

53-1003241-01
Server Load Balancing in In-line topology
Server Load Balancing in In-line topology
Deploying SLB in In-line topology

FIGURE 26 Deploying SLB in In-line topology.
Configuring SLB in an In-line topology


53-1003241-01
Server Load Balancing in Hot-Standby HA topology
Virtual ADX(config-vs-v1)#show server bind
Server Load Balancing in Hot-Standby HA topology
NOTE
Hot-Standby HA configuration illustrated in the following section is only for ESX.
FIGURE 27 SLB Deployment in Hot-Standby HA Topology.
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
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)#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

53-1003241-01
Configuring SLB on the Standby Brocade Virtual ADX

Virtual ADX-A(config-vlan-999)#server backup eth 3 000c.292a.095c vlan 999 shared-
mac
Make sure the virtual switch is configured in promiscuous mode.
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
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)#server backup eth 3 000c.292a.095c vlan 999
Make sure the virtual switch is configured in non-promiscuous mode.
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)#server backup eth 3 000c.292a.095c vlan 999 shared-
mac
Make sure the virtual switch is configured in promiscuous mode.
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

53-1003241-01
Brocade Virtual ADX Troubleshooting
● Brocade Virtual ADX troubleshooting..............................................................................77
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.
Question: The Brocade Virtual ADX failed to boot. What may have occurred?
The Brocade Virtual ADX will not boot due to lack of resources. The console may display appropriate
error messages that are also captured in the eventlog and bootup log files. One of the following
message may be printed when an error is encountered.
• Error: Initialization failed. Minimum number of cores required is 2.
• Error: Initialization failed. Minimum memory required is 2 GB.
Use the following commands for more information:
• The show version and show license commands should provide information about the availabe
license.
• The show bp-status command displays the number of BPs launched and their status.
• The show mem command displays the state of the system memory.
Determine the minimum requirements for your host machine and verify that the machine meets these
requirements.
Question: I am using KVM with OVS and not able to do L2 forwarding. How can I make it to work?
After the VM is deployed, an XML file is saved at /etc/libvirt/qemu/virtual_adx.xml. In this file, make sure
that the interface type and virtualport type are defined correctly for all of the interfaces. If the virtualport
type is not there, you need to add it as shown below.

53-1003241-01
Brocade Virtual ADX Troubleshooting
<interface type='bridge'>
<source bridge='br0'/>
<virtualport type='openvswitch'/>

53-1003241-01

Virtual ADX 03100 InstallGuide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Virtual ADX 03100 InstallGuide

Transféré par

Droits d'auteur :

Formats disponibles

53-1003241-01

Brocade Virtual ADX

Supporting Brocade Virtual ADX version 03.1.00

Brocade Virtual ADX Overview..................................................................................................11

Brocade Virtual ADX Installation on ESX host........................................................................... 15

Brocade Virtual ADX Installation on KVM Host..........................................................................27

Brocade Virtual ADX Installation and Deployment Guide 3

Brocade Virtual ADX Installation on Citrix XenServer.............................................................. 41

Brocade Virtual ADX Basic Network Settings Configuration.................................................... 57

Brocade Virtual ADX CLI Access.............................................................................................59

4 Brocade Virtual ADX Installation and Deployment Guide

Brocade Virtual ADX Server Load Balancing Deployments........................................................ 71

Brocade Virtual ADX Troubleshooting.......................................................................................77

Brocade Virtual ADX Installation and Deployment Guide 5

Text formatting conventions

italic text Identifies emphasis

Courier font Identifies CLI output

Command syntax conventions

Brocade Virtual ADX Installation and Deployment Guide 7

[] Syntax components displayed within square brackets are optional.

{x|y|z} A choice of required parameters is enclosed in curly brackets separated by

x|y A vertical bar separates mutually exclusive elements.

<> Nonprinting characters, for example, passwords, are enclosed in angle

... Repeat the previous element, for example, member[member...].

\ Indicates a “soft” line break in command examples. If a backslash separates

Notes, cautions, and warnings

8 Brocade Virtual ADX Installation and Deployment Guide

Contacting Brocade Technical Support

Online Telephone E-mail

Brocade OEM customers

Brocade Virtual ADX Installation and Deployment Guide 9

10 Brocade Virtual ADX Installation and Deployment Guide

● Brocade Virtual ADX features......................................................................................... 11

Brocade Virtual ADX features

Brocade Virtual ADX Interfaces

Brocade Virtual ADX Installation and Deployment Guide 11

• interface mgmt 1: This interface is mgmt1 in the guest OS.

Virtual ADX (config)#show interface brief

Typical deployment topologies

Tools supported on Virtual ADX

12 Brocade Virtual ADX Installation and Deployment Guide

1. Power on and login to the Brocade Virtual ADX VM.

[user@Virtual ADX ~]# curl 172.21.1.10

To specify a specific HTML page, enter a command similar to the following.

[user@Virtual ADX ~]# curl http://10.21.1.10/index.html

[user@Virtual ADX ~]# curl "http://172.21.1.10/index.html --local 1234"

Brocade Virtual ADX Installation and Deployment Guide 13

14 Brocade Virtual ADX Installation and Deployment Guide

● Brocade Virtual ADX in the ESX host environment.........................................................15

Brocade Virtual ADX in the ESX host environment

Brocade Virtual ADX Prerequisites

Brocade Virtual ADX Installation and Deployment Guide 15

• 2 Virtual CPUs (minimum 2)

Brocade Virtual ADX download

Brocade Virtual ADX installation

16 Brocade Virtual ADX Installation and Deployment Guide

Brocade Virtual ADX Installation and Deployment Guide 17

5. Deploy Brocade Virtual ADX.

18 Brocade Virtual ADX Installation and Deployment Guide

e) Connect the Brocade Virtual ADX to the vSwitch.

Brocade Virtual ADX Installation and Deployment Guide 19

Brocade Virtual ADX installation validation

Welcome to Brocade Virtual ADX:

20 Brocade Virtual ADX Installation and Deployment Guide