網頁

2009年8月5日 星期三

2009.8.5 台語俗語[阿婆踉港]意思與典故

阿婆踉港這俗語不陌生, 但由來一直不曉得. 一直到昨晚看一台節目, 主持人就解釋了阿婆踉港的由來. 今早起床後,忘記了由來的前半段,只記得後半段, 於是Google又發揮了價值, 把來由找出來了.
以下文來自於儒林戲語部落格

『阿婆踉港』這句俗語，為什麼說是最[正港]的台灣話呢？這是有歷史典故的。中日甲午戰爭滿清戰敗，1895年簽訂[馬關條約]將台灣割讓給日本，日軍由台北澳底登陸，由前清官出任的「台灣民主國」總統唐景松卻不戰而逃，以喬裝老太婆從滬尾港[今淡水港]，潛逃回大陸。留下台灣義勇軍與日軍做殊死激戰，戰死的台灣義勇軍，估計達一萬四千人以上。因此才有這句『阿婆踉港』俗語產生。形容見情勢不對有狀況時，自己先開溜，趕快逃跑的意思。因此，[跤踏台灣地，頭戴台灣天]的台灣人，要知道這段悲慘的台灣史。
張貼者： 於 沒有留言:
標籤：

SOL7727: A service check date that is earlier than the license check date now requires you to relicense the system before upgrading

SOL7727: A service check date that is earlier than the license check date now requires you to relicense the system before upgrading

Updated: 6/16/09 11:08 AM
Solution

Beginning with BIG-IP version 9.2 and Enterprise Manager version 1.2, a license check date in the software is verified against the service check date in the license file.

License Check Date

The license check date is a static date built into the software for BIG-IP products versions 9.2 and later.

The following table contains the license check date for BIG-IP versions 9.2 and later, and Enterprise Manager versions 1.2 and later:

Product Version License Check Date
Enterprise Manager 1.2.0 2005-08-24
Enterprise Manager 1.2.1 2006-10-02
Enterprise Manager 1.2.1 2006-08-18
Enterprise Manager 1.2.2 2006-08-18
Enterprise Manager 1.4 2006-08-18
Enterprise Manager 1.4.1 2007-08-18
Enterprise Manager 1.6.0 2007-08-18
Enterprise Manager 1.7.0 2006-10-02
BIG-IP 9.2 - 9.2.5 2005-08-24
BIG-IP 9.3.0 2007-03-23
BIG-IP 9.3.1 2007-10-09
BIG-IP 9.4 - 9.4.1 2006-10-02
BIG-IP 9.4.2 - 9.4.3 2007-09-18
BIG-IP 9.4.4 2007-12-07
BIG-IP 9.4.5 2008-05-01
BIG-IP 9.4.6 - 9.4.7 2008-09-15
BIG-IP 9.6.0 - 9.6.1 2007-12-05
BIG-IP 10.0.0 2009-01-02
BIG-IP 10.0.1 2009-04-24

Note: For information about an early build of Enterprise Manager version 1.2.1 that contained an incorrect license check date, refer to SOL7613: Enterprise Manager systems licensed prior to October 2, 2006 require relicensing after an upgrade to version 1.2.1.

Service Check Date

The service check date is located in the BIG-IP license and is the same as the date the license was last activated or the date the service contract for the device expires, whichever is earlier. For example, if you have an active service contract that ends on December 31, and you license a device on June 30, the service check date is set to June 30.

Note: The service check date in the BIG-IP license is updated each time the license is reactivated.

Enforcement during an upgrade

When you upgrade a system, the install script will verify the service check date with the license check date of the version being installed. If the service check date is missing or it is earlier than the license check date, the upgrade will not continue, and an error message similar to the following example is displayed:

An active service contract is required for the software you are attempting
to install. The license found for  
does not contain a valid service check date for this software release.
If you have a current service contract, please re-activate your product
license and resume installation. If you do not have an active service
contract, please contact F5 Sales. Cannot proceed with changes to this
product image.

