BIG-IP® Virtual Edition Setup Guide forCitrix® XenServer®

Version 11.1

Table of Contents

Legal Notices.....................................................................................................5

Chapter 1:  Getting Started with BIG-IP Virtual Edition...........................................................7

What is BIG-IP Virtual Edition?..........................................................................................8

BIG-IP Virtual Edition compatibility with XenServer hypervisor products................8

Hypervisor guest definition......................................................................................8

Chapter 2:  Deploying BIG-IP Virtual Edition............................................................................9

Deployment of BIG-IP VE on XenServer..........................................................................10

Host machine requirements and recommendations..............................................10

Deploying the BIG-IP VE virtual machine..............................................................10

Powering on the BIG-IP VE virtual machine..........................................................11

Assigning a management IP address to a BIG-IP VE virtual machine..................12

Chapter 3:  Updating a BIG-IP VE Virtual Machine.................................................................13

About updates to the BIG-IP VE virtual machine.............................................................14

Downloading and importing a BIG-IP VE update..................................................14

Installing a BIG-IP VE update................................................................................14

Rebooting after a BIG-IP VE update.....................................................................15

Upgrading BIG-IP VE from version 10.2.x to 11.1............................................................15

Appendix A: Deployment Best Practices...............................................................................19

Best practices for deploying BIG-IP VE on XenServer.....................................................20

Appendix B: Unsupported BIG-IP Features...........................................................................21

BIG-IP VE unsupported features......................................................................................22

Appendix C: Troubleshooting BIG-IP Virtual Edition.............................................................23

Troubleshooting BIG-IP Virtual Edition.............................................................................24

3

Table of Contents

4

Table of Contents

Legal Notices

Publication Date

This document was published on August 2, 2013.

Publication Number

MAN-0348-01

Copyright

Copyright © 2012, F5 Networks, Inc. All rights reserved.

F5 Networks, Inc. (F5) believes the information it furnishes to be accurate and reliable. However, F5 assumesno responsibility for the use of this information, nor any infringement of patents or other rights of thirdparties which may result from its use. No license is granted by implication or otherwise under any patent,copyright, or other intellectual property right of F5 except as specifically described by applicable userlicenses. F5 reserves the right to change specifications at any time without notice.

Trademarks

3DNS, Access Policy Manager, Acopia, Acopia Networks, Advanced Client Authentication, AdvancedRouting, APM, Application SecurityManager, ARX, AskF5, ASM, BIG-IP, Cloud Extender, CloudFucious,CMP, Data Manager, DevCentral, DevCentral [DESIGN], DNS Express, DSC, DSI, Edge Client, EdgeGateway, Edge Portal, EM, Enterprise Manager, F5, F5 [DESIGN], F5 Management Pack, F5 Networks,F5 World, Fast Application Proxy, Fast Cache, FirePass, Global Traffic Manager, GTM, IBR, IntelligentBrowser Referencing, Intelligent Compression, IPv6 Gateway, iApps, iControl, iHealth, iQuery, iRules,iRules OnDemand, iSession, IT agility. Your way., L7 Rate Shaping, LC, Link Controller, Local TrafficManager, LTM, Message Security Module, MSM, Netcelera, OneConnect, Packet Velocity, ProtocolSecurity Module, PSM, Real Traffic Policy Builder, ScaleN, SSL Acceleration, StrongBox, SuperVIP, SYNCheck, TCP Express, TDR, TMOS, Traffic Management Operating System, TrafficShield, TransparentData Reduction, VIPRION, vCMP, WA, WAN Optimization Manager, WANJet, WebAccelerator, WOM,and ZoneRunner, are trademarks or service marks of F5 Networks, Inc., in the U.S. and other countries,and may not be used without F5's express written consent.

All other product and company names herein may be trademarks of their respective owners.

Patents

This product may be protected by U.S. Patents 6,374,300; 6,473,802; 6,970,733; 7,197,661; 7,287,084;7,975,025; 7,996,886; 8,004,971; 8,010,668; 8,024,483; 8,103,770; 8,108,554; 8,150,957. This list is believedto be current as of August 2, 2013.

Export Regulation Notice

This product may include cryptographic software. Under the Export Administration Act, the United Statesgovernment may consider it a criminal offense to export this product from the United States.

RF Interference Warning

This is a Class A product. In a domestic environment this product may cause radio interference, in whichcase the user may be required to take adequate measures.

