Release Notes : BIG-IP 15.0.0 New and Installation

Applies To:

Show Versions Show Versions

BIG-IP DNS

  • 15.0.0

BIG-IP FPS

  • 15.0.0

BIG-IP Analytics

  • 15.0.0

BIG-IP AFM

  • 15.0.0

BIG-IP PEM

  • 15.0.0

BIG-IP ASM

  • 15.0.0

BIG-IP Link Controller

  • 15.0.0

BIG-IP APM

  • 15.0.0

BIG-IP LTM

  • 15.0.0
Release Notes
Software Release Date: 05/23/2019

Summary:

These release notes document the BIG-IP version 15.0.0.x releases. You can apply the software upgrade to systems running software version 13.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, 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.

Note: The BIG-IP VE product license determines the maximum allowed throughput rate. To view this rate limit, you can display the licensing page within the BIG-IP Configuration utility.

Contents:

Platform support

For comprehensive information about supported platforms, see:

Module combination and memory considerations

BIG-IP platform considerations

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:

  • vCMP supported platforms
    • VIPRION B2100, B2150, B2250
    • VIPRION B4300 blade in the C4480(J102) and C4800(S100)
    • VIPRION B4450 blade in the C4480(J102) and C4800(S100)
    • BIG-IP 5200v, 5250v, 7200v, 7250v, 10200v, 10250v, 10350v, 12250v
    • BIG-IP i5800, i7800, i10800, i11800, i15800
  • PEM and CGNAT supported platforms
    • VIPRION B2100, B2150, B2250, B4300, B4340N, B4450N
    • BIG-IP 5x00v(s), 7x00v(s), 10x00v(s)
    • PEM for BIG-IP iSeries: i5800, i7800, i10800, i11800, i15800
    • CGNAT for BIG-IP iSeries: i2x00, i4x00, i5x00,i7x00,i10x00,i11x00,i15x00
    • BIG-IP Virtual Edition (VE) (Not including Amazon Web Service Virtual Edition) (3 GB, 10 GB production and combination lab models)
    • PEM may be provisioned on the VIPRION B2100, but it is not recommended for production, only for evaluation. Use the B4300/B4340N or another blade instead.
    • PEM is not supported on vCMP guests.
    • PEM is not supported on 8 GB platforms.
  • BIG-IP 800 and i850 platform support
    • The BIG-IP 800 and i850 platforms support 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. 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.

Memory: 8 GB

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.)

  • 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.
  • To use Access Policy Manager (APM) and Secure Web Gateway (SWG) modules together on platforms with exactly 8 GB of memory, Local Traffic Manager (LTM) provisioning must be set to None.

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.
  • Analytics (AVR) counts towards the two module-combination limit (for platforms with less than 6.25 GB of memory).

Memory: 4 GB or less (VE and vCMP only)

The following guidelines apply 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.
  • ASM 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

 

VE considerations

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.

Memory: 12 GB or more

All licensable module-combinations may be run on BIG-IP Virtual Edition (VE) guests provisioned with 12 GB or more of memory.

Memory: 8 GB

The following guidelines apply to VE guests configured with 8 GB of memory.

  • No more than three modules should be provisioned together.

Memory: Less than 8 GB and more than 4 GB

The following guidelines apply to VE guests provisioned with less than 8 GB and more than 4 GB of memory.

  • 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.

Memory: 4 GB or less

The following guidelines apply to VE 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.
  • ASM should not be provisioned, except as Dedicated

User documentation for this release

For a list of Virtual Edition (VE) hypervisor support, see the Virtual Edition and Supported Hypervisors Matrix.

Configuration utility browser support

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

  • Microsoft Internet Explorer 11.x, or later
  • Mozilla Firefox v62.0, or later
  • Google Chrome v69.0.3497, or later

Compatibility of BIG-IQ products with BIG-IP releases

K34133507: BIG-IQ Centralized Management compatibility matrix provides a summary of version compatibility between the BIG-IQ Centralized Management and BIG-IP releases.

New in 15.0.0 :: LTM/TMOS

Support for session persistence in HTTP/2 full-proxy deployments

This release supports additional session persistence types for HTTP/2 full-proxy deployments.

Diameter Dynamic Routing

This release include Diameter dynamic routing, a complementary solution to persistence, which you can use to forward messages to the same host.

Prioritization of ICMP health monitor traffic

You can now configure the BIG-IP system to prioritize ICMP and ICMP Gateway health-monitor traffic over all other types of traffic. This feature minimizes the chance that ICMP health-monitor traffic is dropped when traffic congestion occurs at a BIG-IP switch, at a high-speed bridge, or on a TMM instance.

HTTP chunked transfer encoding

The HTTP Request Chunking and Response Chunking profile settings have been enhanced to allow the profile and other internal functions to better control the chunking or unchunking of a payload as it transitions through the system. HTTP chunked transfer encoding is controlled within the HTTP profile. Chunking in the HTTP profile has a list of three options which directly inherits Unchunk and Rechunk, deprecating Preserve and Selective and replacing them with a new Sustain option. Sustain tries to preserve existing transfer encoding unless a hudfilter makes it irreversible.

Client Certificate Constrained Delegation Support (C3D)

Expanded functionality for Client Certificate Constrained Delegation Support (C3D).

Fallback pool for policies

You can now select 'fallback-pool' along with primary 'pool' using LTM policy. If primary pool present in the forward action is unavailable, then LTM policy will forward traffic to the fallback pool. LTM policy forwards traffic only if primary 'pool' within that action is not available. You must specify 'pool' along with 'fallback-pool' and both cannot have same pool name.

Message Routing Framework.

This functionality supports both the load-balancing and routing. A 'diameter-session' profile for protocol-specific configuration and 'diameter-router' profile for specifying the static-route configurations are implemented as part of this feature. Both these profiles must be present in the virtual server configuration for Diameter that uses the MR framework.

CGNAT: Port Block Allocation periodic block refresh logs

This release includes a new logging option that logs Port Block Allocation (PBA) block periodically with a configurable refresh time.

CGNAT: Provide statistics to count numbers of subscribers and active translation addresses

This release includes new statistics to count the number of active subscribers, the peak active subscribers, number of translation addresses in use, and the number of active connections per translation prefix

Enhanced Diameter Statistics

This release includes Diameter statistics aggregated by peer and pool level.

Diameter Loop Detection

This release includes Diameter loop detection to support proper routing of Diameter messages, ensuring that a message is not endlessly routed between two Diameter agents.

MRF: Diameter support for Tcl Context per Message

This release includes a feature enhancement to MRF protocols by providing every ingress and egress message with its own private Tcl execution context, thus limiting the scope of iRule variables.

iRule Session and Table support in HTTP/2

The iRule 'session' and 'table' commands can now be used in iRules assigned to Virtual Servers configured with the HTTP/2 and httprouter profiles (i.e., HTTP/2 full proxy mode). These commands previously did not work in BIG-IP version 14.1.0 when HTTP/2 full proxy mode was introduced. These iRule commands have already been documented on DevCentral.

Ramcache Support for HTTP/2

The 'webacceleration' profile can now be assigned to Virtual Servers configured with the HTTP/2 and httprouter profiles (i.e., HTTP/2 full proxy mode). In other words, RAM cache is now working with HTTP/2 full proxy virtual servers that use the MRF router. This is a phase 1 implementation that gets HTTP/1.1 semantics working, but the profile does not cache HTTP/2 PUSH responses.

Remote CA Certificate Generation CA API support

This feature allows API access to Certificate Authorities in order to perform the following functions:
  • Request new certificates.
  • Renew existing certificates (including automatic renewal when within 2 weeks of the certificate expiring).
  • Revoke existing certificates.
The CAs that this feature supports are:
  • Sectigo (was Comodo).
  • Digicert (for those who started with Symantec).

Support for RSA PSS Padding in Cavium HSM Cards

This feature updates our support of Cavium Nitrox III FIPS HSMs (N3FIPS) to allow generating RSA PSS signature using private keys stored in Cavium FIPS HSM. This is required for support of TLS 1.3 support.

MRF Per-Peer Statistics