Enforcement during system startup

The license check date enforcement also applies during system startup. The system compares the license check date to the service check date in the license file. If the service check date is earlier than the license check date, the system will initialize but the configuration will not be loaded. To allow the configuration to load, you must update the service check date in the license file by re-activating the system's license.

Important: For devices managed with Enterprise Manager version 1.4 and later, the Enterprise Manager will verify the license check date and the service check date before upgrading a managed system. If required, the Enterprise Manager will attempt to re-activate the system's license before performing the upgrade. For more information, refer to SOL7702: Upgrades using Enterprise Manager will verify service check date and attempt to reactivate system license if required.

Workaround

You can prevent upgrade issues by relicensing your system before performing the upgrade, or recovering a system that fails to initialize by relicensing your system after performing the upgrade. To do so, complete the following two procedures:

  • Verifying the service check date in your license
  • Reactivating the system's license

Verifying the service check date of your license

To verify the service check date in your system's license, perform the following procedure:

  1. Log in to the command line.
  2. Change directories to the /config directory, by typing the following command:

    cd /config
  3. Parse the bigip.license file for the Service check date, by typing the following command:

    grep "Service check date" bigip.license
  4. Referencing the table previously mentioned in this Solution, verify the Service check date listed is after the license check date listed for the version you are upgrading.

If the value in the Licensed Date field is earlier than the license check date, you must reactivate the system's license before upgrading.

Reactivating the system license

To reactivate a system's license, perform the following procedure:

  1. Log in to the Configuration utility.
  2. Click System.
  3. Click License.
  4. Click Reactivate.
  5. Select either the Automatic or Manual as the activation method.

    Note: If your system does not have internet access to the F5 Networks license server, you must select Manual.

  6. Click Next and follow the on-screen instructions.

Note: Be sure to log in as the admin user to re-license the system. For more information, refer to SOL9965: The admin user account must be used to license the system.

張貼者： 於 沒有留言:
標籤：

SOL4423: Overview of UCS archives

SOL4423: Overview of UCS archives

Updated: 9/24/08 2:17 PM
Solution

A UCS archive is a compressed file that contains all of the configuration files that are typically required to restore your current configuration to a new system. These files are:
  • All BIG-IP specific configuration files
  • BIG-IP product licenses
  • User accounts and password information
  • DNS zone files and ZoneRunner configuration
  • SSL certificates and keys

Important: In addition to user accounts, passwords, and critical system files, the UCS archive contains the SSL private keys that are used with your SSL proxies. You must store backup UCS archives in an environment that is as secure as where you store your private keys.

Note: For more information about the specific files that are contained in a UCS archive and instructions about how to modify those files, refer to SOL4422: Viewing and modifying the files that are configured for inclusion in a UCS archive.

Creating a UCS archive

You can create a UCS archive at any time using the Configuration utility or the command line.

Configuration utility

To create a UCS archive from the Configuration utility, perform the following steps:

  1. From the Configuration utility, click System.

  2. Click Archives.

    The Archives page displays.

  3. From the Archives page, click the Create button.

  4. In the File Name field, type a name for the file.

    Note: You can supply a path for the file, but if you do, the file will not appear in the Archive List. Only files stored in the default UCS path, /var/local/ucs, will appear in the Archive List.

  5. Select Enabled from the Encryption dropdown menu only if you want to encrypt the UCS archive file.

    Note: If you enable encryption, you will need to type a passphrase for the encrypted UCS archive file. This passphrase will be required in order to restore using the encrypted UCS archive.

  6. Click the Finished button.

    A status screen displays.

  7. Click the OK button.

Command line

To create a UCS archive from the command line, use the following command syntax:

bigpipe config save

Replace with the name you want to give the archive. If you include a path, the file will be saved to that location. If you do not include a path, the file will be saved to the default path, /var/local/ucs.

To create an encrypted UCS archive from the command line, use the following command syntax:

bigpipe config save passsphrase

