Applies To:

Show Versions Show Versions

Release Note: BIG-IP GTM and BIG-IP Link Controller 11.4.1
Release Note

Original Publication Date: 09/17/2015

Summary:

This release note documents the version 11.4.1 release of BIG-IP Global Traffic Manager and BIG-IP Link Controller. You can apply the software upgrade to systems running software versions 10.1.0 (or later) or 11.x.

Contents:

- Supported platforms
- Configuration utility browser support
- User documentation for this release
- New in 11.4.1
- New in 11.4.0
- Installation overview
     - Installation checklist
     - Installing the software
     - Post-installation tasks
     - Installation tips
- Upgrading from earlier versions
- Fixes in 11.4.1
- Fixes in 11.4.0
- Behavior changes in 11.4.1
- Behavior changes in 11.4.0
- Known issues
- Contacting F5 Networks
- Legal notices

Supported platforms

This version of the software is supported on the following platforms:

Platform name Platform ID
BIG-IP 800 (LTM only) C114
BIG-IP 1600 C102
BIG-IP 3600 C103
BIG-IP 3900 C106
BIG-IP 6900 D104
BIG-IP 8900 D106
BIG-IP 8950 D107
BIG-IP 11000 E101
BIG-IP 11050 E102
BIG-IP 2000s, BIG-IP 2200s C112
BIG-IP 4000s, BIG-IP 4200v C113
BIG-IP 5000s, BIG-IP 5200v

BIG-IP 5x50 (requires 11.4.1 HF3)

C109
BIG-IP 7000s, BIG-IP 7200v

BIG-IP 7x50 (requires 11.4.1 HF3)

D110
BIG-IP 10x50 (requires 11.4.1 HF3) D112
BIG-IP 10000s, BIG-IP 10200v D113
VIPRION B2100 Blade A109
VIPRION B2150 Blade A113
VIPRION B2250 Blade (requires 11.4.1 HF1) A112
VIPRION C2400 Chassis F100
VIPRION B4100, B4100N Blade A100, A105
VIPRION B4200, B4200N Blade A107, A111
VIPRION B4300, B4340N Blade A108, A110
VIPRION C4400, C4400N Chassis J100, J101
VIPRION C4480, C4480N Chassis J102, J103
VIPRION C4800, C4800N Chassis S100, S101
Virtual Edition (VE) Z100
vCMP Guest Z101

These platforms support various licensable combinations of product modules. This section provides general guidelines for module support.

Most of the support guidelines relate to memory on the platform or provisioned guest. For vCMP support and for Policy Enforcement Module (PEM), Carrier-Grade NAT (CGNAT), and the BIG-IP 800 platform, the following list applies for all memory levels:

  • vCMP supported platforms
    • VIPRION B2100, B2150, B2250, B4200, B4300, B4340N
    • BIG-IP 5200v, 7200v, 10200v
  • PEM and CGNAT supported platforms
    • VIPRION B2150, B2250, B4300, B4340N
    • BIG-IP 5200v, 7200v, 10200v
    • BIG-IP Virtual Edition (VE) (Not including Amazon Web Service Virtual Edition)
    • PEM and CGNAT may be provisioned on the VIPRION B4200, but it is not recommended for production, only for evaluation. PEM may be provisioned on the VIPRION B2100, but it is not recommended for production, only for evaluation. Use the B4300 or B4340N instead.
  • BIG-IP 800 platform support
    • The BIG-IP 800 platform supports Local Traffic Manager (LTM) only, and no other modules.

Memory: 12 GB or more

All licensable module-combinations may be run on platforms with 12 GB or more of memory, and on VE and vCMP guests provisioned with 12 GB or more of memory.

Memory: 8 GB

