Applies To:

Show Versions Show Versions

Manual Chapter: After Deploying BIG-IP VE on Xen Project
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Configure TSO support

The TCP Segmentation Offloading (TSO) feature, which includes support for large receive offload (LRO) and Jumbo Frames, is enabled by default.
Note: You must have the admin user role to enable or disable TSO support.
  1. Use an SSH tool to access the BIG-IP® VE command line.
  2. Log in as root.
  3. Type tmsh to open the tmsh utility.
    You will see tmsh at the prompt once the utility is opened.
  4. To determine whether TSO support is currently enabled, use the command:
    show sys db tm.tcpsegmentationoffload
  5. To enable support for TSO, use the command:
    sys db tm.tcpsegmentationoffload enable
  6. To disable support for TSO, use the command:
    sys db tm.tcpsegmentationoffload disable

Increase disk space for BIG-IP VE

Before proceeding with these steps, use Virt Manager 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.

  1. Use an SSH tool to access the BIG-IP VE tmsh utility.
  2. From the command line, log in as root.
  3. List the current size of the directories on your disk so you can determine which ones need to be resized.
    tmsh show sys disk directory
  4. Expand the size of the directories in which you need additional space.
    tmsh modify sys disk directory <directory name> new-size <new directory size in 1KB blocks>
    For example, use tmsh modify sys disk directory /config new-size 3145740 to increase the size of /config directory to 3145740 1KB blocks (or roughly 3,221,237,760 bytes).
  5. To confirm that the command you just submitted is properly scheduled, you can show the new list of directories again.
    tmsh show sys disk directory
  6. If you change your mind about a submitted size change, you can revoke the size change.
    tmsh modify sys disk directory /config new-size 0
    In this example, the size of the /config directory is left as is, revoking any scheduled size changes.
    After you submit this sequence of tmsh commands, the directory size changes will be scheduled to occur the next time the BIG-IP VE virtual machine (VM) is rebooted.
The next time the VM running BIG-IP VE reboots, the changes are applied.

Enable config sync for BIG-IP VE in Xen Project

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.
  1. Use an SSH tool to connect to each of the BIG-IP VEs.
  2. Ensure you are at the tmsh prompt.
    tmsh
  3. On each BIG-IP VE, disable functionality that enforces single NIC setup.
    modify sys db provision.1nicautoconfig value disable
  4. Confirm that the value was set correctly by typing list sys db provision.1nicautoconfig.
    The following text is returned: value "disable".
  5. On each BIG-IP VE, specify the static private IP address of the BIG-IP VE itself.
    modify cm device <device_name> configsync-ip <private_ip_address>
  6. Establish device trust: On one BIG-IP VE, enter the static private IP address of the other BIG-IP VE, along with its user name and password.
    modify cm trust-domain add-device { ca-device true device-ip <peer_ip_address> device-name <peer_device_name> username <peer_username> password <peer_password> }
  7. On the same BIG-IP VE as the previous step, create a sync-failover device group with network failover disabled.
    create cm device-group <device_group_name> devices add { <all-bigip-device-names-separated-by-space> } type sync-failover auto-sync enabled network-failover disabled
  8. Sync the BIG-IP VE to the other BIG-IP VE.
    run cm config-sync to-group <device_group_name>

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.
  1. Use an SSH tool to connect to BIG-IP VE.
  2. Return to the default configuration.
    tmsh load sys config default
  3. Save the changes.
    tmsh save sys config
  4. Set a database variable so that the number of NICs will be recognized on reboot.
    setdb provision.1nic enable
  5. Reboot BIG-IP VE.
    reboot
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.
  1. Use an SSH tool to connect to BIG-IP VE.
  2. Return to the default configuration of BIG-IP VE.
    tmsh load sys config default
  3. Save the changes.
    tmsh save sys config
  4. Set a database variable so that the number of NICs will be recognized on reboot.
    setdb provision.1nic forced_enable
  5. Reboot BIG-IP VE.
    reboot
When the BIG-IP VE instance is up and running, it will have a single NIC and related network objects will be created.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)