 Feedback
|
Table Of Contents
Release Notes for Cisco MWR 1941-DC Mobile Wireless Edge Router for Cisco IOS Release 12.2(15)MC2h
System Configuration Requirements
Determining the Software Version
Upgrading to a New Software Release
Upgrading to a New ROM Monitor Version
New Features in the Cisco IOS Release 12.2(15)MC2h
Support for 6 T1/E1 Interfaces per/MWR
Support for Enhanced Link Noise Monitoring (LNM)
New Features in the Cisco IOS Release 12.2(15)MC2g
New Features in the Cisco IOS Release 12.2(15)MC2f
New Features in the Cisco IOS Release 12.2(15)MC2e
New Features in the Cisco IOS Release 12.2(15)MC2b
New Features in the Cisco IOS Release 12.2(15)MC2a
New Features in the Cisco IOS Release 12.2(15)MC2
New Features in the Cisco IOS Release 12.2(15)MC1
Ignoring the IP ID in RTP/UDP Header Compression
Configuring ACFC and PFC Handling During PPP Negotiation
Configuring the cUDP Flow Expiration Timeout Duration
Limitations, Restrictions, and Important Notes
Caveats in Cisco IOS Release 12.2(15)MC2h
Caveats in Cisco IOS Release 12.2(15)MC2g
Caveats in Cisco IOS Release 12.2(15)MC2f
Caveats in Cisco IOS Release 12.2(15)MC2e
Caveats in Cisco IOS Release 12.2(15)MC2b
Caveats in Cisco IOS Release 12.2(15)MC2a
Configuring RTP/UDP Compression
The show ip rtp header-compression Command
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco MWR 1941-DC Mobile Wireless Edge Router for Cisco IOS Release 12.2(15)MC2h
October 27, 2006
Cisco IOS Release 12.2(15)MC2h
OL-13984-17
These release notes are for the Cisco MWR 1941-DC Mobile Wireless Edge Router for Cisco IOS Release 12.2(15)MC2h. These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and changes to the microcode and related documents.
For a list of the software caveats that apply to Cisco IOS Release 12.2(15)MC2h, see the "Caveats in Cisco IOS Release 12.2(15)MC2h" section. To review the release notes for Cisco IOS Release 12.2, go to www.cisco.com and click Documentation in the Support menu. Then click on Cisco IOS Software, and select Cisco IOS Software Releases 12.2 Mainline from the Cisco IOS Software Release 12.2 Family menu item. Next, under the General Information menu item, click Release Notes > Cross-Platform Release Notes for Cisco IOS Release 12.2, Part 5:Caveats. Alternately, you can click Part 6, Part 7, or Part 8 for these Caveats. Parts 5 through 8 include Caveats from Cisco IOS Release 12.2(1) through 12.2(37).
Contents
This document contains the following sections:
•
System Configuration Requirements
•
•
•
•
•
•
•
•
•
•
•
Introduction
The Cisco MWR 1941-DC Mobile Wireless Edge Router running Cisco IOS Release 12.2(15) MC2h software is a networking platform optimized for use in mobile wireless networks. It extends IP connectivity to the cell site and Base Transceiver Station (BTS), and through a Fast Ethernet interface to the BTS, provides bandwidth-efficient IP transport of voice and data bearer traffic, as well as maintenance, control, and signalling traffic, over the leased line backhaul network between the BTS and leased line termination and aggregation node via compression (cRTP/cUDP) and packet multiplexing (PPPMux and MLPPP). It supports a limited set of interfaces and protocols, but offers high performance at a low cost while meeting the critical requirements for deployment in cell sites, including small size, extended operating temperature range, high availability, and DC input power flexibility.
System Configuration Requirements
When implemented in a Cisco IP Radio Access Network (IP-RAN) solution, the Cisco MWR 1941-DC router requires the following system configuration:
•
•
Network Time Protocol must be configured. The Cisco MWR 1941-DC router uses NTP to maintain a clocking source for the proper time stamping of system messages and log files.
•
When not using the Cisco MWR 1941-DC router in a redundant configuration, the standalone option must be configured from redundancy mode.
When using the Cisco MWR 1941-DC router in a redundant configuration:
–
–
–
•
You cannot disable CEF on the MWR 1941-DC. Commands such as no ip cef will display an error message "%Cannot disable CEF on this platform." Some commands, such as no ip route-cache cef, will not return an error message, however, CEF will not be disabled regardless of whether or not an error message is displayed.
•
In case of a tie in priority, HSRP uses the IP address to determine the active router. Therefore, you should ensure that the order of the IP addresses of the E1/T1 interfaces of the active router corresponds to the order of the IP addresses of the E1/T1 interfaces of the standby router.
Memory Recommendations
Determining the Software Version
To determine the version of Cisco IOS software running on your Cisco MWR 1941-DC router, log in to the Cisco MWR 1941-DC and enter the show version EXEC command:
router> show versionCisco Internetwork Operating System SoftwareIOS (tm) 1900 Software (MWR1900-I-MZ), Version 12.2(15)MC2a, EARLY DEPLOYMENT RELEASESOFTWARE (fc1)Upgrading to a New Software Release
For general information about upgrading to a new software release, refer to Software Installation and Upgrade Procedures located at the following URL:
http://www.cisco.com/en/US/products/hw/routers/tsd_products_support_category_home.html
Upgrading to a New ROM Monitor Version
The Cisco MWR 1941-DC router ROM Monitor (ROMMON) consists of two modules:
•
•
Note
Note
Note
To upgrade the ROMMON version on your Cisco MWR 1941-DC router, complete these steps from EXEC mode:
Step 1
Step 2
Router#dir slot0:Directory of slot0:/3 -rw- 871 Mar 01 1993 00:05:02 MWR1900-3-default.cfg4 -rw- 610704 Mar 01 1993 00:10:30 MWR1900_RM2.srec.122-8r.MC3Step 3
Router# upgrade rom-monitor file slot0:MWR1900_RM2.srec.122-8r.MC3This command will reload the router. Continue? [yes/no]:yStep 4
ROMMON image upgrade in progressErasing boot flasheeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeProgramming boot flash ppppNow ReloadingSystem Bootstrap, Version 12.2(20010915:181836) DEVELOPMENT SOFTWARECopyright (c) 1994-2001 by cisco Systems, Inc.Running new upgrade for first timeSystem Bootstrap, Version 12.2(8r)MC3, RELEASE SOFTWARE (fc1)TAC Support:http://www.cisco.com/tacCopyright (c) 2002 by cisco Systems, Inc.mwr1900 processor with 131072 Kbytes of main memoryMain memory is configured to 64 bit mode with parity disabledUpgrade ROMMON initializedrommon 1 >
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco MWR 1941-DC router for Cisco IOS Release 12.2(15)MC software.
New Features in the Cisco IOS Release 12.2(15)MC2h
The following features were introduced in Cisco IOS Release 12.2(15)MC2h:
•
•
•
Support for 6 T1/E1 Interfaces per/MWR
The new MWRs support up to 6 T1/E1 interfaces on the platform. These interfaces are configured by IOS software as controller t1 0/4 and controller t1 0/5 for the T1 interface, and as controller e1 0/4 and controller e1 e1 0/5 for the E1 interface. In effect, the multilink interface can now be configured with 6 T1 or 6 E1 interfaces under it. Also, the number of serial interfaces can increase depending upon how the T1/E1 interfaces are split up by the configuration. All controller specific commands are applicable to the new T1/E1 interfaces
Support for 1800 CIDs per/MWR
With Cisco IOS Release 12.2(15)MC2h, the maximum number of connections is increased to 1800 for the interface configuration command ip rtp compression-connections. This command is also used to specify the total number of Real-Time Transport Protocol (RTP) header compression connections that can exist on an interface. The default is 16 CID connections.
Router(config-if)# ip rtp compression-connections number
Number of RTP header compression connections the cache supports in the range of 3 to 1800.
To restore the default value, use the no form of this command.
Support for Enhanced Link Noise Monitoring (LNM)
With Cisco IOS Release 12.2(15)MC2h, LNM algorithm support has been changed or updated. There is no longer support for the existing or previous LNM algorithm. The enhanced LNM algorithm is now supported by default. However, the existing or previous LNM CLI is still used to set the threshold and duration values.
The averaging algorithm is responsible for maintaining the simple moving average of link quality Bit Error Rate (BER), Line Code Violation/Path Code Violation (LCV/PCV) values as and when noise samples arrive. The noise is calculated as a simple moving average for the duration configured. The average noise at any time represents the noise average for the last configured duration in seconds. It is recalculated each second as the noise samples arrive each second. Basically, it's a sliding window of noise averages for the last duration in seconds.
The Benefits of this new algorithm are the following:
•
•
•
•
•
New Features in the Cisco IOS Release 12.2(15)MC2g
No features are introduced in Cisco IOS Release 12.2(15)MC2g.
New Features in the Cisco IOS Release 12.2(15)MC2f
No features are introduced in Cisco IOS Release 12.2(15)MC2f.
New Features in the Cisco IOS Release 12.2(15)MC2e
No features are introduced in Cisco IOS Release 12.2(15)MC2e.
New Features in the Cisco IOS Release 12.2(15)MC2b
No features are introduced in Cisco IOS Release 12.2(15)MC2b.
New Features in the Cisco IOS Release 12.2(15)MC2a
No features are introduced in Cisco IOS Release 12.2(15)MC2a.
New Features in the Cisco IOS Release 12.2(15)MC2
No features are introduced in Cisco IOS Release 12.2(15)MC2.
New Features in the Cisco IOS Release 12.2(15)MC1
The following features were introduced in Cisco IOS Release 12.2(15)MC1:
•
•
•
For information on new features in previous Cisco IOS Release 12.2MC software releases, see the platform release notes:
http://www.cisco.com/univercd/cc/td/doc/product/wireless/ipran/1_0/relnotes/index.htm
Ignoring the IP ID in RTP/UDP Header Compression
With Cisco IOS Release 12.2(8)MC2c, IP ID checking was suppressed in RTP/UDP header compression. With Cisco IOS Release 12.2(15)MC1, a new option has been added to the ip rtp header-compression interface configuration command that allows you to enable or suppress this checking. The default is to suppress.
To suppress IP ID checking, issue the following command while in interface configuration mode:
Router(config-if)# ip rtp header-compression ignore-id
Suppresses the IP ID checking in RTP/UDP header compression.
To restore IP ID checking, use the no form of this command.
This new feature is identified by CSCdz75957.
Configuring ACFC and PFC Handling During PPP Negotiation
With Cisco IOS 12.2(15)MC1, ACFC and PFC handling during PPP negotiation can be configured.
Configuring ACFC Handling During PPP Negotiation
Use the following commands beginning in global configuration mode to configure ACFC handling during PPP negotiation:
Configuring PFC Handling During PPP Negotiation
Use the following commands beginning in global configuration mode to configure PFC handling during PPP negotiation:
To restore the default, use the no forms of these commands.
Note
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122b/122b_15/12b_acf.htm
Configuring the cUDP Flow Expiration Timeout Duration
To minimize traffic flow corruption, cUDP flows now expire after an expiration timeout duration during which no packets are passed. When this duration of inactivity occurs on a flow at the compressor, the compressor sends a full header upon receiving a packet for that flow, or, if no new packet are received for that flow, makes the CID for the flow available for new use. When a packet is received at the decompressor after the duration of inactivity, the packet is dropped and a context state message is sent to the compressor requesting a flow refresh.
The default expiration timeout is 5 seconds. The recommended value is 8 seconds.
Caution
To configure the cUDP flow expiration timeout duration, issue the following command while in multilink interface configuration mode:
Router(config-if)# ppp iphc max-time seconds
Specifies the duration of inactivity, in seconds, that when exceeded causes the cUDP flow to expire. The recommended value is 8.
To restore the default, use the no form of this command.
This new feature is identified by CSCeb44623.
Limitations, Restrictions, and Important Notes
Caution
Caution
Unsupported Cisco IOS Software Features
The Cisco MWR 1941-DC router requires a special version of Cisco IOS software. Not all Cisco IOS software features can be used with the Cisco MWR 1941-DC router as the core routing is handled by the network processor. The following standard Cisco IOS software features are not supported on the Cisco MWR 1900 router:
•
•
•
•
•
•
Upgrading the VWIC-2MFT-T1-DIR Microcode
When upgrading the image on your Cisco MWR 1941-DC router, power cycle the router or perform a microcode reload on the VWIC-2MFT-T1-DIR to ensure that the firmware for the VWIC-2MFT-T1-DIR is updated during the upgrade.
Disabling PPP Multiplexing
To fully disable PPP multiplexing (PPPMux), issue the no ppp mux command on the T1 interfaces of the routers at both ends of the T1 link. If PPP multiplexing remains configured on one side of the link, that side will offer to receive PPP multiplexed packets.
MLP LFI Support
MLP LFI is not supported by the Cisco MWR 1941-DC router. Therefore, MLP LFI must be disabled on peer devices connecting to the Cisco MWR 1941-DC router T1 MLP connections.
ACFC and PFC Support on PPP Interfaces
If upgrading to Cisco IOS Release 12.2(8)MC2c or later for the ACFC and PFC support on PPP interfaces, ensure that you upgrade the MGX-RPM-1FE-CP backcard image first. After doing so, immediately upgrade all MWR 1941-DC routers connected to the MGX-RPM-1FE-CP back card.
Caveats in Cisco IOS Release 12.2(15)MC2h
The following sections list and describe the open and closed caveats for the Cisco MWR 1941-DC router running Cisco IOS Release 12.2(15)MC2h. Only severity 1 through 3 caveats are included.
Caveats describe unexpected behavior in 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.
Caveats in Cisco IOS Releases 12.2 and 12.2 T are also in Cisco IOS Release 12.2(15)MC2h. For information on caveats in Cisco IOS Release 12.2, see Caveats for Cisco IOS Release 12.2. For information on caveats in Cisco IOS Release 12.2 T, see Caveats for Cisco IOS Release 12.2 T. These two documents list severity 1 and 2 caveats and are located on CCO and the Documentation DVD.
Note
http://www.cisco.com/en/US/support/tsd_most_requested_tools.html
Open Caveats
This section lists the open caveats in Cisco IOS Release 12.2(15)MC2h.
•
Description: This caveat addresses the issue of trap loss during an MWR failover when T1/E1 relays on the active MWR are opened before multilink goes down. This issue was addressed originally in wireless_mc and later in v122_15_mc2 throttle, both through CSCea73056. The CSCea73056 fix involves forcing a multilink shutdown just when the relays open on the active MWR during failover, and bringing it back up very soon. This allowed just enough time for routing to converge and queued SNMP traps to pass through the active multilink.
But this fix was found to have other side effects causing loss of network connectivity and traffic outage. It was present in MC2e but had to be backed out in MC2f as a result of traffic outage during re-insertion of a GLI card. This was done through CSCsd25168 with the problem and reasons for backing out explained in detail. While the issue of trap loss is seen inconsistently, this fix always causes loss of traffic.
As a result, an effort is underway to address the trap loss issue by using a solution that does not involve bringing down multilink. The issue is being reproduced on an MC2g image and analyzed accordingly.
Workaround: There is currently no workaround.
•
Description: The 10 SES results for error value less than 832 PCV in the E1 controller with error rate as 6e-5(120) and with lcv and pcv configuration set as follwos:
Link noise monitor settings:
–
–
–
–
For E1-CRC signals, a Severely Errored Second is a second with either 832 or more Path Code Violation error events or one or more OOF defects.
Workaround: There is currently no workaround.
Resolved Caveats
This section lists the caveats that are resolved in Cisco Release 12.2(15)MC2h.
•
Description: When an FE cable is re-inserted into an MWR running with Cisco IOS 12.3(3), instead of a linkUp display, an incorrect linkdown trap type ('2', down) is generated, and an up telltale locIfReason value is displayed.
Workaround: There is currently no workaround.
•
Description: The MWR-1900 does not load rmon commands on reload. The following errors occur on boot.
–
–
After performing a copy tftp start and reloading the device, rmon commands related to HSRP are marked as invalid and are not placed in the running config. The two commands are:
–
–
Workaround: The commands can be entered manually into the running configuration without a problem, After performing copy tftp start, do a wr mem to load commands properly on boot.
•
Description: Remote Authentication Dial In User Service (RADIUS) authentication on a device that is running certain versions of Cisco Internetworking Operating System (IOS) and configured with a fallback method to none can be bypassed. Systems that are configured for other authentication methods or that are not configured with a fallback method to none are not affected. Only the systems that are running certain versions of Cisco IOS are affected. Not all configurations using RADIUS and none are vulnerable to this issue. Some configurations using RADIUS, none and an additional method are not affected.
Workaround: Cisco has made free software available to address this vulnerability. There are workarounds available to mitigate the effects of the vulnerability. For more details see the following URL:
http://www.cisco.com/warp/public/707/cisco-sa-20050629-aaa.shtml
•
Description: The Cisco IOS Stack Group Bidding Protocol (SGBP) feature in certain versions of Cisco IOS software is vulnerable to a remotely-exploitable denial of service condition. Devices that do not support or have not enabled the SGBP protocol are not affected by this vulnerability.
Workaround: Cisco has made free software available to address this vulnerability for affected customers. There are workarounds available to mitigate the effects of the vulnerability. Cisco has published a Security Advisory on this issue; it is available at the following URL:
http://www.cisco.com/warp/public/707/cisco-sa-20060118-sgbp.shtml
•
Description: A vulnerability exists in the IOS HTTP server in which HTML code inserted into dynamically generated output, such as the output from a show buffers command, will be passed to the browser requesting the page. This HTML code could be interpreted by the client browser and potentially execute malicious commands against the device or other possible cross-site scripting attacks. Successful exploitation of this vulnerability requires that a user browse a page containing dynamic content in which HTML commands have been injected.
Workaround: Cisco will be making free software available to address this vulnerability for affected customers. There are workarounds available to mitigate the effects of the vulnerability. This advisory is posted at the following URL:
http://www.cisco.com/warp/public/707/cisco-sa-20051201-http.shtml
•
Description: This DDTS changes how IOS handles packets destined to the router or switch.
When sending ip packet with option 0x89 (strict source route) or 0x83 (loss source route) follow some invalid data, IOS throws out some error messages and trackback. The messages and trackback pop up every 60 seconds as long as the malformed packet is sent to the router.
Workaround: See the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
Caveats in Cisco IOS Release 12.2(15)MC2g
The following sections list and describe the open and closed caveats for the Cisco MWR 1941-DC router running Cisco IOS Release 12.2(15)MC2g. Only severity 1 through 3 caveats are included.
Caveats describe unexpected behavior in 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.
Caveats in Cisco IOS Releases 12.2 and 12.2 T are also in Cisco IOS Release 12.2(15)MC2g. For information on caveats in Cisco IOS Release 12.2, see Caveats for Cisco IOS Release 12.2. For information on caveats in Cisco IOS Release 12.2 T, see Caveats for Cisco IOS Release 12.2 T. These two documents list severity 1 and 2 caveats and are located on CCO and the Documentation DVD.
Note
http://www.cisco.com/en/US/support/tsd_most_requested_tools.html
Note
There are no known open caveats in Cisco IOS Release 12.2(15)MC2g.
Resolved Caveats
This section lists the caveats that are resolved in Cisco Release 12.2(15)MC2g.
•
Description: Multicast packets are dropped by IOS until context is re-established.
This occurs during multicast on one flow at a rate of 100pps or more.
Workaround: Reduce the PPPMux subframe size on the RPM to a size smaller than a compressed multicast packet so that the multicast packets are not PPPMux'd.
•
Description: An RPM router running Cisco software release122-15.MC2e may drop multicast packets across a multilink interface if the ppp mux is configured on that interface.
Workaround: Reduce the PPPMux subframe size on the RPM to a size smaller than a compressed multicast packet so that the multicast packets are not PPPMux'd
Caveats in Cisco IOS Release 12.2(15)MC2f
The following sections list and describe the open and closed caveats for the Cisco MWR 1941-DC router running Cisco IOS Release 12.2(15)MC2f. Only severity 1 through 3 caveats are included.
Caveats describe unexpected behavior in 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.
Caveats in Cisco IOS Releases 12.2 and 12.2 T are also in Cisco IOS Release 12.2(15)MC2f. For information on caveats in Cisco IOS Release 12.2, see Caveats for Cisco IOS Release 12.2. For information on caveats in Cisco IOS Release 12.2 T, see Caveats for Cisco IOS Release 12.2 T. These two documents list severity 1 and 2 caveats and are located on CCO and the Documentation DVD.
Note
http://www.cisco.com/en/US/support/tsd_most_requested_tools.html
Open Caveats
This section lists the caveats that are open in Cisco Release 12.2(15)MC2f.
•
Description: The MWFM or any other NMS system does not get important SNMP traps generated during failover. Up to 50% of the traps are lost.
During failover the Cisco MWR 1900 router software opens the T1/E1 relays on an active router without taking down the Multilink interface first. The Cisco MWR 1900 routing software keeps sending packets into the disconnected interface for the next few seconds until the interface Multilink goes down. Traps are sent and lost. Traps generated after the link is declared down are kept in the SNMP queue waiting to be routing in order to get restored.
Workaround: There is currently no workaround.
Resolved Caveats
This section lists the caveats that are resolved in Cisco Release 12.2(15)MC2f.
•
Description: The insertion of a GLI card to one of the Fast Ethernet (FE) ports of the Cisco MWR1900 router could cause the Multilink PPP interface to flap leading to a traffic outage for few seconds. A Hot Standby Routing Protocol (HSRP) swap over will also happen.
The Cisco MWR1900 routers are configured for HSRP redundancy and a GLI card insertion on the active Cisco MWR1900 router would cause the mlppp interface to go DOWN and come UP and would eventually cause the active Cisco MWR1900 router to become standby, and the standby router would then become the active router.
Workaround: There is no workaround to avoid the Multilink PPP interface from going down. However, to avoid HSRP swap over, the standby <number> preempt delay <seconds> commands can be configured. A value of 3 seconds is recommended.
Caveats in Cisco IOS Release 12.2(15)MC2e
The following sections list and describe the open and closed caveats for the Cisco MWR 1941-DC router running Cisco IOS Release 12.2(15)MC2e. Only severity 1 through 3 caveats are included.
Caveats describe unexpected behavior in 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.
Caveats in Cisco IOS Releases 12.2 and 12.2 T are also in Cisco IOS Release 12.2(15)MC2e. For information on caveats in Cisco IOS Release 12.2, see Caveats for Cisco IOS Release 12.2. For information on caveats in Cisco IOS Release 12.2 T, see Caveats for Cisco IOS Release 12.2 T. These two documents list severity 1 and 2 caveats and are located on CCO and the Documentation DVD.
Note
http://www.cisco.com/en/US/support/tsd_most_requested_tools.html
Open Caveats
This section lists the caveats that are open in Cisco Release 12.2(15)MC2e.
•
Description: Frame slips were observed on port 0/1 if the T1 cable on port 0/0 was disconnected.
This situation occurs when the T1 cable connected to the first VWIC port (either port 0/0 or port 0/2) is pulled out from either the MWR side or the FRSM/MPSM side, and frame slips are seen on the remaining port in the same controller.
Workaround: Connect and disconnect the T1 cable according to following sequence:
1. Connect port 0/0 first and then port 0/1.
2. Disconnect port 0/1 first and then port 0/0
3. Perform the same procedure to ports 0/2 and 0/3.
Resolved Caveats
This section lists the caveats that are resolved in Release 12.2(15)MC2e.
•
Description: Mobile Wireless Fault Mediator (MWFM) or any other Network Management System (NMS) does not receive important Simple Network Management Protocol (SNMP) traps generated during failover. Up to 50% of the traps are lost.
During failover, the MWR 1900 routing software opens T1/E1 relays on the active router without taking down the Multilink interface first. The MWR 1900 routing software keeps sending packets into the disconnected interface for the next few seconds until the Multilink interface goes down. Traps are sent and lost. Traps generated after the link is declared down are kept in the SNMP queue waiting for the routing to become restored.
Workaround: There is currently no workaround.
•
Description: If a virtual access interface is created and that interface is assigned to a multilink group interface by the application of the ppp multilink group group-number interface configuration command, then when the interface goes down, the configuration is not properly removed when the virtual access interface is recycled for reuse.
Perhaps the most visible effect of this symptom, is that if the virtual access interface negotiates to use multilink during a future session (a different use of the virtual access interface than the one when the interface was first created), the interface does not join the designated multilink group interface. Instead, a separate virtual access interface is created for the bundle. This behavior may lead to additional problems since the multilink bundle interface that is created probably does not have the desired configuration that is required for the connection.
This symptom is observed on all Cisco platforms that are running Cisco IOS Release 12.2(5) and later.
Workaround: There is currently no workaround.
•
Description: A router may reload with a bus error when the Point-to-Point protocol (PPP) sessions are disconnected.
This symptom is observed on a Cisco router that is running an interim release of Cisco IOS Release 12.3(4). The symptom occurs on PPP sessions that are not directly associated with an interface or a subinterface (for example, PPP over ATM [PPPoATM] or Layer 2 Tunneling Protocol [L2TP]). Earlier releases of Cisco IOS software do not display this symptom.
Workaround: There is currently no workaround.
•
Description: A Cisco 7200 router may unexpectedly reload. This problem occurs when the router attempts to correct a single bit error in memory (DRAM parity). The symptoms are similar to CSCdu00306 however CSCdu00306 may not correct every situation where this may occur.
This symptom is specific to Network Processing Engine (NPE-400).
Workaround: There is currently no workaround.
•
Description: A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or Secure Shell [SSH] session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.
All Cisco products which contain TCP stack are susceptible to this vulnerability.
More details can be found in the security advisory which is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml
and it describes this vulnerability as it applies to Cisco products that run Cisco IOS software.
A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at
http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml
•
Description: Cisco Internetwork Operating System (IOS) Software is vulnerable to a Denial of Service (DoS) attack from crafted IPv6 packets when the device has been configured to process IPv6 traffic. This vulnerability requires multiple crafted packets to be sent to the device which may result in a reload upon successful exploitation.
More details can be found in the security advisory which is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20050126-ipv6.shtml
•
Description: A document that describes how the Internet Control Message Protocol (ICMP) could be used to perform a number of Denial of Service (DoS) attacks against the Transmission Control Protocol (TCP) has been made publicly available. This document has been published through the Internet Engineering Task Force (IETF) Internet Draft process, and is entitled "ICMP Attacks Against TCP" (draft-gont-tcpm-icmp-attacks-03.txt).
These attacks, which only affect sessions terminating or originating on a device itself, can be of three types:
a.
b.
c.
Successful attacks may cause connection resets or reduction of throughput in existing connections, depending on the attack type.
Multiple Cisco products are affected by the attacks described in this Internet draft.
Cisco has made free software available to address these vulnerabilities. In some cases there are workarounds available to mitigate the effects of the vulnerability.
More details can be found in the security advisory which is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20050412-icmp.shtml
The disclosure of these vulnerabilities is being coordinated by the National Infrastructure Security Coordination Centre (NISCC), based in the United Kingdom. NISCC is working with multiple vendors whose products are potentially affected.
More details can be found in the security advisory which is posted at:
http://www.cpni.gov.uk/Products/advisories.aspx
•
Description: A Hot Standby Routing Protocol (HSRP) tracking configuration is not accepted when you re-enter the configuration after you first delete it.
This symptom is observed on a Cisco router that runs Cisco IOS Release 12.2S or Release 12.3T.
Workaround: Configure interface tracking by entering the track 100 interface e2/3 line-protocol command. Then, set the HSRP group to track the tracking object number by entering the standby 1 track 100 command.
•
Description: A specifically crafted Transmission Control Protocol (TCP) connection to a telnet or reverse telnet port of a Cisco device running Internetwork Operating System (IOS) may block further telnet, reverse telnet, Remote Shell (RSH), Secure Shell (SSH), and in some cases Hypertext Transport Protocol (HTTP) access to the Cisco device. Telnet, reverse telnet, RSH and SSH sessions established prior to exploitation are not affected.
All other device services will operate normally.
User initiated specially crafted TCP connection to a telnet or reverse telnet port results in blocking further telnet sessions. Whereas, services such as packet forwarding, routing protocols and all other communication to and through the device remains unaffected.
More details can be found in the security advisory which is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20040827-telnet.shtml
•
Description: Reception of certain IPv6 fragments with carefully crafted illegal contents may cause a router running Cisco IOS to reload if it has IPv6 configured. This applies to all versions of Cisco IOS that include support for IPv6.
The system may be protected by installing appropriate access lists to filter all IPv6 fragments destined for the system. For example:
interface Ethernet0/0ipv6 traffic-filter nofragments in!ipv6 access-list nofragmentsdeny ipv6 any <my address1> undetermined-transportdeny ipv6 any <my address2> fragmentspermit ipv6 any anyThis must be applied across all interfaces, and must be applied to all IPv6 addresses which the system recognizes as its own.
This will effectively disable reassembly of all IPv6 fragments. Some networks may rely on IPv6 fragmentation, so careful consideration should be given before applying this workaround.We would recommend for customers to upgrade to the fixed IOS release. All IOS releases listed in IPv6 Routing Header Vulnerability Advisory at
http://www.cisco.com/warp/public/707/cisco-sa-20070124-IOS-IPv6.shtml contain fixes for this issue.
•
Description: Cisco Internetwork Operating System (IOS) Software is vulnerable to a Denial of Service (DoS) attack and potentially an arbitrary code execution attack from a specifically crafted IPv6 packet. The packet must be sent from a local network segment. Only devices that have been explicitly configured to process IPv6 traffic are affected. Upon successful exploitation, the device may reload or be open to further exploitation.
Cisco has made free software available to address this vulnerability for all affected customers.
More details can be found in the security advisory which is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20050729-ipv6.shtml
•
Description: In an active router, the relays are closed and the revertive interface should be in the ADMINDOWN state. However, when the interface is brought up, the command standby use-interface loopback 102 revertive is re-issued. This is causing an issue with Hot Standby Routing Protocol (HSRP) as the difference of HSRP priorities between the active and standby routers is no longer 5 but 10. As a result, a router swap will not occur when a single interface goes down.
This situation occurs when re-configuring the redundancy command which brings up revertive int lo102.
Workaround: Manually shut the interface down if it is re-configured.
•
Description: When the no shutdown command is configured on a Multilink interface, some links that are members of the multilink bundle may fail to renegotiate the PPP Link Control Protocol (LCP) and thus fail to activate the bundle.
This symptom occurs very rarely, and is usually associated with several multilink member links and the use of the shutdown and no shutdown commands in rapid succession on the Multilink interface.
Workaround: Configure shutdown on the Multilink interface, wait a few moments, then configure no shutdown.
•
Description: A router may reset its Border Gateway Protocol (BGP) session.
This symptom is observed when a Cisco router that peers with other routers receives an Autonomous System (AS) path with a length that is equal to or greater than 255.
Workaround: Configure the bgp maxas limit command in such a way that the maximum length of the AS path is a value below 255. When the router receives an update with an excessive AS path value, the prefix is rejected and the event is recorded in the log.
•
Description: When an FE cable is pulled out of a Cisco MWR 1900 Mobile Wireless Edge Router, a LINK DOWN Trap is generated. When the cable is inserted back in, the LINK DOWN Trap is generated again, instead of the LINK UP Trap.
This symptom occurs when the FE cable is pulled out and re-inserted in the Cisco MWR 1900 Mobile Wireless Edge Router.
Workaround: There is currently no workaround.
•
Description: The MWR controllers are down when the `detect v54 channel-group' is configured.
This symptom occurs when you Boot both redundancy MWRs at the same time. Some of the controllers can go down in the active MWR.
Workaround: Reload the active MWR to cause a failover. All the controllers will come up after the standby router becomes the active router.
•
Description: Cisco IOS may permit arbitrary code execution after exploitation of a heap-based buffer overflow vulnerability. Cisco has included additional integrity checks in its software, as further described below, that are intended to reduce the likelihood of arbitrary code execution.
Cisco has made free software available that includes the additional integrity checks for affected customers.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20051102-timers.shtml.
•
Description: Through normal software maintenance processes, Cisco is removing deprecated functionality from the OS boot routine. These changes have no impact on system operation or feature availability.
•
Description: Array indexing on toaster address queue may go out of array boundary. This may cause a crash or exhibit unexpected behavior.
Workaround: There is currently no workaround.
•
Description: When you send traffic through a link, after a few seconds the packets of traffic that are sent through the link are not incrementing, even though the Chars Out display clearly shows the packets are incrementing.
Workaround: There is currently no workaround.
Caveats in Cisco IOS Release 12.2(15)MC2b
The following sections list and describe the open and closed caveats for the Cisco MWR 1941-DC router running Cisco IOS Release 12.2(15)MC2b. Only severity 1 through 3 caveats are included.
Caveats describe unexpected behavior in 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.
Caveats in Cisco IOS Releases 12.2 and 12.2 T are also in Cisco IOS Release 12.2(15)MC2b. For information on caveats in Cisco IOS Release 12.2, see Caveats for Cisco IOS Release 12.2. For information on caveats in Cisco IOS Release 12.2 T, see Caveats for Cisco IOS Release 12.2 T. These two documents list severity 1 and 2 caveats and are located on CCO and the Documentation DVD.
Note
http://www.cisco.com/en/US/support/tsd_most_requested_tools.html
Open Caveats
There are no known open caveats in Cisco IOS Release 12.2(15)MC2b.
Resolved Caveats
This section lists the caveats that are resolved in Release 12.2(15)MC2b.
•
Description: An adjacent T1 link keeps having CRC input errors if the peer router has its T1 link shut. The serial interface on the router in question would keep resetting.
This problem only occurs on the GT96K serial interface when the peer router has its adjacent T1 link shut. This problem is observed in Cisco IOS 12.2T and 12.3.
Workaround: Shut down the T1 link on the router in question.
•
Description: Cisco routers running Cisco IOS supporting Multi Protocol Label Switching (MPLS) are vulnerable to a Denial of Service (DoS) attacks on the MPLS disabled interfaces.
This vulnerability is only present in Cisco IOS release trains based on 12.1T, 12.2, 12.2T, 12.3 and 12.3T. Releases based on 12.1 mainline, 12.1E and all releases prior to 12.1 are not vulnerable.
This bug is a complementary fix to CSCeb56909 which addresses this vulnerability.
More details can be found in the security advisory which is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20050126-les.shtml
•
Description: When a standby router is reloaded, it takes over as the active router.
This occurs more often when the IP address of the standby router is higher than the active router. Pre-emption occurs on reload.
Workaround: Unconfigure pre-emption when reloading the standby router if this additional swap over is considered an inconvenience and the outage is not considered acceptable.
•
Description: NetFlow Feature Acceleration CLI.
NetFlow Feature Acceleration has been deprecated and removed from Cisco IOS. The global command ip flow-cache feature-accelerate will no longer be recognized in any IOS configuration.
If your router configuration does not currently contain the command ip flow-cache feature-accelerate, this change does not affect you.
This removal does not require an upgrade of your existing installation.
The removal of NetFlow Feature Acceleration does not affect any other aspects of Netflow operation, for example Access-list processing. The features are separate and distinct.
Cisco Express Forwarding (CEF) supersedes the deprecated NetFlow Feature Acceleration.
Additionally, the following MIB objects and OIDs have been deprecated and removed from the netflow mib (CISCO-NETFLOW-MIB):
cnfFeatureAcceleration 1.3.6.1.4.1.9.9.99999.1.3
cnfFeatureAccelerationEnable 1.3.6.1.4.1.9.9.99999.1.3.1
cnfFeatureAvailableSlot 1.3.6.1.4.1.9.9.99999.1.3.2
cnfFeatureActiveSlot 1.3.6.1.4.1.9.9.99999.1.3.3
cnfFeatureTable 1.3.6.1.4.1.9.9.99999.1.3.4
cnfFeatureEntry 1.3.6.1.4.1.9.9.99999.1.3.4.1
cnfFeatureType 1.3.6.1.4.1.9.9.99999.1.3.4.1.1
cnfFeatureSlot 1.3.6.1.4.1.9.9.99999.1.3.4.1.2
cnfFeatureActive 1.3.6.1.4.1.9.9.99999.1.3.4.1.3
cnfFeatureAttaches 1.3.6.1.4.1.9.9.99999.1.3.4.1.4
cnfFeatureDetaches 1.3.6.1.4.1.9.9.99999.1.3.4.1.5
cnfFeatureConfigChanges 1.3.6.1.4.1.9.9.99999.1.3.4.1.6
Caveats in Cisco IOS Release 12.2(15)MC2a
The following sections list and describe the open and closed caveats for the Cisco MWR 1941-DC router running Cisco IOS Release 12.2(15)MC2a. Only severity 1 through 3 caveats are included.
Caveats describe unexpected behavior in 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.
Caveats in Cisco IOS Releases 12.2 and 12.2 T are also in Cisco IOS Release 12.2(15)MC2a. For information on caveats in Cisco IOS Release 12.2, see Caveats for Cisco IOS Release 12.2. For information on caveats in Cisco IOS Release 12.2 T, see Caveats for Cisco IOS Release 12.2 T. These two documents list severity 1 and 2 caveats and are located on CCO and the Documentation DVD.
Note
http://www.cisco.com/en/US/support/tsd_most_requested_tools.html
Open Caveats
The caveats listed in this section are open in Cisco IOS Release 12.2(15)MC2a.
•
Description: When PPPMux and cUDP are configured, during periods of sustained multicast traffic at a rate of 100 pps or more causes a periodic "out-of-sequence" condition in the MWR 1941-DC IOS decompression.
Workaround: Reduce the rate of multicast traffic.
•
Description: During a failover, the MWR 1941-DC router software opens T1/E1 relays on the active router without taking down the multilink interface first. Packets are sent to the disconnected interface for the next several second until the multilink interface is declared down. This condition causes the network management system to not receive SNMP traps generated during the failover.
Workaround: There is currently no workaround.
•
Description: When shutting down a multilink interface, the virtual access (VA) interface associated with the multilink interface flaps.
Workaround: Shut down the subinterface associated with the multilink group.
Resolved Caveats
This section lists the caveats that are resolved in Release 12.2(15)MC2a.
•
Description: Memory allocation failure (MALLOCFAIL) messages no longer occur for Cisco Discovery Protocol (CDP) processes.
•
A Cisco device running Internetwork Operating System (IOS) and enabled for the Open Shortest Path First (OSPF) Protocol is vulnerable to a Denial of Service (DoS) attack from a malformed OSPF packet. The OSPF protocol is not enabled by default.
The vulnerability is only present in IOS release trains based on 12.0S, 12.2, and 12.3. Releases based on 12.0, 12.1 mainlines and all IOS images prior to 12.0 are not affected. Refer to the Security Advisory for a complete list of affected release trains.
Further details and the workarounds to mitigate the effects are explained in the Security Advisory which is available at the following URL:
http://www.cisco.com/warp/public/707/cisco-sa-20040818-ospf.shtml.
•
Description: A Cisco device reloads on receipt of a corrupt CDP packet.
•
Description: The carrier delay detects interface flaps and closes a serial interface even though the carrier delay timer was not exceeded.
•
Description: On occasion, when an MWR 1941-DC router relay closes, syslog messages report the relay as opening.
•
Description: When a PPP multiplexed ICMP echo request is sent to an MWR 1900 series router, the MWR 1941-DC router corrupts the ICMP data payload when de-multiplexing the ICMP packets.
•
Description: Problems with the CDP protocol have been resolved.
•
Description: A Cisco device experiences a memory leak in the CDP process. The device sending CDP packets sends a hostname that is 256 or more characters. There are no problems with a hostname of 255 or fewer characters.
Unreproducible Caveat
The caveat listed in this section has not been reproduced during testing. In the unlikely event you experience the problem described in this section, contact Cisco customer service.
•
Description: Periods of sustained mixed traffic (UDP multicast, IP, and TCP) might cause the MWR 1941-DC router to crash.
Troubleshooting
Collecting Data for Router Issues
To collect data for reporting router issues, issue the following command:
•
Collecting Data for Redundancy Issues
To collect data for redundancy-related issues, issue the following commands while in EXEC mode:
•
•
•
•
•
•
Collecting Data for ROMmon Issues
To collect data for ROMmon issues, issue the following command while in EXEC mode:
•
Collecting Data for Router Rebooting to ROMmon
If a router reboot to ROMmon occurs, issue the dir device ID command where device ID is slot0:, and look for the router processor or network processor exception file (crashinfo* or pxf_crashinfo* respectively). Once you have located one of these files, you can email the file along with a description of the problem to your Cisco representative.
Documentation Updates
The following sections describe updates to the published documentation for the Cisco MWR 1941-DC router. The heading in this section corresponds with the applicable section title in the documentation.
Configuring RTP/UDP Compression
The maximum number of RTP header compression connections per MLP bundle is documented as 600 when in fact, up to 1000 connections are supported on an interface. This change also applies to the ip rtp header-compression command description.
The show ip rtp header-compression Command
The detail keyword is not supported in the show ip rtp header-compression command. Therefore, output does not display for the detail keyword if it is specified in command.
Configuring T1 Interfaces
Some configuration modes shown in the procedure for configuring T1 interfaces in the "Configuring T1 Interfaces" of the Cisco MWR 1900 Software Configuration Guide are incorrect. The correct command modes are as follows:
Step 1
Router(config)# controller t1 slot/portStep 2
Router(config-controller)# framing esfStep 3
Router(config-controller)# linecode b8zsStep 4
Note
Router(config-controller)# channel-group 0 timeslots 1-24 speed 64Step 5
Router(config-controller)# cablelength feet
Note
Step 6
Router(config-controller)# exitStep 7
Router(config)# interface serial slot/port:0Step 8
Router(config-if)# ip address ip_address subnet_maskStep 9
Router(config-if)# encapsulation pppStep 10
Router(config-if)# carrier-delay numberStep 11
Step 12
Router(config-if)# exit
Configuring Redundancy
Before configuring redundant MWR 1941-DC routers as described in the "Configuring T1 Interfaces" section of the Cisco MWR 1900 Software Configuration Guide, ensure that you disable EADI capabilities on the router by issuing the disable-eadi global configuration command as follows:
Router(config)# disable-eadiRelated Documentation
The following sections describe the documentation available for the Cisco MWR 1941-DC router. These documents consist of hardware and software installation guides, Cisco IOS configuration guides and command references, system error messages, and other documents.
Documentation is available as printed manuals or electronic documents.
Platform-Specific Documents
These documents are available for the Cisco MWR 1941-DC router on Cisco.com and the Documentation DVD:
•
–
–
–
–
•
•
On Cisco.com at:
Technical Support and Documentation: Documentation: Routers: Cisco MWR 1900 Mobile Wireless Routers: Install and Upgrade Guides: Cisco 1900 Mobile Wireless Routers
then, under the menu title Cisco 1941-DC Mobile Wireless Edge Router, choose the type document.
On the Documentation DVD at:
Cisco Product Documentation: Fixed and Mobile Wireless Solution: Mobile Wireless Products: Cisco Radio Access Network Products: Cisco Mobile Wireless IP RAN:
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL:
http://www.cisco.com/univercd/home/home.htm
The Product Documentation DVD is created and released regularly. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
Ordering Documentation
You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
If you do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Documentation Feedback
You can provide feedback about Cisco technical documentation on the Cisco Technical Support & Documentation site area by entering your comments in the feedback form available in every online document.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to do the following:
•
•
•
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked encryption key or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material.
Product Alerts and Field Notices
Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information.
To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the tool at this URL: http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Tip
If you suspect that the browser is not refreshing a web page, force the browser to update the web page by holding down the Ctrl key while pressing F5.
To find technical information, narrow your search to look in technical documentation, not the entire Cisco.com website. On the Cisco.com home page, click the Advanced Search link under the Search box and then click the Technical Support & Documentation radio button.
To provide feedback about the Cisco.com website or a particular technical document, click Contacts & Feedback at the top of any Cisco.com web page.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411
Australia: 1 800 805 227
EMEA: +32 2 704 55 55
USA: 1 800 553 2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/offer/subscribe
•
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm
•
•