The following guidelines apply to the BIG-IP 2000s, 2200s, 3900, 6900 platforms, to the VIPRION B4100 and B4100N platforms, and to VE guests configured with 8 GB of memory. (A vCMP guest provisioned with 8 GB of memory has less than 8 GB of memory actually available and thus does not fit in this category.)

  • No more than three modules should be provisioned together.
  • On the 2000s and 2200s, Application Acceleration Manager (AAM) can be provisioned with only one other module.
  • Note that Global Traffic Manager (GTM) and Link Controller (LC) do not count toward the module-combination limit.

Memory: Less than 8 GB and more than 4 GB

The following guidelines apply to platforms, and to VE and vCMP guests provisioned with less than 8 GB and more than 4 GB of memory. (A vCMP guest provisioned with 8 GB of memory has less than 8 GB of memory actually available and thus fits in this category).

  • No more than three modules (not including AAM) should be provisioned together.
  • Application Acceleration Manager (AAM) cannot be provisioned with any other module; AAM can only be provisioned standalone.
  • Note that GTM and LC do not count toward the module-combination limit.
  • Analytics (AVR) counts towards the two module-combination limit (for platforms with less than 6.25 GB of memory).

Memory: 4 GB or less

The following guidelines apply to the BIG-IP 1600 and 3600 platforms, and to VE and vCMP guests provisioned with 4 GB or less of memory.

  • No more than two modules may be configured together.
  • AAM should not be provisioned, except as Dedicated.

VIPRION and vCMP caching and deduplication requirements

Application Acceleration Manager (AAM) supports the following functionality when configuring vCMP and VIPRION platforms.

  • AAM does not support disk-based caching functionality on vCMP platforms. AAM requires memory-based caching when configuring it to run on vCMP platforms.
  • AAM supports disk-based caching functionality on VIPRION chassis or blades.
  • AAM does not support deduplication functionality on vCMP platforms, or VIPRION chassis or blades.

vCMP memory provisioning calculations

The amount of memory provisioned to a vCMP guest is calculated using the following formula: (platform_memory - 3 GB) x (cpus_assigned_to_guest / total_cpus).

As an example, for the B2100 with two guests, provisioned memory calculates as: (16-3) x (2/4) ~= 6.5 GB.

For certain platforms, the vCMP host can allocate a single core to a vCMP guest. However, because a single-core guest has relatively small amounts of CPU resources and allocated memory, F5 supports only the following products or product combinations for a single-core guest:

  • BIG-IP LTM standalone only
  • BIG-IP GTM standalone only
  • BIG-IP LTM and GTM combination only

Configuration utility browser support

The BIG-IP Configuration Utility supports these browsers and versions:

  • Microsoft Internet Explorer 8.x and 9.x
  • Mozilla Firefox 15.0.x
  • Google Chrome 21.x

User documentation for this release

For a comprehensive list of documentation that is relevant to this release, refer to the BIG-IP GTM / VE 11.4.1 Documentation page.

New in 11.4.1

Maximized Enterprise Application Delivery Value

To make it easier and more affordable to get the Software Defined Application Services capabilities all organizations need, F5 introduces three software bundle offerings: Good, Better, and Best.
Good
Provides intelligent local traffic management for increased operational efficiency and peak network performance of applications.
Better
Good plus enhanced network security, global server load balancing, and advanced application delivery optimization.
Best
Better plus advanced access management and total application security. Delivers the ultimate in security, performance, and availability for your applications and network.
You can learn more about these new software bundles from your F5 Networks Sales Representative.

New in 11.4.0

Incremental synchronization for GTM synchronization groups

The BIG-IP GTM system now synchronizes configuration changes incrementally across a GTM synchronization group. Incremental synchronization improves system performance, because only the data that has changed on a GTM device is synchronized to the other GTM devices in the synchronization group. Although incremental synchronization is the default behavior, if an incremental synchronization fails, the system automatically performs a full configuration synchronization.

Manual saves of GTM configuration changes

By default, BIG-IP Global Traffic Manager (GTM) automatically saves GTM configuration changes 15 seconds after the change is made in either the Configuration utility or tmsh. You can now change how long GTM waits before it saves GTM configuration changes. In addition, you can disable automatic saves of GTM configuration changes, and then run a tmsh command to save those changes.

