(SOL3759) Note: This article only applies to BIG-IP platforms that contain an SCCP (1500, 3400, 4100, 6400, 6800, 8400, and 8800).
Synchronizing SSH keys
TheSwitch Card Control Processor (SCCP) and BIG-IP host systemsecure shell (SSH) keys can become unsynchronized if you modify the keys or restore the keys from a backup. To synchronize the SSH keys, perform the following procedure:
Log in to the command line using the root account.
Synchronize the keys by typing the following command:keyswap.sh sccp
W
↧
How-To: Synchronizing SSH keys between the BIG-IP host system and the SCCP
↧
Informational: Enterprise Manager 3.1.1 cumulative hotfix
(SOL15199) F5 has recently discovered and corrected a number of issues that affect customers running Enterprise Manager 3.1.1. F5 recommends that all customers currently running Enterprise Manager 3.1.1 install the latest cumulative rollup hotfix.
The following table lists the rollup hotfixes released for Enterprise Manager 3.1.1. The table lists each hotfix, along with the ID numbers of issues that the corresponding hotfix resolves, and a description of each issue. If an article exists for the issue, the
↧
↧
Known Issue: TMM may produce a core with the 'Assertion "correct accounting" failed' error message
(SOL15926) Description
The Traffic Management Microkernel (TMM) process may produce a core file that includes the 'Assertion "correct accounting" failed' error message.
This issue occurs when the following condition is met:
Your BIG-IP platform is equipped with a Cavium Nitrox SSL or hardware compression card. To determine if your BIG-IP platform is equipped with a Cavium Nitrox card, refer to SOL7778: BIG-IP hardware SSL and compression cards.
In rare instances, I/O flows for the Cavium Nitrox
↧
Manual: FirePass Controller Client Compatibility Matrix
↧
Manual: BIG-IP APM Client Compatibility Matrix
↧
↧
Manual: BIG-IP APM Client Compatibility Matrix
↧
How-To: Configuring the BIG-IP system to run commands or scripts upon system startup
(SOL11948) Important:F5 recommends that you modify the startup commands or scripts only when directed by F5 Technical Support.
To configure the BIG-IP system to run startup commands or scripts, append the commands or scripts to the end of the /config/startup file. The /config/startup file is called by /etc/rc.local, and the file is saved in UCS archive files and synchronized to redundant BIG-IP systems during ConfigSync operations.
Note: F5 periodically changes the /etc/rc.local file between software relea
↧
Known Issue: TCP sessions on virtual servers with BIG-IP WebAccelerator and ASM configured may reset
(SOL15824) Description
TCP sessions on virtual servers, with both BIG-IP WebAccelerator and ASM configured, may reset.
This issue occurs when all of the following conditions are met:
A virtual server configuration includes a BIG-IP ASM httpclass and a WebAccelerator profile.
The BIG-IP ASM httpclass is configured to bypass the BIG-IP WebAccelerator system.
Impact
Affected client connections will terminate with a TCP RESET packet.
Symptoms
As a result of this issue, you may encounter the following symptom
↧
How-To: Accessing the bash shell as a remotely authenticated user
(SOL10272) You can assign privileges to remote user accounts by mapping vendor-specific attributes to a set of access-control properties defined within the BIG-IP configuration. One of the configurable privileges is remote console access for users. An administrator can enable or disable this privilege, however, the shell program is not a configurable option. Since remote users do not have an account defined in the /etc/passwd file, a custom shell cannot be defined there either. As a result, the shell for r
↧
↧
Known Issue: Enterprise Manager may fail to transfer a UCS archive from a managed device
(SOL15944) Description
When the Enterprise Manager system takes more than ten minutes to transfer the user configuration set (UCS) archive from a managed device via iControl, the Enterprise Manager auth token times out and the file transfer fails.
This issue occurs when one or both of the following conditions are met:
The affected UCS archive is particularly large
The network latency between the Enterprise Manager system and the managed device is high
Impact
The Enterprise Manager system is unable to t
↧
Known Issue: An incorrect MSS calculation with FastL4 may result in a TMM core
(SOL15945) Description
An incorrect maximum segment size (MSS) calculation with FastL4 may cause the Traffic Management Microkernel (TMM) to produce a core file.
This issue occurs when all of the following conditions are met:
Differing MSS values result in an incorrect calculation.
You are using the FastL4 profile.
Impact
TMM may produce a core file and temporarily fail to process traffic.
Symptoms
As a result of this issue, you may encounter the following symptoms:
The BIG-IP system sends aSIGSEGV sig
↧
Known Issue: TMM may log 'Clock advanced by' messages and possibly restart when loading many FIPS keys on BIG-IP 11050 platforms
(SOL15950) Description
The Traffic Management Microkernel (TMM) may log Clock advanced by <number> ticks messages, and may also restart, when loading many FIPS keys on a BIG-IP 11050 platform.
This issue occurs when all of the following conditions are met:
You have a BIG-IP 11050 platform with a FIPS card installed.
You have created 200 or more FIPS keys.
Impact
TMM may restart and temporarily fail to process traffic.
Symptoms
As a result of this issue, you may encounter one or more of the follo
↧
Known Issue: TMM may restart when a FastL4 virtual server has connection mirroring enabled
(SOL15947) Description
TMM may restart and produce a core file when a FastL4 virtual server has connection mirroring enabled.
This issue occurs when all of the following conditions are met:
A virtual server is configured to use a FastL4 profile.
The virtual server has connection mirroring enabled.
Impact
Service will be interrupted as TMM restarts.
Symptoms
As a result of this issue, you may encounter one or more of the following symptoms:
The BIG-IP system may fail to process traffic for a brief period
↧
↧
Known Issue: The BIG-IP APM /var/log/httpd/access_log file may not contain data
(SOL15943) Description
The BIG-IP APM /var/log/httpd/access_log file may not contain data.
This issue occurs when all of the following conditions are met:
Your BIG-IP APM system is configured with an access policy that actively processes user sessions.
Your BIG-IP APM system has already run the daily log rotation (default time is 4:02 AM).
User sessions are processed after the daily log rotation.
Impact
Access logs are no longer written to the /var/log/httpd/access_log file.
Symptoms
As a result of this
↧
How-To: Resetting the BIG-IP ASM database to a default configuration
(SOL6992) You can restore the BIG-IP ASM database to a default or clean configuration by performing the following procedure:
Note: This procedure restores the BIG-IP ASM MySQL database to default settings. It does not affect or restore BIG-IP LTM configuration objects. For more information, refer to SOL7550: Restoring the BIG-IP configuration to factory default settings (9.3.x - 9.4.x).
Log in to the BIG-IP ASM command line.
Stop theASM module by typing the following command:
bigstart stop asm
For 9
↧
Error Message: Error Message: Received message too long 1433625970
(SOL15952) Error Message
Received message too long 1433625970
Message Location
You may encounter this message in the following location:
Secure shell (SSH)session console output
Description
This message occurs when all of the following conditions are met:
Command line SSH File Transfer Protocol (SFTP) is used to transfer a file to a BIG-IP system.
The user credentials utilized are not privileged to transfer files to the BIG-IP system with SSH.
Impact
The user is unable to use SFTP to transfer a file
↧
Informational: Good, Better, Best license options and provisioning
(SOL14826) Summary
Starting in November 2013 (for Virtual Edition (VE) and appliances), and December 2013 (for VIPRION), F5 is introducing a tiered licensing model to consolidate purchasing options for its solutions and to significantly reduce customer costs when customers deploy application services together versus individually. This Good, Better, Best licensing schema will be available on the following F5 platforms:
Virtual Edition (VE)
BIG-IP 4000 series
BIG-IP 5000 series
BIG-IP 7000 series
BIG-IP 100
↧
↧
Known Issue: TMM may leak memory when connections with compressed content are reset
(SOL15955) Description
The Traffic Management Microkernel (TMM) may leak memory when connections with compressed content are reset.
This issue occurs when all of the following conditions are met:
Your system is running on one of the following BIG-IP platforms:
2000s or 2200s
4000s or 4200v
You have a virtual server that uses hardware compression.
Compressed streams are reset.
Impact
Performance may degrade over time and the system may eventually become unresponsive due to memory exhaustion.
Sympt
↧
Known Issue: TMM may produce a core with the 'Assertion "we always have room in tx ring!" failed' error message
(SOL15953) Description
The Traffic Management Microkernel (TMM) process may produce a core file that includes the 'Assertion "we always have room in tx ring!" failed' error message.
This issue occurs when the following condition is met:
TCP segmentation offload (TSO) is enabled on the BIG-IP system.Note: TSO support was introduced in BIG-IP 11.4.0 and was initially enabled, by default, only for BIG-IP Virtual Edition (VE). However, beginning in BIG-IP 11.5.0, TSO is enabled, by default, for all
↧
Known Issue: The BIG-IP system may erroneously log critical messages after synchronizing an updated SSL key/certificate to the device group
(SOL15960) Description
The BIG-IP system may erroneously log critical messages about the failure to load SSL certificate and key files (for details of the critical level messages, refer to the Symptoms section).
This issue occurs when all of the following conditions are met:
The BIG-IP system is running any of the following versions:
11.6.0 through 11.6.0 HF3
11.4.0 through 11.5.1 HF5
11.3.0 HF6 through 11.3.0 HF10
11.2.1 HF8 through 11.2.1 HF13
You deleted and recreated an SSL certificate or SSL ke
↧