(SOL14218) Summary
The tables in this article list the amount of memory and the number of CPU cores allocated to aVirtual Clustered Multiprocessing (vCMP) guest for each of the VIPRION and BIG-IP platforms that support vCMP.
Description
Starting in BIG-IP 11.0.0, the BIG-IP system supports vCMP, a feature that allows you to run multiple instances (guests) of the BIG-IP software on a single hardware platform. The vCMP host (hypervisor) allocates hardware resources to each BIG-IP vCMP guest instance.
The f
↧
Informational: vCMP guest memory/CPU core allocation matrix
↧
Manual: BIG-IP TMOS: Tunneling and IPsec
↧
↧
Informational: BIG-IP support for spanning tree protocols
(SOL9796) Note: Spanning Tree Protocol (STP) and Link Layer Discovery Protocol (LLDP) are supported on the 2000/4000 series hardware platforms beginning in BIG-IP 11.6.0.
BIG-IP systems support the following spanning tree protocol implementations:
Spanning Tree Protocol (STP, IEEE 802.1d )
Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w)
Multiple Spanning Tree Protocol (MSTP, IEEE 802.1s/802.1Q-2003)
The BIG-IP system does not support proprietary versions of the spanning tree protocol, such as PVST, PVS
↧
Known Issue: Creating a DNS monitor or loading a configuration containing DNS monitors may fail
(SOL16032) Description
Creating a DNS monitor or loading a configuration containing DNS monitors may fail.
This issue occurs when all of the following conditions are met:
The BIG-IP system is running or has recently been upgraded to BIG-IP 11.4.0 or later.
The BIG-IP system is not licensed with the BIG-IP LTM, GTM or DNS Services modules.
Impact
The BIG-IP system is unable to create a DNS monitor or load a configuration that contains DNS monitors.
Symptoms
As a result of this issue, you may encounter one
↧
Known Issue: Unable to delete FQDN nodes in multiple partitions
(SOL16332) Description
The BIG-IP Configuration utility and Traffic Management Shell (tmsh) may erroneously allow you to create nodes with the same Fully Qualified Domain Name (FQDN) across partitions.
This issue occurs when all of the following conditions are met:
You have multiple partitions configured.
You create a FQDN node in multiple partitions.
Impact
You are unable to delete FQDN nodes that exist in multiple partitions with the same FQDN.
Symptoms
As a result of this issue, you may encounter
↧
↧
Known Issue: The SSL::disable and SSL::enable iRule commands may cause connections to reset
(SOL16520) Description
The SSL::disable and SSL::enable iRule commands may cause connections to reset.
This issue occurs when the following condition is met:
An iRule configuration includes the SSL::enable command immediately after the SSL::disable command, similar to the following example:
ltm rule /Common/test_ssl_rule {
when HTTP_REQUEST {
SSL::disable serverside
if { [HTTP::uri] starts_with "/ssl" } {
SSL::enable serverside
}
}
}
Impact
Connections may be intermittently an
↧
Informational: BIG-IP hardware SSL and compression cards
(SOL7778) The following BIG-IP platforms are equipped with the hardwareSecure Socket Layer (SSL) card and/or hardware compression card:
Platform
Hardware SSL Card
Hardware Compression Card
(max hardware compression throughput)
520/540
Broadcom BCM95820 PCI
None
1000
Broadcom BCM5822
None
2400
Broadcom BCM5822
None
51x0
Broadcom BCM5821
None
1500
Cavium Nitrox 1005 PCI
None
1600
Cavium Nitrox 1610 PCI
None
2000s
Intel Cave Creek
None
2200s
Intel Cave Creek
Intel Cave Cr
↧
Security Advisory: Apache Tomcat vulnerability CVE-2014-0096
(SOL15428)
↧
Informational: Match Across options for session persistence
(SOL5837) BIG-IP offers multiple persistence options that you can use to ensure that a client is directed back to the same server to whichit was originally load balanced.
Bydefault, persistence records are specific to the virtual server upon which they arrived, and include both the IP address and the port of the selected pool member. However, in some configurations, multiple virtual servers may share the same servers, and a different approach to persistence across services, virtual servers, or pools may b
↧
↧
Manual: BIG-IP Link Controller: Monitors Reference
↧
Manual: BIG-IP Global Traffic Manager: Monitors Reference
↧
Troubleshooting: Troubleshooting RSA SecurID authentication
(SOL12164) If users experience system-wideissues authenticating against RSA SecurID, you can troubleshoot the issue in the following ways:
Confirming the AAA server definition
Confirming the IP Address of RSA SecurID server
Ensuring that the network path is open between the BIG-IP APM system and the RSA SecurID server
Checking the time on systems
Viewing logs
Running the securidtest utility
Reviewing the RSA SecurID server
Generating and uploading thenew sdconf.rec file
Confirming the AAA server definiti
↧
Known Issue: The BIG-IP LTM Acceleration > Symmetric Optimization menu may be missing form the Configuration utility
(SOL16513) Description
The BIG-IP LTM Acceleration > Symmetric Optimization menu may be missing from the Configuration utility.
This issue occurs when all of the following conditions are met:
You have licensed the system for BIG-IP LTM.
You have not licensed the system BIG-IP AAM.
Impact
You are unable to configureiSession acceleration objects using the Configuration utility.
Symptoms
As a result of this issue, you may encounter one or more of the following symptoms:
The Acceleration > Symmetric
↧
↧
Known Issue: Radius authentication may fail
(SOL16522) Description
Radius authentication may fail.
This issue occurs when all of the following conditions are met:
The BIG-IP APM access policy references a Radius AAA profile.
The Radius AAA profile is configured with a pool of Radius servers that reside in a non-default route domain.
Impact
Authentication fails.
Symptoms
As a result of this issue, you may encounter the following symptom:
When viewing the Radius request sent to the destination Radius server, the nas-ip-address is omitted.
Status
↧
Known Issue: Form-based client-initiated SSO may cause TMM to exit and restart
(SOL16527) Description
Form-based client-initiated single sign-on (SSO) may cause the Traffic Management Microkernel (TMM) to exit and restart.
This issue occurs when all of the following conditions are met:
The BIG-IP APM system is configured to use form-based client-initiated SSO authentication.
Memory corruption occurs due to a decryption failure on the BIG-IP APM system during SSO processing.
Impact
The BIG-IP APM system may temporarily fail to process traffic, and fail over if you have configured it
↧
Known Issue: The bigip health monitor incorrectly marks down virtual servers with a duplicate ltm-name
(SOL16194) Description
The bigip health monitor incorrectly marks down virtual servers with a duplicate ltm-name.
This issue occurs when all of the following conditions are met:
You have a BIG-IP GTM system monitoring BIG-IP LTM virtual servers using the bigip monitor.
A BIG-IP GTM server object has two BIG-IP LTM virtual servers with the same ltm-name. For example, the ltm-name one.test.com_webservers occurs twice in the following BIG-IP GTM server object:
gtm server /Common/local_server {
addresse
↧
Known Issue: The BIG-IP system may incorrectly mark pool members down when health monitor traffic uses TCP source port 54321
(SOL15907) Description
The BIG-IP system may incorrectly mark pool members down when the health monitor traffic uses TCP source port 54321.
This issue occurs because the default iptables rules on the BIG-IP system contain a rule that is configured to protect a BIG-IP APM service listening on TCP port 54321, even though APM or SWG is not provisioned.
Impact
Pool members monitored by the affected health monitor are erroneously marked down.
Symptoms
As a result of this issue, you may encounter one or more of
↧
↧
Informational: Supported operating systems and web browsers for the BIG-IP APM system
(SOL14047) The BIG-IP APM system uses a stand-alone client or web browser plug-ins to provide users with Virtual Private Network (VPN) access through a BIG-IP APM system. The BIG-IP APM system supports the following operating systems and web browsers:
Operating systems
Microsoft Windows
Apple OS X
Linux
Apple iOS
Google Android
Web browsers
Internet Explorer
Mozilla Firefox
Google Chrome
Apple Safari
BIG-IP APM client compatibility
To view whether a specific version of an operating system or web brows
↧
Security Advisory: Multiple Wireshark vulnerabilities
(SOL15868)
↧
Security Advisory: TLS in Mozilla NSS vulnerability CVE-2013-1620
(SOL15630)
↧