Table Of Contents
New Features in Release 4.1(6)
New Features in Release 4.1(1)
Upgrading or Downgrading the Software
Upgrading the Operating System and ASDM Images
Catalyst 6500 Series Requirements
Cisco 7600 Series Requirements
Resolved Caveats in Release 4.1(9)
Resolved Caveats in Release 4.1(8)
Resolved Caveats in Release 4.1(7)
Resolved Caveats in Release 4.1(6)
Resolved Caveats in Release 4.1(5)
Resolved Caveats in Release 4.1(4)
Resolved Caveats in Release 4.1(3)
Resolved Caveats in Release 4.1(2)
Resolved Caveats in Release 4.1(1)
Obtaining Documentation and Submitting a Service Request
Release Notes for the Catalyst 6500 Series and Cisco 7600 Series Firewall Services Module, Software Release 4.1(x)
May 2012
This document contains release information for FWSM Release 4.1(1) through 4.1(9).
This document includes the following sections:
•
Upgrading or Downgrading the Software
•
Obtaining Documentation and Submitting a Service Request
Important Notes
•
For traffic that passes through the control-plane path, such as packets that require Layer 7 inspection or management traffic, the FWSM sets the maximum number of out-of-order packets that can be queued for a TCP connection to 2 packets, which is not user-configurable. Other TCP normalization features that are supported on the PIX and ASA platforms are not enabled for FWSM.
•
You can disable the limited TCP normalization support for FWSM using the no control-point tcp-normalizer command.
•
When you log in to the system execution space from the switch in multiple context mode, a feature introduced in FWSM Release 3.2 lets you use authentication using a AAA server or local database. Previously, the only method of authentication available was to use the login password defined in the system configuration. The new authentication method is enabled by the aaa authentication telnet console command in the admin context. If you upgrade to Release 3.2 and later, and have this command already in the admin context configuration, then authentication for the system execution space is enabled using the specified server or local database, even if you did not intend to enable it. To use the login password instead, you must remove the aaa authentication telnet console command in the admin context.
•
Do not configure both the timeout uauth 0 command and the aaa authentication clear-conn command; if you do so, you cannot open any connections through the FWSM because the connection immediately closes when AAA succeeds. This happens every time you try to open a connection (because the FWSM is not caching uauth entries).
•
In 3.x, when you used the set connection command for an access list (match access-list), then connection settings were applied to each individual ACE; in 4.0 and later, connection settings are applied to the access list as a whole.
New Features
This section includes the new features for FWSM releases.
Note
There are no new features in FWSM Releases 4.1(2) through 4.1(5) nor in Releases 4.1(7) through 4.1(9).
•
New Features in Release 4.1(6)
•
New Features in Release 4.1(1)
New Features in Release 4.1(6)
Table 1 lists the new feature for FWSM Release 4.1(6).
New Features in Release 4.1(1)
Table 2 lists the new features for FWSM Version 4.1(1).
Upgrading or Downgrading the Software
This section describes how to upgrade to the latest version, and includes the following topics:
•
Upgrading the Operating System and ASDM Images
Note
For ASDM procedures, see the ASDM release notes.
Viewing Your Current Version
Use the show version command to verify the software version of your FWSM.
Upgrading from 2.x or 3.x
Starting in Release 4.0(1), many commands are migrated to new commands (for example, the http-map commands are converted to policy-map type inspect http commands).
If you upgrade from 2.x or 3.x, the configuration is converted. This converted configuration is not saved to memory until you enter the write memory command (or the write memory all command from the system execution space in multiple context mode).
If you try to downgrade to 2.x or 3.x using a converted configuration, many commands will be rejected. Moreover, if you add access lists to the 4.x configuration to take advantage of larger access list memory space, then downgrading could result in an inability to load all the new access lists.
If you want to downgrade, be sure to copy a saved 2.x or 3.x configuration to the starting configuration before you reload with the 2.x or 3.x image.
Upgrading the Operating System and ASDM Images
This section describes how to install the ASDM and operating system (OS) images to the current application partition using TFTP. For FTP or HTTP, or to install to a different partition, see the "Managing Software, Licenses, and Configurations" chapter in Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Configuration Guide using the CLI.
To install and start using the new images, perform the following steps:
Detailed Steps
Step 1
If you have a Cisco.com login, you can obtain the OS and ASDM images from the following website:
http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpmStep 2
For multiple context mode, change to the system execution space:
hostname# changeto systemStep 3
Install the new OS using TFTP:
hostname# copy tftp://server[/path]/filename flash:For example:
hostname# copy tftp://10.1.1.1/c6svc-fwm-k9.4-1-1.bin flash:Step 4
Install the new ASDM using TFTP:
hostname# copy tftp://server[/path]/filename flash:asdmFor example:
hostname# copy tftp://10.1.1.1/asdm-621f.bin flash:asdmStep 5
To reload to start running the new software, enter the following command:
hostname# reload
Downgrading From 4.1
This section describes how to downgrade from 4.1, and includes the following topics:
Important Notes
If you configure the shared management VLAN feature that was introduced in 4.1(1), this feature is not supported when you downgrade to a pre-4.1(1) release.
See the following issues when you use this feature, and then downgrade:
•
The interface configuration for the shared VLAN is accepted in the first context configuration in which it appears, but is rejected in subsequent transparent mode contexts.
•
For these subsequent contexts, if the startup-config has the management VLAN configuration defined directly after another VLAN configuration for through traffic, then the name and security level associated with the (rejected) shared management VLAN is erroneously applied to the immediately preceding VLAN.
Workaround: Remove the interface configuration for the shared VLAN from all contexts before you downgrade.
For example, you have the following configuration in 4.1:
interface Vlan100nameif outsidebridge-group 5security-level 0interface Vlan101nameif dmzsecurity-level 100management-onlyip address 10.90.90.4 255.255.255.0 standby 10.90.90.5After downgrading, the shared management interface vlan101 command is rejected if it was already used in another context; so the nameif dmz and security-level 100 commands are applied to VLAN 100, overwriting the original nameif and security-level commands. (The VLAN 101 management-only and ip address commands are rejected because they are not allowed for the interface vlan command pre-4.1). The resulting VLAN 100 configuration is the following:
interface Vlan100nameif dmzbridge-group 5security-level 100Downgrading
This section describes how to downgrade the ASDM and operating system (OS) images to the current application partitionusing TFTP. For FTP or HTTP, or to install to a different partition, see the "Managing Software, Licenses, and Configurations" chapter in Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Configuration Guide using the CLI.
To install and start using the old images, perform the following steps:
Detailed Steps
Step 1
If you have a Cisco.com login, you can obtain the OS and ASDM images from the following website:
http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm
Step 2
If you configured shared management VLANs for transparent mode contexts, see the "Important Notes" section to remove the configuration for each context.
Step 3
For multiple context mode, change to the system execution space:
hostname# changeto systemStep 4
Install the old OS using TFTP:
hostname# copy tftp://server[/path]/filename flash:For example:
hostname# copy tftp://10.1.1.1/c6svc-fwm-k9.4-0-1.bin flash:Step 5
(Optional) Install the old ASDM using TFTP:
hostname# copy tftp://server[/path]/filename flash:asdmASDM Version 6.2F is backwards compatible with previous versions, so you do not need to downgrade ASDM.
For example:
hostname# copy tftp://10.1.1.1/asdm-611f.bin flash:asdmStep 6
To reload to start running the old software, enter the following command:
hostname# reload
Chassis System Requirements
You can install the FWSM in the Catalyst 6500 series switches or the Cisco 7600 series routers. The configuration of both series is identical, and the series are referred to generically in these release notes as the "switch." The switch includes a switch (the supervisor engine) as well as a router (the MSFC 2).
The switch supports Cisco IOS software on both the switch supervisor engine and the integrated MSFC router.
Note
The Catalyst operating system software is not supported.
The FWSM does not support a direct connection to a switch WAN port because WAN ports do not use static VLANs. However, the WAN port can connect to the MSFC, which can connect to the FWSM.
The FWSM runs its own operating system.
Note
Because the FWSM runs its own operating system, upgrading the Cisco IOS software does not affect the operation of the FWSM.
This section includes the following topics:
•
Catalyst 6500 Series Requirements
•
Cisco 7600 Series Requirements
Catalyst 6500 Series Requirements
Table 3 shows the supervisor engine version and software.
Table 3 Support for FWSM 4.1 on the Catalyst 6500
FWSM Features: Supervisor Engines1 PISA Integration Route Health Injection Virtual Switching System Cisco IOS Software Release12.2(33)SXJ2
720-10GE
No
Yes
Yes
12.2(33)SXJ2
720
No
Yes
No
12.2(33)SXJ2
32
No
Yes
No
12.2(33)SXI8
720-10GE
No
Yes
Yes
12.2(33)SXI8
720
No
Yes
No
12.2(33)SXJ1
720-10GE
No
Yes
Yes
12.2(33)SXJ1
720
No
Yes
No
12.2(33)SXJ1
32
No
Yes
No
12.2(33)SXJ
720-10GE
No
Yes
Yes
12.2(33)SXJ
720
No
Yes
No
12.2(33)SXJ
32
No
Yes
No
12.2(33)SXI6
720-10GE
No
Yes
Yes
12.2(33)SXI6
720
No
Yes
No
12.2(33)SXI7
720-10GE
No
Yes
Yes
12.2(33)SXI7
720
No
Yes
No
12.2(18)SXF and higher
720, 32
No
No
No
12.2(18)SXF2 and higher
2, 720, 32
No
No
No
12.2(33)SXI
720-10GE
No
Yes
Yes
12.2(33)SXI
720, 32
No
Yes
No
12.2(33)SXI2
720-10GE
No
Yes
Yes
12.2(33)SXI2
720, 32
No
Yes
No
12.2(18)ZYA
32-PISA
Yes
No
No
Cisco IOS Software Modularity Release12.2(18)SXF4
720, 32
No
No
No
1 The FWSM does not support the supervisor 1 or 1A.
Cisco 7600 Series Requirements
Table 4 shows the supervisor engine version and software.
Table 4 Support for FWSM 4.1 on the Cisco 7600
FWSM Features: Supervisor Engines1 PISA Integration Route Health Injection Virtual Switching System Cisco IOS Software Release12.2(33)SRD6
720-3C-1GE
No
No
No
12.2(33)SRA
720, 32
No
No
No
12.2(33)SRB
720, 32
No
No
No
12.2(33)SRC
720, 32, 720-1GE
No
No
No
12.2(33)SRD
720, 32, 720-1GE
No
No
No
12.2(33)SRE
720, 32, 720-1GE
No
No
No
12.2(33)SRE2
720-3C-1GE
No
No
No
1 The FWSM does not support the supervisor 1 or 1A.
Management Support
The FWSM supports the following management methods:
•
Cisco ASDM—Software Release 6.2F supports FWSM software Release 4.1 features. ASDM is a browser-based configuration tool that resides on the FWSM. The system administrator can configure multiple security contexts. If desired, individual context administrators can configure only their contexts.
•
Command-line interface (CLI)—Access the CLI by sessioning from the switch or by connecting to the FWSM over the network using Telnet or SSH. The FWSM does not have its own external console port.
Software License Information
The FWSM supports the following licensed features:
•
Multiple security contexts. The FWSM supports two virtual contexts plus one admin context for a total of three security contexts without a license. For more than three contexts, obtain one of the following licenses:
–
20
–
50
–
100
–
250
•
BGP stub support.
•
GTP/GPRS support.
Limitations and Restrictions
Note
These limitations and restrictions also exist in FWSM 3.x.
See the following limitations and restrictions on the FWSM:
•
The following features are not supported when you use TCP state bypass:
–
Application inspection—Application inspection requires both inbound and outbound traffic to go through the same FWSM, so application inspection is not supported with TCP state bypass.
–
AAA authenticated sessions—When a user authenticates with one FWSM, traffic returning via the other FWSM will be denied because the user did not authenticate with that FWSM.
•
Multiple context mode does not support most dynamic routing protocols. BGP stub mode is supported. Security contexts support only static routes or BGP stub mode. You cannot enable OSPF or RIP in multiple context mode.
•
Transparent firewall mode supports a maximum of eight interface pairs per context; however, when multiple bridge-group interfaces exist in a single context, inspection may not work properly. We recommend that you create a separate context for traffic that requires inspection.
•
For transparent firewall mode, you must configure a management IP address per interface pair.
•
The outbound connections (from a higher security interface to a lower security interface) from an interface that is shared between the contexts can only be classified and directed through the correct context if you configure a static translation for the destination IP address. This limitation makes cascading contexts unsupported, because configuring the static translations for all the outside hosts is not feasible.
•
The CPU-intensive commands, such as copy running-config startup-config (the same as the write memory command), might affect system performance, including reducing the successful rate of inspection and AAA connections. When a CPU-intensive action completes, the FWSM might produce a burst of traffic to catch up. If you limit the resource rates for a context, the burst might unexpectedly reach the maximum rate. We recommend using these commands during low traffic periods. Other CPU-intensive actions include the show arp command, polling the FWSM with SNMP, loading a large configuration, and compiling a large access list.
•
Do not configure both the timeout uauth 0 command and the aaa authentication clear-conn command; if you do so, you cannot open any connections through the FWSM because the connection immediately closes when AAA succeeds. This happens every time you try to open a connection (because the FWSM is not caching uauth entries).
•
During URL filtering at high rates, the HTTP connection to the server through the FWSM might not complete correctly in some scenarios with the TCP normalizer enabled and URL filtering enabled. To solve this issue, enter the url-block block 16 command in multiple mode or the url-block block 128 command in single mode. (CSCsj00658)
•
SIP application inspection does not match regular expressions specified in the message-path against a second or larger instance of the VIA SIP Header. Check whether your purpose is accomplished by matching the regular expression specified in the message-path against the first VIA: SIP Header. (CSCso69892)
•
SIP calls with a SIP URI length greater than 256 characters are dropped by the FWSM. Make the SIP User Agent make SIP calls with a SIP URI length less than 256 characters. (CSCsm37291)
•
If the FWSM uses EIGRP, and receives multiple equal-cost routes to the same destination, it installs all of them in the EIGRP topology table. But the FWSM fails to install all the equal-cost routes into the routing table. (CSCso98423)
Open Caveats
The caveats listed in Table 5 are open in the latest maintenance release.
If you are running an older release, and you need to determine the open caveats for your release, then add the caveats in this section to the resolved caveats from later releases. For example, if you are running Release 4.1(1), then you need to add the caveats in this section to the resolved caveats from 4.1(2) and above to determine the complete list of open caveats.
If you are a registered Cisco.com user, view more information about each caveat using the Bug Toolkit at the following website:
http://www.cisco.com/support/bugtoolss
Resolved Caveats
This section contains resolved caveats in each maintenance release and includes the following topics:
•
Resolved Caveats in Release 4.1(9)
•
Resolved Caveats in Release 4.1(8)
•
Resolved Caveats in Release 4.1(7)
•
Resolved Caveats in Release 4.1(6)
•
Resolved Caveats in Release 4.1(5)
•
Resolved Caveats in Release 4.1(4)
•
Resolved Caveats in Release 4.1(3)
•
Resolved Caveats in Release 4.1(2)
•
Resolved Caveats in Release 4.1(1)
Resolved Caveats in Release 4.1(9)
The caveats listed in Table 6 were resolved in Release 4.1(9) and were not previously documented. If you are a registered Cisco.com user, you can view more information about the caveat using the Bug Toolkit at the following website:
Resolved Caveats in Release 4.1(8)
The caveats listed in Table 7 were resolved in Release 4.1(8) and were not previously documented. If you are a registered Cisco.com user, you can view more information about the caveat using the Bug Toolkit at the following website:
Resolved Caveats in Release 4.1(7)
The caveats listed in Table 8 were resolved in Release 4.1(7) and were not previously documented. If you are a registered Cisco.com user, you can view more information about the caveat using the Bug Toolkit at the following website:
Resolved Caveats in Release 4.1(6)
The caveats listed in Table 9 were resolved in Release 4.1(6) and were not previously documented. If you are a registered Cisco.com user, you can view more information about the caveat using the Bug Toolkit at the following website:
Resolved Caveats in Release 4.1(5)
The following caveats were resolved in Release 4.1(5) and were not previously documented. If you are a registered Cisco.com user, you can view more information about the caveat using the Bug Toolkit at the following website:
•
CSCtk61424—OpenSSL Ciphersuite Downgrade and J-PAKE Issues
Symptom:
The device may be affected by an OpenSSL vulnerabilities described in CVE-2010-4180 and CVE-2010-4252.
Conditions:
Device configured with any feature that uses SSL.
Workaround:
Not available
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are 5.1/3.8:
https://intellishield.cisco.com/security/alertmanager/cvssCalculator.do?dispatch=1&version=2&vector=AV:N/AC:L/Au:N/C:C/I:C/A:C/E:H/RL:U/RC:C
CVE IDs CVE-2010-4180 and CVE-2010-4252 have been assigned to document this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
•
CSCtl21186—Cmd authorization fails for certain commands on fallback to LOCAL db
Symptom:
Certain commands like 'show running-config', 'show interface' are allowed to be executed by users with lower privilege-level when fallback has occured.
Conditions:
1. Fallback to LOCAL is configured
2. All FWSM commands are assigned their default privilege levels in LOCAL db.
3. Users with lower privilege-level than 15 login into privileged-exec mode and execute 'show running-config' or 'show interface' commands, and some config commands.
Workaround:
none.
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are 6.0/5.0:
https://intellishield.cisco.com/security/alertmanager/cvssCalculator.do?dispatch=1&version=2&vector=AV:L/AC:H/Au:S/C:C/I:C/A:C/E:F/RL:OF/RC:C
CVE ID CSCtl94142 has been assigned to document this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
•
CSCtl84952—SCCP inspection DoS vulnerability
A vulnerability exists in the Cisco Firewall Services Module (FWSM) for Cisco Catalyst 6500 Series Switches and Cisco 7600 Series Routers that may cause the Cisco FWSM to reload after processing a malformed Skinny Client Control Protocol (SCCP) message. Devices are affected when SCCP inspection is enabled.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at
http://www.cisco.com/warp/public/707/cisco-sa-20110223-fwsm.shtml
Note: Cisco ASA 5500 Series Adaptive Security Appliances are affected by the vulnerability described in this advisory. A separate Cisco Security Advisory has been published to disclose this and other vulnerabilities that affect the Cisco ASA 5500 Series Adaptive Security Appliances. The advisory is available at
http://www.cisco.com/warp/public/707/cisco-sa-20110223-asa.shtml
•
CSCtn04571—Breakage in dcerpc inspection code
Symptom:
RCI response is not processed correctly. Enabling dcerpc debugs shows that the signature 'MEOW' is not found.
Conditions:
Processing RCI response.
Workaround:
None.
Resolved Caveats in Release 4.1(4)
The caveats listed in Table 10 were resolved in software Release 4.1(4). If you are a registered Cisco.com user, view more information about each caveat using the Bug Toolkit at the following website:
http://www.cisco.com/support/bugtools
Resolved Caveats in Release 4.1(3)
The caveats listed in Table 11 were resolved in software Release 4.1(3). If you are a registered Cisco.com user, view more information about each caveat using the Bug Toolkit at the following website:
http://www.cisco.com/support/bugtools
Resolved Caveats in Release 4.1(2)
The caveats listed in Table 12 were resolved in software Release 4.1(2). If you are a registered Cisco.com user, view more information about each caveat using the Bug Toolkit at the following website:
http://www.cisco.com/support/bugtools
Resolved Caveats in Release 4.1(1)
The caveats listed in Table 13 were resolved in software Release 4.1(1). If you are a registered Cisco.com user, view more information about each caveat using the Bug Toolkit at the following website:
http://www.cisco.com/support/bugtools
Related Documentation
See the following sections for related documentation:
Hardware Documents
See the following related hardware documentation:
•
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Installation and Verification Note
•
Catalyst 6500 Series Switch Installation Guide
•
Catalyst 6500 Series Switch Module Installation Guide
Software Documents
See the following related software documentation:
•
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Configuration Guide using the CLI
•
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Command Reference
•
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module System Log Messages
•
Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Configuration Guide using ASDM
•
Release Notes for Cisco ASDM
•
Open Source Software Licenses for FWSM
•
Catalyst 6500 Series Cisco IOS Software Configuration Guide
•
Catalyst 6500 Series Cisco IOS Command Reference
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
©2012 Cisco Systems, Inc. All rights reserved.