Replace with the name you want to give the archive. If you include a path, the file will be saved to that location. If you do not include a path, the file will be saved to the default path, /var/local/ucs.

Replace with the password you want to give the archive.

Restoring a configuration from a UCS archive

You can restore a configuration that is contained in a UCS archive using the Configuration utility or the command line.

Configuration utility

To restore a configuration in a UCS archive using the Configuration utility, perform the following steps:

  1. From the Configuration utility, click System.

  2. Click Archives.

    The Archives page displays.

  3. From the Archive List, click the name of the UCS archive from which you want to restore.

    Note: If the UCS archive is encrypted, you will need to type the passphrase for the encrypted UCS archive file in the Restore Passphrase field.

  4. Click the Restore button.

    A status screen displays.

  5. Click the OK button.

Command line

To restore a configuration in a UCS archive from the command line, use the following command syntax:

bigpipe config install

Replace with the name of the archive. If the file is not contained in the default path or the directory from which you are working, you must also specify the path.

Note: If the UCS archive file specified was encrypted, you will be prompted to enter the passphrase for the archive file.

For more information about backing up and restoring your configuration using a UCS archive, see SOL3499: Backing up and restoring BIG-IP LTM, GTM, Link Controller, or ASM configuration files..

Viewing the UCS archive content

Note: For encrypted UCS archive files, refer to SOL8465: Viewing and extracting the contents of an ecrypted UCS archive file.

To view the files that are saved in a UCS archive, use the following command syntax:

tar -ztf

Replace with the name of the UCS archive.

This will provide a list of all the files included in the UCS archive.

Extracting files from the UCS archive

Note: For encrypted UCS archive files, refer to SOL8465: Viewing and extracting the contents of an ecrypted UCS archive file.

You can extract the files from a UCS archive without overwriting your existing configuration by using one of the following processes:

  • Extract all UCS archive files
  • Extract a single UCS archive file

Extracting all UCS archive files

To extract all files from a UCS archive, perform the following steps:

  1. Create a new directory within the /var/tmp directory, using the following command syntax:

    mkdir /var/tmp/

    Replace with a name of your choice.

  2. Copy the UCS archive into the new directory using the following command syntax:

    cp /var/tmp//

    Replace with the name of the UCS archive from which you want to extract files and with the name of the directory that you created in step 1.

  3. Change directories to the new directory using the following command syntax:

    cd /var/tmp/

    Replace with the name of the directory that you created in step 1.

  4. Extract the files from the UCS archive using the following command syntax:

    tar -zxf

    Replace with the name of the UCS archive.

    This command will extract the files and put them in the current directory. It will create subdirectories to match the directories in which the configuration files are normally stored. For example, a config directory will be created and will contain all the files that are normally contained in the /config directory.

Extracting a single UCS archive file

To extract a single file from a UCS archive, perform the following steps:

  1. Create a new directory within the /var/tmp directory using the following command syntax:

    mkdir /var/tmp/

    Replace with a name of your choice.

  2. Copy the UCS archive into the new directory using the following command syntax:

    cp /var/tmp//

    Replace with the name of the UCS archive from which you want to extract files and with the name of the directory that you created in step 1.

  3. Change directories to the new directory using the following command syntax:

    cd /var/tmp/

    Replace with the name of the directory that you created in step 1.

  4. Extract the desired file from the UCS archive, using the following command syntax:

    tar -zxf

    Replace:

    • with the name of the UCS archive

    • with the relative path and name of the file that you want to extract from the UCS archive

    For example, to retrieve the file bigip.conf you must specify the config directory, but not the root directory.

    For example:

    tar -zxf myconfig.ucs config/bigip.conf

    This command will extract the files and put them in the current directory. It will create a subdirectory to match the directory in which the configuration file is normally stored. For example, if you extract config/bigip.conf, a config directory will be created.

Viewing the contents of a file contained in a UCS archive

Note: For encrypted UCS archive files, refer to SOL8465: Viewing and extracting the contents of an ecrypted UCS archive file.

