SCG

Cisco MWR 1941-DC Mobile Wireless
Edge Router Software Configuration Guide

October 27, 2006
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
Text Part Number: OL-11503-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant
to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause
harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required
to correct the interference at their own expense.
The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not
installed in accordance with Ciscos installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to
comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable
protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation.
Modifying the equipment without Ciscos written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital
devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television
communications at your own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its
peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
Turn the television or radio antenna until the interference stops.
Move the equipment to one side or the other of the television or radio.
Move the equipment farther away from the television or radio.
Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits
controlled by different circuit breakers or fuses.)
Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public
domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCVP, the Cisco Logo, and the Cisco Square Bridge logo 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, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study,
LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, RateMUX, ScriptShare, SlideCast, 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. (0609R)
Cisco MWR 1941-DC Mobile Wireless Edge Router Software Configuration Guide
Copyright 2006 Cisco Systems, Inc. All rights reserved.
C O N T E N T S
Preface
ix
Document Revision History

Objectives
Audience
x
x
Organization
Document Conventions
xi
Additional Information
xii
Related Documentation
xii
Obtaining Documentation
Cisco.com
xiii
xiii
Product Documentation DVD

Ordering Documentation
Documentation Feedback
xiii
xiv
xiv
Cisco Product Security Overview
xiv
Reporting Security Problems in Cisco Products

Product Alerts and Field Notices
xiv
xv
Obtaining Technical Assistance
xv
Cisco Technical Support & Documentation Website

Submitting a Service Request
xvi
Definitions of Service Request Severity
xvii
Obtaining Additional Publications and Information
CHAPTER
Overview of the Cisco MWR 1941-DC Router

Primary Uses of the MWR 1941-DC Router
IP-RAN Solution
xv
xvii
1-1
1-1
1-1
Cell Site DCN Solution

Cisco IOS Software Features
1-2
1-4
Software Features for the IP-RAN Implementation

MIPs-Based Software Features
1-4
Network Processor (PXF) Software Features

Redundancy Support
1-4
1-5
1-6
IP-RAN Implementation Updates
1-7
OL-11503-01
iii
Contents
Software Features for the Cell Site DCN Application

MIB Support
1-8
1-9
Limitations and Restrictions
1-9
IP-RAN Implementation Limitations and Restrictions
1-10
Cell Site DCN Implementation Limitations and Restrictions

New Features in Cisco IOS Release 12.2(15)MC2h
Support for 6 T1/E1 Interfaces per/MWR
Support for 1800 CIDs per/MWR
1-11
1-11
1-11
Support for Enhanced Link Noise Monitoring (LNM)
CHAPTER
Cisco IOS Software Basics

Getting Help
2-1
2-2
Undoing a Command or Feature
2-3
Saving Configuration Changes

Where to Go Next
3
1-12
2-1
Understanding Command Modes
CHAPTER
1-11
2-3
First-Time Configuration
Before You Begin
2-3
3-1
3-1
Understanding Boot Images
3-1
Understanding MWR 1941-DC Router Interface Numbering

Slot and Port Numbering
3-2
Before Starting Your Router
3-3
Using the Setup Command Facility

Configuring Global Parameters
3-3
3-4
Configuring Interface Parameters
3-6
Ethernet Interface Configuration
3-6
FastEthernet Interface Configuration

Serial Interface Configuration
LAPB Encapsulation
3-8
X.25 Encapsulation
3-9
ATM-DXI Encapsulation
3-7
3-7
Frame Relay Encapsulation
SMDS Encapsulation
3-2
3-8
3-9
3-9
Serial Cisco IOS Commands Generated
3-9
Asynchronous/Synchronous Serial Interface Configuration
3-10
iv
OL-11503-01
Contents
Synchronous Configuration
3-10
Asynchronous Configuration
Completing the Configuration
Where to Go Next
PART
3-12
3-13
Implementing the MWR 1941-DC Router in an IP-RAN
CHAPTER
3-12
Configuring the MWR 1941-DC in an IP-RAN

Before You Begin
4-1
4-2
Verifying the Version of Cisco IOS Software

Configuring the Host Name and Password
Configuring Loopback Interfaces
4-2
4-2
4-4
Configuring Fast Ethernet Interfaces
4-4
Configuring the FE Interface IP Address

Setting the Speed and Duplex Mode
4-5
4-5
Configuring Routing Protocol Attributes

Configuring PIM
4-6
4-6
Configuring HSRP Support

Enabling the FE Interface
4-6
4-8
Configuring Multilink Interfaces
4-8
Configuring Multilink PPP
4-9
Configuring IP Address Assignment

Configuring PPP Multiplexing
4-9
4-10
Configuring ACFC and PFC Handling During PPP Negotiation

Configuring RTP/UDP Compression
4-11
4-12
Configuring the RTP/UDP Compression Flow Expiration Timeout Duration

Configuring PIM
4-13
4-13
4-14
Configuring T1 and E1 Interfaces
4-14
Configuring T1 Interfaces
4-14
Configuring E1 Interfaces
4-16
Configuring QoS Attributes
4-17
Creating a Class Map
4-17
Creating a Policy Map
4-18
Assigning a QoS Boilerplate to an Interface

Configuring Redundancy
4-19
4-20
OL-11503-01
Contents
Redundant MWR 1941-DCs
4-20
Stand-Alone MWR 1941-DC
4-21
Configuring the Link Noise Monitor

Usage Notes
4-22
Configuring LNM
4-23

Verifying the Configuration
Notes
4-21
4-24
4-24
4-28
Monitoring and Managing the MWR 1941-DC
4-28
Show Commands for Monitoring the MWR 1941-DC

Where to Go Next
CHAPTER
PART
4-30
Cisco MWR 1941-DC Router IP-RAN Command Reference
5-1
Implementing the MWR 1941-DC Router in a Cell Site DCN
CHAPTER
4-29
Configuring the MWR 1941-DC in a Cell Site DCN

Before You Begin
6-1
6-2

Verifying the Host Name and Password
Configuration Example
6-3
6-3
6-5
6-5
6-6
Configuring the Ethernet Switch Network Module

6-6
6-6
Configuring Asynchronous/Synchronous Serial Network Modules or WAN Interface Cards

6-11
Configuring 16-Port Asynchronous Network Module

6-12
6-12
6-13
6-13
6-14
Configuring Drop and Insert

Configuration Examples
6-9
6-14
6-16
Configuring the 1 T3/E3 Module
6-17
Configuring the T3 Interface
6-17
vi
OL-11503-01
Contents
Configuring the Card Type and Controller for a T3 Interface

Configuring DSU Mode and Bandwidth for T3
Configuring the E3 Interface
6-17
6-19
6-19
Configuring the Card Type and Controller for an E3 Interface

Configuring DSU Mode and Bandwidth for E3
Configuring Scrambling for E3
6-21
6-22
6-22
Configuring the NM-AIC-64, Contact Closure Network Module

Serial Communication Channels
Serial Data Channel
Configuring the AIC
6-24
6-25
6-25
6-26
Configuring the AIC
6-26
Accessing the AIC
6-29
Configuring the NOC IP Address

Configuring Alarms
6-23
6-24
Asynchronous Craft Port

Configuration Tasks
6-20
6-30
6-30
Programming the Analog Contact Points

Programming the Discrete Contact Points
Verifying the IP Address
6-31
6-32
6-33
Troubleshooting Tips
6-35
Monitoring and Maintaining the NM-AIC-64 Contact Closure Network Module

Software Upgrade
6-35
Configuration Backup
Override
6-35
6-35
6-36
6-36
6-43
6-43
6-44

6-45
6-45
Filtering IP Packets Using Access Lists
6-46
Creating Standard and Extended Access Lists Using Numbers
6-46
Creating Standard and Extended Access Lists Using Names
6-50
Specifying IP Extended Access Lists with Fragment Control
6-53
OL-11503-01
vii
Contents
Benefits of Fragment Control in an IP Extended Access List

Enabling Turbo Access Control Lists
Configuring Turbo ACLs
Verifying Turbo ACLs
6-56
6-56
6-57
Applying Time Ranges to Access Lists
6-57
Including Comments About Entries in Access Lists

Applying Access Lists
6-55
6-58
6-58
Controlling Access to a Line or Interface
6-59
Controlling Policy Routing and the Filtering of Routing Information

Controlling Dialer Functions
6-59
6-60
Numbered Access List Examples

Named Access List Example
6-60
6-62
IP Extended Access List with Fragment Control Example

Time Range Applied to an IP Access List Example
Commented IP Access List Entry Examples
6-62
6-62
6-63
6-64
6-64
Monitoring and Managing the MWR 1941-DC Router
6-68

Where to Go Next
6-59
6-69
6-69
INDEX
viii
OL-11503-01
Preface
This preface discusses the objectives, audience, organization, and conventions of this software
configuration guide.
This preface contains the following sections:
Document Revision History, page x
Objectives, page x
Audience, page x
Organization, page x
Document Conventions, page xi
Additional Information, page xii
Related Documentation, page xii
Obtaining Documentation, page xiii
Documentation Feedback, page xiv
Cisco Product Security Overview, page xiv
Product Alerts and Field Notices, page xv
Obtaining Technical Assistance, page xv
Obtaining Additional Publications and Information, page xvii
OL-11503-01
ix
Preface

The Document Revision History table below records technical changes to this document. The table
shows the document revision number for the change, the date of the change, and a brief summary of the
change. Note that not all Cisco documents use a Document Revision History table.
Revision
Date
Change Summary
OL-11503-01
October 27, 2006
First usage of Document History Table.

Added Support for 6 T1/E1 interfaces by enabling additional
VWIC on the router.
Increased the maximum number of connections for the
Real-Time Transport Protocol (RTP) header compressions in the
syntax of the ip rtp compression-connections command in the
Command Reference to 1800.
Modified Link Noise Monitor (LNM) algorithm to make it more
efficient on noisy links.
Objectives
This guide explains how to configure features that enable the Cisco MWR 1941-DC Mobile Wireless
Edge Router to be implemented in an IP Radio Access Network (IP-RAN) or a Cell Site Data
Communications Network (Cell Site DCN) solution.
Audience
This publication is designed for the person who will be responsible for configuring the router. This guide
is intended for the following audiences:
Customers with technical networking background and experience
System administrators who are familiar with the fundamentals of router-based internetworking, but
who might not be familiar with Cisco IOS software
System administrators who are responsible for installing and configuring internetworking
equipment, and who are familiar with Cisco IOS software
Organization
The major sections of this software configuration guide include:
Chapter
Title
Description
Chapter 1 Overview of the Cisco MWR

1941-DC Router
Describes the purpose of the MWR 1941-DC and its

unique software features.
Chapter 2 First-Time Configuration
Discusses using the setup command facility to configure

basic attributes of your router.
OL-11503-01
Preface
Chapter
Title
Description
Chapter 3 Cisco IOS Software Basics
Describes what you need to know about the Cisco IOS

software.
Chapter 4 Configuring the MWR

1941-DC in an IP-RAN
Describes how to use the Cisco IOS software

command-line interface (CLI) to configure basic router
functionality in an IP-RAN.
Chapter 5 Cisco MWR 1941-DC Router

IP-RAN Command Reference
Provides information about new and changed commands.
Chapter 6 Configuring the MWR

1941-DC in a Cell Site DCN
Describes how to use the Cisco IOS software

command-line interface (CLI) to configure basic router
functionality in Cell Site DCN.
This publication uses the following conventions to convey instructions and information.
Note
Convention
Description
boldface font
Commands and keywords.
italic font
Variables for which you supply values.
Keywords or arguments that appear within square brackets are optional.
{x | y | z}
A choice of required keywords appears in braces separated by vertical bars.

You must select one.
screen font
Examples of information displayed on the screen.
boldface screen
font
Examples of information you must enter.
<
>
Nonprinting characters, for example passwords, appear in angle brackets in

contexts where italic font is not available.
Default responses to system prompts appear in square brackets.
Means reader take note. Notes contain helpful suggestions or references to additional
information and material.
Timesaver
This symbol means the described action saves time. You can save time by performing the
action described in the paragraph.
Caution
This symbol means reader be careful. In this situation, you might do something that could
result in equipment damage or loss of data.
OL-11503-01
xi
Preface
Tips
This symbol means the following information will help you solve a problem. The tips
information might not be troubleshooting or even an action, but could be useful
information, similar to a Timesaver.
This configuration guide does not contain the following:
Network design guide
Application case studies
Troubleshooting guide
A comprehensive reference to access services
For additional information about any of these topics, refer to the following resources:
Documentation DVD
Cisco Connection Online (CCO)
Customer Service
Technical Assistance Center (TAC)
European TAC
Related Documentation
The following list includes documentation related to your product by implementation.
Cisco Mobile Wireless IP-RAN
http://www.cisco.com/univercd/cc/td/doc/product/wireless/ipran/1_0/index.htm
Cisco MWR 1941 Mobile Wireless Edge Router Documents

Cisco MWR 1941-DC Mobile Wireless Edge Router Hardware Installation Guide
Cisco MWR 1941-DC Mobile Wireless Edge Router Rack Mounting Instructions
Regulatory Compliance and Safety Information for the Cisco MWR 1941-DC Mobile Wireless
Edge Router
MGX-RPM-1FE-CP Back Card Installation and Configuration Note
VWIC-2MFT-T1-DIR, VWIC-2MFT-E1-DIR Installation Instructions
Release Notes
Cisco Mobile Wireless Cell Site DCN
http://www.cisco.com/univercd/cc/td/doc/product/wireless/csdcn/index.htm
Cisco MWR 1941 Mobile Wireless Edge Router Documents

Cisco MWR 1941-DC Mobile Wireless Edge Router Hardware Installation Guide
Cisco MWR 1941-DC Mobile Wireless Edge Router Rack Mounting Instructions
xii
OL-11503-01
Preface
Regulatory Compliance and Safety Information for the Cisco MWR 1941-DC Mobile Wireless
Edge Router
Cisco Network Modules Installation Guides

Network Modules Quick Start Guide
Cisco Network Modules Hardware Installation Guide
Cisco Interface Cards Installation Guides

Quick Start Guide: Interface Cards
Cisco Interface Cards Installation Guide
VWIC-2MFT-T1-DIR, VWIC-2MFT-E1-DIR Installation Instructions
Note
Release Notes
To be sure of obtaining the latest information, access the online 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:
http://www.cisco.com
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
OL-11503-01
xiii
Preface
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
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:
Report security vulnerabilities in Cisco products
Obtain assistance with security incidents that involve Cisco products
Register to receive security information from Cisco
A current list of security advisories, security notices, and security responses for Cisco products is
available at this URL:
http://www.cisco.com/go/psirt
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:
For emergencies only security-alert@cisco.com

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.
For nonemergencies psirt@cisco.com
xiv
OL-11503-01
Preface
In an emergency, you can also reach PSIRT by telephone:
Tip
1 877 228-7302
1 408 525-6532
We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to
encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been
encrypted with PGP versions 2.x through 9.x.
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.

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

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
OL-11503-01
xv
Preface
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
Use the Cisco Product Identification Tool to locate your product serial number before submitting a
request for service online or by phone. You can access this tool from the Cisco Technical Support &
Documentation website by clicking the Tools & Resources link, clicking the All Tools (A-Z) tab, and
then choosing Cisco Product Identification Tool from the alphabetical list. This tool offers three search
options: by product ID or model name; by tree view; or, for certain products, by copying and pasting
show command output. Search results show an illustration of your product with the serial number label
location highlighted. Locate the serial number label on your product and record the information before
placing a service call.
Tip
Displaying and Searching on Cisco.com

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 2447
For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
xvi
OL-11503-01
Preface
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.

Information about Cisco products, technologies, and network solutions is available from various online
and printed sources.
The Cisco Online Subscription Center is the website where you can sign up for a variety of
Cisco e-mail newsletters and other communications. Create a profile and then select the
subscriptions that you would like to receive. To visit the Cisco Online Subscription Center,
go to this URL:
http://www.cisco.com/offer/subscribe
The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief
product overviews, key features, sample part numbers, and abbreviated technical specifications for
many Cisco products that are sold through channel partners. It is updated twice a year and includes
the latest Cisco channel product offerings. To order and find out more about the Cisco Product Quick
Reference Guide, go to this URL:
http://www.cisco.com/go/guide
Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo
merchandise. Visit Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
Cisco Press publishes a wide range of general networking, training, and certification titles. Both new
and experienced users will benefit from these publications. For current Cisco Press titles and other
information, go to Cisco Press at this URL:
http://www.ciscopress.com
Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering
professionals involved in designing, developing, and operating public and private internets and
intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/ipj
Networking products offered by Cisco Systems, as well as customer support services, can be
obtained at this URL:
http://www.cisco.com/en/US/products/index.html
OL-11503-01
xvii
Preface
Networking Professionals Connection is an interactive website where networking professionals

share questions, suggestions, and information about networking products and technologies with
Cisco experts and other networking professionals. Join a discussion at this URL:
http://www.cisco.com/discuss/networking
Whats New in Cisco Documentation is an online publication that provides information about the
latest documentation releases for Cisco products. Updated monthly, this online publication is
organized by product category to direct you quickly to the documentation for your products. You
can view the latest release of Whats New in Cisco Documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm
World-class networking training is available from Cisco. You can view current offerings at
this URL:
http://www.cisco.com/en/US/learning/index.html
xviii
OL-11503-01
C H A P T E R

The MWR 1941-DC Mobile Wireless Edge Router is a networking platform optimized for use in mobile
wireless networks; specifically designed to be use at the cell site edge as a part of an IP Radio Access
Network (IP-RAN) or Cell Site Data Communications Network (DCN).
The MWR 1941-DC router offers high performance at a low cost while meeting the critical requirements
for deployment in cell sites, including small size, high availability, and DC input power flexibility.
This chapter includes the following sections:
Primary Uses of the MWR 1941-DC Router, page 1-1
Cisco IOS Software Features, page 1-4
Limitations and Restrictions, page 1-9

The MWR 1941-DC router is designed to be used at the cell site as part of an IP-RAN or Cell Site DCN
solution.
IP-RAN Solution
Note
Cisco IOS Release 12.3(11)T supports the Cisco IOS IP-RAN feature set (software image) for the MWR
1941-DC router.
In an IP RAN application, the MWR 1941-DC router extends IP connectivity to the cell site and Base
Transceiver Station (BTS). Through a FastEthernet interface to the BTS, the MWR 1941-DC router
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).
OL-11503-01
1-1
Chapter 1
Figure 1-1 shows the placement of and connections for the MWR 1941-DC router implemented in an
IP-RAN solution.
Figure 1-1
MWR 1941-DC Router in an IP-RAN Solution
Active
100BaseT
T1/E1 backhaul link to
IP RAN aggregation node
Standby
MWR 1900 IP BTS router pair
65827
pBTS
In the IP-RAN solution, the BTS site consists of a pair of MWR 1941-DC routers. The pair of
MWR 1941-DC routers provides for an active and standby router for redundancy. A failure of the active
MWR 1941-DC router causes the standby router to take over as the active router for the BTS site.
Each pair of MWR 1941-DC routers at the BTS site is identical in hardware configuration. They connect
to each other through the BTS via the Fast Ethernet interfaces. The individual backhaul links to an
MWR 1941-DC router are cabled from a single T1/E1 termination block in the BTS, connecting to both
the active and standby routers utilizing a Y cable. The redundancy design to control the active/standby
transitions of the router pair leverages HSRP to control the relays on the VWIC-2MFT-T1-DIR (or
VWIC-2MFT-E1-DIR) in each router to ensure that the relays on the active router are closed and the
relays on the standby router are open to avoid double termination of the T1 (or E1).
Cell Site DCN Solution

Note
Cisco IOS Release 12.3(11)T does not support the Cisco IOS Cell Site DCN feature set (software image)
for the MWR 1941-DC router.
In a Cell Site DCN, the MWR 1941-DC router can be used to extend a mobile operators DCN to the cell
site, providing the ability to manage radio and cell site equipment remotely from the operations center.
A cell site DCN minimizes the need to dispatch technicians for every problem that might occur at the
cell site by providing the ability to perform the following types of maintenance tasks remotely:
troubleshooting
diagnosis
repairs
control
upgrades
routine maintenance of the cell site devices
Additionally, the MWR 1941-DC router cell site DCN implementation also provides IP connectivity to
the cell site, enabling the use of IP-related applications that provide operation support (for example, web
camera for site surveillance, IP telephone for voice connectivity, and LAN extension to the cell site to
provide remote access to network applications, data, and access to the Internet and/or intranet).
1-2
OL-11503-01
Chapter 1

Cisco network modules and WAN interface cards used with the MWR 1941-DC router provide a variety
of connectivity options at the cell site.
Figure 1-2 shows an example placement and connections for the MWR 1941-DC router implemented in
a Cell Site DCN solution.
Figure 1-2
MWR 1941-DC Router in an Cell Site DCN Solution
BTS Node B
T1/E1
BSC/RNC
MWR 1941-DC, 7200, 1/0 DACS

Voice circuits
10/100 Base-T
T1/E1
Cisco MWR
1941-DC
Network Operations
Center
Drop
and
Insert
RS-232
DCN traffic
T1/E1
RF monitoring Unit
Microwave Equipment
Tower Light Controller
Battery System
Email access for trouble tickets

OSS network access
Database access for inventory and technical knowledge
Cisco IP SoftPhone or FXO/FXS VoIP for tech and support services
Web camera for Security
Local data archival
101070
10/100 Base-T
In the Cell Site DCN solution, the MWR 1941-DC router provides a channelized T1/E1 interface to the
BTS and routes management and control traffic via one DS0 from a T1. Additionally, the
MWR 1941-DC router supports a variety of interfaces to monitored and controlled devices using Cisco
network modules installed in the MWR 1941-DC router.
OL-11503-01
1-3
Chapter 1

There are two versions of software available for the Cisco MWR 1941-DC router. One version of
software is required for implementing the Cisco MWR 1941-DC router in an IP RAN; the other for
implementing the router in a Cell Site DCN.
The software features vary depending on the version of software running on the MWR 1941-DC router.
Software Features for the IP-RAN Implementation, page 1-4
Software Features for the Cell Site DCN Application, page 1-8
Software Features for the IP-RAN Implementation

The software required for implementing the MWR 1941-DC router in an IP-RAN consists of two
components: Cisco IOS software running on the MIPs-based route processor portion of the
MWR 1941-DC router hardware, and microcode running on the Cisco network processor, also known as
Parallel eXpress Forwarding (PXF). When deployed in an IP-RAN, the MWR 1941-DC router is
customized for performance, high availability, quality of service, and link efficiency.
Cisco IOS software functions added to the MWR 1941-DC router for the IP-RAN implementation
include:
Redundancy logicFor monitoring Hot Standby Routing Protocol (HSRP) information to

determine the active and standby router and control T1 termination.
Failover logicTo force a switchover for hardware failures or an over-temperature condition.
Relay controlTo open and close the T1/E1 interfaces on the active and standby routers.
Diagnostic functionsTo monitor the health of the standby MWR 1941-DC router.
This section contains the following information:
MIPs-Based Software Features, page 1-4
Network Processor (PXF) Software Features, page 1-5
Redundancy Support, page 1-6
IP-RAN Implementation Updates, page 1-7
MIPs-Based Software Features

Standard Cisco IOS software features supported in the MWR 1914-DC router for the IP-RAN
implementation include:
IP Fragmentation
IP Multicast
IGMP
MLP, PPP Control Path (IPCP, NCP, LCP, CLNS)
ACFC and PFC Handling During PPP Negotiation
HSRP
OSPF
DHCP
1-4
OL-11503-01
Chapter 1

CDP
NTP
SNMP
Network Processor (PXF) Software Features

To achieve the required efficiency, when implemented in an IP-RAN, the MWR 1941-DC router
additionally has microcode running on the network processor to offload the fast-path processing of
packets. This allows the MWR 1941-DC router to support the traffic of up to 4 T1s or E1s (up to 60,000
packets per second) at a targeted 80% processor utilization while performing UDP/RTP header
compression/decompression (cUDP/cRTP) and PPPmux.
The following features are supported in the network processor:
MAC Classify
ICMP
FIB (CEF)
Load-balancing
MAC Rewrite
QoS Matching, including IP Access Lists (Input/Output Security ACLs are not supported), QoS
Group, IP Precedence, IP DSCP, and Input Interface
QoS Actions, including Set IP Precedence, Set IP DSCP, Set QoS Group, Traffic Shaping, Class
Based WFQ (CB-WFQ), and Low Latency Queuing (LLQ)
Maintenance of statistics, such as Forwarding, Drop, and Interface
IPv4
MLPPP, MLP, PPP Data Path (MLP LFI is not supported)
PPPmux
cRTP/cUDP
Link Noise Monitoring (LNM) provides configuration monitoring of individual T1/E1 circuit
quality
PPP Multiplexing/Demultiplexing
Encapsulated PPP frames contain several bytes of header information, which adds overhead to a network
that is used to transport PPP frames.
RFC 3153 describes a way to overcome this overhead. On the sending end, a multiplexor concatenates
multiple PPP frames (subframes) into a single, multiplexed frame (superframe). One header is included
in the superframe and the individual PPP subframes are separated by delimiters. On the receiving end, a
demultiplexor uses the delimiters to separate the individual PPP subframes.
The MWR 1914-DC router network processor software conforms to this specification and acts as both a
multiplexor and a demultiplexor.
RTP/UDP Header Compression
RTP is a protocol used for carrying packetized audio and video traffic over an IP network. RTP, described
in RFC 1889, is not intended for data traffic, which uses TCP or UDP. Instead, RTP provides end-to-end
network transport functions intended for applications with real-time requirements (such as audio, video,
or simulation data) over multicast or unicast network services.
OL-11503-01
1-5
Chapter 1
In an RTP frame, there is a minimum 12 bytes of the RTP header, combined with 20 bytes of IP header,
and 8 bytes of UDP header. This creates a 40-byte IP/UDP/RTP header. By comparison, the RTP packet
has a payload of approximately 20 to 160 bytes for audio applications that use compressed payloads.
Given this ratio, it is very inefficient to transmit the IP/UDP/RTP header without compressing it.
Figure 1-3
RTP Header Compression
Before RTP header compression:

20 bytes
IP
8 bytes 12 bytes
UDP
RTP
Header
Payload
20 to 160 bytes
After RTP header compression:

2 to 4 bytes
IP/UDP/RTP header
20 to 160 bytes
12076
Payload
RFCs 2508 and 2509 describe a method for compressing not only the RTP header, but also the associated
UDP and IP headers. Using this method, the 40 bytes of header information is compressed into
approximately 2 to 4 bytes, as shown in Figure 1-3. Because the frames are compressed on a link-by-link
basis, the delay and loss rate are lower, resulting in improved performance.
The MWR 1914-DC router network processor offloads both the compression and decompression of RTP
frames from the Cisco IOS software.
Note
The MWR 1941-DC router can be configured to perform only IP/UDP compression, in which case the
header is reduced from 28 bytes to 2 to 4 bytes.
Redundancy Support
In an IP-RAN application, to ensure availability, the backhaul links to an MWR 1941-DC router are
redundantly cabled to the VWIC-2MFT-T1-DIR/ VWIC-2MFT-E1-DIR cards. This card, designed
specifically for the MWR 1941-DC router, is a modified 2-port T1/E1 Multiflex VWIC with Drop and
Insert.The modifications include the addition of relays to activate the T1/E1 ports. The relays allow Y
cabling for router redundancy where the T1/E1 link is not redundant and default to open. The relays are
controlled by HSRP/redundancy protocol between the two routers connected to the same T1/E1.
Note
If you choose to use the MWR 1941-DC router in a non-redundant configuration, you must close the
relays on the card using the standalone subcommand. Also, redundancy parameters are processed when
the router is booted up. These parameters cannot be changed on the fly.
1-6
OL-11503-01
Chapter 1

HSRP
Ciscos Hot Standby Router Protocol (HSRP) is used to control which router is active and which is
standby. HSRP uses a priority scheme to determine which HSRP-configured router is to be the default
active router. Priority is determined first by the configured priority value, and then by the IP address. In
each case a higher value is of greater priority.
IP-RAN Implementation Updates

This section lists MWR 1941-DC router product updates:
Traffic Recovery Over MLP After T1 Failure

With Cisco IOS Release 12.2(8)MC2b and later, you can use the keepalive interface configuration
command to configure traffic over an MLP link to recover within 6 second if a T1 failure should
occur.
ACFC and PFC Support on PPP Multilink Interfaces

With Cisco IOS Release 12.2(8)MC2c and later, 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
If upgrading for this support, ensure that you upgrade the MGX-RPM-1FE-CP back card
images first. After doing so, immediately upgrade all MWR 1941-DC routers connected to
the MGX-RPM-1FE-CP back card.
Ignore IP ID Field Delta in cUDP Packet Flows

With Cisco IOS Release 12.2(8)MC2c and later, 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.
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, with Cisco IOS release
12.2(8)MC2d and later, you can configure the Link Noise Monitor (LNM) on the MWR 1941-DC
router to monitor the quality of individual links in a multilink bundle. The LNM provides the ability
to detect, alert, and remove noisy links from a bundle based on user-defined thresholds and
durations. For more information on the LNM feature, see Configuring the Link Noise Monitor
section on page 4-21.
First Two Packets Sent with Full cUDP Headers

With Cisco IOS Release 12.2(8)MC2d and later, at the start of a call flow, the MWR 1941-DC router
and the MGX 8850 RPM-PR back card send the first two packets of 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.
OL-11503-01
1-7
Chapter 1
Software Features for the Cell Site DCN Application

The software required for implementing the MWR 1941-DC router in a Cell Site DCN runs on the
MIPs-based router processor portion of the MWR 1914-DC router hardware.
Standard Cisco IOS software features supported in the MWR 1914-DC router for the Cell Site DCN
implementation include:
Standard and extended Access Control Lists
IP Fragmentation
IP Multicast
IGMP
MLPPP
PPPo HDLC
HSRP
OSPF
DHCP
IP Precedence
cRTP/cUDP
CB-WFQ
Traffic shaping
TDM Drop & Insert
DS0-level grooming
NTP
SNMP
1-8
OL-11503-01
Chapter 1

