BIG-IP® Virtual Edition Setup Guide for VMware ESX® or ESXi®

Version 10.2.2

........8 BIG-IP Virtual Edition compatibility with VMware hypervisor products..............8 Hypervisor guest definition..............................................................................................................11 Chapter 3:  Updating a BIG-IP VE Virtual Machine................................9 Deployment of BIG-IP VE on VMware..................................................................................................Table of Contents Table of Contents Legal Notices................................10 Host machine requirements and recommendations...................................................................................................................................................................................8 Chapter 2:  Deploying BIG-IP Virtual Edition...........22 3 ..................21 Troubleshooting the BIG-IP Virtual Edition.........................................................................................................................................................................................................17 Best practices for deploying BIG-IP VE on VMware..........................................................................................7 What is BIG-IP Virtual Edition?.................................................................................................................19 BIG-IP VE unsupported features....................................................................................................................................................................................................14 Installing a BIG-IP VE update.....18 Appendix B: Unsupported BIG-IP Features...................................10 Deploying the BIG-IP VE virtual machine................................................................15 Rebooting after a BIG-IP VE update...................13 Updating a BIG-IP VE virtual machine....................5 Chapter 1:  Getting Started with BIG-IP Virtual Edition......................................15 Appendix A: Deployment Best Practices..........................................................20 Appendix C: Troubleshooting BIG-IP Virtual Edition....11 Assigning a management IP address to a BIG-IP VE virtual machine...............................................................10 Powering on the BIG-IP VE virtual machine..........................................14 Downloading and importing a BIG-IP VE update.................

Table of Contents 4 .

CloudFucious. 2012. APM. BIG-IP. Acopia Networks. StrongBox. PSM. LTM. F5 [DESIGN]. or other intellectual property right of F5 except as specifically described by applicable user licenses.. All rights reserved. TrafficShield. Packet Velocity. Application Security Manager. TMOS. Intelligent Browser Referencing. Protocol Security Module. SuperVIP. Transparent Data Reduction. Inc. VIPRION. DSC. DevCentral [DESIGN]. This unit generates. nor any infringement of patents or other rights of third parties which may result from its use. IPv6 Gateway. Advanced Routing. IT agility. Netcelera. (F5) believes the information it furnishes to be accurate and reliable. Link Controller. Acopia. Data Manager. WOM. Intelligent Compression. and ZoneRunner. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. in the U. iRules. F5 Networks. EM. Enterprise Manager. WebAccelerator. AskF5. and . Edge Client. MSM. ARX. DSI. DevCentral. iRules OnDemand. Fast Cache. Traffic Management Operating System. iQuery. F5. F5 Networks. Cloud Extender. vCMP. Trademarks 3DNS. All other product and company names herein may be trademarks of their respective owners. Inc. F5 assumes no responsibility for the use of this information. in which case the user may be required to take adequate measures. GTM. F5 Management Pack.Legal Notices Publication Date This document was published on August 3. However. Publication Number MAN-0347-00 Copyright Copyright © 2012. L7 Rate Shaping. iSession. Export Regulation Notice This product may include cryptographic software. and other countries. iHealth. iControl. Global Traffic Manager. SYN Check. uses. Access Policy Manager. IBR. Message Security Module. WA. Real Traffic Policy Builder. DNS Express.. In a domestic environment this product may cause radio interference. F5 Networks. TCP Express. ASM. WAN Optimization Manager. FirePass. ScaleN. CMP. FCC Compliance This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC rules. Fast Application Proxy. the United States government may consider it a criminal offense to export this product from the United States. copyright. F5 World. iApps. F5 reserves the right to change specifications at any time without notice. Edge Portal. and may not be used without F5's express written consent. SSL Acceleration. Advanced Client Authentication. Local Traffic Manager. are trademarks or service marks of F5 Networks.S. RF Interference Warning This is a Class A product. Your way. OneConnect. No license is granted by implication or otherwise under any patent. Edge Gateway. TDR. WANJet. Under the Export Administration Act. LC. Inc.

Standards Compliance This product conforms to the IEC. can void the user's authority to operate this equipment under part 15 of the FCC rules. at his own expense. in which case the user. 6 .Legal Notices can radiate radio frequency energy and. Operation of this equipment in a residential area is likely to cause harmful interference. Canadian Regulatory Compliance This Class A digital apparatus complies with Canadian ICES-003. if not installed and used in accordance with the instruction manual. may cause harmful interference to radio communications. ANSI/UL and Canadian CSA standards applicable to Information Technology products at the time of manufacture. European Union. will be required to take whatever measures may be required to correct the interference. Any modifications to this device. unless expressly approved by the manufacturer.

