Applies To:
Show Versions
BIG-IP versions 1.x - 4.x
- 4.6.4
Updated Date: 04/18/2019
Summary:
This release note documents version 4.6.4 of the BIG-IP® software. You can apply the software upgrade to version 4.5 and later. For information about installing the software, please refer to the instructions below.
F5 now offers both maintenance-only and new feature releases. Version 4.6.4 is a feature release that is based on version 4.5.12 code. This release includes all features and fixes included in versions 4.5.12 and 4.6.2. For more information on our new release polices, please see New Versioning Schema for F5 Software Releases.
Warning: This is a feature release, not a maintenance release. Unless you need specific features that are new to this feature release, please upgrade to the latest maintenance release instead.
Contents:
Minimum system requirements and supported browsers
The minimum system requirements for this release are:
- Intel® Pentium® III 550MHz processor
- 256MB disk drive or CompactFlash® card (if you have the 3-DNS module, you need a 512MB disk drive or CompactFlash® card)
- 256MB RAM
The supported browsers for the Configuration utility are:
- Microsoft® Internet Explorer 5.0, 5.5, and 6.0
- Netscape® Navigator 4.7x
Note: The IM package for this release is quite large. If the disk drive in your platform does not meet the minimum requirement, you may not be able to successfully install this release.
Supported platforms
This release supports the following platforms:
- D35 (BIG-IP 520 and 540)
- D39 (BIG-IP 1000)
- D44 (BIG-IP 2400)
- D45 (BIG-IP 2000)
- D50 (BIG-IP 5000)
- D51 (BIG-IP 5100 and 5110)
If you are unsure which platform you have, look at the sticker on the back of the chassis to find the platform number.
Installing the software
Important: Before you run the Configuration utility to configure the unit, you must complete the authorization and licensing process. (For details, see the Activating the license section of the BIG-IP version 4.5 Release Note.) If you do not obtain a license before you run the Configuration utility, the system may behave in an unexpected manner.
Important: If you are upgrading a BIG-IP redundant system, you must upgrade both units. We do not support running different versions on a BIG-IP redundant system.
Important: If you are upgrading an IP Application Switch or a BIG-IP system that uses a CompactFlash® media drive, use the installation instructions here.
Note: In rare instances, using a notebook computer to perform PXE installations of BIG-IP software causes corruption on the notebook computer hard drive. If you are using a notebook computer as a PXE server to install BIG-IP software, we recommend, as a precaution, that you first back up any important data stored on the notebook computer hard drive.
The following instructions explain how to install the BIG-IP software, version 4.6.4 onto existing systems running version 4.5 and later. The installation script saves your current configuration.
- Go to the Downloads site and locate the BIG-IP 4.6.4 upgrade file, BIGIP_4.6.4_Upgrade.im.
- Download the software image and the BIGIP_4.6.4_Upgrade.md5 file.
For information about how to download software, refer to SOL167: Downloading software from F5 Networks.
- If you downloaded the image file to a directory other than /var/tmp, copy the image file to the /var/tmp/ directory on your BIG-IP system.
- Check the md5 of the upgrade file by typing the following command:
md5 BIGIP_4.6.4_Upgrade.im
cat BIGIP_4.6.4_Upgrade.md5The two md5 values should be identical.
- Install this PTF by typing the following command:
im BIGIP_4.6.4_Upgrade.imThe BIG-IP system automatically reboots once it completes installation.
To upgrade an IP Application Switch or a BIG-IP system that uses a CompactFlash media drive, use the following process.
- Create a memory file system by typing the following command:
mount_mfs -s 200000 /mnt
- Go to the Downloads site and locate the BIG-IP 4.6.4 upgrade file, BIGIP_4.6.4_Upgrade.im.
- Download the software image and the BIGIP_4.6.4_Upgrade.md5 file.
For information about how to download software, refer to SOL167: Downloading software from F5 Networks.
- If you downloaded the image file to a directory other than /mnt, copy the image file to the /vmnt directory on your BIG-IP system.
- Check the md5 of the upgrade file by typing the following command:
md5 BIGIP_4.6.4_Upgrade.im
cat BIGIP_4.6.4_Upgrade.md5The two md5 values should be identical.
- Install this PTF by typing the following command:
im /mnt/BIGIP_4.6.4_Upgrade.imThe BIG-IP system automatically reboots once it completes installation.
Note: This procedure provides over 90MB of temporary space on /mnt. The partition and the im package file are deleted upon rebooting.
Activating the license
Once you install the upgrade and connect the unit to the network, you need a valid license certificate to activate the software. To gain a license certificate, you need to provide two items to the license server: a registration key and a dossier.
The registration key is a 25-character string. You should have received the key by email. The registration key lets the license server know which F5 products you are entitled to license.
The dossier is obtained from the software, and is an encrypted list of key characteristics used to identify the platform.
You can obtain a license certificate using one of the following methods:
- Automatic license activation
You perform automatic license activation from the command line or from the web-based Configuration utility of an upgraded unit. This method automatically retrieves and submits the dossier to the F5 license server, as well as installs the signed license certificate. In order for you to use this method, the unit must be installed on a network with Internet access. - Manual license activation
You perform manual license activation from the Configuration utility, which is the software user interface. With this method, you submit the dossier to, and retrieve the signed license file from, the F5 license server manually. In order for you to use this method, the administrative workstation must have Internet access.
Note: You can open the Configuration utility using either Netscape Navigator 4.7x, or Microsoft Internet Explorer 5.0, 5.5, or 6.0.
To automatically activate a license from the command line for first time installation
- Type the user name root and the password default at the logon prompt.
- At the prompt, type license. The following prompts display:
IP:
Netmask:
Default Route:
Select interface to use to retrieve license:
The unit uses this information to make an Internet connection to the license server. - After you type the Internet connection information, continue to the following prompt:
The Registration Key should have been included with the software or given when the order was placed. Do you have your Registration Key? [Y/N]:
Type Y, and the following prompt displays:
Registration Key: - Type the 25-character registration key you received. If you received more than one key, enter all of the keys, separating each with a space.
The dossier is retrieved and sent to the F5 license server, and a signed license file is returned and installed. A message displays indicating the process was successful. - You are asked to accept the End User License Agreement.
The system is not fully functional until you accept this agreement. - You are prompted to reboot the system. Press Enter to reboot.
The system is not fully functional until you reboot.
To automatically activate a license from the command line for upgrades
- Type your user name and password at the logon prompt.
- At the prompt, type setup.
- Choose menu option L.
- The following prompt displays:
Number of keys: 1
If you have more than one registration key, enter the appropriate number. - The following prompt displays:
Registration Key:
Type the 25-character registration key you received. If you received more than one key, enter all of the keys, separating each with a space.
The dossier is retrieved and sent to the F5 license server, and a signed license file is returned and installed. A message displays indicating the process was successful. - When you are finished with the licensing process, type the following command to restart the services on the system:
bigstart restart
To manually activate a license using the Configuration utility
- Open the Configuration utility according to the type of BIG-IP unit you are licensing:
- If you are licensing a previously configured BIG-IP unit, open the Configuration utility using the configured address.
- If you are licensing a new BIG-IP unit, from the administrative workstation, open the Configuration utility using one of the following addresses: https://192.168.1.245 or https://192.168.245.245. These are default addresses on the units local area network.
- If you are licensing a previously configured BIG-IP unit, open the Configuration utility using the configured address.
- Type the user name and password, based on the type of BIG-IP unit you are licensing:
- If you are licensing a previously configured BIG-IP unit, type your user name and password at the logon prompt.
- If you are licensing a new BIG-IP system, type the user name root, and the password default at the logon prompt.
The Configuration utility menu displays. - If you are licensing a previously configured BIG-IP unit, type your user name and password at the logon prompt.
- Click License Utility to open the License Administration screen.
- In the Registration Key box, type the 25-character registration key that you received. If you have more than one key to install, click Enter More Keys to install multiple keys. Once you have entered all registration keys, click Manual Authorization.
- At the Manual Authorization screen, retrieve the dossier using one of the following methods:
- Copy the entire contents of the Product Dossier box.
- Click Download Product Dossier, and save the dossier to the hard drive.
- Copy the entire contents of the Product Dossier box.
- Click the link in the License Server box.
The Activate F5 License screen opens in a new browser window. - From the Activate F5 License screen, submit the dossier using one of the following methods:
- Paste the data you just copied into the Enter your dossier box, and click Activate.
- At the Product Dossier box, click Browse to locate the dossier on the hard drive, and then click Activate.
The screen returns a signed license file. - Paste the data you just copied into the Enter your dossier box, and click Activate.
- Retrieve the license file using one of the following methods:
- Copy the entire contents of the signed license file.
- Click Download license, and save the license file to the hard drive.
- Copy the entire contents of the signed license file.
- Return to the Manual Authorization screen, and click Continue.
- At the Install License screen, submit the license file using one of the following methods:
- Paste the data you copied into the License Server Output box, and click Install License.
- At the License File box, click Browse to locate the license file on the hard drive, and then click Install License.
The License Status screen displays status messages, and Process complete appears when the licensing activation is finished. - Paste the data you copied into the License Server Output box, and click Install License.
- Click License Terms, review the EULA, and accept it.
- At the Reboot Prompt screen, select when you want to reboot the platform.
License activation is complete only after rebooting.
To automatically activate a license using the Configuration utility
- Open the Configuration utility according to the type of BIG-IP unit you are licensing:
- If you are licensing a previously configured BIG-IP unit, open the Configuration utility using the configured address.
- If you are licensing a new BIG-IP unit, from the administrative workstation, open the Configuration utility using one of the following addresses: https://192.168.1.245 or https://192.168.245.245. These are default addresses on the units local area network.
- If you are licensing a previously configured BIG-IP unit, open the Configuration utility using the configured address.
- Type the name and password, based on what type of BIG-IP unit you are licensing:
- If you are licensing a previously configured BIG-IP unit, type your user name and password at the logon prompt.
- If you are licensing a new BIG-IP unit, type the user name root, and the password default at the logon prompt.
The Configuration utility menu displays. - If you are licensing a previously configured BIG-IP unit, type your user name and password at the logon prompt.
- Click License Utility to open the License Administration screen.
- In the Registration Key box, type the 25-character registration key that you received. If you have more than one key to install, click Enter More Keys to install multiple keys. Once you have entered all registration keys, click Automated Authorization.
The License Status screen displays status messages, and Process complete appears when the licensing activation is finished. - Click License Terms, review the EULA, and accept it.
- At the Reboot Prompt screen, select when you want to reboot the platform.
License activation is complete only after rebooting.
New features in this release
This release includes no new features. The primary reason we released version 4.6.4 was to fix an issue that existed in version 4.6.3 which, under certain circumstances, caused the system to become unresponsive. The issue has been resolved in version 4.6.4.
New fixes in this release
Note: In version 4.6.3, we modified the format for displaying CRs for fixes and known issues. So from version 4.6.3 on, the CRs are listed in a table format, with the corresponding solution listed next to the CR. Clicking the solution link directs you to the more detailed solution document that is posted on the AskF5 Technical Support Web Site. We continually update these solution documents on AskF5 as new details become available. If additional known issues are discovered after we release a version, we will update the known issues table with the new CR and solution numbers, with the goal of keeping you current on our known issues.
If you encounter a CR that does not have an active solution link, it is likely that we have not yet had a chance to get the solution posted on AskF5, but please continue to check this table for new content or links.
This release includes the following new fixes.
CR | Solution | Description |
CR47237 | SOL4583 | Some versions of the BIG-IP system are subject to the vulnerability described in VU#222750 |
CR47296 | SOL4583 | Some versions of the BIG-IP system are subject to the vulnerability described in VU#222750 |
CR47613 | SOL4722 | SSL sessions might not be closed correctly when SSL persistence is enabled |
CR47719 | SOL4819 | The BIG-IP system might become unresponsive when performing delayed binding operations |
CR47758 | SOL4819 | The BIG-IP system might become unresponsive when performing delayed binding operations |
CR47829 | SOL4821 | The BIG-IP system might reset HTTP connections that contain a retransmitted response |
CR47830 | SOL4821 | The BIG-IP system might reset HTTP connections that contain a retransmitted response |
CR48224 | SOL4720 | Connections to a Siebel application server might fail due to pipelining protection |
CR48262 | SOL4583 | Some versions of the BIG-IP system are subject to the vulnerability described in VU#222750 |
CR48301 | SOL4718 | The BIG-IP system might become unresponsive or behave unpredictably when you use header insert |
CR48302 | SOL4718 | The BIG-IP system might become unresponsive or behave unpredictably when you use header insert |
CR48303 | SOL4718 | The BIG-IP system might become unresponsive or behave unpredictably when you use header insert |
CR48313 | SOL4583 | Some versions of the BIG-IP system are subject to the vulnerability described in VU#222750 |
CR48314 | SOL4720 | Connections to a Siebel application server might fail due to pipelining protection |
CR48315 | SOL4722 | SSL sessions might not be closed correctly when SSL persistence is enabled |
CR48353 | SOL4819 | The BIG-IP system might become unresponsive when using delayed binding features |
CR48563 | SOL4821 | The BIG-IP system might reset HTTP connections that contain a retransmitted response |
CR48835 | SOL4900 | The BIG-IP system might corrupt UDP packets when the packets are accelerated by PVA |
CR49011 | SOL4900 | The BIG-IP system might corrupt UDP packets when the packets are accelerated by PVA |
Fixes and features in prior releases
To view fixes and features that were distributed in prior releases, see the previous release notes on AskF5.
Known issues
CR | Solution | Description |
CR571 | SOL808 | Reverse ECV monitors report node status at the same frequency as the timeout period that you have configured |
CR14962 | SOL4539 | If you connect to the standby system you might get an address conflict warning message |
CR15998 | SOL4539 | If you connect to the standby system you might get an address conflict warning message |
CR20647 | SOL4539 | If you connect to the standby system you might get an address conflict warning message |
CR20801 | SOL213 | SNATs route by packet, rather than by connection, as virtual servers route |
CR21228 | SOL216 | Auto-lasthop prevents ARP information update for self address traffic |
CR21750 | SOL497 | The bigpipe proxy show command may not display the correct values for current and max connections |
CR22494 | SOL507 | For connections accelerated by the PVA, the BIG-IP system does not send a reset to the client or the node |
CR22728 | SOL837 | When gateway failsafe is triggered for active-active units in a redundant pair, failover does not occur |
CR23564 | SOL783 | Saving a new copy of snmptrap.conf can create a conflict after an upgrade |
CR24772 | SOL5131 | HTTP POSTs are slow when cookie persistence is enabled |
CR25821 | SOL816 | F5 source addresses are not added to hosts.allow when the support account is enabled |
CR25874 | SOL271 | The BIG-IP system does not work correctly with administrative user names longer than 15 characters |
CR26137 | SOL4111 | You cannot set cookie attributes when using cookie persistence |
CR26567 | SOL222 | Client MSS is not provided to the node when SYN cookies are in use |
CR26610 | SOL336 | Using the Configuration utility to disable SNMP traps causes an error |
CR26612 | SOL848 | The beholder-ctrl bigstart script does not include the stop and start command functions, which results in an error |
CR26843 | SOL359 | You cannot configure a URI path for a fallback host using the command line |
CR26953 | SOL4148 | The bigpipe snatpool show command displays incorrect values for a new SNAT pool |
CR27049 | SOL4301 | Subject and Issuer data is not displayed correctly for certificates encoded using BMPSTRING or UTF8STRING |
CR27061 | SOL4148 | The bigpipe snatpool show command displays incorrect values for a new SNAT pool |
CR27090 | SOL226 | The BIG-IP system might become unresponsive when the target of a virtual server is changed |
CR27158 | SOL494 | The BIG-IP system disables ARP for all virtual servers even though it is disabled for only a single virtual server |
CR27202 | SOL727 | The SNMPDCA monitor is not fully compatible with the Microsoft http_server MIB |
CR27229 | SOL363 | Changes to bigdb keys are not saved unless the configuration is saved |
CR27260 | SOL371 | You cannot change default gateway pools using the config command |
CR27515 | SOL236 | SIP persistence does not key connections to a particular virtual server |
CR27515 | SOL239 | SIP persistence does not work correctly when the SIP connection is handled by a SNAT |
CR27547 | SOL298 | Ratio settings are not available when ratio is used as the alternate load balancing mode |
CR27607 | SOL4252 | The bigpipe pool command does not display SIP persistence records |
CR27635 | SOL151 | The vlangroups global setting applies only to the first configured VLAN group |
CR27639 | SOL428 | In active-active pairs, the unit ID of a local self IP address for unit 2 is reported as the unit ID of a local self IP address for unit 1 |
CR27650 | SOL433 | You must manually configure hops factories before hops load balancing works on a Link Controller |
CR27975 | SOL240 | You cannot set the global memory_reboot_percent to 0 |
CR28012 | SOL250 | The status LED incorrectly displays green on a standby unit when a power supply has failed |
CR28035 | SOL4120 | A Java error is reported when you assign the Oracle health monitor to an invalid node |
CR28057 | SOL461 | Changing the port of a virtual server results in multiple virtual server statements |
CR28072 | SOL467 | You can partially remove a link by deleting its self address and VLAN |
CR28099 | SOL486 | BIG-IP will continue to probe any routers that are defined for a datacenter, even if you have deleted all of the BIG-IP prober factories |
CR28124 | SOL241 | The standby unit configures a floating self address if it does not have its own self address |
CR28217 | SOL1435 | The Configuration utility allows a maximum of 15 characters for an Auth Model role in the Valid Roles list |
CR28333 | SOL184 | The Configuration utility does not create an ECV monitor that includes an Authorization: header |
CR28346 | SOL251 | You cannot configure the BIG-IP system to pass bootp traffic |
CR28421 | SOL3734 | SSL proxies might retransmit multiple packets from a connection |
CR28429 | SOL1566 | The Setup utility does not allow VLAN names with more than 12 characters |
CR28451 | SOL1643 | The bigpipe verify command does not detect misspelled monitor names or monitors that do not exist |
CR28533 | SOL5143 | Web aggregation may fail when a default SNAT automap is enabled |
CR28656 | SOL520 | The wlnode() function does not work with BEA Web Logic 7.0 and later versions |
CR29394 | SOL5135 | BIG-IP may fail back to a previous failover state in a very specific and unusual configuration |
CR29395 | SOL5135 | BIG-IP may fail back to a previous failover state in a very specific and unusual configuration |
CR29407 | SOL4148 | The bigpipe snatpool show command displays incorrect values for a new SNAT pool |
CR29421 | SOL1863 | When you attempt to print the snmpget help screen, the snmp_dca health monitor enters a loop |
CR29475 | SOL200 | Insert mode cookie persistence might very rarely fail due to node-side packet loss |
CR29602 | SOL249 | The bigpipe interface command incorrectly reports the media type of fiber ports as 1000BaseTX |
CR29606 | SOL1864 | SNMP monitoring software reports an error when it attempts to query the ifRcvAddressAddress OID entry in the ifRcvAddressEntry table |
CR29709 | SOL242 | The BIG-IP system sends a reset to the node when deleting a connection that was never fully established |
CR29744 | SOL256 | The BIG-IP system reports that Probe control features are not available when VLAN mirroring is enabled |
CR29751 | SOL3783 | The verify command rejects configurations using SNAT connection mirroring |
CR29801 | SOL4407 | An unhelpful error message displays when you enter a header insert that is too long |
CR29988 | SOL243 | Connections might be deleted as much as 30 seconds after they are timed out |
CR30143 | SOL244 | Priority load balancing does not work when you set minimum active members to 0 |
CR30493 | SOL4149 | ITCMPortal might become unresponsive when using large amounts of memory |
CR30731 | SOL4154 | Fragmented ICMP ping requests may not be passed by the BIG-IP system |
CR30783 | SOL2942 | Default gateway entry is converted to a default gateway pool |
CR30877 | SOL4242 | The im -Q command does not always report the correct versions for installed packages |
CR31044 | SOL245 | In rare circumstances, the BIG-IP system might become unresponsive during configsync |
CR31182 | SOL207 | Virtual server performance is lower on virtual servers that have not processed L7 traffic |
CR31994 | SOL246 | The bigAPI might not successfully free memory in some circumstances |
CR32179 | SOL2100 | The maximum value for 32-bit counters is 4,194,302 |
CR32242 | SOL4391 | You can configure node select expressions with invalid classes |
CR32791 | SOL4040 | The global vlans unique_mac might not work when VLANs contain the same tagged interface |
CR32826 | SOL208 | The header insert and erase features might not work when requests contain carriage returns before the command |
CR32944 | SOL4148 | The bigpipe snatpool show command displays incorrect values for a new SNAT pool |
CR33116 | SOL4032 | The BIG-IP system might become unresponsive if you configure a header insert on traffic that is not decrypted |
CR33223 | SOL4407 | An unhelpful error message displays when you enter a header insert that is too long |
CR33581 | SOL837 | When gateway failsafe is triggered for active-active units in a redundant pair, failover does not occur |
CR33583 | SOL3344 | SNMP statistics for the loopback interface are not collected |
CR33584 | SOL3344 | SNMP statistics for the loopback interface are not collected |
CR33774 | SOL5141 | Retransmissions from node to client may be dropped after packet loss between client and BIG-IP |
CR33815 | SOL761 | The table that contains Nokia NetAct SNMP traps might grow very large and use disk space |
CR33878 | SOL3566 | When you restore the archived snmptrap.conf file after an upgrade, the BIG-IP system uses the previous version of the snmptrap.conf file |
CR33921 | SOL3657 | Available memory reported by the memAvailReal OID and the vmstat command differs |
CR33922 | SOL258 | The BIG-IP system might report the CPU temperature as 255 degrees when it cannot determine the CPU temperature |
CR34022 | SOL654 | Nodes that are monitored with a monitor rule are reported as unchecked |
CR34056 | SOL658 | The symbolic link generation page does not provide scroll bars when output exceeds one screen |
CR34267 | SOL4717 | The BIG-IP system changes the interface media settings after running the Setup utility |
CR34409 | SOL209 | In very rare circumstances, the BIG-IP system might repeatedly become unresponsive |
CR35320 | SOL309 | The Telnet and FTP servers are not started when you enable Telnet and FTP |
CR35527 | SOL3775 | The BIG-IP system does not provide data for existing pool members in the PoolMemberEntry OID table |
CR35752 | SOL5080 | Gateway failsafe can cause a failover immediately after it is enabled |
CR35906 | SOL144 | Internal, hidden interfaces may be displayed by bigpipe vlan fdb show |
CR36811 | SOL310 | Link statistics are not displayed correctly after you add or remove links |
CR36993 | SOL265 | Time zone information is not restored after you reinstall system software |
CR37500 | SOL808 | Reverse ECV monitors mark nodes up only as frequently as the timeout period |
CR37746 | SOL808 | Reverse ECV monitors report node status at the same frequency as the timeout period that you have configured |
CR37847 | SOL4149 | ITCMPortal might become unresponsive when using large amounts of memory |
CR37915 | SOL4149 | ITCMPortal might become unresponsive when using large amounts of memory |
CR37986 | SOL5142 | Health monitors may attempt to use source ports that are already in use |
CR38085 | SOL800 | The SSL ECV monitor cannot negotiate an SSLv2 connection |
CR38086 | SOL145 | Copper gigabit switch ports should not allow manual media settings |
CR38087 | SOL145 | Copper gigabit switch ports should not allow manual media settings |
CR40319 | SOL694 | An error displays if you refresh the Configuration utility after creating a link |
CR40826 | SOL247 | Header insert does not work when the full HTTP command is not received at once |
CR40861 | SOL699 | SSL proxy address and port information is not checked for invalid addresses or characters |
CR40884 | SOL715 | The Configuration utility prompts for a netmask for individual virtual servers |
CR41694 | SOL5144 | ZebOS routing may not work correctly when SSL proxy target virtual servers are bound to loopback |
CR41762 | SOL151 | The vlangroups global setting applies only to the first configured VLAN group |
CR41763 | SOL184 | The Configuration utility does not create an ECV monitor that includes an Authorization: header |
CR41764 | SOL200 | Insert mode cookie persistence might very rarely fail due to node-side packet loss |
CR41766 | SOL207 | Virtual server performance is lower on virtual servers that have not processed L7 traffic |
CR41767 | SOL208 | The header insert and erase features might not work when requests contain carriage returns before the command |
CR41768 | SOL4148 | The bigpipe snatpool show command displays incorrect values for a new SNAT pool |
CR41769 | SOL209 | In very rare circumstances, the BIG-IP system might repeatedly become unresponsive |
CR41771 | SOL213 | SNATs route by packet, rather than by connection, as virtual servers route |
CR41772 | SOL216 | Auto-lasthop prevents ARP information update for self address traffic |
CR41773 | SOL222 | Client MSS is not provided to the node when SYN cookies are in use |
CR41774 | SOL226 | The BIG-IP system might become unresponsive when the target of a virtual server is changed |
CR41775 | SOL236 | SIP persistence does not key connections to a particular virtual server |
CR41775 | SOL239 | SIP persistence does not work correctly when the SIP connection is handled by a SNAT |
CR41776 | SOL240 | You cannot set the global memory_reboot_percent to 0 |
CR41777 | SOL241 | The standby unit configures a floating self address if it does not have its own self address |
CR41779 | SOL242 | The BIG-IP system sends a reset to the node when deleting a connection that was never fully established |
CR41780 | SOL243 | Connections might be deleted as much as 30 seconds after they are timed out |
CR41781 | SOL244 | Priority load balancing does not work when you set minimum active members to 0 |
CR41782 | SOL245 | In rare circumstances, the BIG-IP system might become unresponsive during configsync |
CR41783 | SOL246 | The bigAPI might not free memory successfully in some circumstances |
CR41784 | SOL808 | Reverse ECV monitors report node status at the same frequency as the timeout period that you have configured |
CR41785 | SOL247 | Header insert does not work when the full HTTP command is not received at once |
CR41786 | SOL249 | The bigpipe interface command incorrectly reports the media type of fiber ports as 1000BaseTX |
CR41788 | SOL250 | The status LED incorrectly displays green on a standby unit when a power supply has failed |
CR41790 | SOL251 | You cannot configure the BIG-IP system to pass bootp traffic |
CR41792 | SOL256 | The BIG-IP system reports that Probe control features are not available when VLAN mirroring is enabled |
CR41793 | SOL258 | The BIG-IP system might report the CPU temperature as 255 degrees when it cannot determine the CPU temperature |
CR41795 | SOL265 | Time zone information is not restored after you reinstall the system software |
CR41798 | SOL271 | The BIG-IP system does not work correctly with administrative user names longer than 15 characters |
CR41799 | SOL298 | Ratio settings are not available when ratio is used as the alternate load balancing mode |
CR41803 | SOL2942 | Default gateway entry is converted to a default gateway pool |
CR41805 | SOL309 | The Telnet and FTP servers are not started when you enable Telnet and FTP |
CR41807 | SOL310 | Link statistics are not displayed correctly after you add or remove links |
CR41819 | SOL336 | Disabling SNMP traps using the Configuration utility causes an error |
CR41820 | SOL336 | Disabling SNMP traps using the Configuration utility causes an error |
CR41822 | SOL359 | You cannot configure a URI path for a fallback host using the command line |
CR41823 | SOL363 | Changes to bigdb keys are not saved unless you save the configuration |
CR41824 | SOL371 | You cannot change default gateway pools using the config command |
CR41827 | SOL428 | In active-active pairs, the unit ID of a local self IP address for unit 2 is reported as the unit ID of a local self IP address for unit 1 |
CR41832 | SOL461 | Changing the port of a virtual server results in multiple virtual server statements |
CR41833 | SOL467 | You can partially remove a link by deleting its self address and VLAN |
CR41834 | SOL486 | BIG-IP will continue to probe any routers that are defined for a datacenter, even if you have deleted all of the BIG-IP prober factories |
CR41838 | SOL520 | The wlnode() function does not work with BEA Web Logic 7.0 and later versions |
CR41848 | SOL4407 | An unhelpful error message displays when you enter a header insert that is too long |
CR41850 | SOL654 | Nodes that are monitored with a monitor rule are reported as unchecked |
CR41851 | SOL658 | The symbolic link generation page does not provide scroll bars when output exceeds one screen |
CR41860 | SOL694 | An error displays if you refresh the Configuration utility after creating a link |
CR41861 | SOL699 | SSL proxy address and port information is not checked for invalid addresses or characters |
CR41862 | SOL715 | The Configuration utility prompts for a netmask for individual virtual servers |
CR41873 | SOL727 | The SNMPDCA monitor is not fully compatible with the Microsoft http_server MIB |
CR41877 | SOL761 | The table that contains Nokia NetAct SNMP traps might grow very large and use disk space |
CR41889 | SOL783 | Saving a new copy of snmptrap.conf can create a conflict after an upgrade |
CR41891 | SOL816 | F5 source addresses are not added to hosts.allow when the support account is enabled |
CR41892 | SOL848 | The beholder-ctrl bigstart script does not include the stop and start command functions, which results in an error |
CR41895 | SOL494 | The BIG-IP system disables ARP for all virtual servers even though it is disabled for only a single virtual server |
CR41898 | SOL1435 | The Configuration utility allows a maximum of 15 characters for an Auth Model role in the Valid Roles list |
CR41900 | SOL1566 | The Setup utility does not allow VLAN names with more than 12 characters |
CR41901 | SOL1643 | The bigpipe verify command does not detect misspelled monitor names or monitors that do not exist |
CR41904 | SOL1863 | When you attempt to print the snmpget help screen, the snmp_dca health monitor enters a loop |
CR41905 | SOL1864 | SNMP monitoring software reports an error when it attempts to query the ifRcvAddressAddress OID entry in the ifRcvAddressEntry table |
CR41913 | SOL2100 | The maximum value for 32-bit counters is 4,194,302 |
CR41915 | SOL3344 | SNMP statistics for the loopback interface are not collected |
CR41916 | SOL3344 | SNMP statistics for the loopback interface are not collected |
CR41918 | SOL3566 | When you restore the archived snmptrap.conf file after an upgrade, the BIG-IP system uses the previous version of the snmptrap.conf file |
CR41919 | SOL3657 | Available memory reported by the memAvailReal OID and the vmstat command differs |
CR41921 | SOL3775 | The BIG-IP system does not provide data for existing pool members in the PoolMemberEntry OID table |
CR41923 | SOL4024 | The Add Proxy pages do not work correctly with the Netscape Navigator browser |
CR41930 | SOL5080 | Gateway failsafe can cause a failover immediately after it is enabled |
CR41942 | SOL4407 | An unhelpful error message displays when you enter a header insert that is too long |
CR41985 | SOL5135 | BIG-IP may fail back to a previous failover state in a very specific and unusual configuration |
CR42010 | SOL5141 | Retransmissions from node to client may be dropped after packet loss between client and BIG-IP |
CR42057 | SOL497 | The bigpipe proxy show command may not display the correct values for current and max connections |
CR42114 | SOL5142 | Health monitors may attempt to use source ports that are already in use |
CR42119 | SOL5143 | Web aggregation may fail when a default SNAT automap is enabled |
CR42147 | SOL4717 | The BIG-IP system changes the interface media settings after you run the Setup utility |
CR42150 | SOL5144 | ZebOS routing may not work correctly when SSL proxy target virtual servers are bound to loopback |
CR42907 | SOL5023 | BIG-IP can run out of memory when loading very large configurations |
CR43900 | SOL4252 | The bigpipe pool command does not display SIP persistence records |
CR45017 | SOL5040 | The PVA will reconfigure itself if it detects duplicate SSL proxy addresses |
CR46405 | SOL4810 | BIG-IP and 3-DNS may report "date not found" during installation |
CR46407 | SOL4810 | BIG-IP and 3-DNS may report "date not found" during installation |
CR46509 | SOL4497 | Switch appliances do not send an SNMP trap when booting because the switch ports are disabled |
CR46515 | SOL5039 | The Configuration utility cannot successfully import FIPS keys |
CR46516 | SOL5039 | The Configuration utility cannot successfully import FIPS keys |
CR46624 | SOL5074 | BIG-IP ignores the first data packet when syn cookie processing is active |
CR46625 | SOL5074 | BIG-IP ignores the first data packet when syn cookie processing is active |
CR46706 | SOL5149 | BIG-IP will disable ARP for SNAT automap if ARP is disabled on a wildcard virtual server |
CR46975 | SOL4596 | iRules that contain a large number of decode_uri functions may fail |
CR46976 | SOL4596 | iRules that contain a large number of decode_uri functions may fail |
CR47153 | SOL4579 | Connection mirroring does not work on virtual servers that use cookie persistence |
CR47221 | SOL4575 | The BIG-IP system silently removes asterisks from auth model group names |
CR47235 | SOL4572 | The login.conf file might be overwritten during an upgrade |
CR47236 | SOL4572 | The login.conf file might be overwritten during an upgrade |
CR47276 | SOL4574 | The BIG-IP system and 3-DNS Controller do not prevent you from installing unsupported versions on older hardware |
CR47979 | SOL4665 | ICMP connections, including ICMP health checks, fail if you have configured an established rule |
CR48148 | SOL5040 | The PVA will reconfigure itself if it detects duplicate SSL proxy addresses |
CR48152 | SOL4809 | BIG-IP and 3-DNS are vulnerable to CAN-2005-1278, CAN-2005-1279, and CAN-2005-1280 |
CR48153 | SOL4809 | BIG-IP and 3-DNS are vulnerable to CAN-2005-1278, CAN-2005-1279, and CAN-2005-1280 |
CR48598 | SOL5052 | An SSL proxy will not attempt to reconnect to an LDAP server after failing three attempts |
CR48599 | SOL5052 | An SSL proxy will not attempt to reconnect to an LDAP server after failing three attempts |
CR48750 | SOL4853 | When running more than 400 SSL health monitors, the bigd process might run out of memory |
CR48759 | SOL4854 | Rule operations that match content fail if the text ends in a duplicated character followed by an underscore |
CR48761 | SOL4854 | Rule operations that match content fail if the text ends in a duplicated character followed by an underscore |
CR49272 | SOL4532 | The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0758, CAN-2005-0988, and CAN-2005-1228 |
CR49273 | SOL4532 | The BIG-IP system and 3-DNS Controller are vulnerable to CAN-2005-0758, CAN-2005-0988, and CAN-2005-1228 |
CR49295 | SOL5023 | BIG-IP can run out of memory when loading very large configurations |
CR49336 | SOL4616 | BIG-IP and 3-DNS are vulnerable to CAN-2005-0488 |
CR49337 | SOL4616 | BIG-IP and 3-DNS are vulnerable to CAN-2005-0488 |
CR49454 | SOL5070 | BIG-IP does not delete mirrored SSL session ID persistence records |
CR49455 | SOL5070 | BIG-IP does not delete mirrored SSL session ID persistence records |
CR49457 | SOL5045 | The active unit may crash after failover when mirroring is enabled |
CR49458 | SOL5045 | The active unit may crash after failover when mirroring is enabled |
CR49691 | SOL4326 | BIG-IP may panic when mirroring large numbers of SSL session ID persistence records |
CR49692 | SOL4326 | BIG-IP may panic when mirroring large numbers of SSL session ID persistence records |
CR49695 | SOL5069 | The SNMP daemon may become unresponsive or crash when sending data |
CR49696 | SOL5069 | The SNMP daemon may become unresponsive or crash when sending data |
CR49773 | SOL5083 | Connections may not be rebound to a new node after all nodes became unavailable |
CR49774 | SOL5083 | Connections may not be rebound to a new node after all nodes became unavailable |
CR50382 | SOL4331 | BIG-IP may send a reset to the wrong VLAN when a rule results in a discard statement |
CR50383 | SOL4331 | BIG-IP may send a reset to the wrong VLAN when a rule results in a discard statement |
CR50387 | SOL4808 | NTLM authentication may fail when a site is accessed through a delayed binding virtual server |
CR50712 | SOL4808 | NTLM authentication may fail when a site is accessed through a delayed binding virtual server |
CR51441 | SOL144 | Internal, hidden interfaces might be displayed by bigpipe vlan fdb show command |
CR58321 | SOL6551 | Changes in US and Canada Daylight Saving Time |
N/A | SOL4001 | Aggregated connections sometimes fail, particularly when there is packet loss on the network |