MIB Support
The MWR 1914-DC router supports the following MIBs:
CISCO-ACCESS-ENVMON-MIB
CISCO-TCP-MIB
CISCO-CDP-MIB
ENTITY-MIB
CISCO-CLASS-BASED-QOS-MIB
IF-MIB
CISCO-CONFIG-COPY-MIB
IGMP-MIB
CISCO-CONFIG-MAN-MIB
IPMROUTE-MIB
CISCO-ENVMON-MIB
OLD-CISCO-CHASSIS-MIB
CISCO-FLASH-MIB
OLD-CISCO-FLASH-MIB
CISCO-HSRP-EXT-MIB
OLD-CISCO-INTERFACES-MIB
CISCO-HSRP-MIB
OLD-CISCO-IP-MIB
CISCO-ICSUDSU-MIB
OLD-CISCO-SYSTEM-MIB
CISCO-IMAGE-MIB
OLD-CISCO-TS-MIB
CISCO-IP-STAT-MIB
RFC1213-MIB
CISCO-IPMROUTE-MIB
RFC1253-MIB
CISCO-MEMORY-POOL-MIB
RFC1406-MIB
CISCO-MOBILE-IP-MIB
TCP-MIB
CISCO-PROCESS-MIB
UDP-MIB
CISCO-QUEUE-MIB
CISCO-SYSLOG-MIB
The MWR 1914-DC router uses the same software base as the Cisco 10000. As such, it shares the same
QoS MIB limitations of the Cisco 10000. For information about the Cisco10000 MIB support, see the
Cisco 10000 Series ESR MIB Specifications Guide on CCO at
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kmibs/specgdll/index.htm.

Caution
The Cisco MWR 1941-DC router does not support online insertion and removal (OIR) of WAN interface
cards. Any attempt to perform OIR on a card in a powered up router might cause damage to the card.
Caution
Removing the compact flash from the Cisco MWR 1941-DC router during a read/write operation might
corrupt the contents of the compact flash, rendering it useless. To recover from an accidental removal of
or corruption to the compact flash, a maintenance spare with the appropriate bootable Cisco IOS
software image might be needed.
OL-11503-01
1-9
Chapter 1
IP-RAN Implementation Limitations and Restrictions

The following list of restrictions applies when implementing the MWR 1941-DC router in an IP-RAN.
Cisco IOS Software Features not Supported on the MWR 1941-DC Router
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. A list of supported features is included in the Cisco IOS Software Features section
on page 1-4. The following standard Cisco IOS software features are not supported on the Cisco
MWR 1941-DC router:
Security Access Control Lists
MPLS
802.1Q VLANs
Frame Relay (FR)
MLP LFI
ATM
Use of additional WICs. The only supported WIC is the VWIC-2MFT-T1DIR/VWIC-2MFT-E1DIR.

(IP-RAN implementation only.)
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 back card image first. After doing so,
immediately upgrade all MWR 1941-DC routers connected to the MGX-RPM-1FE-CP back card.
1-10
OL-11503-01
Chapter 1

Cell Site DCN Implementation Limitations and Restrictions

The following list of restrictions applies when implementing the MWR 1941-DC router in a Cell Site
DCN.
Caution
The Cisco MWR 1941-DC router does not support online insertion and removal (OIR) of network
modules. Any attempt to perform OIR on a card in a powered up router might cause damage to the card.
Using the 1-port T3/E3: NM-1T3/E3(=)
When using the 1-port T3/E3 network module in your MWR 1941-DC router configuration, note that E3
mode is not supported with Cisco IOS Release 12.2(15)MC1a. E3 mode is supported with Cisco IOS
Release 12.2(15)MC1b and later.
Also, when used with the MWR 1941-DC router, the NM-1T3/E3 supports line rate throughput for traffic
with packet sizes of 1500 bytes. For traffic with smaller packet sizes, degradation in throughput will be
seen.
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.

The following new features are implemented in Cisco IOS Release 12.2(15)MC2h and later releases:
Support for 6 T1/E1 interfaces per/MWR
Support for 1800 Context IDs (CIDs) per/MWR
Support for enhanced Link Noise Monitoring (LNM)
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.
OL-11503-01
1-11
Chapter 1
Command
Purpose
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, its a sliding window of
noise averages for the last duration in seconds.
The Benefits of this new algorithm are the following:
Improves CDMA backhaul link robustness by detecting noisy spans and removing them out of
service 100 percent of the time and restoring them back 100 percent of the time when the link quality
reaches an acceptable value.
Improves CDMA Link Noise Monitoring Capability through intelligent threshold setting by using
the averaging algorithm and providing better detection at a wide range of Bit Error Rate levels.
100 percent detection at the Threshold which the customer sets to.
Alerts the customer 100 per cent of the time about the quality of the spans.
Removes the degraded span effectively and having only acceptable spans in service.
1-12
OL-11503-01
C H A P T E R

This chapter describes what you need to know about the Cisco IOS software before you configure the
router using the command-line interface (CLI). This chapter includes the following:
Getting Help, page 2-1
Understanding Command Modes, page 2-2
Undoing a Command or Feature, page 2-3
Saving Configuration Changes, page 2-3
Where to Go Next, page 2-3
Understanding these concepts will save time as you begin to use the CLI. If you have never used the
Cisco IOS software or need a refresher, take a few minutes to read this chapter before you proceed to the
next chapter.
If you are already familiar with the Cisco IOS software, proceed to Part 2, Implementing the MWR
1941-DC Router in an IP-RAN.
Getting Help
Use the question mark (?) and arrow keys to help you enter commands:
For a list of available commands, enter a question mark:

Router> ?
To complete a command, enter a few known characters followed by a question mark (with no space):
Router> s?
For a list of command variables, enter the command followed by a space and a question mark:
Router> show ?
To redisplay a command you previously entered, press the up arrow key. You can continue to press
the up arrow key for more commands.
OL-11503-01
2-1
Chapter 2

The Cisco IOS user interface is divided into different modes. Each command mode permits you to
configure different components on your router. The commands available at any given time depend on
which mode you are currently in. Entering a question mark (?) at the prompt displays a list of commands
available for each command mode. Table 2-1 lists the most common command modes.
Table 2-1
Timesaver
Common Command Modes
Command Mode
Access Method
Router Prompt
Displayed
Exit Method
User EXEC
Log in.
Router>
Use the logout command.
Privileged EXEC
From user EXEC mode, Router#

enter the enable
command.
To exit to user EXEC

mode, use the disable,
exit, or logout command.
Global configuration
From the privileged

EXEC mode, enter the
configure terminal
command.
To exit to privileged
EXEC mode, use the exit
or end command, or press
Ctrl-z.
Interface configuration
Router (config-if)# To exit to global

From the global
configuration mode,
configuration mode, use
enter the interface type
the exit command.
number command, such
To exit directly to
as interface serial 0/0.
privileged EXEC mode,
press Ctrl-z.
Router (config)#
Each command mode restricts you to a subset of commands. If you are having trouble entering a
command, check the prompt, and enter the question mark (?) for a list of available commands. You
might be in the wrong command mode or using the wrong syntax.
In the following example, notice how the prompt changes after each command to indicate a new
command mode:
Router> enable
Password: <enable password>
Router# configure terminal
Router (config)# interface serial 0/0
Router (config-if)# line 0
Router (config-line)# controller t1 0
Router (config-controller)# exit
Router (config)# exit
Router#
%SYS-5-CONFIG_I: Configured from console by console
The last message is normal and does not indicate an error. Press Return to get the Router# prompt.
Note
You can press Ctrl-z in any mode to immediately return to enable mode (Router#), instead of
entering exit, which returns you to the previous mode.
2-2
OL-11503-01
Chapter 2


If you want to undo a command you entered or disable a feature, enter the keyword no before most
commands; for example, no ip routing.

You need to enter the copy running-config startup-config command to save your configuration changes
to nonvolatile random-access memory (NVRAM), so the changes are not lost if there is a system reload
or power outage. For example:
Router# copy running-config startup-config
Building configuration...
It might take a minute or two to save the configuration to NVRAM. After the configuration has been
saved, the following appears:
[OK]
Router#
Where to Go Next
Now that you have learned some Cisco IOS software basics, you can begin to configure the router using
the CLI.
Remember that:
You can use the question mark (?) and arrow keys to help you enter commands.
Each command mode restricts you to a set of commands. If you have difficulty entering a command,
check the prompt and then enter the question mark (?) for a list of available commands. You might
be in the wrong command mode or using the wrong syntax.
To disable a feature, enter the keyword no before the command; for example, no ip routing.
You need to save your configuration changes to NVRAM so the changes are not lost if there is a
system reload or power outage.
Proceed to Part 2, Implementing the MWR 1941-DC Router in an IP-RAN to begin configuring the
router.
OL-11503-01
2-3
Chapter 2
Where to Go Next
2-4
OL-11503-01
C H A P T E R
This chapter describes how to use the setup command facility to configure your router. The setup
command facility prompts you to enter information needed to start a router functioning quickly. The
facility steps you through a basic configuration, including local-area network (LAN) and wide-area
network (WAN) interfaces. The following sections are included:
Before You Begin, page 3-1
Using the Setup Command Facility, page 3-3
Configuring Global Parameters, page 3-4
Configuring Interface Parameters, page 3-6
Completing the Configuration, page 3-12
If you prefer to configure the router manually or you wish to configure a module or interface that is not
included in the setup command facility, proceed to Chapter 2, Cisco IOS Software Basics to
familiarize yourself with the command-line interface (CLI) and then proceed to PART II for instructions
on configuring your MWR 1941-DC router.
Before You Begin

This section contains information with which you should be familiar before you begin to configure your
router for the first time, including understanding boot images, interface numbering, and knowing what
you should do before starting your router.
Understanding Boot Images

The first file on the compact flash device in slot0: must be the Cisco IOS software image that you want
to use. If it is not, the MWR 1914-DC router will not be able to boot.
If you need to upgrade or replace the compact flash, be sure to follow the procedures in the
Cisco MWR 1941-DC Mobile Wireless Router Hardware Installation Guide.
OL-11503-01
3-1
Chapter 3
Before You Begin
Understanding MWR 1941-DC Router Interface Numbering

Each network interface on a Cisco MWR 1941-DC router is identified by a slot number and a port
number.
Figure 3-1 shows an example of interface numbering on a Cisco MWR 1941-DC router with the
following configuration for a Cell Site DCN implementation:
Figure 3-1
A VWIC in three of the three VWIC slots
A 4-port asynchronous/synchronous serial network module in slot 1
Two built-in Fast Ethernet interfaces
Cisco MWR 1941-DC Router Port Numbers
Serial 0/3
Serial 0/1
Serial 0/2
Serial 0/0
SERIAL
A/S
CN/LP
RXC
RXD
TXC
TXD
CN/LP
RXC
RXD
TXC
TXD
CN/LP
RXC
RXD
TXC
TXD
CN/LP
RXC
RXD
TXC
TXD
EN
SEE MAN
UAL BEFO
RE INST
ALLATION
Serial 1/3
Serial 1/1
Serial 1/2
Serial 1/0
DSU
56K
SEE MAN
UAL BEFO
RE INST
ALLATION
FE1
FE0
CONSOL
AUXILIA
DSU
56K
98716
RY
Console
port
Auxiliary
port
Slot and Port Numbering

The Cisco MWR 1941-DC router chassis contains the following LAN and WAN interface types:
Two built-in Fast Ethernet LAN interfaces
Three slots in which you can install Voice/WAN interface cards (VWICs)
One slot in which you can install a network module
The slot numbers are as follows:
0 for all built-in interfaces
0 for all built-in VWIC slots
1 for the network module slot
The numbering format is:

Interface type Slot number/Interface number
3-2
OL-11503-01
Chapter 3
Interface (port) numbers begin at 0 for each interface type, and continue from right to left.
The two built-in Ethernet 10/100 interfaces are Fast Ethernet 0/0 and Fast Ethernet 0/1.
The slot number for all VWIC interfaces in the built-in VWIC slot is always 0. (The W0, W1, and
W2 slot designations are for physical slot identification only.) Interfaces in the VWICs are
numbered from right to left, starting with 0/0 for each interface type, regardless of the physical
VWIC slot in which the VWICs are installed.
For example, if you have a VWIC in two of the VWIC slots (W0 and W1), then the interfaces are:
Serial 0/0 and Serial 0/1 in physical slot W0
Serial 0/2 and Serial 0/3 in physical slot W1
However, if you install a VWIC in physical slot W1 (leaving slot W0 empty), the interfaces in slot
W1 are Serial 0/0 and Serial 0/1. If you then add a VWIC to slot W0, the interface numbering will
shift. The configuration that you created for interfaces Serial 0/0 and Serial 0/1 will now be applied
to the VWIC in slot W0 and you will need to create a new configuration for the interfaces that you
previously configured on W1 (which will now be Serial 0/2 and Serial 0/3).
The slot number of WIC/VWIC interfaces installed in slot 1 using a WAN network module is always
1 and the interfaces are always numbered from the right to left.
The slot number for all network module interfaces is always 1 and the interfaces are always
numbered from right to left starting with 1/0.
Before Starting Your Router

Before you power ON your router and begin to use the setup command facility, make sure you follow
these steps:
Step 1
Set up the hardware and connect the console and network cables as described in the
Cisco MWR 1941-DC Router Hardware Installation Guide.
Step 2
Configure your PC terminal emulation program for 9600 baud, 8 data bits, no parity, and 1 stop bit.

The setup command facility displays from your PC terminal emulation program window.
To create a basic configuration for your router, do the following:
Note
Complete the steps in the Configuring Global Parameters section on page 3-4.
Complete the steps in the Configuring Interface Parameters section on page 3-6.
Complete the steps in the Completing the Configuration section on page 3-12.
If you make a mistake while using the setup command facility, you can exit and run the facility again.
Press Ctrl-c, and type setup at the enable mode prompt (1900#).
OL-11503-01
3-3
Chapter 3

Step 1
Power ON the router, see the Cisco MWR 1941-DC Router Hardware Installation Guide.
Messages will begin to appear in your terminal emulation program window.
Caution
Do not press any keys on the keyboard until the messages stop. Any keys pressed during this time
are interpreted as the first command typed when the messages stop, which might cause the router to
power off and start over. It takes a few minutes for the messages to stop.
The messages look similar to the following:
Note
The messages vary, depending on the Cisco IOS software image and interface modules in
place in your router. The screen displays in this section are for reference only and might not
exactly reflect the messages on your console.
rommon 1 >b slot0:mwr1900-i-mz.12042001

program load complete, entry point:0x80008000, size:0x658258
Self decompressing the image :
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
############################################################################
####################### [OK]
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) 10000 Software (MWR1900-I-M), Version 12.2(xy), EARLY DEPLOYMENT RELEASE SOFTWARE
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Tue 04-Dec-01 23:20 by jsmith
Image text-base:0x600089C0, data-base:0x60B42000
cisco mwr1900 (R7000) processor (revision 0.5) with 98304K/32768K bytes of
memory.
Processor board ID 12345678901
R7000 CPU at 240Mhz, Implementation 39, Rev 3.3, 256KB L2 Cache
Bridging software.
X.25 software, Version 3.0.0.
Primary Rate ISDN software, Version 1.1.
Toaster processor tmc has been reset.
2 FastEthernet/IEEE 802.3 interface(s)
2 Channelized T1/PRI port(s)
3-4
OL-11503-01
Chapter 3
DRAM configuration is 64 bits wide with parity disabled.

55K bytes of non-volatile configuration memory.
39168K bytes of ATA Slot0 CompactFlash (Read/Write)
--- System Configuration Dialog --At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Step 2
When the following message appears, enter yes to begin the initial configuration dialog:
Basic management setup configures only enough connectivity
for management of the system, extended setup will ask you
to configure each interface on the system
Would you like to enter basic management setup? [yes/no]:y
Configuring global parameters:
Step 3
Enter a host name for the router (this example uses 1941-1):
Configuring global parameters:
Enter host name [Router]: 1941-1
Step 4
Enter an enable secret password. This password is encrypted (more secure) and cannot be seen when
viewing the configuration:
The enable secret is a password used to protect access to
privileged EXEC and configuration modes. This password, after
entered, becomes encrypted in the configuration.
Enter enable secret: xxxx
Step 5
Enter an enable password that is different from the enable secret password. This password is not
encrypted (less secure) and can be seen when viewing the configuration:
The enable password is used when you do not specify an
enable secret password, with some older software versions, and
some boot images.
Enter enable password: guessme
Step 6
Enter the virtual terminal password, which prevents unauthenticated access to the router through ports
other than the console port:
The virtual terminal password is used to protect
access to the router over a network interface.
Enter virtual terminal password: guessagain
Step 7
Respond to the following prompts as appropriate for your network:

Configure SNMP Network Management? [yes]:
Community string [public]:
Step 8
The summary of interfaces is displayed. This list varies depending on the network modules, if any,
installed in your router.
Current interface summary
Controller
T1 0/0
T1 0/1
T1 0/2
T1 0/3
Interface
Timeslots
24
24
24
24
D-Channel
23
23
23
23
Configurable modes
pri/channelized
pri/channelized
pri/channelized
pri/channelized
IP-Address
Status
Administratively
Administratively
Administratively
Administratively
OK? Method Status
up
up
up
up
Protocol
OL-11503-01
3-5
Chapter 3
FastEthernet0/0
FastEthernet0/1
Serial0/0:0
Serial0/1:0
Step 9
172.18.46.74
150.0.1.0
unassigned
unassigned
YES
YES
YES
YES
NVRAM
NVRAM
NVRAM
NVRAM
up
up
up
up
up
up
up
up
Specify the interface to be used to connect to the network management system.

Enter interface name used to connect to the
management network from the above interface summary:FastEthernet0/0
Step 10
You are then prompted to configure the specified interface.

Configuring interface FastEthernet0/0:
Use the 100 Base-TX (RJ-45) connector? [yes]:
Operate in full-duplex mode? [no]:
Configure IP on this interface? [yes]:no

From this point on in the setup process, the prompts you see vary depending on the network modules
and WAN interface cards in place in your router. The following sections provide examples of the setup
steps for each interface module. Refer to the sections appropriate to your routers configuration.
Configuration for network modules includes:
Ethernet Interface Configuration, page 3-6
FastEthernet Interface Configuration, page 3-7
Serial Interface Configuration, page 3-7
Asynchronous/Synchronous Serial Interface Configuration, page 3-10
When you complete the setup steps for your interface modules, go to the Completing the Configuration
section on page 3-12 for directions on saving your configuration.
Ethernet Interface Configuration

This section contains a sample configuration for the Ethernet interface. Enter the values appropriate for
your router and network. The messages you see may vary.
Do you want to configure Ethernet0/0 interface [yes]:
Configure IP on this interface? [yes]:
IP address for this interface: 255.255.255.0
Subnet mask for this interface [255.0.0.0]:
Class A network is 1.0.0.0, 8 subnet bits, mask is /8
Configure IPX on this interface? [no]: y
IPX network number [1]:
Need to select encapsulation type
[0] sap (IEEE 802.2)
[1] snap (IEEE 802.2 SNAP)
[2] arpa (Ethernet_II)
[3] novell-ether (Novell Ethernet_802.3)
Enter the encapsulation type [2]:
3-6
OL-11503-01
Chapter 3
FastEthernet Interface Configuration

This section contains a sample configuration for the FastEthernet interface. Enter the values appropriate
for your router and network. The messages you see may vary.
Do you want to configure FastEthernet0/0 interface [yes]:
Use the 100 Base-TX (RJ-45) connector? [yes]:
Operate in full-duplex mode? [no]:
Configure IP on this interface? [no]: yes
Number of bits in subnet field [0]:
Class A network is 6.0.0.0, 0 subnet bits, mask is /8
Configure IPX on this interface? [yes]:
Need to select encapsulation type
[0] sap (IEEE 802.2)
[1] snap (IEEE 802.2 SNAP)
[2] arpa (Ethernet_II)
[3] novell-ether (Novell Ethernet_802.3)
Enter the encapsulation type [2]:
Serial Interface Configuration

This section contains a sample configuration for the 1- or 2-port serial interface. Enter the values
appropriate for your router and network. The messages you see may vary.
Do you want to configure Serial0/0 interface? [yes]:
Some encapsulations supported are
ppp/hdlc/frame-relay/lapb/atm-dxi/smds/x25
Choose encapsulation type
[ppp]:
Note
The following sections describe the prompts for each encapsulation type. For PPP and HDLC
encapsulation, no further configuration is needed.
No serial cable seen.
Choose mode from (dce/dte) [dte]:
Note
If no cable is plugged in to your router, you need to indicate whether the interface is to be used as
DTE or DCE. If a cable is present, the setup command facility determines the DTE/DCE status. If
the serial cable is DCE, you see the following prompt:
Serial interface needs clock rate to be set in dce mode.
The following clock rates are supported on the serial interface.
0
1200, 2400, 4800, 9600, 19200, 38400
56000, 64000, 72000, 125000, 148000, 500000
800000, 1000000, 1300000, 2000000, 4000000, 8000000
Choose clock rate from above: [2000000]:
Class A network is 2.0.0.0, 8 subnet bits; mask is /8
Configure IPX on this interface? [no]: yes
OL-11503-01
3-7
Chapter 3

The following lmi-types are available to be set,
when connected to a frame relay switch
[0] none
[1] ansi
[2] cisco
[3] q933a
Enter lmi-type [2]:
Note
The setup command facility only prompts for the data-link connection identifier (DLCI) number if
you specify none for the Local Management Interface (LMI) type. If you accept the default or specify
another LMI type, the DLCI number is provided by the specified protocol.
Enter the DLCI number for this interface [16]:
Do you want to map a remote machines IP address to dlci? [yes]:
IP address for the remote interface: 2.0.0.2
Do you want to map a remote machines IPX address to dlci? [yes]:
IPX address for the remote interface: 40.1234.5678
0
1200, 2400, 4800, 9600, 19200, 38400
56000, 64000, 72000, 125000, 148000, 500000
800000, 1000000, 1300000, 2000000, 4000000, 8000000
choose speed from above: [2000000]: 1200
If IPX is configured on the router, the setup command facility prompts for the IPX map:
Do you want to map a remote machine's IPX address to dlci? [yes]:
IPX address for the remote interface: 40.0060.34c6.90ed
LAPB Encapsulation
lapb circuit can be either in dce/dte mode.
Choose either from (dce/dte) [dte]:
3-8
OL-11503-01
Chapter 3
X.25 Encapsulation
x25 circuit can be either in dce/dte mode.
Choose from either dce/dte [dte]:
Enter local x25 address: 1234
We will need to map the remote x.25 stations x25 address
to the remote stations IP/IPX address
Enter remote x25 address: 4321
Do you want to map the remote machines x25 address to IP address? [yes]:
Do you want to map the remote machines x25 address to IPX address? [yes]:
Enter
Enter
Enter
Enter
Enter
lowest 2-way channel [1]:

highest 2-way channel [64]:
frame window (K) [7]:
Packet window (W) [2]:
Packet size (must be powers of 2) [128]:
Enter VPI number [1]:
Enter VCI number [1]:
Do you want to map the remote machines IP address to vpi and vcis? [yes]:
Do you want to map the remote machines IPX address to vpi and vcis? [yes]:
SMDS Encapsulation
Enter smds address for the local interface: c141.5556.1415
We will need to map the remote smds stations address
Enter smds address for the remote interface: c141.5556.1414
Do you want to map the remote machines smds address to IP address? [yes]:
Do you want to map the remote machines smds address to IPX address? [yes]:
Serial Cisco IOS Commands Generated

The following is an example of the Cisco IOS commands generated by a typical serial configuration:
interface Serial0/0
encapsulation ppp
clock rate 2000000
ip address 2.0.0.1 255.0.0.0
OL-11503-01
3-9
Chapter 3
Asynchronous/Synchronous Serial Interface Configuration

This section contains sample configurations for an asynchronous/synchronous serial interface. Enter the
values appropriate for your router and network. The messages you see may vary.
Enter mode (async/sync) [sync]:
Synchronous Configuration
If you select synchronous, you see screen displays similar to the following:
Enter mode (async/sync) [sync]:
Some supported encapsulations are
ppp/hdlc/frame-relay/lapb/x25/atm-dxi/smds
Choose encapsulation type [hdlc]:
Note
The following sections describe the prompts for each encapsulation type. For PPP and HDLC
encapsulation, no further configuration is needed.
No serial cable seen.
Choose mode from (dce/dte) [dte]:
Note
If no cable is plugged in to your router, you need to indicate whether the interface is to be used as
DTE or DCE. If a cable is present, the setup command facility determines the DTE/DCE status. If
the serial cable is DCE, you see the following prompt:
Configure IP on this interface? [no]: yes
Configure IP unnumbered on this interface? [no]:
Configure LAT on this interface? [no]:

The following lmi-types are available to be set,
when connected to a frame relay switch
[0] none
[1] ansi
[2] cisco
[3] q933a
Enter lmi-type [2]:
Note
The setup command facility only prompts for the data-link connection identifier (DLCI) number if
you specify none for the Local Management Interface (LMI) type. If you accept the default or specify
another LMI type, the DLCI number is provided by the specified protocol.
Enter the DLCI number for this interface [16]:
Do you want to map a remote machines IP address to dlci? [yes]:
Do you want to map a remote machines IPX address to dlci? [yes]:
3-10
OL-11503-01
Chapter 3

0
1200, 2400, 4800, 9600, 19200, 38400
56000, 64000, 72000, 125000, 148000, 500000
800000, 1000000, 1300000, 2000000, 4000000, 8000000
choose speed from above: [2000000]: 1200
Note
If IPX is configured on the router, the setup command facility prompts for the IPX map:
Do you want to map a remote machine's IPX address to dlci? [yes]:
IPX address for the remote interface: 40.0060.34c6.90ed
LAPB Encapsulation
lapb circuit can be either in dce/dte mode.
Choose either from (dce/dte) [dte]:
X.25 Encapsulation
x25 circuit can be either in dce/dte mode.
Choose from either dce/dte [dte]:
Enter local x25 address: 1234
We will need to map the remote x.25 stations x25 address
Enter remote x25 address: 4321
Do you want to map the remote machines x25 address to IP address? [yes]:
Do you want to map the remote machines x25 address to IPX address? [yes]:
Enter
Enter
Enter
Enter
Enter
lowest 2-way channel [1]:

highest 2-way channel [64]:
frame window (K) [7]:
Packet window (W) [2]:
Packet size (must be powers of 2) [128]:
Enter VPI number [1]:
Enter VCI number [1]:
Do you want to map the remote machines IP address to vpi and vcis? [yes]:
Do you want to map the remote machines IPX address to vpi and vcis? [yes]:
OL-11503-01
3-11
Chapter 3
SMDS Encapsulation
Enter smds address for the local interface: c141.5556.1415
We will need to map the remote smds stations address
Enter smds address for the remote interface: c141.5556.1414
Do you want to map the remote machines smds address to IP address? [yes]:
Do you want to map the remote machines smds address to IPX address? [yes]:
Asynchronous Configuration
If you select asynchronous, you see screen displays similar to the following:
Enter mode (async/sync) [sync]: async
Configure IP unnumbered on this interface? [no]:
Configure LAT on this interface? [no]:
Configure AppleTalk on this interface? [no]:
Configure DECnet on this interface? [no]:
Configure CLNS on this interface? [no]:
Configure IPX on this interface? [no]: yes
Configure Vines on this interface? [no]:
Configure XNS on this interface? [no]:
Configure Apollo on this interface? [no]:

When you have provided all the information prompted for by the setup command facility, the
configuration appears (messages similar to the following):
The following configuration command script was created:
!
hostname 1941-1
enable secret 5 $1$kA4t$2LpzAVTQADpqTMeqAIG3F0
enable password guessme
line vty 0 4
password guessagain
no snmp-server
!
no ip routing
!
interface FastEthernet0/0
no shutdown
media-type 100BaseX
half-duplex
no ip address
!
shutdown
3-12
OL-11503-01
Chapter 3
Where to Go Next
no ip address
!
end
To complete your router configuration, do the following:

Step 1
A setup command facility prompt asks if you want to save this configuration.
[0] Go to the IOS command prompt without saving this config.
[1] Return back to the setup without saving this config.
[2] Save this configuration to nvram and exit.
Enter your selection [2]:
Use the enabled mode 'configure' command to modify this configuration.
Press RETURN to get started!
If you answer no, the configuration information you entered is not saved, and you return to the router
enable prompt. Type setup to return to the System Configuration Dialog.
If you answer yes, the configuration is saved and you are returned to the EXEC prompt.
Step 2
When the messages stop displaying on your screen, press Return to get the command line prompt.
The 1941-1> prompt indicates that you are now at the command-line interface (CLI) and you have just
completed a basic router configuration. However, this is not a complete configuration. You must
configure additional parameters using the Cisco IOS software CLI as described in Part 2, Implementing
the MWR 1941-DC Router in an IP-RAN.
Where to Go Next
At this point you can proceed to the following:
Part 2, Implementing the MWR 1941-DC Router in an IP-RAN for information on and details on
how to complete the configuration of the interfaces, routing protocols, and other features when
implementing the MWR 1941-DC router in an IP-RAN.
Part 3, Configuring the MWR 1941-DC in a Cell Site DCN for information on and details on how
to complete the configuration of the interfaces, routing protocols, and other features when
implementing the MWR 1941-DC router in an Cell Site DCN.
The Cisco IOS software configuration guide and command reference publications for more
advanced configuration topics.
The Cisco 10000 ESR Quality of Service Documents for more information on configuring QoS.
These publications are available on the Documentation CD-ROM that came with your router, on the
World Wide Web from Ciscos home page, or you can order printed copies.
OL-11503-01
3-13
Chapter 3
Where to Go Next
3-14
OL-11503-01
PA R T
Implementing the MWR 1941-DC Router in

an IP-RAN
C H A P T E R
Note
Cisco IOS Release 12.3(11)T supports the Cisco IOS IP-RAN feature set (software image) for the
MWR 1941-DC router.
This chapter describes how to use the Cisco IOS software command-line interface (CLI) to configure the
following features of the Cisco MWR 1941-DC in an IP-RAN:
Verifying the Version of Cisco IOS Software, page 4-2
Configuring the Host Name and Password, page 4-2
Configuring Multilink Interfaces, page 4-8
Configuring Fast Ethernet Interfaces, page 4-4
Configuring Multilink Interfaces, page 4-8
Configuring T1 and E1 Interfaces, page 4-14
Configuring QoS Attributes, page 4-17
Configuring Redundancy, page 4-20
Configuring the Link Noise Monitor, page 4-21
Verifying the Configuration, page 4-24
Monitoring and Managing the MWR 1941-DC, page 4-28
Follow the procedures in this chapter to configure the router manually or if you want to change the
configuration after you have run the setup command facility (described in Chapter 1, First-Time
Configuration).
This chapter describes how to configure features related to the use of the MWR 1941-DC in an IP-RAN.
For additional configuration topics, refer to the Cisco IOS configuration guide and command reference
publications. These publications are available on the Documentation CD-ROM that came with your
router, on the World Wide Web from Ciscos home page, or you can order printed copies separately.
Note
If you skipped the previous chapter, Chapter 2, Cisco IOS Software Basics, and you have never
configured a Cisco router, go back to that chapter and read it now. The chapter contains important
information you need to successfully configure your router.
78-13983-08
4-1
Chapter 4
Before You Begin
Before You Begin

Before you configure the MWR 1941-DC in an IP-RAN, please be aware of the following:
Cisco IOS Release 12.2(8)MC2 or later mwr1900-i-mz image must be installed on the Cisco
MWR 1941-DC router.
You cannot disable Cisco Express Forwarding (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 an error message is displayed.
If you are using the MWR 1941-DC in a redundant configuration and are attaching the
MWR 1941-DC to a device that uses spanning tree, configure portfast on the device to avoid
problems with HSRP at start up.
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.

To implement the MWR 1941-DC router in an IP-RAN, Cisco IOS Release 12.2(8)MC2 or a later must
be installed on the router. To verify the version of Cisco IOS software, use the show version command.
The show version command displays the configuration of the system hardware, the software version, the
names and sources of configuration files, and the boot images.

One of the first configuration tasks you might want to do is configure the host name and set an encrypted
password. Configuring a host name allows you to distinguish multiple Cisco routers from each other.
Setting an encrypted password allows you to prevent unauthorized configuration changes.
Command
Step 1 Router> enable
Password: password
Router#
Step 2 Router# configure terminal

Enter configuration commands, one per line.
End with CNTL/Z.
Purpose
Enter enable mode. Enter the password.
You have entered enable mode when the prompt
changes to Router#.
Enter global configuration mode. You have
entered global configuration mode when the
prompt changes to Router(config)#.
Router(config)#
Step 3 Router(config)# hostname Router

Router(config)#
Change the name of the router to a meaningful

name. Substitute your host name for Router.
4-2
78-13983-08
Chapter 4

Command
Purpose
Step 4 Router(config)# enable secret guessme
Enter an enable secret password. This password

provides access to privileged EXEC mode. When
a user types enable at the EXEC prompt
(Router>), they must enter the enable secret
password to gain access to configuration mode.
Substitute your enable secret for guessme.
Step 5 Router(config)# line con 0
Enter line configuration mode to configure the

console port. When you enter line configuration
mode, the prompt changes to
Router(config-line)#.
Router(config-line)# exec-timeout 0 0
Prevent the routers EXEC facility from timing out

if you do not type any information on the console
screen for an extended period.
Router(config-line)# exit
Exit back to global configuration mode.
Router(config)#
To verify that you configured the correct host name and password:
Step 1
Enter the show config command:

Router(config)# show config
Using 1888 out of 126968 bytes
!
version XX.X
.
.
.
!
hostname Router
!
enable secret 5 $1$60L4$X2JYOwoDc0.kqa1loO/w8/
.
.
.
Check the host name and encrypted password displayed near the top of the command output.
Step 2
Exit global configuration mode and attempt to re-enter it using the new enable password:
Router# exit
.
.
.
Router con0 is now available
Press RETURN to get started.
Router> enable
Password: guessme
Router#
78-13983-08
4-3
Chapter 4

The loopback interface is a software-only, virtual interface that emulates an interface that is always up.
The interface-number is the number of the loopback interface that you want to create or configure. There
is no limit on the number of loopback interfaces you can create.
The multilink interface is a virtual interface, if you are not going to assign an explicit IP address to the
interface, you should create a loopback interface for the multilink interface to enable IP processing on
the interface.
In the case where the MWR 1941-DC is used in a redundant configuration, you must also configure
loopback interfaces for the health and revertive interfaces. The health interface monitors the status of the
redundant configuration so that the standby router can take over if there is a problem with the active
router. The revertive interface is required to ensure that the switchover takes place. We recommend that
you use 101 for the health interface and 102 for the revertive interface.
To configure a loopback interface, do the following beginning in global configuration mode:
Step 1
Create a loopback interface for each multilink interface:

Router(config)# interface loopback number
Router(config-if)# ip address ip_address subnet_mask
Note
Step 2
For the health and revertive interfaces, you do not need to assign an IP address.
Exit interface configuration mode:

Router(config-if)# exit

To configure the FE interface of the MWR 1941-DC, complete the following tasks:
Configuring PIM
4-4
78-13983-08
Chapter 4


To configure the FE interface, do the following starting in global configuration mode:
Step 1
Specify the port adapter type and the location of the interface to be configured.
Router(config)# interface fastethernet slot/port
The slot is always 0 and the port is the number of the port (0 or 1).
Step 2
Assign an IP address and subnet mask to the interface.


The Fast Ethernet ports of the MWR 1941-DC can run in full or half duplex mode and at 100 Mbps or
10 Mbps. The MWR 1941-DC also has an auto-negotiation feature that allows the router to negotiate the
speed and duplex mode with the corresponding interface on the other end of the connection.
Auto negotiation is the default setting for the speed and transmission mode.
When configuring an interface speed and duplex mode, note these guidelines:
If both ends of the line support auto negotiation, we highly recommend the default auto negotiation
settings.
When the auto negotiation is turned on for either speed or duplex, it auto negotiates both speed and
duplex.
If one interface supports auto negotiation and the other end does not, configure duplex and speed on
both interfaces; do not use the auto setting on the supported side or the duplex setting will be half.
To configure speed and duplex operation, do the following while still in interface configuration mode:
Step 1
Specify the duplex operation.

Router(config-if)# duplex [auto | half | full]
Step 2
Specify the speed.

Router(config-if)# speed [auto | 100 | 10]
78-13983-08
4-5
Chapter 4

When used in the CDMA IP-RAN solution, the MWR 1941-DC must be configured to support the OSPF
routing protocol. To configure OSPF routing protocol attributes, do the following while still in interface
configuration mode:
Step 1
Enable OSPF Message Digest 5 (MD5) authentication.

Router(config-if)# ip ospf message-digest-key key-id md5 key
Step 2
Specify the interval between hello packets that the Cisco IOS software sends on the interface.
Router(config-if)# ip ospf hello-interval seconds
Step 3
Set the interval at which hello packets must not be seen before neighbors declare the router down.
Router(config-if)# ip ospf dead-interval seconds
Configuring PIM
Because the MWR 1941-DC is used in a multicast PPP environment, you should configure the PIM mode
of the FE interface.
To configure the PIM mode, do the following while still in interface configuration mode:
Step 1
Enter the following command:

Router(config-if)# ip pim {sparse-mode | sparse-dense-mode | dense-mode [proxy-register
{list access-list | route-map map-name}]}