This release supports Message Routing Framework (MRF per-peer statistics. Service providers require the ability to monitor the health of clients and servers by observing the traffic between the BIG-IP system and other devices in the network. You can now observe traffic to and from a connected device using statistics.

tcpdump support for encrypted traffic

This release adds handling of encrypted traffic in tcpdump operations

Logging of Login Attempts

This release provides the ability to log login attempts.

New in 15.0.0 :: ASM

OWASP Compliance Dashboard

The OWASP Compliance Dashboard details the coverage of each ASM security policy for the top 10 most critical web application security risks as well as the changes needed to meet OWASP compliance. Using the dashboard, you can quickly improve security risk coverage and perform security policy configuration changes.

Public APIs Protection

AWAF feature. Customer-specific OpenAPI files, in Swagger format, can be loaded to the platform to automatically create a security policy attached to a specified virtual server.

HTTP Header Sequence Behavioral Metric

Certain bots spoof legitimate browsers by attempting to copy browser requests. These copy attempts are inaccurate and give disorganized HTTP header sequences. The HTTP header sequence can be used as a signature metric in distinguishing between real browsers and Bad Actor bots that have inaccurately copied HTTP browser request headers.

DoS-L7 Traffic Passive Monitoring via Switched Port Analyzer

This feature is now production ready.

HTTP/2 Support

ASM Security Policies, DoS L7 and Bot Defense support HTTP/2 over SSL/TLS on both the client and server sides, without having to translate the client HTTP/2 traffic to HTTP/1.1 on the server-side. Server pushed requests are ignored, meaning that they are not inspected or enforced. Log data includes an HTTP Version field but server pushed requests are not logged or counted in suspicious traffic statistics.

Failed Challenge Logging

Challenge failures are now logged in the event logs for Application Security and Bot Defense. Remote logging is available for Bot Defense in the field challenge_failure_reason.

User JSON Schema

A JSON schema for user REST endpoints can be uploaded to a JSON profile. The schema is validated when uploaded and any violations are noted. After a JSON schema is selected, the Parse Parameters setting is disabled because the policy stops using any configured policy parameters and begins using the JSON parameters.

API Security

Guided Configuration. API calls originating from enterprise, partner, and consumer applications that access cloud and on-premise resources require strong authentication and identity mediation. You can use Guided Configuration in ASM to configure API Security to protect API calls.

The API Protection Dashboard displays API server health including security events that were flagged, such as web application attacks, bad source IP addresses, and malicious transactions. You can use the dashboard for troubleshooting API Security.

New in 15.0.0 :: APM

Guided Configuration

Guided Configuration 5.0 includes enhancements for BIG-IP release 15.0. Guided Configuration for BIG-IP Access Policy Manager (APM) provides simple, workflow-driven configuration templates for common use case scenarios. Using the templates, you can create per-session and per-request policies to implement complex scenarios such as Zero Trust (Identity Aware Proxy), API Protection, and Federation Single Sign On more easily. Later, you can edit the policies in the Guided Configuration interface or using the traditional BIG-IP interface. Refer to the Release Notes for Guided Configuration 5.0 for details on the enhancements and how to upgrade to the latest Use Case Packs.

API Protection

Access Policy Manager lets you configure an API protection proxy for securing API calls. In this release, you can configure rate limiting thresholds, control traffic spikes, and use a whitelist and blacklist to allow or restrict specific network traffic. Configuration is simplified using the Guided Configuration for API Protection. The API Protection Proxy template is provided in the Guided Configuration ( Access > Guided Configuration ). You can also use the Access menus to implement API protection use cases.

API Protection Dashboard

You can use the API protection dashboard for troubleshooting potential problems on your system. If using APM only, you can review the total number of requests, API server errors, rejections at the BIG-IP system (proxy errors), and determine the response time range for each API protection profile. If using AdvWAF (ASM provisioned) in addition, the dashboard also displays API server health including security events that were flagged, such as web application attacks, bad source IP addresses, and malicious transactions.

Enhancements for Step-Up Authentication and Zero Trust

To make it easier to trust no one, many agents previously available only in per-session policies are now available in per-request policies. These agents allow you to perform additional forms of step-up authentication on a per-request basis. A new Assign Credentials agent was also added to per-request policies. You use these agents in a subroutine in a per-request policy to protect each request.

Agents Added to Per-Request Policies Description
AD Query agent Gets user attributes for resource assignment or other functions, such as AD group mapping.
Assign Credentials agent New agent. Provides the username and password source session variable names. and stores them in perflow variables. Agent must come before the subroutine where the credential needs to be reused.
Client Cert Inspection agent Checks last result of the On-Demand Cert Auth agent, and goes to the fallback branch if no On-Demand Cert Auth agent is found in front of it.
Email agent Sends email messages for reporting.
LDAP Query agent Gets user attributes for resource assignment or other functions, such as LDAP group mapping.
Logon Page agent Modified to add extra logic to auto-submit credentials assigned by the Assign Credentials agent, and save the submitted credentials if the Save Validated User Credentials are set and the authentication agent has not failed.
OTP Generate agent Generates One Time Passcode (OTP).
OTP Verify agent Verifies One Time Passcode (OTP).
Pool Assign agent Supports application and application-group configuration by connecting to the backend application based on the URL branching classification.
Radius Acct Agent Sends accounting messages to a RADIUS server when users log on and off.
SAML Auth Agent Provides SAML authentication using the SAML Service Provider Interface, for example, when end users access different resources. APM must be configured as a service provider for this to work.
Note: No current support for Single Logout (SLO) when the main per-session policy or any subsession times out or dies.

Refer to BIG-IP APM: Implementing Zero Trust with Per-Request Policies on support.f5.com for per-request policy use cases.

Support for device posture checks

APM now supports device posture checks on macOS or Windows clients on a per-request basis. You implement device posture checks in a per-request policy by using a Client Information agent followed by a subroutine with one or more client check agents.

You can continuously check the state of the following:

  • Antivirus
  • Endpoint State
  • Firewall
  • Hard Disk Encryption
  • Patch Management
  • Public File Sharing
  • System Health Check

Continuous client checks require F5 Access Guard and a browser extension.

Customizable remediation for failed device posture checks

APM now provides a customizable remediation page for requests denied as a result of a failed device posture check. The Reject Ending in a per-request policy can display messages or URLs that help to resolve the device posture issue. New error codes are also added.

F5 Access Guard

F5 Access Guard is a new set of client software tools designed to help administrators validate the security posture of incoming web connections from remote desktop clients. F5 Access Guard allows real-time posture information to be inspected with per-request policy subroutines on BIG-IP Access Policy Manager. F5 Access Guard generates posture information asynchronously and transparently transmits it to chosen APM server endpoints using special HTTP headers. Refer to the Release Notes for F5 Access Guard 1.0 for details.

Sharing of credentials across subroutines

Subroutines now include session variables, which are used to save authenticated credentials. When a user is authenticated in one subroutine, you can configure a subsequent subroutine to use the saved credentials for authentication. To share a saved credential between subroutines, configure the session variables in the subroutine to be the same as the session variables configured in the Assign Credential agent. Be sure to position the Assign Credential agent so it is located before the subroutine in the per-request policy.

SSLO authentication as transparent proxy

APM now supports authentication offload for SSL Orchestrator configured as a transparent forward proxy. Authentication is done through a captive portal or using user access profile scope (named and public) to offload authentication for proxy-chaining.

NTLM Authentication enhancement

Microsoft has deprecated SMBv1 due to security impacts. F5's NTLM authentication no longer uses SMBv1. We now implement MSRPC over TCP.

New in 15.0.0 :: AFM

DoS/DDoS: Auto-Discovery of services

This release provides support for Auto-Discovery of services.

Zone based firewall rules

This release supports Zones, or lists of VLANs used for packet matching.

DoS/DDoS: Hardware Debug Registers

This release supports new hardware debug registers, providing information about how packets are handled in hardware.

DoS/DDoS: Add BGP FlowSpec actions

This release supports new BGP FlowSpec actions for scrubbing or redirecting IP addresses.

IP-Intelligence: Allow GEO locations.

This release supports the use of GEO locations in IP Intelligence categories.

IP-Intelligence: Allow Fully Qualified Domain Names (FQDN).

This release supports the use of FQDNs in IP Intelligence categories.

IPv6 Packet Filters

This release supports IPv6 Packet Filters, allowing inspection of IPv6 Extension Header types.

Protocol Inspection: SCTP support

This release supports SCTP protocol inspection.

Protocol Inspection: Diameter support

This release supports Diameter protocol inspection.

Traffic Intelligence: Classification over encrypted QUIC

This release supports Traffic Intelligence: Classification over encrypted QUIC.

New in 15.0.0 :: DNS

DNS cache scalability and sizing enhancements

This release provides greater DNS cache scalability and sizing enhancements.

New in 15.0.0 :: FPS

Use of DOM Signatures for Malware Detection

The Malicious Words feature has been improved and renamed as DOM Signatures. Use DOM Signatures to set the location in the webpage where the BIG-IP system searches for suspicious character strings (can be alphanumeric, non-alphanumeric, or a combination of both). If the BIG-IP detects a blacklisted string in the location you specify, an alert is sent to the FPS dashboard.

FPS Logging Profiles

In BIG-IP 15.0.0, you can create Fraud Protection logging profiles to log information on client attempts to login to your protected website, and to log information on FPS alerts sent by the BIG-IP system. Once the logging profile is properly configured, the BIG-IP system sends the logs to a third-party platform of your choice. The logging profile includes an option to create your own template to determine what information is included in the logs, or to use a default template.

GUI Enhancements

Various improvements have been made to the FPS GUI to provide a more logical and user-friendly presentation of FPS configuration.

Geo-location reporting in alerts

The Collect Geolocation Coordinates setting has been added to the advanced general profile settings. When this setting is enabled:

  • For a standard web-application (not mobile), the web browser will ask the end-user if he approves revealing his location. If the end-user approves, geo-location coordinates will be included in alerts. If the end-user does not approve, alerts will indicate that the end-user did not approve revealing his location.
  • For mobile apps, the software developer needs to provide the MobileSafe SDK with the location data so that geo-location coordinates will be included in alerts. See the F5 MobileSafe Deployment and Configuration Guide, ver. 7.0 for more details on how do this.

Improved client-side performance

General client-side performance and loading time has been improved for FPS-protected websites running on the latest web browsers.

New in 15.0.0 :: PEM

Enhancements to PEM HSL logs

This release includes new functionality enhancements in HSL flow and session reporting. You can disable start and interim messages to save network bandwidth and add new reporting fields (dropped flows and flow duration) to provide more visibility about subscribers.

Enhanced iRule commands and events for subscriber creation

This release adds several new iRule events for PEM session creation, modification, and deletion.

New in 15.0.0 :: VE

Updated socket driver supporting up to 10Gbps throughput

This release provides an updated socket driver in BIG-IP Virtual Edition (VE) to enable improved performance (up to 10Gbps throughput) running in Microsoft Azure cloud and Hyper-V hypervisor.

Cloud-specific metadata added to default info sent by VE to PhoneHome service

This release adds cloud-specific metadata to default info sent by BIG-IP VE to the PhoneHome service.

New in 15.0.0 :: Cloud

No new features

There are no new cloud-specific features in this release.

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 Software, and we strongly recommend that you reference this information 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 K12878: Generating diagnostic data using the qkview utility.
  • Update/reactivate your system or vCMP host license, if needed, to ensure that you have a valid service check date. For more information, see K7727: License activation may be required before a software upgrade for the BIG-IP or Enterprise Manager system.
  • Ensure that your system is running version 13.x or later.
  • Download the .iso file 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.
  • Check all DNSSEC Key generation's 'expiration' and 'rollover' date:time fields before performing a GTM sync group upgrade. If any of the DNSSEC Key generations are set to rollover or expire during the planned upgrade window, modify the date:time of the 'expiration' and/or 'rollover' fields to extend past the anticipated upgrade window, to a date:time when all units in the sync group will again have GTM config sync enabled.
  • 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 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 13.0.0 to volume 3 of the main hard drive.

tmsh install sys software image BIGIP-13.0.0.0.0.1645.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 Software, and we strongly recommend that you reference this information 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 K12878: Generating diagnostic data using the qkview utility.
  3. Log on to the browser-based Configuration utility.
  4. Run the Setup utility.
  5. Provision the modules.
Note: You can find information about running the Setup utility and provisioning the modules in 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 earlier configurations

When you upgrade from an earlier versions of the software, you might need to know about or take care of these configuration-specific issues.

ID Number Description
394873 Upgrade process does not update Tcl scripts Upgrading Tcl scripts (such as iRules). This might cause issues when iRule syntax changes between releases. After upgrading, you might need to modify iRules to reflect any changes in iRule syntax. The upgrade process does not update Tcl scripts (such as iRules) in the configuration. Workaround: None.
530010 FIPS firmware v2.2 update on BIG-IP 5250, 7200F, 10200F, and 11050F platforms running the Cavium Nitrox XL FIPS cards. "This impacts BIG-IP 5250, 7200F, 10200F, and 11050F FIPS platforms running FIPS firmware 2.1 or earlier. You can tell what firmware you have installed by running the following command at the command line: fipsutil info The firmware version listed should be the following: CN16XX-NFBE-FW-2.2-130013." "All platforms shipped prior to June 30th, 2016, contain an older firmware version and must be updated to run the NIST-approved version. To comply with current NIST requirements, the new firmware has deprecated support for 1024-bit key creation. Existing 1024-bit keys in the device can still be used normally." On BIG-IP 5250, 7200F, 10200F, and 11050F platforms running the Cavium Nitrox XL FIPS cards, the FIPS firmware version 2.1 has been moved to the Legacy list by NIST as the RNG function does not meet modern-day FIPS standards. For more information, see the external resource, available here: http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm. Workaround: "F5 Networks has released a downloadable firmware installer that you can download and apply to the platforms containing the FIPS firmware 2.1 or earlier. For more information about FIPS compliance, see SOL7837: Overview of FIPS 140-2 EAL Level 2 and 3 RoHS Certification Status, available here: https://support.f5.com/kb/en-us/solutions/public/7000/800/sol7837.html." FIPS firmware v2.2 update on BIG-IP 5250, 7200F, 10200F, and 11050F platforms running the Cavium Nitrox XL FIPS cards.
566998 Edge client upgrade fails if client was configured in locked mode "Edge client package was downloaded with ""Enable Always Connected mode"" option checked Server contains a newer version of edge client" Automatic upgrade of edge client will fail Edge client cannot be upgraded automatically to a newer version Workaround: Manually uninstall and re-install client
575347 Unexpected backslashes remain in monitor 'username' attribute after upgrade Upgrading from an earlier version with a configuration that contains a monitor 'username' attribute with at least one escaped backslash ('\\'). Monitor probes contain excess backslashes which can lead to monitor failures. The monitor 'username' attribute contains unexpected backslashes. Workaround: Un-escape backslashes after upgrade by transforming '\\' sequences to '\'. Removed excess backslashes from monitor 'username' attribute during upgrade process.
576521 If you have MSSQL proxy feature configured, you will lose it upon upgrading to v13.0.0 or later. "-- MSSQL proxy is configured. -- Upgrade to v13.0.0 or later." You will lose MSSQL proxy feature upon upgrade to v13.0.0 or later. MSSQL proxy is no longer supported. MSSQL proxy is removed from BIG-IP product. Workaround: None. If you have MSSQL proxy feature configured, you will lose it upon upgrading to v13.0.0 or later.
580602 Configuration containing LTM nodes with IPv6 link-local addresses fail to load. Attempt to load a configuration containing a LTM node with a IPv6 link-local address. Configuration fails to load. As a result of a known issue a configuration containing LTM nodes with IPv6 link-local addresses may fail to load. Workaround: Use IPv6 global addresses instead. Bigip now loads correctly a configuration containing a LTM node with a IPv6 link-local address.
581824 "Instance not found" error when viewing the properties of GSLB monitors gateway_icmp and bigip_link. Viewing the GSLB Monitors tcp_half_open, gateway_icmp and bigip_link's properties page. You cannot view some of their monitors' properties. When you attempt to view the monitors' properties, the page throws an "Instance not found" error. Workaround: Fixed the "Instance not found" error.
596104 HA trunk unavailable for vCMP guest "This occurs when an HA trunk is configured a vCMP guest, with a threshold value greater than 0. This may occur by any of the following means: 1) Attempting to upgrade a guest to an affected version of BIG-IP, with an HA trunk configured with a threshold value greater than 0. The upgrade fails with the indicated error message. 2) Attempting to load a UCS from a guest with an HA trunk configured with a threshold value greater than 0. The UCS load fails with the indicated error message. 3) Creating an HA group and then attempting to modify the threshold value for the HA trunk. The modify command fails with the indicated error message." "HA trunks do not work. You cannot upgrade the vCMP guest to an affected version of BIG-IP or load a configuration with an HA trunk configured with a threshold value greater than 0." "If a vCMP guest is configured with a high availability (HA) trunk with a threshold value greater than 0, the HA trunk configuration fails with a message similar to the following: err mcpd[5926]: 01071569:3: Ha group ha_group threshold for trunk _your_trunk_name_here_ 1 is greater than the maximum number of members 0." Workaround: "To allow the upgrade to succeed or the configuration to load, configure the HA trunk threshold to 0. Important! This disables the HA trunk feature." HA trunks with a threshold value greater than 0 are supported on vCMP guests.
596826 Don't set the mirroring address to a floating self IP address Accidentally setting the mirroring IP address to the floating self IP address using tmsh. Mirroring does not work in this case. If you configured it this way using tmsh, the GUI will show the primary and secondary mirroring address as "None". "Using tmsh, you can configure the mirroring IP address using the command tmsh modify cm device devicename mirror-secondary-ip ip_address It is possible to set ip_address to a floating self IP address when using tmsh, but BIG-IP can't mirror to a floating self IP address. The tmsh command will complete without error." Workaround: "Change the mirroring address to a non floating self IP address. The GUI will only present non floating self IP addresses. For more information about mirroring, see K13478: Overview of connection and persistence mirroring at https://support.f5.com/csp/#/article/K13478"
597253 HTTP::respond tcl command may incorrectly identify parameters as ifiles "HTTP::respond command making use of a variable as a header name. For instance: HTTP::respond 500 -version 1.1 content ""<content>"" ""$VariableHeaderName"" ""header_value_text"" ""Connection"" ""close"" Configure a HTTP/TCP virtual server and attach the iRule." 1070151:3: Rule [/Common/example_rule] error: Unable to find ifile (header_value_text) referenced at line 3: [HTTP::respond 500 -version 1.1 content "<content>" "$VariableHeaderName" "header_value_text" "Connection" "close"] The HTTP::respond iRule command may incorrectly identify parameters as an iFile parameter when attaching the iRule to a Virtual Server. Workaround: Ensure the offending header name and value are either both literal strings or variables. BigIP no longer incorrectly identifies parameters as an iFile parameter.
597951 Upgrade fails when MSSQL and IIOP profiles exist in bigip.conf. This occurs when an MSSQL or IIOP profile exists in the configuration. Configuration does not load after upgrading. "Beginning with this version of the software, the MSSQL and IIOP profiles are no longer supported. If you upgrade a configuration that contains a MSSQL and IIOP profile, the config load fails, and the system posts the following error message: emerg load_config_files: ""/usr/bin/tmsh -n -g load sys config partitions all"" - failed. -- 01020036:3: The requested profile (/Common/mssql) was not found. Unexpected Error: Loading configuration process failed." Workaround: Manually delete the profiles from bigip.conf and try the upgrade again.
600811 Starting in v12.1.1, the CATEGORY::lookup iRule command will no longer accept an HTTP URI in its argument to the command if the BIG-IP system has APM and URL Filtering provisioned or just URL Filtering provisioned along for SSL Bypass decisions. Only a valid hostname can be used and have its category returned. In versions prior to v12.1.1, the following iRule command was valid:

              when HTTP_REQUEST {
              set this_uri http://[HTTP::host][HTTP::uri]
              set reply [CATEGORY::lookup $this_uri]
              log local0. "Category lookup for $this_uri returns $reply"
              }

Starting in v12.1.1, using the previous example, you must remove the HTTP::uri statement. If an HTTP::uri is provided to the command, the system returns an error similar to the following: err tmm2[12601]: 01220001:3: TCL error: /Common/_1_categ_test <HTTP_REQUEST> - Categorization engine returned an error. invoked from within "CATEGORY::lookup $this_uri" Correcting the iRule for post-v12.1.1 installation, the example must be modified to pass in the HTTP::host only, as follows:

                when HTTP_REQUEST {
                set this_uri http://[HTTP::host]
                set reply [CATEGORY::lookup $this_uri]
                log local0. "Category lookup for $this_uri returns $reply"
                }

Note: If APM and SWG are licensed and provisioned, the CATEGORY::lookup iRule command will accept an HTTP URI as a part of the argument to the command. - BIG-IP licensed and provisioned for: o APM and URL Filtering o URL Filtering (used for SSL Bypass decisions in SSL Air-Gap deployments). - An iRule that supplies a URI path to the CATEGORY::lookup iRule command. - Upgrading from pre-v12.1.1 versions that use the CATEGORY::lookup iRule command and use an HTTP::uri or pass in a plain text string that contains anything other than an HTTP hostname. There is an error returned from the command. This can cause errors in existing deployments. Workaround: Update the iRule to only pass an HTTP hostname to the CATEGORY::lookup iRule command.
601420 Possible SAML authentication loop with IE and multi-domain SSO. APM is configured with SAML authentication and multi-domain SSO. Using Internet Explorer, the client may not be unable to connect to its desired destination. When APM is configured with SAML authentication and multi-domain SSO, Internet Explorer may encounter authentication loop and never complete the access policy. Workaround: Chrome and Firefox do not seem to be affected. Use cookie for session for multi-domain if TOKEN lookup fails. Previously, the cookie was ignored for multi-domain response URI. However, with the introduction of TOKEN based session lookup, this causes a failure if the client retries the request (since the TOKEN was consumed in the request prior to the retry).
606573 FTP traffic does not work through SNAT when configured without Virtual Server The BIG-IP system configured to allow FTP traffic through, and SNAT is configured without a virtual server. The BIG-IP system does not SNAT port 21 traffic. In rare circumstances this can cause tmm to restart. After upgrading to 12.1.0 or 12.1.1, FTP traffic no longer works correctly with SNAT, when SNAT is configured without a virtual server. Workaround: None. FTP traffic now works through SNAT when SNAT is configured without a virtual server.
621374 "abbrev" argument in "whereis" iRule returns nothing iRule relying on whereis abbrev is used. The whereis iRule command will not return the expected value. The iRule [whereis <ip|ldns> abbrev] does not return a value. Workaround:
624044 LTM Monitor custom recv/send/recv-disable parameters have backslash at the end may fail to load Any of the "recv", "send", or "recv-disable" parameters having a backslash at the end, and the configuration is saved. The new configuration fails upon reload. If LTM monitor configuration parameters have custom strings that end with backslash, the saved configuration will fail to load. Workaround: Do not end custom strings with backslashes. BIG-IP no longer allows custom strings to end with backslash. The system presents a validation error.
630430 IPsec ALG: Traffic may not go through IPsec tunnel if ipsec.lookupspi is disabled and default DAG is used This may occur on appliances when the IPsec ALG is used with default DAG and the sys db variable ipsec.lookupspi is disabled. Connections going through the IPsec tunnel may fail. The connection table and IPsec ALG profile stats may indicate that the IPsec tunnel has been established, but traffic may not be passing through it. Workaround: Ensure the db variable ipsec.lookupspi is enabled.
631369 Empty external data-groups fail to load Config references an empty or missing datagroup. Config fails to load. "Config will fail to load after upgrade or ucs restore with error regarding an empty or missing data group: 01070630:3: The requested data group file (/config/filestore/.stage_d/130_d/Common_d/data_group_d/:Common:empty_48650_1) was not found or empty)." Workaround: Remove references to empty or missing datagroups. You can now use an empty file as an external data-group, and it will simply behave as though it has 0 elements.
637811 Upgrade failure when Common Criteria Mode is enabled Common criteria mode is enabled (i.e., the db variable security.commoncriteria is set to true). Software cannot be updated using the Web UI. The install fails with no indication as to why. When the software is in "Common Criteria Mode", an upgrade via the Web UI is not possible, because the upgrade process automatically generates a UCS file, but Common Criteria requires that a password be supplied whenever a UCS is generated. The Web UI does not take this in to account, and never asks for a password for the UCS file. Workaround: Disable Common Criteria Mode before upgrade by setting the db variable security.commoncriteria to false.
638935 Monitor with send/receive string containing double-quote may cause upgrade to fail. Configuration where monitor string contains \" (backslash double-quote) but does not contain one of the following characters: ' (single quote), | (pipe), { (open brace), } (close brace), ; (semicolon), # (hashtag), literal newline, or literal space. Configuration fails to load. When you upgrade from an affected version, the config gets saved before moving to the new version, thus dropping the enclosing quotes and causing a load failure when booting into the new version. Workaround: Manually edit each string in the bigip.conf to include enclosing quotes in order to get the config to load the first time. "Configs load successfully after upgrade. Surrounding quotes, if missing, are added to strings in the bigip.conf file after upgrade. For example: \""service_status\"":\""on\"".+\""maintenance\"":\""off\"" in the recv, send recv-disable and username fields. Output of list ltm monitor and bigip.conf match. Reloading the same config via tmsh does not cause unintentional changes, such as losing a level of escape in monitor strings. If you have an escaped quote in your configuration, and are moving to a configuration with this the dependency of this fix, you cannot reload the configuration or the license which also reloads the configuration. Doing so, will cause the config load to fail."
643768 Invalid entries in SNMP allowed-address and SNMP community fields can cause upgrade failure. "This can happen when upgrading from a release older than 13.0.0, and there is an invalid entry in the SNMP allowed-address field or communities source field, such as: sys snmp { allowed-address { 1.0.0.0/2.0.0.0 ""1.1.1.1 2.2.2.2"" 3.3.3.3,4.4.4.4 } communities { /Common/test { community-name test source 1.0.0.0/foo } } }" Upgrade to 13.0.0 fails if the configuration contains these invalid values, due to input validation that was added in this version. "If there are invalid entries in the SNMP allowed-address field, or in the SNMP communities source field, upgrade to v13.0.0 fails to load the configuration on validation of the input, with this error signature: 01070911:3: The requested host (<host-ip-address>) is invalid for allow in snmpd (/Common/snmpd), Unexpected Error: Loading configuration process failed." Workaround: Remove the invalid entries from these 2 field types before doing an upgrade to 13.0.0. The fix removes the invalid entries from the configuration on upgrade automatically.
645203 Configuration load fails after upgrade when a SAML SSO config object is put in a sync-only device group When a SAML SSO config object or a Form-Based SSO config object is configured in a folder and that folder is in a Sync-Only device group. When upgrading with the existing configuration, the configuration load will fail. The configuration does not load. Configuration load fails after upgrading BIG-IP from a previous version. The system posts an error similar to the following: 01070734:3: Configuration error: Invalid Devicegroup Reference. The sso_config_saml (/Common/Auth/<object>) requires apm_log_config (/Common/sso-log-setting-Notice) to be syncd to the same devices Unexpected Error: Loading configuration process failed." Workaround:

              1. Disassociate the folder from Sync-Only device group using the following commands: tmsh modify sys folder <folder name> device-group none tmsh save sys config.
              2. Upgrade and verify config loads.
              3. Create log-setting in each folder.
                  root@(temp12)(cfg-sync In Sync (Sync Only))(/S1-green-P:Active)(/Common)(tmos)# cd <folder name>/
                  root@(temp12)(cfg-sync In Sync (Sync Only))(/S1-green-P:Active)(/Common/<folder name>)(tmos)# create apm
                      log-setting sso-log-setting-Notice { access add { general-log { log-level { access-control notice } publisher sys-sso-access-publisher } } }
              4. Repeat this step for each log level: Alert, Critical, Debug, Emergency, Error, Informational, Notice, Warning, and use the appropriate log level accordingly.
              5. Modify SSO log-settings to use log-setting created under the folder (<folder name>), according to their previous log level before upgrading. For example,
                      root@(temp12)(cfg-sync In Sync (Sync Only))(/S1-green-P:Active)(/Common)(tmos)# modify apm sso saml <folder name>/<sso object
                      name> apm-log-config <folder name>/sso-log-setting-Notice
              6. Associate Sync-Only device group SO1 to folder, as shown in the following example:
                      root@(temp12)(cfg-sync In Sync (Sync Only))(/S1-green-P:Active)(/Common)(tmos)# modify sys folder <folder name>/ device-group <DG name>
              7. Verify config load.

Configuration load now completes successfully after upgrade when a SAML SSO config object is put in a sync-only device group.
645206 Missing cipher suites in outgoing LDAP TLS ClientHello You have LDAP servers requiring SHA256 and SHA384 ciphers for LDAP/TLS authentication. Servers requiring SHA for LDAP/TLS authentication will no longer be able to authenticate. This could suddenly break LDAP auth if you are upgrading from version 11.x where SHA256 and SHA384 existed. BIG-IP drops all SHA256 and SHA384 ciphers in the advertised ciphers list in the Client Hello when initiating LDAP/TLS with a pool member (in the case of a monitor). The same behavior is also seen for BIG-IP system auth via LDAP or AD when TLS is used. Workaround: Configure LDAP servers not to be dependent on SHA256 and SHA384 ciphers. The BIG-IP system now supports SHA256 and SHA384 ciphers in the advertised ciphers list in the Client Hello when initiating LDAP/TLS with a pool member (in the case of a monitor). You also see the same behavior for the BIG-IP system auth by way of LDAP or AD when TLS is used.
649759 ssmtp RewriteDomain setting is set to the empty string. This applies when the 'sys outbound-smtp rewrite-domain' setting is unset. It is difficult to determine the originating device for system email. The ssmtp RewriteDomain setting is set to the empty string. Therefore, the From address in any email sent by the BIG-IP has an empty domain. Workaround: Set the 'sys outbound-smtp rewrite-domain' to the local hostname. The ssmtp RewriteDomain setting is no longer set to the empty string. If 'sys outbound-smtp rewrite-domain' is unset, no rewriting will occur and the From address will have the hostname as its domain.
652052 PEM:sessions iRule made the order of parameters strict Some parameters, for example, subscriber-id come before the parameter user-name. Configuration that was valid in earlier versions is not accepted in newer versions. This may result in the configuration failing to load during an upgrade and return an MCP validation error. "In the versions before 12.0, the order of parameters for ""PEM::SESSIONS"" rule was flexible. It was made strict because of the new validation infrastructure in 12.0. This breaks some existing iRules. The system will report a validation error such as: 01070151:3: Rule [/Common/test_irule] error: /Common/test_irule:2: error: [""invalid argument subscriber-type""][PEM::session create $ip subscriber-type e164 user-name $user imsi $imsi subscriber-id $callingstationid]" Workaround: Change the order of the parameters.
653930 Monitor with description containing backslash may fail to load. Monitor with description containing backslash. Configuration changes without human intervention. Potential load failure. When a monitor description contains a \ (backslash) character, the system adds another backslash for every save-load operation. After enough saves/loads, the description eventually hits the maximum length, causing an error message: '01020057:3: The string with more than 65535 characters cannot be stored in a message' upon loading the config. Workaround: Don't use backslashes in monitor descriptions.
660833 merged repeatedly cores due to unused istats-trigger object The merged process continuously cores. merged restarts. If any of the elements of the istats-trigger configuration are not defined, this issue occurs. For example, all the elements defined in the key of the istats-trigger definition must be defined before the trigger is created. Workaround: None.
667148 Config load or upgrade can fail when loading GTM objects from a non-/Common partition GTM config referencing non-/Common partition objects from /Common. GTM configuration fails to load, which may keep a system from becoming active GTM configuration fails to load. Workaround: No workaround. Fixed issue preventing GTM configurations from loading when non-Common partitioned items present.
673018 Parsed text violates expected format error encountered while upgrading or loading UCS "This can occur under the following conditions: -- When loading a configuration that contains iFiles. -- During an upgrade process, when the source-path for an iFile contain a URL with a space or other invalid URL character in it, for example: http://myfiles.com/get this file.txt." Configuration fails to load, and the system reports the following error: Parsed text violates expected format. "During a configuration roll-forward on an upgrade, the UCS load fails and reports the following error: Parsed text violates expected format." Workaround: "You can use either of the following workarounds: -- Modify the URL to the iFile to remove any spaces, and then reload the configuration. -- Use the HTTP specification for specifying spaces (and other characters) in URLs. For example, represent a space using the string %20 in the URL: http://myfiles.com/get%20this%20file.txt."
673664 TMM crashes when sys db Crypto.HwAcceleration is disabled. This occurs when sys db Crypto.HwAcceleration is disabled. TMM crash. Traffic disrupted while tmm restarts. TMM crashes when sys db Crypto.HwAcceleration is disabled. Workaround: "Enable crypto hardware acceleration using the following command: tmsh modify sys db crypto.hwacceleration value enable"
673832 Performance impact for certain platforms after upgrading to 13.1.0. "The following platforms, with Fast HTTP/OneConnect/Full Proxy configured.

              -- i2800
              -- i4800
              -- i5800
              -- i7800
              -- i10800
              -- i11800
              -- B2250
              -- B4450

The performance impacts occur on the following platforms under the associated conditions:

              -- i2800 2%-3% Full Proxy traffic.
              -- i4800 2%-3% Full Proxy traffic.
              -- i5800 3%-8% FastHTTP/Full Proxy traffic.
              -- i7800 3%-7% Fast HTTP/Full Proxy traffic.
              -- i10800 3%-7% Fast HTTP/Full Proxy traffic.
              -- i11800 2%-3% Fast HTTP traffic.
              -- B2250 3%-6% OneConnect/Full Proxy traffic.
              -- B4450 4%-10% Fast HTTP/OneConnect/Full Proxy traffic.

Performance impact for certain platforms after upgrading to 13.1.0. Workaround: None. Performance impact for certain platforms has been eliminated.
681377 The BIG-IP system sends out SYN/ACK with MSS 0 in VLAN syncookie protection mode on some platforms Hardware syncookie is enabled on a VLAN that is under SYN flood attack and the syncookie protection is triggered. This occurs on the following platforms: BIG-IP series 5000, 7000, and 10000 platforms, and VIPRION B2100, B2150, B2250, and B43x0 blades. Most TCP clients can handle these SYN/ACK packets gracefully, but some clients (such as Ixia traffic-test appliances) may not be able to handle them properly, thus impacting traffic. A firmware issue exists on certain platforms that will result in SYN/ACK packets with an MSS filed with a value of 0, even though TMOS sets it to a different value. Workaround: Turn off hardware VLAN syncookie protection if regular TCP traffic is impacted. In 13.1.0, the per-VLAN-based syncookie protection will be disabled in the data plane BIG-IP series 5000, 7000, and 10000 platforms, and VIPRION B2100, B2150, B2250, and B43x0 blades.
684068 FIX with PVA offload and late binding without flow release may not execute iRules on subsequent messages Configure a virtual server with a fastL4 profile and a FIX profile. Configure the FastL4 profile to have late binding and explicit flow migration. Place iRules on the virtual server that trigger on FIX_MESSAGE or FIX_HEADER. Restart the BIG-IP, connect to the virtual server and begin sending FIX messages. The iRules may not trigger on the second and further messages sent to the FIX virtual server on the first connection after the restart. With a virtual server configured with a fastL4 profile and a FIX profile where the fast L4 profile is configured with late binding and explicit flow migration, the first connection after a setup or restart may not correctly execute FIX iRules if the flow is not handed off to ePVA after the first FIX message. Workaround:
686190 LRO performance impact with BWC and FastL4 virtual server

              -- BWC is configured.
              -- Virtual server has a FastL4 profile assigned.
              -- LRO is enabled (enabled by default in 13.1.0).

Very large performance impact to the BWC policy (up to 75%). For example, if the BWC policy rate limit is set to 100Mb, the actual rate limit could be 25Mb. Using Bandwidth controller (BWC) might result in a very large drop in performance of up to 75%. In this release, Large receive offload (LRO) is enabled by default. Workaround: "Disabling LRO recaptures most of the performance degradation related to using FastL4. To disable LRO (this is a system-wide setting), run the following command: tmsh modify sys db tm.largereceiveoffload value disable Important note: Although you can disable LRO to recapture much of the 13.0.0-level performance, you will likely still experience some impact: 2-5% for small files, 17-22% degradation for the '10 requests per connection' benchmark. The only guaranteed way to avoid performance degradation is to remain on version 13.0.0."
686307 Monitor Escaping is not changed when upgrading from 11.6.x to 12.x and later

              -- Upgrading and rolling forward monitor configuration data.
              -- LTM policy data present.

Monitors may not work after upgrade. "When upgrading, monitor attributes such as receive string and send string might contain escape sequences that must be processed after the upgrade. However, due to a problem introduced by the LTM policy upgrade script, this processing is not performed, resulting in monitors not functioning correctly after the upgrade. Note: Without LTM policies in the configuration, monitors upgrade without problem." Workaround: No workaround at this time. This release addresses the underlying problem so the issue no longer occurs.
696525 B2250 blades experience degraded performance. This occurs when the FastL4 profile is configured to offload to hardware and the service provider DAG is configured and in use on B2250 blades. Performance will be degraded due to more connections being handled in software. B2250 blades have degraded performance by up to 17%. This is caused by connections not being offloaded to hardware as often as expected. Workaround: None. The performance issue for the B2250 blades has been fixed.
698182 Upgrading from 13.1.1 to newer release might cause config to not be copied over Upgrade or loading a UCS from 13.1.1 to newer release. Config cannot be loaded or fails. Upgrading from 13.1.1 to newer release might cause config to not be copied over. This is due to the UUID being available on the older release but not on the newer one. Workaround: Copy config and remove UUID-specific schema before loading the config. When upgrading to a version in which UUID is not supported, the system now automatically copies the config and removes UUID-specific schema before loading it.
699249 The config may not load after upgrade if syslog-ng syntax is not valid "In v13.0.0, the syslog-ng version changed from 2.1.4 to 3.8.1. Syslog-ng include options may contain syntax which is correct in 2.1.4 syslog but is not correct in 3.8.1. TMOS does not parse the 'include' option, or translate it from older versions to newer, or any other modification. It blindly copies it into the configuration file." The config will not load after upgrade if the syntax is not valid in a new syslog-ng version. The config is not loaded after upgrade Workaround: "Manually modify the 'include' option in BIG-IP_base.conf file after upgrade. The config cannot be loaded so tmsh will not work."
701898 Certain virtual address route-advertisement settings break upgrades from 13.0.0 hotfix rollups "- Upgrading from a version of 13.0.0 other than the base (i.e. HF1 or later). - Upgrading to 13.1.0 or later. - At least one virtual address with its route-advertisement value set to ""selective"", ""any"", or ""all""." Configuration will not load. "Upgrading from a version of 13.0.0 other than the base build may result in failure depending on the values of the virtual address route-advertisement setting. If set to ""selective"", ""any"", or ""all"", the configuration will fail with an error similar to this in /var/ltm/log: load_config_files: ""/usr/bin/tmsh -n -g load sys config partitions all "" - failed. -- Loading schema version: 13.0.0 Syntax Error:(/config/bigip.conf at line: 1790) invalid property value ""route-advertisement"":""selective""" Workaround: "Prior to the upgrade: 1. Note any virtual address route-advertisement settings that are ""selective"", ""any"", or ""all"". 2. Change all of these values to either ""enabled"" or ""disabled"" (note that this will change their route advertisement behavior temporarily). 3. Perform the upgrade. 4. Change the route advertisement settings back to their original values."
702792 Upgrade creates Server SSL profiles with invalid cipher strings Custom HTTPS monitors configured prior to an upgrade will result in these profiles being created during the upgrade. The default HTTPS cipherlist is 'DEFAULT:+SHA:+3DES:+kEDH', which is a valid OpenSSL cipher list, but is not a valid Client SSL / Server SSL cipher list. Upgrade creates configurations that are challenging to manage as a result of MCPD validation. "Upgrade of BIG-IP creates Server SSL profiles for custom HTTPS monitors that may have an invalid Ciphers attribute. This will not prevent the configuration from loading, but attempting to modify the existing SSL profile or create a new one with matching configuration will fail: 01070312:3: Invalid keyword 'kedh' in ciphers list for profile /Common/name-of-server-ssl-profile" Workaround: "Reconfigure the cipher list to be valid according to both the OpenSSL cipher list and the Client SSL / Server SSL cipher list expectations. For instance, ""DEFAULT:+SHA:+3DES:+EDH"" instead of ""DEFAULT:+SHA:+3DES:+kEDH""."
705730 Config fails to load due to invalid SSL cipher after upgrade from v13.1.0 "-- Config uses 'https' monitors. -- Upgrade occurs from v13.1.0 to a later version." The configuration fails to load, an error message is issued, and the device remains offline until a manual config load is performed. "Config with apparently invalid SSL cipher entry fails to load after upgrade from v13.1.0, and requires a manual config load after upgrade: 'tmsh load sys config' This occurs because starting in v13.1.0, 'https' monitors rely upon SSL-attributes configured through a 'serverssl' profile, which does not support the 'kEDH' cipher; but the 'kEDH' cipher was a default cipher for previous releases (where 'https' relied upon 'OpenSSL')." Workaround: "You can use either of the following workarounds: -- After upgrade from v13.1.0, perform manual config load by running the following command: tmsh load sys config (This works because upon a manual config load command ('tmsh load sys config'), the system replaces the existing 'https' ciphers with defaults appropriate for a 'serverssl' profile in the new version of the software. Even though the system posts an error referencing the invalid 'kEDH' cipher, the device will become 'Active' seconds later, and new default ciphers will be established for 'https' monitors.) -- Remove 'https' monitors prior to upgrade, and add again after upgrade." Config loads without error after upgrade from v13.1.0.

Issues when upgrading from earlier ASM versions

If you upgrade from an earlier version of ASM, note the following issues.

Upgrade warnings and notes

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.

ASM Logging Profile behavior in 12.1.0 and later

In 12.1.0 ASM logging profiles have changed from a single profile that can support remote and/or local logging to multiple profile support for profiles that are either remote, or local logging. No functionality is lost, however what was previously a single profile now becomes two profiles. This occurs when you upgrade from a pre-12.1.0 release to 12.1.0 or later, and there is an ASM logging profile exists in the configuration. In this case, logging profiles have changed from a single profile that can support remote and/or local logging to multiple profile support for profiles that are either remote OR local logging. No functionality is lost, however what was previously a single profile now becomes two profiles.

Exporting Logs

In version 13.0.0 the ability to export request logs in binary(.csv) and PDF file formats was removed. Log files are exported in HTML format only. The resultant HTML log file can be converted to a PDF by:
  • Printing the HTML page to PDF from the browser window.
  • Scripting the HTML to PDF conversion using CLI found here: https://wkhtmltopdf.org/

Layer 7

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:

  • A Layer 7 local traffic policy is created and the HTTP class is removed. If the HTTP Class name is different than the name of the security policy, upon upgrade, the system changes the name of the security policy to the name of the HTTP Class.
  • Security policies are now in folders (partitioned) like pools and virtual servers. Upon upgrade, the system places security policies in the folder to which the HTTP Class belonged. The system places security policies that were inactive in the /Common folder.
  • iRules that use HTTP Class do not work here. Users must manually change the HTTP Class part of the iRule to Policy after the upgrade.

ASM cookie security

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:

  • Disable the modified domain cookie violation, and re-enable it only after at least 24 hours have passed.
  • If you do not have a wildcard cookie, before the upgrade add an ASM allowed cookie to the security policy, with the name TS*.
  • Have all clients restart their browsers.

After upgrading, users must synchronize their Cookie Protection settings in the following cases:

  • Systems that share traffic but are NOT in the same device group
  • Systems from different versions that share traffic, even if they are in the same device group

Cookie signature validation

After upgrading, the system performs the following:

  • Turns on staging for all Allowed cookies
  • Applies signature checks on existing Allowed cookies
  • Adds a * wildcard Allowed cookie even if the user did not have on previously Upgrading to version 11.3.0 or later

Web scraping

There was a check box for enabling web scraping that was removed in version 11.3.0.

  • When you upgrade from versions 11.0.0 through 11.2.x, if the check box is enabled, the new Bot Detection setting has the option Alarm and Block enabled. If the check box is not enabled, the value is Off.
  • When you upgrade from versions prior to 11.0.0 (where there was no enable flag), the Bot Detection setting is based on the blocking check boxes for web scraping:
    • If the global Block check box is enabled, the value is Alarm and Block.
    • If the global Block check box is disabled, and the global Alarm check box is enabled, the value is Alarm.
    • If both Alarm and Block check boxes are disabled, the value is Off.

Brute Force

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:

  • Source-based mitigation will be set to Alarm and CAPTCHA for Username, Device IP and Source ID.
  • Dynamic mitigation will be set to Alarm and CAPTCHA.
  • Client Side Integrity Bypass Mitigation will be set to Alarm and CAPTCHA.
  • CAPTCHA Bypass Mitigation will be set to Alarm and CAPTCHA.
  • Detection and prevention duration will be derived from previous values.
  • Enforcement of both the source-based and distributed brute force protections depends on the Blocking settings of the Brute Force: Maximum login attempts are exceeded violation.
  • The Learning flag for Brute Force: Maximum login attempts are exceeded violation is discontinued.
  • The Unlimited value for Prevention Duration is discontinued.

DoS profiles

In versions 11.3.0 and later, DoS profiles are assigned to virtual servers. Previously, they were assigned to security policies.

  • Upon upgrading DoS Profiles from versions prior to 11.3.0, all active security policies have their DoS 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.
  • If you have a disabled DoS profile in a version prior to 11.3.0, and upgrade, after the upgrade the system automatically assigns the DoS profile to a virtual server. As a result, even though the system does not perform DoS protection, it still collects statistics, which impacts the system’s performance. To work around this issue, if you have a disabled DoS profile assigned to a virtual server, to improve system performance you should remove its association from the virtual server. (ID 405211)
  • We do not support exporting and importing DoS profiles.

Logging Profiles

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.

XFF configuration (ID 405312)

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 Local Traffic > Profiles > Services > HTTP > Properties screen, and enable the Accept XFF setting.

IP address whitelist

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).

