<?xml version="1.0" encoding="UTF-8"?>

	
















































































<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
   <channel>
      <atom:link href="http://support.f5.com/kb/en-us/recentadditions.rss.xml" rel="self" type="application/rss+xml"/>
      <title>AskF5 Knowledge Base - Recent Additions and Updates</title>
      <link>http://support.f5.com/kb/en-us/recentadditions.rss.xml</link>
      <description>Whether you have a specific technical question about an F5 product or you simply want general information about F5 solutions and services, the Ask F5 online database has the answer. Our RSS feeds are updated daily. Shown below are the last 30 days worth of results.</description>
      <language>en-us</language>
      <copyright>Copyright 1998-2008 F5 Networks, Inc. All rights reserved.</copyright>
      <pubDate>Thu, 20 Nov 2008 00:00:00 -0800</pubDate>
      <lastBuildDate>Thu, 20 Nov 2008 00:00:00 -0800</lastBuildDate>
      <generator>XML::RSS</generator>
      <ttl>1440</ttl>
      <image>
         <url>http://support.f5.com/images/assets/f5logo_ball.gif</url>
         <title>AskF5 Knowledge Base - Recent Additions and Updates</title>
         <link>http://support.f5.com/kb/en-us/recentadditions.rss.xml</link>
         <height>74</height>
         <width>74</width>
         <description>The Ask F5 Knowledge Base</description>
      </image>
      <item>
         <title>Known Issue: Snapshot consistency is enforced indeterminately</title>
         <description>(SOL9417)  The snapshot consistency feature is not consistently and uniformly enforced across all virtual servers.&#13;
&#13;
When the same volume is exported by more than one virtual server, consistency is only enforced via one of the virtual servers. In addition, when multiple snapshots begin simultaneously on the same snapshot schedule, only one of the virtual servers will enforce consistency.&#13;
&#13;
F5 Networks Product Development is tracking this issue as ARX ID 32297.&#13;
&#13;
 Workaround&#13;
&#13;
There is no workaround at</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9417.html?ref=rss</link>
         <pubDate>Thu, 20 Nov 2008 15:54:30 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9417.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: The Firefox browser crashes for Power Mac users when the Check Files (Mac OSX) prelogon sequence rule is applied</title>
         <description>(SOL9409)  If the prelogon sequence rule Check Files (MacOSX) is applied, Power Mac users using Firefox will experience a crash of their browser. If Firefox does not crash immediately, it will hang indefinitely. This behavior is the result of an issue with the InspectionHost plugin. As an immediate workaround, users can use an alternate browser, such as Safari.&#13;
&#13;
F5 Networks Product Development is tracking this issue as CR89277. This issue does not exist in FirePass version 6.0.3.&#13;
&#13;
Additionally, this i</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9409.html?ref=rss</link>
         <pubDate>Thu, 20 Nov 2008 10:55:53 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9409.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Firefox 3 does not pass session cookies to Java-based applets</title>
         <description>(SOL9436) Firefox 3 does not pass session cookies to Java-based applets when the Firefox Accept 3rd party cookies option is not selected. &#13;
&#13;
Mozilla is tracking this issue as Bug 441166. &#13;
&#13;
Note: For more information, refer to the following website:&#13;
&#13;
https://bugzilla.mozilla.org/show_bug.cgi?id441166&#13;
&#13;
When the Accept 3rd party cookies option is not selected, FirePass Java applets that require maintaining session state, such as Application Tunnels, will fail. &#13;
&#13;
Note: For more information about conf</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9436.html?ref=rss</link>
         <pubDate>Thu, 20 Nov 2008 10:55:47 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9436.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: Users cannot change their Windows domain passwords on the Tools: Account Details page</title>
         <description>(SOL9431)  If a user logs on to the FirePass webtop using the following format for the FirePass username, where &amp;lt;DOMAIN&amp;gt; is the Windows domain name and &amp;lt;username&amp;gt; is the Windows username, the user cannot change the Windows password on the Tools: Account Details page.&#13;
&#13;
For example:&#13;
&amp;lt;DOMAIN&amp;gt;\&amp;lt;username&amp;gt;&#13;
&#13;
If the user attempts to change the password, FirePass reports the following error message:&#13;
&#13;
Current password is not correct.&#13;
&#13;
F5 Networks Product Development is tracking this</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9431.html?ref=rss</link>
         <pubDate>Thu, 20 Nov 2008 10:55:46 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9431.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: The FirePass Administrative Console incorrectly displays the SNMPv3 informs field as SNMPv2 informs</title>
         <description>(SOL9426)  On the Device Management: Configuration: SNMP page in the Hosts section, the FirePass Administrative Console incorrectly displays theSNMPv3 informs field as SNMPv2 informs. This issue is cosmetic, and does not affect the functionality of the feature. If you need to configure one or more SNMPv3 trap hosts, enter that information in the SNMPv2 informs field.&#13;
F5 Networks Product Development is tracking this issue as CR111307.</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9426.html?ref=rss</link>
         <pubDate>Thu, 20 Nov 2008 10:55:44 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9426.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: Virtual snapshots of multiple EMC volumes may time out and fail</title>
         <description>(SOL9430)  Virtual snapshots may time out if multiplemanaged volumes are snapshot on the same schedule, and the correspondingphysical volumes are on an EMC filer. Becausean EMC filer requiressnapshots to perform one at a time, the ARX system mustsnapshot each physical volume sequentially. The time required to complete these serial physical snapshots can exceed the time configured for the managed volume snapshot.&#13;
F5 Networks Product Development is tracking this issue as ARX ID 32330.&#13;
Workaround&#13;
You can </description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9430.html?ref=rss</link>
         <pubDate>Thu, 20 Nov 2008 08:27:46 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9430.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Change in Behavior: Persistent connections are load balanced when the pool member in a persistent session becomes unavailable</title>
         <description>(SOL6844) In BIG-IP versions prior to 9.0, persistent connections are sent to the next available pool member in the configuration when the pool member in a persistent session becomes unavailable.&#13;
Beginning in BIG-IP LTM version 9.0, persistent connections are load balanced using the pool load balancing method when the pool member in a persistent session becomes unavailable.</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/6000/800/sol6844.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 16:37:51 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/6000/800/sol6844.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Configuring an HTTP profile to rewrite URLs so that redirects from an HTTP server specify the HTTPS protocol</title>
         <description>(SOL6912) A ClientSSL virtual server is typically configured to accept HTTPS connections from a client, decrypt the SSL session, and send the unencrypted HTTP request to the web server. &#13;
When a requested URI does not include a trailing slash (a forward slash, such as /, at the end of the URI), some web servers generate a courtesy redirect. Without a trailing slash, the web server will first treat the resource specified in the URI as a file. If the file cannot be found, the web server may search for a dir</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/6000/900/sol6912.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 16:37:04 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/6000/900/sol6912.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Configuring the BIG-IP to use an intermediate or chain certificate with a client SSL profile</title>
         <description>(SOL6401) In order to use the intermediate certificate with BIG-IP version 9.x, you must perform the following two procedures:&#13;
&#13;
    Import the intermediate certificate to the BIG-IP system &#13;
    Configure an SSL client profile to use the intermediate certificate &#13;
&#13;
Note: Intermediate certificates or chain certificates are obtained from the vendor of the certificate. For example, the Verisign intermediate certificate is available at the following location: http://www.verisign.com/support/verisign-interm</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/6000/400/sol6401.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 16:35:26 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/6000/400/sol6401.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Configuring the FirePass controller to use different servers for authentication and Dynamic Group Mapping</title>
         <description>(SOL7549) You can configure the FirePass controller to use different servers for authentication and Dynamic Group Mapping. For example, if you want to use two-factor authentication with RSA SecurID and your group hierarchy is stored in Active Directory, set the authentication method for your Master Groups to RSA SecurID Authentication. Then, configure Dynamic Group Mapping to use your Active Directory server to dynamically assign master groups and resource groups at user log on.&#13;
Note: For more informatio</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/7000/500/sol7549.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 16:33:29 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/7000/500/sol7549.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Transferring files to or from an F5 Networks system</title>
         <description>(SOL175) The following three options are available for transferring files between F5 devices:&#13;
&#13;
&#13;
    Secure Copy (SCP)&#13;
    File Transfer Protocol (FTP)&#13;
    Secure HTTP (HTTPS)&#13;
&#13;
SCP&#13;
Secure Copy (SCP) is the preferred means of transferring files to or from an F5 device. SCP securely transfers files between hosts using the Secure Shell (SSH) protocol for authentication and encryption. Unlike FTP, SCP file transfers preserve the original datestamp on the file. You can use SCP to transfer files to or f</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/0000/100/sol175.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 15:16:07 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/0000/100/sol175.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Installing a UCS file containing an encrypted passphrase</title>
         <description>(SOL9420) Beginning in BIG-IP LTM version 9.4.5, passphrases for SSL private keys are stored in the configuration file in encrypted form. The BIG-IP system uses a hardware-key encrypted master SSL key to encrypt and decrypt SSL key passphrases in the configuration file.&#13;
&#13;
Note: For more information about encrypted passphrases in SSL profiles, refer to the BIG-IP LTM version 9.4.5 Release Notes.&#13;
&#13;
Important: Passphrase encryption is not a configurable option, and once encrypted, passphrases can only be d</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9420.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 14:09:52 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9420.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: A BIGpipe: self IP address deletion error message occurs when deleting one of two non-floating self IP addresses</title>
         <description>(SOL9398) When two non-floating self IP addresses are defined on the same VLAN, deleting one of them may fail with the following erroneous error message:&#13;
&#13;
BIGpipe: self IP address deletion error: 01070393:3: Cannot delete IP 172.16.0.2 because it would leave a floating IP with no non-floating IP on this network.&#13;
&#13;
F5 Networks Product Development is tracking this issue as CR109058 for the BIG-IP LTM 9.3. branch.&#13;
&#13;
Workaround&#13;
&#13;
You can work around this issue by removing the non-floating self IP address</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/300/sol9398.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 14:09:45 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/300/sol9398.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: BIG-IP support for multicast traffic</title>
         <description>(SOL9310) Multicast traffic overview&#13;
L2 multicast addressing&#13;
L3 multicast addressing&#13;
L2 multicast (multicast bridging)&#13;
BIG-IP LTM as a multicast bridge&#13;
Accepting frames with L2 multicast source address&#13;
Multicast traffic and VLAN groups&#13;
L3 multicast (multicast forwarding &amp;amp; routing)&#13;
BIG-IP LTM as a multicast router&#13;
BIG-IP LTM as a multicast node&#13;
&#13;
Multicast traffic overview&#13;
As opposed to unicast, where a packet is sent to a single host, or broadcast, whe</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/300/sol9310.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 14:00:39 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/300/sol9310.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: Configuring more than 16 managed volumes for snapshots using the same schedule may result in an incomplete snapshot</title>
         <description>(SOL9421)  Configuring snapshotsfor more than 16managed volumes using the same schedule may result in an incomplete snapshot.&#13;
Important: This issue only affects snapshots scheduled for an EMC filer.&#13;
For example, if you have configured snapshots for 50 managed volumes using the same schedule, the following sequence of events will occur:&#13;
&#13;
    At the scheduled time, the schedulerstarts creating snapshot requests for each managed volume.&#13;
    TheAfnSnapd process begins processing the requests and attempts</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9421.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 13:28:53 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9421.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: Command line login fails when the local user name is longer than 32 characters</title>
         <description>(SOL9411)  The BIG-IP system allows you to create a local user account with a username containing 33 characters or more. When you attempt to log on to the BIG-IP system with the username using the serial console or SSH, the system generatesone of the following twoparsing error messages:&#13;
&#13;
 Serial console &#13;
&#13;
BIGpipe parsing error:&#13;
 01070827:3: User login disallowed: User&#13;
(user_name_longer_than_33_characters) is not an administrator, does not have a UID of zero, and has not been assigned a role on a par</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9411.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 11:41:56 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9411.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Enabling and disabling PDF linearization on the BIG-IP WebAccelerator</title>
         <description>(SOL9408) With the default BIG-IP WebAccelerator configuration, PDFlinearization cannot be disabled using an accelerationpolicy because the globalfragment.xml file's default objType definition for PDF filescontains the transformFile&amp;quot;pdf.code&amp;quot; entry. The globalfragment.xml file's transformFile entrywill override any Response Rewriting configurations made in theassembly rules of an acceleration policy.&#13;
To globally disable PDF linearization, and selectively enable PDF linearization, perform the fo</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9408.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 11:34:58 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9408.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Overview of BIG-IP version 9.6.1 HF2</title>
         <description>(SOL9327) F5 Networks has recently discovered and corrected a number of critical issues that affect customers running BIG-IP version 9.6.1. F5 Networks recommends that all customers currently running version 9.6.1 install Hotfix-BIGIP-v9.6.1-HF2, or a later version of the cumulatave hotfix rollup, as soon as possible.&#13;
