Original Publication Date: 01/30/2019
These release notes document the BIG-IP version 13.1.0.x releases. You can apply the software upgrade to systems running software version 11.0.0 or later (except as detailed in the upgrading sections).
BIG-IP Virtual Edition (VE) is a version of the BIG-IP system that runs as a virtual machine. Supported modules include Local Traffic Manager, BIG-IP DNS, Application Security Manager, Access Policy Manager, Application Acceleration Manager, Policy Enforcement Manager, Application Firewall Manager, and Analytics. BIG-IP VE includes all features of device-based BIG-IP modules running on standard BIG-IP TMOS, except as noted in release notes and product documentation.
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. The following list applies for all memory levels:
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. Note that this does not mean that all modules may be simultaneously provisioned on all platforms with 12 GB or more of memory. The BIG-IP license for the platform determines which combination of modules are available for provisioning.
The following guidelines apply to the BIG-IP 2000s, 2200s, 6900 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.)
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.)
The following guidelines apply to VE and vCMP guests provisioned with 4 GB or less of memory.
Application Acceleration Manager (AAM) supports the following functionality when configuring vCMP and VIPRION platforms.
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.
This version of the software is supported in the following configurations. For a list of VE hypervisor support, see the Virtual Edition and Supported Hypervisors Matrix.
All licensable module-combinations may be run on BIG-IP Virtual Edition (VE) guests provisioned with 12 GB or more of memory.
The following guidelines apply to VE guests configured with 8 GB of memory.
The following guidelines apply to VE guests provisioned with less than 8 GB and more than 4 GB of memory.
The following guidelines apply to VE guests provisioned with 4 GB or less of memory.
The BIG-IP Configuration Utility supports these browsers and versions:
K14592: Compatibility of BIG-IQ products with BIG-IP releases provides a summary of version compatibility for specific features between the BIG-IQ system and BIG-IP releases.
This release includes a new virtual wire configuration object, which enables you to add a BIG-IP device to the network in-line to manage bi-directional network traffic transparently at Layer 2.
When managing VXLAN tunnels using the Open vSwitch Database (OVSDB) management protocol to communicate with a software-defined networking (SDN) controller, you can now enable the Bidirectional Forwarding Detection (BFD) protocol. With this protocol, the system can detect the failure of an active service node and remove the node from the algorithm used for forwarding broadcast packets.
When configuring the BIG-IP system to store BIG-IP user accounts on a remote RADIUS authentication server, you can now specify the RADIUS server name as an IPv4 address, an IPv6 address, or a fully-qualified domain name (FQDN).
The i11000 Series platform now supports Virtual Clustered Multiprocessing (vCMP) to provide the ability to create multiple BIG-IP guests on the system.
A BIG-IP system administrator can now control the number of acknowledgements (ACKs) that the system receives as a result of setting the PSH bit in a TCP header. Reducing the number of ACKs that the system receives can improve system performance.
In this release, when creating an HTTPS monitor, there is a new SSL Profile setting. You can select an SSL profile from an available list of all serverssl profiles in the BIG-IP system, or accept the default (None) to specify no SSL profile. When selecting an SSL profile, the HTTPS connections are handled directly by the BIG-IP system's data plane processes (TMM). This improves HTTPS Monitor scaling on systems with four or more CPU cores and allows the HTTPS Health Monitor to use SSL acceleration hardware. This includes TCP, TCP Half-Open, ICMP Gateway, HTTP, and HTTPS monitors, which may now run within tmm, saving performance.
This release adds support for optional subscriber ID logging when creating various logging profiles, including LSN, and local/custom Network Firewall.
Starting with this release, if a BIG-IP device is not licensed and you attempt to load a configuration, the BIG-IP configuration loads, but the system indicates it is OFFLINE, and will not pass traffic until you apply a license. You need to either add the appropriate license, or remove the configuration elements for the module that is not licensed.
Dynamic routing protocols, BGP and BFD, can now be configured via tmsh and iControl REST. When enabling RCI, ZebOS imish is in a Read-Only state.
BIG-IP 13.1.0 now allows TCPDump to send packets over a GRE tunnel to a remote client.
The new functionalities ensure that a legitimate user will be able to log in even if the user account is under a brute force attack.
There is a new brute force reporting screen that shows the status of all login pages. For each attack there is information about mitigated sources and, in the case of a credentials stuffing attack, the leaked user names.
After upgrade, the detection and prevention duration will be derived from previous settings. Mitigation options will be same as in new a policy.
Mobile applications detection is added in bot protection. This enables the exemption of mobile application clients from challenges and mitigations which are not relevant to them and the use of mobile application-appropriate mitigations. It also gives control over the mobile applications that are allowed on a virtual server. The system is able to extract a unique, non-Java Script, fingerprint for each mobile application instance and report client traffic composition per application for any given time period and what applications are used and the top URLs accessed.
ASM can identify that the access is indeed a mobile app access and that the application is indeed untampered with.
Mobile application detection is supported via a Software Development Kit (which requires minimal development and integration) and is supported on both Android and iOS devices.
The system uses proprietary correlation algorithms to aggregate reported events from non-staged traffic into user-understandable security issue incidents for quicker review and user action.
For CSRF protection, PUT, PATCH, DELETE methods are treated as POST requests. CSRF Protection cannot be applied to Parent policies, i.e. cannot be inherited.
After upgrade, all CSRF URLs will be configured for inspection with method POST.
Custom attack signature rule writing has been simplified to allow users to create rules without needing to use Snort syntax or escape common characters. Using Simple Edit Mode, a user can quickly create custom signatures using keywords. For users comfortable in Snort who want more control over rule syntax, Advanced Edit Mode allows users to write directly in Snort. Rules written in Simple Edit Mode can be viewed and edited in their corresponding Snort syntax by switching to Advanced Edit Mode.
Mobile threats and Tor proxies are added to the IP Address Intelligence Categories options while illegal websites were removed.
The Potential Disallowed Files Type List is a list of file types which may be seen in malicious requests, such as information leakage and remote code execution, and is now available for use in the GUI. The system comes with a preconfigured list which users can add to. The system automatically checks all traffic for all policies against this list and can generate suggestions to amend a policy to add or remove file types from the Disallowed File Types list. The Potential Disallowed Files Type List is configurable.
The acceleration is achieved by the Fast-L4 data path for most flows during non-attack periods. The acceleration is switched on and off automatically by the system depending on traffic intensity. Once an attack has been detected, all flows are switched to the full HTTP proxy mode. The selected Fast-L4 profiles specify the configuration of the Fast-L4 data path.
Working with mirrored traffic entering via the BIG-IP Switched Port Analyzer (SPAN) port, DoS-L7 traffic can be monitored and evaluated passively. Violations, suggestions and logs are generated to show how the system would have responded if it were in active monitoring mode.
In a new policy these violations initially will be set to not enforced. Policy Builder will create suggestions to enforce these violations according to tightening settings.
New triage sections were added to the Traffic Learning screen to speed up the traffic learning process.
To better accommodate production chain approval processes and performance issues, the application of policy changes, by setting the General Settings Learning Mode field to Automatic and then configuring the Auto-Apply Policy field, can be scheduled to best suit the user environment. Suggestions and the Audit Log can then be filtered by Since last Apply Policy.
BADOS supports multiple DoS profiles per virtual server and directs traffic based on incoming HTTP request properties. Each DoS profile can be configured differently. If no custom DoS Protection Profile policy is defined for a security policy, the default DoS profile is used. A default DoS profile with configured Application Security attached to a virtual server is necessary even if no HTTP requests direct the default profile.
Starting with BIG-IP 188.8.131.52, the following LTM features are available in Advanced WAF (AWAF):
F5 Access Policy Manager now deploys services in any one traffic group. Within that traffic group, APM operates in Active/Standby mode. APM is supported in an N+M configuration with up to 7 standby participants. Identical hardware models must be used. Active/Standby status of BIG-IP participants in traffic groups without APM services do not impact this feature.
Allows APM services to be in any single traffic group, rather than only in Traffic-Group-1.
F5 Access Policy Manager now supports OpenID Connect (OIDC) for OAuth client and resource server features. OpenID provides enhancements to the client application access control rules. This feature has three scenarios:
The F5 Access Policy Manager OAuth 2.0 infrastructure now supports stateless authentication. The OAuth resource server can now validate the incoming JSON Web Token (JWT) and provide access control checks based on the token's content without contacting the Authorization Server. This feature has three scenarios:
You can now download and update a single ISO package containing APM client packages for Windows, Mac, and Linux
Kerberos SSO has schema changes supporting UPN suffixes as well as enabling and disabling UPN. Kerberos now also has improved credentials caching.
You can now run additional Endpoint Checks that require admin privileges. This feature is supported on Microsoft Windows and Macintosh systems. This allows Windows Hard Disk Encryption Checks for Win10, and Software Patch on Mac.
An F5 Access Policy Manager native application allows application tunnels on Linux and Macintosh operating systems. Applications such as browsers, SSH clients, and RDP clients have controlled access to a specific backend server.
This release provides improved ability to support the Network Access feature.
F5 Access Policy Manager can now take on the role of an Active Directory Federation Services (ADFS) proxy by supporting ADFS-PIP protocol and Microsoft ADFS 3.0 (on Windows Server 2012 R2) and 4.0 (on Windows Server 2016).
F5 can check with Microsoft Intune device enrollment and compliance posture for iOS and Android devices before allowing access.
F5 Access Policy Manager now authenticates native Microsoft Office applications access to SharePoint. APM no longer requires persistent cookies and prior web sessions. You can open a SharePoint document from a native Office application, such as Microsoft Word, click the link in the document, and the correct document type opens with authentication using Microsoft OFBA.
F5 Access Policy Manager now has reporting enhancements to provide better user visibility for the Access module of BIG-IQ product.
VDI profile now supports StoreFront functionality on APM. You can enable or disable the native StoreFront protocol when you configure F5 Access Policy Manager to replace the StoreFront server.
AFM includes support for subscriber awareness allowing you to develop firewall rules that match traffic based on subscriber information. A subscriber is a remote user with a unique subscriber ID.
AFM now allows you to use a scrubbing profile to exclude, for specific route domains, VLANs that should be exempt from scrubbing (in case of DoS attacks).
Several enhancements improve DoS protection in AFM. DoS profiles can be attached to virtual servers with the name *, meaning any. More vectors can be configured so that the system automatically determines appropriate threshold values (Fully Automatic). A partially automatic setting also lets you manually set threshold values, yet let the system perform mitigation as needed (Manual Detection/Auto Mitigation). In the Device Protection properties, you can disable DoS vectors globally if they are not relevant for your network configuration. Additional internal enhancements improve the effectiveness of DoS protection in both hardware and software.
For Device Network DoS and virtual Server Network DoS, you can now configure the system to detect and mitigate Dynamic Signatures using L4 Behavioral DoS detection. When configured, the system detects possible DoS threats based on traffic history, and can automatically track and mitigate such threats. This feature has been enhanced to include DNS and ICMP protocols.
This release provides new options for Route Advertisement and Proxy ARP in the NAT policy rule. Customizable log options for NAT events include the subscriber identity, the ability to specify what to log, and what delimiter to use.
AFM can now provide visibility into what traffic is being dropped by the BIG-IP system, what is happening to the traffic, and this information enhances packet tracing. You can have the system redirect dropped packets to a specific VLAN, and log them while collecting statistics needed for debugging.
In the Protocol Security section, you can configure inspection profiles to examine traffic for protocol inspection items and compliance with protocols. Protocol inspection items are arranged in categories by the service type. You can assign groups of protocol inspection items by service (such as DNS, HTTP, SIP, and so on). You can also add valid Snort signatures to a service. You can assign protocol inspection items to a firewall rule, or directly to a virtual server.
This feature adds the capability to initiate a DHCP session for unknown subscribers and also recreates PEM sessions in a BIG-IP PEM restart scenario. When the packet flows are received which do not have existing PEM sessions, PEM uses DHCP lease query (by IP address) to communicate with the DHCP servers. PEM obtains DHCP lease information to create new PEM sessions. IPv4 and IPv6 is are both supported.
PEM can function as a DHCP relay agent and there is now support for load balancing DHCP sessions while being able to leverage DHCP for subscriber awareness.
PEM can now operate on mirrored traffic. PEM can be inserted non-intrusively in the network for reporting or analytics. Classification and reporting PEM actions are the only ones supported in this mode. This feature is supported on a subset of platforms but not on VE or GUI.
F5 Networks provides Fraud Protection Service (FPS) that detects and protects customer's web sites and mobile apps from fraud attacks, such as malware and phishing. Using layered security, automatic engines, and a 24/7 security operation center (SOC), FPS efficiently detects attacks as they are being set up, monitors the fraudulent activity, and documents the incident. Users can view notifications of fraud incidents by means of alerts sent to the FPS Dashboard.
New FPS features and improvements in BIG-IP 13.1.0 include:
Full AJAX encryption is now possible on URLs that use JSON format for submitting data.
FPS performance was improved to avoid page crashing in old versions of Internet Explorer (IE 6-8) and to shorten loading time in all browsers.
You can now revoke a license from a running instance of BIG-IP VE, and then use that license on another BIG-IP VE.
NIC Teaming is supported on all existing NICs supported by F5 in VMWare and KVM Hypervisors. To configure NIC teaming, use the BIG-IP trunking feature.
You can now use as many as 24 vCPUs with BIG-IP VE.
BIG-IP VE now has a native VMXNET3 driver (unic is no longer needed). Because of this, dataplane interfaces are no longer as 'ethN' (with Linux tools like ifconfig, ethconfig, and ip).
The disk space for the 2-slot Better/Best image is now 82 GB; previously it was 139 GB. An additional 20 GB is provided to support the AAM module. If you are not running AAM, you can remove this extra 20 GB. A new 1-slot Better/Best image with 60 GB is available for non-cloud hypervisors. An additional 20G is also provided for AAM and can be removed.
You can now use tools like the Common OVF Tool, the VMware OVF tool, or another tool of your choice to set the management IP address and root / admin passwords for BIG-IP VE. You can use these tools before, during, or after deployment.
You can now use a template to deploy BIG-IP VE with multiple NICs in Google Cloud Platform.
Hourly licensing is now supported up to 5 Gbps and the BIG-IP VE does not need internet access to be licensed.
AWS IC Marketplace is now available for customers that need the security of a data center with no access from IC cloud to the public internet and likely no encrypted (or other data) may leave the network. Current offerings are BYOL and hourly licenses in 25M, 200M, and 1G throughputs. Support is available with U.S. national support only.
You can now deploy a single-NIC BIG-IP VE in the Azure Stack environment..
This release includes the following new hardware-specific items.
This release provides support for the new BIG-IP i11000 platform. For more information, see Platform Guide: i5000/i7000/i10000/i11000 Series.
This release includes the AOM device ID licensing feature, which ties the software license to a unique identifier in the hardware. This feature is available on BIG-IP iSeries and BIG-IP standard series platforms. Note that if you need to downgrade to an earlier version after installing version 13.1.0, you will have to install the earlier version of BIG-IP software and then open an SR so that F5 Support can allow the reactivation of your key to work on the older version of BIG-IP software. You can then follow the normal license activation process to activate your license. For more information, see BIG-IP System: Essentials or K7752: Licensing the BIG-IP system
In this release, Platform Diagnostics includes enhancements to the platform_diag and platform_check tests. For more information, see F5 Platforms: Platform Diagnostics.
In this release, a 10350 FIPS platform includes a FIPS hardware security module (HSM) enabled with single-root I/O virtualization (SR-IOV). With SR-IOV and Virtual Clustered Multiprocessing (vCMP) provisioned on the system, you can offer FIPS multi-tenancy for guests that must manage FIPS-related application traffic. This feature allows a vCMP host administrator to create multiple virtual HSMs, or FIPS partitions, on the HSM to provide each guest with dedicated cores and FIPS key storage.
This release includes updates to the Configuration utility and TMOS Shell (tmsh) to enable you to switch TurboFlex Profiles based on your needs. For more information, see F5 Platforms: TurboFlex Profiles.
This release provides early access to the hardware-optimized FIX Low Latency (FIX-LL) feature on BIG-IP i5000/i7000/i10000 Series platforms and VIPRION B4450 blades. If you encounter any problems with this functionality, please contact your F5 Networks representative. Resolution of any software defects found in this version might appear in a future release.
BIG-IP iSeries systems and VIPRION B4450 blades include a TPM 2.0 security device that implements security functions as defined by the Trusted Computing Group (TCG). In this release, these systems now support the use of the TPM measurement function to establish a hardware-based chain of trust at system start up. This verifies that firmware (BIOS) is authentic and has not been tampered with by a malicious user. This feature is highly manual in this release and should be considered Early Access functionality. It will be automated and more layers of operating system and software will be included in future releases.
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 Software, and we strongly recommend that you reference this information to ensure successful completion of the installation process.
Before you begin:
|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.|
The following command installs version 13.0.0 to volume 3 of the main hard drive.
tmsh install sys software image BIGIP-184.108.40.206.0.1645.iso volume HD1.3
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 Software, and we strongly recommend that you reference this information to ensure successful completion of the installation process.
Your upgrade process differs depending on the version of software you are currently running.
When you upgrade from version 11.x or later, 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.
You cannot roll forward a configuration directly to this version from BIG-IP version 10.x or earlier. You must be running version 11.x (or later) software. For details about upgrading from earlier versions, see the release notes for the associated release.
You cannot directly upgrade from pre-11.5.0 versions (e.g., v11.4.x, v11.2.x, etc.) to any 4th element version (e.g., v220.127.116.11, v18.104.22.168, etc.). Direct upgrade to 4th element versions is supported only from v11.5.0 and later. For pre-11.5.0 versions, you must first upgrade to v11.5.0 or later. The recommended upgrade path is from v11.4.1 to v12.1.3, and then to v22.214.171.124. For details about upgrading to those versions, see the release notes for the associated release.
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.
When you upgrade from an earlier versions of the software, you might need to know about or take care of these configuration-specific issues.
|588946||You can install v11.5.4 on the 12250v platform, but are unable to license BIG-IP. This is because v11.5.4 is not supported on the 12250v platform. Install BIG-IP v11.5.4 on a 12250v platform. BIG-IP v11.5.4 is not supported on the 12250v platform. Even though installation succeeds, it is not possible to license BIG-IP system. Workaround: Install a supported version of BIG-IP on the 12250v. Supported versions are 11.6.0 HF2 or later and 12.0.0 or later.|
|223704||When you import a single configuration file (SCF file) that contain VLANs of the same name that exist in different administrative partitions, the operation fails with a unknown operation error. Upgrading configurations with VLANs of the same name in different administrative partitions. Upgrade operation fails with a unknown operation error. Workaround: Before installing an SCF file, run the command: tmsh load sys config default. This returns the system to the default configuration, so subsequent configuration import operations should succeed as expected.|
|513501||When upgrading from a version prior to 11.5.0 to 11.5.0 or newer, the configuration might fail to load with an error similar to the following: LSN pool is configured with a prefix address that overlaps with a prefix address on another LSN pool. "On versions prior to 11.5.0, tmsh allowed users to configure overlapping DNAT and NAPT pools, even though this configuration is invalid and non-functional. Version 11.5.0 and later contain validation to prohibit such configurations. However, when upgrading versions newer than 11.5.0, a configuration that contains overlapping DNAT and NAPT pools fails to load." Configuration fails to load on upgrade. Workaround: Edit bigip.conf and locate the overlapping LSN pools. Either remove one of the pools or change the mode on the DNAT pool to NAPT.|
|571333||When a VIP is configured with a fastl4 profile that enables full acceleration and offload state to embryonic, and if a flow is offloaded to be hardware accelerated, the connection idle timeout during the TCP handshake is set to the "idle timeout" value of the fastl4 profile, but it should be set to the "tcp handshake timeout" instead. "1. Configure fastl4 profile with ePVA=full, offload state=SYN, apply to network VS 2. Ensure ARP entry exists for server node (static arp, ping, etc.) to satisfy requirements for offloading initial SYN 3. Send over SYN packet from client to server via VS" The connection may remain in the half-open state longer than what is set in the TCP handshake timeout value. Workaround: Set the offload state to "established"|
|436075||Using syslog include field when the command 'syslog-ng -s' does not succeed before the upgrade. Using syslog include field. It is possible to roll forward an include field with invalid syntax. This will cause the configuration to fail to load. Workaround: When using the syslog include field, ensure that the command 'syslog-ng -s' succeeds before the upgrade.|
|581932||Upgrading to a newer version of the BIG-IP software removes the signatures that were installed using an IM signature package, and returns app signatures to the default version. "- New '.im' signature package installed manually using the BIG-IP GUI or tmsh. This adds extra applications and categories to the default signatures. - TMOS software upgraded to a newer version, for example installing a rollup hotfix or an engineering ho" "After rebooting into the new software volume, all the additional categories and applications are gone but the signature package is still showing as installed. This makes a simple re-installation of the new .im signature package impossible. The applications and categories are actually back to default settings for version 11.6.0." Workaround:
"1. After rebooting into the new software volume, open the bigip.conf file with a text editor and remove all the configurations from the 'ltm classification signature-version' stanza:
|415961||The upgrade process does not migrate unassigned HTTP Class profiles to BIG-IP 11.4.0 and later When you upgrade a BIG-IP system to BIG-IP 11.4.0 or later, the upgrade process attempts to convert all assigned HTTP Class profiles to their equivalent local traffic policies. If an HTTP Class profile is not assigned to a virtual server, the upgrade process will not perform the conversion and the unassigned HTTP Class profile will no longer exist in the configuration of the upgraded BIG-IP system. Similarly, if you restore a UCS archive that contains unassigned HTTP Class profiles in BIG-IP 11.4.0 and later, the restoration process will not convert the unassigned HTTP Class profiles and these profiles will no longer exist. This behavior is by design. You might lose unused HTTP Class profiles in the configuration. Workaround: "When upgrading to BIG-IP 11.4.0 and later or saving a UCS archive from a pre-11.4.0 system, you should consider the following factor: Prior to upgrading or saving a UCS archive, ensure that all HTTP Class profiles are assigned to a virtual server."|
|401828||The following configurations are invalid for a SIP virtual server: a) TCP virtual server with a UDP profile and a SIP profile. b) UDP virtual server with a TCP profile and a SIP profile. TCP virtual server with a UDP profile and a SIP profile, or a UDP virtual server with a TCP profile and a SIP profile. If such a configuration exists in previous versions, it loads in 11.3.x but may cause a core. Workaround: "Fix the configuration manually, as follows: a) A SIP TCP virtual server must have TCP as one of its profile type. b) A SIP UDP virtual server must have UDP as one of its profile type."|
|490139||Loading iRules from the iRules file deletes last few comment lines immediately preceding the closing bracket. This occurs when loading an iRule file from versions prior to 11.5.1. Although the comments are removed, this does not affect iRule functionality. Workaround: Put comments in places other than immediately above the closing bracket.|
|496663||iRule object in non-Common partition referenced from another partition results in upgrade/configuration load failure in 11.x/12.x. This occurs when upgrading/loading a configuration containing an iRule in one non-Common partition that references an object in another non-Common partition. A configuration of this type can be saved only using pre-11.x versions of the software. The config upgrade fails, and the UCS/configuration files cannot be loaded. The system posts an error message similar to the following: 'myucs.ucs' failed with the following error message: 'Rule [/UNCOMMONPARTITION/RULEABC] error: Unable to find rule_object (...) referenced at line xyz: [element]'. Workaround: None.|
|532559||If the client-ssl profile is /Common/clientssl, its parent profile is supposed to be /Common/clientssl. But the configuration could potentially use 'defaults-from none'. "This condition could be caused by executing the following command when generating the configuration. 'tmsh modify ltm profile client-ssl clientssl defaults-from none'" The upgrade fails after booting into the new release, during the config loading phase. This occurs because the script extracts the line 'defaults-from none' and treats 'none' as its parent profile. Workaround: Edit the configuration prior to upgrading, changing the defaults-from value on the client-ssl profile to the name of that profile.|
|449617||If a configuration file includes a passphrase for an ssl-key file object, the object may fail to validate when loading the configuration. Passphrase present in ssl-key file object Configuration fails to load Workaround: Remove passphrase line from the file object.|
|586878||"During upgrade, configuration fails to load due to invalid clientssl profile cert/key configuration. The validation to verify whether at least one valid key/cert pair exists in clientssl profiles was enforced in software versions through 11.5.0. This validation was not in effect in versions 11.5.1, 11.5.2, and 11.5.3. The lack of validation resulted in invalid clientssl profiles (those containing empty key/certs or a cert/key of 'default'). When you upgrade such a configuration to 11.5.4 or later, you will receive a validation error, and the configuration will fail to load after upgrade." "The issue occurs when all the below conditions are met.
1. You have a clientssl profile in a configuration from a version without validation (that is, 11.5.1, 11.5.2, or 11.5.3).
|435482||"BIG-IP configuration object names that include a space may cause an upgrade or user configuration set (UCS) load to fail. As a result of this issue, you may encounter the following symptoms: Your attempts to upgrade the BIG-IP system or load a UCS fail. After loading a UCS file or upgrading from a configuration that has object names with spaces on BIG-IP 11.4.0 or a later version, the Configuration utility displays an error message similar to the following example: The configuration has not yet loaded. If this message persists, it may indicate a configuration problem. After loading a UCS file that has configuration object names that include spaces on BIG-IP 11.4.0 or a later version, a message appears similar to following example: Unexpected Error: Configuration cannot be saved unless mcpd is in the running phase. Save was canceled. See 'show sys mcp' and 'show sys service'. If 'show sys service' indicates that mcpd is in the run state, but 'show sys mcp' is not in phase running, issue the command 'load sys config' to further diagnose the problem." "This issue occurs when one of the following conditions is met: You attempt to upgrade a BIG-IP system from 11.3.0, or an earlier version, with a configuration that has configuration object names with spaces. You attempt to load a BIG-IP 11.3.0 or earlier UCS file, that has configuration object names with spaces, on BIG-IP 11.4.0 or a later version." The BIG-IP system upgrade or UCS load fails. Workaround: "To work around this issue, you can boot back to the previous BIG-IP 11.3.0 or earlier version and rename all affected configuration objects to exclude spaces before upgrading or saving a UCS file. Impact of workaround: Performing the suggested workaround should not have a negative impact on your system."|
|489015||An LTM request-log profile that references a non-existent pool can pass validation in 11.0.0 or 11.1.0, but fails in 11.2.0 or later, with an error similar to the following: 'The requested Pool (/Common/poolname) was not found.' "This issue occurs when all of the following conditions are met: The UCS file has a Request Logging profile configuration with at least one of the following conditions: A Request Logging profile references a non-existent pool. A Request Logging profile references a pool in a non-default administrative partition without specifying the path to the /<partition>/<pool>. You upgrade from 11.0.0 or 11.1.0 to 11.2.0 or later and roll forward the configuration. You attempt to load an affected UCS created on 11.0.0 or 11.1.0 to a system running 11.2.0 or later." This can cause a load failure when rolling forward the configuration. Workaround: Correct the request-log profile in the config either prior to upgrade or by editing the config after.|
If you upgrade from an earlier version of ASM, note the following issues.
The Application Security Manager supports .ucs files from versions 10.1.0 and later of the Application Security Manager. Additionally, you may import policies exported from versions 10.1.0 and later of the Application Security Manager.
Warning: With the introduction of the Local Traffic Policies feature in BIG-IP version 11.4.0, HTTP Class iRule events and commands are no longer available. If you plan to upgrade to 11.4.0 or later, and your configuration contains an iRule that uses an HTTP class iRule event or command, please read K14381: HTTP Class iRule events and commands are no longer available in BIG-IP 11.4.0 and later.
Warning: Local Traffic Policies do not support regular expressions for matching. While the upgrade process is able to migrate simple glob expressions, manual administrator intervention is required in order to ensure that the policies are properly configured. If you plan to upgrade to 11.4.0 or later, and your configuration contains regular expressions or glob expressions, please read K14409: The HTTP Class profile is no longer available in BIG-IP 11.4.0 and later.
Important: The system creates its internal cookie in versions 10.2.4 and later (including all versions of 11.x) differently than in versions prior to 10.2.4. As a result, while upgrading your system from a version prior to 10.2.4 to version 10.2.4 or later, the system will produce the Modified ASM Cookie violation for existing browser sessions. If the security policy has the Modified ASM Cookie violation enabled and set to block traffic when this violation occurs, after upgrading to version 10.2.4 or later, the system will block traffic to the web application. However, since the TS cookie is a session cookie, the system will block traffic only until the browser session ends (the end-user restarts the browser). To prevent the security policy from blocking traffic until the end-user’s browser is restarted, before upgrading to version 10.2.4 or later, we recommend you disable the security policy from blocking the Modified ASM Cookie violation, upgrade, and wait long enough to allow all users to restart their browsers (two weeks are expected to be enough). After enabling the violation, we recommend you monitor the logs. If the Modified ASM Cookie violation appears, consider disabling the violation again for a longer period of time, or communicate to the users to restart their browsers.
In version 11.4.0, local traffic policies replace HTTP Classes. When you create an ASM security policy, the system automatically creates a default Layer 7 local traffic policy. Note the following changes that occur to your system after upgrading from a version prior to 11.4.0:
As a result of changes made to the signing of ASM cookies, performing a clean upgrade may result in cookie violations and blocked traffic. To prevent these, F5 recommends that you perform the following actions before upgrading:
After upgrading, users must synchronize their Cookie Protection settings in the following cases:
After upgrading, the system performs the following:
There was a check box for enabling web scraping that was removed in version 11.3.0.
In versions prior to 11.3.0, if the Dynamic Brute Force Protection Operation Mode was Blocking, and the security policy’s Enforcement Mode was Transparent, the system blocked brute force attacks. In order to keep functionality after upgrading, the system continues to block brute force attacks if you upgrade to versions 11.3.0 or later, under these circumstances. However, in versions 11.3.0 and later, the functionality changed so that if the security policy’s Enforcement Mode is Transparent, so the system does not block brute force attacks even if the Dynamic Brute Force Protection Operation Mode setting is Alarm and Block (previously Blocking).
In version 13.1 the session-based and dynamic brute force protections are discontinued and replaced with source-based brute force protection. When upgrading:
In versions 11.3.0 and later, DoS profiles are assigned to virtual servers. Previously, they were assigned to security policies.
In versions 11.3.0 and later, logging profiles are assigned to virtual servers. Previously, they were assigned to security policies. Upon upgrading logging profiles from versions prior to 11.3.0, all active security policies have their logging profile settings migrated and assigned to the virtual server associated with the HTTP Class. If a virtual server had more than one HTTP Class assigned to it, it inherits the settings of the last in the list.
In versions prior to 11.3.0, DoS profiles used the Trust XFF setting that was a security policy setting. The Trust XFF setting was renamed Accept XFF, and moved from a security policy property to a property of the HTTP profile. If you upgrade a DoS profile and a security policy with the Trust XFF setting enabled, after the upgrade, the new XFF configuration setting is disabled. If you want the DoS profile to continue trusting XFF, navigate to screen, and enable the Accept XFF setting.
In version 11.2 we unified various whitelists for Policy Builder trusted IP addresses, and anomaly whitelists (DoS Attack Prevention, Brute Force Attack Prevention, and Web Scraping Detection) into a single list. When you upgrade, these separate lists are unified to a single whitelist (called the IP Address Exceptions List).
After you install a .ucs (user configuration set) file that was exported from version 10.1.0 or later, the system does not automatically apply changes that you made, but did not apply, to the security policies. The system enforces the web application according to the settings of the last set active security policy. However, the system preserves any changes to the current edited security policy, and marks the security policy as modified [M] if the changes have not been applied.
If you are running Application Security Manager on a vCMP system: For best performance, F5 recommends configuring remote logging to store ASM logs remotely on Syslog servers rather than locally.
After upgrading or installing a new version, before you can use the Application Security Manager, you must set the Application Security Manager resource provisioning level to Nominal. You can do this from the command line, or using the Configuration utility.
For important information needed to prevent traffic from bypassing the Application Security Manager, please see the AskF5 Knowledge Center articles K8018: Overview of the BIG-IP HTTP class traffic flow and K12268: Successive HTTP requests that do not match HTTP class may bypass the BIG-IP ASM.
When Application Security Manager (ASM) is provisioned, the datasync-global-dg device-group is automatically created (even if there are no device-groups on the unit) in any of the following scenarios:
This device group is used to synchronize client-side scripts and cryptographic keys across all of the devices in the trust-domain.
Note the following:
For BIG-IP version 11.6.0, F5 Networks tested the anti-virus feature on the following ICAP servers: McAfee®, Trend Micro™, Symantec™, and Kaspersky. The following table displays which version of each anti-virus vendor was tested, and the value of the virus_header_name variable that needs to be adjusted in ASM for each tool. (You can set the virus_header_name variable: .)
|Anti-Virus Vendor||Anti-Virus Version||Value of virus_header_name|
|McAfee® VirusScan Enterprise||7.0||X-Infection-Found, X-Virus-Name|
|Trend Micro™ InterScan™ Web Security||5.0.1013||X-Virus-ID|
|Symantec™ Protection Engine||126.96.36.199||X-Violations-Found|
Metrics used in select HTTP tables in versions 12.X and lower, were merged into additional HTTP tables in this version, resulting in default values immediately following the upgrade.
|Metric Title||Applying Metric(s) in GUI||Tables with Added Metric||Initial Value After Upgrade||Version Before Upgrade|
|sessions||Average Sessions||URLs, Pool Members, Response Codes, Client IP Addresses, User Agents, HTTP Method||0||12.X or lower|
|max_tps||Max TPS||User Agents, HTTP Method||0||12.X or lower|
|client_latency_hits||Avg Page Load time, Sampled Transactions||User Agents, HTTP Method||0||12.X or lower|
|max_client_latency||Max Page Load Time||User Agents, HTTP Method||0||12.X or lower|
|client_latency||Avg Page Load time||User Agents, HTTP Method||0||12.X or lower|
|max_server_latency||Max Server Latency||User Agents, HTTP Method||0||12.X or lower|
|min_server_latency||Min Server Latency||User Agents, HTTP Method||MAX_INT||12.X or lower|
|server_latency||Avg Server Latency||User Agents, HTTP Method||0||12.X or lower|
|max_request_throughput||Max Request Throughput||User Agents, HTTP Method||0||12.X or lower|
|total_request_size||Avg Request Throughput||User Agents, HTTP Method||0||12.X or lower|
|max_response_throughput||Max Response Throughput||User Agents, HTTP Method||0||12.X or lower|
|total_response_size||Avg Transaction Response size||User Agents, HTTP Method||0||12.X or lower|
Dimensions were added since previous versions, resulting in default values immediately following the upgrade.
The following table lists the new dimension titles and the initial values displayed in the GUI following an upgrade from a previous version. Once new data is collected, the displayed values for each dimension will appear as expected.
|Dimension Title||Dimension Module||Location in GUI||Initial Value After Upgrade||Version Before Upgrade|
|Behavioral Signatures||HTTP||Aggregated||12.X or lower|
|Bot Defense Reasons||HTTP||Aggregated||12.X or lower|
|Browser Names||HTTP||Aggregated||12.X or lower|
|OS Names||HTTP||Aggregated||12.X or lower|
|Vectors||Common||Aggregated||12.X or lower|
|Triggers||Common||Aggregated||12.X or lower|
|Mitigations||Common||Aggregated||12.X or lower|
|Activity Types||Common||Regular Activity||12.X or lower|
|Destination Countries||Network||Aggregated||13.X or lower|
|Destination IP Address||Network||Aggregated||13.X or lower|
|Client Types||HTTP||Aggregated||13.X or lower|
|Human Behavior Indications||HTTP||Aggregated||13.X or lower|
|Application Versions||HTTP||Aggregated||13.X or lower|
|Application Display Names||HTTP||Aggregated||13.X or lower|
|Jail Break||HTTP||Aggregated||13.X or lower|
|Emulation Modes||HTTP||Aggregated||13.X or lower|
Metrics were added since previous versions, resulting in default values immediately following the upgrade.
The following table lists the new metrics and the initial value displayed in the GUI following an upgrade from a previous version. Once new data is collected, the displayed value will appear as expected in the metric field.
|Metric Title||Applying Metric(s) in GUI||Initial Value After Upgrade||Version Before Upgrade|
|min_server_latency||Min Server Latency||MAX_INT||12.X or lower|
|server_hitcount||Avg Server Latency, Avg Application Response Time, Avg Server Network Latency||0||12.X or lower|
|application_response_time||Avg Application Response Time||0||12.X or lower|
|max_application_response_time||Max Application Response Time||0||12.X or lower|
|min_application_response_time||Min Application Response Time||MAX_INT||12.X or lower|
|client_ttfb_hitcount||Avg Client TTFB||0||12.X or lower|
|max_client_ttfb||Max Client TTFB||0||12.X or lower|
|min_client_ttfb||Min Client TTFB||MAX_INT||12.X or lower|
|clientside_network_latency||Avg Client Network Latency||0||12.X or lower|
|max_clientside_network_latency||Max Client Network Latency||0||12.X or lower|
|min_clientside_network_latency||Min Client Network Latency||MAX_INT||12.X or lower|
|serverside_network_latency||Avg Server Network Latency||0||12.X or lower|
|max_serverside_network_latency||Max Server Network Latency||0||12.X or lower|
|min_serverside_network_latency||Min Server Network Latency||MAX_INT||12.X or lower|
|request_duration_hitcount||Avg Request Duration||0||12.X or lower|
|max_request_duration||Max Request Duration||0||12.X or lower|
|min_request_duration||Min Request Duration||MAX_INT||12.X or lower|
|response_duration_hitcount||Avg Response Duration||0||12.X or lower|
|max_response_duration||Max Response Duration||0||12.X or lower|
|min_response_duration||Min Response Duration||MAX_INT||12.X or lower|
The HTTP statistics tables were updated in this version. When upgrading from version 12.X or lower, non-cumulative metrics of the affected dimensions may display slightly different values after the upgrade.
The following table lists the affected HTTP dimensions and the initial values displayed in the GUI following an upgrade from a previous version. Once new data is collected, the displayed value will appear as expected for the dimension.
|Phone - North America:||1-888-882-7535 or (206) 272-6500|
|Phone - Outside North America, Universal Toll-Free:||+800 11 ASK 4 F5 or (800 11275 435)|
|Fax:||See Regional Support for your area.|
For additional information, please visit http://www.f5.com.
You can find additional support resources and technical documentation through a variety of sources.
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 is your storehouse for thousands of knowledgebase articles that help you manage your F5 products more effectively. Whether you want to browse periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
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.
To subscribe, click AskF5 Publication Preference Center, enter your email address, select the publications you want, and click the Submit button. You will receive a confirmation email. You can unsubscribe at any time by clicking the Unsubscribe link at the bottom of the email, or on the AskF5 Publication Preference Center screen.