AsyncOS 6.0.0 is GA

Hi,
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
Let us know how you like it!
Best,
Jakob

Hi,
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.
Best Regards,
Jakob

Similar Messages

  • Is it possible to perform a "Clean Install" of AsyncOS on my c100 ESA?

    after decommissioning this c100, both Hard Disk Drives (HDDs) were removed, reformatted, and reinstalled in the ESA by the IT Group.
    Is there a method to reload the AsyncOS on this appliance?  Or do I now have a clean "brick"?
    Please help.
    Regards

    Hello Gordon,
    I'm sorry but AsyncOS is not available on CD/DVD for a fresh install. All appliances are delivered with AsyncOS on it and they can upgrade either via our downloads server or using a local upgrade server. For the local upgrade server procedure (when internet connectivity for the appliance is not available for security reasons), you can download the AsyncOS upgrade package from an URL. But this requires that you have a) already an AsyncOS release on your appliance and b) a valid support contract is in place for the appliance serial number. So in your case the local upgrade server option would also not work as this requires that the appliance can run the 'upgrade' command.
    So sad to say but without an replacement of the entire appliance via the sales team (as it is not a product malfunction support cannot help here) there is no way to get the C100 back online with an AsyncOS. But of course installing Windows OS or Linux (I can confirm that Debian is running on the hardware) would be a good reusage of the C100 in a different way.
    Thanks and regards,
    Martin

  • Strange ARP Problems with C170 and AsyncOS 9

    after upgrading to asyncOS 9.0 (Ironport C170) we have the following problem.
    For better understanding a short explanation (without all network devices)
    The traffic flow is
    Lan --- Application Firewall ---Ironport 
    During a connection between the Firewall and the Ironport, the Ironport is unable to make a  response.
    It seems the Ironport is unable to make an arp resolution for the virtual cluster ip from the firewall.
    E.g. ping from the firewall with the virtual cluster ip as source won't work.
    Ping from the firewall with the physical interface as source works fine.
    AsyncOS prior to version 9 has not such problems.
    The arp table shows following entry for the virtual cluster ip (AsynOS) 
    (xxx.xxx.103.254) at (incomplete) on em1 expired [ethernet]
    Explantation:
    xx.103.254 with mac  01:00:5e:19:67:fe = virtual cluster ip
    xx.103.128 with mac  00:e0:ed:37:05:1a = physical interface ip
    Ping from "xxx.103.254 Cluster IP" as source  to xxx.103.135 (cisco Ironport) as destination
    The ICMP Packet went from the virtual Cluster Interface (xxx.25.103.254) with mac-adress 05:1a (physical interface) to the ironport.
    The ironport makes an arp request...who is xxx.25.103.254?..and receives as answer the OTHER mac-address (virtual Clusterinterface) 67:fe.
    I think, the ironport with the new asyncOS has some troubles with this 2 different mac-addresses.
    No.     Time        Source                Destination           Protocol Length Info
         10 4.115231    xxx.25.103.254        xxx.25.103.135        ICMP     98     Echo (ping) request  id=0xaa26, seq=0/0, ttl=64 (no response found!)
    Frame 10: 98 bytes on wire (784 bits), 98 bytes captured (784 bits)
    Ethernet II, Src: Silicom_37:05:1a (00:e0:ed:37:05:1a), Dst: Cisco_9c:ba:3a (50:3d:e5:9c:ba:3a)
    Internet Protocol Version 4, Src: xxx.25.103.254 (xxx.25.103.254), Dst: xxx.25.103.135 (xxx.25.103.135)
    Internet Control Message Protocol
    No.     Time        Source                Destination           Protocol Length Info
         11 4.115251    Cisco_9c:ba:3a        Broadcast             ARP      42     Who has xxx.25.103.254?  Tell xxx.25.103.135
    Frame 11: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
    Ethernet II, Src: Cisco_9c:ba:3a (50:3d:e5:9c:ba:3a), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
    Address Resolution Protocol (request)
    No.     Time        Source                Destination           Protocol Length Info
         12 4.115365    Silicom_37:05:1a      Cisco_9c:ba:3a        ARP      60     xxx.25.103.254 is at 01:00:5e:19:67:fe
    Frame 12: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
    Ethernet II, Src: Silicom_37:05:1a (00:e0:ed:37:05:1a), Dst: Cisco_9c:ba:3a (50:3d:e5:9c:ba:3a)
    any ideas?

    Try a different DNS server.
    Open System Preferences > Network > Advanced > DNS
    Click + and type:
    208.67.222.222
    Click + again and do the same.
    208.67.220.220
    Click OK.
    Then try Safari or Mail.

  • "An application fault occurred" with AsyncOS 8.0.1 on multiple ESAs

    Ever since upgrading to AsyncOS 8.0.1-023, we have been getting the following application fault intermittently but it has been triggering constantly this morning on all 4 appliances in a cluster and 2 others in a separate cluster:
    An application fault occurred: ('egg/coro_ssl.py _non_blocking_retry|140', "<class 'sslip.Error'>", "(336195711, 'error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry')", '[egg/smtp_client.py run|885] [egg/smtp_client.py _run|964] [egg/coro_ssl.py close|238] [egg/coro_ssl.py shutdown|218] [egg/coro_ssl.py _non_blocking_retry|140]')
    The only thread I see regarding this is that is an known bug with the OS version.  Is there a way to temporarily correct this and is there a known cause to this such as a corrupt message?  We do not want to keep receiving this alert until a fix is released and do not want to be forced to turn off the alerting.
    https://supportforums.cisco.com/discussion/12071286/cscug73383-ironport-esa-version-801-023

    The same for our 2 ESA C370, Version: 8.0.1-023 AND a similiar message for our M670 Version: 8.1.1-013. They were upgraded vom V 7.x last weekend.
    Suprisingly we drive 2 ESA C360, 1 M670 and 1 M160 for another customer without this error. Tose machines were upgraded to the same 8.x versions mentioned above in December last year! Looks a bit strange to me ...
    The Critical message is (on M670):
    An application fault occurred: ('navigation/HelpBarYUI.py my_tasks_list_submenu|462', "<type 'exceptions.KeyError'>", "'varstore'", '[util/Aquarium.py screenLoop|408] [util/InternalLibrary.py inverseExtend|328] [util/InternalLibrary.py __call__|769] [layout/Bare.py __call__|578] [util/InternalLibrary.py __call__|769] [layout/CssAndJavaScript.py __call__|451] [util/InternalLibrary.py __call__|769] [layout/Sparse.py __call__|1483] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [layout/Sparse.py doTop|851] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [layout/Sparse.py doHelpBar|795] [util/InternalLibrary.py call|280] [navigation/HelpBar.py __call__|154] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [navigation/HelpBarYUI.py options_and_help_yui_menubar|217] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [navigation/HelpBarYUI.py my_tasks_mainmenu|275] [Cheetah/NameMapper.py valueFromSearchList|250] [Cheetah/NameMapper.py _valueForName|229] [navigation/HelpBarYUI.py my_tasks_list_submenu|462]')
    Version: 8.1.1-013

  • Cisco IronPort AsyncOS 6.7.6-068 for Management GA Notification

    Cisco is pleased to announce the General Availability (GA) of a new major release of AsyncOS 6.7.6-068 for
    Management to all customers. This release applies to all our Security Management Appliances (M-Series).
    AsyncOS 6.7.6-068 for Management enables Centralized Tracking and Reporting for the new features introduced in AsyncOS 7.0 for Email.
    New Features and Enhancements in AsyncOS 6.7.6-068 for Management
    New Feature: Centralized support for the reporting and tracking changes in the AsyncOS for Email release 7.0:
    RSA Data Loss Prevention
    Marketing Message Detection
    New Feature: Reporting by ESA Groups
    Enhanced: Domain-Based Executive Summary Report now configurable by:
    Domain of Email Server
    Domain of Email Address
    Fixes in AsyncOS 6.7.6-068 for Management
    Fixed: MemoryError after losing Housekeeper thread [Defect ID: 52048]
    Fixed: The Show Details link results in a timeout [Defect ID: 51558]
    Fixed: Safelist/Blocklist should be exportable via CLI [Defect ID: 43360]
    Fixed: LDAP Query strips spaces [Defect ID: 46099]
    Fixed: Tracking database time does not update after system timezone is changed [Defect ID: 49407]
    Fixed: Application error when accessing Online Help from the End User Spam Quarantine page [Defect ID: 52395]
    This release has gone through our beta program, internal soak tests and is also running in production at our FCS customers.
    Please upgrade at your convenience and let us know how you like this new release!
    Cheers,
    Jakob

    Hi,
    We identified an issue in AsyncOS 6.7.6-068 for Management that under certain circumstances can cause loss of historical reporting data when reporting groups are configured. To ensure a high quality release, further testing on our side is required.
    6.7.6-068 is no longer available for upgrade to your M-Series appliances.
    If you already upgraded to 6.7.6-068 we strongly recommend to disable group based reporting to avoid being affected.
    We expect to release a new improved build of 6.7.6 shortly and apologize for any inconvenience or confusion this might have caused.
    If you are required to upgrade to 6.7.6 before a new build is available, please contact Cisco IronPort Customer Support.
    I'll let you know once the new build is available...
    Best Regards,
    Jakob

  • IronPort C670 AsyncOS Upgrade over http proxy

    Good day.
    I try to upgrade my IronPort C670 AsyncOS over http proxy.
    Proxy is working fine when i try to get featured keys for example. But whe when i try to ugprade AsyncOS i get "Error — Error fetching manifest: Failed to connect to manifest server" message.
    Proxy server is work and ironport have network acess to it. Even for telnet to 80 port.
    Squid proxy log:
    1373973019.051     57 {{IP_ADDRESS}} TCP_IMS_HIT/304 368 GET http://downloads.ironport.com/vtl/vof_history_year.tgz - NONE/- application/x-gzip
    1373973079.194    117 {{IP_ADDRESS}} TCP_IMS_HIT/304 368 GET http://downloads.ironport.com/vtl/vof_history_year.tgz - NONE/- application/x-gzip
    1373973119.168    497 {{IP_ADDRESS}} TCP_MISS/200 715 GET http://downloads.ironport.com/asyncos/fkey? - DIRECT/217.212.252.179 text/plain
    What can be the problem?

    Hi,
    Please take a look to this:
    http://tools.cisco.com/squish/c93bE
    HTH
    Luis Silva
    "If you need PDI (Planning, Design, Implement) assistance feel free to reach"
    http://www.cisco.com/web/partners/tools/pdihd.html

  • What is the latest available AsyncOS Version for the IronPort C160

    Hello @ all,
    i try to figure out if there is a AsyncOS 8.x update for the Cisco IronPort C160 available.
    My Cisco C160 cluster is running the 7.6.0-357 AsyncOS version.
    Greetings Robert

    8.0.1-023 is still the latest GA release.  If you are on that release, you won't see any of the FCS releases.  
    Q: Are there any other releases available for AsyncOS?
    A: Yes, FCS candidates are available for provisioning, but you must open a support case and request to be added to the FCS provisioning group.  Please see our other CSC blog posts for recent FCS release information.
    I'll shoot you a DM and work with you to get your SN and info, if you are wanting to get 8.5.6-073?
    I hope this helps!
    -Robert
    (*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

  • AsyncOS 5.5 - errno 60 in mail logs

    We upgraded our IronPorts to AsyncOS 5.5 two weeks ago and over the past week, an issue has begun to manifest itself. We are wondering if anyone else has seen this.
    When sending to some domains (at this point about 20 or so) we receive error responses (soft bounces) and eventually hard bounces. The errors we are seeing in the mail logs are:
    Thu Nov 15 11:43:57 2007 Info: Delayed: DCID 11509176 MID 43979667 to RID 0 - 4.4.0 - Other network problem ('000', ['[Errno 60] Operation timed out']) []
    and less often:
    Thu Nov 15 11:33:23 2007 Info: Delayed: DCID 11508361 MID 44031268 to RID 0 - 4.4.0 - Other network problem ('000', ['[Errno 54] Connection reset by peer']) []
    The systems on the other side appear to be all fronted by PIX Firewalls and do not have the SMTP Fixup command enabled. (If you telnet to it you get 220 ************************) Only very small manual telnet emails seem to make it through. The MTU packet size by default on their end is 1380. They lowered it and more emails made it through, but not all. The MTU packet size on our firewalls in 1500 and adjusting the packet size on the IronPorts has not helped the issue.
    Has anyone else seen this, or better yet, fixed this issue? If you look at delivery status and see domains that are up and have a lot of softbounces, this may be a sign that this is happening.
    Any and all help would be appreciated.

    We turned it on as soon as it was a feature in AsyncOS - around 2005 - despite it being half implemented (ala AsyncOS's support of SMTP-TLS).
    It's not that it was only half implemented - it's that there are two different protocols at play here.
    The first is DomainKeys, which IronPort has supported for some time. This is an early standard designed largely by Yahoo. DomainKeys is covered in Historic RFC 4870.
    The second is DomainKeys Identified Mail, or DKIM, which is a newer standard based on a combination of DomainKeys and Cisco's Identified Internet Mail. DKIM is covered in the Standards Track RFC 4871, and was implemented in AsyncOS 5.5.
    However, it is pretty much finished [for everyone on the internet] for the next 12+ months unless Cisco+Ironport fix the PIX smtp fixup issue.
    It's been fixed since August in PIX code 7.2(3). The problem is of course that it's the recipients end that needs this upgrade (or to disable MailGuard), not the end doing the DKIM signing, which obviously make it more difficult to resolve.

  • AsyncOS 5.5.1-014 for Email is now available

    UPDATE: 2008-2-26 5.5.1-014 releases:
    This release includes a number of fixes:
    * Fixed: Appliances Are Not Generating SNMP Traps
    * Fixed: Leftover Files Are Deposited in scanning_temp_files Directory
    * Fixed: DNS-Related Memory Issues Delay Acceptance of Incoming Mail
    UPDATE: 2007-12-17 5.5.1-011, 5.1.2-011, 4.7.2-005 releases:
    This release includes a number of updates and fixes:
    * Fixed: 35715,38152,38531,38532 Consolidated LDAP fixes
    * Fixed: 38506,38527 Certain malformed messages can severely degrade performance
    * Fixed: 38274 IronPort Spam Quarantine alias consolidation issues with Active Directory
    * Fixed: 38248 Clustered SafeList/BlockList incorrectly prompts for login
    About Earlier Builds of AsyncOS for Email
    38527 is also present in earlier builds of AsyncOS for Email. Due to the potential severity of this issue we have also patched the earlier versions listed below, customers who are not ready to upgrade to 5.5.1-011 are encouraged to upgrade to one of these builds:
    5.1.2-011
    4.7.2-005
    UPDATE: 2007-11-28 5.5.1-010 releases:
    This Hot Patch release contains the following feature and stability fixes
    * New: PCI, HIPAA, GLB and SOX dictionaries preloaded for use in content and message filters
    * 37711 Logging into the IronPort Spam Quarantine generates error
    * Fixed: 37971 LDAP can slow delivery after log subscription update
    * Fixed: 37772 LDAP routing host is ignored when the routing address matches the original address
    * Fixed: 36408 application fault in smtpauth
    IronPort Systems is pleased to announce the release of AsyncOS 5.5.1-010 for Email for all C-Series and X-Series Email Security Appliances. This release includes all of the powerful new tools for integrated Data Loss Prevention and Encryption released in AsyncOS 5.5.0 as well as critical security patches. IronPort recommends all customers to upgrade to 5.5.1.
    * New Feature: IronPort PXE Encryption
    * Enhanced: Content Scanning capabilities for Data Loss Prevention
    * Enhanced: LDAP Capabilities
    * New Feature: DKIM Authentication
    * New Feature: End-User Safelists and Blocklists
    * Enhanced: Reporting
    * Enhanced: Web User Interface
    * Updated: Brazilian DST
    * Fixed: Double-Byte character rendering in IronPort Spam Quarantine
    * Fixed: Performance optimization of disabled content filters
    * Fixed: Virtual gateway delivery to host with invalid DNS entry may disrupt mailflow
    NOTE: For customers running pre 5.5.0 releases, there is no requirement to upgrade to 5.5.0 first. If 5.5.1 appears as an available upgrade customers are encouraged to upgrade directly to 5.5.1.
    Customers running older builds who are not ready to move to 5.5.1, are encouraged to upgrade to our current patched builds:
    - 5.1.2-014
    These builds provide out latest stability fixes.
    Webinar for Selected New 5.5.0 Features
    We are pleased to offer a webinar that presents information about Safelist/Blocklists, Smart Identifiers and DKIM. You can download the webinar from the Support Portal:
    http://tinyurl.com/2o28uw
    Preparing to Upgrade
    As a best practice, IronPort recommends preparing for an upgrade by taking the following steps:
    1. Save the XML configuration file off of the appliance.
    2. Suspend the listeners.
    3. Drain the mail queue and the delivery queue.
    4. Re-enable the listeners after you upgrade.

    I haven't upgraded to 5.5.0 yet, but I was very excited to learn about end-user whitelists and blacklists, which is something we'd been pushing for since we bought our Ironports. Unfortunately, it looks like it's being implemented in a way that makes it impossible for me to deploy at this time.
    We have two C350s, and would need the whitelists and blacklists to appear on each box. It appears that I could do this by exporting the database from one machine, transferring it to the other, and then importing it. However, this appears to ONLY be able to be done via the GUI.
    This is a showstopper for me, because I do not want to have to log into the Ironport every day to import and export the databases - I would want to automate it. I talked to technical support, and it appears that there is no way to do this via the CLI.
    My feature request is this: please consider adding a command that would allow me to remotely force the database to be dumped, and another command to import the database.
    Ideally, it would be something like:
    safelistconfig dump
    safelistconfig import
    If that was available, I would make my users a lot happier with this feature.

  • AsyncOS 6.5.3 for Email and Management is GA

    Hi,
    On Monday (08/17) we released AsyncOS 6.5.3 for Email and Management to all customers. Here is a summary of the fixes included in this release. 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.
    Partial list of defects fixed in 6.5.3-007:
    * Fixed: Clustered Appliances Don’t Close Orphaned Connections. [Defect ID: 40184 and 34441]
    * Fixed: 30 connections to ldap when max=10 [Defect ID: 45194]
    * Fixed: Multibyte filename for encrypted attachment can be corrupted [Defect ID: 45721]
    * Fixed: Export on Delivery Status page on Monitor tab only gives 10 entries when 100 are displayed [Defect ID: 46977]
    I'd like to encourage you to have a look at the release notes and to upgrade to 6.5.3 at your convenience.
    Please be advised that due to some optimizations for future upgrades, it will not be possible to revert from 6.5.3 to versions earlier than 6.5.0.
    Let us know how you like it!
    Best,
    Jakob

    this is a bit old now, can it be un-stickied?
    As you wish! :)

  • AsyncOS 7.1.1 for Email is GA

    Hi,
    Cisco is pleased to announce the General Availability (GA) of a new major release of AsyncOS 7.1.1-012 for Email to all customers. This release applies to all our Email Security Appliances (C and X-Series).
    Please be advised that a new maintenance release AsyncOS 7.0.2-007 for Email is also currently generally available to all customers. We highly recommend upgrading to AsyncOS 7.1.1-012 for Email, if you plan to use any of the new features and enhancements listed below.
    New Features and Enhancements in 7.1.1-012 for Email
    Enhancement: DLP Assessment Wizard (Requires RSA DLP Feature Key)
    Enhancement: New RSA Email DLP Policy templates support (Massachusetts CMR-201 and Corporate Financials)
    Enhancement: TLS Administration Enhancements
    Enhancement: No Authentication Encryption Envelope (Requires IronPort Email Encryption Feature Key)
    New Feature: Administrative Access Control List
    New Feature: Customized Login Banner
    Partial list of defects fixed in 7.1.1-012 for Email
    Fixed: A Malformed Viral Message can potentially cause a Mail Outage, when using McAfee as AV engine with non-default settings [Defect ID: 68615]
    Fixed: Some Viral messages can be reported unscannable and potentially delivered, when using Sophos as AV engine with non-default settings [Defect ID: 68896]
    Fixed: Extra Spaces in Footer When Forwarding via Outlook [Defect ID: 67312]
    Fixed: Demo Certificate Becomes Default Certificate After Upgrade to AsyncOS 7.1 for Email [Defect ID: 69456]
    Fixed: Application Fault Occurs When Switching Cluster Levels in Encryption Profile [Defect ID: 55874]
    Fixed: Robustness Fixes for Lockups on C160 Appliances [Defect ID: 68955]
    Fixed: Invalid Regular Expressions Affects RSA Email DLP Scanning [Defect ID: 67002]
    For further information about this release, please refer to the AsyncOS Release Notes. The release notes are available on our Support Portal.
    https://supportportal.ironport.com
    Thank you for choosing Cisco IronPort Security Products.
    Best,
    Kishore

    I haven't upgraded to 5.5.0 yet, but I was very excited to learn about end-user whitelists and blacklists, which is something we'd been pushing for since we bought our Ironports. Unfortunately, it looks like it's being implemented in a way that makes it impossible for me to deploy at this time.
    We have two C350s, and would need the whitelists and blacklists to appear on each box. It appears that I could do this by exporting the database from one machine, transferring it to the other, and then importing it. However, this appears to ONLY be able to be done via the GUI.
    This is a showstopper for me, because I do not want to have to log into the Ironport every day to import and export the databases - I would want to automate it. I talked to technical support, and it appears that there is no way to do this via the CLI.
    My feature request is this: please consider adding a command that would allow me to remotely force the database to be dumped, and another command to import the database.
    Ideally, it would be something like:
    safelistconfig dump
    safelistconfig import
    If that was available, I would make my users a lot happier with this feature.

  • AsyncOS 6.3.3 for Web is GA

    Hi,
    Cisco is pleased to announce a maintenance release of AsyncOS 6.3.3-015 for Web to all customers (GA). This release applies to all our Web Security Appliances (S-Series).
    Enhancements and Fixes in AsyncOS 6.3.3-015 for Web
    Fixed: Web Proxy returns incomplete web pages from objects in the web cache in some cases [Defect ID: 66076]
    Fixed: Uploading data to servers using a POST command fails in some cases [Defect ID: 52504]
    Fixed: Appliance may lock up or reboot when tailing access logs in some cases [Defect ID: 42438]
    Fixed: TLS/SSL Man-in-the-Middle Vulnerability [Defect ID: 55972]
    Fixed: hostkeyconfig CLI command erroneously returns a traceback in some cases [Defect ID: 48748]
    Fixed: Cannot join the Active Directory domain in some cases [Defect ID: 54854]
    For further information about this release, please refer to the AsyncOS Release Notes. The release notes are available on our Support
    Portal.
    Release Stage
    General Availability (GA): This release is available to all our customers and is a recommended build to be used in your production environments.
    Please have a look at the release notes and give the new build a spin!
    Thank you for choosing Cisco IronPort Security Products.
    Cheers,
    Jakob

    .

  • AsyncOS 6.3.5-015 for Web

    We are currently running 6.3.3-015 but are running
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}
    something called defect 44344.
    They say our proxy service is crashing which is causing timeouts on web surfing.
    Ironport suggests going version 6.3.5-015 but I'm not sure how stable that version is and how long it has been released.
    Anyone have any experience w/ AsyncOS 6.3.5-015?
    thx,
    cris

    .

  • EoS (end of support) AsyncOS 7.5.2-014 of ESA

    Hi All,
       I would like to know about end of support for AsyncOS 7.5.2-014 of ESA  and I want official document  end of support announcement from cisco. Please give link or document if some who have it.
    Thanks,

    EOL dates and information can be found here:
    http://www.cisco.com/web/ironport/asyncOS_esa_eol_dates.html
    7.5.2-014 would have been EOL as of April 30, 2014.
    Full EOL info:
    http://www.cisco.com/web/ironport/product_discontinuance.html
    Cisco IronPort AsyncOS and Mail Flow Central software releases are supported for up to eighteen (18) months from the First Customer Shipment Date (FCS), or two (2) subsequent major releases of such software, whichever occurs first. At such time, the software reaches EOL. Major releases of the software are designated as an increment in the first number in a release designation (i.e. 4.y.z to 5.y.z).
    At EOL, Engineering, Customer Support and the Cisco IronPort Threat Operations Center no longer provide support for the software release. Thus, update releases (e.g. service, maintenance, and patches) are no longer created for the software release and "signatures," "rules," or similar data services may not be compatible with discontinued versions of the software. To receive software support and updates, customers are required to upgrade to a supported version of the software.
    -Robert

  • AsyncOS 5.5.2 General Release - Date?

    Just wondering if you know an indicative release date for the general release of AsyncOS 5.5 for Web? We will soon be rolling out our s650, and would prefer to do it on 5.5 if possible (i.e. if it's due to be released shortly, we might delay our rollout for a while until it is released.)

    AsyncOS 5.5.2-030 is generally available and released on 7/15/08.
    New Features in AsyncOS 5.5.2
    * New Feature: HTTPS Decryption
    * New Feature: PAC file hosting
    * New Feature: Customizable local EUN pages
    * New Feature: Admin login enhancements

  • AsyncOS 6.3.1-025 and 6.0.2-017 for Web are GA

    Dear Cisco IronPort Customer,
    IronPort, now part of Cisco, is pleased to announce the General Availability (GA) of the two maintenance releases of AsyncOS 6.3.1-025 for Web and 6.0.2-017 for Web to all customers. These releases applies to all our Web Security Appliances (S-Series).
    Enhancements and Fixes in AsyncOS 6.3.1-025 for Web
    Partial list of defects fixed in 6.3.1-025
    * Fixed: Web Security appliance spontaneously reboots due to a slow memory leak when clients used NTLMv1 authentication in some cases. [Defect ID: 52548]
    * Fixed: Webroot scanning engine stops working when downloading some .cab files. [Defect ID: 53793]
    * Fixed: Web Proxy generates a core file after a client sends a POST request to a server that returns a 503 “Service Unavailable” message in some cases. [Defect ID: 54019]
    * Fixed: Web interface erroneously shows 100% CPU utilization when rate is lower. [Defect ID: 54767]
    * Fixed: Web Proxy generates a core file and restarts in some cases. [Defect ID: 54890]
    * Fixed: Web Proxy generates a core file and restarts after processing some HTTPS requests in some cases. [Defect ID: 55407]
    Enhancements and Fixes in AsyncOS 6.0.2-017 for Web
    Partial list of defects fixed in 6.0.2-017
    * Enhancement: Added support for NTLM proxy authentication against Windows 2008 Server R2. [Defect ID: 49114]
    * Fixed: Web Security appliance spontaneously reboots due to a slow memory leak when clients used NTLMv1 authentication in some cases. [Defect ID: 52548]
    * Fixed: Webroot scanning engine stops working when downloading some .cab files. [Defect ID: 53793]
    * Fixed: WBNP engine erroneously runs at 100% due to a memory leak. [Defect ID: 54034]
    * Fixed: Web interface erroneously shows 100% CPU utilization when rate is lower. [Defect ID: 54767]
    * Fixed: Vulnerability in Secure Sockets Layer (SSL) certificates. [Defect ID: 55278]
    * Fixed: Web Proxy generates a core file and restarts after processing some HTTPS requests in some cases. [Defect ID: 55407]
    For further information about these releases, please refer to the AsyncOS Release Notes. The release notes are available on our Support Portal:
    https://supportportal.ironport.com
    If you are concerned about an issue not listed there, please contact your authorized support provider to make an inquiry.
    How to Upgrade
    Prior to upgrading, please read the Release Notes referenced above and save a copy of the configuration file somewhere other than on your appliance.
    Once you have read the Release Notes you may log into the command line of your IronPort Appliance as the 'admin' user, and type 'upgrade', or use the WebUI upgrade functionality in the "System Administration" tab.
    **NOTE** It is important that you follow the upgrade instructions available in the Release Notes. If you do attempt to upgrade and do not see the desired release version available, your appliance is likely not on a version allowed to upgrade directly. See 'Upgrade Paths', below.
    Upgrade Paths
    Please refer to the Release Notes for qualified upgrade paths.
    If your systems are on any other AsyncOS release, you will need to perform multiple upgrades as specified in the release notes. Only the immediate next step in the upgrade path will be shown to you, with the next revision being shown once you are at the approved level.
    Release Stage
    General Availability (GA): This release is available to all our customers and is a recommended build to be used in your production environments.
    Thank you for choosing Cisco IronPort Security Products.
    Best Regards,
    Jakob

    6.3.1-025 is GA and anybody can upgrade. Release notes can be found on the portal.
    Notifications are done in several stages so not every customer is notified on the first day of GA.
    I'll post a GA announcement here on the portal as well - sorry for the delay.
    Best,
    Jakob

Maybe you are looking for

  • IPhone is not being recognized by iTunes

    Hi everyone, so today i tried to update my musics on iphone and i plugged into my PC, i heard the usual sound of being recognized as charging but iTunes didn't recognized it..., i tried at least 2 other cables i have and nothing (recognized by PC not

  • How do I take a snapshot picture of my screen

    , How do I take a snapshot picture of my screen?

  • Changed MIC in quality plan for new lot.....

    Hi All, I created quality plan for one material and did result recording. Now again new lot is created for same material but this time I donu2019t want to check same MIC what I did last time. I deleted the pervious MIC and added new MIC what I want t

  • Page printing

    Hi all My smartform is printing basically 2 page, a letter and a form. These 2 item is printed using same print program and smartform. I put the letter as first page without Main Window, because this letter is not going to be more than one page. Whil

  • Picture title not shown in iPhoto

    When I import a batch of photos into Iphoto - all are shown but several have no title and will not transfer to my iPad. The photos come from another source and the ones with titles have not been edited but the ones with no title have. Does anyone kno