Yesterday (07/15) we released AsyncOS 6.0.0 for Web to all customers. This release introduces a lot of new features and also contains fixes and enhancements. Here is a short overview. Please have a look at the release notes for a more comprehensive list or contact Cisco IronPort Customer Support if you have questions in regards to anything specific that is not listed there.
* New Feature: IronPort Data Security * New Feature: External Data Loss Prevention * New Feature: Native FTP * New Feature: Multiple Identities in a Policy Group * New Feature: Warning Users Before Continuing * Enhanced: Authentication (Includes Active Directory 2008 Support) * Enhanced: Logging * Enhanced: Accelerated AsyncOS Upgrades
Partial list of defects fixed in 6.0.0-544 *Fixed: AsyncOS does not fetch new HTTPS server certificate when the cached certificate has expired [Defect ID: 47454] * Fixed: End-user notification pages do not display correctly because they do not contain UTF-8 encoding information [Defect ID: 32009] * Fixed: HTTPS connections break when client certificates are required when the Web Security appliance is deployed in transparent mode [Defect ID: 44706] * Fixed: testauthconfig CLI command fails for NTLM authentication realms in some cases [Defect ID: 47431]
I'd encourage you to have a look at the release notes and to upgrade to 6.0.0 at your convenience.
5.7.1/6.7.0 is just about to be GA'ed as well so if you plan to centrally manage your S-Series appliances via a M-Series, please keep in mind that there is no upgrade path between those two branches. If you want to use 5.7.1/6.7.0, do not upgrade to 6.0.0... Please have a look at this KB article for more details: http://tinyurl.com/mpd4wc
We found two defects in this GA version that I want to make you aware of:
* Access logs do not contain entries for requests from users with spaces in the user name. [Defect ID: 52092] * End-user acknowledgment page link contains client IP instead of Web Security appliance IP after DNS failure [Defect ID: 49114] - We have a workaround documented in the release notes.
Fixes for those issues will be included in the next maintenance release of AsyncOS 6.0.1 for Web which we expect to be available on request shortly.
will AsyncOS 6.0 support upcoming Windows Server 2008 R2
pls be so kind and let us know whether AsyncOS 6.0 will support the upcoming Windows Server 2008 R2 release for the purpose of authentication (both LDAP and NTLM). As Windows Server 2008 R2 will be available very soon (expected by mid of September 2009) for ordering we have to know at earliest so that we can plan accordingly the upgrade of Domain Controllers.
Windows Server 2008 R2 will not be supported in 6.0.0. Here is a section from the release notes:
NTLM proxy authentication against Windows 2008 Server R2 does not work. At the time AsyncOS for Web 6.0 became generally available, Windows 2008 Server R2 was not generally available. NTLM proxy authentication does work and is supported against generally available versions of Windows 2008 Server before version R2. [Defect ID: 52047]
We plan to add support for R2 in an upcoming 6.0 maintenance release post 6.0.1 and it is also supported in the upcoming 6.3 release which will be available for early adopters shortly.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :