Cisco Cisco Catalyst 6500 Series Firewall Services Module Release Notes
12
Release Notes for the Catalyst 6500 Series and Cisco 7600 Series Firewall Services Module, Software Release 3.2(x)
Resolved Caveats
Workaround: None.
•
CSCsy74687
You might experience an unexpected reload in Thread Name: doorbell_poll or Syslog_entry.
Workaround: None.
•
CSCsz74961
FWSM might log incorrect system messages for DNS traffic which are then denied in an ACL. This
occurs only when DNS is enabled.
occurs only when DNS is enabled.
Workaround: None.
•
CSCsz81503
Multicast bi-directional forwarding fails due to an incorrect forwarding entry. The results can be
seen when you use the show np 3 mroute command. This problem can be seen when using OSPF
in redundant FWSM environments, where the FWSM is between the multicast source and the
routing protocol.
seen when you use the show np 3 mroute command. This problem can be seen when using OSPF
in redundant FWSM environments, where the FWSM is between the multicast source and the
routing protocol.
Workaround: Use the clear ospf process command.
•
CSCsz82463
FWSM is not correctly parsing the RTSP setup messages and opens a connection stream on the
wrong port.
wrong port.
Workaround: None.
•
CSCta28599
In certain instances when setting up failover, FWSM may crash and reload due to a problem with
Thread Name: fover_health_monitoring_thread entry.
Thread Name: fover_health_monitoring_thread entry.
Workaround: None.
•
CSCtc23265
After a failover of the FWSM, active H.323 connections through the FWSM might be disconnected.
After the connection is re-established it should work fine. This occurs when H.323 inspection is
enabled, and a failover takes place while the H.323 connections are active through the FWSM. For
example, if a call is made from one H.323 endpoint to another, and the FWSM fails over while the
call is active.
After the connection is re-established it should work fine. This occurs when H.323 inspection is
enabled, and a failover takes place while the H.323 connections are active through the FWSM. For
example, if a call is made from one H.323 endpoint to another, and the FWSM fails over while the
call is active.
Workaround: If NAT is not being performed by the FWSM, disable the H.323 inspection and
permit all necessary connectivity between the H.323 endpoints explicitly via the access-lists on the
FWSM.
permit all necessary connectivity between the H.323 endpoints explicitly via the access-lists on the
FWSM.
•
CSCte02257
A SIP call might not work when SIP inspection is enabled.
Workaround: None.
Resolved Caveats
This section contains resolved caveats in each maintenance release and includes the following topics:
•
•
•