53-1003241-01 July 2014 Brocade Virtual ADX Installation and Deployment Guide Supporting Brocade Virtual ADX version 03.1.
© 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.
Contents Preface..................................................................................................................................... 7 Document conventions......................................................................................7 Text formatting conventions.................................................................. 7 Command syntax conventions.............................................................. 7 Notes, cautions, and warnings....................................
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...............................
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.....
Brocade Virtual ADX Installation and Deployment Guide 53-1003241-01
Preface ● Document conventions......................................................................................................7 ● Brocade resources............................................................................................................ 9 ● Contacting Brocade Technical Support.............................................................................9 ● Document feedback........................................................................................................
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.
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.
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.
Brocade Virtual ADX Overview ● Brocade Virtual ADX features......................................................................................... 11 ● Brocade Virtual ADX Interfaces...................................................................................... 11 ● Typical deployment topologies........................................................................................12 ● Tools supported on Virtual ADX....................................................................................
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. interface ethernet 2: This interface is not visible to the guest OS. interface ethernet 3: 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.
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.
cURL 14 Brocade Virtual ADX Installation and Deployment Guide 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....................................................................................
Brocade Virtual ADX download • 2 Virtual CPUs (minimum 2) • 20 GB disk space • 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. Brocade Virtual ADX download You can download a copy of the Brocade Virtual ADX software. Use the following steps to complete the download. 1.
Brocade Virtual ADX Installation on ESX host 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.
Brocade Virtual ADX Installation on ESX host h) Click Finish . You will see a screen similar to the one shown. 5. Deploy Brocade Virtual ADX. a) b) c) d) 18 From the File menu, choose Deploy OVF Template . Follow instructions from the wizard to install from local copy of the OVA file. 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.
Brocade Virtual ADX Installation on ESX host 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. 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. Repeat the above step for each of the remaining Network Adapters .
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.
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.
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.
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.
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.
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 26 Brocade Virtual ADX Installation and Deployment Guide 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 ● Brocade Virtual ADX download.................................................................................
Brocade Virtual ADX download • 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 KVM host during configuration. • 2 virtual CPUs • 20GB disk space • 4 virtual ethernet ports 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.
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.
Installing Brocade Virtual ADX using Virtual Machine Manager GUI . 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 to all four interface entries.
Brocade Virtual ADX Installation on KVM Host FIGURE 3 Create a new VM - Step 1 4. Enter the name of the new guest VM and select Import existing disk image radio button. Then, click Forward button to navigate to the next step. FIGURE 4 Create a new VM - Step 2 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.
Brocade Virtual ADX Installation on KVM Host NOTE If you see a pop up message indicating that the Disk qcow2 image is already in use by another guest, select no to the question "Do you really want to use the disk?". Then, select the one that is not in use. FIGURE 5 Create a new VM - Step 3 7. Set the Memory to 2048 MB and CPUs to 2 . Click Forward button to navigate to the next step. FIGURE 6 Create a new VM - Step 4 8. Select the Customize configuration before install checkbox and click Finish button.
Brocade Virtual ADX Installation on KVM Host FIGURE 7 Create a new VM - Step 5 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.
Brocade Virtual ADX Installation on KVM Host FIGURE 8 Create a new VM - Step 6 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.
Brocade Virtual ADX Installation on KVM Host FIGURE 9 Create a new VM - Step 7 12.Select Specify shared device name from the Source device dropdown and assign a name to the bridge (example: br0) in the Bridge name field. 13.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.
Powering on the Brocade Virtual ADX FIGURE 10 Create a new VM - Step 8 15.Select Network tab on the left menu and then select the host device from the Host device drop down. Alternately, you can select Specify shared device name form the Host device drop down and then enter the name in the Bridge name field. 16.Select the device model as e1000 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.
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.
Brocade Virtual ADX Installation on KVM Host a) b) c) in Linux, open the Virtual Machine Manager application from Application > System Tools. Right click on Brocade Virtual ADX in the guest VM list and select Open to access to the console. Select Virtual Machine > Shutdown > Shutdown, to shut down the VM. NOTE Failure to perform a shutdown prior to adding or removing interfaces, will cause unexpected behavior on Brocade Virtual ADX. 2.
Displaying interface information 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 to confirm that the interfaces are now added or removed. Displaying interface information Use the following steps and commands to display interface information. 1. Logon to your Brocade Virtual ADX. 2.
Incoming packets 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. 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.
Brocade Virtual ADX Installation on Citrix XenServer ● Brocade Virtual ADX on XenServer: overview................................................................ 41 ● Brocade Virtual ADX on XenServer: prerequisites..........................................................41 ● Brocade Virtual ADX download.......................................................................................42 ● Brocade Virtual ADX on XenServer: installation.............................................................
Software • 2 virtual CPUs • 20GB disk space • 4 virtual ethernet ports 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. 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.
Brocade Virtual ADX on XenServer: installation 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.
Brocade Virtual ADX Installation on Citrix XenServer 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.
Brocade Virtual ADX Installation on Citrix XenServer 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.
Brocade Virtual ADX Installation on Citrix XenServer 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.
Brocade Virtual ADX Installation on Citrix XenServer 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.
Brocade Virtual ADX Installation on Citrix XenServer FIGURE 18 XenCenter: Import network b) The Import window displays. Select the OVA file and click Next . FIGURE 19 XenCenter: Select OVA file c) 48 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.
Brocade Virtual ADX Installation on Citrix XenServer 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.
Brocade Virtual ADX Installation on Citrix XenServer FIGURE 21 XenCenter: Transfer VM settings g) h) Click Next . 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.
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.
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.
Displaying ovs-bridge and ovs-port information To configure a VLAN trunk port, use the following command. [root@xenserver ~]# ovs-vsctl set port trunks=< vlan-id1, vlan-id2, vlanid3, vlan-id4,...> To configure a VLAN access port, use the following command. [root@xenserver ~]# ovs-vsctl set port tag= To configure a native-tagged port, use the following command. [root@xenserver ~]# ovs-vsctl set port
Brocade Virtual ADX Installation on Citrix XenServer NOTE Failure to perform a shutdown prior to adding or removing interfaces, will cause unexpected 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 Brocade Virtual ADX supports a maximum of nine interfaces.
Displaying interface information Displaying interface information 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.
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 By default, TCP checksum offload is disabled and checksum calculation is performed by the Brocade Virtual ADX software.
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.
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.
Brocade Virtual ADX CLI Access ● Overview......................................................................................................................... 59 ● Accessing Brocade Virtual ADX......................................................................................59 ● Navigating a console CLI session................................................................................... 61 ● Single IP address for Management Port..................................................................
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.
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.
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.
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.
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.
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 66 Brocade Virtual ADX Installation and Deployment Guide 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.
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 NOTE It is mandatory to enter primary or secondary. 5. Reboot your VM.
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 ...
Copying the current configuration onto a new target virtual ADX VM 70 Brocade Virtual ADX Installation and Deployment Guide 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.
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.
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.
Server Load Balancing in In-line topology Virtual Virtual Virtual Virtual Virtual Virtual Virtual Virtual Virtual ADX(config-vif-2)#exit ADX(config)#server real rs1 192.168.1.10 ADX(config-rs-rs1)#port http ADX(config-rs-rs1)#exit ADX(config)#server real rs2 192.167.1.10 ADX(config-rs-rs2)#port http ADX(config-rs-rs2)#server virtual v1 192.166.1.
Server Load Balancing in Hot-Standby HA topology Virtual Virtual Virtual Virtual Virtual Virtual Virtual ADX(config-rs-rs1)#exit ADX(config)#server real rs2 192.168.1.11 ADX(config-rs-rs2)#port http ADX(config-rs-rs2)#server virtual v1 192.166.1.10 ADX(config-vs-v1)#port http ADX(config-vs-v1)#bind http rs1 http rs2 http 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.
Configuring SLB on the Standby Brocade Virtual ADX Virtual ADX-A(config-vlan-999)#untag eth 3 added untagged port ethe 3 to port-vlan 999. Virtual ADX-A(config-vlan-999)#server backup eth 3 000c.292a.095c vlan 999 sharedmac Make sure the virtual switch is configured in promiscuous mode. Reload required. Please write memory and then reload or power cycle.
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.
Brocade Virtual ADX Troubleshooting 78 Brocade Virtual ADX Installation and Deployment Guide 53-1003241-01