In redundant configurations, the MWR 1941-DC uses HSRP to control the active and standby routers.
To use HSRP, you must configure the standby priority attributes and the IP address of the virtual router.
Priority is determined first by the configured priority value, and then by the IP address. In each case a
higher value is of greater priority.
Note
If you do not plan to use the MWR 1941-DC in a redundant configuration, do not configure HSRP
support and see Configuring Redundancy, page 4-20 for information about using the router in a
stand-alone environment.
4-6
78-13983-08
Chapter 4

To configure HSRP support, do the following while still in interface configuration mode:
Step 1
Specify the name of the standby group.

Router(config-if)# standby group name group-name
Note
Tips
Step 2
The standby group names must be one and two. For FE 0/0, the command must be
standby 1 name one. For FE 0/1, the command must be standby 2 name two.
If you omit the group-name or if you enter a group name that doesnt begin with one or two, the
configuration will fail and there will be a mismatch in the information displayed by the show
redundancy and show standby commands.
Enable HSRP and assign an IP address to the virtual router. This address is the same for both the active
and standby routers.
Router(config-if)# standby group ip address
Step 3
Configure the time between hello packets and the time before other routers declare the active Hot
Standby or standby router to be down.
Router(config-if)# standby group timers [msec] hellotime [msec] holdtime
Note
Step 4
You must use 1 for the hello time and 3 for the hold time.
Indicate that the router can become the active router when its priority is higher than all other
HSRP-configured routers. Without preemption, a standby router will only transition to the active state
if HSRP hello messages cease. In the CDMA IP-RAN solution, there may be situations in which you
want a switchover to occur in the absence of a router or FE failure, therefore, preemption is required.
Router(config-if)# standby group preempt
Step 5
Specify other interfaces on the router for the HSRP process to monitor in order to alter the HSRP
priority for a given group. When using the MWR 1941-DC router in the CDMA IP-RAN solution, you
must configure each FE interface to track the multilink interface, the loopback interfaces, and the other
FE interface.
Router(config-if)# standby group track multilink number decrement_value
Router(config-if)# standby group track loopback number decrement_value
Router(config-if)# standby group track fastethernet number decrement_value
Note
In redundant configurations, you should issue standby track commands for both the health
interface (loopback101) and the revertive interface (loopback102) as well as for the backhaul
interface (multilink1). The decrement values must be as follows: 10 for the multilink, FE,
and health interfaces; 5 for the revertive interface.
78-13983-08
4-7
Chapter 4
Step 6
Specify a priority of 100.

Router(config-if)# standby group priority 100
Note
If you are using the MWR 1941-DC in a redundant configuration, you must also set the keepalives
under the FE interface to 1.
Router(config-if)# keepalive 1

Once you have configured the FE interface, enable it by doing the following while still in interface
configuration mode:
Step 1
Enable the interface.

Router(config-if)# no shutdown

To configure the multilink interfaces, complete the following tasks:
Configuring Multilink PPP, page 4-9
Configuring IP Address Assignment, page 4-9
Configuring PPP Multiplexing, page 4-10
Configuring RTP/UDP Compression, page 4-12
Configuring the RTP/UDP Compression Flow Expiration Timeout Duration, page 4-13
Configuring Routing Protocol Attributes, page 4-13
Configuring PIM, page 4-14
4-8
78-13983-08
Chapter 4

Configuring Multilink PPP

As higher-speed services are deployed, Multilink-PPP (MLP) provides a standardized method for
spreading traffic across multiple WAN links, while providing multivendor interoperability and
load-balancing on both inbound and outbound traffic.
A Multilink interface is a special virtual interface which represents a multilink PPP bundle. The
multilink interface serves to coordinate the configuration of the bundled link, and presents a single object
for the aggregate links. However, the individual PPP links that are aggregated together, must also be
configured. Therefore, to enable Multilink PPP on multiple serial interfaces, you need to first set up the
multilink interface, and then configure each of the serial interfaces and add them to the same multilink
interface.
The MWR 1941-DC router can support up to 16 T1 interfaces through the multilink interface.
To set up the multilink interface, do the following beginning in global configuration mode:
Step 1
Specify the multilink interface to be configured.

RPM-3(config)# interface multilink number
Step 2
Enable multilink PPP operation.

RPM-3(config-if)# ppp multilink
Step 3
If using Cisco IOS Release 12.3(15)MC2a or prior, enter the following command to specify an
identification number for the multilink interface.
RPM-3(config-if)# multilink-group group-number
If using Cisco IOS Release 12.3(11)T or later, enter the following command to specify an identification
number for the multilink interface:
RPM-3(config-if)# ppp multilink group group-number
Step 4
Enable IP processing on a the multilink interface without assigning an explicit IP address to the
interface.
RPM-3(config-if)# ip unnumbered loopback number
Where number is the number of the multilink loopback interface that you configured in Configuring
Loopback Interfaces.
Configuring IP Address Assignment

A point-to-point interface must be able to provide a remote node with its IP address through the IP
Control Protocol (IPCP) address negotiation process. The IP address can be obtained from a variety of
sources. The address can be configured through the command line, entered with an EXEC-level
command, provided by TACACS+ or the Dynamic Host Configuration Protocol (DHCP), or from a
locally administered pool.
IP address pooling uses a pool of IP addresses from which an incoming interface can provide an IP
address to a remote node through IPCP address negotiation process. IP address pooling also enhances
configuration flexibility by allowing multiple types of pooling to be active simultaneously.
78-13983-08
4-9
Chapter 4
To configure IP address assignment, do the following do the following while still in multilink interface
configuration mode:
Step 1
Specify an IP address, an address from a specific IP address pool, or an address from the Dynamic Host
Configuration Protocol (DHCP) mechanism to be returned to a remote peer connecting to this interface:
RPM-3(config-if)# peer default ip address {ip-address | dhcp | pool [pool-name]}
Configuring PPP Multiplexing

To enable and control the multiplexing of PPP frames, do the following while still in multilink interface
configuration mode:
Step 1
Enable PPP multiplexing:

RPM-3(config-if)# ppp mux
Step 2
Specify the parameters of multiplexing.

To set the maximum time delay, enter:
RPM-3(config-if)# ppp mux delay integer
To set the maximum length of the subframe, enter:

RPM-3(config-if)# ppp mux subframe length integer
To set maximum length of the superframe, enter:

RPM-3(config-if)# ppp mux frame integer
To set the maximum number of subframes in a superframe, enter:

RPM-3(config-if)# ppp mux subframe count integer
To set the default PPP protocol ID, enter:

RPM-3(config-if)# ppp mux pid integer
4-10
78-13983-08
Chapter 4

Configuring ACFC and PFC Handling During PPP Negotiation

Note
This feature requires Cisco IOS Release 12.2(15)MC1 and later be installed on the MWR 1941-DC
router.
ACFC and PFC handling during PPP negotiation can be configured. By default, ACFC/PFC handling is
not enabled.
To configure ACFC handling during PPP negotiation, do the following while in multilink interface
configuration mode:
Step 1
Enter the following command to configure how the router handles the ACFC option in configuration
requests received from a remote peer.
RPM-3(config-if)# ppp acfc remote {apply | reject | ignore}
Where:
Step 2
applyACFC options are accepted and ACFC may be performed on frames sent to the remote peer.
rejectACFC options are explicitly ignored.
ignoreACFC options are accepted, but ACFC is not performed on frames sent to the remote peer.
Enter the following command to configure how the router handles ACFC in its outbound configuration
requests.
RPM-3(config-if)# ppp acfc local {request | forbid}
Where:
requestThe ACFC option is included in outbound configuration requests.
forbidThe ACFC option is not sent in outbound configuration requests, and requests from a
remote peer to add the ACFC option are not accepted.
To configure PFC handling during PPP negotiation, do the following while in multilink interface
configuration mode:
Step 1
Enter the following command to configure how the router handles the PFC option in configuration
requests received from a remote peer.
RPM-3(config-if)# ppp pfc remote {apply | reject | ignore}
Where:
applyPFC options are accepted and ACFC may be performed on frames sent to the remote peer.
rejectPFC options are explicitly ignored.
ignorePFC options are accepted, but ACFC is not performed on frames sent to the remote peer.
78-13983-08
4-11
Chapter 4
Step 2
Enter the following command to configure how the router handles PFC in its outbound configuration
requests.
RPM-3(config-if)# ppp acfc local {request | forbid}
Where:
requestThe PFC option is included in outbound configuration requests.
forbidThe PFC option is not sent in outbound configuration requests, and requests from a remote
peer to add the PFC option are not accepted.
Configuring RTP/UDP Compression

Enabling RTP/UDP compression (cRTP/cUDP) on both ends of a low-bandwidth serial link can greatly
reduce the network overhead if there is a lot of RTP traffic on that slow link. This compression is
beneficial especially when the RTP payload size is small (for example, compressed audio payloads of
20-50 bytes).
Before you can enable RTP header compression, you must configure a serial line that uses PPP
encapsulation.
To configure RTP header compression, do the following while still in multilink interface configuration
mode:
Step 1
If using Cisco IOS release 12.2(15)MC2a or prior, enter the following command to enable RTP header
compression for serial encapsulations:
SRPM-3(config-if)# ip rtp header-compression
If using Cisco IOS release 12.3(11)T or later, enable RTP header compression for serial encapsulations
and suppress IP ID checking during RTP compression by entering the ip rtp header-compression
interface configuration command and specifying the ignore-id keyword option:
SRPM-3(config-if)# ip rtp header-compression ignore-id
Step 2
By default, the software supports a total of 16 RTP header compression connections on an interface. To
change that number, enter the following command:
RPM-3(config-if)# ip rtp compression-connections number
Note
The MWR 1941-DC supports up to 1000 RTP header compression connections on an

interface.
4-12
78-13983-08
Chapter 4

Configuring the RTP/UDP Compression Flow Expiration Timeout Duration

To minimize traffic corruption, cUDP flows expire after a period of time during which no packets are
passed. When this user defined 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 is received for that flow,
the compressor makes the CID for the flow available for new use. When a packet is received at the
decompressor after the duration of inactivity has been exceeded, 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
Failure of performance/latency scripts could occur if the expiration timeout duration is not changed to
the recommended 8 seconds.
To configure the duration of the cUDP flow expiration timeout, do the following while in multilink
interface configuration mode:
Step 1
To specify the duration of inactivity, in seconds, that when exceeded causes the cUDP flow to expire,
enter the following command:
RPM-3(config-if)# ppp iphc max-time seconds

When used in the CDMA IP-RAN solution, the multilink interface must be configured to support the
OSPF routing protocol.
To configure OSPF routing protocol attributes, do the following while still in interface configuration
mode:
Step 1
Enable OSPF Message Digest 5 (MD5) authentication:

RPM-3(config-if)# ip ospf message-digest-key key-id md5 key
Step 2
Specify the interval between hello packets that the Cisco IOS software sends on the interface:
RPM-3(config-if)# ip ospf hello-interval seconds
Step 3
Set the interval at which hello packets must not be seen before neighbors declare the router down:
RPM-3(config-if)# ip ospf dead-interval seconds
78-13983-08
4-13
Chapter 4
Configuring PIM
Because the MWR 1941-DC is used in a multicast PPP environment, you should configure the PIM mode
of the multilink interface.
To configure the PIM mode, do the following while still in interface configuration mode:
Step 1
Enter the following command:

RPM-3(config-if)# ip pim {sparse-mode | sparse-dense-mode | dense-mode [proxy-register
{list access-list | route-map map-name}]}

To configure a T1/E1 multiflex trunk interface, enter the following Cisco IOS commands at the router
prompt.
Note
Before you begin, disconnect all WAN cables from the router to keep it from trying to run the
AutoInstall process. The router tries to run AutoInstall whenever you power it on if there is a WAN
connection on both ends and the router does not have a valid configuration file stored in NVRAM
(for instance, when you add a new interface). It can take several minutes for the router to determine
that AutoInstall is not connected to a remote Transmission Control Protocol/Internet Protocol
(TCP/IP) host.
To configure the T1 interfaces, do the following while still in global configuration mode:
Step 1
Specify the controller that you want to configure. For information about interface numbering, see
Understanding MWR 1941-DC Router Interface Numbering, page 3-2.
Router(config)# controller t1 slot/port
Step 2
Specify the framing type.

Router(config-controller)# framing esf
Step 3
Specify the line code format.

Router(config-controller)# linecode b8zs
Step 4
Specify the channel group and time slots to be mapped. For the VWIC interfaces, you can configure two
channel-groups (0 and 1) on the first T1 port or you can configure one channel-group (0 or 1) on each
T1 port. Once you configure a channel group, the serial interface is automatically created.
4-14
78-13983-08
Chapter 4

Note
The default speed of the channel group is 56. To get full DS0/DS1 bandwidth, you must
configure a speed of 64.
Router(config-controller)# channel-group 0 timeslots 1-24 speed 64
Step 5
Configure the cable length.

Router(config-controller)# cablelength feet
Note
Step 6
Although you can specify a cable length from 0 to 450 feet, the hardware only recognizes two
ranges: 0 to 49 and 50 to 450. For example, entering 35 feet uses the 0 to 49 range. If you later change
the cable length to 40 feet, there is no change because 40 is within the 0 to 49 range. However, if you
change the cable length to 50, the 50 to 450 range is used. The actual number you enter is stored in
the configuration file.
Exit controller configuration mode.
Router(config-controller)# exit
Step 7
Configure the serial interface. Specify the T1 slot (always 0), port number, and channel group.
Router(config)# interface serial slot/port:0
Step 8
Assign an IP address and subnet mask to the interface. If the interface is a member of a Multilink
bundle (MLPPP), then skip this step.
Step 9
Before you can enable RTP header compression, you must have configured a serial line that uses PPP
encapsulation. Enter the following command to configure PPP encapsulation.
Router(config-if)# encapsulation ppp
Step 10
Enable keepalive packets on the interface and specify the number of times keepalive packets will be sent
without a response before bringing down the interface:
Router(config-if)# keepalive [period [retries]]
Note
Step 11
When enabled in an IP-RAN solution, the recommended configuration is keepalive 1 2 on

both the MWR 1941-DC serial interface and associated MGX-RPM-1FE-CP virtual template
interface.
Set the carrier delay for the serial interface.

Router(config-if)# carrier-delay number
Step 12
Return to Step 1 to configure the second port on the VWIC and the ports on any additional VWICs.
Step 13
Exit to global configuration mode.

78-13983-08
4-15
Chapter 4
To configure the E1 interfaces, do the following while still in global configuration mode:
Step 1
Specify the controller that you want to configure. Controller E1 0/0 maps to the first port of the VWIC
in slot 0. Controller E1 0/1 maps to the second port of the VWIC in slot 0.
Router(config)# controller e1 slot/port
Step 2

Router(config-controller)# framing crc4
Step 3

Router(config-controller)# linecode hdb3
Step 4
Specify the channel group and time slots to be mapped. For the VWIC interfaces, you can configure
channel-group 0 and 1 on one port or one channel-group (either 0 or 1) on each port. Once you configure
a channel group, the serial interface is automatically created.
Router(config-controller)# channel-group 0 timeslots 1-24 speed 64
Note
Step 5
The default speed of the channel group is 56. To get full DS0/DS1 bandwidth, you must
configure a speed of 64.
Configure the serial interface. Specify the E1 slot (always 0), port number, and channel group.
Router(config-controller)# interface serial slot/port:0
Step 6

Router(config-controller)# cablelenth feet
Note
Step 7
Although you can specify a cable length from 0 to 450 feet, the hardware only recognizes
two ranges: 0 to 49 and 50 to 450. For example, entering 35 feet uses the 0 to 49 range. If
you later change the cable length to 40 feet, there is no change because 40 is within the 0 to
49 range. However, if you change the cable length to 50, the 50 to 450 range is used. The
actual number you enter is stored in the configuration file.
Assign an IP address and subnet mask to the interface. If the interface is a member of a Multilink bundle
(MLPPP), then skip this step.
Step 8
Before you can enable RTP header compression, you must have configured a serial line that uses PPP
encapsulation. Enter the following command to configure PPP encapsulation.
Router(config-if)# encapsulation ppp
Step 9
Enable keepalive packets on the interface and specify the number of times keepalive packets will be
sent without a response before bringing down the interface:
Router(config-if)# keepalive [period [retries]]
4-16
78-13983-08
Chapter 4

Note
Step 10
When enabled in an IP-RAN solution, the recommended configuration is keepalive 1 2 on

both the MWR 1941-DC serial interface and associated MGX-RPM-1FE-CP virtual template
interface.

Router(config-if)# carrier-delay number
Step 11
Return to Step 1 to configure the second port on the VWIC and the ports on any additional VWICs.
Step 12
Exit to global configuration mode.


To use QoS on the MWR 1941-DC router, you must first create a class map. The class map defines the
criteria that a packet must match to be placed in that class. Once you have created a class map, the router
can recognize packets that are subject to QoS. You must then tell the router the action to take on those
packets by creating a policy map.Once you have completed the creation of a QoS boilerplate, you can
assign it to an interface.
Note
The QoS functionality of the MWR 1941-DC router is built on the same code as the Cisco 10000 ESR
(with some exceptions). For more information about the QoS feature, see Configuring Quality of
Service (http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10ksw/qosos.htm) and the
Cisco 10000 Series ESR Quality of Service feature module
(http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/fm_qos.htm), as well as the
Cisco IOS Quality of Service Solutions Configuration Guide and the Cisco IOS Quality of Service
Solutions Command Reference.

For each class map that you want to create, do the following in global configuration mode:
Step 1
Assign a name to your class map.

Router(config)# class-map [match-all | match-any] class_name
Where match-any means a single match rule is sufficient for class membership and match-all means
only those packets that have all the attributes you specify are part of the class.
When you enter the class-map command, you are placed in class map configuration mode.
Step 2
Describe the characteristics of the packets that are subject to QoS using one or more of the following.
Router(config-cmap)#
match
match
match
match
match
access-group number
ip dscp number
ip precedence number
input-interface interface-name
protocol protocol
78-13983-08
4-17
Chapter 4
match access-group specifies access control list (ACL) that a packet must match.
match ip dscp specifies the IP differentiated service code point (DSCP) that a packet must match.
match ip precedence specifies the precedence values (0-7) that a packet must match.
match input-interface specifies the name of the input interface used as a match criterion.
match input-protocol specifies the protocol that a packet must match.
For more information about these commands, see the Cisco IOS Quality of Service Solutions Command
Reference.
Step 3
Exit class map configuration mode.

Router(config-cmap)# exit

To create a policy map, do the following in global configuration mode:
Step 1
Assign a name to your policy map.

Router(config)# policy-map policy_name
When you enter the policy-map command, you are placed in policy map configuration mode.
Step 2
Associate the policy map with a class map.

Router(config-pmap)# class class_name
Specify the same class_name as you did in Step 1 of Creating a Class Map. When you enter the class
command, you are placed in class submode of the policy-map configuration mode.
Step 3
Describe the QoS actions you want the router to perform when the router encounters a packet that has
the characteristics described by the class map. Use one or more of the following commands:
Router(config-pmap-c)# priority percent number
Router(config-pmap-c)# bandwidth percent number
Router(config-pmap-c)# queue-limit number
Router(config-pmap-c)# priority rate-in-kbps
Router(config-pmap-c)# shape {average | peak} cir [bc] [be]
Router(config-pmap-c)# shape max-buffers number-of-buffers
priority percent gives priority to a class of traffic belonging to a policy map and specifies that a
certain percentage of the available bandwidth should be reserved for this class.
bandwidth percent specifies the bandwidth allocated for a class belonging to a policy map.
queue-limit specifies the maximum number of packets the queue can hold for a class policy
configured in a policy map.
priority enables low-latency priority queuing, which allows you to assign a specified share of the
link bandwidth to one queue that receives priority over all others. Low-latency priority queueing
minimizes the packet-delay variance for delay-sensitive traffic, such as live voice and video.
4-18
78-13983-08
Chapter 4

shape and shape max-buffers are used with class-based weighted fair queuing (CB-WFQ), which
allows you to control the traffic going out an interface in order to match its transmission to the speed
of the remote target interface.
Note
The bandwidth percent and priority percent commands cannot be used in the same
class, within the same policy map. These commands can be used together in the same
policy map, however.
Reference.
Step 4
To configure the Class-Based Packet Marking feature, you must configure either an IP Precedence value
or an IP differentiated services code point (DSCP). The QOS group is optional.
Router(config-pmap-c)# set ip dscp ip-dscp-value
Router(config-pmap-c)# set ip precedence ip-precedence-value
Router(config-pmap-c)# set qos-group qos-group-value
set ip dscp marks a packet by setting the IP DSCP value.
set ip precedence marks a packet by setting the IP Precedence bits in the ToS byte.
set qos-group associates a local QoS group value with a packet.
Reference.
Step 5
Repeat Step 2 and Step 3 for each class map.
Step 6
Exit policy map configuration mode.

Router(config-pmap-c)# exit
Router(config-pmap)# exit

To assign a QoS boilerplate to a multilink interface, do the following in global configuration mode.
Step 1
Access the multilink interface configuration mode.

Router(config)# interface multilink number
Step 2
Assign the QoS boilerplate to the multilink interface.

Router(config-if)# service-policy output policy_name
78-13983-08
4-19
Chapter 4
The MWR 1941-DC router can be used in either a redundant configuration (preferable) or as a
stand-alone device.
Note
Before implementing redundancy, you must disable EADI capabilities on the router using the
diable-eadi global configuration command and also configure HSRP under the Fast Ethernet
interface. See the Configuring HSRP Support section on page 4-6 for more information on
configuring HSRP under the Fast Ethernet interface.
Redundant MWR 1941-DCs

For redundancy, the MWR 1941-DC router makes use of the existing HSRP feature. However, additional
controls are needed for the MWR 1941-DC. In a redundant configuration, the MWR 1941-DC router
must track the status of the health and revertive loopback interfaces as well as the backhaul interface.
To configure an MWR 1941-DC for use in a redundant configuration, do the following starting in global
configuration mode:
Step 1
Enter redundancy mode.