Chapter 1 Getting Started with BIG-IP Virtual Edition Topics: • What is BIG-IP Virtual Edition? .

0 and 4. F5 Networks suggests using the maximum configuration limits for the BIG-IP VE system.1. 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.0 and 4. Tip: For production licenses. Lab editions have no guarantee of throughput rate and are not supported for production environments.Getting Started with 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 in specifically-supported hypervisors. BIG-IP Virtual Edition compatibility with VMware hypervisor products BIG-IP® VE is compatible with VMware ESX® 4. • • 8 . BIG-IP VE emulates a hardware-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. you can display the BIG-IP VE licensing page within the BIG-IP Configuration utility. Virtual disk should be deployed Thick (allocated up front). RAM reservation can be only 2 GB or 4 GB.1 hosts. For example. if the hypervisor has a 3 GHz core speed. must include the following: • • • • • 2 x virtual CPUs (reserve 2GHz) 2 GB RAM 1 x virtual Flexible (PCnet32 LANCE) network adapter (for management) 2 x virtual VMXNET3 network adapters 1 x 40 GB SCSI disk Important: Not supplying at least the minimum virtual configuration limits will produce unexpected results. To view this rate limit. at minimum. the reservation of a virtual machine with two CPUs can be only 6 GHz or less. and VMware ESXi® 4. Hypervisor guest definition The VMware virtual machine guest environment for the BIG-IP® VE.

Chapter 2 Deploying BIG-IP Virtual Edition Topics: • Deployment of BIG-IP VE on VMware .

