(SOL50522620) Known IssueThe BIG-IP APM rewrite profile may incorrectly handle the EventTarget.addEventListener() method.This issue occurs when all of the following conditions are met:The BIG-IP APM system is configured for portal access.The JavaScript code in the web application invokes the EventTarget.addEventListener() method.ImpactWeb applications may malfunction or fail to render properly.SymptomsAs a result of this issue, you may encounter one or more of the following symptoms: Web page content that inv
↧
Known Issue: The BIG-IP APM rewrite profile may incorrectly handle the EventTarget.addEventListener() method
↧
Security Advisory: Linux kernel vulnerabilities CVE-2015-2925, CVE-2015-5307, and CVE-2015-8104
(SOL31026324)
↧
↧
Known Issue: The VIPRION system may incorrectly display the serial number of the blade after removal
(SOL90384094) Known IssueThe VIPRION system may incorrectly display the serial number of the blade after you remove the blade.This issue occurs when the following condition is met:You remove a blade from the VIPRION system without rebooting the system.On a VIPRION system, you may use the BIG-IP Configuration utility to display the serial number of the blades in the chassis by navigating to System > Clusters > Properties. If you move a blade to another slot on the same chassis, the BIG-IP system may not
↧
Security Advisory: Linux kernel vulnerability CVE-2015-7872
(SOL94105604)
↧
Release Note: BIG-IP LTM and TMOS 11.6.0
This release note documents the version 11.6.0 release of BIG-IP Local Traffic Manager and TMOS. You can apply the software upgrade to systems running software versions 10.1.0 (or later) or 11.x.
↧
↧
Security Advisory: OpenSSL vulnerability CVE-2015-0286
(SOL16317)
↧
How-To: BIG-IP DNS and Link Controller require a unique VLAN and IP subnet for each configured link (11.x - 12.x)
(SOL13761) TopicThis article applies to BIG-IP DNS and Link Controller 11.x and 12.x. For information about other versions, refer to the following article:SOL12175: The BIG-IP Link Controller requires a unique VLAN and IP subnet for each configured link (9.x - 10.x)PurposeYou should consider using this procedure under the following condition:You want BIG-IP DNS, or Link Controller to monitor multiple ISP links that reside on the same Virtual Local Area Network (VLAN) and IP subnet.PrerequisitesYou must mee
↧
Known Issue: The TMM process may restart and produce a core file when processing a firewall rule
(SOL21527029) Known IssueThe Traffic Management Microkernel (TMM) process may restart and produce a core file when processing a firewall rule.This issue occurs when all of the following conditions are met:You configure a network firewall rule whose action is an iRule.The iRule includes a FLOW_INIT event.You assign the network firewall rule to a self IP.The self IP processes traffic that triggers a FLOW_INIT event.ImpactThe BIG-IP system may temporarily fail to process traffic, as it recovers from TMM restart.
↧
Known Issue: Options List setting on the Client SSL profile may fail to reset
(SOL47576922) Known IssueThe Options List setting on the Client SSL profile may fail to reset.This issue occurs when all of the following conditions are met:You have modified the Options List setting on a customized Client SSL profile.After the system committed the changes, you used the Traffic Management Shell (tmsh) to reset the Options List back to its inherited default value.When you create a customized Client SSL profile, the Options List setting will inherit the values from the Parent Profile by default
↧
↧
Known Issue: BIG-IP APM portal access sessions may intermittently fail
(SOL25117932) Known IssueBIG-IP APM portal access sessions may intermittently fail.This issue occurs when all of the following conditions are met:Your BIG-IP APM system is configured with an access portal.Portal access session users are using the Safari browser on an iOS 6 or iOS 7 device.ImpactPortal access sessions fail sporadically or web applications malfunction.SymptomsAs a result of this issue, you may encounter one or more of the following symptoms:When attempting to access content through a BIG-IP APM
↧
Security Advisory: Linux kernel vulnerability CVE-2015-3636
(SOL17246)
↧
Security Advisory: Linux kernel vulnerability CVE-2015-2830
(SOL17462)
↧
Security Advisory: SNMP vulnerability CVE-2015-5621
(SOL17378)
↧
↧
Known Issue: SIP monitor marks members down when the monitor and pool members use white space differently from one another in the SIP headers
(SOL17196) Known IssueSIP monitor marks members down when the monitor and pool members use white space differently from one another in the SIP headers.This issue occurs when a subset of the following conditions are met:The BIG-IP system sends and receives the following SIP headers: BIG-IP sends: Call-ID:222abcde@example.f5.com.BIG-IP receives: Call-ID: 123454321@example.f5.com. The BIG-IP sends and receives the following headers: BIG-IP sends: Call-ID: 222abcde@example.f5.com.BIG-IP receives: Call-ID:
↧
Known Issue: Generating a BIG-IP qkview snapshot may fail
(SOL38385852) Known IssueGenerating a BIG-IP qkview snapshot may fail.This issue occurs when the following conditions are met:A filestore mapping has become corrupt. For example, there are files listed in the filestore that are missing from the filesystem.ImpactYou are unable to generate a qkview snapshot.SymptomsAs a result of this issue, you may encounter one or more of the following symptoms:The qkview processing does not complete.In the /var/log/ltm file, you may observe an error message similar to the fo
↧
Known Issue: The TCP profile may allow a non-SYN packet to create a new connection flow after sending a TCP RST (reset) to the client
(SOL36717289) Known IssueA TCP profile may allow a non-SYN packet to create a new connection flow after sending a TCP RST (reset) to the client.This issue occurs when all of the following conditions are met:You are using one of the following platforms that have hardware SYN cookie protection enabled by default: BIG-IP appliances: BIG-IP 5000 series, 7000 series, 10000 series, and 12000 seriesBIG-IP VIPRION blades: B2000 series, and B4300 You have configured your virtual server to use a TCP profile.Impact
↧
Known Issue: The BIG-IP system may intermittently fail to authenticate users with valid credentials
(SOL15285) Known IssueOn rare occasions, the BIG-IP system may intermittently fail to authenticate users with valid credentials.This issue occurs when the following condition is met:The BIG-IP system processes a high volume of invalid credential authentication requests.ImpactUsers with valid credentials experience intermittent authentication failures.SymptomsAs a result of this issue, you may encounter one or more of the following symptoms:In the /var/log/secure log file, you notice an error message simila
↧
↧
Known Issue: BIG-IP APM ActiveSync connection requests may fail
(SOL17286) Known IssueBIG-IP APM ActiveSync connection requests may fail.This issue occurs when all of the following conditions are met:Your BIG-IP APM system is configured with an access profile for Microsoft Exchange ActiveSync. You modify the BIG-IP system tmm.access.maxrequestbodysize database variable to a value larger than the default 64 KB value.An ActiveSync access session connection attempts to send an email message that is larger than 64 KB.ImpactThe BIG-IP APM system does not successfully proces
↧
Known Issue: TMM may restart when a OneConnect profile is applied to a virtual server and OneConnect reuse is disabled on the server side by an iRule
(SOL16456) Known IssueThe Traffic Management Microkernel (TMM) may restart when a OneConnect profile is applied to a virtual server and OneConnect reuse is disabled on the server side by an iRule.This issue occurs when all of the following conditions are met:You have configured a virtual server to use a OneConnect profile.The virtual server references an iRule that disables OneConnect reuse on server side connections. For example: when SERVER_CONNECTED { if { [clientside ONECONNECT::reuse] } {
↧
Known Issue: The Idle Timeout period is five seconds when using ePVA full acceleration
(SOL17426) Known IssueThe Idle Timeout period is five seconds when usingembedded Packet Velocity Acceleration (ePVA) full acceleration.This issue occurs when all of the following conditions are met: Your BIG-IP system has an ePVA chip. For more information about platforms with the ePVA chip, refer to SOL12837: Overview of the ePVA feature. The system processes traffic with a TCP virtual server that has an associated FastL4 profile. The FastL4 profile's PVA acceleration value is "full" and the
↧