Router(config)# redundancy
Step 2
Enter the y-cable mode.

Router(config-r)# mode y-cable
Step 3
Specify the loopback interface to be used to monitor the health of the router and for revertive purposes.
Router(config-r-y)# standby use-interface interface health
Router(config-r-y)# standby use-interface interface revertive
Note
Step 4
The interfaces that you specify for the health and revertive interfaces should match those that
you configured and tracked in Configuring Loopback Interfaces. (We recommend you use
loopback101 for the health and loopback102 for the revertive interface).
Specify the interface to be used for backhauling.

Router(config-r-y)# standby use-interface interface backhaul
Note
Step 5
The interface that you specify for the backhaul must be an MLPPP interface. If you want to
use a serial interface as the backhaul, you must first configure that interface to be part of an
MLPPP bundle. The interface that you specify for the backhaul interface should match one
of those that you configured and tracked in Configuring Loopback Interfaces.
Exit y-mode configuration mode.

Router(config-r-y)# exit
4-20
78-13983-08
Chapter 4

To verify the status of the relays on an MWR 1941-DC router, use the show controllers command.
Stand-Alone MWR 1941-DC

The MWR 1941-DC router has relays that work with a special y cable for redundancy and are
controlled by HSRP. You can, however, use the MWR 1941-DC as a stand-alone device. If you choose
not to use the MWR 1941-DC in a redundant configuration, you should not configure HSRP and you
must control the relays of the VWIC card manually.
To manually set the relays to open or closed, do the following starting in global configuration mode:
Step 1

Step 2

Step 3
Specify that the router is to be used as a stand-alone device. This command closes the relays.
Router(config-r-y)# standalone
Step 4


Note
This feature requires Cisco IOS Release 12.2(8)MC2d and later be installed on the MWR 1941-DC
router.
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. To monitor the quality of individual links in a multilink
bundle, you can configure the Link Noise Monitor (LNM) on your MWR 1941-DC router
The LNM detects, alerts, and removes 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:
Line Code Violation (LCV)A Bi-Polar Violation (BPV) or Excessive Zeroes (EXZ) error has
occurred.
Path Code Violation (PCV)A Cyclic Redundancy Check (CRC) error, which is generally caused
by one or more LCV or logic errors, has occurred in a time slot.
78-13983-08
4-21
Chapter 4
The LNM provides the following types of noise monitors:
Link WarningIssues a warning when the noise level of a link exceeds a user-defined threshold and
notifies the operator when the noise level improves to the point that it drops below a second
user-defined threshold.
Link RemovalIssues an error and removes a link from service when the noise level of the link
exceeds a user-defined threshold and restores the link and provides notification when the noise level
improves to the point that it drops below a second user-defined threshold.
Note
If the noise level on the last active link in a multilink bundle exceeds the Link Removal
threshold, an alert is issued but the link will not be removed from service. If this situation
occurs, the standard T1 error rate is used to determine if the last active link must be
removed from service.
Usage Notes
When configuring the LNM, please note the following:
If the warn and remove keywords are specified without any other options, the LCV and PCV
thresholds and duration defaults will be use to determine (set) and clear (clear) the condition.
If the span command is issued with the set keyword specified (defining the LNM type and
parameters to use to determine a condition exists) and the command is not issued again with the
clear keyword specified (defining the parameters used to clear a condition), or vice versa, the values
configured for the threshold and duration will be used for both.
If the span command is issued without either the set or clear keywords specified, set is the default.
The set and clear keywords can only be specified if the threshold and/or duration has been specified.
If the PCV threshold is not configured (using the pcv keyword and value), the threshold is calculated
using Gaussian probability distribution that is representative of most noise environments.
The following SYSLOG messages have been added for fault notification:
- %LNM-4- WARNEXCEED:Controller <Controller IF>, exceeded noise warning threshold
<int>, duration <int>
- %LNM-4- WARNIMPROVE:Controller <Controller IF>, noise improved below threshold
- %LNM-2-REMOVE:Interface <Serial IF> removed, noise exceeded threshold <int>,
duration <int>
- %LNM-2- RESTORE:Interface <Serial IF> restored, noise improved below threshold
- %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>
4-22
78-13983-08
Chapter 4

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:
warnEnables Link Warning monitoring on the link.
removeEnables Link Removal monitoring on the link.
lcv valueThreshold (in bit errors per second) that when exceeded for the configured duration when
the set keyword has been specified, creates a condition (warning or link removal), or when fallen
below for the configured duration when the clear keyword has been specified, clears the condition.
For T1 links:
Valid range is 5 to 1544.
For Link Warning monitoring, the default is 15.
For Link Removal monitoring, the default is 154.
For E1 links,
pcv valueNumber of time slots in errors per second. If not specified by the user, this value is
calculated from the LCV threshold based on a Gaussian distribution that matches typical
noise-induced errors.
For T1 links:
For E1 links,
duration secondsNumber of seconds that a threshold must be exceeded to create a condition or

fallen below to clear a condition. Valid range is 1 to 600. The default is 10.
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.
setSpecifies that the values configured for the span command are to be used to set a condition.
clearSpecifies that the values configured for the span command are to be used to clear a
condition.
78-13983-08
4-23
Chapter 4

To prevent the loss of the router configuration, save it to non-volatile random access memory (NVRAM).
To save the configuration to NVRAM, do the following:
Step 1
Exit configuration mode.

Router(config)# exit
Note
Step 2
You can press Ctrl-z in any mode to immediately return to enable mode (Router#), instead
of entering exit, which returns you to the previous mode.
Save the configuration changes to NVRAM so that they are not lost during resets, power cycles, or power
outages.

To verify the configuration of the MWR 1941-DC, enter the following command:
MWR1900-1#show running-config
hostname MWR1900-1
!
boot system slot0:mwr-1900-boot
!
! description Loopback IP for O & M
!
interface loopback 0
ip address 10.1.170.3 255.255.255.255
!
! description Loopback IP for IP Unnumbered
!
interface loopback 2
ip address 192.168.170.2 255.255.255.255
!
interface loopback101
description Health Loopback Interface
no ip address
!
interface loopback102
description Revertive Loopback Interface
no ip address
!
enable password cisco
!
memory-size iomem 25
!
redundancy
mode y-cable
standby use-interface Loopback101 health
standby use-interface Loopback102 revertive
standby use-interface Multilink2 backhaul
4-24
78-13983-08
Chapter 4

!
controller T1 0/0
framing esf
cablelength short 133ft
clock source internal
linecode b8zs
channel-group 0 timeslots 1-1 speed 64
!
controller T1 0/1
framing esf
linecode b8zs
cablelength short 133ft
!
!
class-map match-all class1_fch
match ip dscp cs5
class-map match-all class2_sch
match ip dscp cs4
class-map match-any class3_paging_ospf
match ip dscp cs3
match access-group 101
!
policy-map llq-policy
class class1_fch
priority percent 68
class class2_sch
bandwidth percent 20
queue-limit 128
class class3_paging_ospf
bandwidth percent 2
queue-limit 128
class class-default
queue-limit 512
!
ip dhcp excluded-address 192.168.146.1 192.168.146.3
ip dhcp ping packets 0
!
ip dhcp pool pbts
network 192.168.146.0 255.255.255.0
bootfile CENOMIbts.img
next-server OMCR-IPaddr
option 43 ascii "Logical-IPaddr CENOMI-IPaddr another-IPaddr SpanMapping"
default-router 192.168.146.3
dns-server OMCR-IPaddr
lease 0 0 1
!
ip routing
ip subnet-zero
ip classless
ip multicast-routing
ip tftp source-interface Loopback 0
cdp run
!
! Setup sys logging to OMCIP-CW2000
!
logging on
logging buffered 4
logging cw4mw
logging trap 5
logging source-interface Loopback0
!
! Setup SNMP
78-13983-08
4-25
Chapter 4
!
snmp community private rw
snmp community public ro
snmp-server enable traps
snmp-server trap-source Loopback 0
snmp-server host cw4mw public
!
! Setup useful aliases
!
ip host omcr OMCR_ip_address
ip host omcip OMCIP_ip_address
ip host cw4mw CW4MW_ip_address
ip host btsha-other-0 192.168.146.2
ip host btsha-other-1 192.168.147.2
!
!interface Multilink1
description Backhaul Interface
ip unnumbered loopback 2
cdp enable
ppp multilink
ip ospf hello-interval 1
ip ospf dead-interval 3
ip ospf message-digest-key 1 md5 mymd5pw
!
interface Multilink2
description
ip unnumbered loopback 2
ip mroute-cache
ip mtu 256
cdp enable
ppp multilink
ip rtp header-compression ignore-id
ip rtp compression-connections 700
ppp mux
ppp mux subframe length 64
ppp mux subrame count 15
ppp mux frame 256
ppp mux delay 800
ppp mux pid 0x2067
ip pim sparse-mode
ip pim version 2
service-policy output llq-policy
!
ip address 192.168.146.1 255.255.255.0
no ip proxy-arp
no ip mroute-cache
keepalive 1
full-duplex
speed 100
ntp broadcast version 3
standby 1 ip 192.168.146.3
standby 1 timers 1 3
standby 1 priority 100
standby 1 preempt
standby 1 name one
standby 1 track FastEthernet0/1 10
standby 1 track Loopback101 10
standby 1 track Multilink2 10
4-26
78-13983-08
Chapter 4

ip
ip
ip
ip
ip
ospf dead-interval 3
ospf message-digest-key 1 md5 mymd5pw
pim sparse-mode
pim version 2
pim query-interval 2
ip address 192.168.147.1 255.255.255.0
standby 2 timers 1 3
standby 2 preempt
standby 2 priority 100
standby 2 ip 192.168.147.3
standby 2 name two
standby 2 track Fa0/0 10
standby 2 track Multilink2 10
keepalive 1
speed 100
full-duplex
ntp broadcast version 3
ip pim sparse-mode
ip pim version 2
ip pim query-interval 2
!
!
!interface Serial0/0:0
no ip address
encapsulation ppp
keepalive 1 2
ppp multilink
ppp multilink group 1
!
interface Serial0/1:0
no ip address
encapsulation ppp
keepalive 1 2
ppp multilink
ppp multilink group 2
!
router ospf 1
log-adjacency-changes
area 2 nssa
area 2 authentication message-digest
auto-cost reference-bandwidth 10240
timers spf 1 10
redistribute ospf 2 metric-type 1 subnets
redistribute static metric-type 1 subnets
network 192.168.170.2 0.0.0.3 area 2
distribute-list 10 out
distance ospf external 125
summary-address area-51-prefix mask
!
router ospf 2
log-adjacency-changes
auto-cost reference-bandwidth 10240
area 51 authentication message-digest
timers spf 1 10
redistribute ospf 1 metric-type 1 subnets tag 202051
network 192.168.146.0 0.0.0.255 area 51
network 192.168.147.0 0.0.0.255 area 51
78-13983-08
4-27
Chapter 4
network 10.0.0.0 0.255.255.255 area 51

default-information originate metric 100 metric-type 1
distribute-list 11 out
distance 120
!
ip route 64.102.16.25 255.255.255.255 FastEthernet0/0
ip route 64.102.16.25 255.255.255.255 192.168.1.10
!
Notes
Keepalives must be set for all Ethernet interfaces to ensure proper redundant behavior. A keepalive
value of 1 has been selected for maximum responsiveness.
Configuring no ip proxy-arp is helpful to avoid confusion with routes and ARP caches.
In a redundant configuration, both MWR 1941-DCs share a common IP address for their Multilink
interface.

You can use Ciscos network management applications, such as CiscoWorks2000 for Mobile Wireless
(CW4MW), to monitor and manage aspects of the MWR 1941-DC.
To enable remote network management of the MWR 1941-DC, do the following:
Step 1
At the privileged prompt, enter the following command to access configuration mode:
Router(config)#
Step 2
End with CNTL/Z.
At the configuration prompt, enter the following command to assign a host name to each of the network
management workstations:
Router(config)# ip host hostname ip_address
Where hostname is the name assigned to the Operations and Maintenance (O&M) workstation and
ip_address is the address of the network management workstation.
Step 3
Enter the following commands to create a loopback interface for O&M:

Step 4

Step 5
At the configuration prompt, enter the following command to specify the recipient of a Simple Network
Management Protocol (SNMP) notification operation:
Router(config)# snmp-server host hostname [traps | informs] [version {1 | 2c | 3 [auth |
noauth | priv]}] community-string [udp-port port] [notification-type]
Where hostname is the name assigned to the CW4MW workstation with the ip host command in Step 2.
4-28
78-13983-08
Chapter 4

Step 6
Enter the following commands to specify the public and private SNMP community names:
Router(config)# snmp-server community public RO
Router(config)# snmp-server community private RW
Step 7
Enter the following command to enable the sending of SNMP traps:

Router(config)# snmp-server enable traps
Step 8
Enter the following command to specify the loopback interface from which SNMP traps should
originate:
Router(config)# snmp-server trap-source loopback number
Where number is the number of the loopback interface you configured for the O&M in Step 3.
Step 9
At the configuration prompt, press Ctrl-Z to exit configuration mode.
Step 10
Write the new configuration to nonvolatile memory as follows:


To monitor and maintain the MWR 1941-DC router (including the multilink, VWIC, and FE interfaces)
and to view information about the PPP mux and header compression configuration, use the following
commands:
Command
Purpose
show ip rtp header-compression
Displays RTP header compression statistics.
show interface fastethernet slot/port
Displays the status of the FE interface.
show ppp multilink
Displays MLP and multilink bundle information.
show ppp multilink interface number
Displays multilink information for the specified

interface.
show ppp mux interface interface
Displays statistics for PPP frames that have passed

through a given multilink interface.
show controllers fastethernet slot/port
Displays information about initialization block,

transmit ring, receive ring and errors for the Fast
Ethernet controller chip.
show controllers t1
Displays information about the cable length, framing,

firmware, and errors associated with the T1. With the
MWR 1941-DC, this command also displays the
status of the relays on the VWIC.
show redundancy
Displays current redundant setting and recent

changes in state.
show standby
Displays HSRP configuration information.
clear counters fastethernet slot/port
Clears interface counters.
clear ppp mux interface
Clears the PPP mux counters on the specified

interface.
clear ip rtp header-compression
Clears RTP header compression structures and

statistics.
78-13983-08
4-29
Chapter 4
Where to Go Next
Command
Purpose
show controllers
Displays all network modules and their interfaces.

Displays the status of the VWIC relays when a VWIC
is installed.
show interface type slot/port
Displays the configuration and status of the specified

interface.
show protocols
Displays the protocols configured for the router and

the individual interfaces.
Where to Go Next
advanced configuration topics. These publications are available on the Documentation CD-ROM
that came with your router, on the World Wide Web from Ciscos home page, or you can order
printed copies.
The System Error Messages and Debug Command Reference publications for troubleshooting
information
4-30
78-13983-08
C H A P T E R
Cisco MWR 1941-DC Router IP-RAN Command

Reference
This chapter contains information about commands that were introduced specifically in support of
implementing the Cisco MWR 1941-DC router in an IP-RAN:
The following commands have been added or changed:
clear ppp mux
mode y-cable
ip rtp compression-connections
ip rtp header-compression
ppp mux
ppp mux delay
ppp mux frame
ppp mux pid
ppp mux subframe length
ppp mux subframe count
redundancy
show ppp mux
show redundancy
standalone
standby use-interface
The following commands were not altered but have been included for your convenience:
keepalive
OL-11503-01
5-1
Chapter 5

To clear Real-Time Transport Protocol (RTP) header compression structures and statistics, use the clear
ip rtp header-compression EXEC command.
clear ip rtp header-compression [interface-type interface-number]
Syntax Description
type number
Command Modes
EXEC
Command History
Release
Modification
11.3
This command was introduced.
12.2(8)MC2
This command was incorporated in Cisco IOS 12.2(8)MC2.
12.2(15)MC1
12.3(11)T
This command was incorporated in Cisco IOS 12.3(11)T.
(Optional) Interface type and number.
Usage Guidelines
If this command is used without an interface type and number, it clears all RTP header compression
structures and statistics.
Examples
The following example clears RTP header compression structures and statistics for multilink interface 1:
clear ip rtp header-compression multilink1
Related Commands
Command
Description
Enables RTP header compression.
5-2
OL-11503-01
Chapter 5

clear ppp mux
clear ppp mux

To clear PPP mux statistics, use the clear ppp mux EXEC command.
clear ppp mux [interface interface]
Syntax Description
interface
Defaults
If no interface is specified, statistics for all multilink and serial interfaces are cleared.
Command Modes
EXEC
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
(Optional) The identifier of the multilink or serial interface for which you
want to clear counters.
Usage Guidelines
None
Examples
The following example clears PPP mux statistics for multilink interface 1:
clear ppp mux interface multilink1
Related Commands
Command
Description
show ppp mux
Displays PPP mux counters for the specified multilink interface.
OL-11503-01
5-3
Chapter 5
keepalive
keepalive
To enable keepalive packets and to specify the number of times that the Cisco IOS software tries to send
keepalive packets without a response before bringing down the interface or before bringing the tunnel
protocol down for a specific interface, use the keepalive command in interface configuration mode.
When the keepalive function is enabled, a keepalive packet is sent at the specified time interval to keep
the interface active. To turn off keepalive packets entirely, use the no form of this command.
keepalive [period [retries]]
no keepalive [period [retries]]
Syntax Description
period
(Optional) Integer value in seconds greater than 0. The default is 10.
retries
(Optional) Specifies the number of times that the device will continue to
send keepalive packets without response before bringing the interface down.
Integer value greater than 1 and less than 255. If omitted, the value that was
previously set is used; if no value was specified previously, the default of 5
is used.
If using this command with a tunnel interface, specifies the number of times
that the device will continue to send keepalive packets without response
before bringing the tunnel interface protocol down.
Defaults
period: 10 seconds
retries: 5
If you enter only the keepalive command with no arguments, defaults for both arguments are used.
If you enter only the keepalive command and the timeout (period) parameter, the default number of
retries (5) is used.
If you enter the no keepalive command, keepalive packets are disabled on the interface.
Command Modes
Command History
Release
Modification
10.0
12.2(8)T
The retries argument was added and made available on tunnel interfaces.
12.2(13)
The default value for the retries argument was increased to 5.
12.2(8)MC2
12.2(15)MC1
12.3(11)T
5-4
OL-11503-01
Chapter 5

keepalive
Usage Guidelines
Keepalive Time Interval
You can configure the keepalive time interval, which is the frequency at which the Cisco IOS software
sends messages to itself (Ethernet and Token Ring) or to the other end (serial and tunnel), to ensure that
a network interface is alive. The interval is adjustable in 1-second increments down to 1 second. An
interface is declared down after three update intervals have passed without receiving a keepalive packet
unless the retry value is set higher.
Setting the keepalive timer to a low value is very useful for rapidly detecting Ethernet interface failures
(transceiver cable disconnecting, cable not terminated, and so on).
Line Failure
A typical serial line failure involves losing Carrier Detect (CD) signal. Because this sort of failure is
typically noticed within a few milliseconds, adjusting the keepalive timer for quicker routing recovery
is generally not useful.
Keepalive Packets with Tunnel Interfaces
GRE keepalive packets may be sent from both sides of a tunnel, or from just one side. If they are sent
from both sides, the period and retry parameters can be different at each side of the link. If you configure
keepalives on only one side of the tunnel, the tunnel interface on the sending side might perceive the
tunnel interface on the receiving side to be down because the sending interface is not receiving
keepalives. From the receiving side of the tunnel, the link appears normal because no keepalives were
enabled on the second side of the link.
Dropped Packets
Keepalive packets are treated as ordinary packets, so it is possible that they will be dropped. To reduce
the chance that dropped keepalive packets will cause the tunnel interface to be taken down, increase the
number of retries.
Note
Examples
When adjusting the keepalive timer for a very low bandwidth serial interface, large datagrams can
delay the smaller keepalive packets long enough to cause the line protocol to go down. You may need
to experiment to determine the best values to use for the timeout and the number of retry attempts.
The following example shows how to set the keepalive interval to 3 seconds:
Router(config)# interface ethernet 0
Router(config-if)# keepalive 3
The following example shows how to set the keepalive interval to 3 seconds and the retry value to 7:
Router(config)# interface tunnel 1
Router(config-if)# keepalive 3 7
OL-11503-01
5-5
Chapter 5
To specify the total number of Real-Time Transport Protocol (RTP) header compression connections that
can exist on an interface, use the ip rtp compression-connections interface configuration command. To
restore the default value, use the no form of this command.
ip rtp compression-connections number
no ip rtp compression-connections
Syntax Description
number
Defaults
16 connections
Command Modes
Command History
Release
Modification
11.3
12.0(7)T
For PPP and High-Level Data Link Control (HDLC) encapsulation, the
maximum number of connections increased from 256 to 1000.
Number of RTP header compression connections the cache supports, in the

range from 3 to 1800. The default is 16 connections.
For Frame Relay encapsulation, the maximum number of connections

increased to 256. The maximum value for Frame Relay is fixed, not
configurable.
Examples
12.1(4)E
This command was supported on Cisco 7100 series routers.
12.2(8)MC2
The upper limit for the MWR 1941-DC is set at 1000.
12.2(14)S
This command was integrated into Cisco IOS Release 12.2(14)S.
12.2(15)MC1
12.3(11)T
12.2(15)MC2h
The upper limit for MWR 1941-DC is set at 1800.
The following example changes the number of RTP header compression connections supported to 150:
interface serial 0
encapsulation ppp
ip rtp header-compression ignore-id
5-6
OL-11503-01
Chapter 5

Related Commands
Command
Description
show ip rtp
header-compression
OL-11503-01
5-7
Chapter 5
To enable Real-Time Transport Protocol (RTP) header compression, use the ip rtp header-compression
interface configuration command. To disable RTP header compression, use the no form of this command.
ip rtp header-compression [passive] [ignore-id]
no ip rtp header-compression
Syntax Description
passive
(Optional) Compresses outgoing RTP packets only if incoming RTP packets

on the same interface are compressed. This option is not applicable on PPP
links.
ignore-id
(Optional) Suppresses the IP ID checking in RTP/UDP header compression.
Defaults
Disabled
Command Modes
Command History
Release
Modification
11.3
12.2(15)MC1
This command was incorporated in Cisco IOS Release 12(15)MC1 and the
ignore-id keyword option was added.
12.3(11)T
This command was incorporated in Cisco IOS Release 12.3(11)T.
Usage Guidelines
If you use this command without the passive keyword, the software compresses all RTP traffic.
You can compress IP/UDP/RTP headers and IP/UDP headers to reduce the size of your packets.
Compressing headers is especially useful for RTP, because RTP payload size can be as small as 20 bytes,
and the decompressed header is 40 bytes.
RTP header compression is supported on serial lines using PPP encapsulation. You must enable
compression on both ends of a serial connection.
Examples
The following example enables RTP header compression on fast ethernet interface 1 and limits the
number of RTP header compression connections to 10:
interface serial 0
encapsulation ppp
Related Commands
5-8
OL-11503-01
Chapter 5

Command
Description
clear ip rtp
header-compression
Clears RTP header compression structures and statistics.
ip rtp
compression-connections
Specifies the total number of RTP header compression connections

that can exist on an interface.
show ip rtp
header-compression
OL-11503-01
5-9
Chapter 5
mode y-cable
mode y-cable
To access the command mode that allows you to manually control the relays on the VWIC card, use the
mode y-cable command.
mode y-cable
Syntax Description
This command has no parameters, it invokes the y-cable mode.
Defaults
There are no default settings or behaviors.
Command Modes
Redundancy configuration
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
Examples
The following example enables y-cable mode.

mode y-cable
Related Commands
Command
Description
standalone
Indicates whether the MWR 1941-DC router is being used as a

standalone device and manually sets the relays.
Designates a loopback interface as a health or revertive interface.
redundancy
Invokes redundancy mode.
5-10
OL-11503-01
Chapter 5

ppp mux
ppp mux
To enable PPP multiplexing/demultiplexing, use the ppp mux command in interface configuration
mode. To disable PPP multiplexing/demultiplexing, use the no form of this command.
ppp mux
no ppp mux
Syntax Description
This command has no parameters.
Defaults
PPP multiplexing/demultiplexing is disabled by default.
Command Modes
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
Examples
The following example enables PPP multiplexing/demultiplexing.

ppp mux
Related Commands
Command
Description
ppp mux delay
Sets the maximum delay.
ppp mux frame
Sets the maximum length of the PPP superframe.
ppp mux pid
Sets the default PPP protocol ID.
Sets the maximum number of subframes in a superframe.
Sets the maximum length of the PPP subframe.
show ppp mux
OL-11503-01
5-11
Chapter 5
ppp mux delay
ppp mux delay

To set the maximum time the processor can wait before sending a superframe, use the ppp mux delay
command in interface configuration mode. To set the maximum delay to the default, use the no form of
this command.
ppp mux delay integer
no ppp mux delay
Syntax Description
integer
Defaults
The default maximum delay is 0, which indicates that a superframe will be sent when the transmit queue
is full.
Command Modes
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
The maximum number of microseconds that the processor can wait before
sending out a PPP superframe. Possible values are 0 through 4000000
microseconds.
Usage Guidelines
To use this command, you must first enable PPP multiplexing/demultiplexing.
Examples
The following example sets the maximum delay to 5 microseconds.

ppp mux delay 5
Related Commands
Command
Description
ppp mux
Enables PPP multiplexing/demultiplexing
ppp mux frame
ppp mux pid
show ppp mux
5-12
OL-11503-01
Chapter 5

ppp mux frame
ppp mux frame

To set the maximum length (in bytes) of the PPP superframes, use the ppp mux frame command in
interface configuration mode. To set the maximum length to the default, use the no form of this
command.
ppp mux frame integer
no ppp mux frame
Syntax Description
integer
Defaults
The default maximum length is 197.
Command Modes
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
The maximum number of bytes in any multiplexed PPP superframe. Possible

values are 1 through 512 bytes.
Usage Guidelines
Examples
The following example sets the maximum superframe length to 80 bytes.

ppp mux frame 80
Related Commands
Command
Description
ppp mux
ppp mux delay
ppp mux pid
show ppp mux
OL-11503-01
5-13
Chapter 5
ppp mux pid
ppp mux pid

To set the default receiving PPP protocol ID, use the ppp mux pid command in interface configuration
mode. To remove this configuration, use the no form of this command.
ppp mux pid integer
no ppp mux pid
Syntax Description
integer
Defaults
The default is 33 (0x21), which is the IP protocol.
Command Modes
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
The default value of the PPP protocol ID. Possible values are 0 through
65534.
Usage Guidelines
Examples
The following example sets the default PPP protocol ID to 8.

ppp mux pid 8
Related Commands
Command
Description
ppp mux
ppp mux delay
ppp mux frame
show ppp mux
5-14
OL-11503-01
Chapter 5


To set the maximum length (in bytes) of the PPP subframes, use the ppp mux subframe length
command in interface configuration mode. To set the maximum length to the default, use the no form of
this command.
ppp mux subframe length integer
no ppp mux subframe length
Syntax Description
integer
Defaults
The default maximum length is 195.
Command Modes
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
The maximum number of bytes in any single subframe that is to be

multiplexed. Possible values are 1 through 512 bytes.
Usage Guidelines
To use this command, you must first enable PPP multiplexing/demultiplexing. The maximum length of
the subframe should be the maximum length of the superframe minus the length of the L2 header.
Examples
The following example sets the maximum subframe length to 20 bytes.

ppp mux subframe length 20
Related Commands
Command
Description
ppp mux
ppp mux delay
ppp mux frame
ppp mux pid
show ppp mux
OL-11503-01
5-15
Chapter 5

To set the maximum number of PPP subframes that can be contained in a superframe, use the ppp mux
subframe count command in interface configuration mode. To set the maximum number to the default,
use the no form of this command.
ppp mux subframe count integer
no ppp mux subframe count
Syntax Description
integer
Defaults
The default maximum is 15.
Command Modes
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
The maximum number of subframes that can be contained in a superframe.

Possible values are 1 through 15 bytes.
Usage Guidelines
Examples
The following example sets the maximum subframe count to 20 bytes.

ppp mux subframe count 20
Related Commands
Command
Description
ppp mux
ppp mux delay
ppp mux frame
ppp mux pid
show ppp mux
5-16
OL-11503-01
Chapter 5

redundancy
redundancy
To access the command mode that allows you to configure aspects of redundancy, use the redundancy
command.
redundancy
Syntax Description
This command has no parameters, it invokes the redundancy mode.
Defaults
There are no default settings or behaviors.
Command Modes
Global configuration
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
Examples
The following example enables redundancy mode.

redundancy
Related Commands
Command
Description
mode y-cable
Invoked y-cable mode.
standalone
Indicates whether the MWR 1941-DC router is being used as a

standalone device and manually sets the relays.
Designates a loopback interface as a health or revertive interface.
OL-11503-01
5-17
Chapter 5

To show RTP header compression statistics, use the show ip rtp header-compression EXEC command.
show ip rtp header-compression [type number] [detail]
Syntax Description
type number
(Optional) Interface type and number.
detail
(Optional) Displays details of each connection.

Note
Command Modes
EXEC
Command History
Release
This keyword is not supported on the Cisco MWR 1941-DC.
Modification
11.3
12.1(5)T
The command output was modified to include information related to the