Rate-Limited Licenses Statistics

With this release, BIG-IP GTM and DNS Services rate-limited licenses are available. If a BIG-IP system has a rate-limited license, the system displays statistics about the rate limits on the Local Traffic DNS profile statistics page. It is important to note that GTM requests (requests for wide IPs) are a subset of DNS requests. Therefore, when the number of requests that GTM receives for a wide IP exceeds the DNS Services rate limit, the Rate Rejects count for DNS increments, rather than the Rate Rejects count for Global Traffic Management incrementing.

DNSKey records available in the Configuration utility

With this release, you can now copy the public DS record for a DNS zone from within the Configuration utility to facilitate sending the record to the parent authority.

GTM load balancing decisions

When BIG-IP GTM receives a DNS name resolution request for a wide IP, in order to send a response, the system makes a load-balancing decision. With this release, you can send information about how GTM made the load-balancing decision to the high-speed remote logs.

Disabling TSIG verification for NOTIFY messages (ID 388869)

You can disable TSIG verification for NOTIFY messages that the BIG-IP system receives from the Master DNS server for a DNS Express zone. When the BIG-IP system receives a NOTIFY message without a TSIG HMAC included, the system processes the request. To disable TSIG verification for NOTIFY Messages, run the tmsh command: modify ltm dns dns-express zone <zone name> verify-notify-tsig no

GTM notifies iControl of GTM object state change

In this release, when the status of a GTM object changes, if you have enabled the GTM general global-setting Forward Status, GTM now notifies iControl of the change. This setting is disabled by default. You can enable the Forward Status setting in the Configuration utility on the System :: Configuration : Global Traffic : General screen. You can also enable this setting using the command: tmsh modify gtm global-settings general { forward-status enabled}

Installation overview

This document covers very basic steps for installing the software. You can find complete, step-by-step installation and upgrade instructions in BIG-IP Systems: Upgrading Active-Standby Systems and BIG-IP Systems: Upgrading Active-Active Systems, and we strongly recommend that you reference these documents to ensure successful completion of the installation process.

Installation checklist

Before you begin:

  • Use BIG-IP iHealth to verify your configuration file. For more information, see SOL12878: Generating BIG-IP diagnostic data using the qkview utility (10.x - 11.x).
  • Update/reactivate your system license, if needed, to ensure that you have a valid service check date.
  • Ensure that your system is running version 10.1.0 or later and is using the volumes formatting scheme.
  • Download the .iso file (if needed) from F5 Downloads to /shared/images on the source for the operation. (If you need to create this directory, use the exact name /shared/images.)
  • Configure a management port.
  • Set the console and system baud rate to 19200, if it is not already.
  • Log on as an administrator using the management port of the system you want to upgrade.
  • Boot into an installation location other than the target for the installation.
  • Save the user configuration set (UCS) in the /var/local/ucs directory on the source installation location, and copy the UCS file to a safe place on another device.
  • Log on to the standby unit, and only upgrade the active unit after the standby upgrade is satisfactory.
  • Turn off mirroring.
  • If you are running Application Acceleration Manager, set provisioning to Minimum.
  • If you are running Policy Enforcement Manager, set provisioning to Nominal.
  • If you are running Advanced Firewall Manager, set provisioning to Nominal.

Installing the software

You can install the software at the command line using the Traffic Management shell, tmsh, or in the browser-based Configuration utility using the Software Management screens, available in the System menu. Choose the installation method that best suits your environment.
Installation method Command
Install to existing volume, migrate source configuration to destination tmsh install sys software image [image name] volume [volume name]
Install from the browser-based Configuration utility Use the Software Management screens in a web browser.

Sample installation command

The following command installs version 11.2.0 to volume 3 of the main hard drive.

tmsh install sys software image BIGIP-11.2.0.2446.0.iso volume HD1.3

