Manual Chapter :
After Deploying BIG-IP VE on XenServer
Applies To:
Show Versions
BIG-IP AAM
- 13.0.1, 13.0.0
BIG-IP APM
- 13.0.1, 13.0.0
BIG-IP Analytics
- 13.0.1, 13.0.0
BIG-IP LTM
- 13.0.1, 13.0.0
BIG-IP AFM
- 13.0.1, 13.0.0
BIG-IP PEM
- 13.0.1, 13.0.0
BIG-IP DNS
- 13.0.1, 13.0.0
BIG-IP ASM
- 13.0.1, 13.0.0
Turn off LRO or GRO
Although there are a number of ways
to turn off LRO, the most reliable way is to connect to the virtual machine and use the
ethtool
utility.
See the XenServer documentation for more details.
Increase disk space for BIG-IP VE
Before proceeding with these steps,
use XenCenter to expand the disk size for the BIG-IP® VE virtual
machine and reboot.
Use the BIG-IP VE tmsh utility to increase
the amount of disk space used by the four BIG-IP VE directories:
- /config
- /shared
- /var
- /var/log
Note: At the time of
this release, decreasing the VE disk size is not supported.
For each directory you want to resize, complete these steps.
The next time the VM running BIG-IP
VE reboots, the changes are applied.
Enable config sync for BIG-IP VE in XenServer
Before you can complete this task:
- Both BIG-IP VEs must be running the same version of BIG-IP VE system software.
- The BIG-IP VEs must not have the same device name. To view the name, use the tmsh command: list /cm device. The device name is in the first line that is returned, for example cm device bigip1 {. To change the name, use mv cm device <current_device_name> <new_device_name> .
Enable config sync communication
when you want to automatically or manually synchronize configuration information.
Note: The following steps apply to
single-NIC configuration only. If you have multiple NICs, follow the standard
procedures for enabling config sync.
Change the NIC used for BIG-IP VE management
By default, management traffic goes
through the eth0 NIC and data traffic goes through the other available NICs. If you need
to use eth0 for data traffic, you can change the NIC that management traffic goes
through.
- Use SSH to connect to BIG-IP VE.
- If you need to determine which NICs are available, stop TMM by typing bigstart stop tmm. Then type ip addr to view the list of available NICs.
- Change the management NIC by typing tmsh modify sys db provision.managementeth value eth1 where eth1 is the NIC you want to use for management. You can use any available NIC.
- Press Enter.
- Reboot BIG-IP VE by typing reboot and pressing Enter.
When BIG-IP VE is running again, you
can use eth0 for data.
Note: If the subnet associated with the
management NIC does not have DHCP, you must assign a new IP address by using the
BIG-IP Configuration utility tool.
About routes in a single NIC configuration
If you want to configure a static route that relies on a gateway in the same subnet as the self IP address, you must first disable the setting that enforces single NIC setup:
modify sys db provision.1nicautoconfig value disableConfirm that the value is correct by typing list sys db provision.1nicautoconfig.
The return value should be disable.
If you do not change this value, any time you reboot BIG-IP VE, the manually-configured static route will cause validation errors during load sys config.
Change from single NIC to multi-NIC
When you initially boot BIG-IP VE,
if it recognized only one NIC, then some network configuration was done automatically.
If you want to use more than one NIC, complete the following steps.
When the BIG-IP VE instance is up and
running, multiple NICs will be recognized and you can begin configuring BIG-IP
VE.
Change from multi-NIC to single NIC
If you have a BIG-IP VE
configuration with multiple NICs, you can simplify the configuration to have only one
NIC. When you boot the BIG-IP VE and only one NIC is recognized, some networking objects
are created automatically for you.
When the BIG-IP VE instance is up and
running, it will have a single NIC and related network objects will be created.