To view a single file from a UCS archive on a terminal screen (standard output), perform the following steps:

  1. Change directories to the directory that contains the UCS archive using the following command syntax:

    cd

    Replace with the name of the directory where the UCS achive is located.

    Extract the desired file from the UCS archive to standard output using the following command syntax:

    Note: The third character in the flags list is a capital letter "O".

    tar -zxOf

    Replace:

    • with the name of the UCS archive

    • with the relative pathe and name of the file that you want to extract from the UCS archive

    For example, to view the file bigip.conf you must specify the config directory, but not the root directory, as follows:

    tar -zxOf myconfig.ucs config/bigip.conf

    Note: It is possible to use wildcards, for example config/bigip.*, to display multiple files from an archive.

    Warning: Some files contained in a UCS archive are binary files which will not display correctly to standard output.

張貼者： 於 沒有留言:
標籤：

SOL10245: BIG-IP UCS installation and licensing behavior

SOL10245: BIG-IP UCS installation and licensing behavior

Updated: 7/30/09 2:23 PM
Solution

A user configuration set (UCS) is an archive of configuration files contained on a BIG-IP system, including the system license.

Note: For more information about the contents of a UCS file, refer to SOL4423: Overview of UCS archives.

When you use the bigpipe config save command to save the BIG-IP system configuration to a UCS file, the system also saves the existing license to the UCS file. When you use the bigpipe config install command to restore the UCS file on the BIG-IP system, the UCS installer uses the following logic to determine whether to install the license from the UCS file, or retain the system's existing license file:

  • The license file is only installed when the hostname in the UCS file matches the system hostname
  • If there is no /config/bigip.license on the system, the license from the UCS file is installed to the system
  • If there is a /config/bigip.license on the system, the BIG-IP system performs the following checks to determine whether to install the license from the UCS, or retain the system's existing license file:

    • If neither license is time limited (neither license file contains a License end date), the BIG-IP system uses the LATEST_ONE.

      Note: For more information, refer to the following LATEST_ONE section.
    • If both licenses are time limited (both license files contain a License end date), the BIG-IP system uses the license that expires last. If the time limited date is the same, the BIG-IP system uses the LATEST_ONE.

      Note: For more information, refer to the following LATEST_ONE section.
    • If one license is time limited:
      • If the license has expired, use the other license
      • If the license is still valid, use the LATEST_ONE

LATEST_ONE

Select the service check date in both bigip.license files for the following conditions:

  • If only one license contains a service check date, use that license
  • If both licenses contain a service check date, use the license with latest service check date
  • If the service check dates match or do not exist, use the license check date for comparison, and use the license with latest license check date

Note: For more information about the license check date, refer to SOL7727: A service check date that is earlier than the license check date now requires you to relicense the system before upgrading.

Note: For more information about saving and restoring BIG-IP configurations, refer to SOL3499: Backing up and restoring BIG-IP LTM, ASM, GTM, Link Controller, or WebAccelerator configuration files.

張貼者： 於 沒有留言:
標籤：

Ask F5 - Added and updated documents from 7/26 through 8/01

*Top 10 Solutions for July*

1. SOL8035: Overview of BIG-IP daemons https://support.f5.com/kb/en-us/solutions/public/8000/000/sol8035.html

2. SOL5527: Configuring the BIG-IP system to log to a remote syslog server https://support.f5.com/kb/en-us/solutions/public/5000/500/sol5527.html

3. SOL3499: Backing up and restoring BIG-IP LTM, ASM, GTM, Link Controller, or WebAccelerator configuration files https://support.f5.com/kb/en-us/solutions/public/3000/400/sol3499.html

4. SOL3667: Configuring SNMP trap alerts to send email notifications https://support.f5.com/kb/en-us/solutions/public/3000/600/sol3667.html

5. SOL7024: Overview of the configsync process https://support.f5.com/kb/en-us/solutions/public/7000/000/sol7024.html