Distributed Compressed Real-Time Transport Protocol (dCRTP) feature.
12.2(8)MC2
This command was incorporated in Cisco IOS Release 12.2(8)MC2.
12.2(15)MC1
12.3(11)T
Usage Guidelines
The detail keyword is not available with the show ip rtp header-compression command on a Route
Switch Processor (RSP). However, the detail keyword is available with the show ip rtp
header-compression command on a Versatile Interface Processor (VIP). Enter the show ip rtp
header-compression type number detail command on a VIP to retrieve detailed information regarding
RTP header compression on a specific interface.
Examples
The following is sample output from the show ip rtp header-compression command:
RTP/UDP/IP header compression statistics:
Interface Serial1:
Rcvd: 0 total, 0 compressed, 0 errors
0 dropped, 0 buffer copies, 0 buffer failures
Sent: 430 total 429 compressed
15122 bytes saved, 0 bytes sent
0 efficiency improvement factor
Connect: 16 rx slots, 16 tx slots, 0 long searches, 1 misses
99% hit ratio, five minute miss rate 0 misses/sec, 0 max.
Table 5-1 describes the significant fields shown in the display.
5-18
OL-11503-01
Chapter 5

Table 5-1
Related Commands
show ip rtp header-compression Field Descriptions
Field
Description
Interface Serial1
Type and number of interface.
Rcvd: total
Number of packets received on the interface.
compressed
Number of packets with compressed header.
errors
Number of errors.
dropped
Number of dropped packets.
buffer copies
Not applicable to the MWR 1941-DC router.
buffer failures
Sent: total
Total number of packets sent.
compressed
Number of packets sent with compressed header.
bytes saved
Total savings in bytes due to compression.
bytes sent
efficiency improvement factor
Efficiency achieved through compression.
Connect: rx slots
Total number of receive slots.
tx slots
Total number of transmit slots.
long searches
misses
Number of new states that were created.
hit ratio
Number of times existing states were revised.
five minute miss rate
Average miss rate.
max.
Maximum miss rate.
negative cache
Command
Description
ip rtp
compression-connections
Specifies the total number of RTP header compression connections

that can exist on an interface.
OL-11503-01
5-19
Chapter 5
show ppp mux
show ppp mux

To display counters for a multilink interface on the MWR 1941-DC, use the show ppp mux command
in EXEC mode.
show ppp mux [interface interface]
Syntax Description
interface interface
Defaults
If no interface is specified, statistics for all multilink and serial interfaces are displayed.
Command Modes
EXEC
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
(Optional) The identifier of the multilink or serial interface for which you
want to view counters.
Usage Guidelines
This command is only valid when issued against multilink or PPP interfaces.
Examples
The following is an example of the output generated by this command.

show ppp mux interface multilink 1
PPP Multiplex Statistics on Interface Multilink1:
Multiplex:
Total input packets:0
Errored input packets:0
Valid input bytes:0
Total output packets:0
Multiplexed output packets:0
Output bytes:0
Efficiency improvement factor:0%
Demultiplex:
Total input packets:0
Multiplexed input packets:0
Errored input packets:0
Valid input bytes:0
Total output packets:0
Output bytes:0
Efficiency improvement factor:0%
5-20
OL-11503-01
Chapter 5

show ppp mux
Table 5-2 describes the significant fields shown in the display.

Table 5-2
show ppp mux Field Descriptions
Field
Description
Total output packets
Number of outbound packets
Multiplexed output packets
Number of outbound multiplexed superframes
Output byte count
Number of outbound bytes
Total input packets
Number of inbound packets
Errored input packets
Number of inbound packets discarded due to error
Efficiency improvement factor
Percentage of efficiency improvement achieved

through multiplexing or demultiplexing
The efficiency improvement factor is calculated as follows:

Multiplex efficiency improvement factor = 100 * (Total bytes saved) / (Total bytes received)
Where total bytes saved = bytes_received_at_muxer - bytes_sent_at_muxer.
Demultiplex efficiency improvement factor = 100 * (Total bytes saved) / (Total bytes sent)
Where total bytes saved = bytes_sent_at_demuxer - bytes_received_at_demuxer.
Related Commands
Command
Description
ppp mux
OL-11503-01
5-21
Chapter 5
show redundancy
show redundancy
To display information about the current redundant configuration and recent changes in states, use the
show redundancy command in EXEC mode.
show redundancy
Syntax Description
This command has no attributes.
Command Modes
EXEC
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
Usage Guidelines
In the standby group name group-name command, if you omit the group-name or if you enter a group
name that doesnt begin with one or two, the configuration will fail and there will be a mismatch in the
information displayed by the show redundancy and show standby commands.
Examples
The following is an example of the output generated by this command.

show redundancy
MWR1900 is the Active Router
Previous States with most recent at bottom
INITL_INITL
LISTN_INITL
LISTN_LISTN
SPEAK_LISTN
SPEAK_SPEAK
STDBY_SPEAK
ACTIV_SPEAK
ACTIV_STDBY
ACTIV_ACTIV
INITL_ACTIV
INITL_INITL
INITL_LISTN
LISTN_LISTN
LISTN_SPEAK
SPEAK_SPEAK
SPEAK_STDBY
SPEAK_ACTIV
STDBY_ACTIV
ACTIV_ACTIV
INITL_ACTIV
INITL_INITL
INITL_LISTN
LISTN_LISTN
Dec
Feb
Feb
Feb
Feb
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
31
28
28
28
28
19
19
19
19
19
19
19
19
19
19
19
19
19
19
19
19
19
19
19:00:00.000
19:00:15.568
19:00:15.568
19:00:18.568
19:00:18.568
08:54:26.191
08:54:26.191
08:54:26.191
08:54:26.191
08:56:22.700
08:56:22.700
08:56:28.544
08:56:28.652
08:56:31.544
08:56:31.652
08:56:34.544
08:56:34.544
08:56:34.652
08:56:34.652
10:20:41.455
10:20:41.455
10:20:49.243
10:20:49.299
5-22
OL-11503-01
Chapter 5

show redundancy
LISTN_SPEAK
SPEAK_SPEAK
SPEAK_STDBY
STDBY_STDBY
ACTIV_STDBY
ACTIV_ACTIV
Related Commands
Mar
Mar
Mar
Mar
Mar
Mar
19
19
19
19
19
19
10:20:52.244
10:20:52.300
10:20:55.244
10:20:55.300
10:21:01.692
10:21:01.692
Command
Description
mode y-cable
Invokes y-cable mode.
redundancy
standalone
Specifies whether the MWR 1941-DC router is used in a redundant or

stand-alone configuration.
standby
Sets HSRP attributes
Specifies the interfaces to be used for health and revertive interfaces.
OL-11503-01
5-23
Chapter 5
standalone
standalone
To specify that the MWR 1941-DC is being used in a stand-alone configuration (which impacts the
relays on the VWIC), use the standalone command. To use the MWR 1941-DC in a redundant
configuration, use the no form of this command.
[no] standalone
Syntax Description
This command has no attributes.
Defaults
By default, the MWR 1941-DC is configured to be used in a redundant configuration (no standalone)
and the relays are open.
Command Modes
Y-cable configuration
Command History
Release
Modification
12.2(8)MC2
12.2(15)MC1
12.3(11)T
Usage Guidelines
Issuing the standalone command closes the relays on the VWICs installed in the MWR 1941-DC.
Examples
The following example closes the relays so that the MWR 1941-DC can be used as a stand-alone device.
standalone
Related Commands
Command
Description
mode y-cable
Specifies the interfaces to be used for health and revertive interfaces.
5-24
OL-11503-01
Chapter 5

To designate a loopback interface as a health or revertive interface, use the standby use-interface
command.
standby use-interface interface {health | revertive | backhaul}
Syntax Description
interface
Indicates the interface to be used with the specified parameter. For health
and revertive, this is the loopback interface specified in the standby track
command. For backhaul, the interface must be an MLPPP interface. If you
want to use a serial interface as the backhaul, you must first configure that
interface to be part of an MLPPP bundle.
health
Indicates the interface to monitor for an over temperature condition, the

state of the processor, and the state of the T1/E1 firmware. If any of these
watched conditions indicate a failure, this interface is brought down.
Otherwise, the health interface remains in the up state.
revertive
Indicates the interface that acts as the revertive interface. If the MWR 1941-DC
router changes state from active to standby, the revertive interface is brought up.
If the MWR 1941-DC router changes state from standby to active, the revertive
interface is brought down.
backhaul
Indicates the interface to be used for backhauling.
Defaults
By default, the MWR 1941-DC is configured to be used in a redundant configuration (no standalone)
and the relays are open.
Command Modes
Y-cable configuration
Command History
Release
Modification
12.2(8)MC2
Usage Guidelines
The loopback interfaces that you specify for health and revertive interfaces must be the same loopback
interfaces that you specified in the standby track command. In the standby track command, the
decrement value for the revertive interface should always be less than that for other interfaces. We
recommend that you use loopback101 for health and loopback102 for revertive.
The interface that you specify for the backhaul must be an MLPPP interface. If you want to use a serial
interface as the backhaul, you must first configure that interface to be part of an MLPPP bundle. We
recommend you use multilink1 for the backhaul interface.
OL-11503-01
5-25
Chapter 5
Examples
The following example specifies loopback101 as the health interface and loopback102 as the revertive
interface.
standby use-interface loopback101 health
standby use-interface loopback102 revertive
standby use-interface multilink1 backhaul
Related Commands
Command
Description
mode y-cable
redundancy
standalone
Specifies whether the MWR 1941-DC router is used in a redundant or

stand-alone configuration.
standby
Sets HSRP attributes
5-26
OL-11503-01
PA R T
Implementing the MWR 1941-DC Router in

a Cell Site DCN
C H A P T E R
Note
Cisco IOS Release 12.3(11)T does not support the Cisco IOS Cell Site DCN feature set (software
image) for the MWR 1941-DC router.
This chapter describes how to use the Cisco IOS software command-line interface (CLI) to configure the
following features of the MWR 1941-DC router in a Cell Site DCN:
Configuring the Host Name and Password, page 6-3
Configuring Fast Ethernet Interfaces, page 6-5
Configuring the Ethernet Switch Network Module, page 6-6
Configuring Asynchronous/Synchronous Serial Network Modules or WAN Interface Cards, page

6-9
Configuring 16-Port Asynchronous Network Module, page 6-12
Configuring T1 and E1 Interfaces, page 6-13
Configuring the 1 T3/E3 Module, page 6-17
Configuring the NM-AIC-64, Contact Closure Network Module, page 6-23
Configuring QoS Attributes, page 6-43
Filtering IP Packets Using Access Lists, page 6-46
Verifying the Configuration, page 6-64
Monitoring and Managing the MWR 1941-DC Router, page 6-68
Follow the procedures in this chapter to configure the router manually, or if you want to
change the configuration after you have run the setup command facility Using the Setup Command
Facility section on page 3-3.
This chapter describe only a small portion of commonly used configuration procedures. For detailed
configuration topics, refer to the Cisco IOS configuration guide and command reference publications.
These publications are available on the Documentation CD-ROM that came with your router, on the
World Wide Web from Ciscos home page, or you can order printed copies separately.
OL-11503-01
6-1
Chapter 6
Before You Begin
Note
If you skipped Chapter 3, First-Time Configuration, and you have never configured a Cisco router,
go back to that chapter and read it now. The chapter contains important information you need to
successfully configure your router.
Before You Begin

Before you configure the MWR 1941-DC in a Cell Site DCN, please note the following:
Step 1
Cisco IOS Release 12.2(15)MC1a or later mwr1900-is-mz image must be installed on the Cisco
MWR 1941-DC router.
When using the NM-16ESW with the MWR 1941-DC router, shielded cables are required and IP
phone inline power is not supported.
When using the 1-port T3/E3 network module (NM-1T3/E3) in your MWR 1941-DC router
configuration, note that E3 mode is not supported with Cisco IOS Release 12.2(15)MC1a.
Network Time Protocol (NTP). NTP 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.
RedundancyStandalone Mode. The MWR 1941-DC router must be configured to operate in

standalone mode. The standalone option must be configured from redundancy mode. To manually
set the relays to open or closed, do the following starting in global configuration mode:

Step 2

Step 3
Specify that the router is to be used as a stand-alone device. This command closes the relays.
Router(config-r-y)# standalone
Step 4

Timesaver
Before you begin configuring interfaces, disconnect all WAN cables from the router to keep it from
trying to run the AutoInstall process. The router tries to run AutoInstall whenever you power it ON,
if there is a WAN connection on both ends and the router does not have a valid configuration file
stored in nonvolatile random-access memory (NVRAM) (for instance, when you add a new
interface). It can take several minutes for the router to determine that AutoInstall is not connected to
a remote Transmission Control Protocol/Internet Protocol (TCP/IP) host.
6-2
OL-11503-01
Chapter 6

Caution
The MWR 1941-DC router does not support online insertion and removal (OIR) of WAN interface
cards. Any attempt to perform OIR on a card in a powered up router might cause damage to the card.
Caution
The Cisco MWR 1941-DC router does not support online insertion and removal (OIR) of network
modules. Any attempt to perform OIR on a card in a powered up router might cause damage to the
card.

To implement the MWR 1941-DC router in an Cell Site DCN, the router requires Cisco IOS Release
12.2(15)MC1a or a later be installed. To verify the version of Cisco IOS software, use the show version
command.
The show version command displays the configuration of the system hardware, the software version, the
names and sources of configuration files, and the boot images.

One of the first configuration tasks you might want to do is configure the host name and set an encrypted
password. Configuring a host name allows you to distinguish multiple Cisco routers from each other.
Setting an encrypted password allows you to prevent unauthorized configuration changes.
Command
Purpose
Enter enable mode. Enter the password.
Password: password

changes to Router#.
Router#
Step 2 Router# configure terminal

End with CNTL/Z.
Enter global configuration mode. You have

entered global configuration mode when the
prompt changes to Router(config)#.
Router(config)#
Step 3 Router(config)# hostname Router

Router(config)#
Change the name of the router to a meaningful

name. Substitute your host name for Router.
OL-11503-01
6-3
Chapter 6
Command
Purpose
Step 4 Router(config)# enable secret guessme
Enter an enable secret password. This password

provides access to privileged EXEC mode. When
a user types enable at the EXEC prompt
(Router>), they must enter the enable secret
password to gain access to configuration mode.
Substitute your enable secret for guessme.
Step 5 Router(config)# line con 0
Enter line configuration mode to configure the

console port. When you enter line configuration
mode, the prompt changes to
Router(config-line)#.
Router(config-line)# exec-timeout 0 0
Prevent the routers EXEC facility from timing out

if you do not type any information on the console
screen for an extended period.
Router(config-line)# exit
Router(config)#
6-4
OL-11503-01
Chapter 6

Verifying the Host Name and Password

To verify that you configured the correct host name and password:
Step 1
Enter the show config command:

Router(config)# show config
Using 1888 out of 126968 bytes
!
version XX.X
.
.
.
!
hostname Router
!
enable secret 5 $1$60L4$X2JYOwoDc0.kqa1loO/w8/
.
.
.
Step 2
Check the host name and encrypted password displayed near the top of the command output.
Step 3
Exit global configuration mode and attempt to re-enter it using the new enable password:
Router# exit
.
.
.
Router con0 is now available
Press RETURN to get started.
Router> enable
Password: guessme
Router#
Tips
If you are having trouble, check the following:
Caps Lock is off.
You entered the correct passwords. Passwords are case sensitive.

To configure the FE interface, complete the following tasks, beginning in global configuration mode:
Command
Purpose
Step 1 Router(config)# interface fastethernet 0/0

Router(config-if)#
Step 2 Router(config-if)# ip address 172.16.74.3

255.255.255.0
Enter interface configuration mode. You have

entered interface configuration mode when the
prompt changes to Router(config-if)#.
Assign an IP address and subnet mask to the
interface.
OL-11503-01
6-5
Chapter 6
Command
Step 3 Router(config-if)# ip helper address
99.1.1.2
Purpose
Configure the router to forward User Datagram
Protocol (UDP) broadcasts, including BOOTP,
received on an interface to a specific address.
Step 4 Router(config-if)# speed [auto | 100 | 10]
Configure the speed.
Step 5 Router(config-if)# duplex [auto | half |

full]
Configure the duplex operation
Step 6 Router(config-if)# exit

Repeat Step 4 through Step 6 if your router has
more than one interface that you need to
configure.
Step 7 Router(config-if)# Ctrl-z

Router#
When you finish configuring interfaces, return to

enable mode.
The following is a sample output from the show running-config command for a FE interface:
ip address 172.18.28.202 255.255.255.128
ip helper-address 99.1.1.2
no ip mroute-cache
speed 100
full-duplex

The 16-port Ethernet Switch network module (NM-16ESW) is a high-density module that provides
Layer 2 switching across Ethernet ports. In a Cell Site DCN implementation, you can use the
NM-16ESW in the Cisco MWR 1941-DC router for a cell site LAN for IP connectivity for peripheral
equipment.
For information on configuring the NM-16ESW, see 16- and 36-Port Ethernet Switch Module for Cisco
2600 Series, Cisco 3600 Series, and Cisco 3700 Series Cisco IOS Release 12.2(T) feature module:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft1636nm.ht
m
The following is a sample output from the show running-config command for a NM-16ESW:
ip address 172.18.28.206 255.255.255.128
no ip proxy-arp
speed 100
full-duplex
!
no ip address
no ip proxy-arp
6-6
OL-11503-01
Chapter 6

load-interval 30
shutdown
speed 100
full-duplex
no keepalive
no cdp enable
!
ip address 100.50.0.206 255.255.255.0
no ip proxy-arp
encapsulation ppp
load-interval 30
keepalive 1
no fair-queue
no cdp enable
!
interface Serial0/2
no ip address
shutdown
clockrate 125000
!
interface Serial0/3
no ip address
shutdown
clockrate 125000
!
no ip address
duplex full
speed 100
!
no ip address
duplex full
speed 100
!
no ip address
duplex full
speed 100
!
no ip address
duplex full
speed 100
!
switchport access vlan 162
no ip address
duplex full
speed 10
!
no ip address
duplex full
speed 100
!
no ip address
duplex full
speed 100
!
OL-11503-01
6-7
Chapter 6
no ip address
load-interval 30
duplex full
speed 100
no keepalive
no cdp enable
spanning-tree portfast
!
no ip address
load-interval 30
shutdown
duplex full
speed 10
no cdp enable
!
no ip address
duplex full
speed 100
!
switchport mode trunk
no ip address
duplex full
speed 10
!
no ip address
duplex full
speed 100
!
no ip address
duplex full
speed 100
!
no ip address
duplex full
speed 10
keepalive 1
!
no ip address
duplex full
speed 100
!
no ip address
load-interval 30
duplex full
speed 10
no cdp enable
!
interface Vlan1
no ip address
shutdown
!
6-8
OL-11503-01
Chapter 6

interface Vlan10
no ip address
!
interface Vlan11
ip address 41.42.43.206 255.255.255.0
no ip proxy-arp
load-interval 30
!
interface Vlan12
no ip address
no ip proxy-arp
no ip mroute-cache
load-interval 30
shutdown
!
interface Vlan20
no ip address
!
Configuring Asynchronous/Synchronous Serial Network

Modules or WAN Interface Cards
The interfaces on the Asynchronous/Synchronous serial network modules or WAN interface card can be
configured for synchronous or asynchronous serial protocols. HDLC (synchronous) and PPP
(asynchronous or synchronous) are typical serial protocols.
Note
For complete information on configuring serial interfaces, see the Configuring Serial Interfaces
chapter of the Cisco IOS Interface Configuration Guide, Release 12.2:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/finter_c/index.htm
To configure a serial interface, complete the following tasks, beginning in global configuration mode:
Command
Purpose
Step 1 Router(config)# interface serial 0/0

Router(config-if)#

255.255.255.0
Step 3 outer(config-if)# encapsulation

encapsulation_type
Enter the interface configuration mode. You have

Assign the IP address and subnet mask to the
interface.
Set the encapsulation method, (for example,
HDLC, PPP, Frame-Relay) used by the interface.
Step 4 Router(config-if)# physical-layer async
All serial ports are initially configured as

synchronous. Enter this command if you want to
configure the port as asynchronous.
Step 5 Router(config-if)# async mode dedicated
Configure asynchronous parameters according to

your needs.
Router(config-if)# async default routing
Step 6 Router(config-if)# line async <#>
Configure the asynchronous line setting.
OL-11503-01
6-9
Chapter 6
Command
Purpose
Step 7 Router(config-if)# clockrate 7200
To use a port in DCE mode, connect a DCE cable

and set the internal transmit clock signal (TXC)
speed in bits per second. See Table 6-1 and
Table 6-2 for a list of clock rate settings for your
specific interface. (For ports used in DTE mode,
the router automatically uses the external timing
signal.)
Step 8 Router(config-if)# nrzi-encoding
All serial interfaces support both nonreturn to zero

(NRZ) and nonreturn to zero inverted (NRZI)
formats. NRZ is the default; NRZI is commonly
used with EIA/TIA-232 connections in IBM
environments. To enable NRZI encoding on an
interface, enter this command.

Repeat Step 4 through Step 14 if your router has
more that one serial interface that you need to
configure.
Step 10 Router(config)# Ctrl-z

Router#
Table 6-1
When you finish configuring interface, return to

enable mode.
Clock Rate Settings for 2-Port Asynchronous/Synchronous Serial WAN Interface Card
Timer (bits per

second)
Syntax (bits per

second)
Default Setting (bits

per second)
1200
28800
72000
2400
32000
115200
4800
38400
125000
9600
56000
128000
14400
57600
19200
64000
Table 6-2
Clock Rate Settings for 4-Port/8-Port Asynchronous/Synchronous Serial Network Module
Timer (bits per

second)
Syntax (bits per

second)
Default Setting (bits

per second)
300
19200
64000
1200
28800
72000
2400
32000
115200
4800
38400
128000
9600
56000
14400
57600
6-10
OL-11503-01
Chapter 6

The following is a sample output from the show running-config command:
HDLC, DCE Side
!
interface Serial1/3
ip address 45.45.45.62 255.255.255.0
clockrate 64000
no cdp enable
!
HDLC, DTE Side

!
interface Serial1/0
ip address 44.44.44.62 255.255.255.0
no cdp enable
!
Sync PPP, DCE Side

!
interface Serial1/3
ip address 45.45.45.62 255.255.255.0
encapsulation ppp
clockrate 64000
no cdp enable
!
Sync PPP, DTE Side

!
interface Serial1/0
ip address 44.44.44.62 255.255.255.0
encapsulation ppp
no cdp enable
!
Async PPP (same configuration for either side, must set line speed via line interface)
!
interface Serial1/0
physical-layer async
ip address 44.44.44.62 255.255.255.0
encapsulation ppp
async mode dedicated
!
line 33
speed 57600
OL-11503-01
6-11
Chapter 6

The serial interfaces of the NM-16A provide low-speed EIA/TIA-232 data links from cell site equipment
to the backhaul network. Alternatively, these interfaces can provide terminal server capability allowing
cell site equipment to be managed remotely.
Note
For information on configuring terminal server capability; see the Configuring a Terminal/Comm
Server technical note:
http://www.cisco.com/en/US/tech/tk801/tk36/technologies_configuration_example09186a008014f8
e7.shtml
To configure an asynchronous interface on the NM-16A, complete the following tasks, beginning in
global configuration mode:
Command
Step 1 Router(config)# interface async 45

Router(config-if)#

255.255.255.0
Step 3 Router(config-if)# async mode dedicated

Router(config-if)# async default routing
Purpose
Enter the interface configuration mode and specify
the asynchronous interface to configure. You have
Assign the IP address and subnet mask to the
interface.
Configure asynchronous parameters according to
your needs.
Router(config-if)# line async 45

Router(config-if)# speed 115200
Return to the global configuration mode and

repeat Step 4 through Step 7 if your router has
more than one interface that you need to
configure.
Return to enable mode.
Router#
The following is a sample output from the show running-config command:
!
interface Async40
ip address 10.10.15.62 255.255.255.0
encapsulation ppp
async dynamic routing
async mode dedicated
no keepalive
!
line 40
speed 115200
6-12
OL-11503-01
Chapter 6


To configure a T1/E1 trunk interface, enter the following Cisco IOS commands at the router prompt.
To configure a new T1 interface (or change an existing one), complete the following tasks beginning in
Command
Purpose
Step 1 Router(config)# controller t1 1/0
Select the CT1/PRI interface to configure. This

example configures a T1 interface in slot 1 and
unit 0.
Step 2 Router(config-controller)# clock source
Specify which end of the circuit provides

clocking. The clock source should be set to use
internal clocking only for testing the network or if
the full T1 line is used as the channel group. Only
one end of the T1 line should be set to internal.
line
Step 3 Router(config-controller)# framing esf
Step 4 Router(config-controller)# linecode b8zs
Step 5 Router(config-controller)# channel-group 0

timeslots 1,3-5,7
Specify the channel group and time slots to be

mapped.
For the VWIC interfaces, you can configure two
channel-groups (0 and 1) on the first T1 port or
you can configure one channel-group (0 or 1) on
each T1 port.
Once you configure a channel group, the serial
interface is automatically create.
Step 6 Router(config-controller)# cablelength feet
Step 7 Router(config-controller)# exit
Exit controller configuration mode.
Step 8 Router(config-controller)# Router(config)#
Configure each channel group as a virtual serial

interface. Specify the T1 slot, unit number, and
channel group to modify.
interface serial slot/port:0

255.255.255.0

interface.
Step 10 Router(config-if)# carrier-delay number

Return to Step 1 if your router has more than one
T1 interface that you need to configure.

Router#

enable mode.
OL-11503-01
6-13
Chapter 6
To configure a new T1 interface (or change an existing one), complete the following tasks beginning in
Command
Purpose
Step 1 Router(config)# controller e1 1/0
Select the CE1/PRI interface to configure. This

example configures an E1 interface in slot 1 and
unit 0.
Step 2 Router(config-controller)# framing crc4
Step 3 Router(config-controller)# linecode hdb3
Step 4 Router(config-controller)# channel-group 0
Specify the channel group and time slots to be

mapped. For multiflex trunk interfaces, only
channel 0 can be configured.
timeslots 1,3-5,7
Step 5 Router(config-controller)# interface serial

1/0:0

255.255.255.0
Configure each channel group as a virtual serial

interface. Specify the E1 interface, unit number,
and channel group to modify.
interface.
Return to Step 4 if your router has more than one
CE1/PRI interface that you need to configure.

enable mode.
Configuring Drop and Insert

The Drop and Insert feature can be configured using the Cisco VWIC-2MFT-T1-DIR and
VWIC-2MFT-E1-DIR VWICs.
Drop-and-Insert capabilities allow individual 64Kb DS0 channels to be transparently passed,
uncompressed, between two ports on the same VWIC without passing through a digital signal processor
(DSP).
Note
T1/E1 channels can be used either for Drop and Insert or VoIP, but not both.
6-14
OL-11503-01
Chapter 6

To set up the Drop and Insert feature, complete the following tasks beginning in controller configuration
mode:
Command
Purpose
Step 1 Router(config-controller)# tdm-group

tdm-group-no
timeslots timeslot-list type [e&m | fxs
[loop-start |
ground-start] fxo [loop-start |
ground-start]
Enter this command to set up TDM channel groups

for the Drop-and-Insert function.
tdm-group-no is a value from 0 to 23 for T1 and
from 0 to 30 for E1; it identifies the group.
timeslot-list is a single number, numbers separated
by commas, or a pair of numbers separated by a
hyphen to indicate a range of timeslots. The valid
range is from 1 to 24 for T1. For E1, the range is
from 1 to 31.
The signaling method selection for type depends
on the connection that you are making. The fxs
and fxo options allow you to specify a ground-start
or loop-start line. The Cisco IOS Release 12.0
Voice, Video, and Home Applications Command
Reference includes additional information about
these options.
Note
Step 2 Router(config-controller)# channel-group

channel-group-no timeslots timeslot-list
[speed [56|64]]
The group numbers for controller groups

must be unique. For example, a TDM
group should not have the same ID number
as a DS0 group or channel group.
(Optional) Enter this command to set up channel

groups for WAN data services.
For the VWIC interfaces, you can configure
channel-group 0 and 1 on one port or one
channel-group (either 0 or 1) on each port.
channel-group-no is a value from 0 or 1 on the first
port, or you can configure one channel group (0 or
1) on each port.
timeslot-list is a single number, numbers separated
by commas, or a pair of numbers separated by a
hyphen to indicate a range of timeslots. The valid
range is from 1 to 24 for T1. For E1, the range is
from 1 to 31.
The optional speed setting defaults to 56 Kbps for
T1 and 64 Kbps for E1.
Step 3 Router(config-controller)# no shutdown
Activate the controller.
OL-11503-01
6-15
Chapter 6
Command
Step 4
Router(config)# connect id {T1 | E1}

slot/port-1
tdm-group-no-1 {T1 | E1} slot/port-2
tdm-group-no-2
Purpose
This global configuration command sets up the
connection between two T1 or E1 TDM groups of
timeslots on the VWICfor Drop and Insert.
id is a name for the connection.
Identify each controller by its slot/port location.
tdm-group-no-1 and tdm-group-no-2 identify the
TDM group numbers (from 0 to 23 or 30) on the
specified controller. The groups were set up in
Step 1.
Step 5 Router(config-controller)# exit
Exit controller configuration mode. Skip the next

step if you are not setting up Drop and Insert.
Step 6 Router(config)# connect id {T1 | E1}
This global configuration command sets up the

connection between two T1 or E1 TDM groups of
timeslots on the VWICfor Drop and Insert.
slot/port-1 tdm-group-no-1 {T1 | E1}

slot/port-2 tdm-group-no-2
id is a name for the connection.

Identify each controller by its slot/port location.
tdm-group-no-1 and tdm-group-no-2 identify the
TDM group numbers (from 0 to 23 or 30) on the
specified controller. The groups were set up in
Step 1.
T1 Controller
The following is a sample configuration of an individual T1 controller from the show running-config
command output:
controller T1 0/0
framing esf
linecode b8zs
cablelength short 133
Drop and Insert
The following is a sample drop and insert configuration from the show running-config command
output:
controller E1 0/0
channel-group 0 timeslots 1-5
tdm-group 2 timeslots 6-24
!
controller E1 0/1
connect E1_TDM E1 0/0 2 E1 0/1 1
6-16
OL-11503-01
Chapter 6


The NM-1T3/E3 is a single port universal T3/E3 network module with integrated CSU/DSU, clear
channel, and subrate support. Channels on the network module can be configured as either T3 or E3
through Cisco IOS software and enables you to switch between T3 and E3 applications with a single IOS
command.
Note
Note for complete information on configuring the Clear Channel 1 T3/E3 module, see the Clear
Channel T3/E3 with Integrated CSU/DSU Cisco IOS Release 12.2(15)T feature module.
Caution
Online insertion and removal (OIR) of the NM-1T3/E3 is not supported on the Cisco MWR 1941-DC
platform.
Note
When used with the MWR 1941-DC router, the NM-1T3/E3 supports line rate throughput for traffic
with packet sizes of 1500 bytes. For traffic with smaller packet sizes, degradation in throughput will
be seen.
Configuring the T3 Interface

To configure the T3 interface, complete the following required tasks:

When the Clear Channel T3/E3 network module is used for the first time, the running configuration does
not show the T3/E3 controller and its associated serial interface. You can use the show version command
to learn if the router recognized the T3/E3 card and was able to initialize the card properly. After the
card type is configured for the slot, the respective controller and serial interface appear in the running
configuration. See the Verifying the Version of Cisco IOS Software section on page 6-3.
After the network module has ascertained that the card has been initialized properly, use the card type
command to configure the card. If the command is accepted successfully, Cisco IOS software creates a
controller and a serial interface for the card.
Note
The autoconfig/setup utility does not support configuring the card type for the T3/E3
network module.
OL-11503-01
6-17
Chapter 6
To select and configure a card type and controller as T3, complete the following tasks beginning in global
configuration mode:
Step 1
Command or Action
Purpose
card type t3 slot
Selects the card type.
Example:
Router(config)# card type t3 1
Step 2
controller t3 slot/port
Example:
Creates a T3 controller and a serial interface.
t3Selects the T3 controller.
slotSlot number of the interface.
By default, the T3 controller does not show up in the

show running-config output.
Specifies the T3 controller and enters controller configuration mode.
Router(config)# controller t3 1
Step 3
framing {c-bit | m23}
Example:
Router(config-controller)# framing c-bit
Step 4
cablelength feet
Example:
Router(config-controller)# cablelength 250
Step 5
clock source {internal | line}
Specifies the framing type.
c-bitSpecifies C-bit framing as the T3 framing type.
m23Specifies M23 framing as the T3 framing type.
Specifies the distance from the routers to the network equipment.
feetNumber of feet in the range from 0 to 450.
The default value is 224 feet.
Selects the clock source.
internalSpecifies that the internal clock source is

used. This is the default for T3.
lineSpecifies that the network clock source is used.

This is the default for E3.
Example:
Router(config-controller)# clock source line
Step 6
exit
slot/portBackplane slot number and port number on

the controller.
Exits controller configuration mode and returns the router

to privileged EXEC mode.
Example:
6-18
OL-11503-01
Chapter 6


To specify the interoperability mode and maximum allowable bandwidth used by a T3 controller,
complete the following tasks beginning in global configuration mode:
Step 1
Command
Purpose
interface serial slot/port
Specifies the serial interface created on the controller.
Example:
Router(config)# interface serial 1/0
Step 2
Specifies the interoperability mode used by a T3 controller.
dsu mode {0 | 1 | 2 | 3 | 4}
0Connects a T3 controller to another T3 controller or to a

Digital Link DSU (DL3100). Bandwidth range is from
300 to 44210 kbps. This is the default.
1Connects a T3 controller to a Kentrox DSU. Bandwidth

range is from 1500 to 35000/44210 kbps.
Note
If the bandwidth is set to greater than 35000 kbps, it

defaults to 44210 kbps.
2Connects a T3 controller to a Larscom DSU. Bandwidth

range is from 3100 to 44210 kbps.
3Connects a T3 controller to an Adtran T3SU 300.

Bandwidth range is from 75 to 44210 kbps.
4Connects a T3 controller to a Verilink HDM 2182.

Bandwidth range is from 1500 to 44210 kbps.
Example:
Router(config-if)# dsu mode 0
Step 3
Specifies the maximum allowable bandwidth in the range from

1 to 44210 kbps.
dsu bandwidth kbps
Example:
Router(config-if)# dsu bandwidth 44210
Step 4
The real (actual) vendor-supported bandwidth is in the range

from 75 to 44210 kbps.
Exits interface configuration mode and returns the router to privileged EXEC mode.
exit
Example:
Configuring the E3 Interface

To configure the E3 interface, complete the following required tasks:
OL-11503-01
6-19
Chapter 6

Note
The autoconfig/setup utility does not support configuring the card type for the T3/E3 network
module.
To configure the card type and controller for an E3 interface, complete the following tasks beginning in
Step 1
Command or Action
Purpose
card type e3 slot
Selects the card type.
Example:
Router(config)# card type e3 1
Step 2
controller e3 slot/port
Example:
Creates an E3 controller and a serial interface.
e3Specifies the E3 transmission scheme

predominantly used in Europe.
Provides 34010 kbps.
slotSlot number of the interface.
By default, the E3 controller does not show up in the

show running config output.
Specifies the E3 controller and enters controller

configuration mode.
Router(config)# controller e3 1
Step 3
framing {bypass | g751}
Example:
Router(config-controller)# framing bypass
Step 4
clock source {internal | line}
Specifies the framing type.
bypassSpecifies that the G.751 framing be bypassed.
g751Specifies G.751 as the E3 framing type.
Default is g751.
Selects the clock source.
internalSpecifies that the internal clock source is

used. This is the default for T3.
lineSpecifies that the network clock source is used.

This is the default for E3.
Example:
Router(config-controller)# clock source line
Step 5
exit
slot/portBackplane slot number and port number on

the controller.
Exits controller configuration mode and returns the router

to privileged EXEC mode.
Example:
6-20
OL-11503-01
Chapter 6


To specify the interoperability mode used by an E3 controller, complete the following tasks beginning
in global configuration mode:
Step 1
Command
Purpose
Enters interface configuration mode and specifies the serial

interface created on the controller.
Example:
Step 2
Specifies the interoperability mode used by an E3 controller.
dsu mode {0 | 1}
0Sets the interoperability mode to 0. This is the default.

Specify mode 0 to connect an E3 controller to another E3
controller or to a Digital Link DSU (DL3100). Bandwidth
range is from 358 to 24500/34010 kbps.
Note
If the bandwidth is set to greater than 24500 kbps, it

defaults to 34010 kbps.
1Sets the interoperability mode to 1. Specify mode 1 to

connect an E3 controller to a Kentrox DSU. Bandwidth range
is from 500 to 34010 kbps.
Example:
Router(config-if)# dsu mode 0
Step 3
Specifies the maximum allowable bandwidth in the range from

22 to 34010 kbps.
dsu bandwidth kbps
Example:
Router(config-if)# dsu bandwidth 44210
Step 4
exit
The real (actual) vendor-supported bandwidth is in the range

from 358 to 34010 kbps.
Exits interface configuration mode and returns the router to

privileged EXEC mode.
Example:
OL-11503-01
6-21
Chapter 6

To enable encryption of the payload on the E3 controller, complete the following tasks beginning in
global configuration mode.
Step 1
Command
Purpose
Enters interface configuration mode.
Example:
Step 2
Enables the scrambling of the payload.
scramble
Default is off.
Example:
Router(config-if)# scramble
Step 3
Exits interface configuration mode and returns the router to

privileged EXEC mode.
exit
Example:
T3 Controller
The following is sample output from the show running-config command for a T3 controller:
card type t3 1
controller T3 1/0
cablelength 10
interface Serial1/0
no ip address
no ip route-cache
no ip mroute-cache
no keepalive
dsu bandwidth 44210
E3 Controller
The following is sample output from the show running-config command for an E3 controller:
card type e3 1
controller E3 1/0
interface Serial1/0
ip address 10.0.0.6 255.255.255.0
encapsulation ppp
no keepalive
dsu bandwidth 34010
no cdp enable
6-22
OL-11503-01
Chapter 6


The Alarm Interface Card Network Module (AICNM) is an optional card that expands network
management capabilities for customer-defined alarms. The AIC has its own CPU that communicates
with the router and external media through serial communication channels. The AIC reduces service
provider and enterprise operating costs by providing a flexible, low-cost network solution for migrating
existing DCNs to IP-based DCNs. The AIC provides its users with a single box solution because it can
be configured in the same router along with other operation, alarm, maintenance, and provisioning
(OAMP) interfaces.
The AIC provides a total of 64 alarm inputs. Eight of the 64 point are software configurable for
measuring either analog inputs or discrete inputs. The remaining 56 points are fixed to measure discrete
points only. The AIC also provides 16 control relay outputs.
The discrete alarm input can be activated through ground or negative battery input. The negative battery
range is -36V to -72V. The analog alarm is software configurable for either DC voltage or current. It can
measure voltage from -60 to 60V or current from 0 to 20mA, but the configurable range is 4 mA to
20mA. The standard 16 control relays can be configured to turn on or turn off an external device.
The AICs 64 input contact points can control and monitor network elements and other non-intelligent
interfaces, permitting the detection and report of alarms such as the following:
Network element alarm states
Building security (door and window open and close)
Fire and smoke indication
Building environmentals (temperature and humidity)
Utility power readings
When an event occurs, such as a door alarm or an open gate, the AIC maps the simple discrete and analog
alarms to preprogrammed intelligent messages and transports the messages to destinations in the
IP network, typically to a Network Operations Center (NOC). These messages are generated either in
Transaction Language 1 (TL1) or in Simple Network Management Protocol (SNMP), which are used by
a NOCs Operations Support System (OSS).
When the AIC is incorporated into the Cisco DCN solution platforms, all the AICs contact-closure
alarms are routed and reported through the same network and systems as the intelligent network elements
(NEs). This facilitates continued use of the existing OSS and its associated networks. A Cisco router with
an AIC sends TL1 or SNMP messages to the OSS autonomously or in response to TL1 or SNMP
commands from the OSS, as shown in Figure 6-1. TL1 supports two sessions, with the port numbers
5011 and 5012, respectively, and SNMP supports four sessions.
OL-11503-01
6-23
Chapter 6
Figure 6-1
TL1 and SNMP Message Flow in a DCN Application
DCN
SNMP
Data Center
TL1 or SNMP
37874
OSS in NOC
Serial Communication Channels

As illustrated in Figure 6-2, the AIC has two serial communications channels that provide different types
of interfaces to Cisco IOS software:
Serial data channel
Asynchronous craft port
Figure 6-2
OS Boundary into the AIC
Cisco router
Packet sent by NOC
NOC
SNMP
Remote CLI
Dest IP address
5.5.5.1
IP
AIC IP 5.5.5.1
TL1
SNMP
TFTP
TELNET
.... on
Ether port
Serial
Data Channel
IOS
Local CLI
Asynchronous
Craft Port
37875
IOS boundary
Serial Data Channel

The serial data channel supports all TCP/IP traffic to and from the AIC. This includes communication
over IP with NOCs and data centers. The channel consists of one physical interface that provides support
for the following applications:
Telnet
TL1
6-24
OL-11503-01
Chapter 6

TFTP
SNMP
The Cisco IOS software assigns an IP address to the AIC for use by the serial data channel. To route
traffic, the serial data channel uses IP over synchronous High-Level Data Link Control (HDLC). All IP
packets coming to the Cisco router with a destination IP address that matches the AICs IP address are
forwarded to the serial data channel using IP over HDLC.
Asynchronous Craft Port

The asynchronous craft port supports Telnet to the AICs port number. This Telnet method, called
local-CLI, is useful for debugging when remote Telnet to the AICs IP address (remote-CLI) is not
applicable. For more information, see the Configuring the NOC IP Address section on page 6-30.
The asynchronous craft port also supports an AIC boot sequence, similar to the ROM monitor in
Cisco IOS software, which allows the user to recover from a corrupted software image or configuration.
See the Override section on page 6-36.
Configuring the AIC

From a top-level view, AIC configuration involves assigning an IP address to the AIC using Cisco IOS
commands and setting up alarm configurations with either TL1 or the AIC command-line interface
(CLI). The flexible TL1 and AIC CLI permit a broad range of alarm configuration scenarios. The
following are examples of alarm configurations that can be programmed with the AIC CLI:
Configuring a Discrete Alarm

enable
config terminal
alarm 1
description "west door"
normally closed
description normal "door closed"
description alarm "door open"
level 2
exit
Configuring an Analog Alarm as an Analog Monitoring Voltage

enable
config terminal
alarm 57
description "tank level"
description normal "full"
description low "low"
description low-low "empty"
analog voltage 2.5 30 60 60
exit
OL-11503-01
6-25
Chapter 6
Configuring an Analog Alarm as a Discrete Monitoring Current

enable
config terminal
alarm 58
description "east door"
discrete current-loop 0.0 3.2 5.9
exit
Configuring an Analog Alarm as a Discrete Monitoring Voltage

enable
config terminal
alarm 58
description "backup battery"
discrete voltage 9.0 high
exit
Configuring an Analog Alarm to Act Like a Discrete Alarm (Minimal Configuration Method)
enable
config terminal
alarm 59
discrete
exit
Configuration Tasks
See the following sections for configuration tasks for the AIC feature. Each task in the list is identified
as either required or optional:
Configuring the AIC, page 6-26 (required)

Entering Alarm Configuration Mode and Configuring the AIC IP Address, page 6-27
Configuring the IP Route to the AIC, page 6-27
Configuring the NOC IP Address, page 6-30 (optional)
Configuring Alarms, page 6-30 (optional)
Configuring the AIC

Cisco IOS commands are used for configuring the AIC IP address and the IP routing to the AIC NM.
After the IP address and the IP routing are set, alarm configurations can then be set up with either TL1
or the AIC command-line interface. See theConfiguring the NOC IP Address section on page 6-30 or
the Configuring Alarms section on page 6-30 for more information.
The following sections describe how to configure the AIC IP address and the IP Routing to the AIC NM.
6-26
OL-11503-01
Chapter 6

Entering Alarm Configuration Mode and Configuring the AIC IP Address

Enter alarm configuration mode and configure the AIC IP address, beginning in privileged EXEC mode:
Step 1
Command
Purpose
Router# show run
Determines if the AIC is installed correctly in the

router. If the AIC has been installed correctly, then
the following appears:
where the slot is the slot in which the AIC is

inserted, and the port is 0.
Step 2
Starts the configuration session.
Step 3
Router(config)# alarm-interface slot
Enters the AIC interface mode, specifying the slot

number into which the AIC is installed.
Step 4
Router(config-aic)# ip address ip-address mask
Enters the IP address of the AIC. Entering a mask is

optional, because the IP address does not use a
subnet address.
Step 5
Router(config-aic)# reset
Resets the AIC. Changing the IP configuration may

not take until the next time the card is started. The
reset command restarts the card.
Step 6
Router(config-aic)# exit
Exits the AIC interface mode.
Configuring the IP Route to the AIC

There are many ways to configure IP routing to the AIC. Below are two methods. The first method uses
an unnumbered IP address. It is used when an administrator wants to assign an IP address that is already
known to the router, such as an address that is one of the addresses in the subnet of a FastEthernet IP
address.
The second method, does not use an unnumbered IP address and is used when there is a subnet available
to the serial interface and to the AIC. Usually this subnet is small with a subnet mask such as
255.255.255.252.
OL-11503-01
6-27
Chapter 6
Configure IP routing to the AIC with an unnumbered IP address, beginning in global

configuration mode:
Step 1
Command
Purpose
Router(config)# ip route network-number network-mask

{IP address | interface} [distance] [name name]
Establish the discrete IP route and mask on the

routers serial interface. The arguments have the
following meanings:
network-numberIP address of the target network
or subnet.
network-maskNetwork mask that lets you mask
network and subnetwork bits.
IP addressInternet address of the next hop that
can be used to reach that network in standard
IP address notation. Example: 10.1.1.1.
interfaceNetwork interface to use.
distance(Optional) An administrative distance,
which is a rating of the trustworthiness of a routing
information source, such as an individual router or a
group of routers.
name name(Optional) Name of the user profile.
Example:
Router(config)#ip route 10.5.5.2
255.255.255.255 serial2/0
Step 2
Router(config)# interface serialslot/port
Enter serial interface mode. Enter the slot in which

the AIC is installed and port 0.
Step 3
Router(config-if)# ip unnumbered type

interface-number
Enable IP processing on the serial interface to the

AIC without assigning an explicit IP address to the
interface. The type and interface-number arguments
indicate another interface on which the router has an
assigned IP address. The other interface cannot be
an unnumbered interface, because only an interface
that has its own IP address can be used to lend its
IP to the serial port. Enter, for example:
Router(config-if)# ip unnumbered FastEthernet
0/0
Step 4
Exit serial interface mode.
6-28
OL-11503-01
Chapter 6

Configure IP routing to the AIC without an unnumbered IP address, beginning in global

configuration mode:
Command
Purpose
Step 1
Router(config)# interface serial slot/port
Enter the serial interface mode. Enter the slot in

which the AIC is installed and the port 0.
Step 2
Router(config-if)# ip address ip-address

network-mask
Specify the IP address and mask of the routers serial

interface to the AIC. For example:
Router(config)# ip route 10.5.5.1
255.255.255.0
Step 3
Exits the serial interface mode.
Accessing the AIC

Remote-CLI and local-CLI are the two methods for accessing the AIC:
Remote-CLI involves telneting to the IP address of the AIC. For example:

telnet 10.5.5.2
Local-CLI involves accessing the asynchronous craft port by telneting to the IP address of the router
and the AICs TCP port number. For example:
telnet 10.2.130.105 2001
where 10.2.130.105 is the routers IP address and 2001 is on slot 0 of the AIC.
The AICs TCP port number depends on the slot number in which the AIC is installed. As shown in
Table 6-3, the Cisco IOS software reserves the first line of each slot for the asynchronous craft port.
Table 6-3
TCP Port Number Allocation for the AIC on the Cisco 2600 and Cisco 3600 Series
Slot Number
Terminal Line Number for the AICs Asynchronous Craft Port
TCP Port Number
2001
33
2033
65
2065
97
2097
129
2129
161
2161
193
2193
OL-11503-01
6-29
Chapter 6
Configuring the NOC IP Address

Note
The aic command-line prompt indicates that either TL1 or AIC CLI commands must be used
Configure up to four NOC IP addresses to which the AIC will send SNMP messages, beginning in global
configuration mode:
Command
Purpose
Step 1
aic(config)# snmp
Enter SNMP configuration mode.
Step 2
aic(config)# noc ip-address {number} ip-address
Enter an NOC IP address in which the AIC will

send SNMP messages. The number argument can
be the numbers 1 through 4.
Step 3
aic(config)# exit
Exit the AIC CLI.
Configuring Alarms
After the AIC and NOC IP addresses have been configured, you can the configure alarms by
programming the AICs discrete and analog contact points. These tasks can be performed on-site or by
Telneting as described in the Accessing the AIC section on page 6-29.
Alarms are configured using either TL1 or AIC CLI. Information about TL1 commands can be found in
the Telcordia Technology (formerly Bellcore) document Network Maintenance: Network Element and
Transport Surveillance Messages, GR-833-CORE, Issue 5, November 1996. For a reference of
security-related commands (ACT-USER and CANC-USER) refer to Telcordia Technologys Operations
Applications Messages-Network Element and Network System Security Admin Messages,
TR-NWT-000835, Issue 2, January 1993. The following TL1 messages and commands are supported by
the AIC:
TL1 Messages
REPT-ALM-ENV
REPT-ALM-EQPT
REPT-EVT
TL1 Commands
ACT-USER
CANC-USER
OPR-EXT-CONT
RLS-EXT-CONT
RTRV-ALM
RTRV-ALM-ENV
RTRV-ATTR
RTRV-ATTR-CONT
RTRV-ATTR-ENV
6-30
OL-11503-01
Chapter 6

RTRV-ATTR-LOG
RTRV-HDR
RTRV-LOG
RTRV-EXT-CONT
SET-ATTR-ENV
SET-ATTR-EQPT
SET-ATTR-LOG
STA-LOG
STP-LOG
Programming the Analog Contact Points

Alarm points 57 through 64 are analog inputs, which are configurable as discrete inputs. When
configured as an analog input, the user must select whether the point is monitoring voltage or current.
The user must also define five ranges by selecting four values for a point monitoring voltage or six ranges
for a point monitoring current. For current-monitoring points, the lowest and highest values define the
range of possible values. (Valid values are from 9999999.9 to 9999999.9.) For voltage-monitoring
alarms, the range of possible values is always 60V to 60V. The other four values must be within the
defined range, and they partition the range into low-low, low, high, and high-high ranges. Except for the
normal range, each range is associated with an alarm condition.
Analog points have four unique alarm states. Each alarm state has its own alarm description string. Only
one alarm state per point may be active at any given time. In other words, when a threshold is crossed,
the previous alarm state is cleared and the new alarm state is active.
When an analog input is configured as discrete, the user must select whether the point is monitoring
voltage or current. Similar to the analog configuration, the user must also select the range of acceptable
values for a current-monitoring alarm. (Valid values are from 9999999.9 to 9999999.9.) The voltage
range is always 60V to 60V. The user must define the threshold that will cause the alarm condition and
whether the normal state of the alarm is the higher or lower range.
Note
For the current analog point, the lower boundary is 4 mA and the upper boundary is 20 mA. For
example,
analog current-loop 10 13 16 17 20 26
has 16 units between 10 and 26. If the AIC measures 4 mA, then it will factor that the point is
registering at the lower boundary. The AIC will interpret 13 as 7 mA, 16 as 10 mA, 17 as 11 mA, 20
as 14 mA, and 26 as the upper boundary, which is 20 mA.
OL-11503-01
6-31
Chapter 6
Following are examples:

Point 57 is monitoring the ambient temperature of a building and the sensor range is 20 to 75 degrees
Celsius. Below 0 degrees is a critical alarm, 0 to 10 degrees is a major alarm, 10 to 35 degrees is the
normal range, 35 to 45 degrees is a minor alarm, and above 45 degrees is a major alarm. The
configuration for this point follows:
alarm 57
analog current-loop 20 0 10 35 45 75
level low-low 1
level low 2
level high 3
level high-high 2
Point 58 is monitoring a fuel tank level with a resistive sensor. Below 46 volts is a critical alarm,
46 to 40 volts is a minor alarm, and above 40 volts is the normal range. This is a unidirectional alarm,
so the high thresholds are set equal to the high bound (since this threshold cannot be crossed). The
configuration for this point follows:
alarm 58
analog voltage 46 40 60 60
level low-low 1
level low 3
Point 59 is monitoring a battery bank. Below 42 volts is a critical alarm and above 42 volts is the
normal range. The configuration for this point follows:
alarm 59
discrete voltage 42 high
level 1
Programming the Discrete Contact Points

The discrete alarms do not require as much programming as the analog alarms. The AIC CLI commands
available are the following:
Command
Description
no
Reversal option
exit
Exits current mode
description
Sets the description. If no is set, then the description

is not required.
normally
Sets the alarms normal state to closed. If the no

option is used, the normal state is set to open. This
command applies only to points 1 - 56.
level
Sets the alarms level to the specified level.
6-32
OL-11503-01
Chapter 6

Verifying the IP Address

To verify that the correct AIC IP address and IP route was entered, use the show run command. Below
are samples of before-configuration and after-configuration show run command outputs:
interface Serial5/0
ip unnumbered FastEthernet0/0
!
ip route 10.2.130.102 255.255.255.255 Serial5/0
!
alarm-interface 5
ip address 10.2.130.102
********Before Configuration show run Output*******

version 12.1
no service single-slot-reload-enable
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname uut2-RouterA
!
logging rate-limit console 10 except errors
!
ip subnet-zero
!
!
no ip finger
no ip domain-lookup
!
call rsvp-sync
cns event-service server
!
!
ip address 10.2.130.2 255.255.0.0
duplex auto
speed auto
no cdp enable
!
interface Serial5/0
no ip address
!
ip kerberos source-interface any
ip classless
ip route 0.0.0.0 0.0.0.0 10.2.0.1
ip http server
!
no cdp run
!
!
dial-peer cor custom
!
!
line con 0
exec-timeout 0 0
transport input none
OL-11503-01
6-33
Chapter 6
line 161
no exec
transport preferred none
transport input telnet
transport output none
stopbits 1
line aux 0
line vty 0 4
password lab
login
!
end
*****After Configuration show run Output*******

version 12.1
!
hostname uut2-3660
!
no logging console
!
ip subnet-zero
!
no ip finger
no ip domain-lookup
!
call rsvp-sync
!
ip address 10.2.130.2 255.255.0.0
duplex auto
speed auto
no cdp enable
!
interface Serial5/0
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.2.0.1
ip route 10.2.130.102 255.255.255.255 Serial5/0
ip http server
!
no cdp run
!
!
alarm-interface 5
ip address 10.2.130.102
!
!
!
!
line con 0
exec-timeout 0 0
6-34
OL-11503-01
Chapter 6

line 161
no exec
stopbits 1
line aux 0
line vty 0 4
password lab
login
!
end
Troubleshooting Tips
If no alarm messages are sent for an unusually long period of time, ping the AIC address to check for
connectivity.
Monitoring and Maintaining the NM-AIC-64 Contact Closure Network Module

The AIC provides a TFTP client for software upgrade and configuration image transfer. The methods for
both actions, as well as how to override the existing software or configuration, are described below.
Software Upgrade
When upgrading software, the AIC must be reset to run the new software. The AIC provides a protected
(login required) command for software download. When the user invokes this command with the TFTP
server address as a parameter, the AIC connects to the IP address and, via TFTP, retrieves the software
image file. After verifying that the software has been transferred successfully, the AIC replaces its
running software with the newly downloaded software.
In the case of incompatible versions of Cisco IOS and AIC software, the Cisco IOS software recognizes
the difference and displays this information to the user. The user makes the decision whether to upgrade
or downgrade either the Cisco IOS or AIC software or to take no corrective action.
Configuration Backup
The AIC CLI provides commands for storing and restoring configurations. Users can transfer the current
configuration of the AIC to or from the TFTP server whose address is given as a parameter to the
get config command. When a configuration file is transferred from the server to the AIC, the AIC takes
on the new configuration.
The configuration is stored as a list of commands (script) that can be applied to the CLI of an AIC for
configuration.
Two other useful commands are the get image and put config commands. Use the get image command
to get a new image, and the put config command to back up the configuration to the TFTP server.
Backup is not automatic, but the AIC reminds the user, on logout, to back up the configuration.
OL-11503-01
6-35
Chapter 6
Override
In the case that bad software is resident on the AIC or that the configured administrator password is lost,
the AIC provides a method for recovering the card. Upon booting, the AIC begins a countdown, visible
at the AIC local CLI (Craft Port). If an ASCII character is received on that local CLI channel (DSCC4
channel 2) during this countdown, the AIC enters a mode in which a limited CLI is available. At this
limited CLI, available over the Craft Port only, no login is necessary. The user may enter commands for
software upgrade and configuration transfer. The new configuration takes effect upon a reset of the AIC
card.
After interrupting the countdown, the user will see an AIC Boot]: prompt. From this prompt, the user
can enter ? to see the available commands, g to get a new application image, or d to delete the
current configuration and return to the defaults. (All commands require a carriage return.) In the case of
the get command, the user will be prompted for the name of the file, the IP address of the TFTP server,
and a confirmation.
AIC IP Address Configuration Example
The following example shows a Cisco router configured for AIC IP address:
version 12.2
service tcp-keepalives-in
service tcp-keepalives-out
!
hostname RouterA-top
!
!
ip subnet-zero
!
!
no ip finger
no ip domain-lookup
ip host moe 172.31.10.2
ip host mickey 10.1.1.2
!
no ip dhcp-client network-discovery
frame-relay switching
x25 routing
!
!
call-history-mib max-size 50
!
interface Ethernet0/0
ip address 10.5.37.13 255.255.0.0
no keepalive
half-duplex
!
6-36
OL-11503-01
Chapter 6

interface Serial0/0
ip address 10.5.5.1 255.255.255.0
encapsulation frame-relay
no ip mroute-cache
clockrate 500000
frame-relay class voice-vc
frame-relay traffic-shaping
frame-relay map ip 10.5.5.2 990 broadcast
frame-relay interface-dlci 990
frame-relay intf-type dce
!
no ip address
half-duplex
no cdp enable
!
interface Serial0/1
ip address 10.11.11.1 255.255.255.0
encapsulation frame-relay
no ip mroute-cache
clockrate 256000
frame-relay class voice-vc
frame-relay traffic-shaping
frame-relay interface-dlci 991
frame-relay intf-type dce
!
interface Serial1/0
ip address negotiated
!
router mobile
!
ip classless
ip route 223.255.254.254 255.255.255.255 10.5.0.1
ip route 223.255.254.254 255.255.255.255 Ethernet0/0
no ip http server
!
!
map-class frame-relay voice-vc
frame-relay cir 800000
frame-relay bc 512000
no frame-relay adaptive-shaping
frame-relay fair-queue
frame-relay voice bandwidth 500000
frame-relay fragment 100
frame-relay ip rtp priority 16384 16383 512
!
map-class frame-relay fr1
frame-relay bc 1000
frame-relay fair-queue
frame-relay fragment 100
!
map-class frame-relay voice-vc2
frame-relay bc 512000
!
map-class frame-relay voice-data
access-list 1 deny
192.200.1.20
access-list 2 deny
10.10.1.10
OL-11503-01
6-37
Chapter 6
dialer-list 1 protocol ip permit

