|
|
Table Of Contents
Release Notes for the Cisco 3200 Series Wireless and Mobile Routers for Cisco IOS Release 12.3(2)JL
Determining the Software Version
Upgrading to a New Software Release
New Hardware Features in Release 12.3(2)JL4
New Software Features in Release 12.3(2)JL4
New Hardware Features in Release 12.3(2)JL3
New Software Features in Release 12.3(2)JL3
New Hardware Features in Release 12.3(2)JL2
New Software Features in Release 12.3(2)JL2
New Hardware Features in Release 12.3(2)JL
New Software Features in Release 12.3(2)JL
Open Caveats - Cisco IOS Release 12.3(2)JL4
Resolved Caveats - Cisco IOS Release 12.3(2)JL4
Open Caveats - Cisco IOS Release 12.3(2)JL3
Resolved Caveats - Cisco IOS Release 12.3(2)JL3
Open Caveats - Cisco IOS Release 12.3(2)JL2
Resolved Caveats - Cisco IOS Release 12.3(2)JL2
Open Caveats - Cisco IOS Release 12.3(2)JL1
Resolved Caveats - Cisco IOS Release 12.3(2)JL1
Hardware Caveats - Cisco IOS Release 12.3(3)JL
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco 3200 Series Wireless and Mobile Routers for Cisco IOS Release 12.3(2)JL
October 29, 2007Cisco IOS Release 12.3(2)JL4OL-12925-03These release notes describe new features and significant software components for the Cisco 3200 Series 5-GHz wireless mobile interface card (WMIC), model C3205, which supports Cisco IOS Release 12.3(2)JL. These release notes are updated as needed to describe new memory requirements, new features, new hardware support, software platform deferrals, microcode or modem code changes, related document changes, and any other important changes. Use these release notes with the Cross-Platform Release Notes for Cisco IOS Release 12.3T located on Cisco.com in pdf or html format.
For a list of the software caveats that apply to Release 12.3(2)JL, see the "Caveats" section section, and see the online Caveats for Cisco IOS Release 12.3(2)T document. The caveats document is updated for every 12.3T maintenance release and is located on Cisco.com.
We recommend that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html . If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/tech_tips/index/fn.html.
Contents
•
Limitations and Restrictions
•
•
System Requirements
This section describes the system requirements for Cisco IOS Release 12.3(2)JL and includes the following sections:
•
•
Memory Requirements
This section describes the memory requirements for the Cisco IOS feature sets that are supported by the Cisco IOS Release 12.3(2)JL for the Cisco 3200 series wireless and mobile routers.
Table 1 Recommended Memory for the Cisco 3200 Series Mobile Access Router
5-GHz Wireless Mobile Interface Card (WMIC)
Cisco C3205 WMIC WLAN
Wireless LAN
c3205-k9w7-tar
8 MB
32MB
Hardware Supported
The Cisco IOS Release 12.3(2)JL supports the 5-GHz Wireless Mobile Interface Card (WMIC) for the Cisco 3200 Series Mobile Access Router.
For descriptions of existing hardware features and supported modules, see the configuration guides and additional documents specific to the Cisco 3200 Series Mobile Access Router, which are available on Cisco.com at the following location:
http://www.cisco.com/en/US/products/hw/routers/ps272/tsd_products_support_series_home.html
Determining the Software Version
To determine which version of Cisco IOS software is currently running on the Cisco 3200 Series router, log in to the router and enter the show version EXEC command. The following sample output from the show version command indicates the version number on the second output line.
Router# show versionCisco Internetwork Operating System SoftwareIOS (tm) C3205 Software (C3205-K9W7-M), Experimental Version 12.3(20061011:211650)Copyright (c) 1986-2006 by cisco Systems, Inc.Compiled Wed 11-Oct-06 14:20Image text-base: 0x00003000, data-base: 0x00682E94Upgrading to a New Software Release
For general information about upgrading to a new software release, see the Software Installation and Upgrade Procedures, which are located on Cisco.com.
Feature Set Tables
The Cisco IOS software is packaged in feature sets consisting of software images, depending on the platform. Each feature set contains a specific set of Cisco IOS features. Cisco IOS Release 12.3(2)JL supports the same feature sets as Cisco IOS Releases 12.3, but Release 12.3(2)JL includes new features supported by the Cisco 3200 Series wireless and mobile routers.
Caution
Table 1 lists the features and feature sets that are supported in Cisco IOS Release 12.3(2)JL.
The table uses the following conventions:
•
•
Note
New and Changed Information
•
•
•
•
•
•
•
•
New Hardware Features in Release 12.3(2)JL4
There are no new hardware features in this release.
New Software Features in Release 12.3(2)JL4
There are no new software features in this release.
New Hardware Features in Release 12.3(2)JL3
There are no new hardware features in this release.
New Software Features in Release 12.3(2)JL3
There are no new software features in this release.
New Hardware Features in Release 12.3(2)JL2
There are no new hardware features in this release.
New Software Features in Release 12.3(2)JL2
There are no new software features in this release.
New Hardware Features in Release 12.3(2)JL
The 5-GHz Wireless Mobile Interface Card (WMIC) is a mobile interface card (MIC) in a standard PC/104-Plus form factor. It is one component of the Cisco 3200 Series wireless and mobile routers, connected to the router internally through a 10/100 Fast Ethernet interface, and provides a 5-GHz wireless interface for ETSI the regulatory domain.
The 5-GHz Wireless Mobile Interface Card (WMIC) can be configured as a:
•
•
•
•
The key features of the Wireless Mobile Interface Card (WMIC) include the following:
•
•
New Software Features in Release 12.3(2)JL
The following sections describe the new software features supported by the Cisco 3200 Series wireless and mobile routers for Cisco IOS Release 12.3(2)JL:
•
•
5 GHz Frequency Band
For different countries or regulatory domains, channelization is different. ETSI regulatory domain defines 5.15 GHz to 5.25 GHz for indoor use, 5.25 GHz to 5.35 GHz for indoor or outdoor use, and 5.47 GHz to 5.725 GHz for outdoor only. FCC regulatory domain defines 5.15 GHz to 5.25 GHz for indoor use, 5.25 GHz to 5.35 GHz for indoor or outdoor use, and 5.725 GHz to 5.825 GHz for outdoor only.
The 5.0 GHz radio in the Cisco 3200 Series router (currently available as the Cisco 3205 WMIC) supports the following US and ETSI channels:
•
•
•
•
802.11h (DFS and TPC)
802.11h is a protocol enhancement designed to add two new feature enhancements in the 5 GHz band. Approved in September, 2003, the IEEE 802.11h standard defines mechanisms to ensure that 802.11h WLAN devices operate according to regulatory requirements for the 5 GHz spectrum. These mechanisms are Dynamic Frequency Selection (DFS) and Transmission Power Control (TPC). DFS selects the radio channel at the access point to minimize interference with military radar. TPC limits the transmitted power to the minimum power level needed to reach the furthest user. In addition to meeting regulatory requirements, DFS and TPC can be leveraged to improve the deployment, operation and management of WLANs.
To date, regulatory requirements governing the use of the 5 GHz band vary from country to country, slowing broad market adoption of 802.11h. In response to these barriers to adoption, the International Telecommunication Union (ITU) recommended a standard for WLANs to share the 5 GHz spectrum with primary-use devices such as military radar systems.
The Cisco 3205 WMIC supports 802.11h for ETSI regulatory domain only.
Limitations and Restrictions
The following sections describe limitations concerning the new hardware and software features supported by the Cisco 3200 Series WMIC for Cisco IOS Release 12.3(2)JL.
•
•
Caveats
Caveats describe unexpected behavior or defects in the Cisco IOS software releases. Severity 1 caveats are the most serious caveats, severity 2 caveats are less serious, and severity 3 caveats are the least serious of these three severity levels.
Note
This sections contains the following information:
•
•
•
•
•
•
•
•
•
Open Caveats - Cisco IOS Release 12.3(2)JL4
There are no open caveats in this release.
Resolved Caveats - Cisco IOS Release 12.3(2)JL4
CSCsj81502 show pagp clis are not displaying the correct informationSymptom In release 12.2(33)SXH or 12.2(18)SXF10 releases, the output of 'show pagp neighbor' command may truncate the neighbor device name and port name fields by 1 character. This is just a display issue and has no functional impact on the PAGP protocol.
Conditions
1.
2.
Workaround
CSCsj66692 Data integrity traceback seen in voip/ccapi/ccapi_call.cSymptom Data corruption copy error tracebacks are seen on the console or output from the show logging command.
For example:
%DATACORRUPTION-1-DATAINCONSISTENCY: copy error, -PC= 0x41224EFC, -Traceback= 0x4153A7D0 0x4155BA0C 0x4157FAF0 0x41224EFC 0x41DDC0A8 0x41DDC1980x41DC6D84 0x41DF3B0C 0x41DC506C 0x41DCE5A4 0x41D91AF8 0x41D90F88 0x41D9BEFC0x41D9C0C0 0x41DAEA68Conditions
Workaround
CSCsk44257 WMIC 3205 RTS/CTS drops the links when used with encryptionSymptom When RTS/CTS is deployed on two WMIC acting as root and non-root in conjunction to encryption WPA/TKIP/PSK, link between the two WMICS might experience RTS retries causing disassociation when the RTS retries threshold is reached.
Conditions
Workaround
CSCsg39295 Syslog displays password if SCP or FTP selected in CISCO-COPY-CONFIG-MIBSymptom Password information may be displayed in a Syslog message as follows:
%SYS-5-CONFIG_I: Configured from scp://userid:password@10.1.1.1/config.txt by consoleConditions
Workaround
CSCeb69473 connect '/terminal-type' command memory corruptionSymptom Device crashes with a segmentation violation (SegV) exception.
Conditions
router>connect 192.168.0.1 login /terminal-type aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaTrying 192.168.0.1...Openlogin:*** System received a SegV exception ***signal= 0xb, code= 0x1100, context= 0x82f9e688PC = 0x61616160, Vector = 0x1100, SP = 0x833ae5a8Workaround
1.
For a complete description of authorization commands, refer to the following links:
–
–
–
2.
–
3.
–
–
CSCeg62070 Tracebacks noticed with Radius configs through HTTP PostSymptom Tracebacks or crash are seen during HTTP transactions with long URLs.
Conditions
Workaround
Open Caveats - Cisco IOS Release 12.3(2)JL3
There are no open caveats in this release.
Resolved Caveats - Cisco IOS Release 12.3(2)JL3
CSCsj18014 Caller ID string received with extra charactersSymptom A caller ID may be received with extra characters.
Conditions
Workaround
CSCed26739 mm/gk/gk_cli.c:CLI:gw-type-prefix possible buffer overflowSymptom The router will reload if "she run" is given after a tech-prefix terminating with a large number of '.'s is configured as follows:
conf tgatekeepergw-type-prefix 1234......................................................Conditions
conf tgatekeepergw-type-prefix1234......................................................and enter command sh runWorkaround
CSCsj66513 Traceback detected at DNQueuePeersSymptom Traceback found at DNQueuePeers
Conditions
Workaround
CSCsh66369 Traceback seen at rpmxf_dg_db_initSymptom Tracebacks seen while running metal_vpn_cases.itcl script
Conditions
Workaround
CSCdz55178 QoS profile name of more then 32 chars will crash the routerSymptom System reloads unexpectedly or other serious side-affects such as memory corruption occur.
Conditions
For example:
cable qos profile 12 name g711@10ms_for_any_softswitch_Traa^C00000000011111111111222222222333^12345678901234567890123456789012||PROBLEM (Variable Overflowed).Workaround
Further Problem Description: The variable which holds the value for the string name only allows for 32 characters and the code did not properly truncate names longer than the associated buffer.
This caused other locations in memory to be corrupted.
CSCsj52927 DATACORRUPTION-1-DATAINCONSISTENCY message in show logSymptom DATACORRUPTION-1-DATAINCONSISTENCY messages are seen in 'show log'
Conditions
Workaround
CSCsb79076 MGCP RSVP enabled calls fails due to spurious error @ qosmodule_mainSymptom %SYS-3-TIMERNEG errors and tracebacks are observed while making MGCP RSVP calls on a analog (RGW) setups. Observed in 12.4(3.9)T1 IOS version.
Workaround
CSCsj16292 DATACORRUPTION-1-DATAINCONSISTENCY: copy errorSymptom Following an upgrade to 12.2(18)SXF9, the following message may be displayed:
%DATACORRUPTION-1-DATAINCONSISTENCY: copy error-Traceback=Conditions
Workaround
CSCsj18014 Caller ID string received with extra charactersSymptom A caller ID may be received with extra characters.
Conditions
Workaround
CSCsj44081 Improvements in diagnostics and instrumentationCisco IOS Software has been enhanced with the introduction of additional software checks to signal improper use of internal data structures. This enhancement was introduced in select Cisco IOS Software releases published after April 5, 2007.
Details: With the new enhancement in place, IOS will emit a %DATACORRUPTION-1-DATAINCONSISTENCY error message whenever it detects an inconsistency in its internal data structures. This is a new error message. The following is an example.
The %DATACORRUPTION-1-DATAINCONSISTENCY error message is preceded by a timestamp
May 17 10:01:27.815 UTC: %DATACORRUPTION-1-DATAINCONSISTENCY: copy errorThe error message is then followed by a traceback.
It is important to note that this error message does not imply that packet data is being corrupted. It does, however provide an early indicator of other conditions that can eventually lead to poor system performance or an IOS restart.
Recommended Action Collect "show tech-support" command output and open a service request with the Technical Assistance Center (TAC) or designated support organization. Pay particular attention to any other error messages or error symptoms that accompany the %DATACORRUPTION-1-DATAINCONSISTENCY message and note those to your support contact.
Open Caveats - Cisco IOS Release 12.3(2)JL2
There are no open caveats in this release.
Resolved Caveats - Cisco IOS Release 12.3(2)JL2
There ere no closed careats for this release.
Open Caveats - Cisco IOS Release 12.3(2)JL1
There are no open caveats in this release.
Resolved Caveats - Cisco IOS Release 12.3(2)JL1
CSCsd85587A vulnerability has been discovered in a third party cryptographic library which is used by a number of Cisco products. This vulnerability may be triggered when a malformed Abstract Syntax Notation One (ASN.1) object is parsed. Due to the nature of the vulnerability it may be possible, in some cases, to trigger this vulnerability without a valid certificate or valid application-layer credentials (such as a valid username or password).
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
The vulnerable cryptographic library is used in the following Cisco products:
–
–
–
–
–
This vulnerability is also being tracked by CERT/CC as VU#754281.
Cisco has made free software available to address this vulnerability for affected customers. There are no workarounds available to mitigate the effects of the vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.
Note
CSCsb12598Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.
Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.
Cisco IOS is affected by the following vulnerabilities:
–
–
–
Cisco has made free software available to address these vulnerabilities for affected customers. There are workarounds available to mitigate the effects of these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.
Note
A combined software table for Cisco IOS is available to aid customers in choosing a software releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is available at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.
CSCec71950 Crafted IP Option may cause DoS or code executionSymptom Cisco routers and switches running Cisco IOS or Cisco IOS XR software may be vulnerable to a remotely exploitable crafted IP option Denial of Service (DoS) attack. Exploitation of the vulnerability may potentially allow for arbitrary code execution. The vulnerability may be exploited after processing an Internet Control Message Protocol (ICMP) packet, Protocol Independent Multicast version 2 (PIMv2) packet, Pragmatic General Multicast (PGM) packet, or URL Rendezvous Directory (URD) packet containing a specific crafted IP option in the packet's IP header. No other IP protocols are affected by this issue.
Workaround
This advisory is available at:
http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml
CSCed95187 IP ID field is predictable for connectionless RST packetsSymptom RST packets sent in response to a TCP SYN packet received by the device on a non-listening port contain a non-randomized Identification value on the IP header.
Conditions
Workaround
Further Problem Description:
From RFC791, the description of the Identification field is: Identification
The choice of the Identifier for a datagram is based on the need to provide a way to uniquely identify the fragments of a particular datagram. The protocol module assembling fragments judges fragments to belong to the same datagram if they have the same source, destination, protocol, and Identifier.
Thus, the sender must choose the Identifier to be unique for this source, destination pair and protocol for the time the datagram (or any fragment of it) could be alive in the internet. It seems then that a sending protocol module needs to keep a table of Identifiers, one entry for each destination it has communicated with in the last maximum packet lifetime for the internet.
Also from RFC791: The IP ID is before the flags and fragment offset fields.
3.1. Internet Header Format
Example Internet Datagram Header
A summary of the contents of the internet header follows:
0 1 2 30 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+|Version| IHL |Type of Service| Total Length |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Identification |Flags| Fragment Offset |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Time to Live | Protocol | Header Checksum |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Source Address |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Destination Address |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Options | Padding |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+CSCeh60551 certificate crashes 12.3.4.JA APSymptom Certain malformed client certificates may cause an Access Point (AP) to crash.
Conditions
Workaround
CSCek26492 Enhancements to Packet Input Path.Symptom A router may crash if it receives a packet with a specific crafted IP option as detailed in Cisco Security Advisory: Crafted IP Option Vulnerability:
http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml
Conditions
Workaround
http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml
CSCek37177 malformed tcp packets deplete processor memory.Symptom The Cisco IOS Transmission Control Protocol (TCP) listener in certain versions of Cisco IOS software is vulnerable to a remotely-exploitable memory leak that may lead to a denial of service condition.
Conditions
Workaround
This advisory is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-tcp.shtml
CSCsd92405 router crashed by repeated SSL connection with malformed finished messageSymptom A router crashes when receiving multiple malformed TLS and/or SSL3 finished messages. A valid username and password are not required for the crash to occur.
Conditions
Workaround
CSCse04560 tftp-server allows for information disclosureSymptom A tftp client trying to transfer a file from a Cisco IOS device configured as a tftp server and which is denied by an ACL receives a different result depending if the file is being offered for download or not. This may allow a third party to enumerate which files are available for download.
Conditions
tftp-serverflash:filename1access-list-numberaccess-list access-list-numberpermit 192.168.1.00.0.0.255access-list access-list-numberdeny anyWorkaround
1.
Configure and attach an access list to every router interface active and configured for IP packet processing. For example:
access-list access-list-numberremark --- the following hostsand networks areaALLOWED for TFTP accessaccess-list access-list-numberpermit udp hostsource_1hostinterface_address_1eq 69access-list access-list-numberpermit udp hostsource_2hostinterface_address_2eq 69access-list access-list-numberpermit udp source source-wildcardhostinterface_address_1eq 69access-list access-list-numberpermit udp source source-wildcardhostinterface_address_2eq 69access-list access-list-numberremark --- everyone else isDENIED for TFTPaccessaccess-list access-list-numberdeny udp any hostinterface_address_1eq 69access-list access-list-numberdeny udp any hostinterface_address_2eq 69access-list access-list-numberremark --- any other trafficto/through the routeris allowedaccess-list access-list-numberpermit ip any anyinterface Ethernet0/0ip access-group access-list-numberinOnce the tftp server in Cisco IOS is enabled and listening by default on all interfaces enabled for IP processing, the access list would need to deny traffic to each and every IP address assigned to any active router interface.
2.
Configure and apply a CoPP policy.
For example:
access-list access-list-numberremark --- Do not police TFTPtraffic from trustedhosts and networksaccess-list access-list-numberdeny udp hostsource_1 anyeq 69access-list access-list-numberdeny udp source source-wildcardany eq 69access-list access-list-numberremark --- Police TFTP trafficfrom untrustedhosts and networksaccess-list access-list-numberpermit udp any any eq69access-list access-list-numberremark --- Do not police anyother traffic goingto the routeraccess-list access-list-numberdeny ip any anyclass-map match-all tftp-classmatch access-group access-list-numberpolicy-map control-plane-policy! Drop all traffic that matches the class tftp-classclass tftp-classdropcontrol-planeservice-policy input control-plane-policy
Note
3.
Although often difficult to block traffic transiting your network, identifying traffic which should never be allowed to target your infrastructure devices and blocking this traffic at the border of your network is possible. Infrastructure ACLs are considered a network security best practice and should be considered as a long-term addition to good network security as well as a workaround for this specific vulnerability. The white paper entitled "Protecting Your Core: Infrastructure Protection Access Control. Lists" presents guidelines and recommended deployment techniques for iACLs:
http://www.cisco.com/warp/public/707/iacl.html
4.
For distributed platforms, rACLs may be an option starting in Cisco IOS Release 12.0(21)S2 for the Cisco 12000 series GSR and Cisco IOS Release 12.0(24)S for the Cisco 7500 series. The receive access lists protect the device from harmful traffic before the traffic can impact the route processor. Receive path ACLs are considered a network security best practice, and should be considered as a long-term addition to good network security, as well as a workaround for this specific vulnerability. The CPU load is distributed to the line card processors and helps mitigate load on the main route processor. The white paper entitled "GSR: Receive Access Control Lists" will help identify and allow legitimate traffic to your device and deny all unwanted packets:
http://www.cisco.com/warp/public/707/racl.html
Note
CSCse05736 A router running RCP can be reloaded with a specific packetSymptom A router that is running RCP can be reloaded by a specific packet.
Conditions
–
–
–
Workaround
CSCse78963 adopt new default summer-time rules from EPA BADCODE BUGSymptom Starting calendar year 2007, daylight savings summer-time rules may cause Cisco IOS to generate timestamps (such as in syslog messages) that are off by one hour.
Conditions
clock summer-time zone recurring
This command uses United States standards for daylight savings time rules by default. The Energy Policy Act of 2005 (H.R.6.ENR), Section 110 changes the start date from the first Sunday of April to the second Sunday of March, and it changes the end date from the last Sunday of October to the first Sunday of November.
Workaround
clock summer-time PDT recurring 2 Sun Mar 2:00 1 Sun Nov 2:00
(this example is for the US/Pacific time zone)
CSCse85200 Inadequate validation of TLVs in cdpSymptom Specifically crafted CDP packets can cause a router to allocate and keep extra memory. Exploitation of this behavior by sending multiple specifically crafted CDP packets could cause memory allocation problems on the router.
Conditions
Workaround
CSCse95758 Access Lists support for all CONFIG-COPY-MIB protocols under snmp-serverSymptom Customers can use an access list to restrict TFTP configuration transfers that are initiated via SNMP by using the command snmp-server tftp-server-list access-list. This restriction is not possible for theFTP, RCP, and SCP protocols.
Conditions
for SNMP. The following sample configuration causes the platform to reject configuration file transfers via SNMP from all hosts except the TFTP server that is specified in access list 5:
snmp-server tftp-server-list 5
access-list 5 permit 10.1.1.1
snmp-server community private RW 5
snmp-server tftp-server-list 5
Workaround
1) Apply a more general access list to restrict traffic to and from the affected platform.
2) Disallow configuration copy from SNMP by excluding CISCO-CONFIG-COPY-MIB using snmp views.
3) Disable the SNMP server. Fixed Software Information:
Access-List Support for CISCO-CONFIG-COPY-MIB
The snmp-server file-transfer access-group command is introduced to restrict configuration transfers that are initiated via the Simple Network Management Protocol (SNMP). Supported transfer protocols are TFTP, FTP, Remote Copy Protocol (RCP), Secure Copy Protocol (SCP), and Secured File Transfer Protocol (SFTP). This command replaces the snmp-server tftp-server-list command. For detailed information about the snmp-server file-transfer access-group command, see the Cisco IOS Network Management Command Reference, Release 12.4.
CSCsg47917 WMIC takes over 10+ minutes to associate when set distance = 99Symptom WMIC takes over 10+ minutes to associate when distance = 99
Conditions
Workaround
CSCsg70355 adopt new default summer-time rules from Energy Policy Act of 2005Symptom Starting in calendar year 2007, daylight savings summer-time rules may cause Cisco IOS to generate timestamps (such as in syslog messages) that are off by one hour.
Conditions
clock summer-time zone
recurring
uses United States standards for daylight savings time rules by default. The Energy Policy Act of 2005 (H.R.6.ENR), Section 110 changes the start date from the first Sunday of April to the second Sunday of March. It changes the end date from the last Sunday of October to the first Sunday
of November.
Workaround
clock summer-time PDT
recurring 2 Sun Mar 2:00 1 Sun Nov 2:00
(This example is for the US/Pacific time zone.)
Note
CSCsg95833 Redundant HTML subdir generated by c3202/3205 WMIC tar imageSymptom There is a confusion with flash memory content which includes empty HTML subdirectory under main image directory on both c3202 and c3205 platform while document describes no GUI interface supported.
Conditions
Directory of flash:/c3205-k9w7-mx/
16 drwx 64 Jan 1 1970 00:07:59 +00:00 html
18 -rwx 3425677 Jan 1 1970 00:11:36 +00:00 c3205-k9w7-mx
19 -rwx 256 Jan 1 1970 00:11:36 +00:00 info
Directory of flash:c3205-k9w7-mx.123/html/
17 drwx 0 Jan 1 1970 00:07:59 +00:00 level
Workaround
bridge: rmdir flash:/c3205-k9w7-mx/html/level
bridge: rmdir flash:/c3205-k9w7-mx/html
To install new fixed image run following command at bootloader prompt:
bridge: tar tftp://<tftp server ip addr>/c3205-k9w7-mx flash:
Hardware Caveats - Cisco IOS Release 12.3(3)JL
CSCek56714Symptom Low throughput for Uni-Dir at Channel 100 (5.5 GHz)
See the Hardware release note for more infomation at:
http://www.cisco.com/en/US/products/hw/routers/ps272/prod_release_note09186a00806547c0.html
Additional References
http://www.cisco.com/en/US/products/hw/routers/ps272/prod_release_note09186a00806547c0.html#wp60567
Your product shipped with a minimal set of printed documentation. The full set of documentation is available online at: http://www.cisco.com/en/US/products/hw/routers/ps272/tsd_products_support_series_home.html
Release-Specific Documents
Cisco 3200 Series Router Product Release Notes—This document. It provides caveats and information on accessing documentation and obtaining technical assistance for the Cisco 3200 Series Router.
Platform-Specific Documents
The following documentation is available at the www.cisco.com>Technical Support & Documentation>Routers>Cisco 3200 Series Routers unless otherwise specified:
Cisco 3200 Series Router Hardware Reference Guide—Descriptions of the Cisco 3200 Series Mobile Access Router enclosures and mobile interface cards.
Cisco 3200 Series Wireless MIC Software Configuration Guide—Example procedures for using the IOS commands to configure the Cisco Wireless Mobile Interface Card (WMIC).
Configuration Guide for the Cisco 3200 Series Router—Example procedures for using the Cisco IOS commands to configure assembled Cisco 3200 Series routers.
Cisco 3200 Series Mobile Access Router Reference Sell Document—An overview of the reference sell program and components for the Cisco 3200 Series routers.
Cisco 3200 Rugged Enclosure Assembly Guidelines—Guidelines for adding or removing cards from the Cisco 3200 Router MIC stack in the Cisco 3200 Rugged Enclosure Assembly at http://www.cisco.com/en/US/partner/products/hw/routers/ps272/prod_technical_reference_list.html (A restricted document that requires a CCO password to access.)
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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
Use this document in conjunction with the documents listed in the "Additional References" section.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0710R)
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.
© 2006-2007, Cisco Systems, Inc. All rights reserved
Posted: Wed Nov 21 21:41:57 PST 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