6. SOL2486: Providing files to F5 Networks Technical Support https://support.f5.com/kb/en-us/solutions/public/2000/400/sol2486.html

7. SOL4707: Choosing a profile for HTTP traffic https://support.f5.com/kb/en-us/solutions/public/4000/700/sol4707.html

8. SOL9447: Choosing an installation method https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9447.html

9. SOL7595: Overview of IP forwarding virtual servers https://support.f5.com/kb/en-us/solutions/public/7000/500/sol7595.html

10. SOL3350: Changing account passwords for the command line and Configuration utility https://support.f5.com/kb/en-us/solutions/public/3000/300/sol3350.html

*FirePass hotfix released*

FirePass has releases cumulative HF-602-11 for FirePass version 6.0.2. For more information, refer to the following location:

F5 Networks Downloads site:

https://downloads.f5.com/esd/product.jsp?sw=FirePass&pro=firepass_v5.x&fromArchive=1&prodesc=FirePass&ver=6.0.2

*Added and updated documents from 7/26 through 8/01*

BIG-IP - New
SOL10366: BIND vulnerability - CVE-2009-0696 https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10366.html

SOL10352: Qkview may not collect all necessary BIG-IP WebAccelerator log files https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10352.html

SOL10350: Deleting the dynamic parameter does not delete the corresponding extraction object https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10350.html

SOL10348: A large client-side TCP window scale factor may cause data re-segmentation https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10348.html

SOL10347: LACP trunk may be created with actor key value set to 0 https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10347.html

SOL10344: The BIG-IP GTM system logs an error message for a default gateway pool in another datacenter https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10344.html

SOL10343: A virtual server configured with a FastL4 profile and no available pool members will not send a reset packet https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10343.html

SOL10340: A BIG-IP GTM user with the Operator role cannot enable or disable BIG-IP GTM pool members https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10340.html

SOL10338: The command prompt changes to ?Active? after loading larger BIG-IP GTM configurations https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10338.html

SOL10337: Simultaneously changing the BIG-IP GTM monitor's timeout and interval values results in the host status changing to a down state https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10337.html

SOL10336: The pvad process may crash when attempting to add a pool and node at the same time https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10336.html

SOL10334: The BIG-IP GTM object status changes may not immediately reflect in the Configuration utility https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10334.html

SOL10332: Remote syslog entries are not correctly imported during an upgrade https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10332.html

SOL10331: Configuring the big3d agent to listen on all self IP addresses on a VLAN https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10331.html

SOL10321: The BIG-IP system sends duplicate traps when Agent Authentication is enabled https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10321.html

SOL10319: Using the tcpdump utility disables hardware checksum offloading https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10319.html

SOL10318: Cache-Control headers may still be modified when the client cache policy is set to 'Do not change'
https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10318.html

SOL10312: Events contained in a UCS archive may cause configsync operations to fail https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10312.html

SOL10296: Error Message: The vlan for self IP must be one of the vlans in the associated route-domain https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10296.html

SOL10281: The persist none iRule command does not disable cookie persistence for the connection when used with the LB::reselect command https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10281.html

SOL10245: BIG-IP UCS installation and licensing behavior https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10245.html

BIG-IP - Updated
SOL10288: Supported product module combinations by platform https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10288.html

SOL10258: ZebOS integration changes starting in BIG-IP version 9.4.4 https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10258.html

SOL10167: Overview of the ClientSSL profile https://support.f5.com/kb/en-us/solutions/public/10000/100/sol10167.html

SOL10111: The BIG-IP WebAccelerator corrupts the Cache-Control header under certain conditions https://support.f5.com/kb/en-us/solutions/public/10000/100/sol10111.html

SOL10025: Managing F5 Networks product hotfixes for BIG-IP version 10.x systems https://support.f5.com/kb/en-us/solutions/public/10000/000/sol10025.html

SOL9858: Deleting a node address using iControl may cause pvad to core https://support.f5.com/kb/en-us/solutions/public/9000/800/sol9858.html

