Académique Documents
Professionnel Documents
Culture Documents
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
Unlike other versions of the BIG-IP system that support multiple software images on the same drive (in multiple boot partitions), this product supports one virtual image on one virtual drive. The following figure shows the high-level architecture of BIG-IP VE Trial, for both bare-metal and hosted hypervisor environments.
1 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
The following table describes the components shown in the previous illustration. Components of the system architecture
Component Virtual machine layer VMware hypervisor layer Operating system layer Hardware platform layer Description This layer represents an image of BIG-IP VE Trial, potentially sharing physical resources with other virtual machines running on the same hardware platform. The VMware hypervisor software layer is a bare-metal or hosted hypervisor that simulates a set of dedicated resources for each BIG-IP virtual machine. Supported hypervisor layers are: VMware Workstation 7, VMware vSphere ESX 4.0, and ESXi 4.0. The operating system layer applies to hosted hypervisors only. Physical resources such as CPU, memory, data storage, and network interface cards (NICs).
To deploy BIG-IP VE Trial, you download a package onto your host machine, and power on the BIG-IP VE Trial virtual machine. For more information, see Deploying BIG-IP Virtual Edition Trial on VMware Workstation 7 or Deploying BIG-IP Virtual Edition Trial on VMware ESX or ESXi. Once you have imported the package and powered on the virtual machine, you can: Assign a management IP address to the virtual machine. For more information, see Assigning a management IP address to the virtual machine. Run the BIG-IP Setup utility to activate the license and configure BIG-IP network objects such as VLANs and self IP addresses. For more information, see Running the BIG-IP Setup Utility . Configure BIG-IP Local Traffic Manager VE to process application traffic using virtual servers and load balancing pools. For more information, see Configuring BIG-IP Local Traffic Manager Virtual Edition.
2 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
1 GB RAM 3 virtual network adapters 1 10 GB LSI logic disk BIG-IP VE Trial does not contain or support VMware Tools. Do not install VMware Tools on the guest system.
3 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
To successfully run BIG-IP VE Trial, the host system requires the following software: VMware Workstation 7 Windows 7 (64-bit) or Windows XP, Service Pack 3 (32-bit) operating system
2. Download the BIG-IP VE Trial Zip file. 3. Extract the VMX and VMDK files from the Zip archive. 4. Start VMware Workstation 7. 5. From the VMware Workstation 7 File menu, choose Open. 6. In the file dialog box, find the new folder and select the VMX file. The VMX file contains the virtual configuration data for the virtual machine. 7. Review the network interface adapter mappings to ensure that they map to their respective network interface adapters.
The following figure shows the VMware Workstation screen that you can now use to view the status of the BIG-IP VE Trial virtual machine.
4 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
5 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
7. Configure the management IP address: If you want to configure DHCP to automatically assign the management IP address, type b mgmt. Copy or make a note of the returned IP address, because you will need this address to access the BIG-IP Setup Utility later. If you want to manually configure the management IP address, type config, press Enter, and follow the required steps.
Note: If the management IP address is to be on a public network, verify that the address is available for use.
6 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
2. Download the BIG-IP VE Trial package. 3. Extract the files from the Zip archive. 4. Start VMware vSphere and log in. 5. From the File menu, choose Deploy OVF Template. The Deploy OVF Template wizard starts. 6. On the Source screen, click Deploy from file, and, using the Browse button, locate the OVA file. For example:
\MyDocuments\Work\Virtualization\BIG-IP-10.1.0.1-45.ova
7. Click Next. The OVF Template Details screen opens. 8. Verify that the OVF template details are correct, and click Next. This displays the End User License Agreement. 9. Read and accept the license agreement and click Next. The Name and Location screen opens. 10. In the Name box, type a name for the BIG-IP virtual machine, such as smith_10.1.0.1-45. 11. In the Inventory Location pane is displayed, select a folder name. Click Next. 12. If the host system is controlled by VMware vCenter, the Host Cluster screen opens. Choose the desired host and click Next. Otherwise, proceed to the next step. 13. Map the source network Management Network to the name of a destination management network in your inventory. An example of a destination management network is Management. 14. Map the source network Internal Network to the name of a destination non-management network in your inventory. An example of a destination internal network is Private Access. 15. Map the source network External Network to the name of an external network in your inventory. An example of a destination external network is Public Access. 16. Click Next. The Ready to Complete screen opens. 17. Verify that all deployment settings are correct, and click Finish.
The following figure shows an example of a VMware ESX screen that you can use to view the status of the BIG-IP VE Trial virtual machine.
7 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
8 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
BIG-IP Setup Utility later. If you want to manually configure the management IP address, type config, press Enter, and follow the required steps.
Note: If the management IP address is to be on a public network, verify that the address is available for use.
9 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
14. For the Self IP setting, type a self IP address and network mask for VLAN internal. 15. For the Port Lockdown setting, retain the default value. 16. For the VLAN Tag ID setting, retain the default value (auto). This is the recommended value. 17. For the VLAN Interfaces setting, click the interface 1.1 and, using the Move button, move the interface number from the Available box to the Untagged box. 18. Click Next. This displays the screen for configuring the default VLAN external. 19. For the Self IP setting, type a self IP address and network mask for VLAN external. 20. For the Port Lockdown setting, retain the default value. 21. In the Default Gateway box, type the IP address that you want the BIG-IP system to use as the default gateway for traffic exiting VLAN external. 22. For the VLAN Tag ID setting, retain the default value (auto). This is the recommended value. 23. For the VLAN Interfaces setting, click the interface 1.2 and, using the Move button, move the interface number from the Available box to the Untagged box. 24. Click Finished. You have successfully configured the network portion of the BIG-IP system and should now see the main screen of the Configuration utility. You are now ready to configure the BIG-IP VE Local Traffic Manager. You can update the network configuration at any time by using the options that are available in the Network section of the Configuration utility.
10 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
To create a load balancing pool By default, the VMware Workstation 7 virtual network is configured in host-only mode, which means that all devices on the virtual network must reside on the local host. For this reason, the pool that you create in the following procedure consists of server nodes that run locally as virtual machines. 1. On the Main tab of the navigation pane, expand Local Traffic, and click Pools. The Pools screen opens. 2. In the Name box, type a name for the pool, such as vm_pool. 3. For the New Members setting, in the Address box, type the IP address of a server node that you want to add to the pool. 4. Type or select a service port. 5. Click Add. 6. Repeat steps 3 through 5 for each pool member that you want to add. 7. Click Finished. To create a virtual server By default, VMware Workstation 7 assigns all local clients and servers to the same virtual bridge, causing potential network issues. When using VMware Workstation 7, you can prevent this (and still retain the default VMware virtual network configuration) by enabling the SNAT Auto Map feature. This feature directs each virtual server within BIG-IP Local Traffic Manager VE to automatically translate a client's source IP address to a self IP address on the BIG-IP system. This translation ensures that each server response returns through the BIG-IP system on its way back to the client, thereby ensuring client acceptance.
1. On the Main tab of the navigation pane, click Virtual Servers. The Virtual Servers screen opens. 2. On the upper right portion of the screen, click the Create button. The New Virtual Server screen opens. 3. In the Name box, type a name for the virtual server, such as vm_virtual_server. 4. In the Destination Address box, type the IP address you want to use for the virtual server. 5. From the Service Port list, select a service name. 6. From the Configuration list, select Advanced. 7. If you are running VMware Workstation 7, then from the SNAT Pool list, select Auto Map. For an explanation of this setting, see the previous note. If you are running VMware ESX or ESXi, proceed to the next step. 8. Click Finished.
For detailed information on configuring other local traffic features, see the Configuration Guide for BIG-IP Local Traffic Manager available from the Ask F5 Knowledge Base.
11 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
Status of virtual network interfaces (CR126854-1) The BIG-IP system reports the status of host-only network interfaces as UNINITIALIZED, even though the interfaces are still functioning normally. Default gateway and fully-qualified domain name (FQDN) (CR133307) The default gateway sometimes appears in the BIG-IP configuration file as an FQDN instead of an IP address. grub command seen on boot (CR133542) The string \'/usr/bin/grub_default -l\' returned 1 appears when booting BIG-IP VE Trial. You can ignore this message. Support for VMware Player (CR133574) VMware Player is not a supported hypervisor for this release. Importing a User Configuration Set (UCS) (CR133762) Importing a UCS file from a BIG-IP software version other than BIG-IP VE Trial might produce unexpected results. Blank user interface fields on VMware ESX/ESXi platforms (CR 133852) On VMware ESX and ESXi platforms, the Vendor, Version, and Description fields appear blank. big3d daemon on Services screen (CR134045) The big3d daemon appears on the Services screen of the BIG-IP Configuration utility even though the daemon is not installed on the system. Display of the command line prompt after reboot (CR134075) On VMware Workstation 7 systems only, after rebooting the VMware console, pressing the Enter key repeatedly too soon after the reboot causes the Active string within the command line interface prompt to appear as ?Active? (for example, [root@jim1029:?Active?] config #. F5 Networks recommends that after you boot the system from the console, you use a different console emulator such as PuTTY. Editing the virtual guest configuration (CR 134076) F5 Networks strongly recommends that you do not edit the virtual configuration of BIG-IP VE Trial, except for the virtual network interface mappings. Unwanted characters on VMware console window (CR134154-1) Because VMware Tools are not installed on the system, unwanted characters might appear in the VMware console window. Support for VMware Server (CR134252) When using the VMware Server graphical user interface to edit a network adapter, the screen erroneously displays a message saying that the e1000 device type is not supported. Note that VMware Server is an unsupported hypervisor for this release. Alert message regarding insufficient video RAM (CR 134473) On VMware ESX and ESXi platforms only, the following event message displays as an alert: 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, increase the amount of video RAM allocated to this virtual machine by setting svga.vramSize="16708800" in the virtual machine's configuration file. You can ignore this message or take the recommended action without adverse effects.
12 of 13
2/22/2010 12:31 PM
https://support.f5.com/kb/en-us/products/big-ip_ve/releasenotes/product/r...
SSL::sessionid iRule command (CR135601) The SSL::sessionid command within an iRule returns a blank value. Invalid BIG-IP VE Trial evaluation license after power-on (CR135602) In rare cases, when you power down the BIG-IP virtual machine and power it on again, you must re-license the BIG-IP VE Trial system. SSL alert codes (CR135917) While handling malicious SSL traffic, upon error, the SSL alert code might describe a different, but similar, error type. Normal SSL traffic is not affected. bigpipe import command (CR136004) Use of the b import default command can generate Security-Enhanced Linux (SELinux) errors. You can ignore these errors. SNMP OIDs in enterprise MIB (CR136079) Certain platform-related SNMP OIDs are missing from the enterprise MIB file F5-BIGIP-SYSTEM-MIB.txt.
Tips
You can use the Linux tcpdump command to verify that the virtual machines on the host machine are communicating.
Contacting F5 Networks
Phone:(206) 272-6888 Fax: (206) 272-6802
Copyright 2010, F5 Networks, Inc., Seattle, Washington. All rights reserved. F5, F5 Networks, the F5 logo, BIG-IP, 3-DNS, Access Policy Manager, APM, Acopia, Acopia Networks, Application Accelerator, Ask F5, Application Security Manager, ASM, ARX, Data Guard, Enterprise Manager, EM, FirePass, FreedomFabric, Global Traffic Manager, GTM, iControl, Intelligent Browser Referencing, Internet Control Architecture, IP Application Switch, iRules, Link Controller, LC, Local Traffic Manager, LTM, Message Security Module, MSM, NetCelera, OneConnect, Packet Velocity, Protocol Security Module, PSM, SSL Accelerator, SYN Check, Traffic Management Operating System, TMOS, TrafficShield, Transparent Data Reduction, uRoam, VIPRION, WANJet, WAN Optimization Module, WOM, WebAccelerator, 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.
13 of 13
2/22/2010 12:31 PM