Post-installation tasks

This document covers very basic steps for installing the software. You can find complete, step-by-step installation and upgrade instructions in BIG-IP Systems: Upgrading Active-Standby Systems and BIG-IP Systems: Upgrading Active-Active Systems, and we strongly recommend that you reference these documents to ensure successful completion of the installation process.

After the installation finishes, you must complete the following steps before the system can pass traffic.
  1. Ensure the system rebooted to the new installation location.
  2. Use BIG-IP iHealth to verify your configuration file. For more information, see SOL12878: Generating BIG-IP diagnostic data using the qkview utility (10.x - 11.x).
  3. Log on to the browser-based Configuration utility.
  4. Run the Setup utility.
  5. Provision the modules.
  6. Convert any bigpipe scripts to tmsh. (Version 11.x does not support the bigpipe utility.)
Note: You can find information about running the Setup utility and provisioning the modules in the BIG-IP TMOS implementations Creating an Active-Standby Configuration Using the Setup Utility and Creating an Active-Active Configuration Using the Setup Utility.

Installation tips

  • The upgrade process installs the software on the inactive installation location that you specify. This process usually takes between three minutes and seven minutes. During the upgrade process, you see messages posted on the screen. For example, you might see a prompt asking whether to upgrade the End User Diagnostics (EUD), depending on the version you have installed. To upgrade the EUD, type yes, otherwise, type no.
  • You can check the status of an active installation operation by running the command watch tmsh show sys software, which runs the show sys software command every two seconds. Pressing Ctrl + C stops the watch feature.
  • If installation fails, you can view the log file. The system stores the installation log file as /var/log/liveinstall.log.

Upgrading from earlier versions

Your upgrade process differs depending on the version of software you are currently running.

Warning: Do not use the 10.x installation methods (the Software Management screens, the b software or tmsh sys software commands, or the image2disk utility) to install/downgrade to 9.x software or operate on partitions. Depending on the operations you perform, doing so might render the system unusable. If you need to downgrade from version 10.x to version 9.x, use the image2disk utility to format the system for partitions, and then use a version 9.x installation method described in the version 9.x release notes to install the version 9.x software.

Upgrading from version 10.1.0 (or later) or 11.x

When you upgrade from version 10.1.0 (or later) or 11.x software, you use the Software Management screens in the Configuration utility to complete these steps. To open the Software Management screens, in the navigation pane of the Configuration utility, expand System, and click Software Management. For information about using the Software Management screens, see the online help.

Upgrading from versions earlier than 10.1.0

You cannot roll forward a configuration directly to this version from BIG-IP version 4.x, or from BIG-IP versions 9.0.x through 9.6.x. You must be running version 10.1.0 software. For details about upgrading to those versions, see the release notes for the associated release.

Automatic firmware upgrades

If this version includes new firmware for your specific hardware platform, after you install and activate this version, the system might reboot additional times to perform all necessary firmware upgrades.

Fixes in 11.4.1

There are no fixes specific to Global Traffic Manager.

Fixes in 11.4.0

ID Number Description
ID 227276 GTM FTP monitors now correctly mark the operational state of IPv6 servers.
ID 247055 "iControl clients will be able to receive event notifications whenever GTM object's availability status has changed via iControl :: Management :: EventNotification interface. This functionality is disabled by default. It can be enabled via the IControl::GlobalLB::Globals interface by: set_forward_status_state('STATE_ENABLED'); The state of the feature is returned via the same interface: get_forward_status_state();"
ID 342508 The bigip_add and gtm_add scripts can now be passed a user name.
ID 381036 Now you can change Global Quality of Service (QoS) load-balancing factors from tmsh.gtm.global-settings.load-balancing.
ID 403125 GTM virtual server auto-discovery now works correctly when the GTM is v11.x and an LTM is upgraded from v10.x to v11.x.
ID 405230 Fixed backwards compatibility between new big3ds and older gtms.
ID 406751 This fix corrects a defect whereby a GTM using topology load balancing can intermittently experience TMM crashes shortly after topology records are added or removed from the configuration.
ID 407256 GTM is now able to collect the right hop count for LDNSs.