SOL9812: Overview of BIG-IP TCP RST behavior https://support.f5.com/kb/en-us/solutions/public/9000/800/sol9812.html

SOL9476: The F5 Networks hardware / software compatibility matrix https://support.f5.com/kb/en-us/solutions/public/9000/400/sol9476.html

SOL9143: The Linux IP routing policy rule for route lookups on the management port is missing https://support.f5.com/kb/en-us/solutions/public/9000/100/sol9143.html

SOL9085: The BIG-IP GTM uses an internal database to provide geolocation maps for topology load balancing https://support.f5.com/kb/en-us/solutions/public/9000/000/sol9085.html

SOL8994: The BIG-IP GTM HTTP monitor fails when the server response uses HTTP Keep-Alive headers https://support.f5.com/kb/en-us/solutions/public/8000/900/sol8994.html

SOL8989: The SSL certificate expiration date is displayed incorrectly in the Configuration utility https://support.f5.com/kb/en-us/solutions/public/8000/900/sol8989.html

SOL8968: Enabling persistence for a virtual server bypasses load balancing https://support.f5.com/kb/en-us/solutions/public/8000/900/sol8968.html

SOL8966: A corrupt MySQL password prevents the Configuration utility from loading https://support.f5.com/kb/en-us/solutions/public/8000/900/sol8966.html\

SOL8940: The BIG-IP system processes traffic for virtual servers after disabling the virtual address https://support.f5.com/kb/en-us/solutions/public/8000/900/sol8940.html

SOL8928: VIPRION compression licensing levels https://support.f5.com/kb/en-us/solutions/public/8000/900/sol8928.html

SOL8927: The BIG-IP system fails to send a TCP window update when interacting with certain TCP/IP stacks https://support.f5.com/kb/en-us/solutions/public/8000/900/sol8927.html

SOL8517: Enabling attack signatures that were not triggered during the staging process https://support.f5.com/kb/en-us/solutions/public/8000/500/sol8517.html

SOL8439: Configuring local host name resolution for BIG-IP version 9.4.2 and later https://support.f5.com/kb/en-us/solutions/public/8000/400/sol8439.html

SOL8254: Support for the OSPF routing protocol in BIG-IP LTM high availability pairs https://support.f5.com/kb/en-us/solutions/public/8000/200/sol8254.html

SOL7922: Overview of BIG-IP ASM HTTP response code filtering https://support.f5.com/kb/en-us/solutions/public/7000/900/sol7922.html

SOL7747: SSL Transactions performance graph and TPS licensing rate limit reached log messages https://support.f5.com/kb/en-us/solutions/public/7000/700/sol7747.html

SOL7233: Change in Behavior: The BIG-IP ASM UCS no longer contains Forensic and Events data https://support.f5.com/kb/en-us/solutions/public/7000/200/sol7233.html

SOL7225: Overview of the BIG-IP LTM mirroring transport protocol https://support.f5.com/kb/en-us/solutions/public/7000/200/sol7225.html

SOL7222: Overview of connection and persistence mirroring https://support.f5.com/kb/en-us/solutions/public/7000/200/sol7222.html

SOL6768: Restricting Configuration utility access to SSL clients that are 128 bits or higher https://support.f5.com/kb/en-us/solutions/public/6000/700/sol6768.html

SOL6767: Overview of the BIG-IP LTM SSL session cache https://support.f5.com/kb/en-us/solutions/public/6000/700/sol6767.html

SOL6475: Error message: 'SSL transaction (TPS) rate limit reached' or 'no SSL TPS or run out'
https://support.f5.com/kb/en-us/solutions/public/6000/400/sol6475.html

SOL6401: Configuring the BIG-IP to use an intermediate or chain certificate with a clientssl profile https://support.f5.com/kb/en-us/solutions/public/6000/400/sol6401.html

SOL6008: Change in Behavior: The BIG-IP system can be configured to execute commands or scripts upon failover https://support.f5.com/kb/en-us/solutions/public/6000/000/sol6008.html