Security policy status after UCS installation

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.

Running Application Security Manager on a vCMP system

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.

About changing the resource provisioning level of the Application Security Manager

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.

Important: Wait 5 minutes after you set the resource provisioning level before making any configuration changes to the Application Security Manager. The system overrides all configuration changes that were made before this process is completed. When the process is not complete, the system informs you by displaying, in the Configuration utility, the following message: ASM is not ready. The system informs you when the process is completed by indicating in the log (/var/log/asm) the following message: ASM started successfully.

Setting the Application Security Manager resource provisioning level to Nominal from the command line

You can set the Application Security Manager resource provisioning level to Nominal from the command line.
  1. Open the command-line interface utility.
  2. Type the command: tmsh modify sys provision asm level nominal
  3. Type the command: tmsh save sys config.
The screen refreshes, and the resource provisioning level of the Application Security Manager is set to Nominal.

Setting the Application Security Manager resource provisioning level to Nominal using the Configuration utility

You can set the Application Security Manager resource provisioning level to Nominal using the Configuration utility.
  1. On the Main tab, click System > Resource Provisioning . The Resource Provisioning screen opens.
  2. Set the Application Security (ASM) option to Nominal.
  3. Click Submit.
The screen refreshes, and the resource provisioning level of the Application Security Manager is set to Nominal.

