A. Not at this time. FlexWAN interfaces and routed ports use hidden VLANs which can't be passed directly to a firewall vlan-group.
The WAN traffic must terminate on the MSFC and then pass to the FWSM using another VLAN.
Q. Can we pass traffic between two interfaces at the same security level?
A. Yes in FWSM2.2, No in FWSM1.1. A command has been provided to allow traffic to pass between interfaces at the same security level (
same-security-level permit inter interface). In addition to invoking this command, the policy must be configured to allow the traffic to pass.
Q. Can we configure more than one interface at security level 100 (inside)?
A. Yes in FWSM2.2, No in FWSM1.1.
FWSM2.2 eliminates the special status given to interfaces with names "inside" and "outside". Beginning with the 2.2 release, the user can assign any name to an interface and configure any security level between 0 to 100 for that interface.
Q. The FWSM has a label that states, "Do not remove card while status light is green or disk corruption may occur." What does this mean?
A. The firewall module should be removed only after disabling power using one of the following methods. (There is no preference for a particular method.)
Use the switch's command-line interface (CLI) and issue one of the following commands.
· When the status light in longer green, you may remove the module safely.
Q. I used the show module command, and my FWSM has a status of faulty/other. What should I do?
A. Refer to the following checklist to troubleshoot an FWSM with a status of faulty/other.
· Ensure that you are running a supported version of code on your switch. Ensure that the FWSM can co-exist with the other blades located in the same chassis. Refer to the
Catalyst 6500 Release Notes and/or
Software Advisor (
registered customers only) for
· If you are running CatOS/Hybrid code on your switch, reset the configuration for the slot occupied by the FWSM module. To do this, use the following commands.
Q. What is the minimum version of code that I need to run to support my FWSM, Intrusion Detection System Module 2 (IDSM2),
and VPN Service Module (VPNSM)?
A. The appropriate version of code depends on the type of Supervisor Module in your 6500 or 7600 chassis, as well as the type of software you are running (CatOS [Hybrid] or Cisco IOS [Native]). Please refer to the table below for specific code versions for your module and Multilayer Switch Feature Card (MSFC). In addition, please refer to the release notes for updates to this table.
Q. Can I run the FWSM, Intrusion Detection System Module 2 (IDSM2), and VPN Service Module (VPNSM) in the same chassis?
A. Yes, you can run these modules in the same chassis if the switch is running integrated Cisco IOS software with a minimum version of Cisco IOS Software Release 12.2(14)SY (Sup2) or 12.2(17a)SX10 (Sup720). Currently, there is no CatOS version that can support these service modules in the same 6500 or 7600 chassis.
Q. What are my configuration and management options for the FWSM?
A. Configuration and management options include the following.
Management Center for Firewalls
Versions 1.3.0 and 1.3.1
This is a web-based interface for configuring and managing multiple FWSM.
Note: Support for service groups within object grouping is limited. Service groups are successfully parsed, but flatten immediately. This affects commands with icmp-type, protocol, and service keywords . This limitation applies to versions 1.3 and earlier. V1.3.1 provides support for AAA fallback and online upgrade features introduced in FWSM2.2.
This is a web-based interface for monitoring Cisco security devices. The software centralizes syslog management from multiple Cisco security devices with flexible reporting and alerting options.
Monitoring Center for Performance
Versions 2.0 and later*
This is a web-based interface for monitoring and troubleshooting the health and performance of services that contribute to network security. Simple Network Management Protocol (SNMP) is the underlying protocol used.
This is a web-based interface for configuring, managing, and monitoring a FWSM. PIX Device Manager (PDM) must be installed locally on the FWSM.
Telnet provides remote command-line interface (CLI) access to a firewall.
Note: To allow Telnet access to the lowest security interface (commonly known as the outside interface), you need to Configure IPSec for Management.
Secure Shell (SSH)
SSH provides secure remote CLI access to a firewall.
SNMP provides a method of monitoring the FWSM.
Note: SNMP is read-only on the FWSM.
Syslog provides a method of monitoring the FWSM.
1This software is part of the CiscoWorks
VPN/Security Management Solution (VMS) bundle. This software provides an integrated approach to managing Cisco security devices via a browser-based interface for Enterprise networks.
Q. What is an SVI? Can I configure multiple SVIs?
A. SVI stands for Switched Virtual Interface. It represents a logical Layer 3 interface on a switch. For CatOS versions earlier than 7.6(1) and Cisco IOS Software Releases earlier than 12.2(14)SY, only one SVI is allowed as part of the firewall VLANs. In other words, only one Layer 3 interface can be configured between the FWSM and Multilayer Switch Feature Card (MSFC). Attempting to configure multiple SVIs produces a command-line interface (CLI) error message.
For CatOS versions 7.6(1) and later and Cisco IOS Software Releases 12.2(14)SY and later, the FWSM supports multiple SVIs. By default, only one SVI is supported. To enable support for multiple SVIs on your switch, use one of the following commands.
If you are configuring your switch for the FWSM VLANs and receive an error message indicating that you have more than one SVI, look at your switch and/or MSFC configuration to ensure that only one Layer 3 interface (or VLAN interface) exists as part of the firewall VLANs.
Note: Cisco recommends using only one SVI; this will allow you to avoid a complicated configuration involving policy routing.
Q. Why am I unable to ping my FWSM on a directly connected interface?
A. By default, each interface denies Internet Control Message Protocol (ICMP). Use the
icmp command to allow this traffic to the interface. This behavior differs from that of the PIX.
Note: When ICMP to the interface is denied by the icmp command, you will still see the correct MAC address in the Address Resolution Protocol (ARP) table. If you do not see the MAC address, please see the next question.
Q. I am unable to ping my FWSM on a directly connected interface, and I do not see an Address Resolution Protocol (ARP) entry for
the interface. I am running CatOS (or hybrid) software on my switch. What should I do?
A. Configuring the interfaces within the FWSM configuration (with the
nameif command) or on the Multilayer Switch Feature Card (MSFC) [ with the
interface vlancommand] before they are configured on the switch (on the Supervisor Module in CatOS) may make the interfaces appear as if they are not responding at all, with no ARP entry or Internet Control Message Protocol (ICMP) response.
If you configured an interface on the FWSM or MSFC that belongs to the firewall VLANs before you configured the switch, remove the FWSM or MSFC entry, reload the module, then re-add the entry.
Q. Why am I unable to ping or pass any traffic through the FWSM?
A. Unlike the PIX, which allowed traffic from inside to outside, The FWSM has an implicit deny rule on all interfaces. For traffic to pass through the FWSM from a higher security interface (the inside interface) to a lower security interface (outside interface), Network Address Translation (NAT) must be configured using the
You must also use the
access-list command to implement access lists that permit traffic to flow through the FWSM. By default, access lists deny all traffic on all interfaces (deny ip any any). This behavior differs from the PIX's default configuration, which allows traffic from higher to lower security and denies traffic from lower to higher security. To get the FWSM to behave like the PIX, configure an access list with permit ip any and apply it to the high-security interface(s).
Q. I can ping the FWSM interface that is directly connected to my network, but I am unable to ping other interfaces. Is this normal?
A. Yes. This is an built-in security mechanism that also exists on the PIX Firewall.
Q. Does virtualization in FWSM2.2 cause any performance hit over FWSM1.1?
A. Yes, although generally not significantly so. FWSM2.2 performance will be within 90% of the performance of FWSM1.1. Some parameters are lower due to allocations established per context. See limitations section.
Q. Can the administrator prevent an individual context from consuming all of the available blade resources?
A. Yes. FWSM2.2 provides a resource manager function that allows an individual context to be limited to either a percentage of blade resources, or a finite amount. Users can be placed in classes of equivalent limitation, or left in a default class, which allows total resource access on a first come first served basis.
Q. Can I configure failover between two FWSMs running different versions of code?
A. No with FWSM1.1, and a qualified yes with FWSM2.2. FWSM1.1 Failover requires that both FWSMs run the same version of code.
A mechanism within the failover feature verifies the peer version and prevents failover if the versions of code are different. For this reason, you must upgrade both FWSMs at the same time. To allow flexibility in upgrading live networks, FWSM2.2 has a feature called `online upgrade' that allows failover between FWSM running different point releases of code (e.g. 2.2 to 2.3). Failover is still not allowed between major releases e.g. 2.x to 3.x)
Q. Can I configure failover between two FWSMs in different chassis?
A. Yes. But the FWSMs must be connected by Layer 2 on all interfaces. In other words, all interfaces must be capable of exchanging Layer 2 broadcast packets [Address Resolution Protocol (ARP), and so forth] with each other. Failover protocol packets cannot be routed at Layer 3.
Q. I have set up failover between two FWSMs, but they are not syncing. What could be the problem?
A. Ensure that your configuration meets the following requirements for successful failover.
Both FWSMs must run the same version of code (FWSM1.1(x).
Both FWSMs must have the same number of VLANs.
A Layer 2 connection must exist between all VLANs on the FWSMs. If the FWSMs exist in different chassis with a trunk configured between them, verify that all VLANs exist and are allowed on the trunk. For more information on how to configure and troubleshoot trunks, refer to the following documents.
SampleConfiguration: 802.1q Trunking Between Catalyst Switches Running CatOS and Integrated Cisco IOS (Native Mode)
Q. How many VLAN interfaces does the FWSM2.2 support in virtual (multiple) mode?
A. FWSM version 2.2 supports up to 1000 VLANs per blade in routed multiple mode and 250 VLANs per security context in routed multiple mode until the 1000VLAN limitation is reached per blade, or 4000 VLANs per chassis. Multiple Transparent mode supports two VLAN interfaces per context and they can not be shared with other contexts on the blade.
Q. Can contexts share VLAN interfaces?
A. Yes, in routed mode in some cases. Sharing is not possible in transparent mode in FWSM2.2 but may be allowed in future releases.
Q. Can I allow users to manage their individual contexts?
A. Yes. Users can use PDM4.0 or CLI to manage their context. If a user logs into a context, he/she is not allowed to switch to a different context. The FWSM administrator can change to any context if they log in to the admin context first.
Q. Do I need a license to run multiple contexts?
A. Maybe. You are allowed to configure two contexts and an admin context without a license. Additional contexts will require a license. A tiered licensing structure is provided with 20, 50, and 100 context licenses available. The maximum number of contexts is equal to the license tier plus 1 admin context.
Q. Does my standby failover FWSM require a license?
A. Yes. The standby FWSM requires the same license as the active unit and the context numbers must match. This differs from the PIX, which has a different license for the Active and standby units (UR/R).
Q. Can I re-use my license key if I replace a FWSM?
A. No. The license key is associated with the FWSM hardware serial number, and can not be transferred. A new key will need to
Q. Does the license have to be renewed every year?
A. No. The license is good indefinitely. There is no expiration date.
Q. Do I need to reboot the blade if I upgrade licenses?
A. No. A reboot is not required.
Q. Can I configure contexts for both routed and transparent mode on the same FWSM?
A. Not in FWSM2.2. The ability to mix transparent and routed contexts on the same blade is planned for a future release.
Q. How many VLANs does the FWSM support?
A. FWSM version 1.1 supports 100 VLANs and FWSM version 2.2 supports up to 1000 VLANs per blade in routed multiple mode and 250 VLANs per security context in routed multiple mode. Transparent mode supports two interfaces per context (they can not be shared with other contexts).
Q. How many ACLs will the FWSM support?
A. FWSM1.1 supports about 80,000 rules. FWSM2.2 supports about 63,000 rules for the entire blade. In FWSM we store the following types of rules as ACLs in the same tree:
All these together comprise the 80K limit in 1.1 (and 2.2 as well). FWSM 1.1 does not restrict the number of individual rule types, so you could potentially configure 80K AAA commands and the user will not be able to get anything else in there. FWSM 2.2 limits the number of individual rules types that a user can configure. The following limits are applied for FWSM 2.2:
These numbers are derived using the following distribution:
Note: X = 80,000 for single mode and 12130 per context in multi-mode
Total Rules (best case) X.
5% of X = Filter MAX
1% of X = Established Rule MAX
5% of X = AAA Rule MAX
3% of X = Console (icmp/telnet/ssh/http) Rule MAX
5% of X = Policy-based NAT Rule MAX
80% of X = ACL Rule MAX
3000 = Dynamic ACL
Q. Where can I find information on the error messages I am seeing on my FWSM?
Error Message Decoder (
registered customers only) provides details on many FWSM error messages. Product documentation on system messages also contains useful information. If you require further assistance, please contact Cisco Technical Support.
Q. Where can I find information on existing bugs for my FWSM?
Q. Does the FWSM support the access-list compiled command?
A. The FWSM automatically compiles access lists into hardware after 1.0 seconds of inactivity at the command-line interface (CLI), there is no need for turbo access lists. FWSM version 2.2 offers the additional functionality of being able to nominate when the access lists are compiled through use of a manual commit option.
Q. Does the FWSM support the IOS Open Shortest Path First (OSPF) auto-cost reference-bandwidth command?
A. No. The FWSM is not aware of the physical ports connected to it. OSPF cost must be configured manually per interface using the
ospf cost command.
Q. Can I run Open Shortest Path First (OSPF) protocol in a topology where two different interfaces of the FWSM connect to the
A. Yes. This functionality is supported in versions 2.2 and later. Note that OSPF and RIP are not supported when operating in
Q. What routing protocols are supported by the FWSM?
Q. Is Multicast (Internet Group Management Protocol [IGMP] v2 and Stub Multicast Routing) supported on the FWSM?
Q. Does the FWSM support third party URL and FTP Filtering?
A. Yes. Websense is supported in versions 1.1 and later, with additional support for N2H2 added in version 2.2.
Q. Why are fragmented packets dropped by the FWSM?
A. In FWSM1.1 fragmented packets can not traverse the FWSM by default. You can use the
fragment command to configure this feature. This behavior differs from that of the PIX Firewall. In FWSM2.2 fragmented packets can traverse the FWSM, as the default setting is now the same as the PIX (200)
Common protocols that use fragmented packets are Open Shortest Path First (OSPF) and Network File System (NFS).
Q. Can I terminate VPN connections on my FWSM?
A. VPN functionality is not supported on the FWSM except for management connections terminating on the FWSM. Termination of VPN connections for traffic flowing through the FWSM should be performed on the switch and/or VPN Services Module. The 3DES license is provided for management purposes only, such as connecting to the management interface on the FWSM through a low-security interface via Telnet, Secure Shell (SSH), and Secure HTTP (HTTPS).
Q. Is authentication, authorization, and accounting (AAA) for RADIUS or TACACS+ supported on the FWSM?
The FWSM offers similar functionality to that of the PIX Firewall, with the exceptions of downloadable access lists which are not available on FWSM1.1, but are available on FWSM2.2, and VPNs. With this in mind, you can use the following PIX Firewall documents as guides for FWSM configuration.