Behavior changes in 11.4.1

There are no behavior changes specific to Global Traffic Manager.

Behavior changes in 11.4.0

ID Number Description
ID 345733 You can now use Ctrl-C to stop the gtm_add process and gtmd, named, and zrd will be restarted if they have been stopped.

Known issues

ID Number Description
ID 224507 When VE is deployed on VMware, the management port might not correctly reflect the uplink port speed of the vSwitch that it is connected to. This should have no adverse affects on actual management port traffic. Workaround:
ID 324960 "big3d daemon on Services screen (CR134045, ID 324960) The big3d daemon appears on the Services screen of the BIG-IP Configuration utility even though the daemon is not installed on the system." Workaround:
ID 346083 "When you remove an interface from all VLANs, and then add the same interface, the interface status remains UNINITIALIZED, and you can only access the system from the console. To recover, manually edit bigip_base.conf, deleting the entries and running the command: 'load sys config'. An entry appears similar to the following: net interface 1.3 { media-fixed 10000T-FD }" Workaround:
ID 351199 When importing an OVA into XenServer, CPU priority is not set. It is recommended that a higher priority be set on the VM. Using XenCenter, click on the General tab of the VM. Then click Properties. On the CPU and Memory tab, the VCPU priority should be configured at the highest value. Workaround:
ID 351367 "XenCenter OVF wizard's Run Operating System Fixups option blocks appliance import (ID 351367) When importing the OVA into XenCenter, make sure <b>Run Operating System Fixups</b> is unchecked." Workaround:
ID 351538 "F5 Networks strongly recommends that the host system use CPUs with AMD-V or Intel-VT technology. This might require adjusting the systems BIOS or Unified Extensible Firmware Interface (UEFI) configuration. For specific hypervisors, hardware assisted virtualization technologies might be required in order to boot BIG-IP VE. For detailed system requirements, see the hypervisor's documentation." Workaround:
ID 352456 Host-based time synchronization can last a few minutes in order to align the clocks. Workaround:
ID 352856 "If an SCF is migrated between BIG-IP VE running on non-similar hypervisor software, a validation error may prevent configuration loading. Loading the configuration ... BIGpipe interface creation error: 01070318:3: ""The requested media for interface 1.1 is invalid."" When this condition is encountered on BIG-IP Virtual Edition, configuration may be fixed for import by removing the entire line that contains ""media fixed"" statements for each interface." Workaround:
ID 354161 DNS Express continues to handle queries for that zone, even if a BIND zone that underlies a DNS Express zone expires. This occurs when using DNS Express to handle queries for zones, and a BIND zone expires. The impact is that DNS Express continues to handle queries for that zone. Workaround: To have DNS Express stop answering queries, disable or delete the DNS Express zone itself.
ID 358355 When deployed as a Microsoft Hyper-V virtual machine, BIG-IP VE must be configured with Static Memory Allocation. The use of Dynamic Memory Allocation is unsupported and might cause issues. Workaround:
ID 364704 Taking a snapshot of the virtual machine's memory often pauses the virtual machine and may produce undesired results. To correct this problem on VMware hypervisors, do not include the virtual machine's memory when snapshots are taken. Workaround:
ID 366403 After modifying the BIG-IP system configuration by adding or removing Network Interfaces, the interface numbering might appear out of order and NICs may appear that are no longer present. If the virtual interfaces on the BIG-IP VE system are changed after a binary MCPD database has been created, the system may not detect the change even after a subsequent reboot. To ensure that the system properly detects the new or removed interfaces, type the command "rm /var/db/mcpd*" at the BIG-IP VE command prompt, and reboot the system. TMM-to-vSwitch interface mapping can be viewed by comparing the MAC addresses of the interfaces displayed in the BIG-IP Configuration utility to those displayed in the hypervisors configuration. The interfaces may need a simple adjustment to map to the correct networks. Workaround:
ID 367759 Modifying an interface's VLAN configuration from tagged to untagged, or untagged to tagged, can result in unavailability of traffic on that interface. Restarting the tmm with "bigstart restart tmm" will correct this condition. Workaround:
ID 367862 Network Interface Port Mirroring is not supported by BIG-IP VE with this release. Workaround:
ID 370367 On BIG-IP VE only, changing the interface used by a VLAN from one to another might show degraded performance in the event that both interfaces are configured to participate on the same broadcast network. Restarting the TMM with "bigstart restart tmm" will restore performance and resolve the issue. Workaround:
ID 371458 On a XenServer Host, all interfaces are expected to show up as 100TX-FD within tmsh. All application traffic handling interfaces will be shown with a media speed of 100 and an Active Duplex of half in the GUI for this release. This speed rating is simply cosmetic and not actually reflective of the speeds and duplex for BIG-IP VE on a XenServer host. The actual link is a high speed internal connection via a Virtual Network Interface within the hypervisor at speeds greater than 100Mbps. Workaround:
ID 372540 Migration of BIG-IP VE, whether live or powered off, will commonly incur an innocuous warning message similar to this on vSphere hypervisors: Virtual Ethernet card 'Network adapter 1' is not supported. This is not a limitation of the host in general, but of the virtual machine's configured guest OS on the selected host." This message is benign and can safely be ignored. Workaround:
ID 374064 Import verification of the .ova may fail when using the XenCenter 5.6. OVA import wizard. It is suggested that XenCenter 5.6 users verify the .ova file signature as described on AskF5. Workaround:
ID 388118 For IPv6 to work on KVM using a macvtap interface, the IFF_ALLMULTI setting must be enabled on the host interface. This is done by using "ifconfig <name of interface> allmulti". Workaround:
ID 390961 Only Virtio NICs must be used for traffic and management. Workaround:
ID 394817 "VADC now supports CMP (that is, multiple TMMs running on the same box). For a rate limited license, the limit is divided by the number of TMMs, so each TMM is capped at a fraction of the total licensed limit. For example, if a 200M license with one connection has a throughput of 180Mbits/s before enabling CMP, then for two TMMs the expected throughput would be 90 Mbits/s, and with four TMMs, the expected throughput would be 45 Mbit/s." Workaround:
ID 399035 "The following message may be logged on each boot with this release of BIG-IP Virtual Edition: ""SRAT: PXMs only cover 61231MB of your 61999MB e820 RAM. Not used. SRAT: SRAT not used."" This message is benign and can safely be ignored." Workaround:
ID 399046 "On boot of BIG-IP Virtual Edition on Xen Hypervisors, a message similar to ""err kernel: piix4_smbus 0000:00:01.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr"" may be displayed. This is considered innocuous and may be ignored." Workaround:
ID 404628 BIG-IP Virtual Edition hosted on XenServer cannot have more than six network interfaces configured in the virtual machine definition for this release of software. Workaround:
ID 409234 "FastL4 Virtual Servers can experience very low throughput on Virtual Edition with TCP Segmentation Offload disabled. The customer will notice a large amount of Transmit Datagram Errors for the fastl4 profile (tmsh show ltm profile fastl4)" Workaround: "The customer should enable TCP Segmentation Offload by modifying 'sys db tm.tcpsegmentationoffload'. The customer may also resolve this issue by disabling large Receive Offload (LRO) on any hypervisor they plan on running Virtual Edition."
ID 412817 Big-IP is unreachable for IPv6 traffic via PCI pass-through interfaces as current ixgbevf drivers do not support multicast receive. Workaround: None
ID 413587 "The customer will see an extra interface when a Big-IP Virtual Edition is deployed on Citrix XenServer 6.1. This extra interface will have the same MAC address as the VE instance's management interface. The shell command 'ip list' will show one more interface that the user has configured through the hypervisor, and two of those interfaces shown will have the same MAC address." Workaround: A customer should use SR-IOV interfaces for VE instances deployed on Citrix XenServer 6.1.
ID 414251 In AWS, connection mirroring does not work if an instance with a different number of cores is present in traffic group. Workaround: BIG-IP instances in AWS used for connection mirroring as part of HA functionality should be of the same instance type and size to ensure the same number of cores.
ID 416201 Community Xen: Only 2 PCI pass-through interfaces can be seen on the guest. This is an issue in the CentOS domain 0, and not the BIG-IP guest. Workaround:
ID 416231 Virtual Edition instances running on Xen 3.0 based hypervisors may report less memory than provisioned. For example a VE instance with 4 GB of memory provisioned may report 3.5 GB of memory available. Workaround: Deploy the Virtual Edition instance with more memory.
ID 428107 "Seeing no traffic passing through the Intel virtual function (VF)-based network interfaces in BIG-IP Virtual Edition (VE). - run <dmesg | grep ixgbe | less> in the host Linux and you should see a line like this: ixgbe 0000:08:00.0: VF 0 has no MAC address assigned, you may have to assign one manually - continue verifying with <ip link show <dev>> and you should see a line like this: vf 0 MAC 00:00:00:00:00:00" Workaround: "Option 1 (Preferred): In the host Linux, assign the MAC addresses for the VFs attached to BIG-IP VE: - run <ip link set <DEVICE> vf <#> mac <MAC-ADDRESS>> Option 2: In the host Linux, downgrade the ixgbe driver to the version of 3.11.33 Option 3: In BIG-IP VE, assign the MAC addresses for the VF-based network interfaces."
ID 428116 Mechanisms in BIG-IP VE for handling PCI-Passthrough Device ID's on VMware hypervisors prevent the correct discovery of these devices on first boot of the deployed Virtual Machine instance. Workaround: Boot the BIG-IP software at least once and safely shut it down before assigning PCI passthrough devices for use as a dataplane. Once the passthrough devices have been assigned and the system booted the second time, it may be then be licensed.
ID 428612 "Seeing no traffic passing through the Intel VF-based network interfaces in BIG-IP VE. - In BIG-IP VE, check the VF-based network interfaces and get the MTUs: - run <ifconfig <device>> - In Linux host, check the PF's MTU - run <ifconfig <device>> - Compare MTUs from above and make sure PF's is equal to or greater than VF's" Workaround: "Increase Intel PF's MTU to be equal to or greater than VFs' which are attached to BIG-IP VE - run <ip link set <DEVICE> mtu <MTU>>"

Contacting F5 Networks

Phone: (206) 272-6888
Fax: (206) 272-6802
Web: http://support.f5.com
Email: support@f5.com

For additional information, please visit http://www.f5.com.

Additional resources

You can find additional support resources and technical documentation through a variety of sources.

F5 Networks Technical Support

Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.

AskF5

AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.

F5 DevCentral

The F5 DevCentral community helps you get more from F5 products and technologies. You can connect with user groups, learn about the latest F5 tools, and discuss F5 products and technology.

AskF5 TechNews

Weekly HTML TechNews
The weekly TechNews HTML email includes timely information about known issues, product releases, hotfix releases, updated and new solutions, and new feature notices. To subscribe, click TechNews Subscription, complete the required fields, and click the Subscribe button. You will receive a confirmation. Unsubscribe at any time by clicking the Unsubscribe link at the bottom of the TechNews email.
Periodic plain text TechNews
F5 Networks sends a timely TechNews email any time a product or hotfix is released. (This information is always included in the next weekly HTML TechNews email.) To subscribe, send a blank email to technews-subscribe@lists.f5.com from the email address you are using to subscribe. Unsubscribe by sending a blank email to technews-unsubscribe@lists.f5.com.

Legal notices

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)