Applies To:
Show VersionsBIG-IP AAM
- 15.1.1
BIG-IP APM
- 15.1.1
BIG-IP Analytics
- 15.1.1
BIG-IP Link Controller
- 15.1.1
BIG-IP LTM
- 15.1.1
BIG-IP AFM
- 15.1.1
BIG-IP PEM
- 15.1.1
BIG-IP FPS
- 15.1.1
BIG-IP DNS
- 15.1.1
BIG-IP ASM
- 15.1.1
Updated Date: 05/28/2022
Summary:
These release notes document the BIG-IP version 15.1.1.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.
Contents:
- Platform support
- Module combination and memory considerations
- User documentation for this release
- Configuration utility browser support
- Compatibility of BIG-IQ products with BIG-IP releases
- Release fixes, behavior changes, and known issues
- New in 15.1.1 :: All modules
- Installation overview
- Installation checklist
- Installing the software
- Post-installation tasks
- Installation tips and important notes
- Upgrading from earlier versions
- Issues when upgrading from earlier ASM versions
- About changing the resource provisioning level of the Application Security Manager
- To prevent traffic from bypassing the Application Security Manager
- FPS 13.1.1 upgrade and compatibility information
- About working with device groups
- Synchronizing the device group
- Supported ICAP servers
- AVR :: Merged metrics to HTTP statistics tables
- AVR :: New and updated dimensions
- AVR :: New and updated metrics
- AVR :: Updated HTTP statistic tables
- Contacting F5
- Legal notices
Platform support
- K9412: The BIG-IP release matrix: A software-hardware support matrix organized by BIG-IP release version.
- K9476: The F5 hardware/software compatibility matrix: A platform-sorted matrix of BIG-IP hardware/software support.
- K4309: F5 platform lifecycle support policy: A definition of platform lifecycle stages from initial release through retirement.
- BIG-IP VE Supported Hypervisors: A list of VE hypervisors and their supported software versions.
Module combination and memory considerations
BIG-IP platform considerations
These platforms support various licensable combinations of product modules.
Most of the support guidelines relate to memory. The following list applies for all memory levels:
- vCMP supported platforms
- VIPRION 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 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 is not supported on vCMP guests.
- PEM is not supported on 8 GB platforms.
- BIG-IP i850 platform support
- The BIG-IP i850 platform supports Local Traffic Manager (LTM) only, and no other modules.
Memory: 12 GB or more
All licensable module-combinations may be run on platforms with 12 GB or more of memory, and on VE and vCMP guests provisioned with 12 GB or more of memory. 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 and 2200s 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) and Application Visibility and Reporting (AVR) 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.) Beginning in v14.x, 8 GB of memory is the very bare minimum to get three modules provisioned, suitable for a lab environment or very light production traffic, especially with a memory-intensive module such as AVR.
- No more than three modules (not including AAM or AVR) 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.
- BIG-IP LTM standalone only
- BIG-IP GTM standalone only
- BIG-IP LTM and GTM combination only
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 (Edge recommended)
- Mozilla Firefox v80.0.1, or later
- Google Chrome v86.0.4240, or later
- Microsoft Edge v44.19041, 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.
Release fixes, behavior changes, and known issues
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
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.
- Ensure the system rebooted to the new installation location.
- Use BIG-IP iHealth to verify your configuration file. For more information, see K12878: Generating diagnostic data using the qkview utility.
- Log on to the browser-based Configuration utility.
- Run the Setup utility.
- Provision the modules.
Installation tips and important notes
- 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.
Notes
The upgrade process does not update Tcl scripts (such as iRules) in the configuration. 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.
Upgrading from earlier versions
Upgrading from version 13.x or later
When you upgrade from version 13.x or later, you use the Software Management screens in the Configuration utility to complete these steps. To open the Software Management screens, in the navigation pane of the Configuration utility, expand System, and click Software Management. For information about using the Software Management screens, see the online help.
Upgrading from versions earlier than 13.x
You cannot roll forward a configuration directly to this version from BIG-IP version 12.x or earlier. You must be running version 13.x (or later) software. For details about upgrading from earlier versions, see the release notes for the associated release.
Automatic firmware upgrades
If this version includes new firmware for your specific hardware platform, after you install and activate this version, the system might reboot additional times to perform all necessary firmware upgrades.
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.
Exporting Logs
- 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 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.
Setting the Application Security Manager resource provisioning level to Nominal from the command line
- Open the command-line interface utility.
- Type the command: tmsh modify sys provision asm level nominal
- Type the command: tmsh save sys config.
Setting the Application Security Manager resource provisioning level to Nominal using the Configuration utility
To prevent traffic from bypassing the Application Security Manager
For important information needed to prevent traffic from bypassing the Application Security Manager, please see the AskF5 Knowledge Center articles K8018: Overview of the BIG-IP HTTP class traffic flow and K12268: Successive HTTP requests that do not match HTTP class may bypass the BIG-IP ASM.
FPS 13.1.1 upgrade and compatibility information
Upgrading to Fraud Protection Service (FPS) 13.1.1
- When upgrading to FPS 13.1.1 from any BIG-IP version (13.0.0 and earlier) you should be aware of the following:
- The standard FPS Data Manipulation Check is disabled for URL parameters that are marked with both the attributes Substitute Value and Check Data Manipulation.
- The Route to Pool user-defined FPS rule has been deprecated and replaced with the Redirect to URL FPS rule, using the URL /changeme.
- Real Time Encryption is disabled on URLs using a custom encryption function.
- 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 to BIG-IP 13.0.x (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 13.1.1, the first location settings in the list will apply to all URLs in the profile.
- 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)
- In FPS 13.1.1, a valid Fingerprint URL Location (called Fingerprint JavaScript Location in BIG-IP 13.0.0 and earlier versions) is non-empty, starts with ‘/’, and ends with .html. When upgrading to FPS 13.1.1, any Fingerprint URL Location that differs from this syntax is changed to /changeme.html.
- When upgrading to FPS 13.1.1 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 13.1.1 from BIG-IP 11.6.x, 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.
WebSafe Dashboard Compatibility
FPS 13.1.1 can be used with WebSafe Dashboard version 4.1 and later versions. Earlier versions of the WebSafe Dashboard are not compatible with FPS 13.1.1.MobileSafe Compatibility
For Mobile Security users, FPS 13.1.1 should be used with MobileSafe SDK 2.0 or a later version, as all MobileSafe SDK versions prior to 2.0 are end-of-life.About 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 that has version 11.6.0, or later, installed.
- Adding a device (with version 11.6.0 or later) to a trust-domain that has another device which already has the datasync-global-dg device-group.
- Upgrading to version 11.6.0, or later, when ASM is already provisioned.
- Upgrading to version 11.6.0, or later, 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
Supported ICAP servers
For BIG-IP version 11.6.0, F5 Networks tested the anti-virus feature on the following ICAP servers: McAfee®, Trend Micro™, Symantec™, and Kaspersky. The following table displays which version of each anti-virus vendor was tested, and the value of the virus_header_name variable that needs to be adjusted in ASM for each tool. (You can set the virus_header_name variable: .)
Anti-Virus Vendor | Anti-Virus Version | Value of virus_header_name |
---|---|---|
McAfee® VirusScan Enterprise | 7.0 | X-Infection-Found, X-Virus-Name |
Trend Micro™ InterScan™ Web Security | 5.0.1013 | X-Virus-ID |
Symantec™ Protection Engine | 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.
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 | Aggregated | 12.X or lower | |
Bot Defense Reasons | HTTP | Aggregated | 12.X or lower | |
Browser Names | HTTP | Aggregated | 12.X or lower | |
OS Names | HTTP | Aggregated | 12.X or lower | |
Vectors | Common | Aggregated | 12.X or lower | |
Triggers | Common | Aggregated | 12.X or lower | |
Mitigations | Common | Aggregated | 12.X or lower | |
Activity Types | Common | Regular Activity | 12.X or lower | |
Destination Countries | Network | Aggregated | 13.X or lower | |
Destination IP Address | Network | Aggregated | 13.X or lower | |
Client Types | HTTP | Aggregated | 13.X or lower | |
Human Behavior Indications | HTTP | Aggregated | 13.X or lower | |
Application Versions | HTTP | Aggregated | 13.X or lower | |
Application Display Names | HTTP | Aggregated | 13.X or lower | |
Jail Break | HTTP | Aggregated | 13.X or lower | |
Emulation Modes | HTTP | Aggregated | 13.X or lower |
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.
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 |
support@f5.com |
Additional resources
You can find additional support resources and technical documentation through a variety of sources.
F5 Support | Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology. |
AskF5 Knowledge Base | 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 | 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 | 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 | 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. |