dialer-list 1 protocol ipx permit
!
snmp-server packetsize 4096
snmp-server manager
!
alarm-interface 1
ip address 10.4.3.2
call rsvp-sync
!
mgcp modem passthrough voip mode ca
no mgcp timer receive-rtcp
!
mgcp profile default
!
!
dial-peer voice 1 pots
destination-pattern 3
direct-inward-dial
forward-digits all
!
dial-peer voice 100 voip
shutdown
session target ipv4:10.2.81.1
playout-delay maximum 300
!
shutdown
!
shutdown
!
shutdown
!
shutdown
destination-pattern 2...
!
shutdown
!
shutdown
destination-pattern 9..
!
shutdown
!
shutdown
!
6-38
OL-11503-01
Chapter 6


shutdown
!
dial-peer voice 200 vofr
shutdown
!
shutdown
!
shutdown
!
shutdown
!
preference 2
shutdown
!
no vad
!
dial-peer voice 1001 voatm
shutdown
!
dial-peer voice 1100 vofr
shutdown
session target Serial0/0 990
no vad
!
gateway
!
gateway
!
gatekeeper
shutdown
!
!
line con 0
exec-timeout 0 0
OL-11503-01
6-39
Chapter 6
line 33
no exec
stopbits 1
line aux 0
line vty 0 4
login
!
end
IP Route to the AIC Configuration Examples
Following examples show the configuration of an IP route to the AIC with an unnumbered and numbered
IP address.
With an Unnumbered IP Address
The following example shows a Cisco router, with an IP route to an AIC, is configured with an
unnumbered IP address:
version 12.1
!
hostname uut2-RouterB
!
no logging console
!
ip subnet-zero
!
!
no ip finger
no ip domain-lookup
!
call rsvp-sync
!
ip address 10.2.130.2 255.255.0.0
duplex auto
speed auto
no cdp enable
!
interface Serial5/0
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.2.0.1
ip route 10.2.130.102 255.255.255.255 Serial5/0
ip http server
!
no cdp run
!
alarm-interface 5
ip address 10.2.130.102
!
!
6-40
OL-11503-01
Chapter 6

!
!
line con 0
exec-timeout 0 0
line 161
no exec
stopbits 1
line aux 0
line vty 0 4
password lab
login
!
end
Without an Unnumbered IP Address
The following example shows a Cisco router configured without an unnumbered IP address:
uut5-2621#s run
Current configuration :1318 bytes
!
version 12.2
!
hostname uut5-RouterC
!
no logging console
!
ip subnet-zero
!
no ip finger
no ip domain-lookup
!
no ip dhcp-client network-discovery
!
ip address 10.2.130.5 255.255.0.0
duplex auto
speed auto
no cdp enable
!
interface Serial1/0
ip address 172.128.12.1 255.255.255.252
!
router rip
network 10.0.0.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.2.0.1
no ip http server
!
no cdp run
OL-11503-01
6-41
Chapter 6
!
snmp-server packetsize 4096
snmp-server manager
!
!
alarm-interface 1
ip address 172.128.12.2
call rsvp-sync
!
!
line con 0
exec-timeout 0 0
line 33
no exec
stopbits 1
line aux 0
line vty 0 4
password lab
login
!
no scheduler allocate
!
end
AIC CLI Configuration for Alarms
These examples are output from the show alarm config # command.
Discrete Alarm
description:west door
normally closed
normal state description:door closed
alarm state description:door open
SNMP trap:enabled
Analog Alarm Monitoring Current

description:thermostat
high-high state description:very hot
high state description:hot
normal state description:just right
low state description:cold
low-low state description:very cold
current-loop -5.2 5.4 15.0 25.0 35.1 45.6
SNMP trap:enabled
Analog Alarm Monitoring Current Configured as a Discrete

description:east door
configured as discrete
normal state description:door closed
alarm description:door open
current-loop 0.0 3.2 5.9
SNMP trap:enabled
6-42
OL-11503-01
Chapter 6


To use QoS on the MWR 1941-DC router in a Cell Site DCN, create a class map that defines the criteria
that a packet much match to be placed in that class and then tell the router the action to take on those
packets that match by creating a policy map. These two components make up the QoS boilerplate and
once you have created the QoS boilerplate, you can assign it to an interface.
Note
The QoS functionality of the MWR 1941-DC router is built on the same code as the Cisco 10000 ESR
(with some exceptions). For more information about the QoS feature, see Configuring Quality of
Service (http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10ksw/qosos.htm) and the
Cisco 10000 Series ESR Quality of Service feature module
(http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kfm/fm_qos.htm), as well as the
Cisco IOS Quality of Service Solutions Configuration Guide and the Cisco IOS Quality of Service
Solutions Command Reference.

For each class map that you want to create, do the following in global configuration mode:
Step 1
Assign a name to your class map.

Router(config)# class-map [match-all | match-any] class_name
Where match-any means a single match rule is sufficient for class membership and match-all means
only those packets that have all the attributes you specify are part of the class.
When you enter the class-map command, you are placed in class map configuration mode.
Step 2
Describe the characteristics of the packets that are subject to QoS using one or more of the following.
Router(config-cmap)# match access-group number
Router(config-cmap)# match ip dscp number
Router(config-cmap)# match ip precedence number
Router(config-cmap)# match input-interface interface-name
Router(config-cmap)# match protocol protocol
match access-group specifies access control list (ACL) that a packet must match.
match ip dscp specifies the IP differentiated service code point (DSCP) that a packet must match.
match ip precedence specifies the precedence values (0-7) that a packet must match.
match input-interface specifies the name of the input interface used as a match criterion.
match input-protocol specifies the protocol that a packet must match.
Reference.
Step 3
Exit class map configuration mode.

Router(config-cmap)# exit
OL-11503-01
6-43
Chapter 6

To create a policy map, do the following in global configuration mode:
Step 1
Assign a name to your policy map.

Router(config)# policy-map policy_name
When you enter the policy-map command, you are placed in policy map configuration mode.
Step 2
Associate the policy map with a class map.

Router(config-pmap)# class class_name
Specify the same class_name as you did in Step 1 of Creating a Class Map. When you enter the class
command, you are placed in class submode of the policy-map configuration mode.
Step 3
Describe the QoS actions you want the router to perform when the router encounters a packet that has
the characteristics described by the class map. Use one or more of the following commands:
Router(config-pmap-c)# priority percent number
Router(config-pmap-c)# bandwidth percent number
Router(config-pmap-c)# queue-limit number
Router(config-pmap-c)# priority rate-in-kbps
Router(config-pmap-c)# shape {average | peak} cir [bc] [be]
Router(config-pmap-c)# shape max-buffers number-of-buffers
priority percent gives priority to a class of traffic belonging to a policy map and specifies that a
certain percentage of the available bandwidth should be reserved for this class.
bandwidth percent specifies the bandwidth allocated for a class belonging to a policy map.
queue-limit specifies the maximum number of packets the queue can hold for a class policy
configured in a policy map.
priority enables low-latency priority queuing, which allows you to assign a specified share of the
link bandwidth to one queue that receives priority over all others. Low-latency priority queueing
minimizes the packet-delay variance for delay-sensitive traffic, such as live voice and video.
shape and shape max-buffers are used with class-based weighted fair queuing (CB-WFQ), which
allows you to control the traffic going out an interface in order to match its transmission to the speed
of the remote target interface.
Note
The bandwidth percent and priority percent commands cannot be used in the same
class, within the same policy map but can be used together in the same policy map.
For more information about these commands, see the Cisco IOS Quality of Service Solutions
Command Reference.
6-44
OL-11503-01
Chapter 6

Step 4
Repeat Step 2 and Step 3 for each class map.
Step 5
Exit policy map configuration mode.

Router(config-pmap-c)# exit
Router(config-pmap)# exit

To assign a QoS boilerplate to an interface, do the following in global configuration mode.
Step 1
Access interface configuration mode.

Router(config)# interface number
Step 2
Assign the QoS boilerplate to the interface.

Router(config-if)# service-policy output policy_name
The following is an example configuration of QoS configured on the MWR 1941-DC router in a Cell
Site DCN.
class-map match-all voice-class
match protocol rtp
class-map match-all nm-class
match protocol snmp
match protocol syslog
class-map match-all data-class
match protocol telnet
match protocol ftp
match protocol http
!
policy-map proto
class nm-class
queue-limit 300
class data-class
queue-limit 300
class voice-class
queue-limit 300
OL-11503-01
6-45
Chapter 6

Packet filtering helps control packet movement through the network. Such control can help limit network
traffic and restrict network use by certain users or devices. To permit or deny packets from crossing
specified interfaces, we provide access lists.
You can use access lists in the following ways:
To control the transmission of packets on an interface
To control vty access
To restrict contents of routing updates
This section summarizes how to create IP access lists and how to apply them.
An access list is a sequential collection of permit and deny conditions that apply to IP addresses. The
Cisco IOS software tests addresses against the conditions in an access list one by one. The first match
determines whether the software accepts or rejects the address. Because the software stops testing
conditions after the first match, the order of the conditions is critical. If no conditions match, the
software rejects the address.
The two main tasks involved in using access lists are as follows:
1.
Create an access list by specifying an access list number or name and access conditions.
2.
Apply the access list to interfaces or terminal lines.
These and other tasks are described in this section and are labeled as required or optional. Either the first
or second task is required, depending on whether you identify your access list with a number or a name.
Creating Standard and Extended Access Lists Using Numbers, page 6-46 (Required)
Creating Standard and Extended Access Lists Using Names, page 6-50 (Required)
Specifying IP Extended Access Lists with Fragment Control, page 6-53 (Optional)
Enabling Turbo Access Control Lists, page 6-56 (Optional)
Applying Time Ranges to Access Lists, page 6-57 (Optional)
Including Comments About Entries in Access Lists, page 6-58 (Optional)
Applying Access Lists, page 6-58 (Required)
Configuration Examples, page 6-60
Creating Standard and Extended Access Lists Using Numbers

Cisco IOS software supports the following types of access lists for IP:
Standard IP access lists that use source addresses for matching operations.
Extended IP access lists that use source and destination addresses for matching operations, and
optional protocol type information for finer granularity of control.
Dynamic extended IP access lists that grant access per user to a specific source or destination host
basis through a user authentication process. In essence, you can allow user access through a firewall
dynamically, without compromising security restrictions. Dynamic access lists and lock-and-key
access are described in the Configuring Traffic Filters chapter of the Cisco IOS Security
Configuration Guide.
6-46
OL-11503-01
Chapter 6

Note
Reflexive access lists that allow IP packets to be filtered based on session information. Reflexive
access lists contain temporary entries, and are nested within an extended, named IP access list. For
information on reflexive access lists, refer to the Configuring IP Session Filtering (Reflexive
Access Lists) chapter in the Cisco IOS Security Configuration Guide and the Reflexive Access
List Commands chapter in the Cisco IOS Security Command Reference.
Release 11.1 introduced substantial changes to IP access lists. These extensions are backward
compatible; migrating from a release earlier than Release 11.1 to the current release will convert your
access lists automatically. However, the current implementation of access lists is incompatible with
Cisco IOS Release 11.1 or earlier. If you create an access list using the current Cisco IOS release and
then load older Cisco IOS software, the resulting access list will not be interpreted correctly. This
condition could cause you severe security problems. Save your old configuration file before booting
Release 11.1 or earlier images.
To create a standard access list, use the following commands in global configuration mode:
Command
Purpose
Step 1
Router(config)# access-list access-list-number remark

remark
Indicates the purpose of the deny or permit

statement.1
Step 2
Router(config)# access-list access-list-number {deny |

permit} source [source-wildcard] [log]
Defines a standard IP access list using a source

address and wildcard.
or
Router(config)# access-list access-list-number {deny |
permit} any [log]
1.
Defines a standard IP access list using an

abbreviation for the source and source mask of
0.0.0.0 255.255.255.255.
This example configures the remark before the deny or permit statement. The remark can be configured after the deny or permit statement.
The Cisco IOS software can provide logging messages about packets permitted or denied by a standard
IP access list. That is, any packet that matches the access list will cause an informational logging
message about the packet to be sent to the console. The level of messages logged to the console is
controlled by the logging console global configuration command.
The first packet that triggers the access list causes an immediate logging message, and subsequent
packets are collected over 5-minute intervals before they are displayed or logged. The logging message
includes the access list number, whether the packet was permitted or denied, the source IP address of the
packet, and the number of packets from that source permitted or denied in the prior 5-minute interval.
However, you can use the ip access-list log-update command to set the number of packets that, when
match an access list (and are permitted or denied), cause the system to generate a log message. You might
want to do this to receive log messages more frequently than at 5-minute intervals.
Caution
If you set the number-of-matches argument to 1, a log message is sent right away, rather than caching
it; every packet that matches an access list causes a log message. A setting of 1 is not recommended
because the volume of log messages could overwhelm the system.
OL-11503-01
6-47
Chapter 6
Even if you use the ip access-list log-update command, the 5-minute timer remains in effect, so each
cache is emptied at the end of 5 minutes, regardless of the count of messages in each cache. Regardless
of when the log message is sent, the cache is flushed and the count reset to 0 for that message the same
way it is when a threshold is not specified.
Note
The logging facility might drop some logging message packets if there are too many to be handled
or if there is more than one logging message to be handled in 1 second. This behavior prevents the
router from crashing due to too many logging packets. Therefore, the logging facility should not be
used as a billing tool or an accurate source of the number of matches to an access list.
Note
If you enable CEF and then create an access list that uses the log keyword, the packets that match the
access list are not CEF switched. They are fast switched. Logging disables CEF.
For an example of a standard IP access list using logs, see the Numbered Access List Examples section
on page 6-60.
6-48
OL-11503-01
Chapter 6

To create an extended access list, use the following commands in global configuration mode:
Command
Purpose
Step 1
Router(config)# access-list access-list-number

remark remark
Indicates the purpose of the deny or permit

statement.1
Step 2
Router(config)# access-list access-list-number {deny

| permit} protocol source source-wildcard
destination destination-wildcard [precedence
precedence] [tos tos] [established] [log |
log-input] [time-range time-range-name] [fragments]
Defines an extended IP access list number and the

access conditions. Specifies a time range to restrict
when the permit or deny statement is in effect. Use
the log keyword to get access list logging messages,
including violations. Use the log-input keyword to
include input interface, source MAC address, or VC
in the logging output.
or
or
| permit} protocol any any [log | log-input]
[time-range time-range-name] [fragments]
or
or

| permit} protocol host source host destination [log
| log-input] [time-range time-range-name][fragments]
Defines an extended IP access list using an

abbreviation for a source and source wildcard of
source 0.0.0.0, and an abbreviation for a destination
and destination wildcard of destination 0.0.0.0.
or
or
Router(config)# access-list access-list-number

[dynamic dynamic-name [timeout minutes]] {deny |
permit} protocol source source-wildcard destination
destination-wildcard [precedence precedence] [tos
tos] [established] [log | log-input] [time-range
time-range-name] [fragments]
1.

0.0.0.0 255.255.255.255, and an abbreviation for a
destination and destination wildcard of 0.0.0.0
255.255.255.255.
Defines a dynamic access list. For information about

lock-and-key access, refer to the Configuring Traffic
Filters chapter in the Cisco IOS Security
Configuration Guide.
Note
The fragments keyword is described in the Specifying IP Extended Access Lists with Fragment
Control section on page 6-53.
After you create an access list, you place any subsequent additions (possibly entered from the terminal)
at the end of the list. In other words, you cannot selectively add or remove access list command lines
from a specific access list.
OL-11503-01
6-49
Chapter 6
Note
When creating an access list, remember that, by default, the end of the access list contains an implicit
deny statement for everything if it did not find a match before reaching the end.
Note
In a standard access list, if you omit the mask from an associated IP host address access list
specification, 0.0.0.0 is assumed to be the mask.
Note
Autonomous switching is not used when you have extended access lists.
After creating an access list, you must apply it to a line or interface, as shown in the Applying Access
Lists section on page 6-58. See the Implicit Masks in Access Lists Examples section on page 6-61
for examples of implicit masks.
Creating Standard and Extended Access Lists Using Names

You can identify IP access lists with an alphanumeric string (a name) rather than a number. Named
access lists allow you to configure more IP access lists in a router than if you were to use numbered
access lists. If you identify your access list with a name rather than a number, the mode and command
syntax are slightly different. Currently, only packet and route filters can use a named list.
Consider the following guidelines before configuring named access lists:
Note
Access lists specified by name are not compatible with Cisco IOS Releases prior to 11.2.
Not all access lists that accept a number will accept a name. Access lists for packet filters and route
filters on interfaces can use a name.
A standard access list and an extended access list cannot have the same name.
Numbered access lists are also available, as described in the Creating Standard and Extended
Access Lists Using Numbers section on page 6-46.
Named access lists will not be recognized by any software release prior to Cisco IOS Release 11.2.
6-50
OL-11503-01
Chapter 6

To create a standard access list, use the following commands beginning in global configuration mode:
Command
Purpose
Step 1
Router(config)# ip access-list standard name
Defines a standard IP access list using a name and

enters standard named access list configuration
mode.
Step 2
Router(config-std-nacl)# remark remark
Allows you to comment about the following deny or

permit statement in a named access list.1
Step 3
Router(config-std-nacl)# deny {source

[source-wildcard] | any}[log]
Specifies one or more conditions allowed or denied,

which determines whether the packet is passed or
dropped.
and/or
Router(config-std-nacl)# permit {source
[source-wildcard] | any}[log]
Step 4
Exits access-list configuration mode.
Router(config-std-nacl)# exit
1.
To create an extended access list, use the following commands beginning in global configuration mode:
Step 1
Command
Purpose
Router(config)# ip access-list extended name
Defines an extended IP access list using a name and

enters extended named access list configuration
mode.
OL-11503-01
6-51
Chapter 6
Command
Purpose
Step 2
Router(config-ext-nacl)# remark remark
Allows you to comment about the following deny or

permit statement in a named access list.1
Step 3
Router(config-ext-nacl)# deny | permit protocol

source source-wildcard destination
destination-wildcard [precedence precedence] [tos
tos] [established] [log | log-input]
In access-list configuration mode, specifies the

conditions allowed or denied. Specifies a time range
to restrict when the permit or deny statement is in
effect. Use the log keyword to get access list logging
messages, including violations. Use the log-input
keyword to include input interface, source MAC
address, or VC in the logging output.
and
or
Router(config-ext-nacl)# deny | permit protocol any

any [log | log-input] [time-range time-range-name]
[fragments]

0.0.0.0 255.255.255.255, and an abbreviation for a
destination and destination wildcard of 0.0.0.0
255.255.255.255.
or
or
Router(config-ext-nacl)# deny | permit protocol host
source host destination [log | log-input]
or
or
Router(config-ext-nacl)# dynamic dynamic-name

[timeout minutes] {deny | permit} protocol source
source-wildcard destination destination-wildcard
[precedence precedence] [tos tos] [established] [log
| log-input] [time-range time-range-name]
[fragments]
1.

source 0.0.0.0, and an abbreviation for a destination
and destination wildcard of destination 0.0.0.0.
Defines a dynamic access list.
Note
Autonomous switching is not used when you have extended access lists.
Note
The fragments keyword is described in the Specifying IP Extended Access Lists with Fragment
Control section on page 6-53.
After you initially create an access list, you place any subsequent additions (possibly entered from the
terminal) at the end of the list. In other words, you cannot selectively add access list command lines to
a specific access list. However, you can use no permit and no deny commands to remove entries from
a named access list.
6-52
OL-11503-01
Chapter 6

Note
When making the standard and extended access list, remember that, by default, the end of the access
list contains an implicit deny statement for everything if it did not find a match before reaching the
end. Further, with standard access lists, if you omit the mask from an associated IP host address
access list specification, 0.0.0.0 is assumed to be the mask.
After creating an access list, you must apply it to a line or interface, as shown in Applying Access Lists
section on page 6-58.
See the Named Access List Example section on page 6-62 for an example of a named access list.
Specifying IP Extended Access Lists with Fragment Control

This section describes the functionality added to IP extended named and numbered access lists. You can
now specify whether the system examines noninitial IP fragments of packets when applying an IP
extended access list.
Prior to this feature, nonfragmented packets and the initial fragment of a packet were processed by IP
extended access lists (if such an access list was applied), but noninitial fragments were permitted by
default. The IP Extended Access Lists with Fragment Control feature now allows more granularity of
control over noninitial packets.
Because noninitial fragments contain only Layer 3 information, access-list entries containing only
Layer 3 information can and now are applied to noninitial fragments. The fragment has all the
information the system needs to filter, so the entry is applied to the fragments.
This feature adds the optional fragments keyword to four IP access list commands [access-list (IP
extended), deny (IP), dynamic, and permit (IP)]. By specifying the fragments keyword in an access
list entry, that particular access list entry applies only to noninitial fragments of packets; the fragment is
either permitted or denied accordingly.
OL-11503-01
6-53
Chapter 6
The behavior of access-list entries regarding the presence or absence of the fragments keyword can be
summarized as follows:
If the Access-List Entry has...
Then..
...no fragments keyword, and

assuming all of the access-list entry
information matches,
For an access-list entry containing only Layer 3 information:
The entry is applied to nonfragmented packets, initial

fragments and noninitial fragments.
For an access list entry containing Layer 3 and Layer 4

information:
The entry is applied to nonfragmented packets and initial

fragments.
If the entry matches and is a permit statement, the
packet or fragment is permitted.

If the entry matches and is a deny statement, the
packet or fragment is denied.
The entry is also applied to noninitial fragments in the

following manner. Because noninitial fragments contain
only Layer 3 information, only the Layer 3 portion of an
access-list entry can be applied. If the Layer 3 portion of
the access-list entry matches, and
If the entry is a permit statement, the noninitial
fragment is permitted.
If the entry is a deny statement, the next access-list
entry is processed.
Note
...the fragments keyword, and

assuming all of the access-list entry
information matches,
Note that the deny statements are handled

differently for noninitial fragments versus
nonfragmented or initial fragments.
The access-list entry is applied only to noninitial fragments.
Note
The fragments keyword cannot be configured for

an access-list entry that contains any Layer 4
information.
Be aware that you should not simply add the fragments keyword to every access list entry because the
first fragment of the IP packet is considered a nonfragment and is treated independently of the
subsequent fragments. An initial fragment will not match an access list permit or deny entry that
contains the fragments keyword, the packet is compared to the next access list entry, and so on, until it
is either permitted or denied by an access list entry that does not contain the fragments keyword.
Therefore, you may need two access list entries for every deny entry. The first deny entry of the pair
will not include the fragments keyword, and applies to the initial fragment. The second deny entry of
the pair will include the fragments keyword and applies to the subsequent fragments. In the cases where
there are multiple deny access list entries for the same host but with different Layer 4 ports, a single
deny access-list entry with the fragments keyword for that host is all that needs to be added. Thus all
the fragments of a packet are handled in the same manner by the access list.
6-54
OL-11503-01
Chapter 6

The fragments keyword can be applied to dynamic access lists also.

Packet fragments of IP datagrams are considered individual packets and each counts individually as a
packet in access list accounting and access list violation counts.
Note
The fragments keyword cannot solve all cases involving access lists and IP fragments.
Turbo Access Lists
A turbo access list treats fragments and uses the fragments keyword in the same manner as a nonturbo
access list.
Policy Routing
Fragmentation and the fragment control feature affect policy routing if the policy routing is based on the
match ip address command and the access list had entries that match on Layer 4 through 7 information.
It is possible that noninitial fragments pass the access list and are policy routed, even if the first fragment
was not policy routed or the reverse.
By using the fragments keyword in access list entries as described earlier, a better match between the
action taken for initial and noninitial fragments can be made and it is more likely policy routing will
occur as intended.
Benefits of Fragment Control in an IP Extended Access List

If the fragments keyword is used in additional IP access list entries that deny fragments, the fragment
control feature provides the following benefits:
Additional Security
You are able to block more of the traffic you intended to block, not just the initial fragment of such
packets. The unwanted fragments no longer linger at the receiver until the reassembly timeout is reached
because they are blocked before being sent to the receiver. Blocking a greater portion of unwanted traffic
improves security and reduces the risk from potential hackers.
Reduced Cost
By blocking unwanted noninitial fragments of packets, you are not paying for traffic you intended to
block.
Reduced Storage
By blocking unwanted noninitial fragments of packets from ever reaching the receiver, that destination
does not have to store the fragments until the reassembly timeout period is reached.
Expected Behavior is Achieved
The noninitial fragments will be handled in the same way as the initial fragment, which is what you
would expect. There are fewer unexpected policy routing results and fewer fragment of packets being
routed when they should not be.
For an example of fragment control in an IP extended access list, see the IP Extended Access List with
Fragment Control Example section on page 6-62.
OL-11503-01
6-55
Chapter 6
Enabling Turbo Access Control Lists

The Turbo Access Control Lists (Turbo ACL) feature processes access lists more expediently than
conventional access lists. This feature enables a Cisco router to evaluate ACLs for more expedient packet
classification and access checks.
ACLs are normally searched sequentially to find a matching rule, and ACLs are ordered specifically to
take this factor into account. Because of the increasing needs and requirements for security filtering and
packet classification, ACLs can expand to the point that searching the ACL adds a substantial amount of
time and memory when packets are being forwarded. Moreover, the time taken by the router to search
the list is not always consistent, adding a variable latency to the packet forwarding. A high CPU load is
necessary for searching an access list with several entries.
The Turbo ACL feature compiles the ACLs into a set of lookup tables, while maintaining the first match
requirements. Packet headers are used to access these tables in a small, fixed number of lookups,
independently of the existing number of ACL entries. The benefits of this feature include the following:
Note
For ACLs larger than three entries, the CPU load required to match the packet to the predetermined
packet-matching rule is lessened. The CPU load is fixed, regardless of the size of the access list,
allowing for larger ACLs without incurring any CPU overhead penalties. The larger the access list,
the greater the benefit.
The time taken to match the packet is fixed, so that latency of the packets is smaller (substantially
in the case of large access lists) and, more importantly, consistent, allowing better network stability
and more accurate transit times.
Access lists containing specialized processing characteristics such as evaluate and time-range entries
are excluded from Turbo ACL acceleration.
The Turbo ACL builds a set of lookup tables from the ACLs in the configuration; these tables increase
the internal memory usage, and in the case of large and complex ACLs, tables containing 2 MB to 4 MB
of memory are usually required. Routers enabled with the Turbo ACL feature should allow for this
amount of memory usage. The show access-list compiled EXEC command displays the memory
overhead of the Turbo ACL tables for each access list.
To configure the Turbo ACL feature, perform the tasks described in the following sections. The task in
the first section is required; the task in the remaining section is optional:
Configuring Turbo ACLs (Required)
Verifying Turbo ACLs (Optional)
Configuring Turbo ACLs

To enable the Turbo ACL feature, use the following command in global configuration mode:
Command
Purpose
Router(config)# access-list compiled
Enables the Turbo ACL feature.
6-56
OL-11503-01
Chapter 6

Verifying Turbo ACLs

Use the show access-list compiled EXEC command to verify that the Turbo ACL feature has been
successfully configured on your router. This command also displays the memory overhead of the Turbo
ACL tables for each access list. The command output contains the following states:
OperationalThe access list has been compiled by Turbo ACL, and matching to this access list is
performed through the Turbo ACL tables at high speed.
UnsuitableThe access list is not suitable for compiling, perhaps because it has time-range enabled
entries, evaluate references, or dynamic entries.
DeletedNo entries are in this access list.
BuildingThe access list is being compiled. Depending on the size and complexity of the list, and
the load on the router, the building process may take a few seconds.
Out of memoryAn access list cannot be compiled because the router has exhausted its memory.
The following is sample output from the show access-lists compiled EXEC command:
Router# show access-lists compiled
Compiled ACL statistics:
12 ACLs loaded, 12 compiled tables
ACL
State
Tables Entries Config
1
Operational
1
2
1
2
Operational
1
3
2
3
Operational
1
4
3
4
Operational
1
3
2
5
Operational
1
5
4
9
Operational
1
3
2
20
Operational
1
9
8
21
Operational
1
5
4
101
Operational
1
15
9
102
Operational
1
13
6
120
Operational
1
2
1
199
Operational
1
4
3
First level lookup tables:
Block
Use
Rows
Columns
0
TOS/Protocol
6/16
12/16
1
IP Source (MS)
10/16
12/16
2
IP Source (LS)
27/32
12/16
3
IP Dest (MS)
3/16
12/16
4
IP Dest (LS)
9/16
12/16
5
TCP/UDP Src Port
1/16
12/16
6
TCP/UDP Dest Port
3/16
12/16
7
TCP Flags/Fragment
3/16
12/16
Fragment
0
0
0
0
0
0
0
0
7
6
0
0
Redundant
0
0
0
0
0
0
0
0
2
0
0
0
Memory
1Kb
1Kb
1Kb
1Kb
1Kb
1Kb
1Kb
1Kb
1Kb
1Kb
1Kb
1Kb
Memory used
66048
66048
132096
66048
66048
66048
66048
66048
Applying Time Ranges to Access Lists

You can implement access lists based on the time of day and week using the time-range global
configuration command. To do so, first define the name and times of the day and week of the time range,
then reference the time range by name in an access list to apply restrictions to the access list.
Currently, IP and Internetwork Packet Exchange (IPX) named or numbered extended access lists are the
only functions that can use time ranges. The time range allows the network administrator to define when
the permit or deny statements in the access list are in effect. Prior to this feature, access list statements
were always in effect once they were applied. The time-range keyword is referenced in the named and
numbered extended access list task tables in the Creating Standard and Extended Access Lists Using
Numbers section on page 6-46 and Creating Standard and Extended Access Lists Using Names
OL-11503-01
6-57
Chapter 6
section on page 6-50. The time-range command is described in the Performing Basic System
Management chapter of the Cisco IOS Configuration Fundamentals Configuration Guide. See the
Time Range Applied to an IP Access List Example section on page 6-62 for a configuration example
of IP time ranges.
Possible benefits of using time ranges include the following:
The network administrator has more control over permitting or denying a user access to resources.
These resources could be an application (identified by an IP address/mask pair and a port number),
policy routing, or an on-demand link (identified as interesting traffic to the dialer).
Network administrators can set time-based security policy, including the following:
Perimeter security using the Cisco IOS Firewall feature set or access lists
Data confidentiality with Cisco Encryption Technology or IP Security Protocol (IPSec)
Policy-based routing (PBR) and queueing functions are enhanced.
When provider access rates vary by time of day, it is possible to automatically reroute traffic cost
effectively.
Service providers can dynamically change a committed access rate (CAR) configuration to support
the quality of service (QoS) service level agreements (SLAs) that are negotiated for certain times of
day.
Network administrators can control logging messages. Access list entries can log traffic at certain
times of the day, but not constantly. Therefore, administrators can simply deny access without
needing to analyze many logs generated during peak hours.
Including Comments About Entries in Access Lists