FCC Compliance

This equipment has been tested and found to comply with the limits for a Class A digital device pursuantto Part 15 of FCC rules. These limits are designed to provide reasonable protection against harmfulinterference when the equipment is operated in a commercial environment. This unit generates, uses, andcan radiate radio frequency energy and, if not installed and used in accordance with the instruction manual,may cause harmful interference to radio communications. Operation of this equipment in a residential areais likely to cause harmful interference, in which case the user, at his own expense, will be required to takewhatever measures may be required to correct the interference.

Anymodifications to this device, unless expressly approved by themanufacturer, can void the user's authorityto operate this equipment under part 15 of the FCC rules.

Canadian Regulatory Compliance

This Class A digital apparatus complies with Canadian ICES-003.

Standards Compliance

This product conforms to the IEC, European Union, ANSI/UL and Canadian CSA standards applicable toInformation Technology products at the time of manufacture.

6

Legal Notices

Chapter

1Getting Started with BIG-IP Virtual Edition

• What is BIG-IP Virtual Edition?

What is BIG-IP Virtual Edition?

BIG-IP® Virtual Edition (VE) is a version of the BIG-IP system that runs as a virtual machine inspecifically-supported hypervisors (Citrix® XenServer® for this guide). BIG-IP VE emulates ahardware-based BIG-IP system running a VE-compatible version of BIG-IP® software.

Note: The BIG-IP VE product license determines the maximum allowed throughput rate. To view this ratelimit, you can display the BIG-IP VE licensing page within the BIG-IP Configuration utility. Lab editionshave no guarantee of throughput rate and are not supported for production environments.

BIG-IP Virtual Edition compatibility with XenServer hypervisor products

BIG-IP® VE is compatible with Citrix® XenServer® version 5.6 or 5.6 Service Pack 2 usingCitrix®XenCenter® version 5.6 or 5.6 Feature Pack 1.

Hypervisor guest definition

The XenServer virtual machine guest environment for the BIG-IP®Virtual Edition (VE), at minimum, mustinclude:

• 2 x virtual CPUs• 4 GB RAM with a 2-core CPU• 4 x virtual rtl8139-compatible network adapters• 1 x 100 GB IDE disk

Important: Not supplying at least the minimum virtual configuration limits will produce unexpected results.

For production licenses, F5 Networks suggests using the maximum configuration limits for the BIG-IP VEsystem. Reservations can be less for lab editions.

There are also some maximum configuration limits to consider for deploying a BIG-IP VE virtual machine,such as:

• CPU reservation can be up to 100 percent of the defined virtual machine hardware. For example, if thehypervisor has a 3 GHz core speed, the reservation of a virtual machine with 2 CPUs can be only 6 GHzor less.

• RAM reservation can be only 2, 4, or 8 GB.• For production environments, virtual disks should be deployed Thick (allocated up front). Thin

deployments are acceptable for lab environments.

8

Getting Started with BIG-IP Virtual Edition

Chapter

2Deploying BIG-IP Virtual Edition

• Deployment of BIG-IP VE on XenServer

Deployment of BIG-IP VE on XenServer

To deploy the BIG-IP® VE system on a Citrix® XenServer®, you need to perform these tasks:

• Verify the host machine requirements.• Deploy an instance of the BIG-IP system as a virtual machine on a host system.• Power on the BIG-IP VE virtual machine.• Assign a management IP address to the BIG-IP VE virtual machine.

After you complete these tasks, you can log in to the BIG-IP VE system and run the Setup utility. Usingthe Setup utility, you can perform basic network configuration tasks, such as assigning VLANs to interfaces.

Host machine requirements and recommendations

There are specific requirements for the host system to run successfully on the BIG-IP® VE system.

To successfully deploy and run the BIG-IP VE system, the host systemmust contain the following elements:

• XenServer 5.6, 5.6 FP1, or 5.6 SP2• XenCenter®

• Connection to a common NTP source (this is especially important for each host in a redundant systemconfiguration)

• Active DHCP server on the same network as the XenServer host

Important: The hypervisor CPU must meet the following requirements:

• use 64 bit architecture• support for virtualization (AMD-V™ or Intel® VT-x) must be enabled• support a one-to-one thread-to-defined virtual CPU ratio, or (on single-threading architectures) support

at least one core per defined virtual CPU• Intel processors must be from the Core (or newer) workstation or server family of CPUs