&#13;
The following CRs are fixed in HF2 for BIG-IP version 9.6.1:&#13;
&#13;
    &#13;
        &#13;
            CR Number&#13;
            Solution Number&#13;
            Description&#13;
        &#13;
        &#13;
          </description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/300/sol9327.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 11:29:37 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/300/sol9327.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: Certain mirrored connections are aborted on the standby system</title>
         <description>(SOL9428)  Connection mirroring is used on the BIG-IP system to duplicate a unit's state information to the peer unit. When a client requests an HTTP Keep-Alive session, and the server does not support HTTP Keep-Alive connections, mirrored connections may be aborted on the standby system . This issue occurs when the virtual server properties are configured as follows:&#13;
&#13;
    Connection mirroring is configured for the virtual server&#13;
    HTTP and OneConnect profiles are defined for the virtual server&#13;
    </description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9428.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 11:27:42 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9428.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: Using SSL::disable followed by SSL::enable in an iRule can cause TMM to crash</title>
         <description>(SOL9419)  When an iRule calls the SSL::disable command to disable SSL processing in the CLIENT_ACCEPTED iRule event, and then calls the SSL::enable command to re-enable SSL processing for the connection in the CLIENT_DATA event, TMM may crash and generate an SIGSEGV core file.&#13;
&#13;
F5 Networks Product Development is tracking this issue as CR110962.</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9419.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 11:24:37 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9419.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: TMM does not limit the rate of resets sent for connection timeouts for various connection profiles</title>
         <description>(SOL9418)  TMM does not limit the rate of resets sent for connection timeouts for various connection profiles.&#13;
&#13;
When a TCP, FastL4 or FastHTTP connection times out, TMM sends a reset that is used to clean up and close the server and client connections. The resets initiated by TMM are not rate-limited. Under high connection loads with a large number of connections being reset, the transmit queue may overflow. As a result, extra resources may be consumed in high load with low memory conditions, leading to</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9418.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 11:22:50 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9418.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: Policy Builder does not remove the internal logging profile</title>
         <description>(SOL9414)  The Policy Builder does not remove the internal logging profile after it has been run on a Web Application. This behavior may result in certain types of requestsbeing unintentionally logged. &#13;
&#13;
For example, ifthe Web Application logging profile is configured to log all requests, then all requests are logged. If theprofile is configured to log only illegal requests, some legal requests may be logged based on the internal logging profile.&#13;
&#13;
Note: This behavior does not block traffic.&#13;
&#13;
F5 Netw</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9414.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 09:58:23 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9414.html?ref=rss</guid>
      </item>
      <item>
         <title>Solution: Overview of the Always-On Management (AOM) subsystem</title>
         <description>(SOL9403) Note: This Solution applies to the 1600 and 3600 BIG-IP platforms, which contain the AOM subsystem.&#13;
The Always-On Management (AOM) is a separate subsystem that provides lights-out management for the BIG-IP system using the 10/100/1000 Ethernet management portover SSH, or using the serial console.&#13;
AOM features&#13;
&#13;
    The AOM allows you to manage BIG-IP platforms using SSH or the serial console, even if the platform&amp;rsquo;s main power supply is turned off.&#13;
    The BIG-IP host system and the AOM</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9403.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 09:55:44 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9403.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: The management port media settings on the 1600 and 3600 platforms are not configurable</title>
         <description>(SOL9402)  The 1600 and 3600 platforms contain a 10/100/1000 ethernet management port, which provides access to the BIG-IP system and the Always-On Management (AOM) subsystem. The default media setting for the management port is auto. It is not currently possible to set the media type of the management port to a value other than auto.&#13;
&#13;
F5 Networks Product Development is tracking this issue as CR109786.</description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9402.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 08:17:54 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9402.html?ref=rss</guid>
      </item>
      <item>
         <title>Known Issue: DC power supplies turn off if no blades are installed in a VIPRION chassis</title>
         <description>(SOL9410)  If a VIPRION chassis is operating using DC power supplies and all blades are removed, one orboth of the DC power supplies may turn off. The power supply will remain off until at least one blade is installed and the affected power supply is reset.&#13;
F5 Networks Product Development is tracking this issue as CR100545.&#13;
&#13;
To reset the offline power supply, perform the following procedure:&#13;
&#13;
    Install at least one blade into the chassis.&#13;
    Remove the affected DC power supply.&#13;
    &#13;
    Wait a </description>
         <link>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9410.html?ref=rss</link>
         <pubDate>Wed, 19 Nov 2008 07:59:35 -0800</pubDate>
         <guid>https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9410.html?ref=rss</guid>
      </item>
   </channel>
</rss>