You can include comments (remarks) about entries in any named IP access list using the remark
access-list configuration command. The remarks make the access list easier for the network
administrator to understand and scan. Each remark line is limited to 100 characters.
The remark can go before or after a permit or deny statement. You should be consistent about where
you put the remark so it is clear which remark describes which permit or deny statement. For example,
it would be confusing to have some remarks before the associated permit or deny statements and some
remarks after the associated statements. The standard and extended access list task tables in the
Creating Standard and Extended Access Lists Using Numbers section on page 6-46 and Creating
Standard and Extended Access Lists Using Names section on page 6-50 include the remark command.
See the Commented IP Access List Entry Examples section on page 6-63 for examples of commented
IP access list entries.
Remember to apply the access list to an interface or terminal line after the access list is created. See the
following section Applying Access Lists for more information.
Applying Access Lists

After creating an access list, you must reference the access list to make it work. To use an access list,
perform the tasks described in the following sections. The tasks in the first section are required; the tasks
in the remaining sections are optional:
Controlling Access to a Line or Interface (Required)
Controlling Policy Routing and the Filtering of Routing Information (Optional)
Controlling Dialer Functions (Optional)
6-58
OL-11503-01
Chapter 6

Controlling Access to a Line or Interface

After you create an access list, you can apply it to one or more interfaces. Access lists can be applied on
either outbound or inbound interfaces. This section describes guidelines on how to accomplish this task
for both terminal lines and network interfaces. Remember the following:
When controlling access to a line, you must use a number.
When controlling access to an interface, you can use a name or number.
To restrict access to a vty and the addresses in an access list, use the following command in line
configuration mode. Only numbered access lists can be applied to lines. Set identical restrictions on all
the virtual terminal lines, because a user can attempt to connect to any of them.
Command
Purpose
Router(config-line)# access-class access-list-number {in

| out}
Restricts incoming and outgoing connections between a

particular vty (into a device) and the addresses in an
access list.
To restrict access to an interface, use the following command in interface configuration mode:
Command
Purpose
Router(config-if)# ip access-group {access-list-number |

access-list-name} {in | out}
Controls access to an interface.
For inbound access lists, after receiving a packet, the Cisco IOS software checks the source address of
the packet against the access list. If the access list permits the address, the software continues to process
the packet. If the access list rejects the address, the software discards the packet and returns an ICMP
host unreachable message.
For outbound access lists, after receiving and routing a packet to a controlled interface, the software
checks the source address of the packet against the access list. If the access list permits the address, the
software sends the packet. If the access list rejects the address, the software discards the packet and
returns an ICMP host unreachable message.
When you apply an access list that has not yet been defined to an interface, the software will act as if the
access list has not been applied to the interface and will accept all packets. Remember this behavior if
you use undefined access lists as a means of security in your network.
Controlling Policy Routing and the Filtering of Routing Information

To use access lists to control policy routing and the filtering of routing information, see the Configuring
IP Routing Protocol-Independent Features chapter in the Cisco IOS IP Configuration Guide.
Controlling Dialer Functions

To use access lists to control dialer functions, refer to the Preparing to Configure DDR chapter in the
Cisco IOS Dial Technologies Configuration Guide.
OL-11503-01
6-59
Chapter 6
The following are access list configuration examples.
Numbered Access List Examples

In the following example, network 36.0.0.0 is a Class A network whose second octet specifies a subnet;
that is, its subnet mask is 255.255.0.0. The third and fourth octets of a network 36.0.0.0 address specify
a particular host. Using access list 2, the Cisco IOS software would accept one address on subnet 48 and
reject all others on that subnet. The last line of the list shows that the software would accept addresses
on all other network 36.0.0.0 subnets.
access-list 2 permit 36.48.0.3
access-list 2 deny 36.48.0.0 0.0.255.255
access-list 2 permit 36.0.0.0 0.255.255.255
interface ethernet 0
ip access-group 2 in
The following example defines access lists 1 and 2, both of which have logging enabled:
ip address 1.1.1.1 255.0.0.0
ip access-group 2 out
!
access-list 1 permit 5.6.0.0 0.0.255.255 log
access-list 1 deny 7.9.0.0 0.0.255.255 log
!
access-list 2 permit 1.2.3.4 log
access-list 2 deny 1.2.0.0 0.0.255.255 log
If the interface receives 10 packets from 5.6.7.7 and 14 packets from 1.2.23.21, the first log will look
like the following:
list 1 permit 5.6.7.7 1 packet
list 2 deny 1.2.23.21 1 packet
Five minutes later, the console will receive the following log:
list 1 permit 5.6.7.7 9 packets
list 2 deny 1.2.23.21 13 packets
Turbo Access Control List Example
The following is a Turbo ACL configuration example. The access-list compiled global configuration
command output indicates that Turbo ACL is enabled.
no ip address
ip access-group 20 out
no ip directed-broadcast
shutdown
!
no ip classless
ip route 192.168.0.0 255.255.255.0 10.1.1.1
!
access-list compiled
access-list 1 deny
any
access-list 2 deny
192.168.0.0 0.0.0.255
access-list 2 permit any
6-60
OL-11503-01
Chapter 6

Implicit Masks in Access Lists Examples
IP access lists contain implicit masks. For instance, if you omit the mask from an associated IP host
address access list specification, 0.0.0.0 is assumed to be the mask. Consider the following example
configuration:
access-list 1 deny 0.0.0.0 255.255.255.255
For this example, the following masks are implied in the first two lines:
The last line in the configuration (using the deny keyword) can be left off, because IP access lists
implicitly deny all other access. Leaving off the last line in the configuration is equivalent to finishing
the access list with the following command statement:
access-list 1 deny 0.0.0.0 255.255.255.255
The following access list only allows access for those hosts on the three specified networks. It assumes
that subnetting is not used; the masks apply to the host portions of the network addresses. Any hosts with
a source address that does not match the access list statements will be rejected.
! (Note: all other access implicitly denied)
To specify a large number of individual addresses more easily, you can omit the address mask that is all
0s from the access-list global configuration command. Thus, the following two configuration commands
are identical in effect:
0.0.0.0
Extended Access List Examples
In the following example, the first line permits any incoming TCP connections with destination ports
greater than 1023. The second line permits incoming TCP connections to the Simple Mail Transfer
Protocol (SMTP) port of host 128.88.1.2. The last line permits incoming ICMP messages for error
feedback.
access-list 102 permit tcp 0.0.0.0 255.255.255.255 128.88.0.0 0.0.255.255 gt 1023
access-list 102 permit tcp 0.0.0.0 255.255.255.255 128.88.1.2 0.0.0.0 eq 25
access-list 102 permit icmp 0.0.0.0 255.255.255.255 128.88.0.0 255.255.255.255
For another example of using an extended access list, suppose you have a network connected to the
Internet, and you want any host on an Ethernet to be able to form TCP connections to any host on the
Internet. However, you do not want IP hosts to be able to form TCP connections to hosts on the Ethernet
except to the mail (SMTP) port of a dedicated mail host.
SMTP uses TCP port 25 on one end of the connection and a random port number on the other end. The
same two port numbers are used throughout the life of the connection. Mail packets coming in from the
Internet will have a destination port of 25. Outbound packets will have the port numbers reversed. The
fact that the secure system behind the router always will be accepting mail connections on port 25 is what
makes possible separate control of incoming and outgoing services. The access list can be configured on
either the outbound or inbound interface.
OL-11503-01
6-61
Chapter 6
In the following example, the Ethernet network is a Class B network with the address 128.88.0.0, and
the address of the mail host is 128.88.1.2. The established keyword is used only for the TCP protocol
to indicate an established connection. A match occurs if the TCP datagram has the ACK or RST bits set,
which indicate that the packet belongs to an existing connection.
access-list 102 permit tcp 0.0.0.0 255.255.255.255 128.88.0.0 0.0.255.255 established
access-list 102 permit tcp 0.0.0.0 255.255.255.255 128.88.1.2 0.0.0.0 eq 25
Named Access List Example

The following configuration creates a standard access list named Internet_filter and an extended access
list named marketing_group:
ip address 2.0.5.1 255.255.255.0
ip access-group Internet_filter out
ip access-group marketing_group in
...
ip access-list standard Internet_filter
permit 1.2.3.4
deny any
ip access-list extended marketing_group
permit tcp any 171.69.0.0 0.0.255.255 eq telnet
deny tcp any any
permit icmp any any
deny udp any 171.69.0.0 0.0.255.255 lt 1024
deny ip any any log
IP Extended Access List with Fragment Control Example

The first statement will match and deny only noninitial fragments destined for host 1.1.1.1. The second
statement will match and permit only the remaining nonfragmented and initial fragments that are
destined for host 1.1.1.1 TCP port 80. The third statement will deny all other traffic. In order to block
noninitial fragments for any TCP port, we must block noninitial fragments for all TCP ports, including
port 80 for host 1.1.1.1.
access-list 101 deny ip any host 1.1.1.1 fragments
access-list 101 permit tcp any host 1.1.1.1 eq 80
access-list 101 deny ip any any
Time Range Applied to an IP Access List Example

The following example denies HTTP traffic on Monday through Friday from 8:00 a.m. to 6:00 p.m. on
IP. The example allows UDP traffic on Saturday and Sunday from noon to 8:00 p.m. only.
time-range no-http
periodic weekdays 8:00 to 18:00
!
time-range udp-yes
periodic weekend 12:00 to 20:00
!
ip access-list extended strict
deny tcp any any eq http time-range no-http
permit udp any any time-range udp-yes
!
ip access-group strict in
6-62
OL-11503-01
Chapter 6

Commented IP Access List Entry Examples

In the following example of a numbered access list, the workstation belonging to Jones is allowed access
and the workstation belonging to Smith is not allowed access:
access-list
access-list
access-list
access-list
1
1
1
1
remark Permit only Jones workstation through

permit 171.69.2.88
remark Do not allow Smith workstation through
deny 171.69.3.13
In the following example of a numbered access list, the Winter and Smith workstations are not allowed
to browse the web:
access-list
access-list
access-list
access-list
100
100
100
100
remark Do
deny host
remark Do
deny host
not allow Winter to browse the web

171.69.3.85 any eq http
not allow Smith to browse the web
171.69.3.13 any eq http
In the following example of a named access list, the Jones subnet is not allowed access:
ip access-list standard prevention
remark Do not allow Jones subnet through
deny 171.69.0.0 0.0.255.255
In the following example of a named access list, the Jones subnet is not allowed to use outbound Telnet:
ip access-list extended telnetting
remark Do not allow Jones subnet to telnet out
deny tcp 171.69.0.0 0.0.255.255 any eq telnet
OL-11503-01
6-63
Chapter 6

To prevent the loss of the router configuration, save it to NVRAM.
Command
Password: password
Router#
Purpose
Enters enable mode. Enter the password.
changes to Router#.
Step 2 Router# copy running-config startup-config
Saves the configuration changes to NVRAM so

that they are not lost during resets, power cycles,
or power outages.
Returns to enable mode.
Router#
%SYS-5-CONFIG_I: Configured from console by
console
This message is normal and does not indicate an

error.

To verify the configuration of the MWR 1941-DC, enter the following command:
MWR1941-1#show running-config
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
!
hostname cellsite_router1
!
logging queue-limit 100
enable secret 5 $1$7w/U$C10zHvVw9lD8OOCAoKBKN.
!
clock timezone EST -5
!
redundancy
mode y-cable
standalone
!
ip subnet-zero
!
!
ip cef
no ip domain lookup
ip host bizarre 64.102.16.25
ip host ax 172.18.28.222
!
ip dhcp-server 3.0.0.1
ip dhcp-server 5.0.0.7
multilink bundle-name both
frame-relay switching
!
no voice hpi capture buffer
no voice hpi capture destination
!
mta receive maximum-recipients 0
!
6-64
OL-11503-01
Chapter 6

controller E1 0/0
channel-group 0 timeslots 1-3
!
controller E1 0/1
!
controller T1 0/3
framing esf
linecode b8zs
!
controller T1 0/2
framing esf
linecode b8zs
!
class-map match-all voice-class
match protocol rtp
class-map match-all nm-class
match protocol snmp
match protocol syslog
class-map match-all data-class
match protocol telnet
match protocol ftp
match protocol http
!
policy-map proto
class nm-class
queue-limit 300
class data-class
queue-limit 300
class voice-class
queue-limit 300
!
ip address 172.18.28.202 255.255.255.128
no ip mroute-cache
speed 100
full-duplex
!
description backhaul interface
ip address 4.0.0.8 255.0.0.0
no ip proxy-arp
max-reserved-bandwidth 100
service-policy output proto
encapsulation ppp
ip tcp header-compression iphc-format
ip tcp compression-connections 256
load-interval 30
no keepalive
ip rtp header-compression iphc-format
!
ip address 100.0.0.2 255.0.0.0
OL-11503-01
6-65
Chapter 6
no ip proxy-arp
no ip mroute-cache
load-interval 30
speed 100
full-duplex
no cdp enable
!
ip address 44.0.0.2 255.255.255.0
encapsulation ppp
!
ip address 55.0.0.2 255.255.255.0
encapsulation ppp
shutdown
!
interface Serial0/4
no ip address
shutdown
clockrate 125000
!
interface Serial0/5
no ip address
shutdown
clockrate 125000
!
interface Serial1/0
ip address 99.1.1.1 255.0.0.0
no ip mroute-cache
!
ip http server
ip classless
ip route 0.0.0.0 0.0.0.0 172.18.28.129
ip route 4.0.0.8 255.255.255.255 Serial1/0
ip route 23.0.0.0 255.255.255.0 4.0.0.9
ip route 125.0.0.0 255.255.255.0 4.0.0.9
ip route 126.0.0.0 255.255.255.0 2.0.0.7
ip route 129.0.0.0 255.255.255.0 126.0.0.10
ip route 172.18.28.204 255.255.255.255 Serial1/0
ip route 200.0.0.0 255.255.255.0 4.0.0.9
!
logging 172.18.61.23
access-list 151 permit icmp host 1.1.1.1 host 23.0.0.7
access-list 151 permit tcp host 31.0.0.7 eq telnet host 23.0.0.7 gt 1024
access-list 151 permit tcp host 31.0.0.7 eq ftp host 23.0.0.7 gt 1024
access-list 151 permit tcp host 31.0.0.7 eq www host 23.0.0.7 gt 1024
access-list 151 permit udp host 1.1.1.1 eq snmp host 23.0.0.7 gt 1024
access-list 151 permit udp host 1.1.1.1 eq syslog host 23.0.0.7 gt 1024
access-list 151 permit udp host 10.0.0.7 gt 16000 host 23.0.0.7 gt 1024
access-list 151 permit tcp host 31.0.0.7 eq ftp-data host 23.0.0.7 gt 1024
access-list 151 permit udp host 1.1.1.1 eq snmptrap host 23.0.0.7 gt 1024
connect TDM E1 0/0 1 E1 0/1 1
!
!
tftp-server nvram:/startup-config
snmp-server community public RO
snmp-server community private RW
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
snmp-server enable traps tty
6-66
OL-11503-01
Chapter 6

snmp-server enable traps isdn call-information

snmp-server enable traps isdn layer2
snmp-server enable traps isdn chan-not-avail
snmp-server enable traps isdn ietf
snmp-server enable traps hsrp
snmp-server enable traps config
snmp-server enable traps entity
snmp-server enable traps envmon
snmp-server enable traps ds0-busyout
snmp-server enable traps ds1-loopback
snmp-server enable traps bgp
snmp-server enable traps ipmulticast
snmp-server enable traps msdp
snmp-server enable traps rsvp
snmp-server enable traps frame-relay
snmp-server enable traps frame-relay subif
snmp-server enable traps rtr
snmp-server enable traps syslog
snmp-server host 172.18.61.23 public
!
alarm-interface 1
ip address 99.1.1.2
call rsvp-sync
!
!
line con 0
exec-timeout 0 0
line 33
session-timeout 1
flush-at-activation
no exec
stopbits 1
line aux 0
line vty 0 4
password lab
login
!
end
OL-11503-01
6-67
Chapter 6

There are several methods you can use to remotely manage the MWR 1941-DC router and attached
devices at the cell site. Examples of these methods include using CiscoWorks2000 for Mobile Wireless
(CW4MW) and Telnet.
To enable remote network management of the MWR 1941-DC using CW24MW, do the following:
Step 1
At the privileged prompt, enter the following command to access configuration mode:
Router(config)#
Step 2
End with CNTL/Z.
At the configuration prompt, enter the following command to assign a host name to each of the network
management workstations:
Router(config)# ip host hostname ip_address
Where hostname is the name assigned to the Operations and Maintenance (O&M) workstation and
ip_address is the address of the network management workstation.
Step 3
Enter the following commands to create a loopback interface for O&M:

Step 4

Step 5
At the configuration prompt, enter the following command to specify the recipient of a Simple Network
Management Protocol (SNMP) notification operation:
Router(config)# snmp-server host hostname [traps | informs] [version {1 | 2c | 3 [auth |
noauth | priv]}] community-string [udp-port port] [notification-type]
Where hostname is the name assigned to the CW4MW workstation with the ip host command in Step 2.
Step 6
Enter the following commands to specify the public and private SNMP community names:
Router(config)# snmp-server community public RO
Router(config)# snmp-server community private RW
Step 7
Enter the following command to enable the sending of SNMP traps:

Router(config)# snmp-server enable traps
Step 8
Enter the following command to specify the loopback interface from which SNMP traps should
originate:
Router(config)# snmp-server trap-source loopback number
Where number is the number of the loopback interface you configured for the O&M in Step 3.
Step 9
At the configuration prompt, press Ctrl-Z to exit configuration mode.
Step 10
Write the new configuration to nonvolatile memory as follows:

6-68
OL-11503-01
Chapter 6

Where to Go Next

To monitor and maintain the MWR 1941-DC router, use the following commands:
Command
Purpose
show interface fastethernet slot/port
Displays the status of the FE interface.
show controllers fastethernet slot/port
Displays information about initialization block,

transmit ring, receive ring and errors for the Fast
Ethernet controller chip.
show controllers t1
Displays information about the cable length, framing,

firmware, and errors associated with the T1. With the
MWR 1941-DC, this command also displays the
status of the relays on the VWIC.
clear counters fastethernet slot/port
Clears interface counters.
show controllers
Displays all network modules and their interfaces.

Displays the status of the VWIC relays when a VWIC
is installed.
show interface type slot/port
Displays the configuration and status of the specified

interface.
show protocols
Displays the protocols configured for the router and

the individual interfaces.
Where to Go Next
advanced configuration topics. These publications are available on Cisco.com, the Documentation
CD-ROM that came with your router, or you can order printed copies.
The System Error Messages and Debug Command Reference publications for troubleshooting
information. These publications are available on Cisco.com, the Documentation CD-ROM that came
with your router, or you can order printed copies.
The CiscoWork2000 publications for information on managing your MWR 1941-DC router
remotely.
OL-11503-01
6-69
Chapter 6
Where to Go Next
6-70
OL-11503-01
I N D E X
caution symbol, meaning of
xi
Cisco 2600 series port numbers (figure)

access-class command
6-59
access control, IP
6-46, 6-59
access groups, IP
6-59
Cisco 2600 series routers

slot and port numbering
3-2
Cisco IOS
access-list compiled command
6-56
about
access lists
2-1
command modes
IP
enable mode
configuration examples
6-60, 6-61
getting help
2-2
2-2, 4-24
2-1
dynamic
6-49
saving configuration changes
extended
6-46, 6-49, 6-50
undo command
fragment control
6-53
undo feature
implicit deny when no match found

implicit masks
6-50, 6-53
interface, applying to
6-58
standard
undefined
copy running-config
6-59
exec-timeout
6-49, 6-52
virtual terminal lines, setting on

Turbo Access Control Lists
help
6-59
6-56
6-9
reference
undo
authentication
4-3, 6-4
5-1
4-3, 6-5
2-3
6-12
before starting router

completing
6-46
saving
3-3
3-12
2-3, 3-13, 4-24, 6-64
timeout
4-3, 6-4
configuring
C
cautions, IP access lists
2-3
configuration
asynchronous interface, configuring

dynamic
2-2
2-1
show config
asynchronous/synchronous serial interface

configuring
3-1
commands
6-57
violations, logging
5-2, 5-3
4-14
command modes, Cisco IOS
6-46, 6-47, 6-50
4-28
3-1
command line interface
6-46
time-based
CLI
clock rate settings
6-50
numbered
2-3

6-59
2-3
2-3
CiscoWorks for Mobile Wireless
6-50, 6-53
inbound or outbound interfaces, applying on

named
3-2
asynchronous/synchronous serial interface

6-50
asynchronous interface
6-9
6-12
78-13983-07
IN-1
Index
E1 interface
FE interfaces
first-time
3-6
3-1
host name
3-4
4-2
4-6
FE interface
interface parameters
IP address
3-6
configuring
4-5, 4-9
enabling
ISDN PRI interface

E1 interface
looback
2-2, 4-24
Ethernet interface, configuring
4-4
global parameters
HSRP
enable mode
4-14, 6-13
6-13
mode
4-4
PIM
multiflex trunk interface

E1 interface
4-16, 6-14
T1 interface
4-14, 6-13
multilink interface
password
4-14, 6-13
routing protocol
4-6
4-5
Cisco 2600 series port numbers
3-2
filters
4-10
IP
4-20
See also access lists, IP
RTP/UDP header compression
4-12
4-14, 6-13
conventions, document
fragment control
6-53
frame
xi
counters, PPP multiplexing

cRTP/cUDP
4-6
figure
4-8
PPP multiplexing
T1 interface
4-5
4-5
speed
4-2
redundancy
4-8
IP address
6-14
4-4
5-20, 5-22
sub, count
5-16
super, size
5-13
1-5, 4-12
G
D
global configuration command mode
deny command
6-51
global parameters, configuring
document conventions
duplex mode
2-2
3-4
xi
4-5
dynamic command
6-52
header compression
clearing
5-2, 5-3
configuring
E1/T1 ISDN PRI interface
6-14
E1/T1 multiflex trunk interface

E1 interface
4-12
displaying statistics
4-14, 4-16, 6-13, 6-14
enabling
5-18
5-8
maximum connections
configuring
6-13
E1 interface, configuring
overview
4-14
5-6
1-5
help, Cisco IOS
2-1
IN-2
78-13983-07
Index
host name
undefined
configuring
violations, accounting
6-3
show config command

verifying
6-59
violations, logging
4-3, 6-5
6-52
violations, log-input
4-3, 6-5
host name, configuring
dynamic access list
overview
6-52
virtual terminal lines, setting on
4-2
HSRP
configuring
6-49
6-49, 6-52
named access lists
4-6
6-50
ip access-group command
1-7
6-59
ip access-list command
6-59
6-51
IP address
FE interface
4-5
multilink interface
interface
4-9
configuring E1
4-16
IP-RAN, using the MWR 1941-DC
configuring T1
4-14, 6-13
ip rtp compression-connection
FE, configuring
4-4
loopback, configuring
multilink
1-1
5-6
5-8
ISDN PRI interface
4-4
configuring
4-8
interface configuration command mode
6-13
E1 configuration
2-2
6-14
IOS software
basics
2-1
features of the MWR 1900

verifying version
1-4, 1-8
lock-and-key access, dynamic access list
4-2, 6-3
IP
loopback interfaces, configuring
6-46
4-4
access lists
(caution)
6-50
dynamic
6-49, 6-52
extended, applying time ranges

extended, creating
6-57
masks
6-46, 6-50
implicit, in IP access lists (example)
fragment control
messages
IP
access list violation
access lists
extended
logging
6-53
implicit deny when no match found

implicit masks
6-61
mode y-cable
6-50, 6-53
implicit masks (example)

interface, applying to
named, creating
standard, creating
6-58
6-50
6-46, 6-50
1-9
5-10, 5-17
monitoring and managing the MWR 1900
6-61
inbound or outbound interfaces, applying on
6-49, 6-52
MIB support
6-50, 6-53
6-49, 6-52
6-59
4-28
multiflex trunk interface

configuring
4-14, 6-13
E1 configuration
4-16, 6-14
T1 configuration
4-14, 6-13
78-13983-07
IN-3
Index
multilink interface
configuring
IP address
PIM
permit command
PIM
4-8
4-6
port numbering
4-14
routing protocol
4-13
multilink PPP, configuring

command
command
delay
5-11
configuring
5-12
overview
5-12
overview
5-11
dislpaying counters
4-10
displaying counters
subframe count
subframe size
5-14
subframe count
5-16
subframe size
5-14
ppp mux
5-15
superframe size
5-15
superframe size
5-16
5-13
5-13
5-11
ppp mux delay
5-12
ppp mux frame
5-13
ppp mux pid
5-20, 5-22
1-5
protocol ID
5-20, 5-22
1-5
protocol ID
5-14
named IP access lists
3-2
PPP multiplexing
4-9
multiplexing PPP
delay
4-14
PIM mode
4-9
6-51
5-16
privileged EXEC command mode
6-50
protocol ID
network modules
2-2
5-14
configuring
asynchronous/synchronous interface
Ethernet interface
3-6
Fast Ethernet interface

serial interface
3-7
R
Real
5-8
redundancy
3-7
network processor software

note symbol, meaning of
3-10
command
1-5
configuring
xi
overview
purpose
5-24, 5-25
4-6, 4-20
1-6
1-2
routing protocol
FE interface
parameters
configuring interface
multilink interface
3-6
4-13
RTP/UDP header compression
password
configuring
1-5, 4-12
6-3
show config command

verifying
4-6
4-3, 6-5
4-3, 6-5
password, configuring
4-2
S
saving configuration changes
2-3, 4-24, 6-64
IN-4
78-13983-07
Index
script, setup
3-3
setup command facility

setup script, using
3-1, 3-3
undo feature, Cisco IOS
3-3
show config command
user EXEC command mode
4-3, 6-5

show ppp mux
5-20, 5-22
verifying
3-2
software
configuration
1-5
verifying version
4-2, 6-3
4-5
y cable
standalone
4-2, 6-3
1-4, 1-8
network processor
speed
4-24, 6-64
software version
2-1
IOS features
2-2
5-18
slot and port numbering
IOS basics
2-3
5-24
y cable command
subframe count
1-6
5-10, 5-17
5-25
5-16
subframe size
frame
sub, size
5-15
superframe size
5-13
Symbols
Caution
Note
xi
xi
Timesaver
Tips
xi
xii
T
T1 interface
configuring
4-14, 6-13
timeout, disabling
time ranges
4-3, 6-4
6-57
timesaver symbol, meaning of

tips symbol, meaning of
xi
xii
Turbo ACL (Access Control List)
6-56
78-13983-07
IN-5
Index
IN-6
78-13983-07

SCG

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SCG

Enviado por

Direitos autorais:

Formatos disponíveis

Cisco MWR 1941-DC Mobile Wireless

Edge Router Software Configuration Guide

Text Part Number: OL-11503-01

Document Revision History

Product Documentation DVD

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Overview of the Cisco MWR 1941-DC Router

Cell Site DCN Solution

Software Features for the IP-RAN Implementation

Network Processor (PXF) Software Features

IP-RAN Implementation Updates

Software Features for the Cell Site DCN Application

Limitations and Restrictions

IP-RAN Implementation Limitations and Restrictions

Cell Site DCN Implementation Limitations and Restrictions

Support for Enhanced Link Noise Monitoring (LNM)

Cisco IOS Software Basics

Undoing a Command or Feature

Saving Configuration Changes

Understanding Command Modes

Understanding Boot Images

Understanding MWR 1941-DC Router Interface Numbering

Before Starting Your Router

Using the Setup Command Facility

Configuring Interface Parameters

Ethernet Interface Configuration

FastEthernet Interface Configuration

Frame Relay Encapsulation

Serial Cisco IOS Commands Generated

Asynchronous/Synchronous Serial Interface Configuration

Implementing the MWR 1941-DC Router in an IP-RAN

Configuring the MWR 1941-DC in an IP-RAN

Verifying the Version of Cisco IOS Software

Configuring Fast Ethernet Interfaces

Configuring the FE Interface IP Address

Configuring Routing Protocol Attributes

Configuring HSRP Support

Configuring Multilink Interfaces

Configuring Multilink PPP

Configuring IP Address Assignment

Configuring ACFC and PFC Handling During PPP Negotiation

Configuring the RTP/UDP Compression Flow Expiration Timeout Duration

Configuring T1 and E1 Interfaces

Configuring QoS Attributes

Creating a Class Map

Creating a Policy Map

Assigning a QoS Boilerplate to an Interface

Redundant MWR 1941-DCs

Stand-Alone MWR 1941-DC

Configuring the Link Noise Monitor

Saving Configuration Changes

Monitoring and Managing the MWR 1941-DC

Show Commands for Monitoring the MWR 1941-DC

Cisco MWR 1941-DC Router IP-RAN Command Reference

Implementing the MWR 1941-DC Router in a Cell Site DCN

Configuring the MWR 1941-DC in a Cell Site DCN

Verifying the Version of Cisco IOS Software

Configuring the Ethernet Switch Network Module

Configuring Asynchronous/Synchronous Serial Network Modules or WAN Interface Cards