To prevent traffic from bypassing the Application Security Manager

Please read 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 on the AskF5 web site. These articles contain important configuration information needed to prevent traffic from bypassing the Application Security Manager.

FPS 15.x Upgrade and Compatibility Information

FPS 15.0.0 Upgrade and Compatibility Information

  • When upgrading to BIG-IP 15.0.0 from any previous BIG-IP version, any words that were blacklisted for means of malware detection either in the web application’s HTML code or JavaScript code are converted to the new DOM Signatures format. Words that were blacklisted for means of malware detection in the HTML code will have the following settings:
    • Search In = HTML
    • Match Type = Contains
    • Search For = <the blacklisted word>

      Words that were blacklisted for means of malware detection in the JavaScript code will have the following settings:

    • Search In = JavaScript Global Variable
    • Match Type = Is
    • Search For = <the blacklisted word>
  • When upgrading to BIG-IP 15.0.0 from BIG-IP versions 14.0 and earlier, HTTP request methods GET and POST on URL parameters are deprecated. Instead, the Search In field for parameters that used these methods is set as follows:
    • For parameters that had the GET method, Search In is set to Query String.
    • For parameters that had the POST method, Search In is set to Payload.
  • When upgrading to FPS 15.0.0 from BIG-IP versions 13.0.0 and earlier, you should be aware of the following:
    1. The standard FPS Data Manipulation Check is disabled for URL parameters that are marked with both the attributes Substitute Value and Check Data Manipulation.
    2. The Route to Pool user-defined FPS rule has been deprecated and replaced with the Redirect to URL FPS rule, using the URL /changeme.
    3. Real Time Encryption is disabled on URLs using a custom encryption function.
    4. The settings for the location of the FPS Main JavaScript have moved from the profile level to the URL level. For profiles with more than one URL, these settings are applied on all URLs in the profile.
      Note: If upgrading from BIG-IP 12.1.2-hf1-BIG-IP 13.0 (but not including 13.0.0) and you enabled the antifraud.internalconfig.flag1 database variable to allow using multiple FPS JavaScript location settings for multiple URLs in a profile, when upgrading to BIG-IP 15.0 the first location settings in the list will applied to all URLs in the profile.
    5. The following Phishing Detection settings have moved from the profile level to the URL level:
      • Location of CSS Link Injection (previously called Inject CSS Link)
      • Location of Phishing Inline JavaScript and Image Injection (previously called Inject Phishing Inline JavaScript and Image)
      • Location of CSS Element Injection (previously called Inject CSS Element)

      For profiles with more than one URL, these settings are applied on all URLs in the profile.

    6. In FPS 15.0, a valid Fingerprint URL Location (called Fingerprint JavaScript Location in BIG 13.0.0 and earlier versions) is non-empty, starts with ‘/’, and ends with .html. When upgrading to FPS 15.0, any Fingerprint URL Location that differs from this syntax is changed to /changeme.html.
  • When upgrading to FPS 15.0 from BIG-IP 12.0.0 or 12.1.0, you should delete the mobile security alerts URL (typically /rstats) and the alert routing iRule on all mobile security profiles.
  • When upgrading to FPS 15.0 from BIG-IP 12.0.0 or 12.1.0, a user-defined malware type is automatically created by the system that contains the malware detection configuration from the previous BIG-IP version. The name of this malware type is general.