you can log in to BIG-IP VE system and run the Setup utility. you can perform basic network configuration tasks such as assigning VLANs to interfaces. open the F5 Downloads page (https://downloads.1. locate the OVA file. click Deploy from file. 4. the host system must contain the following: • • • VMware ESX 4.1 VMware vSphere Client Connection to a common NTP source (this is especially important for each host in a redundant system configuration) Important: F5 Networks highly recommends that the host system contain CPUs based on AMD-V™ or Intel® VT technology. choose Deploy OVF Template.0 or 4. For example: \MyDocuments\Work\Virtualization\<BIG-IP_OVA_filename> 7. Important: Do not modify the configuration of the VMware guest environment with settings less powerful than the ones recommended in this document. 2. To successfully deploy and run the BIG-IP® VE system. you need to perform the following tasks: • • • • Verify the host machine requirements.0 or 4. This includes the settings for the CPU. The Deploy OVF Template wizard starts. you can run the Deploy OVF Template wizard from within the VMware Vsphere client. 10 . Using the Setup utility. In a browser. Click Next. Power on the BIG-IP VE virtual machine. The OVF Template Details pane opens. using the Browse button. After you complete these tasks. and.Deploying BIG-IP Virtual Edition Deployment of BIG-IP VE on VMware To deploy the BIG-IP® VE system on a VMware ESX® or ESXi®.ova. From the File menu. Note that the Zip file contains a virtual disk image based on an Open Virtual Format (OVF) template. Deploying the BIG-IP VE virtual machine The first steps in deploying BIG-IP® VE are to download and extract the Zip file to your local system. Start the VMware Vsphere client and log in. Follow the steps in this procedure to create an instance of the BIG-IP system that runs as a virtual machine on the host system. Host machine requirements and recommendations There are specific requirements for the host system on which the BIG-IP VE system can run. 5. and network adapters. Assign a management IP address to the BIG-IP VE virtual machine. Extract the files from the Zip archive. 3. Download the BIG-IP VE file package ending with scsi.f5. Doing so may produce unexpected results. or ESXi 4. 6. In the Source pane. Deploy an instance of the BIG-IP system as a virtual machine on a host system. 1.

2. 12. Verify that the OVF template details are correct.BIG-IP® Virtual Edition Setup Guide for VMware ESX® or ESXi® 8. such as: smith_10. click the Administration menu. At the password prompt. After a few seconds. Click the Console tab. In the resources pane. Map the source network Internal Network to the name of a destination non-management network in your inventory. 9. Note that the BIG-IP VE will not process traffic until you start the BIG-IP VE from its command line or through its web interface. select the virtual machine to which you want to assign the management IP address. type a name for the BIG-IP virtual machine. In the Name field. The Name and Location pane opens. Verify that all deployment settings are correct. Select the virtual machine that you want to power on. At the <username> login prompt. From the main vSphere Client screen. click the Administration menu. click No and follow the instructions for manually assigning an IP address and netmask for the management port. 8. 2. 7. This displays the End-User License Agreement (EULA). The Ready to Complete screen opens. In the main vSphere client window. 6. click Yes. 10. 14. select a folder name. and click Next. 2. the Host Cluster screen opens. If you want DHCP to automatically assign an address for the management port. Map the source network External Network to the name of an external network in your inventory. 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. 5. Click the Summary tab. Type config and press Enter. Otherwise. click Power On. 17. The BIG-IP VE status icon changes to indicate that the VM is on. The F5 Management Port Setup screen appears. type root. 1. 15. Read and accept the license agreement. Choose the desired host and click Next. Click OK. type default. Click Next. 11 . 3. Otherwise. 16. An example of a destination internal network is Private Access. 3. An example of a destination external network is Public Access. An example of a destination management network is Management. 13. 1. 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. and in the Commands area. Click Next. and click Next. If the host system is controlled by VMware vCenter. and click Finish. proceed to the next step.2. 4.1-45. 9. 11. Map the source network Management Network to the name of a destination management network in your inventory. In the Inventory Location pane. a login prompt appears.

but it is not required for operation of the BIG-IP VE virtual machine. 12 .Deploying BIG-IP Virtual Edition Tip: F5 Networks highly recommends that you specify a default route for the virtual management port.

Chapter 3 Updating a BIG-IP VE Virtual Machine Topics: • Updating a BIG-IP VE virtual machine .

line. You do not need to reinstall BIG-IP VE in the hypervisor guest environment to upgrade your system.Updating a BIG-IP VE Virtual Machine Updating a BIG-IP VE virtual machine BIG-IP® VE updates are installed in the same manner as updates to BIG-IP software already installed on BIG-IP hardware. 3.1-511. To update a BIG-IP VE virtual machine. Save the four files to the BIG-IP® VE virtual machine in the /shared/images directory. Important: If you navigate away from this screen before the operation completes. The system presents a progress indicator during the operation. F5 recommends that you test the integrity of the ISO files to verify that you have downloaded clean copies. On the Main tab. Downloading and importing a BIG-IP VE update 1. click Import to begin the operation. In a browser. and click Software Management. Download the update ISO file. 14 . The Import Software Image screen opens. 7.0-HF3.iso. The following procedure uses the Software Management tool to perform the upgrade. Attention: Before you perform the installation. expand System. such as Hotfix-BIGIP-10. The Software Management screen opens. click Import. 5. F5 recommends that you wait for the operation to complete before continuing with any other work on the BIG-IP VE system. 2. and its associated MD5 checksum you perform the following tasks: • • • Download and import the version's base and update ISO files. Therefore. 6. or you can upgrade the software from the command line. you can use the Software Management tool in the Configuration utility. 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. Install the update on the BIG-IP VE virtual machine. When the image name appears in the Software Image field. Reboot the BIG-IP VE system.2. Download the version's base ISO file. The update procedure uses the Software Management tool. To update the BIG-IP VE system on a VMware ESX® or ESXi®. such as 10. 8. 4.f5. Click Browse to navigate to the downloaded installation file. Use an MD5 verification program to ensure that the downloaded ISO files checksums match the values in their corresponding MD5 files. the system might not import the image successfully. At the right side of the screen.1. and its associated MD5 checksum file. open the F5 Downloads page (https://downloads.2.

The upgrade process installs the software on the inactive installation location that you specify. The installation confirmation screen opens. the system presents the login screen. In the Boot Partition column. click the link representing the software image you want to install. To begin the installation operation. you can use log messages to troubleshoot a solution. select the check box associated with the location where you want to install. expand System. 2. From the Available Images table. On the menu bar.log. The destination you specify for installation must represent a hard drive volume or partition on the BIG-IP system. The system stores the installation log file as /var/log/liveinstall. The Software Management screen opens. click Boot Locations. the system removes the refresh options. Click OK to initiate the reboot operation. 4. log in using an account that has administrative permissions. The system presents progress messages during the restart operation. click Install. To watch the progress of the installation operation.BIG-IP® Virtual Edition Setup Guide for VMware ESX® or ESXi® Installing a BIG-IP VE update After you download the software installation image and import the software image to the /shared/images directory on the BIG-IP® VE system. The image properties screen opens. you can safely reboot the newly installed volume or partition. and click Software Management. On the Main tab of the navigation pane. 3. The Installation Status screen opens. The Boot Locations screen opens. Tip: If there is a problem during installation. click the link representing the boot location you want to activate. 4. When that occurs. In the Installation Targets column. Rebooting after a BIG-IP VE update When the installation operation is complete. When that occurs. The Software Management screen opens. expand System. 3. Click Activate. click the Refresh button. the system removes the refresh options. you can initiate the installation operation. When the installation operation is complete. 5. you can safely reboot into the newly installed volume or partition. 15 . 2. and click Software Management. or specify a value for the Auto Refresh setting. 5. Click Install. 1. A confirmation screen opens. This process usually takes between three and seven minutes. When the BIG-IP® VE system reboot is complete. On the Main tab of the navigation pane. To configure the system. The properties screen for the boot location opens. 1. 6.

Updating a BIG-IP VE Virtual Machine 16 .

Appendix A Deployment Best Practices Topics: • Best practices for deploying BIG-IP VE on VMware .

Perform live migration of BIG-IP VE virtual machines on idle BIG-IP VE virtual machines only. perform live migration of BIG-IP VE virtual machines (using VMware vMotion™) on idle BIG-IP VE virtual machines only. By default. Disable automatic migrations by adjusting the DRS Automation Level to Partially Automated. these reservations normally prevent system instability on heavily loaded hosts and are considered minimal. You can do this either by configuring NTP within BIG-IP VE or by selecting the Synchronize guest time with host check box within vSphere Client. The CPU reservation can be up to 100 percent of the defined virtual machine hardware. Live migration of BIG-IP VE while the virtual machine (VM) is processing traffic could produce unexpected results. You can accomplish this in two ways: either manually create a virtual machine peer on each host. if the hypervisor has a 3 GHz core speed. if you are using VMware Dynamic Resource Scheduler (DRS). BIG-IP VE is deployed with a 2 GHz CPU and 2 GB of memory reservation. Together. or Disabled on a per VE basis. you should follow these best practices. and configuring all VMware hosts to share a single NTP time server or set of related NTP time servers. Live migration of BIG-IP VE virtual machines VMware DRS environments Resource reservations Time synchronization 18 . For example. In DRS environments. Live migration of BIG-IP VE while the virtual machine is processing traffic could produce unexpected results. to prevent inconsistent system behavior. Issue Redundant system configuration Recommendation Run the two units of an active/standby pair on separate physical hosts. the reservation of a virtual machine with two CPUs can be only 6 GHz or less. Note that units within a redundant system configuration must share a common time synchronization source. create a DRS rule with the option Separate Virtual Machine that includes each unit of the BIG-IP® VE redundant pair.Deployment Best Practices Best practices for deploying BIG-IP VE on VMware When deploying BIG-IP® Virtual Edition (VE) on a VMware host. or. Configure all BIG-IP VE systems to use an external time synchronization source. Manual.

Appendix B Unsupported BIG-IP Features Topics: • BIG-IP VE unsupported features .

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 The following VMware features are not supported by BIG-IP VE: • • VMware Fault Tolerance technology vmmemctl memory balloon driver 20 .Unsupported BIG-IP Features BIG-IP VE unsupported features BIG-IP® VE does not support the following BIG-IP system or hypervisor features. • Optional BIG-IP system modules. such as: • • WebAccelerator™ Bridging protocols. The following BIG-IP® features are not supported by BIG-IP® VE.

Appendix C Troubleshooting BIG-IP Virtual Edition Topics: • Troubleshooting the BIG-IP Virtual Edition .

Time synchronization using If you want to use VMware Tools to enable time synchronization.conf and bigpipe merge bigip_sys. save the bigip. Lack of VMXNET3 availability Use of VLAN groups The VMXNET3 driver can become unavailable after you suspend and resume BIG-IP VE. increase the amount of video RAM allocated to this virtual machine by setting svga. run the commands bigpipe merge bigip. Use the following troubleshooting information to solve problems and learn of limitations that you might encounter with BIG-IP VE. However. The properties of the security policy that you need to configure are Promiscuous Mode and Forged Transmits. and copy the files to the new platform. see the VMware ESX® or ESXi® Configuration Guide. Use of Single Configuration Copying an SCF from a VMware host system to an F5 hardware platform File (SCF) feature causes an error related to interface mismatching.conf and bigip_sys. the following event message is logged: The maximum resolution of the virtual machine will be limited to 1176x885 at 16 bits per pixel. To use the configured maximum resolution of 2360x1770 at 16 bits per pixel.vramSize="16708800" in the virtual machine's configuration file. you might encounter some issues as you try new configurations for BIG-IP VE that are outside the scope of this setup guide or altogether not supported in BIG-IP VE with certain hypervisor environments. the interface numbering might appear out of order. BIG-IP® VE should be working correctly with the hypervisor. Use of VLAN groups with BIG-IP VE requires proper configuration of the VMware vSwitch. you must first disable time synchronization in VMware Tools by clearing the check box within vSphere Client. To work around this issue. You can verify that VMware Tools are installed by viewing the IP Address and DNS Name fields on the vSphere screen. you must configure security policies on the vSwitch. you must VMware Tools or NTP select the Synchronize guest time with host check box within vSphere protocol Client. you must configure these properties to accept (rather than reject) the security policy exceptions on the vSwitch. For any transparency mode other than Opaque. For more information. the status correctly shows as Unmanaged. Resetting the system will resolve the problem. If you want to use network time protocol (NTP) instead. Note that if you migrate the virtual machine or start a snapshot or cloned image of the virtual machine. Configuration of an OVF with additional interfaces When you deploy an OVF with more than five interfaces (one management interface and more than four TMM interfaces). Incorrect status of VMware VMware vSphere incorrectly shows the status of VMware Tools as Not Tools in vSphere Installed. To use the VLAN group feature. Event log reports insufficient video RAM On VMware ESXi systems only.conf. see the VMware vSphere Client documentation. For information about how to configure these options.conf files within BIG-IP VE. You can ignore this message or follow the recommended action without adverse effects. Note that the two units of a BIG-IP VE redundant system configuration must share the same time synchronization source. To view the actual TMM-to-vSwitch portgroup 22 .Troubleshooting BIG-IP Virtual Edition Troubleshooting the BIG-IP Virtual Edition If you have followed the setup procedures in this document. because BIG-IP VE emulates BIG-IP hardware running in a virtual environment. On the new platform.

the system logs media-related messages to the file /var/log/ltm. 23 . which can cause the import process to fail. compare the MAC addresses of the interfaces displayed in the BIG-IP Configuration utility to those displayed in the vSphere Client. Exiting the shell at a MOS When you type exit at a Maintenance Operating System (MOS) prompt. event.BIG-IP® Virtual Edition Setup Guide for VMware ESX® or ESXi® interface mapping. or power off and power on the BIG-IP VE virtual machine to restore functionality. The SSL::sessionid command within an iRule returns a blank value with BIG-IP VE. Editing the virtual guest configuration SSL::sessionid iRule command Errors when using the bigpipe import command Use of SNMP OID for RMON tables Media speed messages in log file F5 Networks strongly recommends that you do not edit the virtual configuration of BIG-IP VE. high-availability failure events occur. To ensure that the system properly detects the new or removed interfaces. except for the virtual network interface mappings. To work around this issue. You can ignore these messages. If you change the number of virtual interfaces on the BIG-IP VE system after a binary MCPD database has been created.license. you can re-license the local system after importing the UCS by accessing a backup copy of the license file. Also.1 is used. due to a manual suspension or the timeout of network disk I/O). Use of the b import default command can generate Security Enhanced Linux (SELinux) errors.bak. you should ensure that the host names of the two systems differ. When starting the BIG-IP VE system or when removing an interface from a VLAN. the system correctly imports only the configuration data that is common to both the originating platform and the target platform. the system attempts to import all of the UCS configuration data. When the host names differ. The system might note a failure and restart key system processes and trigger failover if within a high-availability (HA) group. which does not work. and history tables generates an error message. bash prompt the system appears unresponsive. the system overwrites the local license with the license contained in the UCS. when importing a UCS. Opaque. This is intended system behavior. the system does not detect the change when subsequently rebooted. When the VMware vSwitch Promiscuous Mode is set to Reject. VMware vSwitch Promiscuous Mode Virtual network interface status is wrong Auto-licensing and the If you have not defined a default route to the management port. and reboot the system. will not be able to pass packets. located in /config/bigip. The BIG-IP VE system reports the status of host-only network interfaces as UNINITIALIZED. This OID will be disabled in future releases. If the host names match. Setting the source OID for RMON alarm. even though the interface is functioning normally. Use the hypervisor's reset controls. verify that you have defined a default route for the management port before attempting to activate a license. HA events due to BIG-IP VE inactivity If the VMware hypervisor runs the BIG-IP VE software for fewer than four minutes continuously (for example. the VLAN group transparency mode. the default default management route interface 1. You can ignore these errors. type the command rm /var/db/mcpd* at the BIG-IP VE command prompt. BIG-IP licensing and User When you import a User Configuration Set (UCS) from another BIG-IP or Configuration Sets BIG-IP VE system. To prevent this from occurring.

the system BIG-IP Virtual Edition displays an error message. You can ignore this message.1q headers A hypervisor's Layer 2 bridging device might remove quality of service (QoS) classification from packets.Troubleshooting BIG-IP Virtual Edition Importing a UCS from the When you import a UCS from the BIG-IP Virtual Edition Trial. 24 . Trial The virtual switch clears the QoS field in 802.

editing virtual 22 Configuration of OVF with additional interfaces. unsupported 20 E environment. hard-wired unsupported 20 FIPS. troubleshooting sessionid command for SSL 22 ISO file and location on virtual machine 14 downloading 14 downloading base ISO file 14 downloading update ISO file 14 C configuration. troubleshooting 22 G guest environment 8 O OVA file. for guest 8 F failover. troubleshooting 22 license for BIG-IP system. troubleshooting bigpipe import errors 22 installation rebooting after 15 installation operation 15 insufficient video RAM event message. troubleshooting 22 B best practices for deployment 18 for redundant system configuration 18 BIG-IP import command. location 10 25 . hypervisor guest definition 8 A active/standby configuration 18 auto-licensing. assigning 11 maximum allowed throughput rate 8 media speed messages in log file. troubleshooting 22 Multiple Spanning Tree Protocol (MSTP). troubleshooting 22 IP address. troubleshooting 22 log file and location 15. unsupported 20 N NTP time synchronization. troubleshooting 22 BIG-IP system modules. unsupported 20 host machine. 22 log in after updating 15 assigning management IP address 11 deploying BIG-IP VE virtual machine 10 D default route for virtual management port 11 deployment overview 10 downloads and importing update 14 of ISO base file 14 of ISO update file 14 M management port IP address. troubleshooting 22 CPU and best practices for 18 and guest definition 8 and host machine requirements 10 deploying BIG-IP VE virtual machine 10 L LACP protocol. CPU requirements 10 hypervisor.1q headers and QoS field. troubleshooting 22 hard-wired failover. See guest environment. unsupported 20 MOS bash prompt exiting shell. 22 and media speed messages 15. troubleshooting 22 memory balloon driver.Index Index 802. unsupported 20 BIG-IP Virtual Edition and VMware ESX host machine requirements 10 and VMware ESXi host machine requirements 10 updating 14 bridging protocols. troubleshooting 22 H HA events due to BIG-IP VE inactivity. management port 11 iRule. unsupported 20 Layer 2. unsupported 20 I import command.

troubleshooting 22 VMware Tools troubleshooting time synchronization 22 VMware virtual machine creating 10 VMXNET3 unavailability. troubleshooting 22 R Rapid Spanning Tree Protocol (RSTP). troubleshooting 22 SNMP OID for RMON tables. unsupported 20 VMware Tools status.Index P power-on procedure. unsupported 20 SSL. troubleshooting sessionid command in iRule 22 system reboot. and hypervisor guest definition 8 virtual guest configuration. troubleshooting 22 V virtual configuration. for update 14 protocols troubleshooting 22 unsupported 20 T task list for deploying on virtual machine 10 for deploying on VMware 10 for updating on virtual machine 14 for updating on VMware 14 troubleshooting 22 Q QoS. See reboot operation. troubleshooting 22 virtual machine settings 8 virtual management port 11 virtual network interface status. troubleshooting 22 VLAN groups. virtual machine 11 product license 8 progress indicator. troubleshooting 22 vSwitch promiscuous mode. troubleshooting 22 spanning tree protocols. troubleshooting 22 S setup utility 10 Single Configuration File (SCF) feature. unsupported 20 reboot after configuring additional interfaces. troubleshooting 22 reboot operation after updating 15 redundant system configuration and host machine requirements 10 and NTP requirement 10 deploying 18 resource reservations 18 RMON tables and SNMP OID. troubleshooting 22 VMware and compatible versions 8 VMware Fault Tolerance technology. system update procedure 14 26 . troubleshooting 22 U UCS importing from BIG-IP Virtual Edition Trial. editing. troubleshooting 22 unsupported features 20 update downloading and importing 14 installing 15 update progress indicator 14 user configuration sets for licensing BIG-IP system.

Sign up to vote on this title
UsefulNot useful