SOL1858: Overview of the qkview utility
https://support.f5.com/kb/en-us/solutions/public/1000/800/sol1858.html

FirePass - New
SOL10357: Configuring RSA SecurID Authentication on a FirePass standalone controller https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10357.html

SOL10351: The BIG-IP WebAccelerator logs a benign warning message when it receives a request containing a Proxy-Connection header https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10351.html

SOL10329: The Java console reports a 'load: class com.citrix.JICA not found' error when attempting to connect to a Java-based Citrix MetaFrame Terminal Server favorite https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10329.html

SOL10327: Overview of FirePass version 6.0.3 cumulative HF-603-4 https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10327.html

SOL10322: FirePass hotfix matrix
https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10322.html

FirePass - Updated
SOL10259: The session variable session.os.platform is incorrectly set to Undefined for new browsers https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10259.html

SOL10253: Processor change for the FirePass 4100 platform https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10253.html

SOL10222: The RSA Authentication field is pre-populated with existing credentials when using the VPN standalone client https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10222.html

SOL10220: The password expiration warning may not display if the gPLink attribute contains multiple Group Policy Objects https://support.f5.com/kb/en-us/solutions/public/10000/200/sol10220.html

SOL10197: Passive FTP fails through Static Application Tunnels after installing cumulative hotfix HF-603-2.1 or HF-603-3 https://support.f5.com/kb/en-us/solutions/public/10000/100/sol10197.html

SOL10184: Network Access session disconnects when using Safari https://support.f5.com/kb/en-us/solutions/public/10000/100/sol10184.html

SOL10009: FirePass 1000 and 1200 series controllers do not support clustering https://support.f5.com/kb/en-us/solutions/public/10000/000/sol10009.html

SOL9778: Archived logs are not sent to the configured email address https://support.f5.com/kb/en-us/solutions/public/9000/700/sol9778.html

SOL9153: Secondary cluster nodes may become intermittently unresponsive when the Automatically add websites that require client side cookie manipulation setting is enabled https://support.f5.com/kb/en-us/solutions/public/9000/100/sol9153.html

SOL8702: Citrix resources fail to launch through Portal Access when the FirePass URL is in the Trusted Sites list of Internet Explorer https://support.f5.com/kb/en-us/solutions/public/8000/700/sol8702.html

SOL8597: Overview of concurrent session limits https://support.f5.com/kb/en-us/solutions/public/8000/500/sol8597.html

Enterprise Manager - New
SOL10349: Enterprise Manager may require network access to the following F5 Networks hosts: activate.f5.com, callhome.f5.com, and drop.f5.com https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10349.html

Release Note: Enterprise Manager version 1.8 https://support.f5.com/kb/en-us/products/em/releasenotes/product/relnotes_1_8_em.html

Manual: Enterprise Manager Administrator Guide 1.8 https://support.f5.com/kb/en-us/products/em/manuals/product/Enterprise_Manager_AdminGuide_1_8.html

Enterprise Manager - Updated
SOL6556: Enterprise Manager software support policy https://support.f5.com/kb/en-us/solutions/public/6000/500/sol6556.html

ARX - New
SOL10355: A share remains offline after a Windows cluster failover https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10355.html

SOL10307: Editing an export after using the browser's Back button will cause the ARX Manager GUI to dump core https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10307.html

ARX - Updated
SOL10157: A drain share rule may result in omTransactionRaise traps being logged https://support.f5.com/kb/en-us/solutions/public/10000/100/sol10157.html
____________________________________________________________________
F5 Networks | 401 Elliott Avenue West | Seattle, Washington 98119

The Leader in Application Traffic Management Ensuring secure and optimized application delivery for global enterprises.

You may unsubscribe from this list at any time by sending a blank email to technews-unsubscribe@lists.f5.com

張貼者： 於 沒有留言:
標籤：
訂閱： 文章 (Atom)

追蹤者