BIG-IQ Compatibility

FPS 15.0.0 is compatible with BIG-IQ 7.0 and later versions.

MobileSafe Compatibility

For Mobile Security users, BIG-IP 15.0 can be used with all versions of the MobileSafe SDK currently supported by the F5 support policy.

About working with device groups

Note: This section is relevant only if you are working with device groups.

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:

  • First provisioning of ASM on a device.
  • Adding a device to a trust-domain that has another device which already has the datasync-global-dg device-group.
  • Upgrading to this version when ASM is already provisioned.
  • Upgrading to this version when the device is joined in a trust-domain that has another device which already has the datasync-global-dg device-group.

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:

  • The synchronization is performed across the entire trust-domain, regardless of the configured device groups.
  • The datasync-global-dg device group must not be removed; it is essential for consistency of client-side scripts and keys across the devices.
  • This device group is created upon provisioning, even if the BIG-IP system is working as a standalone.
  • All of the devices in the trust-domain are automatically added to this device group.
  • This device group is manually synchronized. Therefore, when working with device groups (multiple devices in a trust-domain), customers must choose which device will hold the master scripts and keys. The rest of the devices receive these scripts and keys from the chosen device.
  • This device group is also created on units that do not have ASM provisioned, but are in a trust-domain with other units which do have ASM provisioned.

