Release Notes for Cisco MWR 1900 Mobile Wireless Edge Router for Cisco IOS Release 12.2(8)MC2d
Available Languages
Table Of Contents
Release Notes for Cisco MWR 1900 Mobile Wireless Edge Router for Cisco IOS Release 12.2(8)MC2d
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 MC Software
New Features in Cisco IOS Release 12.2(8)MC2
New Feature in Cisco IOS Release 12.2(8)MC2b
Traffic Recovery Over MLP After T1 Failure
New Features in Cisco IOS Release 12.2(8)MC2c
ACFC and PFC Support on PPP Interfaces
Ignore IP ID Field Delta in cUDP Packet Flows Support
New Features in the Cisco IOS Release 12.2(8) MC2d Software
Limitations, Restrictions, and Important Notes
Caveats in Cisco IOS Release 12.2(8)MC2d
Configuring RTP/UDP Compression
The show ip rtp header-compression Command
Obtaining Technical Assistance
Release Notes for Cisco MWR 1900 Mobile Wireless Edge Router for Cisco IOS Release 12.2(8)MC2d
March 17, 2003
Cisco IOS Release 12.2(8)MC2d
OL-13984-05
These release notes are for the Cisco MWR 1900 Mobile Wireless Edge Router for Cisco IOS Release 12.2(8)MC2d. 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(8)MC2d, see the "Caveats in Cisco IOS Release 12.2(8)MC2d" section. To review the release notes for Cisco IOS Release 12.2, go to www.cisco.com and click Technical Documents. Select Release 12.2 from the Cisco IOS Software drop-down menu. Then click Cisco IOS Release Notes > Cisco IOS Release 12.2.
Contents
This document contains the following sections:
•
System Configuration Requirements
•
•
•
•
•
Introduction
The Cisco MWR 1900 Mobile Wireless Edge Router running Cisco IOS Release 12.2(8) MC2 or a later Cisco IOS Release 12.2 MC 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
The Cisco MWR 1900 Mobile Wireless edge router requires the following system configuration:
•
•
Network Time Protocol must be configured. The Cisco MWR 1900 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 1900 router in a redundant configuration, the standalone option must be configured from redundancy mode.
When using the Cisco MWR 1900 router in a redundant configuration:
–
–
–
•
You cannot disable Cisco Express Forwarding (CEF) on the MWR 1900. 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 1900 router, log in to the Cisco MWR 1900 and enter the show version EXEC command:
router> show versionCisco Internetwork Operating System SoftwareIOS (tm) 1900 Software (MWR1900-I-MZ), Version 12.2(8)MC2, 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/warp/public/130/upgrade_index.shtml
Upgrading to a New ROM Monitor Version
The MWR 1900 ROM Monitor (ROMMON) consists of two modules:
•
•
Note
Note
To upgrade the ROMMON version on your Cisco MWR 1900 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 Features in the Cisco IOS Release 12.2 MC Software
The following sections list the new hardware and software features supported by the Cisco MWR 1900 router for the Cisco IOS Release 12.2MC software releases:
•
•
•
New Features in Cisco IOS Release 12.2(8)MC2
For detailed descriptions of each of these features, see the Cisco MWR 1900 Mobile Wireless Edge Router Software Configuration Guide.
With Cisco IOS Release 12.2(8)MC2, the MWR 1900 router supports the following:
•
Cisco IOS software function added for the Cisco MWR 1900 router IP-RAN application include:
–
–
–
–
Standard Cisco IOS software features supported in this release include:
–
–
–
–
–
–
–
–
–
–
•
The following features are supported in the network processor:
–
–
–
–
–
–
–
–
–
–
–
–
•
•
•
New Feature in Cisco IOS Release 12.2(8)MC2b
The following new feature is introduced in Cisco IOS Release 12.2(8)MC2b.
Traffic Recovery Over MLP After T1 Failure
When a T1 failure occurs, traffic recovers over the MLP link within 6 seconds.
This caveat is a feature enhancement to the keepalive interface configuration command. With this enhancement, you can also configure a maximum number of retries before a link is declared down by issuing the command as follows:
keepalive [interval] [retries]
where:
•
•
For implementation in an IP RAN solution, the recommended configuration is as follows:
On the MWR 1900:
interface Serial0/0:0no ip addressencapsulation pppkeepalive 1 2no cdp enableppp multilinkmultilink-group 1endOn the MGX-RPM-1FE-CP back card;
interface Virtual-Template2bandwidth 1536no ip addresskeepalive 1 2no peer default ip addressppp multilinkmultilink-group 101end.
Note
This new feature is identified by CSCdy78207.
New Features in Cisco IOS Release 12.2(8)MC2c
The following new features are introduced in Cisco IOS Release 12.2(8)MC2c:
•
•
ACFC and PFC Support on PPP Interfaces
By default, Address and Control Field Compression (ACFC) and Protocol Field Compression (PFC) are enabled on PPP interfaces. Both features are always enabled and will be negotiated on all serial interfaces.
Note
This new feature is identified by CSCdz15365.
Ignore IP ID Field Delta in cUDP Packet Flows Support
By default, the ability to ignore IP ID field delta in cUDP traffic flows is enabled. This ability eliminates the need to send information about the IP header ID field in compressed packets. The decompressor saves the original ID field from the full header packet and generates an ID field by incrementing it by one for each decompressed packet.
This feature improves processing efficiency; helping to minimize dropped packets and link saturation.
This feature is identified by CSCdz00521.
New Features in the Cisco IOS Release 12.2(8) MC2d Software
The following new features are introduced in Cisco IOS Release 12.2(8)MC2d:
Link Noise Monitor
Noise on T1 and E1 links that span between the BTS and central office can affect voice quality for mobile users to the point where it becomes unacceptable. Therefore, beginning with Cisco IOS Release 12.2(8)MC2d software, the Link Noise Monitor (LNM) can be configured on your MWR 1900 router.
The LNM monitors the quality of individual links in a multilink bundle and provides the ability to detect, alert, and remove noisy links from a bundle based on user-defined thresholds and durations. In addition, the LNM notifies the operator once the quality of the line has improved, and restores the link service if the link has been removed.
Specifically, to detect noise on a link, the LNM monitors the following two types of errors which make up the Bit Error Rate (BER) and compares the number of errors with the user-defined thresholds:
•
•
The LNM provides the following types of noise monitors:
•
•
Note
Configuring LNM
To configure the LNM feature, issue the span command from controller configuration mode of each T1 or E1 link in the bundle that you want to monitor. To disable LNM on a link, issue the no version of the command from controller configuration mode of the link.
span { warn | remove } [ { [ lcv value [ pcv value ]] [ duration seconds ] } set | clear ]
where:
•
•
•
For T1 links:
–
–
–
For E1 links,
–
–
–
•
For T1 links:
–
–
–
For E1 links,
–
–
–
•
When specified with the lcv keyword, the duration must be configured after the LCV threshold. For example, span warn lcv 55 duration 20 is a correct way to issue the command; span warn duration 20 lcv 55 is not.
•
•
LNM Usage Notes
When configuring the LNM, keep in mind the following:
•
•
•
•
•
•
- %LNM-4- WARNEXCEED:Controller <Controller IF>, exceeded noise warning threshold <int>, duration <int>- %LNM-4- WARNIMPROVE:Controller <Controller IF>, noise improved below threshold <int>, duration <int>- %LNM-2-REMOVE:Interface <Serial IF> removed, noise exceeded threshold <int>, duration <int>- %LNM-2- RESTORE:Interface <Serial IF> restored, noise improved below threshold <int>, duration <int>- %LNM-2- REMEXCEED:Interface <Serial IF>, noise exceeded threshold <int>, duration <int>- %LNM-2- REMIMPROVE:Interface <Serial IF>, noise improved below threshold <int>, duration <int>This new feature is identified by CSCdz84024.
Double cUDP Full Headers
At the start of a call flow, the MWR 1900 router and MGX 8850 RPM-PR back card now send the first two packets in the flow with full headers. This feature helps to minimize the loss of cUDP headers (and therefore misrouted packets) in noisy and/or congested networks.
This feature is identified by CSCdz84029.
Limitations, Restrictions, and Important Notes
Caution
Caution
Unsupported Cisco IOS Software Features
The Cisco MWR 1900 router requires a special version of Cisco IOS software. Not all Cisco IOS software features can be used with the Cisco MWR 1900 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 1900 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 1900 router. Therefore, MLP LFI must be disabled on peer devices connecting to the Cisco MWR 1900 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 1900 routers connected to the MGX-RPM-1FE-CP back card.
Caveats in Cisco IOS Release 12.2(8)MC2d
The following sections list and describe the open and closed caveats for the Cisco MWR 1900 router running Cisco IOS Release 12.2(8)MC2d. 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(8)MC2d. 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 CD-ROM.
Note
Open Caveats
The caveats listed in this section are open in Release 12.2(8)MC2d.
•
When using an extended ACL with the access-group command to define traffic using the class policy-map configuration command, the Cisco MWR 1900 router crashes to ROMmon. This condition happens because extended ACLs are currently not supported.
Workaround: The access-group command is not part of the IP-RAN configuration. However, if using the command, use only with standard ACLs.
•
When traffic shaping is applied to an MLP output interface, the shaped output rate might be slightly higher than that defined. This condition occurs because the data rate to that interface is greater than the shaping rate.
Workaround: There is currently no workaround.
•
When the class-default queue is used with other class-based queues, the class-default queue's committed information rate (CIR) and the excess information rate are not configured correctly.
Workaround: Manually configure the committed information rate using the shape class-map configuration command. The excess information rate cannot be manually configured, therefore, there is no workaround for it not configuring correctly.
•
QoS class-based WFQs configured with a low percentage of bandwidth cannot use the unused bandwidth from queues assigned a high percentage of the bandwidth.
Workaround: Deconfigure QoS on the output interface.
•
During periods of heavy multicast traffic (approximately 5000 pps), some multicast packets are dropped at the MWR 1900 MLP interface.
Workaround: Reduce the rate of multicast traffic.
•
Entering or modifying the shape class-map configuration command to a policy map that has already been applied to an interface has no affect. Therefore, there will be no change to the traffic flow for that class of traffic. In addition, specifying certain values using the shape command might generate the message "Shape rate too low for interface."
Workaround: Remove the policy map from the interface and then reapply it, or save the new configuration and reload the router to get the changes to take effect. If the "Shape rate too low for interface" message displayed before, the value will be accepted and applied when one of the above methods is used.
•
When PPPMux and cUDP are configured, UDP fragmentation at traffic rates of 600 pps or more causes conditions such as dropped packets at the receiving MLP interface and tail drops at the receiving FE interface.
Workaround: There is currently no workaround.
•
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 1900 IOS decompression.
Workaround: Reduce the rate of multicast traffic.
•
Tail drops and output queue drops occur at traffic rates of mixed traffic of 6000 pps over a 4 T1 WAN link.
Workaround: Reduce the UDP multicast packet rate to no more than 300 pps.
Closed or Resolved Caveats
This section lists the caveats that are closed or resolved in Release 12.2(8)MC2d
•
QoS class-based WFQs configured with a low percentage of bandwidth are unable to use the unused bandwidth from queues assigned a high percentage of the bandwidth.
•
When IOMEM is low, a PXF memory leak occurs when processing multicast traffic (into the FE and out the MLP interface).
•
Noise on T1 and E1 links spanning between the BTS site and central office causes errored packets to be dropped, resulting in degraded voice quality for mobile phone users.
For more information about this resolved caveat, see the "Link Noise Monitor" section.
•
Noise, link overdrive, and other conditions might cause UDP packets to be lost or misrouted.
For more information about this resolved caveat, see the "Double cUDP Full Headers" section.
•
While in standby mode, MWR 1900 router repeatedly sends T1 controller alarms for loss of signal (LOS) / loss of framing (LOF). However, when in standby mode, T1 controllers are electrically disconnected from the cable by relays and therefore should not be reporting any errors for they do not accurately represent the link state.
This fix requires that you 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.
•
During periods of high traffic, when UDP packets are compressed via RTP compression configured on a multilink bundle between the MWR 1900 router and the MGX-RPM-1FE-CP back card, some packets might be misrouted and have incorrect UDP checksums.
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 1900 Mobile Wireless edge 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 1900s 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 1900 Mobile Wireless Edge 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 1900 Mobile Wireless Edge Router on Cisco.com and the Documentation CD-ROM:
•
–
–
–
–
•
•
On Cisco.com at:
Technical Documents: Cisco Product Documentation: Fixed and Mobile Wireless Solution: Cisco Mobile Wireless IP-RAN: Cisco Mobile Wireless IP-RAN Version 1.0
On the Documentation CD-ROM at:
Cisco Product Documentation: Fixed and Mobile Wireless Solution: Cisco Mobile Wireless IP-RAN: Cisco Mobile Wireless IP-RAN Version 1.0
Feature Modules
Feature modules describe new features supported by Cisco IOS Release 12.2 MC and are updates to the Cisco IOS documentation set. A feature module consists of an overview of the feature, configuration tasks, and a command reference.
On Cisco.com at:
Technical Documents: Cisco IOS Software: Cisco IOS Release 12.2: New Feature Documentation: New Features in 12.2-Based Limited Lifetime Releases: New Features in Release 12.2 MC: New Features in Release 12.2 MC2
On the Documentation CD-ROM at:
Cisco Product Documentation: Cisco IOS Software Configuration: Cisco IOS Release 12.2: New Feature Documentation: New Features in 12.2-Based Limited Lifetime Releases: New Features in Release 12.2 MC: New Features in Release 12.2 MC2
Obtaining Documentation
These sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
You can order Cisco documentation in these ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•
•
•
•
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Feedback