(SOL7314) If the rate of HTTP compressed data exceeds the licensed limits, the data exceeding the Mbps rate is processed with NULL compression, and the following alert is issued to the /var/log/ltm file:
Compression license limit of %d Mbit/s exceeded today.
If an SNMP trap is configured, the following trap OID is also sent:
SNMP trap: .1.3.6.1.4.1.3375.2.4.0.35
Note: To reduce excess logging and notification, an alert is issued the first time HTTP compressed data exceeds the licensed limits and subsequen
↧
Informational: Alert actions are triggered when the rate of HTTP compressed data exceeds the licensed limits
↧
Known Issue: Server certificate validation may fail with BIG-IP Edge Client command line for Linux
(SOL14936) Description
Server certificate verification may fail with the BIG-IP Edge Client command line for Linux.
This issue occurs when all of the following conditions are met:
You are using the Linux version of the BIG-IP Edge Client to connect to the BIG-IP APM system.
The SSL certificate in use has more than 10 entries in the Subject Alternative Name field.
The BIG-IP Edge Client command line for Linux attempts to verify the server's SSL certificate when establishing a VPN connection. The certific
↧
↧
Known Issue: Newly-created AAA Server may use the wrong pool after an mcpd restart
(SOL14949) Description
A newly-created AAA Server may use the wrong pool after an mcpd restart.
This issue occurs when all of the following conditions are met:
You have configured the BIG-IP APM system with several AAA Servers.
You have configured the AAA Servers with pools.
After you have restarted mcpd or the BIG-IP APM system, you created or edited an AAA Server that is configured with a pool.
This issue occurs when the BIG-IP system has multiple AAA Servers, each configured to use a pool of servers.
↧
Manual: Platform Guide: BIG-IQ 7000 Series
↧
How-To: Configuring the DNS cache TTL statement for the BIG-IP GTM system
(SOL14922) Purpose
You should consider using this procedure under the following condition:
You want to change the DNS cache TTL statement for the BIG-IP GTM system.
Prerequisites
You must meet the following prerequisite to use this procedure:
You must have access to the Configuration utility.
Description
When you configure the BIG-IP GTM system to perform recursive DNS queries, the system stores responses to the recursive queries in memory so that it can respond more quickly to new queries for the sa
↧
↧
Error Message: Error Message: httpd<pid>: [error] <client_ip> AUTHCACHE Error processing cookie <hash> - Cookie impersonation detected from remote IP
(SOL13048)
Error Message
httpd<pid>: [error] <client_ip> AUTHCACHE Error processing cookie <cookie_string> - Cookie impersonation detected from remote IP
In this error message, note the following:
<pid>is the httpd process ID
<client_ip>is the remote client IP address
<cookie_string>is the 40-byteBIGIPAuthCookie cookie value
For example:
httpd[32157]: [error] [client 172.16.65.11] AUTHCACHE Error processing cookie 37463B53B8C5A55F85DE7A0EB7FEC00AA48C3EC5 - Cookie impe
↧
Informational: iApp: Microsoft Exchange Server 2010 and Exchange Server 2013 Client Access servers
(SOL13497) Description
You can use this F5 supported iApp template to configure availability, optimizations, encryption, and remote access for the Client Access server role in the following Exchange Server versions:
Cumulative Update 3 (CU3) for Microsoft Exchange Server 2013
Cumulative Update 2 (CU2) for Microsoft Exchange Server 2013
Exchange Server 2013 CU1
Exchange Server 2013
Exchange Server 2010 Service Pack 2 (SP2)
Exchange Server 2010 SP1
Exchange Server 2010
This iApp template configures BIG-IP
↧
Manual: BIG-IP DNS Services: Implementations
↧
Known Issue: The BIG-IP APM rewrite process may produce a core file when processing HTTP response headers
(SOL14944) Description
The BIG-IP APM rewrite process may exit and produce a core file when processing certain HTTP responses.
This issue occurs when all of the following conditions are met:
The BIG-IP APM system is configured for portal access.
The HTTP Reason-Phrase in the server response contains 28 characters.
The Status-Line in an HTTP response contains the HTTP-Version, Status-Code, and Reason-Phrase. If the Reason-Phrase for a given response is 28 characters long, meaning the Status-Code and Rea
↧
↧
Manual: BIG-IP DNS Services: Implementations
↧
How-To: Determining the Always-On Management version
(SOL9478) The Always-On Management (AOM) is a separate subsystem that provides lights-out management for certain BIG-IP platforms.
Determining the AOM version (2000, 4000, 5000, 7000, 10000 series platforms)
Impact of procedure: Performing the following procedure should not have a negative impact on your system.
Log in to the BIG-IP command line.
Use SSH to access the AOM command menu by typing the following command:ssh aom
Display the AOM command menu by typing the following key sequence:Esc (
Pre
↧
Known Issue: Configuring an IP address for a BIG-IP object using an IP address in the IPv4 Link-Local address range results in an error message
(SOL14960) Description
You get an error message when you configure an IP address for a BIG-IP object using an IP address in the IPv4 Link-Local address range.
This issue occurs when the following condition is met:
You attempt to configure an IP address for a BIG-IP object in the IPv4 Link-Local address range.
Impact
You are unable to configure the IP address in the range of 169.254.0.0/16.
Symptoms
As a result of this issue, you may encounter the following symptom:
When you attempt to configure the fail
↧
Overview: Overview of the Always-On Management (AOM) subsystem
(SOL9403) Summary
Always-On Management (AOM) is a separate subsystem that provides lights-out management for the BIG-IP system by using the 10/100/1000 Ethernet management port over secure shell (SSH), or by using the serial console.
Description
AOM allows you to manage BIG-IP platforms using SSH (most platforms) or the serial console, even if the Host subsystem is turned off. The BIG-IP Host subsystem and the AOM subsystem operate independently. If AOM is reset or fails, the BIG-IP Host subsystem contin
↧
↧
How-To: Configuring AOM network access (800, 1600, 3600, 3900, 6900, 89XX, 11000, and 11050 series platforms)
(SOL9608) This article applies to the BIG-IP 800, 1600, 3600, 3900, 6900, 89XX, 11000, and 11050 series platforms. For information about other versions, refer to the following article:
SOL14595: Configuring AOM network access (2000, 4000, 5000, 7000, and 10000 series platforms)
The Always-On Management (AOM) is a separate subsystem that provides lights-out management for the BIG-IP system. You can configure the AOM so that it can be accessed over the network by performing one of the following two method
↧
Overview: The BIG-IP Edge Client components for Mac OS X
(SOL14947) This article applies to the BIG-IP Edge Client for Mac OS. For information about other versions, refer to the following articles:
SOL14045: The BIG-IP Edge Client components for Windows
SOL10407: The FirePass client components
Summary
BIG-IP Edge Client for Mac OS X comprises individual components that provide logon integration, endpoint protection, client inspection, and network and application access.
Description
BIG-IP Edge Client for Mac OS X comprises several services that the client prov
↧
Overview: The BIG-IP Edge Client components for Windows
(SOL14045) This article applies to the BIG-IP Edge Client for Windows. For information about other versions, refer to the following article:
SOL14947: The BIG-IP Edge Client components for Mac OS X
SOL10407: The FirePass client components
Summary
BIG-IP Edge Client for Windows comprises individual components that provide Windows logon integration, endpoint protection, client inspection, and network and application access.
Description
BIG-IP Edge Client for Windows comprises several services that the cli
↧
Overview: Overview of BIG-IP SYN cookie protection (11.4.x)
(SOL14779) This article applies to BIG-IP 11.4.x and later versions. For information about other versions, refer to the following article:
SOL7847: Overview of BIG-IP SYN cookie protection (9.x - 11.3.x)
Summary
The SYN cookie feature prevents the BIG-IP SYN queue from becoming full during a SYN flood attack. Certain BIG-IP platforms can perform hardware/software SYN cookie protection, while other platforms perform software-only SYN cookie protection.
Description
The BIG-IP SYN cookie feature protects
↧
↧
Known Issue: The MBLB profile causes an extra five second TCP closure time
(SOL14941) Description
A TCP virtual server configured with a Message Based Load Balancing (MBLB) profile may fail to close connections in the expected time frame, as configured in the TCP profile.
This issue occurs when the following condition is met:
The MBLB profile is associated with the virtual server.
The TCP profile allows the user to modify the timeout settings for the Time Wait, FIN Wait, and Close Wait TCP states. For example, the default FIN Wait timeout for the TCP profile is five seconds. Ho
↧
How-To: Resetting BIG-IP AVR statistics
(SOL14956) Purpose
You should consider using this procedure under the following conditions:
You want to reset the AVR statistics and graphs.
You want to recover from a possible database issue in which AVR stops gathering statistics.
Prerequisites
You must meet the following prerequisite to use this procedure:
You must have access to the BIG-IP command line.
Description
The BIG-IP Analytics module gathers performance information and provides detailed metrics, such as transactions per second, request an
↧
Known Issue: The mcpd process may fail to synchronize a configuration when another configuration synchronization is in progress
(SOL14966) Description
The mcpd process may fail to synchronize configuration for a device group. This issue occurs when all of the following conditions are met:
The affected device group is configured with multiple devices.
The affected device group has another configuration synchronization in progress.
Impact
The configuration is not synchronized between devices in the same device group.
Symptoms
As a result of this issue, you may encounter the following symptoms:
The configuration synchronization fai
↧