Synchronizing the device group

When adding a device to the trust-domain, or when upgrading from a previous release, you must manually synchronize this device group.
  1. In the Configuration utility, navigate to Device Management > Overview .
  2. In the Device Groups area, click datasync-global-dg.
  3. In the Devices area, click the device which is chosen to have the master scripts and keys. These scripts and keys will be sent to the rest of the devices.
  4. Under Sync Options, select Sync Device to Group.
  5. Check Overwrite Configuration.
  6. Click Sync.
  7. When the warning message appears, click OK.
The device that you selected continues to work seamlessly. The rest of the devices go OFFLINE, and will not receive traffic for approximately 3 minutes. During this time, the new client-side scripts and keys are synchronized and prepared. After about 3 minutes, all units should return to the ONLINE (Active) state, and the units should be in sync.

Supported ICAP servers

For this version, 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: Security > Options > Application Security > Advanced Configuration > System Variables .)

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 7.0.2.4 X-Violations-Found
Kaspersky Anti-Virus 5.5 X-Virus-ID

AVR :: Merged metrics to HTTP statistics tables

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.

The following table lists the metrics, the tables they were merged into, 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 in the merged metric field in the additional HTTP tables.
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

AVR :: New and updated dimensions

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 Security > Reporting > DoS Aggregated 12.X or lower
Bot Defense Reasons HTTP Security > Reporting > DoS Aggregated 12.X or lower
Browser Names HTTP Statistics > Analytics > HTTP Aggregated 12.X or lower
OS Names HTTP Security > Reporting > DoS Statistics > Analytics > HTTP Aggregated 12.X or lower
Vectors Common Security > Reporting > DoS Aggregated 12.X or lower
Triggers Common Security > Reporting > DoS Aggregated 12.X or lower
Mitigations Common Security > Reporting > DoS Aggregated 12.X or lower
Activity Types Common Security > Reporting > DoS Regular Activity 12.X or lower
Destination Countries Network Security > Reporting > DoS Aggregated 13.X or lower
Destination IP Address Network Security > Reporting > DoS Aggregated 13.X or lower
Client Types HTTP Security > Reporting > DoS Aggregated 13.X or lower
Human Behavior Indications HTTP Security > Reporting > DoS Aggregated 13.X or lower
Application Versions HTTP Security > Reporting > DoS Aggregated 13.X or lower
Application Display Names HTTP Security > Reporting > DoS Aggregated 13.X or lower
Jail Break HTTP Security > Reporting > DoS Aggregated 13.X or lower
Emulation Modes HTTP Security > Reporting > DoS Aggregated 13.X or lower