Deploying the BIG-IP VE virtual machine

The first steps in deploying BIG-IP® Virtual Edition (VE) are to download and extract the Zip file to yourlocal system. Next, you can run the Deploy OVF Template wizard from within the XenServer XenCenterclient. Note that the Zip file contains a virtual disk image based on an Open Virtual Format (OVF) template.Follow the steps in this procedure to create an instance of the BIG-IP system that runs as a virtual machineon the host system.

Important: Do not modify the configuration of the XenServer guest environment with settings less powerfulthan the ones recommended in this document. This includes the settings for the CPU, RAM, and networkadapters. Doing so might produce unexpected results.

1. In a browser, open the F5 Downloads page (https://downloads.f5.com).2. Download the BIG-IP VE file package ending with ide.ova.zip.3. Extract the files from the Zip archive.4. Before starting the import wizard, review the prospective hypervisor environment for the following.

10

Deploying BIG-IP Virtual Edition

• Make sure a DHCP server is active on the same network as the XenServer host before you start theXenCenter® OVF Appliance.

• Make sure there are no firewall or other restrictions between the required ports for connectivitybetween the XenCenter Client and XenServer. For more information and networking requirements,refer to the XenServer Virtual Machine Installation Guide.

• Make sure enough storage space is available on the XenServer for the BIG-IP virtual machine.

5. Start the XenServer XenCenter client and log in.6. From the XenCenter 5.6 File menu, choose Appliance Import. If you are using XenCenter 5.6 FP1 or

5.6 SP2, click Tools > Virtual Appliance Tools > Import Appliance.The Appliance Import wizard starts.

7. In the Select Appliance pane, click the Browse button. Locate the OVA file.For example: \MyDocuments\Work\Virtualization\<BIG-IP_OVA_filename>

8. Click Next.This displays the End-User License Agreement (EULA).

9. Read and accept the license agreement, and click Next.The Home Server pane opens.

10. In the Home Server pane, select the home server for the BIG-IP VE virtual machine from the list. ClickNext.

11. In the Storage pane, pick the 100 GB storage size and location for the BIG-IP VE virtual machine. ClickNext.

12. In the Network pane, assign the Management, Internal, and External virtual machines to their respectiveTarget Virtual Networks and click Next.

Tip: There is no need to enter MAC addresses, MAC addresses will be assigned automatically.

13. In the Security pane, make sure the Verify Digital Signature check box is not selected. Click Next.14. Map the source network HA to the name of a high-availability network in your inventory. An example

of a destination high-availability network is HA.15. In the Advanced Options pane, make sure theRun Operating System Fixups check box is not selected

and click Next.

Important: The Run Operating System Fixups check box is selected by default.

16. In the Finish pane, scroll down to the highlighted rows and review your settings before continuing. ClickNext.

17. The progress bar and text in the Progress pane will indicate when the BIG-IP virtual machine creationis complete.

Powering on the BIG-IP VE virtual machine

You must power on the BIG-IP® VE virtual machine before you can move on to assigning IP addresses.

1. In the XenCenter® client window, select the Server View.2. Select the virtual machine that you want to power on.3. Click the Start icon.

Note: If you do not see the Start icon, check the tool bar under the View menu.

11

BIG-IP® Virtual Edition Setup Guide for Citrix® XenServer®

The BIG-IP VE status icon changes to indicate that the virtual machine is on. The BIG-IP VE virtualmachine will boot and become ready for configuration.

Assigning a management IP address to a BIG-IP VE virtual machine

The BIG-IP® VE virtual machine needs an IP address assigned to its virtual management port.

1. In the XenCenter® client window, select the Server View.2. In the resources pane, select the virtual machine to which you want to assign the management IP address.3. Click the Console tab.4. After a few seconds, a login prompt appears.

You might need to click the console area and press Enter to activate the console.

5. At the local host login prompt, type root.6. At the password prompt, type default.7. Type config and press Enter.

The F5 Management Port Setup screen appears.8. Click OK.9. If you want DHCP to automatically assign an address for the management port, select Yes. Otherwise,

select No and follow the instructions for manually assigning an IP address and netmask for themanagement port.

Tip: F5 Networks highly recommends that you specify a default route for the virtual management port, butit is not required for operation of the BIG-IP VE virtual machine.

12

Deploying BIG-IP Virtual Edition

Chapter

3Updating a BIG-IP VE Virtual Machine

• About updates to the BIG-IP VE virtualmachine

• Upgrading BIG-IP VE from version 10.2.x to11.1

About updates to the BIG-IP VE virtual machine

BIG-IP® VE updates within the same major version are installed in the same manner as updates to BIG-IPsoftware already installed on BIG-IP hardware. You do not need to reinstall BIG-IP VE in the hypervisorguest environment to upgrade your system. To update a BIG-IP VE virtual machine, you can use the SoftwareManagement tool in the Configuration utility, or you can upgrade the software from the command line. Theupdate procedure described in this guide uses the Software Management tool.

Downloading and importing a BIG-IP VE update

1. In a browser, open the F5 Downloads page (https://downloads.f5.com).2. Download the version's base ISO file, such as 11.1, and its associated MD5 checksum file.

Important: The BIG-IP VE base ISO file for the associated hotfix version must be in the/shared/images directory of the BIG-IP VE virtual machine before any updates can apply.

3. Download the update ISO file, such as Hotfix-BIGIP-11.1.1-511.0-HF3.iso, and its associatedMD5 checksum file.

Attention: Before you perform the installation, F5 recommends testing the integrity of the ISO files toverify that you have downloaded clean copies. Use an MD5 verification program to ensure that thedownloaded ISO files checksums match the values in their corresponding MD5 files.

4. On the Main tab, expand System, and click Software Management.The Software Management screen opens.

5. At the right-side of the screen, click Import.The Import Software Image screen opens.

6. Click Browse to navigate to the downloaded installation file.7. When the image name appears in the Software Image field, click Import to begin the operation.

Important: If you navigate away from this screen before the operation completes, the system might notimport the image successfully. Therefore, F5 recommends that you wait for the operation to completebefore continuing with any other work on the BIG-IP VE system.

The system presents a progress indicator during the operation.

Installing a BIG-IP VE update

After you download the software installation image and import the software image to the /shared/imagesdirectory on the BIG-IP®VE system, you can initiate the installation operation. The destination you specifyfor installation must represent a hard drive volume or partition on the BIG-IP system.

1. On the Main tab of the navigation pane, expand System, and click Software Management.The Software Management screen opens.

2. From the Available Images table, click the link representing the software image you want to install.The image properties screen opens.

14

Updating a BIG-IP VE Virtual Machine

3. In the Installation Targets column, select the check box associated with the location where you want toinstall.

4. Click Install.The installation confirmation screen opens.

5. To begin the installation operation, click Install.The Installation Status screen opens.

6. To watch the progress of the installation operation, click the Refresh button, or specify a value for theAuto Refresh setting.The upgrade process installs the software on the inactive installation location that you specify. Thisprocess usually takes between three and seven minutes.

Tip: If there is a problem during installation, you can use log messages to troubleshoot a solution. Thesystem stores the installation log file as /var/log/liveinstall.log.

When the installation operation is complete, the system removes the refresh options. When that occurs, youcan safely reboot the newly installed volume or partition.

Rebooting after a BIG-IP VE update

When the installation operation is complete, you can safely reboot into the newly installed volume orpartition.

1. On the Main tab of the navigation pane, expand System, and click Software Management.The Software Management screen opens.

2. On the menu bar, click Boot Locations.The Boot Locations screen opens.

3. In the Boot Location column, click the link representing the boot location you want to activate.The properties screen for the boot location opens.

4. Click Activate.A confirmation screen opens.

5. Click OK to initiate the reboot operation.The system presents progress messages during the restart operation.

When the BIG-IP® VE system reboot is complete, the system presents the login screen. To configure thesystem, log in using an account that has administrative permissions.

Upgrading BIG-IP VE from version 10.2.x to 11.1

Follow these steps as specified to upgrade from BIG-IP® VE version 10.2.x to BIG-IP VE version 11.1 thatis available for your hypervisor.

Note: The BIG-IP VE commands in this procedure are run using the BIG-IP command-line interface withinthe hypervisor.

1. Download the base ISO files andMD5 files for versions 10.2.x and version 11.1 from the F5 Downloadspage (https://downloads.f5.com), and verify the downloaded ISO files against their correspondingMD5 files.

15

BIG-IP® Virtual Edition Setup Guide for Citrix® XenServer®

Important: If a 10.2.x hotfix is installed, the 10.2.x and hotfix ISO files can be found in /shared/imageson the BIG-IP VE virtual machine, and will need to be backed up for use later. Be sure to back up thehotfix and 10.2.x ISO files from the virtual machine beforehand to avoid downloading the files again.

2. Save a UCS file offline for the BIG-IP VE system you are upgrading.

Important: An SCF will not suffice for this procedure.

3. Make sure to note the host name for UCS restoration. The command string tmsh list sysglobal-settings hostname will show you the active host name.

4. In the Citrix®XenCenter® client, power off (shut down) the BIG-IP VE virtual machine.5. Take a snapshot and back up your BIG-IP VE virtual machine.6. Under the storage tab for BIG-IP VE, click Click here to create a DVD drive and then pick the ISO

image from your ISO storage repository.7. Under Startup Options, configure the virtual machine to boot from the DVD drive first.8. Select the virtual disk in the list and click Detach. Click OK to confirm the operation.

Important: Use Detach so that the disk is available for recovery purposes.

9. Add a hard disk.a) Under the Storage tab, click Add.b) Name the disk, delegate a size of 100 GB, choose a location for the disk (if necessary), and click

Add.

Caution: Other sizes are not supported and unexpected problems can occur if a size other than 100GB is used.

At this point:

• A CD/DVD drive has been configured to attach when powering on the BIG-IP VE 10.2.x ISO image.• The legacy 40 GB disk was removed.• A new 100 GB disk has been created.

10. Select BIG-IP VE from the inventory screen and click the Start icon.11. You will be prompted for an unattended default installation. Press Enter to continue.

BIG-IP VE version 10.2.2 and later 10.x versions should proceed normally. Versions 10.2.0 and 10.2.1will return the message: No configuration provided for hardware type Z100. Forthese versions, use the command diskinit --style volumes to format the volume and then usethe command image2disk --nosaveconfig --instslot HD1.1 to install the image.This will prepare the disk and automatically install the 10.2.x system onto boot volume HD1.1.

12. When the installation is complete for version 10.2.2 and later, the system prompt shows this message:Remove media, then press [Enter] to reboot. Press Enter to reboot the machine. Forversions 10.2.0 and 10.2.1, type reboot and press Enter.

13. Boot into the 10.2.x BIG-IP VE system.14. Log in to the console and run config to configure the management port's IP address.15. Copy the 10.2.x and 11.1 ISO files to /shared/images.16. If a hotfix was installed, copy the hotfix ISO file to /shared/images and then perform a live installation

of the hotfix onto the system's HD1.2. When finished, reboot into the hotfix image before restoring theUCS.

17. Copy the UCS to /var/local/ucs/ on the BIG-IP VE.

16

Updating a BIG-IP VE Virtual Machine

18. Run the command tmsh modify sys global-settings hostname xxx.xxx, where xxx.xxxis the previously collected host name.

19. Restore the UCS. For example, if the UCS is named webfarm1.ucs and is stored in /var/local/ucs,then the restoration command is tmsh load sys ucs webfarm1.At this point, the system is active with the 10.2.x configuration restored.

20. Perform a live installation of BIG-IP VE 11.1 on the system.21. When the live installation is complete, halt and power off the BIG-IP VE virtual machine.22. Within the hypervisor, open the guest settings for the BIG-IP VE.23. Adjust the memory reservation from 2 GB to 4 GB to match the memory configuration.

Important: BIG-IP VE version 11.1 includes new high-availability features. You should consider addinganother network interface at this point in order to avoid a reboot at a later time.

24. Power on the BIG-IP VE virtual machine.Your BIG-IP VE virtual machine will boot into version 11.1.

17

BIG-IP® Virtual Edition Setup Guide for Citrix® XenServer®

Appendix

ADeployment Best Practices

• Best practices for deploying BIG-IP VE onXenServer

Best practices for deploying BIG-IP VE on XenServer

When deploying BIG-IP® Virtual Edition (VE) on a XenServer host, use these best practices.

RecommendationIssue

Run the two units of an active/standby pair onseparate physical hosts bymanually creating a virtualmachine peer on each host.

Redundant system configuration

Use XenMotion for live migration of BIG-IP® VEvirtual machines on idle virtual machines only. Live

Using XenMotion on live BIG-IP VE virtualmachines

migration of BIG-IP VE while the virtual machineis processing traffic could produce unexpectedresults.

BIG-IP VE is deployed with the hypervisor's defaultresource settings. The CPU reservation can be set

Resource reservations

only to the highest setting of the VCPU priority ofthe virtual machine.

Configure all BIG-IP VE systems to use an externaltime synchronization source. You can do this byconfiguring NTP within BIG-IP VE.

Time synchronization

F5 Networks recommends turning offHyper-Threading Technology when using host

Disable hyper-threading on older processors

machines with Intel® Pentium® 4 era processors.Doing so will prevent possible timing issues withBIG-IP VE.

20

Deployment Best Practices

Appendix

BUnsupported BIG-IP Features

• BIG-IP VE unsupported features

BIG-IP VE unsupported features

BIG-IP® Virtual Edition (VE) does not support specific BIG-IP system or hypervisor features.

BIG-IP features not supported by BIG-IP VE include:

• Optional BIG-IP system modules, such as:

• Link Controller™

• Bridging protocols, such as:

• Spanning Tree Protocol (STP)• Rapid Spanning Tree Protocol (RSTP)• Multiple Spanning Tree Protocol (MSTP)

• Link Aggregation Control Protocol (LACP)• Hard-wired failover• Federal Information Processing Standards (FIPS) 140-2

22

Unsupported BIG-IP Features

Appendix

CTroubleshooting BIG-IP Virtual Edition

• Troubleshooting BIG-IP Virtual Edition

Troubleshooting BIG-IP Virtual Edition

If you have followed the setup procedures as described in this guide, BIG-IP® VE should be workingcorrectly with the hypervisor. However, because BIG-IP VE emulates BIG-IP hardware running in a virtualenvironment, you might encounter some issues as you try new configurations for BIG-IP VE that are outsidethe scope of this setup guide, or unsupported in BIG-IP VE with certain hypervisor environments. Use thistroubleshooting information to solve problems and address limitations that you might encounter with BIG-IPVE.

XenCenter OVF wizard's Run Operating System Fixups option blocks appliance import (ID351367)

When importing the OVA into XenCenter®, make sure the Run Operating System Fixups check boxis not selected.

XenServer reservations should be set (ID 351199)When importing an OVA into XenServer, CPU priority is not set. F5 Networks recommends setting ahigher priority for the virtual machine. To do this, using XenCenter®, click the General tab for thevirtual machine, click Properties, and under the CPU and Memory tab, move the scheduling priorityto the highest setting.

XenServer deployments are not allocated on demand (ID 350143)BIG-IP system deployments will automatically consume 40 GB of space on Thick configured storagerepositories. Utilize Thin deployment strategies on the Storage Repository to make use of allocateon-demand disk allocation strategies.

XenServer allocates less RAM than configured (ID 353416)XenServer virtual machinememory allocations are inclusive of the emulated hardware. A slight differencebetweenmemory allocated andmemory presented to the virtual machine can be noticed. BIG-IP softwarehas been written to accommodate this difference with no adverse effects on traffic.

Configuration of additional interfaces (CR 137616; CR 137621)

When a BIG-IPVE system has been configuredwithmore than five interfaces (onemanagement interfaceand more than four TMM interfaces), the interface numbering might appear out of order. To view theactual portgroup interface mapping, compare the MAC addresses of the interfaces displayed in theBIG-IP Configuration utility to those displayed in the hypervisor client.

If you change the number of virtual interfaces on the BIG-IP VE system after a binary MCPD databasehas been created, the system does not detect the change when subsequently rebooted. To ensure that thesystem properly detects the new or removed interfaces, type the command rm /var/db/mcpd* at theBIG-IP VE command prompt, and reboot the system.

Virtual network interface status is wrong (CR 126854-1)The BIG-IP VE system reports the status of host-only network interfaces as UNINITIALIZED, eventhough the interface is functioning normally.

Auto-licensing and the default management route (CR 133194)If you have not defined a default route to the management port, the default interface 1.1 is used, whichdoes not work. To prevent this from occurring, verify that you have defined a default route for themanagement port before attempting to activate a license.

BIG-IP licensing and User Configuration Sets (CR 138498)When you import a User Configuration Set (UCS) from another BIG-IP system or BIG-IP VE system,the system overwrites the local license with the license contained in the UCS. To work around this issue,you can re-license the local system after importing the UCS by accessing a backup copy of the license

24

Troubleshooting BIG-IP Virtual Edition

file, located in /config/bigip.license.bak. Also, when importing a UCS, ensure that the hostnames of the two systems differ. When the host names differ, the system correctly imports only theconfiguration data that is common to both the originating platform and the target platform. If the hostnames match, the system attempts to import all of the UCS configuration data, which can cause theimport process to fail.

Use of SNMP OID for RMON tables (CR 137905)Setting the source OID for RMON alarm, event, and history tables generates an error message. ThisOID will be disabled in future releases.

Media speed messages in log file (CR 137973)When starting the BIG-IP VE system or when removing an interface from a VLAN, the system logsmedia-related messages to the file /var/log/ltm. You can ignore these messages.

The virtual switch clears the QoS field in 802.1q headers (ID 358996)A hypervisor's Layer 2 bridging device might remove quality of service (QoS) classification frompackets.

25

BIG-IP® Virtual Edition Setup Guide for Citrix® XenServer®

Index

802.1q headers and QoS field, troubleshooting 24

A

active/standby configuration 20active DHCP server 10auto-licensing, troubleshooting 24

B

best practicesfor deployment 20for redundant system configuration 20

BIG-IP import command, troubleshooting 24BIG-IP system modules, unsupported 22BIG-IP Virtual Edition

and XenServer host machine requirements 10updating 14

bridging protocols, unsupported 22

C

Citrix XenCenter, See XenCenter.Citrix XenServer, See XenServer.configuration, editing virtual 24Configuration of additional interfaces, troubleshooting 24CPU

and best practices for 20and guest definition 8and host machine requirements 10deploying BIG-IP VE virtual machine 10

D

default route for virtual management port 12deployment overview 10deployments not allocated on demand, troubleshooting 24DHCP server 10downloads

and importing update 14–15of ISO base file 14–15of ISO update file 14–15

E

environment, for guest 8

F

failover, hard-wired unsupported 22FIPS, unsupported 22

G

guest environment 8

H

hard-wired failover, unsupported 22host machine, CPU requirements 10hypervisor, See guest environment.hypervisor guest definition 8

I

import command, troubleshooting bigpipe import errors 24installation

rebooting after 15troubleshooting OVF wizard 24

installation operation 14IP address, management port 12iRule, troubleshooting sessionid command for SSL 24ISO file

and location on virtual machine 14downloading 14–15downloading base ISO file 14–15downloading update ISO file 14–15

L

LACP protocol, unsupported 22Layer 2, troubleshooting 24license for BIG-IP system, troubleshooting 24log file

and location 14, 24and media speed messages 14, 24

log inafter updating 15assigning management IP address 12deploying BIG-IP VE virtual machine 10

M

management port IP address, assigning 12maximum allowed throughput rate 8media speed messages in log file, troubleshooting 24MOS bash prompt exiting shell, troubleshooting 24Multiple Spanning Tree Protocol (MSTP), unsupported 22

O

Operating System Fixups, troubleshooting 24OVA file, location 10OVF wizard, troubleshooting 24

P

power-on procedure, virtual machine 11product license 8progress indicator, for update 14protocols

troubleshooting 24unsupported 22

27

Index

Q

QoS, troubleshooting 24

R

RAM, less allocated than configured, troubleshooting 24Rapid Spanning Tree Protocol (RSTP), unsupported 22reboot operation

after updating 15redundant system configuration

and host machine requirements 10and NTP requirement 10deploying 20

resource reservations 20RMON tables and SNMP OID, troubleshooting 24

S

server, active DHCP 10setup utility 10SNMP OID for RMON tables, troubleshooting 24spanning tree protocols, unsupported 22SSL, troubleshooting sessionid command in iRule 24SSL functions, unsupported 22system reboot, See reboot operation.system update procedure 14

T

task listfor deploying on virtual machine 10for deploying on XenServer 10for updating on virtual machine 14

task list (continued)for updating on XenServer 14

troubleshooting 24

U

UCS importing from BIG-IP Virtual Edition Trial, troubleshooting24unsupported features 22update

BIG-IP VE version 10.2.x to 11.1 15downloading and importing 14installing 14

update progress indicator 14user configuration sets for licensing BIG-IP system,troubleshooting 24

V

virtual configuration, and hypervisor guest definition 8virtual guest configuration, editing, troubleshooting 24virtual machine settings 8virtual management port 12virtual network interface status, troubleshooting 24

X

XenCenter, and compatible versions 8XenMotion, using 20XenServer

and compatible versions 8and host system requirements 10

XenServer virtual machinecreating 10

28

Index