AVR :: New and updated metrics

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

AVR :: Updated HTTP statistic tables

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.

Dimension Title Initial Value After Upgrade Version before Upgrade
DoS Profiles Aggregated 12.X or lower
Bot Signatures Aggregated 12.X or lower
Bot Signature categories Aggregated 12.X or lower
Countries N/A 12.X or lower

Contacting F5

North America 1-888-882-7535 or (206) 272-6500
Outside North America, Universal Toll-Free +800 11 ASK 4 F5 or (800 11275 435)
Additional phone numbers Regional Offices
Web http://www.f5.com
Email support@f5.com

How to Contact F5 Support or the Anti-Fraud SOC

You can contact a Network Support Center as follows:

You can manage service requests and other web-based support online at F5 My Support (registration required). To register email CSP@F5.com with your F5 hardware serial numbers and contact information.

You can contact the Anti-Fraud SOC as follows:

Additional resources

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

F5 Support

https://f5.com/support :: Self-solve Options

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 Knowledge Base

https://support.f5.com/csp/home

The 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.

BIG-IP iHealth Diagnostics and BIG-IP iHealth Viewer

https://f5.com/support/tools/ihealth

BIG-IP iHealth Diagnostics identifies issues, including common configuration problems and known software issues. It also provides solutions and links to more information. With BIG-IP iHealth Viewer, you can see the status of your system at-a-glance, drill down for details, and view your network configuration.

F5 DevCentral

https://devcentral.f5.com/

Collaborate and share innovations including code samples, new techniques, and other tips, with more than 300,000 F5 users worldwide. DevCentral is the place to ask questions, find solutions, learn to harness the power of F5’s powerful scripting language, iRules, and much more.

Communications Preference Center

https://interact.f5.com/F5-Preference-Center.html

Here, you can subscribe to a number of communications from F5. For information about the types of notifications F5 provides, see K9970: Subscribing to email notifications regarding F5 products.