Cisco 800 Series Software Configuration Guide
Cisco 800 Series Software Configuration Guide
Cisco 800 Series Software Configuration Guide
General Information
1 Years of networking experience: Years of experience with Cisco products:
2 I have these network types: LAN Backbone WAN
Other:
3 I have these Cisco products: Switches Routers
Other (specify models):
4 I perform these types of tasks: H/W installation and/or maintenance S/W configuration
Network management Other:
5 I use these types of documentation: H/W installation H/W configuration S/W configuration
Command reference Quick reference Release notes Online help
Other:
6 I access this information through: % Cisco.com (CCO) % CD-ROM
% Printed docs % Other:
7 I prefer this access method:
8 I use the following three product features the most:
Document Information
Document Title: Cisco 800 Series Software Configuration Guide
Part Number: 78-5372-06 S/W Release (if applicable): 12.2(8)YN
On a scale of 1–5 (5 being the best), please let us know how we rate in the following areas:
The document is written at my The information is accurate.
technical level of understanding.
The document is complete. The information I wanted was easy to find.
The information is well organized. The information I found was useful to my job.
Please comment on our lowest scores:
Mailing Information
Company Name Date
Contact Name Job Title
Mailing Address
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
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 Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as
part of UCB’s 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.
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare,
iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath,
and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That’s Possible, The Fastest
Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA,
CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco
Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack,
Internet Quotient, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing,
RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or
its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0208R)
CBWFQ 1-21
RSVP 1-22
Low Latency Queuing 1-22
Committed Access Rate 1-23
Weighted Fair Queuing 1-24
Weighted Random Early Detection 1-24
ATM Traffic Policing 1-25
Access Lists 1-25
INDEX
This preface describes the audience for, organization of, and conventions used in
this guide. It also provides information on how to access this guide and other
Cisco documentation on the Documentation CD-ROM that ships with Cisco
routers and is available on the World Wide Web.
This document provides software configuration information for the following
Cisco routers:
• Cisco 801, 802, 803, 804, 811, and 813 ISDN routers
• Cisco 805 serial interface router
• Cisco 806 Ethernet router
• Cisco 820 series routers
• Cisco 831, 836, and 837 routers
• Cisco SOHO 70 series routers
• Cisco SOHO 91, 96, and 97 routers
Audience
This guide is intended for network administrators whose backgrounds vary from
having no or little experience configuring routers to having a high level of
experience. You can use this guide in the following ways:
• You have configured the software using the Cisco Router Web Setup tool, and
want to configure additional advanced software features using the
command-line interface (CLI).
• You want to configure the software using only the CLI.
See the “Organization” section of this guide to help you find the chapter(s)
containing the information you need to configure your software.
Organization
This guide contains the following information:
• Chapter 1, “Concepts”—Provides general concept explanations of the
Cisco 800 series and Cisco SOHO routers.
• Chapter 2, “Configuring Basic Networks”—Describes three basic networks
that are appropriate to small independent offices and/or telecommuters.
• Chapter 3, “Configuring Advanced Networks”—Presents more advanced
network scenarios involving a private IP network to the Internet and a
corporate network, and a remote network to two corporate networks.
• Chapter 4, “Network Scenarios”—Describes five Internet access scenarios
and one voice scenario with their specific network topologies and
configurations.
• Chapter 5, “Configuring Remote CAPI”—Describes the Remote Common
Application Programming Interface (CAPI), a PC-based application
programming interface standard used to access ISDN equipment.
Conventions
This guide uses the following conventions for instructions and information.
Note Means reader take note. Notes contain helpful suggestions or references to
materials not contained in this manual.
Caution This caution symbol means reader be careful. In this situation, you might do
something that could result in equipment damage or loss of data.
Command Conventions
Table 1 describes the command syntax used in this document.
Table 1 Conventions
Convention Description
boldface Commands and keywords.
italic Command input that is supplied by you.
[ ] Optional keywords and default responses to system
prompts appear within square brackets.
{x | x | x} A choice of keywords (represented by x) appears in
braces separated by vertical bars. You must select
one.
^ or Ctrl Represent the key labeled Control. For example,
when you read ^D or Ctrl-D, you should hold down
the Control key while you press the D key.
screen font Examples of information displayed on the screen.
boldface screen Examples of information that you must enter.
font
Related Documents
The following publications provide related information on these products:
• Cisco 800 series routers
– Cisco 800 Series Router Cabling and Setup Quick Start Guide—Provides
quick installation information on the Cisco 801–804 routers.
– Cisco 800 Series Routers Hardware Installation Guide—Provides
installation information on the Cisco 801–804 routers.
• Cisco 805 router
– Cisco 805 Router Cabling and Setup Quick Start Guide—Provides quick
installation information on the Cisco 805 router.
– Cisco 805 Router Hardware Installation Guide—Provides installation
information on the Cisco 805 router.
• Cisco 806 router
– Cisco 806 Router Cabling and Setup Quick Start Guide—Provides quick
installation information on the Cisco 806 router.
– Cisco 806 Router Hardware Installation Guide—Provides installation
information on the Cisco 806 router.
• Cisco 811 and 813 routers
– Cisco 811 and 813 Router Cabling and Setup Quick Start
Guide—Provides quick installation information on the Cisco 811 and
813 routers.
– Cisco 811 and 813 Router Hardware Installation Guide—Provides
installation information on the Cisco 806 router.
• Cisco 826 router
– Cisco 826 Routers Hardware Installation Guide—Provides installation
information on the Cisco 826 routers.
– Cisco 826 and Cisco SOHO 76 Router Quick Start Guide—Provides
quick installation information on the Cisco 826 router.
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco
Documentation CD-ROM package, which is shipped with your product. The
Documentation CD-ROM is updated monthly and may be more current than
printed documentation. The CD-ROM package is available as a single unit or
through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
• Registered Cisco Direct Customers can order Cisco product documentation
from the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
• Registered Cisco.com users can order the Documentation CD-ROM through
the online Subscription Store:
http://www.cisco.com/go/subscription
• Nonregistered Cisco.com users can order documentation through a local
account representative by calling Cisco corporate headquarters (California,
USA) at 408 526-7208 or, elsewhere in North America, by calling 800
553-NETS (6387).
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit
technical comments electronically. Click Feedback at the top of the Cisco
Documentation home page. After you complete the form, print it out and fax it to
Cisco at 408 527-0730.
You can e-mail your comments to [email protected].
To submit your comments by mail, use the response card behind the front cover
of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that
provides immediate, open access to Cisco information, networking solutions,
services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use
tool that provides a broad range of features and services to help you to:
• Streamline business processes and improve productivity
• Resolve technical issues with online support
• Download and test software packages
All customers, partners, and resellers who have a valid Cisco services contract
have complete access to the technical support resources on the Cisco TAC Web
Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you
have a valid service contract but do not have a login ID or password, go to the
following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and
you are a Cisco.com registered user, you can open a case online by using the TAC
Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases
through the Cisco TAC Web Site.
The data-and-voice Cisco 827-4V router has four Foreign Exchange Station
(FXS)/plain old telephone service (POTS) ports in addition to the 10BASE-T
Ethernet port and one ADSL network port, and it supports Voice over IP (VoIP).
The four FXS/POTS ports will support loop-start functions for connecting to
POTS devices up to 500 ft. The Cisco 827-4V router includes a digital signal
processor (DSP) chip to support VoIP over ATM adaptation layer (AAL5)
protocol.
AAL5 operates over the ADSL physical interface for both data and voice. The
ADSL protocol supports EOC message sets defined in T1.413 DMT Issue 2 as
limited by digital subscriber line access multiplexers (DSLAMs). The ADSL
controller and line interface unit are based on Alcatel chip sets.
The Cisco 828 router is Cisco IOS-based with ATM/SHDSL support. The
Cisco SOHO 78 router also supports ATM/SHDSL. The routers send data, voice,
and video over high-speed G.SHDSL lines to connect to the Internet or corporate
intranets.
Both the Cisco 828 router and the Cisco SOHO 78 router provide a 4-port
Ethernet hub, in addition to the G.SHDSL port.
Both the Cisco 831 router and the Cisco SOHO 91 Ethernet-to-Ethernet routers
can connect a corporate telecommuter or small office to an ISP over a broadband
or Ethernet connection to corporate LANs or the Internet. The routers are capable
of bridging and multiprotocol routing between LAN and WAN ports. The
Cisco 831 router is a hardware encryption–capable router offering business-class
features to small offices and enterprise telecommuters. The Cisco SOHO 91
router offers software encryption capability without hardware encryption.
The Cisco 836 and Cisco SOHO 96 routers are ADSL routers with an integrated
switch. These routers provide a 4-port Ethernet switch for the LAN and an ADSL
physical interface for the WAN compatibility. The Cisco 836 router is a hardware
encryption–capable, Ethernet-to -ADSL router offering business-class features to
small offices and enterprise telecommuters. The Cisco SOHO 96 router offers
software encryption capability without hardware encryption. Both these routers
provide an ISDN basic rate interface (BRI) S/T interface as a backup for the
ADSL interface.
The Cisco 837 and Cisco SOHO 97 routers are ADSL routers with an integrated
switch. These routers provide a 4-port Ethernet switch for LAN and an ADSL
physical interface for WAN compatibility. The Cisco 837 router is a hardware
encryption–capable, Ethernet-to -ADSL router offering business-class features to
small offices and enterprise telecommuters. The Cisco SOHO 97 router offers
software encryption capability without hardware encryption.
The Cisco 831, 836, and 837, and Cisco SOHO 91, 96, and 97 routers support
switch functions which enable the routers to be connected as a 10/100 BASE-T
device. These routers crossover functionality enable them to detect MDI/MDIX
to any other PC or hub with a straight-through cable or crossover cable.
Table 1-1 summarizes what interface each Cisco model supports.
ADSL
ADSL is a technology that allows both data and voice to transmit over the same
line. It is a packet-based network technology that allows high-speed transmission
over twisted-pair copper wire on the local loop (“last mile”) between a network
service provider (NSP) central office and the customer site, or on local loops
created either within a building or campus.
The benefit of ADSL over a serial or dial-up line is that it is always on and always
connected, increasing bandwidth and lowering the costs compared with a dial-up
or leased line. ADSL technology is asymmetric in that it allows more bandwidth
from an NSP’s central office to the customer site than from the customer site to
the central office. This asymmetry, combined with always-on access (which
eliminates call setup), makes ADSL ideal for Internet and intranet accessing,
video-on-demand, and remote LAN access.
SHDSL
SHDSL is a technology based on the G.SHDSL (G.991.2) standard that allows
both data and voice to be transmitted over the same line. SHDSL is a packet-based
network technology that allows high-speed transmission over twisted-pair copper
wire between a network service provider (NSP) central office and a customer site,
or on local loops created within either a building or a campus.
G.SHDSL devices can extend reach from central offices and remote terminals to
approximately 26,000 feet, at symmetrical data rates from 72 kbps up to
2.3 Mbps. In addition, it is repeatable at lower speeds, which means there is
virtually no limit to its reach.
SHDSL technology is symmetric in that it allows equal bandwidth between an
NSP’s central office and a customer site. This symmetry, combined with
always-on access (which eliminates call setup), makes SHDSL ideal for LAN
access.
With the DNS-based x.25 routing feature, it is easy to manage the X.121-to-IP
addressing correlation and the mnemonic-to-X.121 addressing correlation.
Instead of the router needing a route statement going to all destinations, all that is
needed is a wildcard route statement that covers all addresses in the DNS.
Network Protocols
Network protocols enable the network to pass data from its source to a specific
destination over LAN or WAN links. Routing address tables are included in the
network protocols to provide the best path for moving the data through the
network.
IP
The best known Transmission Control Protocol/Internet Protocol (TCP/IP) at the
internetwork layer is IP, which provides the basic packet delivery service for all
TCP/IP networks. In addition to the physical node addresses, the IP protocol
implements a system of logical host addresses called IP addresses. The IP
addresses are used by the internetwork and higher layers to identify devices and
to perform internetwork routing. The Address Resolution Protocol (ARP) enables
IP to identify the physical address that matches a given IP address.
IP is used by all protocols in the layers above and below it to deliver data, which
means that all TCP/IP data flows through IP when it is sent and received
regardless of its final destination.
IP is a connectionless protocol, which means that IP does not exchange control
information (called a handshake) to establish an end-to-end connection before
transmitting data. In contrast, a connection-oriented protocol exchanges control
information with the remote computer to verify that it is ready to receive data
before sending it. When the handshaking is successful, the computers have
established a connection. IP relies on protocols in other layers to establish the
connection if connection-oriented services are required.
IP exchanges routing information using Routing Information Protocol (RIP), a
dynamic distance-vector routing protocol. RIP is described in more detail in the
following subsections.
G.DMT
G.DMT full-rate ADSL is a technology that can expand the usable bandwidth of
existing copper telephone lines, delivering high-speed data communications at
rates of up to 10 Mbps. The technology brings full-motion video, efficient
telecommuting, and high-speed data transmission to the home or business, all
without interrupting normal telephone service.
American National Standards Institute (ANSI) has published an industry standard
(known as T1.413) for full-rate ADSL in the United States. The International
Telecommunication Union (ITU) has approved a nearly identical global industry
standard for full-rate ADSL, known as G.992.1. The ANSI and ITU specifications
call for operations rates of up to 8 Mbps downstream and up to 640 Kbps upstream
when operating over telephone lines at a distance of up to 18,000 feet.
Standard-compliant full-rate ADSL uses a modulation technique known as
discrete multitone, or DMT. DMT divides the upstream and downstream bands
into a collection of smaller frequency ranges of approximately 4 kHz subchannel
that carries a portion of the total data rate. By dividing the transmission bandwidth
into a collection of subchannels, DMT is able to adapt to the distinct
characteristics of each telephone line and maximize the data transmission rate.
Telephone lines are best suited for transmission of the low frequencies associated
with voice traffic (0–4 kHz). The high frequencies that are used for full-rate
ADSL transmissions experience distortion and attenuation when sent over
telephone lines- the higher the frequency, the more the attenuation. DMT
effectively divides the data into a collection of smaller bandwidth transmissions,
each of which occupies a smaller frequency range and is optimized to maximize
the data throughput in that range. The ANSI and ITU standards have both
established DMT as the standard modulation technique for full-rate ADSL.
U-R2
U-R2 is a German Deutsche Telekom specification for ADSL over copper loops
running ISDN in the base band (lower frequencies). It transmits and receives
ADSL signals according to the ITU-T G.992.1 Annex B standard. It is a superset
of the G.992.1 Annex B standard, allowing for greater cross-vendor
interoperability.
RIP
RIP is an associated protocol for IP, and is widely used for routing Internet
protocol traffic. RIP is a distance-vector routing protocol, which means that it
uses distance (hop count) as its metric for route selection. Hop count is the
number of routers that a packet must traverse to reach its destination. For
example, if a particular route has a hop count of 2, then a packet must traverse two
routers to reach its destination.
By default, RIP routing updates are broadcast every 30 seconds. You can
reconfigure the interval at which the routing updates are broadcast. You can also
configure triggered extensions to RIP so that routing updates are sent only when
the routing database is updated. For more information on triggered extensions to
RIP, refer to the Cisco IOS 12.0(1)T documentation set. For information on
accessing the documentation, see the “References to Cisco IOS Documentation
Set” on page xxi.
EIGRP
EIGRP is an advanced Cisco proprietary distance-vector and link state routing
protocol, which means it uses a metric more sophisticated than distance (hop
count) for route selection. Enhanced IGRP uses a metric based on a successor,
which is a neighboring router that has a least-cost path to a destination that is
guaranteed not to be part of a routing loop. If a successor for a particular
destination does not exist but neighbors advertise the destination, the router must
recompute a route.
Each router running Enhanced IGRP sends hello packets every 5 seconds to
inform neighboring routers that it is functioning. If a particular router does not
send a hello packet within a prescribed period, Enhanced IGRP assumes that the
state of a destination has changed and sends an incremental update.
Because Enhanced IGRP supports IP, you can use one routing protocol for
multi-protocol network environments, minimizing the size of the routing tables
and the amount of routing information.
PAP
PAP uses a two-way handshake to verify the passwords between routers. To
illustrate how PAP works, imagine a network topology in which a remote office
Cisco 827 router is connected to a corporate office Cisco 3600 router. After the
PPP link is established, the remote office router repeatedly sends a configured
username and password until the corporate office router accepts the
authentication.
PAP has the following characteristics:
• The password portion of the authentication is sent across the link in clear text
(not scrambled or encrypted).
• PAP provides no protection from playback or repeated trial-and-error attacks.
• The remote office router controls the frequency and timing of the
authentication attempts.
CHAP
CHAP uses a three-way handshake to verify passwords. To illustrate how CHAP
works, imagine a network topology in which a remote office Cisco 827 router is
connected to a corporate office Cisco 3600 router.
After the PPP link is established, the corporate office router sends a challenge
message to the remote office router. The remote office router responds with a
variable value. The corporate office router checks the response against its own
calculation of the value. If the values match, the corporate office router accepts
the authentication. The authentication process can be repeated any time after the
link is established.
Note Cisco recommends using CHAP because it is the more secure of the two
protocols.
TACACS+
Cisco 800 series routers support the Terminal Access Controller Access Control
System Plus (TACACS+) protocol through Telnet. TACACS+ is a Cisco
proprietary authentication protocol that provides remote access authentication
and related network security services, such as event logging. User passwords are
administered in a central database rather than in individual routers. TACACS+
also provides support for separate modular authentication, authorization, and
accounting (AAA) facilities that are configured at individual routers.
Network Interfaces
This section describes the network interface protocols that Cisco 800 series
routers support. The following network interface protocols are supported:
• Ethernet
• ATM
• ISDN
Ethernet
Ethernet is a baseband LAN protocol that transports data and voice packets to the
WAN interface using carrier sense multiple access collision detect (CSMA/CD).
The term Ethernet is now often used to refer to all CSMA/CD LANs. Ethernet was
designed to serve in networks with sporadic, occasionally heavy traffic
requirements, and the IEEE 802.3 specification was developed in 1980 based on
the original Ethernet technology.
Under the Ethernet CSMA/CD media-access process, any host on a CSMA/CD
LAN can access the network at any time. Before sending data, CSMA/CD hosts
listen for traffic on the network. A host wanting to send data waits until it detects
no traffic before it transmits. Ethernet allows any host on the network to transmit
whenever the network is quiet. A collision occurs when two hosts listen for traffic,
hear none, and then transmit simultaneously. In this situation, both transmissions
are damaged, and the hosts must retransmit at some later time. Algorithms
determine when the colliding hosts should retransmit.
ATM
Asynchronous Transfer Mode (ATM) is a high-speed, multiplexing and switching
protocol that supports multiple traffic types including voice, data, video, and
imaging.
ATM is composed of fixed-length cells that switch and multiplex all information
for the network. An ATM connection is simply used to transfer bits of information
to a destination router or host. The ATM network is considered a LAN with high
bandwidth availability. Unlike a LAN, which is connectionless, ATM requires
certain features to provide a LAN environment to the users.
Each ATM node must establish a separate connection to every node in the ATM
network that it needs to communicate with. All such connections are established
through a permanent virtual circuit (PVC).
PVC
A PVC is a connection between remote hosts and routers. A PVC is established
for each ATM end node with which the router communicates. The characteristics
of the PVC that are established when it is created are set by the ATM adaptation
layer (AAL) and the encapsulation type. An AAL defines the conversion of user
information into cells. An AAL segments upper-layer information into cells at the
transmitter and reassembles the cells at the receiver.
Cisco routers support the AAL5 format, which provides a streamlined data
transport service that functions with less overhead and affords better error
detection and correction capabilities than AAL3/4. AAL5 is typically associated
with variable bit rate (VBR) traffic and unspecified bit rate traffic (UBR).
Cisco 800 series routers also support AAL1 and 2 formats.
ATM encapsulation is the wrapping of data in a particular protocol header. The
type of router you are connecting to determines the type of ATM PVC
encapsulation types.
The routers support the following encapsulation types for ATM PVCs:
• LLC/SNAP (RFC 1483)
• VC-MUX (RFC 1483)
• PPP (RFC 2364)
Each PVC is considered a complete and separate link to a destination node. Users
can encapsulate data as needed across the connection. The ATM network
disregards the contents of the data. The only requirement is that data be sent to the
router's ATM subsystem in a manner that follows the specific AAL format.
Dialer Interface
A dialer interface assigns PPP features (such as authentication and IP address
assignment method) to a PVC. Dialer interfaces are used when configuring PPP
over ATM.
Dialer interfaces can be configured independently of any physical interface and
applied dynamically as needed.
Dial Backup
Dial backup provides protection against WAN downtime by allowing user to
configure a backup modem line connection. The following can be used to bring
up the dial backup feature in the Cisco IOS software:
• Backup Interface
• Floating Static Routers
• Dialer Watch
Backup Interface
A backup interface is an interface that stays idle until certain circumstances occur,
such as WAN downtime, at which point it is activated. The backup interface can
be a physical interface such as Basic Rate Interface (BRI), or an assigned backup
dialer interface to be used in a dialer pool. While the primary line is up, the backup
interface is placed in standby mode. In standby mode, the backup interface is
effectively shut down until it is enabled. Any route associated with the backup
interface does not appear in the routing table.
Because the backup interface command is dependent on the router’s identifying
that an interface is physically down, it is commonly used to back up ISDN BRI
connections and async lines and leased lines. The interfaces to such connections
go up when the primary line fails, and the backup interface quickly identifies such
failures.
Dialer Watch
Dialer watch is a backup feature that integrates dial backup with routing
capabilities. Dialer watch provides reliable connectivity without having to define
traffic of interest to trigger outgoing calls at the central router. Hence, dialer watch
can be considered regular DDR with no requirement for traffic of interest. By
configuring a set of watched routes that define the primary interface, you are able
to monitor and track the status of the primary interface as watched routes are
added and deleted.
When a watched route is deleted, dialer watch checks for at least one valid route
for any of the IP addresses or networks being watched. If there is no valid route,
the primary line is considered down and unusable. If there is a valid route for at
least one of the watched IP networks defined and the route is pointing to an
interface other than the backup interface configured for dialer watch, the primary
link is considered up and dialer watch does not initiate the backup link.
NAT
Network address translation (NAT) provides a mechanism for a privately
addressed network to access registered networks, such as the Internet, without
requiring a registered subnet address. This mechanism eliminates the need for
host renumbering and allows the same IP address range to be used in multiple
intranets.
NAT is configured on the router at the border of an inside network (a network that
uses nonregistered IP addresses) and an outside network (a network that uses a
globally unique IP address; in this case, the Internet). NAT translates the inside
local addresses (the nonregistered IP addresses assigned to hosts on the inside
network) into globally unique IP addresses before sending packets to the outside
network.
With NAT, the inside network continues to use its existing private or obsolete
addresses. These addresses are converted into legal addresses before packets are
forwarded onto the outside network. The translation function is compatible with
standard routing; the feature is required only on the router connecting the inside
network to the outside domain.
Easy IP (Phase 1)
The Easy IP (Phase 1) feature combines Network Address Translation (NAT) and
PPP/Internet Protocol Control Protocol (IPCP). This feature enables a Cisco
router to automatically negotiate its own registered WAN interface IP address
from a central server and to enable all remote hosts to access the Internet using
this single registered IP address. Because Easy IP (Phase 1) uses existing
port-level multiplexed NAT functionality within the Cisco IOS software, IP
addresses on the remote LAN are invisible to the Internet.
The Easy IP (Phase 1) feature combines NAT and PPP/IPCP. With NAT, the router
translates the nonregistered IP addresses used by the LAN devices into the
globally unique IP address used by the dialer interface. The ability of multiple
LAN devices to use the same globally unique IP address is known as overloading.
NAT is configured on the router at the border of an inside network (a network that
uses nonregistered IP addresses) and an outside network (a network that uses a
globally unique IP address; in this case, the Internet).
With PPP/IPCP, the Cisco routers automatically negotiate a globally unique
(registered) IP address for the dialer interface from the ISP router.
Easy IP (Phase 2)
The Easy IP (Phase 2) feature combines Dynamic Host Configuration Protocol
(DHCP) server and relay. DHCP is a client-server protocol that enables devices
on an IP network (the DHCP clients) to request configuration information from a
DHCP server. DHCP allocates network addresses from a central pool on an
as-needed basis. DHCP is useful for assigning IP addresses to hosts connected to
the network temporarily or for sharing a limited pool of IP addresses among a
group of hosts that do not need permanent IP addresses.
DHCP frees you from having to assign an IP address to each client manually, and
configures the router to forward UDP broadcasts, including IP address requests,
from DHCP clients.
DHCP allows for increased automation and fewer network administration
problems by
• Eliminating the need for the manual configuration of individual computers,
printers, and shared file systems
• Preventing the simultaneous use of the same IP address by two clients
• Allowing configuration from a central site
Note When using NAT, DHCP relay cannot be used on the Cisco 800 series routers. The
built-in DHCP server should be used instead.
After the IPSec server has been configured, a VPN connection can be created with
minimal configuration on an IPSec client, such as a supported Cisco 800 series
router. When the IPSec client then initiates the VPN tunnel connection, the IPSec
server pushes the IPSec policies to the IPSec client and creates the corresponding
VPN tunnel connection.
VoIP
The Cisco 827-4V router is a voice-and-data-capable router that provides
Voice-over-IP (VoIP) functionality and can carry voice traffic (such as telephone
calls and faxes) over an IP network.
Cisco voice support is implemented using voice packet technology. There are two
primary applications for VoIP:
• It provides a central-site telephony termination facility for VoIP traffic from
multiple voice-equipped remote office facilities.
• It provides a PSTN gateway for Internet telephone traffic. VoIP used as a
PSTN gateway leverages the standardized use of H.323-based Internet
telephone client applications.
In VoIP, the digital signal processor (DSP) segments the voice signal into frames
and stores them in voice packets. These voice packets are transported by using IP
in compliance with H.323 signaling standards.
H.323
H.323 is an International Telecommunication Union (ITU-T) standard that
describes packet-based video, audio, and data conferencing. H.323 is an umbrella
standard that describes the architecture of the conferencing system and refers to a
set of other standards (H.245, H.225.0, and Q.931) to describe its actual protocol.
Cisco H.323 Version 2 support upgrades Cisco IOS software to comply with the
mandatory requirements and several of the optional features of the version 2
specification. This upgrade enhances the existing VoIP gateway and the
Multimedia Conference Manager (gatekeeper and proxy). A gateway allows
H.323 terminals to communicate with non-H.323 terminals by converting
protocols, and it is an endpoint on the LAN that provides real-time, two-way
communications between H.323 terminals on the LAN and other ITU-T terminals
in the WAN or to another H.323 gateway.
QoS
This section describes quality of service (QoS) parameters, including the
following:
• IP Precedence
• PPP Fragmentation and Interleaving
• CBWFQ
• RSVP
• Low Latency Queuing
QoS refers to the capability of a network to provide better service to selected
network traffic over various technologies, including ATM, Ethernet and IEEE
802.1 networks, and IP-routed networks that may use any or all of these
underlying technologies. Primary goals of QoS include dedicated bandwidth,
controlled jitter and latency (required by some real-time and interactive traffic),
and improved loss characteristics. QoS technologies provide the elemental
building blocks for future business applications in campus, WAN, and service
provider networks.
QoS must be configured throughout your network, not just on your router running
VoIP, to improve voice network performance. Not all QoS techniques are
appropriate for all network routers. Edge routers and backbone routers in your
network do not necessarily perform the same operations; the QoS tasks they
perform might differ as well. To configure your IP network for real-time voice
traffic, you need to consider the functions of both edge and backbone routers in
your network.
QoS software enables complex networks to control and predictably service a
variety of networked applications and traffic types. Almost any network can take
advantage of QoS for optimum efficiency, whether it is a small corporate network,
an Internet service provider, or an enterprise network.
IP Precedence
You can partition traffic in up to six classes of service using IP Precedence (two
others are reserved for internal network use). The queuing technologies
throughout the network can then use this signal to expedite handling.
Features such as policy-based routing and committed access rate (CAR) can be
used to set precedence based on extended access-list classification. This allows
considerable flexibility for precedence assignment, including assignment by
application or user, or by destination and source subnet, and so on. Typically this
functionality is deployed as close to the edge of the network (or administrative
domain) as possible, so that each subsequent network element can provide service
based on the determined policy.
IP Precedence can also be set in the host or network client with the signaling used
optionally. IP Precedence enables service classes to be established using existing
network queuing mechanisms (such as CBWFQ), with no changes to existing
applications or complicated network requirements.
CBWFQ
In general, class-based weighted fair queuing (CBWFQ) is used in conjunction
with multilink PPP and interleaving and RSVP or IP precedence to ensure voice
packet delivery. CBWFQ is used with multilink PPP to define how data is
managed; RSVP or IP Precedence is used to give priority to voice packets.
There are two levels of queuing: ATM queues and Cisco IOS queues. CBWFQ is
applied to Cisco IOS queues. A first-in-first-out (FIFO) Cisco IOS queue is
automatically created when a PVC is created. If you use CBWFQ to create classes
and attach them to a PVC, a queue is created for each class.
CBWFQ ensures that queues have sufficient bandwidth and that traffic gets
predictable service. Low-volume traffic streams are preferred; high-volume traffic
streams share the remaining capacity, obtaining equal or proportional bandwidth.
RSVP
RSVP enables routers to reserve enough bandwidth on an interface to ensure
reliability and quality performance. RSVP allows end systems to request a
particular QoS from the network. Real-time voice traffic requires network
consistency. Without consistent QoS, real-time traffic can experience jitter,
insufficient bandwidth, delay variations, or information loss. RSVP works in
conjunction with current queueing mechanisms. It is up to the interface queuing
mechanism (such as CBWFQ) to implement the reservation.
RSVP works well on PPP, HDLC, and similar serial-line interfaces. It does not
work well on multi-access LANs. RSVP can be equated to a dynamic access list
for packet flows.
You should configure RSVP to ensure QoS if the following conditions
characterize your network:
• Small-scale voice network implementation
• Links slower than 2 Mbps
• Links with high utilization
• Need for the best possible voice quality
Rate Limitation
The rate limitation feature of CAR provides the network operator with the means
to define Layer 3 aggregate or granular access, or egress bandwidth rate limits,
and to specify traffic handling policies when the traffic either conforms to or
exceeds the specified rate limits. Aggregate access or egress matches all packets
on an interface or subinterface. Granular access or egress matches a particular
type of traffic based on precedence. You can designate CAR rate limitation
policies based on physical port, packet classification, IP address, MAC address,
application flow, and other criteria specifiable by access lists or extended access
lists. CAR rate limits may be implemented either on input or output interfaces or
subinterfaces including Frame Relay and ATM subinterfaces.
An example of the use of the rate-limiting capability of CAR is application-based
rates limiting HTTP World Wide Web traffic to 50 percent of link bandwidth,
which ensures capacity for non-Web traffic including mission-critical
applications.
Marking of IP Precedence
Extended access list classification can be used to set precedence that might be
needed for features like class-based traffic shaping and CAR. This allows
considerable flexibility for precedence assignment, including assignment by
application or user, or by destination and source subnet, and so on. Typically this
functionality is deployed as close to the edge of the network (or administrative
domain) as possible, so that each subsequent network element can provide service
based on the determined policy.
IP Precedence can also be set in the host or network client with the signaling used
optionally. IP precedence enables service classes to be established using existing
network queuing mechanisms (such as CBWFQ), with no changes to existing
applications or complicated network requirements.
Access Lists
With basic standard and static extended access lists, you can approximate session
filtering by using the established keyword with the permit command. The
established keyword filters TCP packets based on whether the ACK or RST bits
are set. (Set ACK or RST bits indicate that the packet is not the first in the session
and the packet therefore belongs to an established session.) This filter criterion
would be part of an access list applied permanently to an interface.
Step 1 If using ISDN, order an ISDN line from your telephone service provider. For
complete information on ordering your ISDN line, see Appendix D,
“Provisioning an ISDN Line.”
Step 2 While ordering your ISDN line, gather the following information from your
telephone service provider:
• ISDN switch type.
• Service profile identifiers (SPIDs). Only telephone service providers in North
America assign SPIDs. SPIDs identify the ISDN B channels. The SPID
format is generally an ISDN telephone number with additional numbers at the
end; for example, 40855522220101. Depending on the switch that supports
your ISDN line, your ISDN line could be assigned zero, one, or two SPIDs.
• ISDN local directory numbers (LDNs), which are the local ISDN telephone
numbers of your router. Examples are 4085552222 or 5553333.
Note The format of the LDN varies from region to region, depending on the
telephone service provider. In some regions, you need to add the area
code to the telephone number. Find out from your local telephone
service provider whether or not you need to specify an area code for
the LDN.
Step 3 If setting up an Internet connection, gather the following information from your
Internet service provider (ISP):
• Point-to-Point Protocol (PPP) client name that the ISP assigns as your login
name.
• PPP authentication type: Challenge Handshake Authentication Protocol
(CHAP) or Password Authentication Protocol (PAP).
• PPP password to access your ISP account.
• IP address information: the IP address and subnet mask of the ISP ISDN
interface. Also, if configuring a public IP network, you must gather the
registered IP addresses and subnet masks to be used on your router LAN and
WAN interfaces.
• ISP telephone number.
2
6
5
1
7
8
3
10.0.0.0 255.0.0.0
74930
4 9
192.168.1.100
Callout
Number Description
1 DHCP server at Site 1
2 National ISDN-1 switch type, with B1 SPID 40855511110101 and
B2 SPID 40855522220101
3 Private IP network
4 DHCP client
5 PPP link
6 ISDN phone number, 4085551111
7 Internet service provider
8 CHAP or PAP
9 Domain Name System (DNS) server
Features Used
This network uses the following features on the LAN:
• IP routing
• Dynamic Host Configuration Protocol (DHCP) server (optional)
When your router is acting as a DHCP server, workstations configured as DHCP
clients are automatically assigned an IP address and subnet mask.
This network uses the following features on the WAN:
• IP routing
• PPP
• Network Address Translation (NAT) overload
• Internet Protocol Control Protocol (IPCP)
• CHAP or PAP over PPP
• Dial-on-demand routing (DDR)
• Static routes
With NAT overload configured, the router uses one address for multiple hosts.
With IPCP configured, your router automatically negotiates its IP address from
the router it is attempting to connect to.
You can use either CHAP or PAP as the PPP authentication protocol. Cisco
recommends using CHAP, because it is the more secure of the two protocols.
In addition, the ISDN line is activated only when needed (DDR), using one route
that has been manually configured (static route). DDR using static routes suits
small networking environments that do not have complex routing topologies.
Configuration
To configure the features for this network example, perform the following steps
on the PC, starting in global configuration mode.
Step 1 Specify a name for the router. For example, specify SanJose as the router name:
router(config)# hostname SanJose
Step 3 Configure the router to recognize the zero subnet range as a valid range of
addresses:
SanJose(config)# ip subnet-zero
Step 4 Disable the router from translating unfamiliar words entered during a console
session into IP addresses:
SanJose(config)# no ip domain-lookup
Step 5 Optional. Configure your router as a DHCP server. Define the DHCP relay pool
name. For example:
router(config)# ip dhcp pool DHCPpoolLAN_0
b. Set the IP address and subnet mask for the LAN interface. For example:
SanJose(config-if)# ip address 10.0.0.1 255.0.0.0
Step 7 Enable NAT on your LAN. The inside network address is not directly routed to
the Internet, but is subject to translation to a routable address outside the LAN.
For example:
SanJose(config-if)# ip nat inside
c. Enable PPP:
SanJose(config-if)# encapsulation ppp
f. Create a dialer rotary group, specifying a number between 0 and 255. Dialer
rotary groups are useful in environments that require multiple calling
destinations. For example:
SanJose(config-if)# dialer rotary-group 0
g. North America only. Associate the ISDN local directory numbers (LDNs)
provided by your telephone service provider with the first and second SPIDs.
You can specify the SPID number, or you can have it automatically detected
by entering a 0.
In the following example, the SPID number is represented by a 0, so that it
will be automatically detected. The primary LDN is followed by the
secondary LDN for each SPID.
SanJose(config-if)# isdn spid1 0 4085551111 4085552222
SanJose(config-if)# isdn spid2 0 4085553333 4085554444
Note Find out from your telephone service provider whether you need to
specify an area code for the LDN.
h. North America only. If you had manually entered the SPID number, enable
the BRI0 interface.
SanJose(config-if)# no shutdown
j. Outside of North America only. Specify the ISDN switch type. To get a listing
of supported switches, enter the isdn switch-type ? command.
The following example specifies the NET3 switch type:
router(config-if)# isdn switch-type basic-net3
Step 9 Follow these steps to specify characteristics of the dialer rotary group that were
created in the previous step:
a. Change to global configuration mode:
SanJose(config-if)# exit
SanJose(config)#
c. Specify that the IP address for this interface is obtained by using IPCP:
SanJose(config-if)# ip address negotiated
e. Enable DDR:
SanJose(config-if)# dialer in-band
f. Specify the amount of time in number of seconds that the line can be idle
before it is disconnected:
SanJose(config-if)# dialer idle-timeout 300
g. Specify the telephone number of the interface to be called if you are calling
a single site. For example:
SanJose(config-if)# dialer string 14085553333
h. Set the maximum number of packets to be held in the outgoing queue to 10.
If an ISDN connection does not exist yet, the hold queue holds up to 10
packets before dropping them. For example:
SanJose(config-if)# dialer hold-queue 10
i. Define the load level that must be exceeded on the first ISDN B channel
before the second B channel is brought up. The load-threshold variable
represents a utilization percentage and is a number between 1 and 255, where
255 equals 100 percent. For example:
SanJose(config-if)# dialer load-threshold 10 outbound
Note Enter outbound to calculate the load using outbound data only,
inbound to calculate the load using inbound data only, and either to
set the maximum calculated load as the larger of the outbound and
inbound loads.
l. Configure PAP. To configure CHAP, skip this step and follow the previous
step.
The following command enables PAP and specifies authentication on
incoming calls only. Unidirectional authentication is used because routers
that do not support bidirectional authentication are potentially in use at the
ISP. In these cases, when the SanJose router calls the ISP, SanJose does not
authenticate. However, the ISP authenticates SanJose before allowing the
connection.
SanJose(config-if)# ppp authentication pap callin
m. Enable remote PAP support for an interface. The username and password are
sent in the PAP authentication request packet. The password must contain
from 1 to 25 upper- and lowercase alphanumeric characters; it cannot contain
spaces nor underscores.
SanJose(config-if)# ppp pap sent-username SanJose
password gocisco
Step 10 Follow these steps to configure how the IP routing protocol learns routes:
a. Change to global configuration mode:
SanJose(config-if)# exit
SanJose(config)#
c. Enable IP routing and set up a static route. Typically, the ISP does not provide
IP addresses and subnet masks of their networks, but they do provide the IP
address of the ISDN router interface to which your router is connected.
The following example specifies that you need to use dialer 0 on your router
to reach the ISP router. Dialer 0 had been previously configured using the
interface dialer command.
SanJose(config)# ip routing
SanJose(config)# ip route 0.0.0.0 0.0.0.0 192.168.1.1
SanJOse(config)# ip route 192.168.1.1 255.255.255.255 dialer0
Step 12 Perform this step only if ISDN calls at 64 kbps are not supported. Specify
characteristics of the outgoing calls from an ISDN interface by using the
following steps:
a. Define a class of shared configuration parameters for outgoing calls from an
ISDN interface:
SanJose(config)# map-class dialer 56k
Step 13 If you have a Cisco 800 series router that is connected to a telephone, fax machine,
or modem, configure the telephone interfaces by performing the following steps:
a. Change to global configuration mode:
SanJose(config-map-class)# exit
SanJose(config)#
Enter the pots country ? command to get a list of supported countries and
codes.
This command determines the physical characteristics of the telephone
interfaces. By specifying a country, you are configuring your telephone to use
country-specific default settings for each of the physical characteristics.
c. Create dial peers to determine how incoming calls are routed to the telephone
ports. In the following example, the dial-peer tag is 1, the ISDN local
directory number LDN is 5551111, the telephone port is 1, and call waiting
is disabled:
SanJose(config)# dial-peer voice 1 pots
SanJose(config-dial-peer)# destination-pattern 5551111
SanJose(config-dial-peer)# port 1
SanJose(config-dial-peer)# no call-waiting
SanJose(config-dial-peer)# exit
SanJose(config)#
Note Enter a number between 1 and 6 for the dial-peer tag variable.
Find out from your telephone service provider whether or not you
need to specify an area code for the LDN.
e. Specify that incoming voice calls shall be forwarded to the devices connected
to the telephone ports:
SanJose(config-if)# isdn incoming-voice modem
Step 15 In global configuration mode, set global NAT commands. In the following
example, all inside network addresses assigned to interface BRI0 are configured
for translation, and the access list that contains the inside network addresses is
defined.
SanJose(config)# ip nat inside source list 1 interface bri0
overload
SanJose(config)# access-list 1 permit 10.0.0.0 255.0.0.0
2
6
5
1
7
8
3
10.0.0.0 255.0.0.0
74930
4 9
192.168.1.100
Callout
Number Description
1 DHCP server at Site 1
2 National ISDN-1 switch type, with B1 SPID 40855511110101 and
B2 SPID 40855522220101
3 Public IP network
4 DHCP client
5 PPP link
6 ISDN phone number, 4085551111
7 Internet service provider
8 CHAP or PAP
9 Domain Name System (DNS) server
Features Used
This network uses the following features on the LAN:
• IP routing
• DHCP server (optional)
When your router is acting as a DHCP server, workstations configured as DHCP
clients are automatically assigned IP addresses and subnet masks.
This network uses the following features on the WAN:
• IP routing
• PPP
• IPCP (optional)
• CHAP or PAP over PPP
• DDR
• Static routes
If the ISP does not assign an IP address and subnet mask for your WAN interface,
you can use IPCP to automatically negotiate its IP address from the router to
which it is attempting to connect.
You can use either CHAP or PAP as the PPP authentication protocol. Cisco
recommends using CHAP because it is the more secure of the two protocols.
In addition, the ISDN line is activated only when needed (DDR), using one route
that has been manually configured (static route). DDR using static routes suits
small networking environments that do not have complex routing topologies.
Configuration
To configure the features for this network example, perform the following steps
on the PC, starting in the global configuration mode.
Step 1 Specify a name for the router. For example, specify SanJose as the router name:
router(config)# hostname SanJose
Step 3 Configure the router to recognize the zero subnet range as a valid range of
addresses:
SanJose(config)# ip subnet-zero
Step 4 Disable the router from translating unfamiliar words entered during a console
session into IP addresses:
SanJose(config)# no ip domain-lookup
b. Set an IP address and subnet mask for the LAN interface. For example, set the
IP address and subnet mask to 10.1.1.1 and 255.0.0.0, respectively:
SanJose(config-if)# ip address 10.1.1.1 255.0.0.0
c. Enable PPP:
SanJose(config-if)# encapsulation ppp
e. Create a dialer rotary group, specifying a number between 0 and 255. Dialer
rotary groups are useful in environments that require multiple calling
destinations. For example:
SanJose(config-if)# dialer rotary-group 0
f. North America only. Associate the ISDN local directory numbers (LDNs)
provided by your telephone service provider to the first and second SPIDs.
You can specify the SPID number or you can have it automatically detected
by entering a 0.
In the following example, the SPID number is represented by a 0 so that it
will be automatically detected. The primary LDN is followed by the
secondary LDN for each SPID.
SanJose(config-if)# isdn spid1 0 4085551111 4085552222
SanJose(config-if)# isdn spid2 0 4085553333 4085554444
Note Find out from your telephone service provider whether or not you
need to specify an area code for the LDN.
g. North America only. If you had manually entered the SPID number, enable
the BRI0 interface.
SanJose(config-if)# no shutdown
h. North America only. If you had specified the automatic detection of SPID
numbers, enable the automatic detection of ISDN SPID numbers and switch
type:
SanJose(config-if)# isdn autodetect
i. Outside of North America only. Specify the ISDN switch type. To see a listing
of supported switches, enter the isdn switch-type ? command.
The following example specifies the NET3 switch:
SanJose(config-if)# isdn switch-type basic-net3
Step 8 Follow these steps to specify characteristics of the dialer rotary group that you
created earlier:
a. Change to global configuration mode:
SanJose(config-if)# exit
SanJose(config)#
b. Create a dialer rotary group leader and specify a number between 0 to 255 to
represent your dialer rotary group. For example:
SanJose(config)# interface dialer 0
c. Set the IP address and subnet mask for the WAN interface provided by the
ISP. For example:
SanJose(config-if)# ip address 192.168.1.2 255.255.255.0
d. Optional. If the ISP did not provide an IP address and subnet mask for the
WAN interface, set up IPCP to obtain them from the router to which it is
connecting:
SanJose(config-if)# ip address negotiated
e. Enable PPP:
SanJose(config-if)# encapsulation ppp
f. Enable DDR:
SanJose(config-if)# dialer in-band
g. Specify the amount of time (in seconds) that the line can be idle before it is
disconnected. For example:
SanJose(config-if)# dialer idle-timeout 300
i. Set the number of packets to be held in the outgoing queue to 10. If an ISDN
connection does not exist yet, the hold-queue holds up to 10 packets before
dropping them. For example:
SanJose(config-if)# dialer hold-queue 10
j. Define the load level that must be exceeded on the first ISDN B channel
before the second B channel is brought up. The load-threshold variable
represents a utilization percentage and is a number between 1 and 255, where
255 equals 100 percent.
SanJose(config-if)# dialer load-threshold 10 outbound
Note Enter outbound to calculate the load using outbound data only,
inbound to calculate the load using inbound data only, and either to
set the maximum calculated load as the larger of the outbound and
inbound loads.
l. Enable CHAP and configure the CHAP hostname and password. To configure
PAP, skip this step, and go on to the next step.
This command enables CHAP and specifies authentication on incoming calls
only. Unidirectional authentication is used because non-Cisco routers that do
not support bidirectional authentication are potentially in use at the ISP. In
these cases, when SanJose calls the ISP, SanJose does not authenticate.
However, the ISP authenticates SanJose before allowing the connection. For
example:
SanJose(config-if)# ppp authentication chap callin
SanJose(config-if)# ppp chap hostname SanJose
SanJose(config-if)# ppp chap password gocisco1
m. Configure PAP. To configure CHAP, skip this step, and follow the previous
step.
SanJose(config-if)# ppp authentication pap callin
Step 9 Follow these steps to configure how the IP routing protocol learns the routes:
a. Change to global configuration mode:
SanJose(config-if)# exit
SanJose(config)#
Step 11 Perform this step only if ISDN calls at 64 kbps are not supported. Follow these
steps to specify the characteristics of outgoing calls from an ISDN interface. The
unique identifier for the class is 56k.
a. Define a class of shared configuration parameters for outgoing calls from an
ISDN interface:
SanJose(config)# interface dialer 0
SanJose(config-if)# dialer string 5551212 class 56k
SanJose(config-if)# exit
SanJose(config)# map-class dialer 56k
Step 12 If you have a Cisco 800 series router that is connected to a telephone, fax
machine, or modem, configure the telephone interfaces by performing the
following steps:
a. Specify the country where your router is located. For example:
SanJose(config)# pots country us
Note Enter a number between 1 and 6 for the dial-peer tag variable.
Find out from your telephone service provider whether or not you
need to specify an area code for the LDN.
d. Specify that incoming voice calls are forwarded to the devices connected to
the telephone ports:
SanJose(config-if)# isdn incoming-voice modem
2 6
1 7
5
3 8
10.1.0.0 10.2.0.0
74931
4 9
Callout
Number Description
1 Site 1
2 National ISDN-1 switch type, with B1 SPID 40855511110101 and
B2 SPID 40855522220101
3 IP network at Site 1
4 File server on Site 1 network
5 ISDN network connection
6 5ESS custom multipoint switch type, with B1 SPID
0155533330101 / B2 SPID 0155544440101
7 Site 2
Callout
Number Description
8 IP network at Site 2
9 File server at Site 2
Features Used
This network uses the following features on the LAN:
• IP routing (Cisco recommends this for management purposes, such as Telnet)
• DHCP server (optional)
When your router is acting as a DHCP server, workstations configured as DHCP
clients are automatically assigned an IP address and subnet mask.
This network uses the following features on the WAN:
• IP routing
• PPP
• IPCP
• CHAP or PAP over PPP
• DDR
• Static routes
With IPCP configured, your router automatically negotiates its IP address from
the router it is attempting to connect.
You can use either CHAP or PAP as the PPP authentication protocol. Cisco
recommends using CHAP because it is the more secure of the two protocols.
Because DDR is configured, the ISDN line is activated only when needed using
one route that has been manually configured (static route). Because a static route
is configured, the routers do not need to exchange routing updates. As a result, the
ISDN line is activated only when traffic demands.
Step 3 Specify the username of any client that will potentially dial into your router and
the password that your router and the client will share. Specify the username and
password of the central office router (the central office network administrator
should provide this information). For example:
SanJose(config)# username LosAngeles password gocisco1
c. Enable PPP:
SanJose(config-if)# encapsulation ppp
e. Create a dialer rotary group, specifying a number between 0 and 255. Dialer
rotary groups are useful in environments that require multiple calling
destinations. For example:
SanJose(config-if)# dialer rotary-group 0
f. North America only. Associate the ISDN local directory numbers (LDNs)
provided by your telephone service provider to the first and second SPIDs.
You can specify the SPID number or you can have it automatically detected
by entering a 0.
In the following example, the SPID number is represented by a 0 so that it
would be automatically detected. The primary LDN is followed by the
secondary LDN for each SPID.
SanJose(config-if)# isdn spid1 0 4085551111 4085552222
SanJose(config-if)# isdn spid2 0 4085553333 4085554444
Note Find out from your telephone service provider whether you need to
specify an area code for the LDN.
g. North America only. If you had entered the SPID number, enable the BRI0
interface.
SanJose(config-if)# no shutdown
i. Outside of North America only. Specify the ISDN switch type. To see a listing
of supported switches, enter the isdn switch-type ? command.
The following example specifies the NET3 switch:
SanJose(config-if)# isdn switch-type basic-net3
j. Disable CDP.
SanJose(config-if)# no cdp enable
Step 6 Specify the characteristics of the dialer rotary group that you created earlier by
performing the following steps:
a. Change to global configuration mode:
SanJose(config-if)# exit
SanJose(config)#
c. Enable PPP:
SanJose(config-if)# encapsulation ppp
d. Enable DDR:
SanJose(config-if)# dialer in-band
e. Specify the amount of time (in seconds) that the line can be idle before it is
disconnected. For example:
SanJose(config-if)# dialer idle-timeout 300
f. Set the number of packets to be held in the outgoing queue to 10. If an ISDN
connection does not exist yet, the hold-queue holds up to 10 packets before
dropping them. For example:
SanJose(config-if)# dialer hold-queue 10
g. Define the load level that must be exceeded on the first ISDN B channel
before the second B channel is brought up. The load-threshold variable
represents a utilization percentage and is a number between 1 and 255, where
255 equals 100 percent.
SanJose(config-if)# dialer load-threshold 150 outbound
Note Enter outbound to calculate the load using outbound data only,
inbound to calculate the load using inbound data only, and either to
set the maximum calculated load as the larger of the outbound and
inbound loads.
i. Configure CHAP. To configure PAP, skip this step, and go on to the next step.
This command enables CHAP and specifies authentication on incoming and
outgoing calls.
SanJose(config-if)# ppp authentication chap
j. Configure PAP. To configure CHAP, skip this step, and go to the previous
step. This command enables PAP and specifies authentication on incoming
and outgoing calls.
SanJose(config-if)# ppp authentication pap
Step 7 Perform this step only if ISDN calls at 64 kbps are not supported on your line.
Specify the characteristics of outgoing calls from an ISDN interface by
performing the following steps:
a. Define a class of shared configuration parameters for outgoing calls from an
ISDN interface:
SanJose(config)# interface dialer 0
SanJose(config-if)# dialer string 5551212 class 56k
SanJose(config-if)# exit
SanJose(config)# map-class dialer 56k
Step 8 If you have a Cisco 800 series router that is connected to a telephone, fax
machine, or modem, configure the telephone interface by performing the
following steps:
a. Specify the country where your router is located. For example:
SanJose(config)# pots country us
Note Find out from your telephone service provider whether you need to
specify an area code for the LDN.
d. Specify that incoming voice calls are forwarded to the devices connected to
the telephone ports:
SanJose(config-if)# isdn incoming-voice modem
IP Routing Configuration
To configure IP routing, perform the following steps on your PC:
Step 2 Configure the router to recognize the zero subnet range as a valid range of
addresses:
SanJose(config)# ip subnet-zero
Step 3 Disable the router from translating unfamiliar words entered during a console
session into IP addresses:
SanJose(config)# no ip domain-lookup
b. Set an IP address and subnet mask for the LAN interface. For example:
SanJose(config)# ip address 10.1.0.1 255.255.0.0
Step 5 Follow these steps to specify characteristics of the dialer rotary groups that were
created earlier:
a. Specify parameters for the dialer rotary group:
SanJose(config)# interface bri0
d. To configure the WAN interface to call a site or to receive calls from a site,
create a dialer map. In the following example, the same command is entered
twice, once for each dial string provided for the two B channels. The next hop
address is 10.3.1.2, and the host name is LosAngeles in both entries.
SanJose(config-if)# dialer map ip 10.3.1.2
name LosAngeles speed 56 14085553333
Step 6 Follow these steps to configure how the IP routing protocol learns the routes:
a. Change to global configuration mode:
SanJose(config-if)# exit
SanJose(config)#
c. Set up static routes. In the following example, the LosAngeles local network
is 10.2.0.0, the subnet mask is 255.255.0.0, and the router ISDN interface is
10.2.0.1:
SanJose(config)# ip route 10.2.0.0 255.255.0.0 10.2.1.2
Note You must configure the route to the LosAngeles network as well as
the route to the LosAngeles router ISDN interface. The route to the
LosAngeles router is through the dialer 0 port of the SanJose router.
Step 3 Specify the username of any client that will potentially dial in to your router and
the password that your router and the client will share. The following example
specifies SanJose and gocisco1 as the username and password:
LosAngeles# username SanJose password gocisco1
Step 4 Change to global configuration, then to interface configuration mode. Specify the
ISDN switch type. To get a listing of supported switches, enter the isdn
switch-type ? command.
LosAngeles# configure terminal
LosAngeles(config)# interface bri0
LosAngeles(config-if)# isdn switch-type basic-net3
b. Enable PPP:
LosAngeles(config-if)# encapsulation ppp
d. Create a dialer rotary group, specifying a number between 0 and 255. Dialer
rotary groups are useful in environments that require multiple calling
destinations. For example:
LosAngeles(config-if)# dialer rotary-group 0
e. North America only. Specify the SPID numbers assigned to your B channels,
using the isdn spid1 command for the B1 channel and the isdn spid2
command for the B2 channel. For example:
LosAngeles(config-if)# isdn spid1 0155533330101
LosAngeles(config-if)# isdn spid2 0155544440101
f. Disable CDP.
LosAngeles(config-if)# no cdp enable
Step 7 Specify characteristics of the dialer rotary group created earlier by following
these steps:
a. Change to global configuration mode:
LosAngeles(config-if)# exit
LosAngeles(config)#
c. Enable PPP:
LosAngeles(config-if)# encapsulation ppp
d. Enable DDR:
LosAngeles(config-if)# dialer in-band
e. Specify the amount of time (in seconds) that the line can be idle before it is
disconnected. For example:
LosAngeles(config-if)# dialer idle-timeout 300
Set the number of packets to be held in the outgoing queue to 10. In the
following example, if an ISDN connection does not exist yet, the hold queue
holds up to 10 packets before dropping them.
LosAngeles(config-if)# dialer hold-queue 10
f. Define the load level that must be exceeded on the first ISDN B channel
before the second B channel is brought up.The load variable represents a
utilization percentage and is a number between 1 and 255, where 255 is
100 percent.
LosAngeles(config-if)# dialer load-threshold 10 outbound
Note Enter outbound to calculate the load using outbound data only,
inbound to calculate the load using inbound data only, and either to
set the maximum calculated load as the larger of the outbound and
inbound loads.
g. Assign this interface to dialer access group 1. The dialer access group is
defined later in this procedure.
LosAngeles(config-if)# dialer-group 1
h. Configure CHAP. To configure PAP, skip this step, and go to step i. This
command enables CHAP and specifies authentication on incoming and
outgoing calls.
LosAngeles(config-if)# ppp authentication chap
IP Routing Configuration
To configure IP routing, perform the following steps on the PC connected to the
other router.
b. Set an IP address and subnet mask for the LAN interface. For example:
LosAngeles(config)# ip address 10.2.0.1 255.255.0.0
Step 5 Follow these steps to specify characteristics of the dialer rotary group that were
created earlier:
a. Change to global configuration mode:
LosAngeles(config-if)# exit
LosAngeles(config)#
d. To configure the WAN interface to call a site or to receive calls from a site,
create a dialer map in global configuration mode.
In this example, this command is entered twice, once for each B channel. The
next hop address is 10.3.1.1, the host name is SanJose, and the dial strings are
408555111100 and 408555222200:
LosAngeles(config-if)# exit
LosAngeles(config)# dialer map ip 10.3.1.1 name SanJose
speed 56 408555111100
LosAngeles(config)# dialer map ip 10.3.1.1 name SanJose
speed 56 408555222200
Step 6 Follow these steps to configure how the IP routing protocol learns routes:
a. Change to global configuration mode:
LosAngeles(config-if)# exit
LosAngeles(config)#
c. Set up static routes. In the following example, the destination (San Jose)
network is 10.1.0.0, the subnet mask is 255.255.0.0, and the San Jose router
ISDN interface is 10.3.1.1.
LosAngeles(config)# ip route 10.1.0.0 255.255.0.0 10.3.1.1
Note You must configure the route to the San Jose network as well as the
route to the San Jose router ISDN interface. The route to the San Jose
router is through the dialer 0 port of the LosAngeles router.
Step 7 Specify that dialer list 1 permits dialing by the IP routing protocol:
LosAngeles(config)# dialer-list 1 protocol ip permit
Cisco recommends that you familiarize yourself with the features in the
configuration examples to help you decide which features you wish to include in
your network.
Note Certain protocols (IP, User Datagram Protocol [UDP], and Network Time
Protocol [NTP]) send updates that can cause an ISDN line to be activated
excessively. For information on preventing this situation, refer to the “Controlling
the DDR ISDN Line Activation” section on page 3-27.
Step 1 Order your ISDN line from your telephone service provider. For complete
information on ordering your ISDN line, see Appendix D, “Provisioning an ISDN
Line.”
Step 2 While ordering your ISDN line, gather the following information from your
telephone service provider:
• ISDN switch type.
• Service profile identifiers (SPIDs). In North America only, telephone service
providers assign SPIDs. SPIDs identify the ISDN B channels. The SPID
format is generally an ISDN telephone number with additional numbers, such
as 40855522220101. Depending on the switch type that supports your ISDN
line, your ISDN line could be assigned zero, one, or two SPIDs.
• ISDN local directory numbers (LDNs), which are the local ISDN telephone
numbers of your routers, such as 4085552222 and 5553333.
Note The format of the LDN varies from region to region, depending on the
telephone service provider. In some regions, you need to add the area
code to the telephone number. Find out from your local telephone
service provider whether or not you need to specify an area code for
the LDN.
Step 3 If you are setting up an Internet connection, gather the following information from
your Internet service provider (ISP):
• PPP client name that the ISP assigns as your login name
• PPP authentication type, either Challenge Handshake Authentication
Protocol (CHAP) or Password Authentication Protocol (PAP)
• PPP password to access your ISP account
• IP address information: the IP address and subnet mask of the ISP ISDN
interface
• ISP telephone number
Step 4 If you are setting up a connection to a corporate network, you and the network
administrator of the corporate network must decide on or generate the following
information for the WAN interfaces of your routers and share this information:
• PPP authentication type, either CHAP or PAP
• PPP client name to access the router
• PPP password to access the router
• Telephone number assigned to the telephone interface of your router
Step 5 If you are setting up IP routing, collect information on the addressing scheme for
your IP network.
10.0.0.0
1 2
800
3 4
3600
74932
5
Table 3-1 Key for Connecting Private IP Network to Internet and Corporate
Network
Callout
Number Description
1 Private network
2 Site 1
3 ISDN
4 Internet service provider
5 Site 2
Features Used
This network uses the following features on the LAN:
• IP routing
• DHCP server (optional)
When your router is acting as a DHCP server, workstations configured as DHCP
clients are automatically assigned an IP address and subnet mask.
This network uses the following features on the WAN:
• IP routing
• PPP
• NAT overload
• Internet Protocol Control Protocol (IPCP)
• CHAP or PAP over PPP
With NAT overload configured, your router can use one address for multiple
hosts. With IPCP configured, your router can automatically negotiate its IP
address from the router it is attempting to connect to.
You can use CHAP or PAP as the PPP authentication protocol. Cisco recommends
using CHAP, because it is more secure.
For the ISDN connection, you can use one of the following options:
• DDR using snapshot routing (the ISDN line is activated only when needed)
• Permanent ISDN line lease
For complete information on these options, including how to configure them, see
the “Configuring the ISDN Line” section on page 3-19.
The IP routing protocol can use either RIP or EIGRP to learn routes dynamically.
You can also use triggered extensions to RIP to control when RIP sends routing
updates. For information on how to configure these options, see the “Configuring
Dynamic Routing” section on page 3-23.
Note Before you begin to configure your router, review the “Before Configuring
Advanced Networks or Features” section on page 3-2.
Starting from global configuration mode, follow these steps to configure the
Cisco 800 series router in the private IP network to connect to the Internet and the
corporate network. For more information on the commands used, refer to the
Cisco IOS documentation.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# hostname c804 Enter the router name.
Step 3 c804(config)# enable secret 804password Enter the password.
Step 4 c804(config)# pots country us Optional. If you have a Cisco 803 router that
is connected to telephones, fax machines, or
modems, specify the country where your
router is located. Specifying a country
configures the country-specific default
settings for each physical characteristic.
Step 5 c804(config)# interface bri0 Change to interface configuration mode, set
the ISDN switch type, and return to global
c804(config-if)# isdn switch-type basic-ni
configuration mode.
c804(config-if) exit
Step 6 c804(config)# ip subnet-zero Set the router to recognize the zero subnet
range as a valid range of addresses.
Step 7 c804(config)# ip dhcp pool Optional. Configure your router as a DHCP
DHCPpoolLAN_0 server. This step specifies the DHCP relay
pool name.
Step 8 c804(dhcp-config)# network 10.0.0.0 For configuring DHCP only. Set the DHCP
255.255.255.0 pool of addresses.
Step 9 c804(dhcp-config)# dns-server For configuring DHCP only. Set the IP
192.168.1.100 address of the DNS server.
Command Purpose
Step 10 c804(dhcp-config)# netbios-name-server For configuring DHCP only. Set the NetBIOS
10.1.1.2 10.1.1.3 servers.
Step 11 c804(dhcp-config)# default-router 10.1.1.1 For configuring DHCP only. Set the Ethernet
0 IP address as the default gateway.
Step 12 c804(dhcp-config)# exit For configuring DHCP only. Exit to global
configuration mode.
Step 13 c804(config-if)# ip address 10.0.0.1 Enter the IP address and subnet mask.
255.255.255.0
Step 14 c804(config-if)# ip nat inside Enable Network Address Translation (NAT)
on your LAN; then change to global
c804(config-if)# exit
configuration mode.
Step 15 c804(config)# interface bri0 Change to interface configuration mode for
BRI0.
Step 16 c804(config-if)# encapsulation ppp Enable PPP.
Step 17 c804(config-if)# isdn incoming-voice Optional. Specify that incoming voice calls
modem are forwarded to the devices connected to the
telephone ports.
Step 18 c804(config-if)# ppp authentication pap Enable PAP or CHAP on incoming calls only.
chap callin
Step 19 c804(config-if)# ppp chap hostname c804 For CHAP only. Define the router hostname
and password to authenticate.
c804(config-if)# ppp chap password
804password
Step 20 c804(config-if)# ppp multilink Enable multilink PPP.
Step 21 c804(config-if)# ip nat outside Configure a valid Internet address to which
the inside network address will be translated,
c804(config-if)# exit
then change to global configuration mode.
Step 22 c804(config)# interface dialer1 Create a dialer interface.
Step 23 c804(config-if)# ip unnumbered ethernet0 Specify that no specific IP addresses are
assigned for Ethernet 0.
Step 24 c804(config-if)# encapsulation ppp Enable PPP.
Step 25 c804(config-if)# dialer remote-name Specify the name of the corporate router.
corp_router
Command Purpose
Step 26 c804(config-if)# dialer pool 1 Assign a dialer pool.
Step 27 c804(config-if)# dialer idle-timeout 300 Specify the time in seconds that the line is idle
before it is disconnected.
Step 28 c804(config-if)# dialer string 7771111 Set up the dialer string.
Step 29 c804(config-if)# dialer hold-queue 10 Specify the maximum number of packets to
be held in the outgoing queue.
Step 30 c804(config-if)# dialer load-threshold 150 Define the load level that must be exceeded on
either the first ISDN B channel before the second B
channel is brought up. The load-threshold
variable is a number from 1 to 255
representing a utilization percentage.
Enter outbound to calculate the load using
outbound data only, inbound to use inbound
data only, and either to set the maximum load
as the larger of the two loads.
Step 31 c804(config-if)# dialer-group 1 Assign the interface to dialer access group 1.
Step 32 c804(config-if)# ppp authentication chap Configure CHAP and PAP to authenticate
pap callin incoming calls.
Step 33 c804(config-if)# ppp chap hostname c804 Specify the CHAP host name and password.
c804(config-if)# ppp chap password
804password
Step 34 c804(config-if)# ppp pap sent-username Specify the PAP username and password.
c804 password 804password
Step 35 c804(config)# interface dialer2 Create a second dialer interface.
Step 36 c804(config-if)# ip address negotiated Specify that IP addresses are negotiated.
Step 37 c804(config-if)# encapsulation ppp Enable PPP.
Step 38 c804(config-if)# dialer remote-name isp Specify the name of the corporate router.
Step 39 c804(config-if)# dialer pool 2 Assign a dialer pool.
Step 40 c804(config-if)# dialer idle-timeout 300 Specify the time in seconds that the line is idle
before it is disconnected.
Step 41 c804(config-if)# dialer string 18001234567 Set up the dialer string.
Command Purpose
Step 42 c804(config-if)# dialer hold-queue 10 Specify the maximum number of packets to
be held in the outgoing queue.
Step 43 c804(config-if)# dialer load-threshold 150 Define the load level that must be exceeded on
either the first ISDN B channel before the second B
channel is brought up. The load-threshold
variable is a number from 1 to 255
representing a utilization percentage.
Enter outbound to calculate the load using
outbound data only, inbound to use inbound
data only, and either to set the maximum load
as the larger of the two loads.
Step 44 c804(config-if)# dialer-group 1 Assign the interface to dialer access group 1.
Step 45 c804(config-if)# ppp authentication chap Configure CHAP and PAP to authenticate
pap callin incoming calls.
Step 46 c804(config-if)# ppp chap hostname Specify the CHAP username and password.
generic user
c804(config-if)# password user pass
Step 47 c804(config-if)# ppp pap sent-username Specify the PAP username and password.
generic_user password user pass
Step 48 c804(config-if)# ppp multilink Enable multilink PPP.
Step 49 c804(config-if)# exit Change to global configuration mode.
Step 50 c804(config)# access-list 1 permit 10.0.0.1 Specify an access list and a dialer list to
255.255.255.0 control IP traffic.
c804(config)# dialer-list 1 protocol ip
permit
Step 51 c804(config)# ip route 10.1.0.0 255.255.0.0 Add a default route and interface.
bri0
Step 52 c804(config)# dial-peer voice 1 pots Create a dial peer to determine how incoming
calls are routed to the telephone port 1.
c804(config-dial-peer)# destination-pattern
5551212
c804(config-dial-peer)# port 1
Step 53 c804(config-dial-peer)# exit Return to global configuration mode.
Command Purpose
Step 54 c804(config)# dial-peer voice 2 pots Create a second dial peer for the telephone
port 2.
c804(config-dial-peer)# destination-pattern
5551313
c804(config-dial-peer)# port 2
Step 55 c804(config-dial-peer)# exit Change to global configuration mode.
Step 56 c804(config)# ip nat inside source list 1 Set global NAT commands. In this example,
interface bri0 overload all inside network addresses assigned to
interface BRI0 are configured for translation,
c804(config)# access-list 1 permit 10.0.0.0
and the access list that contains the inside
0.0.0.255
network addresses is defined.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# hostname 3600 Specify a name for the router.
Step 3 3600(config)# enable secret secret Set an encrypted password to gain access to
privileged EXEC mode commands.
Step 4 3600(config)# username c800 password Specify the username and password of the
c800 pass Cisco 800 series router.
Step 5 3600(config)# ip subnet-zero Set router to recognize the zero subnet range
as a valid range of addresses.
Step 6 3600(config)# no ip domain-lookup Disable router from translating unfamiliar
words entered during a console session into IP
addresses.
Command Purpose
Step 7 3600(config)# ip dhcp pool Optional. Configure your router as a DHCP
DHCPpoolLAN_1 server. This step specifies the DHCP relay
pool name.
Step 8 3600(dhcp-config)# network 192.168.1.0 For configuring DHCP only. Set the DHCP
255.255.255.0 pool of addresses.
Step 9 3600(dhcp-config)# dns-server 192.168.1.2 For configuring DHCP only. Set the IP
address of the DNS server.
Step 10 3600(dhcp-config)# netbios-name-server For configuring DHCP only. Set the NetBIOS
192.168.1.11 192.168.1.12 servers.
Step 11 3600(dhcp-config)# default-router For configuring DHCP only. Set the Ethernet
192.168.1.1 0 IP address as the default gateway.
Step 12 3600(dhcp-config)# exit For configuring DHCP only. Exit to global
configuration mode.
Step 13 3600(config)# ip local pool POOL1 Set a local pool of IP addresses to be used
192.168.1.10 192.168.1.20 when Cisco 800 series router attempts to
connect.
Step 14 3600(config)# interface e0 Change to interface configuration mode for
Ethernet 0.
Step 15 3600(config-if)# ip address 192.168.1.1 Set IP address and subnet mask for the
255.255.255.0 Ethernet interface, then return to global
configuration mode.
3600(config-if)# exit
Step 16 3600(config)# interface bri0 Change to interface configuration mode for
3600(config-if)# isdn switch-type basic-net3 BRI0 and specify the ISDN switch type.
Step 17 3600(config-if)# encapsulation ppp Enable PPP.
Step 18 3600(config-if)# isdn spid1 0155533330101 North America only. Specify SPID numbers
3600(config-if)# isdn spid2 0155544440101 assigned to B channels by telephone service
provider.
Step 19 3600(config-if)# peer default ip address Specify address from a particular IP address
pool POOL1 pool be returned to the connected router. Use
pool name specified in ip local pool
command.
Command Purpose
Step 20 3600(config-if)# ppp authentication chap Enable PAP or CHAP and specify
callin authentication in incoming calls only.
or
3600(config-if)# ppp authentication pap
callin
Step 21 3600(config-if)# ppp multilink Enable multilink PPP.
Step 22 3600(config-if)# no cdp enable Disable CDP.
Step 23 3600(config-if)# exit Change to global configuration mode, and set
IP addresses to be treated as classless.
3600(config)# ip classless
3600
3
2
800
1
3600
74933
Table 3-2 Key for Connecting Remote Network to Two Corporate Networks
Callout
Number Description
1 Site 1
2 ISDN network
3 Site 2
4 Site 3
Features Used
This network uses the following features on the LAN:
• IP routing (Cisco recommends for management purposes, such as Telnet)
• DHCP server (optional)
When your router is acting as a DHCP server, workstations configured as DHCP
clients are automatically assigned an IP address and subnet mask.
This network uses the following features on the WAN:
• IP routing
• PPP
• NAT overload
• IPCP
• CHAP or PAP over PPP
With NAT overload configured, your router can use one address for multiple
hosts. With IPCP configured, your router can automatically negotiate its IP
address from the router it is attempting to connect to.
You can use either CHAP or PAP as the PPP authentication protocol. Cisco
recommends using CHAP because it is the more secure of the two protocols.
For the ISDN connection, you can use one of the following options:
• DDR using snapshot routing (the ISDN line is activated only when needed)
• Permanently leased ISDN line
For complete information on these options, including how to configure them, see
the “Configuring the ISDN Line” section on page 3-19.
The IP routing protocol can use either RIP or EIGRP to learn routes dynamically.
You can use either one of these options. You can also use triggered extensions to
RIP to control when RIP sends routing updates. For information on how to
configure these options, see the “Configuring Dynamic Routing” section on
page 3-23.
Note Before you begin to configure your router, review the “Before Configuring
Advanced Networks or Features” section on page 3-2 .
Starting from global configuration mode, follow these steps to configure the
Cisco 800 series router in the remote network to two corporate networks. For
information on the commands used in this table, refer to the Cisco IOS
documentation.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# hostname c804 Enter the router name.
Step 3 c804(config)# enable secret 804password Enter the password.
Step 4 c804(config)# pots country us Optional. If you have a Cisco 803 or 804
router that are connected to telephones, fax
machines, or modems, specify the country
where your router is located. Specifying a
country configures the country-specific
default settings for each physical
characteristic.
Step 5 c804(config)# ip subnet-zero Set the router to recognize the zero subnet
range as a valid range of addresses.
Step 6 c804(config)# ip dhcp pool Optional. Configure your router as a DHCP
DHCPpoolLAN_0 server. In this step, specify the DHCP relay
pool name.
Command Purpose
Step 7 c804(dhcp-config)# network 192.168.1.0 Optional. Set the DHCP pool of addresses.
255.255.255.0
Step 8 c804(dhcp-config)# dns-server 172.29.20.41 For DHCP configuration only. Set the IP
172.29.20.51 address of the DNS servers.
Step 9 c804(dhcp-config)# netbios-name-server For DHCP configuration only. Set the
172.29.20.41 172.29.20.51 NetBIOS servers.
Step 10 c804(dhcp-config)# default-router For DHCP configuration only. Set the
192.168.1.1 Ethernet 0 IP address as the default gateway.
Step 11 c804(dhcp-config)# exit For DHCP configuration only. Exit to global
configuration mode.
Step 12 c804(config)# interface ethernet0 Change to the Ethernet interface
configuration mode.
Step 13 c804(config-if)# ip nat inside Enable NAT on the inside network.
Step 14 c804(config-if)# ip address 192.168.2.2 Assign the IP addresses for Ethernet 0; then
255.255.255.0 change to global configuration mode.
c804(config-if)# exit
Step 15 c804(config)# interface dialer1 Create a dialer interface.
Step 16 c804(config-if)# encapsulation ppp Enable PPP.
Step 17 c804(config-if)# dialer remote-name corp1 Specify the name of the corporate router.
Step 18 c804(config-if)# dialer pool 1 Assign a dialer pool.
Step 19 c804(config-if)# dialer idle-timeout 300 Specify the time, in seconds, that the line is
idle before it is disconnected.
Step 20 c804(config-if)# dialer string 7771111 Set up the dialer string.
Step 21 c804(config-if)# dialer hold-queue 10 Specify the maximum number of packets to
be held in the outgoing queue.
Step 22 c804(config-if)# dialer-group 1 Assign the interface to dialer access group 1.
Step 23 c804(config-if)# ppp authentication chap Configure CHAP and PAP to authenticate
pap callin incoming calls.
Step 24 c804(config-if)# ppp chap hostname c804 Specify the CHAP host name.
Step 25 c804(config-if)# ppp chap password Specify the CHAP password.
804password
Command Purpose
Step 26 c804(config-if)# ppp pap sent-username Specify the PAP username and password.
c804 password 804password
Step 27 c804(config)# interface dialer2 Create a second dialer interface.
Step 28 c804(config-if)# ip address 192.168.3.1 Assign the IP addresses for Ethernet 0.
255.255.255.0
Step 29 c804(config-if)# encapsulation ppp Enable PPP.
Step 30 c804(config-if)# dialer remote-name corp2 Specify the name of the corporate router.
Step 31 c804(config-if)# dialer pool 1 Assign a dialer pool.
Step 32 c804(config-if)# dialer idle-timeout 300 Specify the time in seconds that the line is idle
before it is disconnected.
Step 33 c804(config-if)# dialer string 7772222 Set up the dialer string.
Step 34 c804(config-if)# dialer hold-queue 10 Specify the maximum number of packets to
be held in the outgoing queue.
Step 35 c804(config-if)# dialer-group 2 Assign the interface to a dialer access group.
Step 36 c804(config-if)# ppp authentication chap Configure CHAP and PAP to authenticate
pap callin incoming calls.
Step 37 c804(config-if)# ppp chap hostname c804 Specify the CHAP host name.
Step 38 c804(config-if)# ppp chap password Specify the CHAP password.
804password
Step 39 c804(config-if)# ppp pap sent-username Configure PAP username and password.
c804 password 804password
Step 40 c804(config-if)# exit Change to global configuration mode.
c804(config)#
Step 41 c804(config)# dialer-list 1 protocol ip Specify dialer-list protocol permissions.
permit
c804(config) dialer-list 2 protocol ip permit
Step 42 c804(config)# interface bri0 Change to the interface BRI0 configuration
mode and set the ISDN switch type.
c804(config-if)# isdn switch-type basic-ni
Step 43 c804(config-if)# ip address 192.168.1.1. Enter the IP address and subnet mask.
255.255.255.0
Command Purpose
Step 44 c804(config-if)# ip nat outside Configure a valid Internet address to which
the inside network address will be translated.
Step 45 c804(config-if)# encapsulation ppp Enable PPP.
Step 46 c804(config-if)# dialer rotary-group 1 Create dialer rotary groups 1 and 2,
specifying a number between 0 and 255 for
c804(config-if)# dialer rotary-group 2
each.
Step 47 c804(config-if)# isdn spid1 0 4085551212 North America only. Associate the ISDN
LDNs provided by your telephone service
c804(config-if)# isdn spid2 0 4085551313
provider to the first and second SPIDs, and
configure the SPID numbers to be
automatically detected.
Step 48 c804(config-if)# ppp authentication pap Enable PAP or CHAP for incoming data.
chap callin
Step 49 c804(config-if)# isdn incoming-voice Specify that voice calls are forwarded to the
modem devices connected to the analog telephone
ports.
Step 50 c804(config-if)# exit Change to global configuration mode.
Step 51 c804(config)# dial-peer voice 1 pots Create a dial peer to determine how incoming
calls are routed to the telephone port 1.
c804(config-dial-peer)# destination-pattern
5551212
c804(config-dial-peer)# port 1
Step 52 c804(config-dial-peer)# exit Return to global configuration mode.
Step 53 c804(config)# dial-peer voice 2 pots Create a second dial peer to determine how
incoming calls are routed to the telephone
c804(config-dial-peer)# destination-pattern
port 2.
5551313
c804(config-dial-peer)# port 2
Step 54 c804(config-dial-peer)# exit Change to global configuration mode.
Step 55 c804(config)# ip nat inside source list 1 Set global NAT commands. In this example,
interface bri0 overload all inside network addresses assigned to
interface BRI0 are configured for translation,
c804(config)# access-list 1 permit
and the access list that contains the inside
192.168.1.0 0.0.0.255
network addresses is defined.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# hostname 3600 Define the corporate router hostname.
Step 3 3600(config)# enable secret secret Enter an encrypted password to gain access to
privileged EXEC mode commands.
Step 4 3600(config)# username c800 password Specify the username and password of the
c800_pass Cisco 800 series router.
Step 5 3600(config)# ip subnet-zero Set router to recognize the zero subnet range
as a valid range of addresses.
Step 6 3600(config)# no ip domain-lookup Disable router from translating unfamiliar
words entered during a console session into IP
addresses.
Step 7 3600(config)# ip local pool POOL1 1.1.2.1 Set a local pool of IP addresses to be used
1.1.2.7 when the Cisco 800 series router attempts to
connect. Define the pool name and the range
of IP addresses in the pool.
Step 8 3600(config)# ip dhcp pool Optional if configuring your router as a
DHCPpoolLAN_1 DHCP server. If DHCP is not being
configured, go to step 14.
This step specifies the DHCP relay pool
name.
Step 9 3600(dhcp-config)# network 1.1.2.0 For configuring DHCP only. Set the DHCP
255.255.255.0 pool of addresses.
Step 10 3600(dhcp-config)# dns-server 1.1.2.2 For configuring DHCP only. Set the IP
address of the DNS server.
Step 11 3600(dhcp-config)# netbios-name-server For configuring DHCP only. Set the NetBIOS
1.2.2.2 1.2.2.3 servers.
Command Purpose
Step 12 3600(dhcp-config)# default-router 1.1.2.1 For configuring DHCP only. Set the Ethernet
0 IP address as the default gateway.
Step 13 3600(dhcp-config)# exit For configuring DHCP only. Exit to global
configuration mode.
Step 14 3600(config)# ip address 1.1.1.1 Set IP address and subnet mask.
255.255.255.0
Step 15 3600(config)# interface bri0 Change to interface configuration mode for
BRI0 and specify ISDN switch type.
3600(config-if)# isdn switch-type basic-net3
Step 16 3600(config-if)# encapsulation ppp Enable PPP.
Step 17 3600(config-if)# isdn spid1 0155533330101 North America only. Specify SPID numbers
3600(config-if)# isdn spid2 0155544440101 assigned to B channels by telephone service
provider.
Step 18 3600(config-if)# peer default ip address Specify address from a particular IP address
pool POOL1 pool be returned to the connected router. Use
pool name specified in ip local pool
command.
Step 19 3600(config-if)# ppp authentication chap Enable PAP or CHAP.
or
3600(config-if)# ppp authentication pap
Step 20 3600(config-if)# ppp multilink Enable multilink PPP.
Step 21 3600(config-if)# no cdp enable Disable CDP.
Step 22 3600(config-if)# exit Change to global configuration mode.
Step 23 3600(config)# ip classless Set the IP addresses to be treated as classless.
Note Some protocols (IP, UDP, and NTP) send updates that can cause an ISDN line to
be activated excessively. For information on preventing this situation, see the
“Controlling the DDR ISDN Line Activation” section on page 3-27.
Configuration
Starting from interface configuration mode, follow these steps to configure DDR
using snapshot routing. For information on the commands used in this
configuration, refer to the Cisco IOS documentation.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode. Then enter
interface configuration mode.
router(config)# interface bri0
Step 2 router(config-if)# dialer rotary-group 1 Create a dialer rotary-group, useful in
environments that require multiple calling
destinations. Only the rotary-group needs to
be configured with dialer map commands.
Step 3 router(config-if)# interface dialer 0 Create a dialer rotary-group leader.
Step 4 router(config-if)# ppp multilink Enable multilink PPP.
Step 5 router(config-if)# dialer in-band Enable DDR.
Step 6 router(config-if)# dialer idle-timeout 150 Specify the amount of time that the line is idle
before it is disconnected.
Step 7 router(config-if)# dialer hold-queue 10 Set number of packets held in outgoing
queue.
Command Purpose
Step 8 router(config-if)# dialer load-threshold 150 Define the load level that must be exceeded on
either first ISDN B channel before the second B
channel is brought up, and whether the load
level is defined for inbound or outbound
traffic, or for either type.
Step 9 router(config-if)# dialer-group 2 Assign interface to dialer access group.
Step 10 router(config-if)# dialer-list 2 protocol ip Define the traffic types that trigger and
permit sustain an ISDN call on interfaces sharing the
same dialer-group number.
Step 11 router(config-if)# map-class dialer class1 Optional. Define a class of shared
configuration parameters for outgoing calls.
Step 12 router(config-map-class)# dialer isdn speed Optional. If 64-kbps calling is not supported,
56 enter 56 kbps as speed for the B channel.
Step 13 router(config-map-class)# exit Change to global configuration. Then change
to interface configuration mode for BRI0.
router(config)# interface bri0
Step 14 router(config-if)# dialer map 3.3.3.3 name Create a dialer map used by the WAN
name1 5551000 interface.
Step 15 router(config-if)# exit Change to global configuration mode. Then
change to interface configuration for dialer 0.
router(config)# interface dialer0
Step 16 router(config-if)# snapshot server 5 Set up one of the following options for
snapshot routing:
or
• A server router and the active time
router(config-if)# snapshot client 5
interval, in minutes (from 5 to 1000)
• A client router, the active time interval, in
minutes (from 5 to 1000), and the quiet
time interval, in minutes (from 8 to
100,000)
Step 17 router(config-if)# exit Change to global configuration mode. Then
change to interface configuration for BRI0.
router(config)# interface bri0
Step 18 router(config-if)# dialer map snapshot 2 Define a dialer map for snapshot routing on a
5551000 client router connected to a DDR interface.
Command Purpose
Step 1 router# isdn call interface bri0 5551000 Initiate the data call and specify the interface
and dial string.
Step 2 router# isdn disconnect interface bri0 all Disconnect the data call without bringing
down the interface.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# isdn leased-line bri0 128 Configure the BRI interface to use the ISDN
physical connection as a leased-line service.
Select one of the following line speeds:
• 128 combines the two B channels at
128 kbps. Offered in Japan only.
• 144 combines the two B channels and D
channel at 144 kbps.
Command Purpose
Step 1 router(config)# router rip Enable the RIP routing process.
Step 2 router(config-router)# network Associate a network with the RIP routing
network-number process.
Step 3 router(config-router)# version Set the software to receive and send only
{1 | 2} RIP version 1 or only RIP version 2
packets.
2 4
1 5
3
800 3600
74934
10.1.1.1 20.1.1.1
Callout
Number Description
1 NT client
2 Network A
3 ISDN
4 Network B
5 NT server
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# interface bri0 Change to interface configuration mode for
BRI0.
Step 3 router(config-if)# ip Set the router to forward UDP broadcasts,
helper-address address including broadcasts of IP addresses and IP
configuration requests to the NT server.
Note By default, eight other UDP ports, including 137 (NetBIOS name server) and 138
(NetBIOS datagram service), are enabled. For more information, refer to the
Cisco IOS documentation.
3
800 3600
2
74935
1 4
Table 3-4 Key for DHCP Relay
Callout
Number Description
1 DHCP client
2 DHCP relay
3 ISDN network
4 DHCP server
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# ip dhcp-server Specify which DHCP server to use on your
ip-address network.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# interface bri0 Change to interface configuration mode for
the WAN interface.
Step 3 router(config-if)# dialer-group 1 Create a dialer list.
Step 4 router(config-if)# exit Return to global configuration mode.
Step 5 router(config)# access-list 100 Set NetBIOS name service packets not to
deny udp any any eq netbios-nm activate the ISDN line.
Step 6 router(config)# access-list 100 Set NetBIOS datagram service packets not
deny udp any any eq to activate the ISDN line.
netbios-dgm
Step 7 router(config)# access-list 100 Permit all other IP traffic.
permit ip any any
Step 8 router(config)# dialer-list 1 Set IP packets to activate the ISDN line.
protocol ip list 100
Configuration
Starting in global configuration mode, use the following steps to configure an
extended access list so that UDP broadcasts do not activate the ISDN line. For
more information on the commands listed, refer to the Cisco IOS documentation.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# interface bri0 Change to interface configuration mode for
the WAN interface.
Step 3 router(config-if)# dialer-group 1 Create a dialer list.
Step 4 router(config-if)# exit Return to global configuration mode.
Step 5 router(config)# access-list 100 deny udp any Set location services packets not to activate
any eq 135 the ISDN line.
Step 6 router(config)# access-list 100 permit ip any Permit all other IP traffic.
any
Step 7 router(config)# dialer-list 1 protocol ip list Set IP packets to activate the ISDN line.
100
Configuration
Starting in global configuration mode, use the following steps to configure an
extended access list so that UDP broadcasts associated with NTP do not activate
the ISDN line. For more information on the commands listed, refer to the
Cisco IOS documentation.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# interface bri0 Specify parameters for the WAN interface.
Step 3 router(config-if)# dialer-group 1 Create a dialer list.
Step 4 router(config-if)# exit Return to global configuration mode.
Step 5 router(config)# access-list 100 deny udp any Set NTP packets not to activate the ISDN line.
any eq ntp
Step 6 router(config)# access-list 100 permit ip any Permit all other IP traffic.
any
Step 7 router(config)# dialer-list 1 protocol ip list Specify that extended access list 100 defines
100 which IP packets activate the ISDN line.
IP Traffic
You can configure an extended access list so that IP broadcasts, including RIP and
EIGRP broadcasts, do not activate the ISDN line. An extended access list controls
packets. When defining this list, you can specify complex addresses and permit or
deny specific protocols.
Configuration
Starting in global configuration mode, use the following steps to configure an
extended access list so that IP packets do not activate the ISDN line. For more
information on the commands listed, refer to the Cisco IOS documentation.
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# interface bri0 Change to interface configuration mode for
the WAN interface.
Step 3 router(config-if)# dialer-group 1 Create a dialer list.
Step 4 router(config-if)# exit Return to global configuration mode.
Command Purpose
Step 5 router(config)# access-list 100 deny eigrp Set EIGRP packets not to activate the ISDN
any any line.
Step 6 router(config)# access-list 100 deny udp any Set RIP packets not to activate the ISDN line.
any eq rip
Step 7 router(config)# access-list 100 permit ip any Allow other packets to activate the ISDN line.
any
Note This network example and extended access list include commonly anticipated
restrictions. The information in this section is meant to be used as a base from
which you can add or delete restrictions as they relate to your particular network.
The extended access list that you create depends on your particular network.
5
1
192.168.1.2
192.168.1.1 10.0.0.1 4
800
10.0.0.3
2
192.168.1.3
74936
3
192.168.1.4
Callout
Number Description
1 SMTP mail server
2 Web server
3 FTP server
4 Internet service provider
5 DNS server
Command Purpose
Step 1 router# configure terminal Enter global configuration mode.
Step 2 router(config)# interface bri0 Change to interface configuration mode for
the WAN interface.
Step 3 router(config-if)# dialer-group 1 Create a dialer list.
Step 4 router(config-if)# exit Return to global configuration mode.
Command Purpose
Step 5 router(config)# access-list 100 permit tcp Permit any host on the specified network to
any 192.168.1.0 0.0.0.255 established access any Internet host if it has an
established connection.
Step 6 router(config)# access-list 100 deny ip any Prevent IP spoofing using the specified
192.168.1.0 0.0.0.255 any network.
Step 7 router(config)# access-list 100 permit tcp Permit the DNS server to send TCP replies to
host 10.0.0.3 192.168.1.0 0.0.0.255 eq the specified network.
domain
Step 8 router(config)# access-list 100 permit udp Permit the DNS server to send UDP replies to
host 10.0.0.3 192.168.1.0 0.0.0.255 eq the specified network.
domain
Step 9 router(config)# access-list 100 permit tcp Permit any host to access the mail server
any host 192.168.1.2 eq smtp through SMTP.
Step 10 router(config)# access-list 100 permit tcp Permit any host to access the mail server
any host 192.168.1.3 eq www through HTTP.
Step 11 router(config)# access-list 100 permit tcp Allow access to the FTP server from any
any host 192.168.1.4 eq ftp Internet host through FTP.
Step 12 router(config)# access-list 100 deny tcp any Restrict any Internet host from making a
192.168.1.0 0.0.0.255 eq telnet Telnet connection to any host on the specified
network.
Step 13 router(config)# interface dialer 1 Change to dialer interface configuration
mode.
Step 14 router(config-if)# ip access-group 100 in Activate access list 100.
Cisco 3640
ISP POP
ISP POP
ISP POP
1 Cisco 6400
Cisco
7200
2
Cisco 3
827/827-4V
Cisco MGX
5
4 PSTN
74576
Callout
Number Description
1 Corporate network connecting through a Cisco 3640 voice gateway
2 Wholesale ISP business
3 ISP POP (data center) with videoconferencing multipoint control units (MCUs) and
IP/TV video servers
4 Data and voice local exchange carrier connecting through a Cisco MGX voice gateway
5 Small business or remote user, connecting to the network through a Cisco 827/827-4V
router
In the example, the Cisco 827 router sends data or voice packets from the remote
user to the service provider or corporate network through high-speed,
point-to-multipoint asymmetric digital subscriber line (ADSL) technology.
Cisco 3640
ISP POP
ISP POP
ISP POP
1 Cisco 6400
Cisco
7200
2
Cisco 837 3
Cisco 7200
6 4
4
82256
PSTN
5
Callout
Number Description
1 Corporate network connecting through a Cisco 3640 voice gateway
2 Wholesale ISP business
3 ISP POP (data center) with videoconferencing MCUs and IP/TV video servers
4 Dial backup or remote management that keeps the traffic working in case the primary
line’s traffic shuts down
5 PSTN to serve as an analog modem for dial backup or remote management
6 Small business or remote user, connecting to the network through a Cisco 837 router
In the topology, the Cisco 837 router sends data packets from the remote user to
the service provider or corporate network through high-speed, point-to-multipoint
ADSL technology.
Ethernet
ISP
Ethernet
3
82255
DES/3-DES IPSec
PSTN
Table 4-3 Key for Cisco 831 Router Virtual Private Network
Callout
Number Description
1 Small business or remote user, connecting to the network through a Cisco 831 router
2 Corporate network connecting through a Cisco router
3 Dial backup, as a failover link when primary line goes down
4 Branch office network connecting through a Cisco router
Cisco 3640
ISP POP
ISP POP
ISP POP
1 Cisco 6400
Cisco
7200
2
Cisco 836 3
Cisco 7200
6 4
4
82797
ISDN
5
Table 4-4 Key for Cisco 836 Router Network Connections
Callout
Number Description
1 Corporate network connecting through a Cisco 3640 gateway
2 Wholesale ISP business
3 ISP POP (data center) with videoconferencing MCUs and IP/TV video servers
4 Dial backup or remote management that keeps the traffic working in case of
primary line shutdown
Table 4-4 Key for Cisco 836 Router Network Connections (continued)
Callout
Number Description
5 ISDN to serve as an interface for dial backup or remote management
6 Small business or remote user, connecting to the network through a Cisco 836
router
Each scenario is described. Also, for each scenario, a network diagram, steps for
configuring network scenarios, and a configuration example are provided.
Figure 4-5 and Table 4-5 show the network topology for this scenario.
1 2
74577
DSLAM Cisco
Cisco 6400 DHCP
Cisco 6400
827/827-4V
Table 4-5 Key for Replacing a Bridge or Modem with a Cisco 827 Router
Callout
Number Description
1 Small business or remote user, connecting to the network through a Cisco 827 or
Cisco 827-4V router
2 The Internet
The Cisco 827 router is configured to act as a bridge on the WAN, so the data
packets are bridged through the Cisco 6400 router onto the Internet. This network
setup allows the simplicity of bridging data but also maintains router control. This
network is very simple, but it limits more complex services, such as stopping
broadcast traffic. If you want more services available on your network, you may
want to consider some of the others scenarios in this chapter.
Note If you have only a single ATM PVC for your bridging network, you do not have
to configure the protocol bridge broadcast.
Command Task
Step 1 no ip routing Disable IP routing.
Step 2 bridge 1 protocol ieee Specify the bridge protocol to define the type
of Spanning-Tree protocol.
Step 3 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 4 bridge-group 1 Specify the bridge-group number to which the
Ethernet interface belongs.
Step 5 no shutdown Enable the Ethernet interface.
Step 6 exit Exit configuration mode for the Ethernet
interface and the router.
Step 7 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 8 pvc 8/35 Create an ATM permanent virtual circuit
(PVC) for each end node with which the
router communicates.
Step 9 encapsulation aal5snap Specify the encapsulation type for the PVC.
Step 10 bridge-group 1 Specify the bridge-group number to which the
ATM interface belongs.
Step 11 no shutdown Enable the ATM interface.
Step 12 exit Exit configuration mode for the ATM
interface.
Configuration Example
The following is a configuration example for this network scenario. You do not
have to enter the commands marked “default.” These commands appear
automatically in the configuration file generated when you use the show
running-config command.
no ip routing
!
interface Ethernet0
no ip address
no ip directed-broadcast (default)
bridge-group 1
!
interface ATM0
no ip address
no ip directed-broadcast (default)
pvc 8/35
encapsulation aal5snap
!
bridge-group 1
!
ip classless (default)
!
bridge 1 protocol ieee
!
end
LAN
E0{828}ATM0
Router DSL modem DSLAM Access
Concentrator
PPPoE session
56956
Multiple PCs
Callout
Number Description
1 Multiple PCs in LAN.
2 Multiple PCs connected in a LAN.
3 Access concentrator, concentrating data and LAN into ATM service over E1/T1 links.
4 PPPoE session, which is initiated on the client side by a Cisco 837 or Cisco SOHO 97
router. If the session has a timeout, or if the session is disconnected, the PPPoE client
immediately attempts to reestablish the session.
Note Step 1 through Step 4 are not necessary for the Cisco SOHO 96 and 97 routers.
Command Task
Step 1 vpdn enable Enable VPDN.
Step 2 vpdn group tag Set the VPDN group.
Step 3 request-dialin Specify the dialing direction.
Step 4 protocol pppoe Specify the protocol type for the VPDN.
Step 5 interface ATM0 Enter configuration mode for the ATM
mtu 1492 interface. Set the maximum transmission unit
(MTU) size and PVC number.
pvc 8/35
Step 6 pppoe-client dial-pool-number 1 Define the pppoe client in dial pool number 1.
Step 7 interface Dialer 1 ip address negotiated Enter configuration mode for the Dialer 1
encapsulation ppp dialer-pool 1 interface to obtain the IP address via IPCP.
Specify the encapsulation type for the PVC
using dialer pool number 1.
Command Task
Step 1 interface atm 0 Enter configuration mode for the ATM
interface.
Step 2 dsl linerate {number | auto} Specify the DSL line rate. The range of valid
numbers is from 72 to 2312. Note that this
command is applicable only to Cisco 828 and
SOHO 78 routers.
Step 3 ip address 200.200.100.1 255.255.255.0 Set the IP address and subnet mask for the
ATM interface.
Step 4 pvc vpi/vci Create an ATM PVC for each end node with
which the router communcates.
Step 5 ppoe-client dial-pool-number 1 Bind the dialer to the interface.
Step 6 no shutdown Enable the ATM 0 interface.
Command Task
Step 1 ip route default-gateway-ip-address mask Set the IP route for the default gateway for the
dialer 0 Dialer 0 interface.
Step 2 interface dialer 0 Enter the Dialer 0 interface configuration.
Step 3 ip address negotiated Specify that the IP address is to be negotiated
over PPP.
Step 4 ip mtu 1492 Set the size of the IP maximum transmission
unit (MTU).
Step 5 encapsulation ppp Set the encapsulation type to PPP.
Command Task
Step 6 dialer pool 1 Specify the dialer pool to be used.
Step 7 dialer-group 1 Assign this interface to a dialer list.
Step 8 ppp authentication chap Set the PPP authentication method to
Challenge Handshake Authentication
Protocol (CHAP).
Step 9 exit Exit the Dialer 0 interface configuration.
Step 10 dialer-list 1 protocol ip permit Create a dialer list for interested packets to be
forwarded through the specified interface
dialer group.
If you enter the clear vpdn tunnel pppoe command with a PPPoE client session
already established, the PPPoE client session terminates, and the PPPoE client
immediately tries to reestablish the session.
Configuration Example
The following example shows a configuration of a PPPoE client.
vpdn enable
vpdn-group 1
request-dialin
protocol pppoe
!
interface atm0
no ip address
no atm ilmi-keepalive
pvc 1/100
pppoe-client dial-pool-number 1
!
interface dialer 1
ip address negotiated
ppp authentication chap
dialer pool 1
dialer-group 1
!
dialer-list 1 protocol ip permit
Note These four steps are not necessary for the Cisco SOHO 96 and 97 routers.
Command Task
Step 1 vpdn enable Enable VPDN.
Step 2 vpdn group tag Set the VPDN group.
Step 3 request-dialin Specify the dialing direction.
Step 4 protocol pppoe Specify the protocol type for the VPDN.
Command Task
Step 1 interface atm 0 Enter configuration mode for the ATM
interface.
Step 2 ip address 200.200.100.1 255.255.255.0 Set the IP address and subnet mask for the
ATM interface.
Command Task
Step 3 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Step 4 ppoe-client dial-pool-number 1 Bind the dialer to the interface.
dial-on-demand
Step 5 no shutdown Enable the ATM 0 interface.
Command Task
Step 1 ip route default-gateway-ip-address mask Set the IP route for the default gateway for the
dialer 0 Dialer 0 interface.
Step 2 interface dialer 0 Enter Dialer 0 interface configuration.
Step 3 ip address negotiated Specify that the IP address is to be negotiated
over PPP.
Step 4 ip mtu 1492 Set the size of the IP maximum transmission
unit (MTU).
Step 5 ip nat outside Establish the Dialer 0 interface as the outside
interface.
Step 6 encapsulation ppp Set the encapsulation type to PPP.
Step 7 dialer pool 1 Specify the dialer pool to be used.
Step 8 dialer-group 1 Assign this interface to a dialer list.
Step 9 ppp authentication chap Set the PPP authentication method to
Challenge Handshake Authentication
Protocol (CHAP).
Step 10 exit Exit the Dialer 0 interface configuration.
Step 11 dialer-list 1 protocol ip permit Create a dialer list for packets of interest to be
forwarded through the interface dialer group.
If you enter the clear vpdn tunnel pppoe command with a PPPoE client session
already established, the PPPoE client session terminates, and the PPPoE client
immediately tries to reestablish the session.
Configuration Example
The following example shows a configuration of a PPPoE client.
interface Ethernet0
no ip address
ip tcp adjust-mss 1400
no keepalive
hold-queue 100 out
!
vpdn enable
vpdn-group 1
request-dialin
protocol pppoe
!
interface atm0
no ip address
no atm ilmi-keepalive
pvc 1/100
pppoe-client dial-pool-number 1 dial-on-demand
!
interface dialer 1
ip address negotiated
ppp authentication chap
dialer pool 1
dialer-group 1
!
dialer-list 1 protocol ip permit
Cisco 827/827-4V
1 Cisco 6400 4
Cisco
74578
DSLAM
2 6400
192.168.1.1/24 3
Table 4-7 Key for PPP over ATM with NAT
Callout
Number Description
1 Small business or remote user
2 Connection to Ethernet 0 address 192.168.1.1/24 through a dialer interface
3 PPP over ATM PVC 8/35
4 The Internet
In this scenario, the small business or remote user on the Ethernet LAN can
connect to the Internet through ADSL. The Ethernet interface carries the data
packet through the LAN and offloads it to the PPP connection on the ATM
interface. The dialer interface is used to connect to the Internet or the corporate
office. The number of ATM PVCs is set by default.
NAT (represented as the dashed line at the edge of the Cisco 827 router) signifies
two addressing domains and the inside source address. The source list defines how
the packet travels through the network.
This section covers the following topics:
• Configuring the Ethernet Interface
• Configuring the Dialer Interface
• Configuring the ATM Interface
• Configuring NAT
• Configuration Example
To add other features to this network, see Chapter 7, “Router Feature
Configuration.”
After configuring your router, you need to configure the PVC endpoint. For a
general configuration example, see the “Cisco 3640 Gateway Configuration
Example” section on page 4-89.
Command Task
Step 1 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 2 ip address 192.168.1.1 255.255.255.0 Set the IP address and subnet mask for the
Ethernet interface.
Step 3 no shutdown Enable the interface and configuration
changes just made to the Ethernet interface.
Step 4 exit Exit configuration mode for the Ethernet
interface.
Command Task
Step 1 interface dialer 0 Enter configuration mode for the Dialer 0
interface.
Step 2 ip address negotiated Configure a negotiated IP address.
Command Task
Step 3 ip nat outside Set the interface to be connected to the outside
network.
Step 4 encapsulation ppp Specify the encapsulation type for the PVC to
be PPP.
Step 5 dialer pool 1 Specify which dialer pool number you are
using.
Step 6 exit Exit configuration mode for the dialer
interface.
Command Task
Step 1 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 2 pvc 8/35 Create an ATM PVC for each end node with
which the router communicates.
Step 3 encapsulation aal5mux ppp dialer Specify the encapsulation type for the PVC to
be aal5mux (PPP) and point back to the dialer
interface.
Step 4 dialer pool-member 1 Specify a dialer pool member.
Step 5 no shutdown Enable the interface and configuration
changes just made to the ATM interface.
Step 6 exit Exit configuration mode for the ATM
interface.
Configuring NAT
Follow the steps below to configure NAT, beginning in global configuration mode.
Command Task
Step 1 ip nat inside source list 1 interface dialer 0 Enable dynamic translation of addresses
overload permitted by the access list to one of
addresses specified in the dialer interface.
Step 2 ip route 0.0.0.0.0.0.0.0 dialer Set the ip route to point to the dialer interface
as a default gateway.
Step 3 access-list 1 permit 192.168.1 0 0.0.0.255 Define a standard access list permitting
addresses that need translation.
Step 4 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 5 ip nat inside Establish the Ethernet interface as the inside
interface.
Step 6 no shutdown Enable interface and configuration changes
just made to the Ethernet interface.
Step 7 exit Exit configuration mode for the Ethernet
interface.
Configuration Example
In the following configuration example, you do not have to enter the commands
marked “default.” These commands appear automatically in the configuration file
that is generated when you use the show running-config command.
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast (default)
ip nat inside
!
interface ATM0
no ip address
no ip directed-broadcast (default)
ip nat outside
no atm ilmi-keepalive (default)
pvc 8/35
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
bundle-enable
!
interface Dialer0
ip address negotiated
no ip directed-broadcast (default)
ip nat outside
encapsulation ppp
dialer pool 1
!
ip nat inside source list 1 interface Dialer0 overload
ip classless (default)
ip route 0.0.0.0 0.0.0.0 Dialer 0 (default gateway)
!
access-list 1 permit 192.168.1.0 0.0.0.255
!
end
Note The remote management described next refers to backup remote management,
which function allows external control of the router via the ISDN when the ATM
link goes down.
Cisco 836 and 837 Routers and Cisco SOHO 96 and 97 Routers
The following can be used to bring up the dial backup feature in the Cisco IOS
software for the Cisco 836 and 837 routers and the Cisco SOHO 96 and 97 routers:
• Backup Interfaces
• Floating Static Routes
• Dialer Watch
For more information on the three features, see Chapter 1, “Concepts.”
Backup Interfaces
When the device receives an indication that the primary line is down, the backup
interface is brought up. You can configure the backup interface to go down (after
a specified time) when the primary connection is restored.
The dial-on-demand routing (DDR) backup call is triggered by traffic of interest.
Even if the backup interface comes out of standby mode, the router will not trigger
the backup call unless it receives traffic of interest for that backup interface.
Floating static routes depend on traffic of interest to trigger the DDR backup call.
The router does not actually trigger the backup call unless it receives traffic of
interest for that backup interface, even if the router installs the floating static route
in the route table.
Floating static routes are independent of line protocol status. This is an important
consideration on Frame Relay circuits wherein line protocol may not go down if
the data-link connection identifier (DLCI) is inactive. Floating static routes are
also encapsulation independent.
Note When static routes are configured, the primary interface protocol must go down
in order to activate the floating static route.
Dialer Watch
Table 4-8 Encapsulation Types Supported by Dial Backup Feature—Cisco 836 and 837 Routers
Figure 4-8 Cisco 837 Router Dial Backup and Remote Management
1
ATM
837 3620
3 2
Modem Modem
2
PSTN
82269
Modem
PC
Table 4-10 Key for Cisco 837 Router Dial Backup and Remote Management
Callout
Number Description
1 Main WAN link; primary connection to Internet service provider
2 Dial backup; serves as a failover link when primary line goes down
3 Remote management; serves as dial-in access to allow changes or updates to Cisco IOS
configurations
Figure 4-9 Cisco 836 Router Dial Backup and Remote Management—Dial Backup Through CPE
Splitter, DSLAM, and CO Splitter
3 Web
82892
Administrator server
Table 4-11 Key for Cisco 836 Router Dial Backup and Remote Management—Dial Backup Through
CPE Splitter, DSLAM, and CO Splitter
Callout
Number Description
1 Primary ADSL interface
2 Dial backup and remote management via ISDN interface; serves as a failover link
when primary line goes down
3 Administrator remote management via ISDN interface when the primary ADSL link
is down; serves as dial-in access to allow changes or updates to Cisco IOS
configuration
Figure 4-10 Cisco 836 Router Dial Backup and Remote Management—Dial Backup Directly from
Router to ISDN Switch
DSLAM Aggregator
ATM
network
836 CPE
PC splitter
Internet
3
ISDN
2
switch
88208
Web
Administrator server
Table 4-12 Cisco 836 Router Dial Backup and Remote Management—Dial Backup Directly from
Router to ISDN Switch
Callout
Number Description
1 Primary ADSL interface
2 Dial backup and remote management via ISDN interface; serves as a failover link
when primary line goes down
3 Administrator remote management via ISDN interface when the primary ADSL
link is down; serves as dial-in access to allow changes or updates to Cisco IOS
configuration
PPP over ATM with Centrally Managed Addressing and with Dial
Backup
When customer premises equipment such as a Cisco 837 router is connected to an
ISP, an IP address is dynamically assigned to the router, or the IP address may be
assigned by its peer through the centrally managed function. The dial backup
feature can be added to provide a failover route in case the primary line fails.
Configuring Dial Backup and Remote Management for the Cisco 837 Router
Follow the steps below to configure dial backup and remote management for the
Cisco 837 router.
Command Task
Step 1 ip name-server 206.13.28.12 Enter your ISP DNS IP address.
Step 2 ip dhcp pool 1 Configure CPE as a local DHCP server.
Step 3 vpdn enable Enable VPDN.
Step 4 vpdn-group 1 Specify VPDN group for protocol PPPoE.
Step 5 chat-script Dialout ABORT ERROR Configure a chat script for a modem.
ABORT BUSY ““ “AT” OK “ATDT
5555102 T” TIMEOUT 45 CONNECT \c
Step 6 interface Async1 Enter configuration mode for the async
interface.
Step 7 interface Dialer3 Enter configuration mode for the dialer
interface.
Step 8 dialer watch-group 1 Specify the group number for watch-list.
Step 9 ip nat inside source list 101 interface Establish the Ethernet interface as the inside
Dialer3 overload interface.
Step 10 ip route 0.0.0.0 0.0.0.0 ! (dial backup peer Set the IP route to point to the dialer interface
address @ISP) as a default gateway.
Step 11 access-list 101 permit ip 192.168.0.0 Define an extended access list permitting
0.0.255.255 any addresses that need translation.
Step 12 dialer watch-list 1 ip ! (ATM peer address Evaluate the status of the primary link, based
@ISP) 255.255.255.255 on the existence of routes to the peer.
Step 13 line con 0 Enter configuration mode for the console
interface.
Step 14 modem enable Change the console port to auxiliary port
function.
Step 15 line aux 0 Enter configuration mode for the auxiliary
interface.
Step 16 flow control hardware Enable hardware signal flow control
Configuration Example
The following configuration example for a Cisco 837 router specifies an IP
address for the ATM interface via PPP/IPCP address negotiation and dial backup
over the console port.
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Router
!
memory-size iomem 20
enable password cisco
!
ip subnet-zero
ip name-server 206.13.28.12
ip name-server 206.13.31.12
ip name-server 63.203.35.55
ip dhcp excluded-address 192.168.1.1
!
ip dhcp pool 1
import all
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
!
ip audit notify log
ip audit po max-events 100
vpdn enable
!
vpdn-group 1
request-dialin
protocol pppoe
!
! Need to use your own correct ISP phone number
modemcap entry MY-USER_MODEM:MSC=&F1S0=1
chat-script Dialout ABORT ERROR ABORT BUSY ““ “AT” OK “ATDT 5555102\T”
TIMEOUT 45 CONNECT \c
!
!
!
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
ip nat inside
Note Traffic of interest must be present to activate the backup ISDN line by means of
the backup interface and floating static routes methods. Traffic of interest is not
needed for the dialer watch to activate the backup ISDN line.
Command Task
Step 1 isdn switch-type basic-net3 Specify the ISDN switch type.
Step 2 interface BRI0 Enter configuration mode for the ISDN Basic
Rate Interface (BRI).
Step 3 encapsulation ppp Set BRI0 interface encapsulation type to PPP.
Step 4 dialer pool-member 1 Specify the dialer pool membership.
Step 5 isdn switch-type basic-net3 Specify the ISDN switch type.
Step 6 exit Exit to return to global configuration mode.
Step 7 interface Dialer0 Enter configuration mode for the dialer
interface.
Step 8 ip address negotiated Obtain the IP address from the peer.
Step 9 encapsulation ppp Specify Dialer 0 encapsulation type as PPP.
Step 10 dialer pool 1 Specify the dialer pool to be used. Dialer pool
1 setting associates Dialer 0 interface with
BRI0 because the BRI0 dialer pool-member
value is “1.”
Step 11 dialer string 384040 Specify the telephone number to be dialed.
Step 12 dialer-group 1 Assign this interface to a dialer group.
Step 13 exit Exit to return to global configuration mode.
Command Task
Step 14 dialer-list 1 portocol ip permit Create a dialer list for packets of interest to be
forwarded through the specified interface
dialer group. Dialer-list 1 corresponds to
dialer-group 1.
Command Task
Step 1 interface ATM0 Enter ATM interface configuration mode.
Step 2 backup interface BRI0 Assign BRI0 as the secondary backup
interface.
Command Task
Step 1 ip route 0.0.0.0 0.0.0.0 22.0.0.2 Assign the primary route.
Step 2 ip route 0.0.0.0 0.0.0.0 192.168.2.2 150 Assign the lower routing administrative
distance value for the backup interface route.
192.168.2.2 is the peer IP address of the
backup interface.
Note When the static routes are configured, the primary interface protocol must go
down in order to activate the floating static route.
Follow the steps below to configure the dynamic route on the Cisco 836 router
ISDN port, beginning in global configuration mode.
Command Task
Step 1 router rip Enables RIP routing.
Step 2 network 22.0.0.0 Define the primary interface network.
22.0.0.0 is the network value of the primary
interface.
Step 3 ip route 0.0.0.0 0.0.0.0 192.168.2.2 150 Assign the lower routing administrative
distance value for the backup interface route.
192.168.2.2 is the peer IP address of the
backup interface.
Note The floating static route depends on the routing protocol convergence times when
dynamic routing is activated.
Command Task
Step 1 interface Dialer0 Enter configuration mode for the dial backup
interface.
Step 2 dialer watch-group 1 Specify the group number for the watch list.
Step 3 exit Exit to return to global configuration mode.
Step 4 ip route 0.0.0.0 0.0.0.0 22.0.0.2 Assign the primary route. 22.0.0.2 is the peer
IP address of the primary interface.
Step 5 ip route 0.0.0.0 0.0.0.0 192.168.2.2 150 Assign the lower routing administrative
distance value for the backup interface route.
192.168.2.2 is the peer IP address of the
backup interface.
Step 6 dialer watch-list 1 ip 22.0.0.2 Assign an IP address to the watch list via the
255.255.255.255 dialer watch command. If the connection on
the primary interface is lost and the IP address
is unavailable on the Cisco 836 router, the
dial-out feature on the backup interface is
triggered. 22.0.0.2 is the peer IP address of
the primary interface.
Configuration Example
The next three configuration examples shows sample configurations for the three
dial backup interface and remote management methods.
The following is an example of configuring dial backup and remote management
using the backup interface command.
Cisco836#
!
vpdn enable
!
vpdn-group 1
accept-dialin
protocol pppoe
!
!Specifies the ISDN switch type
isdn switch-type basic-net3
!
interface Ethernet0
ip address negotiated
ip mtu 1492
encapsulation ppp
dialer pool 2
dialer-group 2
!
ip classless
no cdp enable
!Primary and backup interface given route metric (This example using
static routes, thus atm0 line protcol must be brought down for backup
interface to function.)
ip route 0.0.0.0 0.0.0.0 22.0.0.2
ip route 0.0.0.0 0.0.0.0 192.168.2.2 150
ip http server
!
!Specifies interesting traffic to trigger backup ISDN traffic
dialer-list 1 protocol ip permit
pppoe-client dial-pool-number 2
!
dsl operating-mode auto
!
! Dial backup interface, associated with physical BRI0 interface.
Dialer pool 1 associates it with BRI0’s dialer pool member 1. Note
“dialer watch-group 1” associates a watch list with corresponding
“dialer watch-list” command
interface Dialer0
ip address negotiated
encapsulation ppp
dialer pool 1
dialer idle-timeout 30
dialer string 384040
dialer watch-group 1
dialer-group 1
!
! Primary interface associated with physical ATM0 interface, dialer
pool 2 associates it with ATM0’s dial-pool-number2
interface Dialer2
ip address negotiated
ip mtu 1492
encapsulation ppp
dialer pool 2
dialer-group 2
no cdp enable
!
ip classless
ip classless
ip route 0.0.0.0 0.0.0.0 22.0.0.1 50
ip route 0.0.0.0 0.0.0.0 30.1.1.2.80
Command Task
Step 1 interface Async1 Enter configuration mode for the async
interface.
Step 2 line con 0 Enter configuration mode for the console
interface.
Step 3 modem enable Change the console port to the auxiliary port.
Step 4 line aux 0 Enter configuration mode for the auxiliary
interface.
Step 5 flowcontrol hardware Enable hardware signal flow control.
Configuration Example
The following configuration example for a Cisco SOHO 97 router specifies the IP
address for the ATM interface via PPP/IPCP address and supports dial-in
maintenance over the console port.
!
!Remote management account
username dialin password cisco
modemcap entry MY_USR_MODEM:MSC=&F1S0=1
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
ip nat inside
hold-queue 100 out
!
interface ATM0
no ip address
no atm ilmi-keepalive
pvc 0/35
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
dsl operating-mode auto
!
interface Async1
no ip address
encapsulation ppp
dialer in-band
autodetect encapsulation ppp
async default routing
Figure 4-11 Cisco 831 Router Dial Backup and Remote Management in a DSL Modem Environment
1
Ethernet
DSL
831 DSL 3620
modem
3 2
Modem Modem
2
PSTN
82270
Modem
PC
Table 4-13 Key for Cisco 831 Router Dial Backup and Remote Management in a DSL Modem
Environment
Callout
Number Description
1 Main WAN link; primary connection to Internet service provider
2 Dial backup; serves as a failover link when primary line goes down
3 Remote management; serves as a dial-in access to allow change or update of Cisco IOS
configurations
Follow the steps below to configure dial backup and remote management for the
Cisco 831 router.
Command Task
Step 1 ip name-server 206.13.28.12 Enter your ISP DNS IP address.
Step 2 ip dhcp pool 1 Configure CPE as a local DHCP server.
Step 3 vpdn enable Enable VPDN.
Command Task
Step 4 vpdn-group 1 Specify VPDN group for protocol PPPoE.
Step 5 chat-script Dialout ABORT ERROR Configure a chap script for a modem.
ABORT BUSY ““ “AT” OK “ATDT
5555102 T” TIMEOUT 45 CONNECT \c
Step 6 interface Async1 Enter configuration mode for the async
interface.
Step 7 interface Dialer3 Enter configuration mode for the dialer
interface.
Step 8 ip nat inside source list 101 interface Establish the Ethernet interface as the inside
Dialer3 overload interface.
Step 9 ip route 0.0.0.0 0.0.0.0 ! (dial backup peer Set the IP route to point to the dialer interface
address @ISP) as a default gateway.
Step 10 access-list 101 permit ip 192.168.0.0 Define an extended access list permitting
0.0.255.255 any addresses that need translation.
Step 11 dialer watch-list 1 ip ! (peer address @ISP) Evaluate the status of the primary link, based
255.255.255.255 on the existence of routes to the peer.
Step 12 line con 0 Enter configuration mode for the console
interface.
Step 13 modem enable Change the console port to the auxiliary port.
Step 14 line aux 0 Enter configuration mode for the auxiliary
interface.
Step 15 flowcontrol hardware Enable hardware signal flow control.
!
memory-size iomem 20
enable password cisco
!
ip subnet-zero
ip name-server 206.13.28.12
ip name-server 206.13.31.12
ip name-server 63.203.35.55
ip dhcp excluded-address 192.168.1.1
!
ip dhcp pool 1
import all
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
!
ip audit notify log
ip audit po max-events 100
vpdn enable
!
vpdn-group 1
request-dialin
protocol pppoe
!
! Need to use your own correct ISP phone number
modemcap entry MY-USER_MODEM:MSC=&F1S0=1
chat-script Dialout ABORT ERROR ABORT BUSY ““ “AT” OK “ATDT 5555102\T”
TIMEOUT 45 CONNECT \c
!
!
!
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip tcp adjust-mss 1452
hold-queue 100 out
!
interface Ethernet1
no ip address
no ip route-cache
no ip mroute-cache
pppoe enable
pppoe-client dial-pool-number 1
!
!Dial backup and remote management physical interface
interface Async1
no ip address
encapsulation ppp
dialer in-band
dialer pool-member 3
async default routing
async dynamic routing
async mode dedicated
ppp authentication pap callin
!
! Primary wan link
interface Dialer1
ip address negotiated
ip mtu 1492
ip nat outside
encapsulation ppp
dialer pool 1
ppp authentication pap callin
ppp pap sent-username account password 7 pass
ppp ipcp dns request
ppp ipcp wins request
ppp ipcp mask request
!
! Dialer backup logical interface
interface Dialer3
ip address negotiated
ip nat outside
encapsulation ppp
no ip route-cache
no ip mroute-cache
dialer pool 3
dialer idle-timeout 60
dialer string 5555102 modem-script Dialout
dialer watch-group 1
!
! Remote management PC ip address
peer default ip address 192.168.2.2
no cdp enable
!
! Need to use your own ISP account and password
ppp pap sent-username account password 7 pass
ppp ipcp dns request
ppp ipcp wins request
ppp ipcp mask request
!
! IP NAT over Dialer interface using route-map
ip nat inside source route-map main interface Dialer1 overload
ip nat inside source route-map secondary interface Dialer3 overload
ip classless
!
stopbits 1
line aux 0
exec-timeout 0 0
!
! To enable and communicate with the external modem properly
script dialer Dialout
modem InOut
modem autoconfigure discovery
transport input all
stopbits 1
speed 115200
flowcontrol hardware
line vty 0 4
exec-timeout 0 0
password cisco
login
!
scheduler max-task-time 5000
end
Command Task
Step 1 interface Async1 Enter configuration mode for the async
interface.
Step 2 line con 0 Enter configuration mode for the console
interface.
Step 3 modem enable Change the console port to the auxiliary port.
Step 4 line aux 0 Enter configuration mode for the auxiliary
interface.
Step 5 flowcontrol hardware Enable hardware signal flow control.
Configuration Example
The following example shows how to configure a Cisco SOHO 91 router to obtain
the IP address for ATM interface via PPP/IPCP address negotiation and shows
how to configure and support dial-in maintenance over the console port.
!
!Remote management account
username dialin password cisco
modemcap entry MY_USR_MODEM:MSC=&F1S0=1
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
ip nat inside
hold-queue 100 out
!
interface Async1
no ip address
encapsulation ppp
dialer in-band
autodetect encapsulation ppp
async default routing
async dynamic routing
async mode dedicated
pap authentication pap callin
peer default ip address 192.168.2.2
!
ip nat inside source list 101 interface Dialer1 overload
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1 150
!
no ip http server
ip pim bidir-enable
!
!
access-list 101 permit ip 192.168.0.0 0.0.255.255 any
dialer-list 1 protocol ip permit
!
line con 0
exec-timeout 0 0
modem enable
stopbits 1
line aux 0
exec-timeout 0 0
script dialer Dialout
modem Dialin
modem autoconfigure discovery
transport input all
stopbits 1
speed 38400
flowcontrol hardware
line vty 0 4
login local
!
scheduler max-task-time 5000
end
Note Whenever you change server properties, you must reload the server to load the
configuration data from the Network Registrar database.
To configure the DHCP server, you must accept Network Registrar’s defaults or
supply the data explicitly:
• The IP address of the server’s interface (Ethernet card). This interface must
have a static IP address that is not assigned dynamically by DHCP.
• The subnet mask, which identifies the network membership of the interface.
The subnet mask defaults to the appropriate value, based on the network class
of the interface address. In most cases, the subnet mask is 255.255.255.0.
Network Registrar uses the interface named default to provide configurable
default values for interfaces that the DHCP server discovers automatically. If you
delete the default interface, the DHCP server uses hard-coded default values for
port numbers and socket buffer sizes for the interfaces that it autodiscovers.
If you enable discover-interfaces, the DHCP server uses the operating system
platform support to enumerate all the active interfaces on the machine and (unless
there is an interface configuration with the ignore feature enabled) attempts to
listen on all of these. If you disable discover-interfaces, the DHCP server listens
on the interface that you specify, as long as it does not have the ignore feature
enabled.
Use the dhcp-interface commands to add, remove, and list the IP addresses of
your server’s hardware cards. Interfaces are named with the IP address and net
mask for the physical device.
If you have two interface cards for the server host, use two dhcp-interface create
commands to register them both. Use the net mask suffix 16 or 24 as part of the
address.
nrcmd> dhcp-interface 192.168.1.12/24 create
nrcmd> dhcp-interface 10.1.2.3/24 create
Use the dhcp-interface set ignore=true command if you want Network Registrar
to use only one interface, you have to set all the other ones to be ignored.
nrcmd> dhcp-interface 10.1.2.3/24 set ignore=true
Command Task
Step 1 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 2 ip address ip-address mask Set the IP address and subnet mask for the
Ethernet interface.
Step 3 no shutdown Enable the Ethernet interface to change the
state from administratively down to up.
Step 4 exit Exit configuration mode for the Ethernet
interface.
interface Ethernet0/1
no ip address
no ip route-cache
no ip mroute-cache
half-duplex
no cdp enable
!
interface ATM1/0
no ip address
no atm ilmi-keepalive
!
interface ATM1/0.1 point-to-point
pvc 1/40
encapsulation aal5mux ppp Virtual-Template1
!
!
interface ATM1/0.2 point-to-point
pvc 1/41
encapsulation aal5snap
protocol pppoe
!
!
interface Virtual-Template1
ip unnumbered Loopback1
peer default ip address pool test
!
interface Virtual-Template2
ip unnumbered Loopback2
ip mtu 1492
!
interface Async65
no ip address
encapsulation ppp
dialer in-band
dialer pool-member 1
autodetect encapsulation ppp
async default routing
async dynamic routing
async mode dedicated
!
interface Dialer0
ip unnumbered Async65
encapsulation ppp
dialer pool 1
dialer remote-name c837
dialer string 5555101 modem-script Dialout
dialer-group 1
autodetect encapsulation ppp
no cdp enable
!
ip local pool test 21.0.0.10 21.0.0.200
ip kerberos source-interface any
ip classless
no ip http server
!
dialer-list 1 protocol ip permit
no cdp run
!
!
dial-peer cor custom
!
!
!
!
!
line con 0
exec-timeout 0 0
transport input none
line aux 0
exec-timeout 0 0
no activation-character
script dialer Dialout
no vacant-message
modem InOut
modem autoconfigure type MY_USR_MODEM
transport input all
transport output telnet
escape-character NONE
autohangup
stopbits 1
speed 38400
flowcontrol hardware
line vty 0 4
exec-timeout 0 0
login
!
end
To configure RADIUS on your Cisco 800 series router, you must perform the
following tasks:
• Use the aaa new-model global configuration command to enable
authentication, authorization, and accounting (AAA). AAA must be
configured if you plan to use RADIUS.
• Use the aaa authentication global configuration command to define the
method lists for RADIUS authentication.
• Use line and interface commands to enable the defined method lists to be
used.
For instructions on configuring a RADIUS client, refer to the Cisco IOS Security
Configuration Guide.
Cisco 827/827-4V
ATM 0
200.200.100.254
1 Cisco 6400 4
Cisco
74579
2 DSLAM
6400
192.168.1.1/24 3
Callout
Number Description
1 Small business or remote user
2 Connection to Ethernet 0 address 192.168.1.1/24
3 ATM 0 PVC 8/35
4 The Internet
In this scenario, the small business or remote user on the Ethernet LAN can
connect to the Internet through ADSL. The Ethernet interface carries the data
packet through the LAN and offloads it to the RFC 1483 connection on the ATM
interface. The number of ATM PVCs is set by default.
NAT (represented as the dashed line at the edge of the 827 routers) signifies two
addressing domains and the inside source address. The source list defines how the
packet travels through the network.
The following configuration topics are covered in this section:
• Configuring the Ethernet Interface
• Configuring the ATM Interface
• Configuring NAT
• Configuration Examples
To add additional features to this network, see Chapter 7, “Router Feature
Configuration.”
After configuring your router, you need to configure the PVC endpoint. For a
general configuration example, see the “Cisco 3640 Gateway Configuration
Example” section on page 4-89.
Command Task
Step 1 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 2 ip address 192.168.1.1 255.255.255.0 Set the IP address and subnet mask for the
Ethernet interface.
Step 3 no shutdown Enable the Ethernet interface.
Step 4 exit Exit configuration mode for the Ethernet
interface.
Command Task
Step 1 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 2 ip address 200.200.100.1 255.255.255.0 Set the IP address and subnet mask for the
ATM interface.
Step 3 pvc 8/35 Create an ATM PVC for each end node with
which the router communicates.
Step 4 protocol ip 200.200.100.254 broadcast Set the protocol broadcast for the IP address.
Step 5 encapsulation type Specify the encapsulation type for the PVC to
be AAL5SNAP or AAL5MUX IP.
Step 6 no shutdown Enable the ATM interface.
Step 7 exit Exit configuration mode for the ATM
interface.
Configuring NAT
Complete the follow steps to configure NAT, beginning in global configuration
mode.
Command Task
Step 1 ip nat inside source list 1 pool interface Enable dynamic translation of addresses
ATM0 overload permitted by the access list to one of
addresses specified in the ATM interface.
Step 2 ip route 0.0.0.0.0.0.0.0 atm0 Set the IP route to point to the ATM interface
as a default gateway.
Step 3 access-list 1 permit 192.168.1.0.0.0.0.255 Define a standard access list permitting
addresses that need translation.
Step 4 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 5 ip nat inside Establish the Ethernet interface as the inside
interface.
Step 6 exit Exit configuration mode for the Ethernet
interface.
Step 7 interface atm 0 Enter configuration mode for the ATM
interface.
Step 8 ip nat outside Establish the ATM interface as the outside
interface.
Step 9 exit Exit configuration mode for the ATM
interface.
Configuration Examples
In the following configuration examples, you do not have to enter the commands
marked “default.” These commands appear automatically in the configuration file
that is generated when you use the show running-config command.
The following example shows an RFC 1483 LLC/SNAP encapsulation over ATM.
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast (default)
ip nat inside
!
interface ATM0
ip address 200.200.100.1 255.255.255.0
no ip directed-broadcast (default)
ip nat outside
no atm ilmi-keepalive (default)
pvc 8/35
encapsulation aal5snap
protocol ip 200.200.100.254 broadcast
!
bundle-enable
!
ip nat inside source list 1 interface ATM0 overload
ip classless (default)
ip route 0.0.0.0 0.0.0.0 200.200.100.254
!
access-list 1 permit 192.168.1.0 0.0.0.255
!
end
Cisco 827/827-4V
1 Cisco 6400 4
Cisco
74580
2 DSLAM
6400
192.168.1.1/24 3
Table 4-15 Key for IRB Internet Scenario
Callout
Number Description
1 Small business or remote user
2 Connection to Ethernet 0 address 192.168.1.1/24
3 ATM 0 PVC 8/35
4 The Internet
One side of the network (the WAN, in this scenario) is configured to act as a
bridge. The Bridge-Group Virtual Interface (BVI) is configured to act as a routed
interface from the WAN bridge-group to the nonbridged LAN interface. From the
LAN, the network appears as a router. From the WAN, the network appears as a
bridge.
The ATM interface uses AAL5SNAP encapsulation. The number of PVCs is set
by default.
NAT (represented as the dashed line at the edge of the Cisco 827 router) signifies
two addressing domains and the inside source address. The source list defines how
the packet travels through the network.
This section covers the following configuration topics:
• Configuring the Default Gateway
• Configuring the Ethernet Interface and IRB
• Configuring the ATM Interface
• Configuring the BVI
• Configuring NAT
• Configuration Example
To add more features to this network, see Chapter 7, “Router Feature
Configuration.”
After configuring your router, you need to configure the PVC endpoint. For a
general configuration example, see the “Cisco 3640 Gateway Configuration
Example” section on page 4-89.
Command Task
Step 1 bridge irb Specify IRB.
Step 2 bridge 1 route ip Enable IP routing to and from bridge-group 1.
Step 3 bridge 1 protocol ieee Specify the bridge protocol to define the type
of Spanning-Tree Protocol (STP).
Step 4 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 5 ip address 192.168.1.1 255.255.255.0 Set the IP address and subnet mask for the
Ethernet interface.
Step 6 no shutdown Enable the Ethernet interface.
Step 7 exit Exit configuration mode for the Ethernet
interface.
Command Task
Step 1 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 2 pvc 8/35 Create an ATM PVC for each end node with
which the router communicates.
Step 3 encapsulation aal5snap Specify the encapsulation type for the PVC.
Step 4 bridge-group 1 Specify the bridge-group number to which the
ATM interface belongs.
Step 5 no shutdown Enable the ATM interface.
Step 6 exit Exit configuration mode for the ATM
interface.
Command Task
Step 1 interface bvi 1 Enter configuration mode for the BVI.
Step 2 ip address 200.200.100.1 255.255.255.0 Set the IP address and subnet mask for the
BVI.
Step 3 exit Exit configuration mode for Ethernet
interface.
Configuring NAT
Follow the steps below to configure NAT, beginning in global configuration mode.
Command Task
Step 1 ip nat pool test 200.200.100.1 200.200.100.1 Create pool of global IP addresses for NAT.
255.255.255.0
Step 2 access-list 101 permit ip 192.168.1 Define a standard access list permitting
0.0.0.0.255 any log addresses that need translation.
Step 3 ip nat inside source list 101 pool test Enable dynamic translation of addresses
overload permitted by the access list to one of the
addresses specified in the pool.
Step 4 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 5 ip nat inside Establish the Ethernet interface as the inside
interface.
Step 6 no shutdown Enable interface and configuration changes
just made to the interface.
Step 7 exit Exit configuration mode for the Ethernet
interface.
Step 8 interface ATM 0 Enter configuration mode for the ATM
interface.
Command Task
Step 9 ip nat outside Establish the ATM interface as the outside
interface.
Step 10 no shutdown Enable the interface and configuration
changes just made to the interface.
Step 11 exit Exit configuration mode for the ATM
interface.
Step 12 interface bvi 1 Enter configuration mode for the BVI.
Step 13 ip nat outside Establish the BVI as the outside interface.
Step 14 no shutdown Enable the interface and configuration
changes just made to the interface.
Step 15 end Exit configuration mode for the BVI.
Configuration Example
In the following configuration example, you do not have to enter the commands
marked “default.” These commands appear automatically in the configuration file
that is generated when you use the show running-config command.
bridge irb
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast (default)
ip nat inside
!
interface ATM0
no ip address
no ip directed-broadcast (default)
ip nat outside
no atm ilmi-keepalive (default)
pvc 8/35
encapsulation aal5snap
!
bridge-group 1
!
interface BVI1
ip address 200.200.100.1 255.255.255.0
no ip directed-broadcast (default)
ip nat outside
!
Cisco
2 827/827-4V 3 Cisco
Cisco 6400 6400 4
1
DSLAM
3640
Voice
gateway
74581
Table 4-16 Key for CRB Internet Scenario
Callout
Number Description
1 Small business or remote user
2 Ethernet 0 bridge
3 ATM connection, ATM0.1 PVC 1/40 Voice 1.0.0.1/24, ATM0.2 PVC 8/35 data
4 The Internet
Command Task
Step 1 bridge crb Specify CRB.
Step 2 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 3 bridge-group 1 Specify the bridge-group number to which the
Ethernet interface belongs.
Step 4 exit Exit configuration mode for the Ethernet
interface and the router.
Step 5 bridge 1 protocol ieee Specify the bridge protocol to define the type
of STP.
Command Task
Step 1 interface ATM 0.1 point-to-point Specify the ATM0.1 subinterface.
Step 2 ip address 1.0.0.1 255.255.255.0 Set the IP address and subnet mask for the
ATM0.1 subinterface.
Step 3 pvc 1/40 Create an ATM PVC for each end node with
which the router communicates.
Step 4 encapsulation aal5snap Specify the encapsulation type for the PVC.
Step 5 protocol ip 1.0.0.2 broadcast Set the protocol broadcast for the IP address.
Step 6 interface ATM 0.2 point-to-point Specify the ATM0.2 subinterface.
Step 7 pvc 8/35 Create an ATM PVC for each end node with
which the router communicates.
Step 8 encapsulation aal5snap Specify the encapsulation type for the PVC.
Step 9 bridge-group 1 Specify the bridge-group number to which the
Ethernet interface belongs.
Step 10 no shutdown Enable the ATM interface.
Step 11 exit Exit configuration mode for the ATM
interface.
Command Task
Step 1 dial-peer voice number POTS Enter configuration mode for the dial peer.
Step 2 destination-pattern string Define the telephone number associated with
the port.
Step 3 voice port-number Specify the port number.
Table 4-17 Mapping of Dial Peer Number to Destination Telephone and Port
Command Task
Step 1 dial-peer voice number VoIP Enter configuration mode for the dial peer.
Step 2 destination-pattern string Define the destination telephone number
associated with each VoIP dial peer.
Step 3 codec g711ulaw Specify a codec if you are not using the
default codec of g.729.
Step 4 session target ipv4:1.0.0.2 Specify a destination IP address for each dial
peer.
Table 4-18 Mapping of VoIP Dial Peers to Destination Telephone Numbers for
H.323
Configuration Example
In the following configuration example, you do not have to enter the commands
marked “default.” These commands appear automatically in the configuration file
that is generated when you use the show running-config command.
ip subnet-zero
!
bridge crb
!
interface Ethernet0
no ip address
no ip directed-broadcast (default)
bridge-group 1
!
interface ATM0
no ip address
no ip directed-broadcast (default)
no atm ilmi-keepalive (default)
bundle-enable
!
interface ATM0.1 point-to-point
ip address 1.0.0.1 255.255.255.0
no ip directed-broadcast (default)
pvc voice 1/40
protocol ip 1.0.0.2 broadcast
encapsulation aal5snap
!
interface ATM0.2 point-to-point
no ip address
no ip directed-broadcast (default)
pvc data 8/35
encapsulation aal5snap
!
bridge-group 1
!
ip classless (default)
!
bridge 1 protocol ieee
!
voice-port 1
local-alerting
!
voice-port 2
local-alerting
!
voice-port 3
local-alerting
!
voice-port 4
local-alerting
!
dial-peer voice 101 pots
destination-pattern 14085271111
port 1
!
dial-peer voice 1100 voip
destination-pattern 12123451111
codec g711ulaw
session target ipv4:1.0.0.2
!
dial-peer voice 102 pots
destination-pattern 14085272222
port 2
!
dial-peer voice 1200 voip
destination-pattern 12123452222
codec g711ulaw
session target ipv4:1.0.0.2
!
dial-peer voice 103 pots
destination-pattern 14085273333
port 3
!
dial-peer voice 1300 voip
destination-pattern 12123453333
codec g711ulaw
session target ipv4:1.0.0.2
!
dial-peer voice 104 pots
destination-pattern 14085274444
port 4
!
dial-peer voice 1400 voip
destination-pattern 12123454444
codec g711ulaw
session target ipv4:1.0.0.2
!
end
Voice Scenario
This section describes a voice scenario configuration using the Cisco 827 router
in an H.323 signaling environment.
Setting up voice on the router actually includes two configurations—one for data
and one for voice. When you have completed the configuration for the data
scenario, you can add voice by configuring the POTS and VoIP dial peers and
voice ports. Scenarios for data and voice are provided in the sections that follow.
Data Network
Figure 4-15 and Table 4-19 show a data network with traffic routing through the
Cisco 827 router and then switching on to the ATM interface.
Cisco Cisco
ATM
827 DSLAM 6400
1
Cisco
ATM 0 6400
10.10.10.20
255.255.255.0
PVC 8/35 PVC 0/40
10.10.10.36
Cisco 255.255.255.0
20.20.20.20 3640
255.255.255.0
74582
3
Cisco 2
3640
Table 4-19 Key for Data Network
Callout
Number Description
1 Ethernet connection to a Cisco 827 router
2 Ethernet connection 0/1 at address 172.17.1.1, subnet 255.255.255.0
3 Ethernet connection 0 at 172.17.1.36, subnet 255.255.255.0
The Cisco 827 router is connected through the ATM interface through one PVC.
The PVC is associated with a QoS policy called mypolicy. Data traffic coming
from the Ethernet must have an IP precedence value of less than 5 (critical) to
distinguish it from voice traffic.
EIGRP is configured to send hello packets every 5 seconds to inform neighboring
routers that it is functioning. If a particular router does not send a hello packet
within a prescribed period, EIGRP assumes that the state of a destination has
changed and sends an incremental update.
NAT (represented by the dashed line at the edge of the Cisco 827 router) signifies
two addressing domains and the inside source address. The source list defines how
the packet travels through the network.
This scenario includes configuration tasks and a configuration example. To add
more features to this network, see Chapter 7, “Router Feature Configuration.”
After configuring your router, you need to configure the PVC endpoint. For a
general configuration example, see the “Cisco 3640 Gateway Configuration
Example” section on page 74.
Voice Network
Figure 4-16 and Table 4-20 show a voice network with an 827-4V router and a
Cisco 3640 router as the VoIP gateway using H.323 signaling (H.323 gateway).
1 ATM Cisco
DSLAM 6400
Cisco
6400
PVC 0/14
10.10.10.36
255.255.255.0
Cisco 3640
3 2
4
74584
5
Cisco 3640
Callout
Number Description
1 Cisco 827-4V router serving as a voice gateway
2 Cisco 3640 router serving as a voice gateway
3 Ethernet 0 connection at address 172.17.1.36, subnet 255.255.255.0
4 Ethernet 1 connection at address 172.17.1.1, subnet 255.255.255.0
5 Cisco 3640 router serving as voice gatekeeper
The Cisco 3640 router is set up on the LAN as a gatekeeper, which provides
address translation and control access for the LAN for H.323 terminals and
gateways. The gatekeeper may provide other services to the H.323 terminals and
gateways, such as managing bandwidth and locating gateways.
In this scenario, the dial endpoint is the Cisco 3640 router, with an IP address of
172.17.1.36 and a subnet mask of 255.255.255.0. This configuration assumes a
single-zone setup so that both the Cisco 827-4V router and the Cisco 3640 router
are in the same zone.
Dialed numbers are stored by the VoIP session application in the 827-4V router,
in this case, H.323. After enough digits are accumulated to match a configured
destination pattern, the telephone number is mapped to a dial peer and session
target. In this configuration, the dial peer has a session target of RAS, which is a
protocol run between the H.323 session protocol gateway and gatekeeper.
The gatekeeper resolves the destination for each dialed number, and the call signal
is routed to the Cisco 3640 gateway, which assigns the call to a voice port.
The coder-decoder compression schemes (codecs) are enabled for both ends of the
connection, and QoS parameters are configured for IP precedence.
Configuration Tasks
To configure the voice scenario, you must first configure the data network and
then configure the voice network.
Command Task
Step 1 access-lists 101 permit ip any any Configure the access list.
precedence 5
Step 2 class-map voice Configure the class map.
Step 3 match access-group 101 Assign access list 101 to the class map.
Step 4 route-map data permit 10 Configure the route map.
Step 5 ip precedence routine Set the IP precedence.
Command Task
Step 6 policy-map mypolicy Configure a policy map.
Step 7 class voice Specify the class for queuing voice traffic.
Step 8 priority 176 Specify the bandwidth for queuing.1
Step 9 class class-default Configure the default class for all traffic but
voice traffic.
1. Total bandwidth for the policy map may not exceed 75 percent of the total PVC bandwidth.
Command Task
Step 1 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 2 ip address 20.20.20.20 255.255.255.0 Set the IP address and subnet mask for the
Ethernet interface.
Step 3 ip policy route-map data Configure the IP policy route map.
Step 4 ip route-cache policy Enable fast-switching policy routing.
Step 5 no shutdown Enable the Ethernet interface.
Step 6 exit Exit configuration mode for the Ethernet
interface.
Command Task
Step 1 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 2 ip address 10.10.10.20 255.255.255.0 Set the IP address and subnet mask for the
ATM interface.
Step 3 pvc 8/35 Create an ATM PVC for each end node with
which the router communicates.
Step 4 encapsulation aal5snap Specify the encapsulation type for the PVC.
Step 5 protocol ip 10.10.10.36 broadcast Specify the protocol broadcast for the IP
address.
Step 6 service-policy output mypolicy Specify the service policy for the ATM
interface.
Step 7 vbr-nrt 640 640 1 Specify the ATM service class.
Step 8 no shutdown Enable the ATM interface.
Step 9 exit Exit configuration mode for the ATM
interface.
Configuring EIGRP
Follow the steps below to configure EIGRP, beginning in global configuration
mode.
Command Task
Step 1 router eigrp 100 Enter router configuration mode, and enable
EIGRP on the router. The autonomous-system
number identifies the route to other EIGRP
routers and is used to tag the EIGRP
information.
Step 2 network number Specify the network number for each directly
connected network.
Step 3 exit Exit router configuration mode.
Command Task
Step 1 dial-peer voice number POTS Enter configuration mode for the dial peer
Step 2 destination-pattern string Define the destination telephone number
associated with the VoIP dial peer.
Step 3 port number Specify the port number.
Command Task
Step 1 dial-peer voice number VoIP Enter configuration mode for the dial peer.
Step 2 destination-pattern string Define the destination telephone number
associated with each VoIP dial peer.
Step 3 codec g711ulaw Specify a codec if you are not using the
default codec of g.729.
Step 4 ip precedence 5 Set the IP precedence.
Step 5 session target ras Specify a destination IP address for each dial
peer.
Configuration Examples
This section contains the following configuration examples:
• Cisco 827-4V Router Configuration Example
• Cisco 3640 Gateway Configuration Example
• Cisco 3640 Gatekeeper Configuration Example
The following is a configuration example for the Cisco 827-4V router portion of
the voice network scenario. You do not have to enter the commands marked
“default.” These commands appear automatically in the configuration file that is
generated when you use the show running-config command.
!
class-map voice
match access-group 101
!
route-map data permit 10
set ip precedence routine
!
policy-map mypolicy
class voice
priority 176
class class-default
fair-queue 16 (default)
!
ip subnet-zero
!
gateway
!
interface Ethernet0
ip address 20.20.20.20 255.255.255.0
no ip directed-broadcast (default)
ip route-cache policy
ip policy route-map data
!
interface ATM0
ip address 10.10.10.20 255.255.255.0
no ip directed-broadcast (default)
no atm ilmi-keepalive (default)
pvc 1/40
service-policy output mypolicy
protocol ip 10.10.10.36 broadcast
vbr-nrt 640 640 1
! 640 is the maximum upstream rate of ADSL
encapsulation aal5snap
!
bundle-enable
h323-gateway voip interface
h323-gateway voip id gk-twister ipaddr 172.17.1.1 1719
h323-gateway voip h323-id gw-820
h323-gateway voip tech-prefix 1#
!
router eigrp 100
network 10.0.0.0
network 20.0.0.0
!
ip classless (default)
no ip http server
!
access-list 101 permit ip any any precedence critical(5)
!
line con 0
exec-timeout 0 0
transport input none
stopbits 1
line vty 0 4
login
!
!
voice-port 1
local-alerting
!
voice-port 2
local-alerting
!
voice-port 3
local-alerting
!
voice-port 4
local-alerting
!
dial-peer voice 10 voip
destination-pattern .......
ip precedence 5
session target ras
!
dial-peer voice 1 pots
destination-pattern 4085258111
port 1
!
dial-peer voice 2 pots
destination-pattern 14085258222
port 2
!
dial-peer voice 3 pots
destination-pattern 14085258333
port 3
!
dial-peer voice 4 pots
destination-pattern 14085258444
port 4
!
end
The following is a configuration example for the Cisco 3640 gateway portion of
the voice network scenario. You do not have to enter the commands marked
“default.” These commands appear automatically in the configuration file that is
generated when you use the show running-config command.
!
class-map voice
match access-group 101
!
policy-map mypolicy
class voice
bandwidth 176
class class-default
fair-queue 16
!
ip subnet-zero
!
cns event-service server
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 1/1/0
!
voice-port 1/1/1
!
dial-peer voice 10 voip
destination-pattern .......
ip precedence 5
session target ras
!
dial-peer voice 1 pots
destination-pattern 12125253111
port 1/0/0
!
dial-peer voice 2 pots
destination-pattern 12125253222
port 1/0/1
!
dial-peer voice 3 pots
destination-pattern 12125253333
port 1/1/0
!
dial-peer voice 4 pots
destination-pattern 12125253444
port 1/1/1
!
process-max-time 200
gateway
!
interface Ethernet0/0
ip address 172.17.1.36 255.255.255.0
no ip directed-broadcast
h323-gateway voip interface
h323-gateway voip id gk-twister ipaddr 172.17.1.1 1719
h323-gateway voip h323-id gw-3640
h323-gateway voip tech-prefix 1#
!
interface ATM2/0
ip address 10.10.10.36 255.255.255.0
no ip directed-broadcast
no atm ilmi-keepalive
pvc 8/35
service-policy output mypolicy
protocol ip 10.10.10.20 broadcast
vbr-rt 1000 600 1
encapsulation aal5snap
!
router eigrp 100
network 10.0.0.0
network 172.17.0.0
!
no ip classless
no ip http server
!
access-list 101 permit ip any any precedence critical (5)
!
line con 0
exec-timeout 0 0
transport input none
line aux 0
line vty 0 4
login
!
!
end
The following is a configuration example for the H.323 gatekeeper portion of the
voice network scenario. You do not have to enter the commands marked “default.”
These commands appear automatically in the configuration file that is generated
when you use the show running-config command.
!
class-map voice
match access-group 101
!
!
policy-map mypolicy
class voice
bandwidth 176
class class-default
fair-queue 16
!
ip subnet-zero
!
ip dvmrp route-limit 20000
!
process-max-time 200
!
interface Ethernet0/0
ip address 172.28.9.83 255.255.255.0
no ip directed-broadcast (default)
!
interface Ethernet0/1
ip address 172.17.1.1 255.255.255.0
no ip directed-broadcast (default)
!
router eigrp 100
network 172.17.0.0
!
ip classless (default)
no ip http server
!
!
gatekeeper
zone local gk-router router.cisco.com 172.17.1.1
zone remote gk-sf1 cisco.com 179.15.2.2
zone remote gk-sf2 lucent.com 180.4.0.1
zone prefix gk-sf1 1415525....
zone prefix gk-sf2 1415527....
!
line con 0
exec-timeout 0 0
Overview of CAPI
The Common Application Programming Interface (CAPI) is an application
programming interface standard used to access ISDN equipment connected to
Basic Rate Interfaces (BRIs) and Primary Rate Interfaces (PRIs). Remote
Common Application Programming Interface (RCAPI) is the CAPI feature
configured remotely from a PC client. CAPI provides the following features:
• A standardized interface through which application programs use ISDN
drivers and controllers. One application can use one or more controllers.
Several applications can share one or more controllers.
• A selection mechanism that supports applications that use protocols at
different levels and standardized network access. To provide this support, an
abstraction from different protocol variables is performed by the software.
All connection-related data, such as connection state and display messages,
is available to the applications at any time.
The framing protocols supported by CAPI include High-Level Data Link Control
(HDLC), HDLC inverted, bit transparent (speech), and V.110
synchronous/asynchronous. CAPI integrates the following data link and network
layer protocols:
• Link Access Procedure on the D-channel (LAPD), in accordance with Q.921
for X.25 D-channel implementation
• Point-to-Point Protocol (PPP)
• ISO 8208 (X.25 DTE-DTE)
• X.25 DCE, T.90NL, and T.30 (fax Group 3)
CAPI Features
CAPI supports the following features:
• Basic call features, such as call setup and tear-down
• Multiple B channels for data and voice connections
• Multiple logical data link connections within a physical connection
• Selection of different services and protocols during connection setup and on
answering incoming calls
• Transparent interface for protocols above Layer 3
• One or more BRIs as well as PRI on one or more Integrated Services Digital
Network (ISDN) adapters
• Multiple applications
• Operating-system-independent messages
• Operating-system-dependent exchange mechanism for optimum operating
system integration
• Asynchronous event-driven mechanism, resulting in high throughput
• Well-defined mechanism for manufacturer-specific extensions
• Multiple supplementary services
When the router receives packets destined for one of the DCP clients on its BRI
port, the router formats the packet as a DCP message and sends it to the
corresponding client. The router supports all of the DCP messages in the
ISDN-DCP specifications defined by RVS-COM.
• T.30 for fax Group 3 (SFF file format [default], sending and receiving up to
14400 bits/sec with ECM option, modulations V.17, V.21, V.27ter, V.29)
• Analog modem (sending and receiving up to 14,400 bits/sec, modulations
V.21, V.22, V.22bis, V.23, V.32, V.32bis)
Supported Applications
ISDN-DCP supports CAPI and non-CAPI applications. Applications are
supported that use one or two B channels for data transfer, different HDLC-based
protocols, Euro file transfer, or G4 fax; also supported are applications that send
bit-transparent data such as A/Mu law audio, group 3 faxes, analog modem, or
analog telephones.
Requirements
Before you can enable the RCAPI feature on the Cisco 800 series router, the
following requirements must be met:
• Cisco 800 series software with RCAPI support is installed on the router.
• CAPI commands are properly configured on the router.
• Both the CAPI local device console and RCAPI client devices on the LAN
are correctly installed and configured with RVS-COM client driver software.
Configuring RCAPI
The following procedure provides step-by-step instructions for configuring
RCAPI on the Cisco 800 series router:
Step 2 Set the switch type. In the following example, the switch type is set to European
Telecommunication Standards Institute (ETSI).
router(config)# isdn switch-type basic-net3
Step 3 Enter the RCAPI directory number assigned by the ISDN provider for the device.
For example:
router(config)# rcapi number 12345
Step 4 Optional. Perform this step only if you wish to specify a port number for RCAPI
functions. Otherwise, the default port 2578 is used. Configure the same number
on both the router and client PC. For example:
router(config)# rcapi server port 2000
Step 6 Set the switch type for the BRI0 interface. In the following example, the switch
type is set to ETSI.
router(config-if)# isdn switch-type basic-net3
Step 7 Set the modem as the default handler for incoming voice calls.
router(config-if)# isdn incoming-voice modem
Step 8 Change to privileged EXEC mode either by pressing Ctrl-Z or by entering exit
twice, once at the interface mode prompt and again at the global configuration
mode prompt.
router(config-if)# exit
router(config)# exit
router#
Step 9 Optional. Enter the following if you wish to display RCAPI status.
router# show rcapi status
Step 10 Optional. In privileged EXEC mode, start the debug program to run in the
background.
router# debug rcapi events
Step 11 If required, at each remote device console, change to global configuration mode.
Repeat Step 2 through Step 10 to configure that device.
The term telephone port refers to the physical port on the router back panel. The
term telephone interface refers to a logical interface that you must configure to
make an analog telephone or fax connected to a telephone port work properly.
This chapter describes how to configure standard and advanced features of the
those Cisco 800 series routers supporting telephone features (Cisco 803, 804, and
813 routers). These routers support push-button analog telephones only; the Cisco
routers do not support rotary telephones. This chapter also describes how to use
the connected devices.
Physical Characteristics
This section discusses the following:
• Physical characteristics that you must configure
• Tones that some users might need to configure
• Ringer equivalent number (REN)
Command Purpose
Step 1 pots country country Enter the pots country ? command to get a
list of supported countries and the code you
must input to indicate a particular country.
By specifying a country, you are
configuring your telephone to use
country-specific default settings for each
physical characteristic. If you need to
change a country-specific default setting,
you can use the optional commands
described in this table.
Step 2 pots line-type Optional. Set the line type. Line type 1 runs
{type1 | type2 | type3} at 600 ohms, line type 2 runs at 900 ohms,
and line type 3 runs at 300 or 400 ohms.
Lines in the U.S. typically run at 600 ohms
(line type 1).
Step 3 pots dialing-method Optional. Set the dialing method. If you
{overlap | enblock} select overlap, the router transmits each
digit dialed in a separate message. If you
select enblock, the router collects all digits
dialed and transmits in one message. To
interrupt collection and transmission of
dial-string digits, enter pound sign (#) or
stop dialing digits until a timer runs out.
Step 4 pots disconnect-supervision Optional. Set how the router notifies the
{osi | reversal} connected device when calling party has
hung up. Japan typically uses the reversal
option. Most other countries use the osi
option.
Step 5 pots encoding {alaw | ulaw} Optional. Set the pulse code modulation
(PCM) encoding scheme. Europe typically
uses the alaw option. North America
typically uses the ulaw option.
Command Purpose
Step 6 pots tone-source Optional. Set who supplies dial, ringback,
{local | remote} and busy tones. If you select local, the
router supplies the tones. If you select
remote, the telephone switch provides the
tones. For more information, refer to the
“Tones for NET3 Switch” section on
page 6-4.
Step 7 pots ringing-freq Optional. Set the frequency at which
{20Hz | 25Hz | 50Hz} telephone ports ring.
Step 8 pots disconnect-time interval Optional. If a connected device, such as an
answering machine, fails to detect that a
calling party has hung up, you can adjust
the interval at which selected disconnect
supervision method is applied. Interval is
from 50 to 2000 milliseconds.
Step 9 pots silence-time interval Optional. If a connected device, such as an
answering machine, fails to detect that a
calling party has hung up, you can adjust
the interval of silence after a hang-up.
Interval is from 0 to 10 seconds.
Step 10 pots distinctive-ring-guard- Optional. Set the delay, in milliseconds (0
time milliseconds to 1000), before a telephone port can be
rung after a previous call is disconnected.
For more information, refer to the
“Distinctive Ringing” section on
page 6-11.
Step 11 show pots status Optional. Display settings of physical
characteristics as well as other information
on telephone interfaces.
Note This command applies only to ISDN lines connected to a NET3 switch.
If the pots dialing-method command is set to enblock, the router provides the
internal dial tone.
REN
You can connect multiple devices (analog telephone or fax machine) to a router
telephone port. The number of devices that you can connect depends on the
following:
• REN of the telephone port (five).
• REN of each device that you plan to connect. (You can usually find the REN
on the bottom of a device.)
If the REN of each device you plan to connect is one, then you can connect a
maximum of five devices to that particular telephone port.
Command Purpose
Step 1 dial-peer voice tag pots Set up tag number (1 through 6) for dial
peer.
Step 2 destination-pattern ldn Specify local ISDN directory number
assigned to telephone interface. Do not
specify an area code.
Step 3 port port-number Specify number (1 or 2) associated with
telephone port.
Step 4 no call-waiting Optional. Disable call waiting.
Step 5 ring cadence-number Optional. Set up distinctive ring (0
through 2). For more information, see the
“Distinctive Ringing” section on
page 6-11.
Step 6 show dial-peer voice [tag] Optional. Display all or a particular
dial-peer configuration (1 through 6).
For example, if you have connected one voice device (555-1111) to port 1 and
another (555-2222) to port 2, you can create two dial peers. The following output
example shows two dial peers:
dial-peer voice 1 pots
destination-pattern 5551111
port 1
no call-waiting
ring 0
dial-peer voice 2 pots
destination-pattern 5552222
port 2
no call-waiting
ring 0
When a caller dials 555-1111, the call is routed to port 1. When a caller dials
555-2222, the call is routed to port 2. If the dial peers are not created, calls to both
numbers are routed to port 1.
Note Make sure that all ISDN directory numbers associated with a service profile
identifier (SPID) are associated with one port. For example, if both 555-1111 and
555-2222 are associated with SPID 1 and you associate 555-1111 to port 1 and
555-2222 to port 2, you will not be able to make calls on ports 1 and 2
simultaneously.
Command Purpose
Step 1 interface bri0 Specify parameters for the WAN interface.
Step 2 isdn incoming-voice modem Specify that incoming ISDN voice calls are
forwarded to devices connected to
telephone ports.
Note If you do not enter the isdn incoming-voice modem command, the router rejects
incoming ISDN voice calls.
Command Purpose
isdn voice-priority Configure ISDN voice priority for each
local-directory-number ISDN directory number.
{in | out} {always | conditional |
off}
If you have multiple ISDN directory numbers associated with a SPID, then the
outgoing voice priority that you set for any of these directory numbers applies to
the other numbers.
For example, if you enter the following command, the outgoing voice priority for
all directory numbers specified in the isdn spid1 command is set to conditional:
router(config-if)# isdn spid1 0 4085551111 4085552222 4085553333
router(config-if)# isdn voice-priority 5551111 out conditional
Table 6-1 describes the possible data call scenarios, what happens when a voice
call comes in, and what happens when you place an outgoing voice call with a
particular configuration.
The setting of the pots dialing-method command determines whether you hear a
busy signal if a data call cannot be bumped when you are trying to make an
outgoing call. If the setting is overlap, you hear a busy signal when you pick up
the handset. If the setting is enblock, you hear a dial tone initially, then a busy
signal.
Note This section applies only to analog telephone services in the U.S.
In some tariff areas, voice calls are less expensive than data calls. If this is the case
in your tariff area, the Cisco 800 series routers support incoming and outgoing
data over voice (DOV) calls. DOV calls are data calls made over the ISDN line
using voice bearer capability (VBC).
The router recognizes the difference between a data call and a voice call.
Incoming data calls are routed to the LAN over the Ethernet port. If a telephone
interface has been configured for DOV, incoming data calls made with VBC are
routed to the LAN over the Ethernet port. Figure 6-1 and Table 6-2 illustrate a
data call being routed to the LAN.
Incoming voice calls are forwarded to the analog device over the analog telephone
port, as shown in Figure 6-2 and Table 6-3.
2
74937
1 4
Callout
Number Description
1 Analog telephone
2 ISDN BRI line with VBC
3 Central office switch
4 Ethernet LAN
3
1 74938
Callout
Number Description
1 Analog telephone
2 ISDN BRI line with VBC
3 Router
4 Ethernet LAN
Note When the router is configured for DOV, ISDN BRI calls are made with VBC,
which has a data rate of 56 kbps, instead of the usual ISDN BRI data rate of
64 kbps.
Use the following command to configure the router to accept incoming DOV
calls:
isdn incoming-voice data 56
Follow these steps to configure the router to place outgoing DOV calls:
Command Purpose
Step 1 class voice number Create a dialer map.
Step 2 map-class dialer voice Define a class of shared configuration
parameters for outgoing calls.
Step 3 dialer voice-call Configure router to make outgoing DOV
calls.
Step 4 dialer isdn speed 56 Specify bit rate used on B channel
associated with specified map class.
Distinctive Ringing
A ringing cadence is a pattern of a ringing and a quiet period. There are two types
of ringing cadences: a primary ringing cadence and distinct ringing. The primary
cadence is determined by the country where your router is located. In addition to
the primary cadence, you can configure up to two distinctive rings on a telephone
port.
Because the router associates a distinctive ring with the ISDN directory number
assigned to an interface, you must configure a distinctive ring with a dial peer. For
information on dial peers and how to configure them, see the “Creating Dial
Peers” section on page 6-4.
Note Generally your telephone service provider assigns one ISDN directory number for
each SPID. You must have one ISDN directory number for each distinctive ring
that you set up. Therefore, if you want to set up two distinctive rings, you must
request an additional ISDN directory number from your telephone service
provider.
To configure the ringing cadence, insert the following commands into a dial-peer
configuration:
ring cadence-number
where cadence-number can be 0, 1, or 2.
• Type 0 is a primary ringing cadence—default ringing cadence for country
your router is located in.
• Type 1 is a distinctive ring—0.8 seconds on, 0.4 seconds off, 0.8 seconds on,
4 seconds off.
• Type 2 is a distinctive ring—0.4 seconds on, 0.2 seconds off, 0.4 seconds on,
0.2 seconds off, 0.8 seconds on, 4 seconds off.
By default, the ring cadence is set to 0, which means that the interface uses the
primary ringing cadence.
You can also insert the following command syntax into a dial-peer configuration:
pots distinctive-ring-guard-time milliseconds
where milliseconds can be a number from 50 to 1000. This command configures
the delay, in milliseconds, before a telephone port can be rung after a previous call
is disconnected. The default is no delay.
Caller Identification
In addition to an analog telephone or fax machine, North American users can
connect a caller ID device to the router telephone ports. This device displays the
telephone numbers of incoming callers. The Cisco 800 series routers support the
following caller ID devices:
• AT&T 25
• AT&T 85 Plus
• CIDCO
• Fans Callscreener
• GE Caller ID with phone
• GE Caller ID without phone
• Northwestern Bell Phone, Bell Phone
• Radio Shack Caller ID System 350
The Cisco 800 series routers do not support the following devices:
• Southwestern Bell Freedom Phone
• TTY System
Step 2 Send the entire set of digits to the switch by using one of the following methods:
• Press the pound key (#) on the telephone keypad.
• Wait 12 seconds without entering any digits. After 12 seconds, the router
sends the set of digits to the switch.
Note This command applies only to ISDN lines connected to an NTT switch.
You can disable this function if a telephone number you are dialing requires the
pound key (#) as one of the digits. After entering the **98# command, wait for a
dial tone and then enter the digits, including the pound key. To send the digits to
the switch, wait 6 seconds without entering any digits.
The end-of-call function automatically resumes for the next call.
Step 1 Put the active call on hold, and get a dial tone by quickly pressing the telephone
receiver (flash) button once, and then entering **95# on the telephone keypad.
Step 2 Make the second call.
Step 3 Toggle between the two calls by quickly pressing the flash button.
If you hang up with a call still on hold, the phone rings to remind you of the
outstanding call. Pick up the handset to reconnect to the call.
Call Waiting
For this feature to work, you must request it when you order your ISDN line. For
information on ordering your ISDN line, see Appendix D, “Provisioning an ISDN
Line.”
By default, call waiting is enabled. You can disable it permanently by using the
no call-waiting command. (You might want to disable it for fax machines.)
Because the router associates call waiting with the ISDN directory number
assigned to a telephone interface, you should disable call waiting at the same time
that you are configuring a dial peer. For information on dial peers and how to
configure them, refer to the “Creating Dial Peers” section on page 6-4.
To disable call waiting on a per-call basis, enter **99# on the telephone keypad.
During an active voice call, a call-waiting tone sounds if another call comes in.
Subsequent tones sound at 10-second intervals until the incoming caller hangs up
or until you answer the call. During this time, the incoming caller hears ringing.
When you hear the call-waiting tone, you can do one of the following:
• Put the current call on hold, and answer the incoming call
• Hang up the current call, and answer the new call.
To put the current call on hold and answer the incoming call, quickly press the
telephone receiver (flash) button once. Press this button again to go back to the
current call.
Step 1 Put the first party on hold and get a dial tone by quickly pressing the telephone
receiver (flash) button once.
Step 2 Dial the second party.
Step 3 Add the first party to the call by quickly pressing the flash button.
Call Transfer
For this feature to work, you must request it when you order your ISDN line. For
information on ordering your ISDN line, see Appendix D, “Provisioning an ISDN
Line.”
If you are connected to a National ISDN-1 (NI1) or a Northern Telecom DMS-100
Custom switch, you might need to activate this feature, using the following
command syntax:
isdn transfer-code range
The range is from 0 to 999. The default code is 61. Your telephone service
provider should provide a code when you order this feature; if a code other than
61 is provided, you need to reconfigure the code by using the isdn transfer-code
command.
Otherwise, you do not need to configure the router to make this feature work.
You can transfer an incoming or outgoing voice call to another party. To transfer
a call, do the following:
Note If you are connected to an NTT switch, you will not be able to transfer an outgoing
call.
Step 1 Put the first party on hold, and get a dial tone by quickly pressing the telephone
receiver (flash) button once.
Step 2 Dial the second party to which you want to transfer the call.
Step 3 While still connected to the second party, hang up.
Hanging up connects the first and second parties. Instead of doing Step 3, you can
also create a three-way call conference by quickly pressing the flash button once.
If the call to the second party fails, you can return to the first party by doing one
of the following:
• Quickly pressing the telephone receiver (flash) button once
• Hanging up
If you hang up, the telephone rings to indicate that the first party is still on hold.
Call Forwarding
The call forwarding feature works for Sweden and Finland only. For this feature
to work, you must request it when you order your ISDN line. For information on
ordering your ISDN line, see Appendix D, “Provisioning an ISDN Line.”
The router supports the following call forwarding features:
• Call forwarding unconditional (CFU)—you can forward all incoming calls to
another telephone number.
• Call forwarding no reply (CFNR)—you can forward incoming calls that are
not answered within a defined period to another telephone number.
• Call forwarding busy (CFB)—you can forward incoming calls that get a busy
signal to another telephone number.
To make sure that the router accepts the activation and deactivation of the call
forwarding features using the telephone keypad, use the pots country country
command in global configuration mode. The country variable is the country that
your router is in. Enter the pots country ? command to get a list of supported
countries and the code you must enter to indicate a particular country.
To activate call forwarding unconditional, call forwarding no reply, or call
forwarding busy, follow these steps:
Your telephone service provider should provide the number for each call
forwarding feature. For example, to forward a call to 408-555-2222, enter the
following:
*21*4085552222#
Your telephone service provider should provide the number for each call
forwarding feature. For example, to deactivate call forwarding, enter the
following:
#21#
Note In the U.S., the call forwarding variable (CFV) feature is available with the NI1
capability package EZ-1. With CFV, you can forward incoming calls. You can turn
this feature on or off through access codes supplied by your telephone service
provider.
where port is the port number 1 or 2, and number is the telephone number to dial.
Note The router does not turn off dual tone multifrequency (DTMF) detection from
the telephone when you enter the POTS dial command. If you do not terminate
the number variable with a pound (#) character, you can complete the call by
using the telephone key pad.
Output Example
The following is an example of the show pots csm command screen output:
router# show pots csm 1
POTS PORT: 1
router#
Entering this command activates events by which your dial application can
determine the progress of calls to and from the ports.
or
hh:mm:ss: EVENT_FROM_ISDN:dchan_idb=0x???????, call_id=0x????, ces=?
bchan=0x????????, event=0x?, cause=0x??
where:
• hh:mm:ss is a timestamp in hours, minutes, and seconds.
• CSM_STATE is one of the call switching module (CSM) states listed in
Table 6-4.
• call id is a hexadecimal value from 0x00 to 0xFF.
• port is telephone port 1 or 2.
• EVENT_FROM_ISDN is a CSM event. Table 6-5 shows a list of CSM events.
• dchan_idb is an internal data structure address.
• ces is the connection end point suffix used by ISDN.
• bchan is the channel used by the call. A value of 0xFFFFFFFF indicates that
a channel is not assigned.
• event is represented by a hexadecimal value that is translated into a CSM
event. Table 6-6 shows a list of events and the corresponding CSM events.
• cause is represented by a hexadecimal value that is given to call-progressing
events. Table 6-7 shows a list of cause values and definitions.
CSM States
Table 6-4 shows the values for CSM states.
CSM Events
Table 6-5 shows the values for CSM events.
Events
Table 6-6 shows the values for events that are translated into CSM events.
Hexadecimal
Value Event CSM Event
0x0 DEV_IDLE CSM_EVENT_ISDN_DISCONNECTED
0x1 DEV_INCALL CSM_EVENT_ISDN_CALL
0x2 DEV_SETUP_ACK CSM_EVENT_ISDN_SETUP_ACK
0x3 DEV_CALL_PROC CSM_EVENT_ISDN_PROC
0x4 DEV_CONNECTED CSM_EVENT_ISDN_CONNECTED
0x5 DEV_CALL_PROGRESSING CSM_EVENT_ISDN_CALL_PROGRESSING
0x6 DEV_HOLD_ACK CSM_EVENT_ISDN_HARD_HOLD
0x7 DEV_HOLD_REJECT CSM_EVENT_ISDN_HARD_HOLD_REJ
0x8 DEV_CHOLD_ACK CSM_EVENT_ISDN_CHOLD
0x9 DEV_CHOLD_REJECT CSM_EVENT_ISDN_CHOLD_REJ
0xa DEV_RETRIEVE_ACK CSM_EVENT_ISDN_RETRIEVED
0xb DEV_RETRIEVE_REJECT CSM_EVENT_ISDN_RETRIEVE_REJ
0xc DEV_CONFR_ACK CSM_EVENT_ISDN_CONFERENCE
0xd DEV_CONFR_REJECT CSM_EVENT_ISDN_CONFERENCE_REJ
0xe DEV_TRANS_ACK CSM_EVENT_ISDN_TRANSFERRED
0xf DEV_TRANS_REJECT CSM_EVENT_ISDN_TRANSFER_REJ
Cause Values
Table 6-7 shows cause values that are assigned only to call-progressing events.
Hexadecimal
Value Cause Definitions
0x01 UNASSIGNED_NUMBER
0x02 NO_ROUTE
0x03 NO_ROUTE_DEST
0x04 NO_PREFIX
0x06 CHANNEL_UNACCEPTABLE
0x07 CALL_AWARDED
0x08 CALL_PROC_OR_ERROR
0x09 PREFIX_DIALED_ERROR
0x0a PREFIX_NOT_DIALED
0x0b EXCESSIVE_DIGITS
0x0d SERVICE_DENIED
0x10 NORMAL_CLEARING
0x11 USER_BUSY
0x12 NO_USER_RESPONDING
0x13 NO_USER_ANSWER
0x15 CALL_REJECTED
0x16 NUMBER_CHANGED
0x1a NON_SELECTED_CLEARING
0x1b DEST_OUT_OF_ORDER
0x1c INVALID_NUMBER_FORMAT
0x1d FACILITY_REJECTED
0x1e RESP_TO_STAT_ENQ
0x1f UNSPECIFIED_CAUSE
Hexadecimal
Value Cause Definitions
0x22 NO_CIRCUIT_AVAILABLE
0x26 NETWORK_OUT_OF_ORDER
0x29 TEMPORARY_FAILURE
0x2a NETWORK_CONGESTION
0x2b ACCESS_INFO_DISCARDED
0x2c REQ_CHANNEL_NOT_AVAIL
0x2d PRE_EMPTED
0x2f RESOURCES_UNAVAILABLE
0x32 FACILITY_NOT_SUBSCRIBED
0x33 BEARER_CAP_INCOMPAT
0x34 OUTGOING_CALL_BARRED
0x36 INCOMING_CALL_BARRED
0x39 BEARER_CAP_NOT_AUTH
0x3a BEAR_CAP_NOT_AVAIL
0x3b CALL_RESTRICTION
0x3c REJECTED_TERMINAL
0x3e SERVICE_NOT_ALLOWED
0x3f SERVICE_NOT_AVAIL
0x41 CAP_NOT_IMPLEMENTED
0x42 CHAN_NOT_IMPLEMENTED
0x45 FACILITY_NOT_IMPLEMENT
0x46 BEARER_CAP_RESTRICTED
0x4f SERV_OPT_NOT_IMPLEMENT
0x51 INVALID_CALL_REF
0x52 CHAN_DOES_NOT_EXIST
0x53 SUSPENDED_CALL_EXISTS
Hexadecimal
Value Cause Definitions
0x54 NO_CALL_SUSPENDED
0x55 CALL_ID_IN_USE
0x56 CALL_ID_CLEARED
0x58 INCOMPATIBLE_DEST
0x5a SEGMENTATION_ERROR
0x5b INVALID_TRANSIT_NETWORK
0x5c CS_PARAMETER_NOT_VALID
0x5f INVALID_MSG_UNSPEC
0x60 MANDATORY_IE_MISSING
0x61 NONEXISTENT_MSG
0x62 WRONG_MESSAGE
0x63 BAD_INFO_ELEM
0x64 INVALID_ELEM_CONTENTS
0x65 WRONG_MSG_FOR_STATE
0x66 TIMER_EXPIRY
0x67 MANDATORY_IE_LEN_ERR
0x6f PROTOCOL_ERROR
0x7f INTERWORKING_UNSPEC
Call Scenario 1
In this call scenario, port 1 is on-hook, the application dial is set to call
4085552221, and the far end successfully connects. The following example shows
the Cisco IOS command:
router# test pots 1 dial 4085552221#
router#
The following screen output shows an event indicating that port 1 is being used
by the dial application:
01:0, port = 1
The following screen output shows events indicating that the CSM is receiving the
application digits of the number to dial:
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
01:58:27: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
The following screen output shows that the telephone connected to port 1 is off
hook:
01:58:39: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1
The following screen output shows a call-proceeding event pair indicating that the
router ISDN software has sent the dialed digits to the ISDN switch:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0x0,
event=0x3, cause=0x0
01:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8004, port = 1
The following screen output shows the call-progressing event pair indicating that
the telephone at the far end is ringing:
01:58:40: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF,
event=0x5, cause=0x0
01:58:40: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8004, port
= 1
The following screen output shows a call-connecting event pair indicating that the
telephone at the far end has answered:
01:58:48: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF,
event=0x4, cause=0x0
01:58:48: CSM_PROC_CONNECTING: CSM_EVENT_ISDN_CONNECTED, call id = 0x8004, port = 1
The following screen output shows a call-progressing event pair indicating that
the telephone at the far end has hung up, and the calling telephone is receiving an
in-band tone from the ISDN switch:
01:58:55: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 01:58:55:
CSM_PROC_CONNECTED: CSM_EVENT_ISDN_CALL_PROGRESSING,
call id = 0x8004, port = 1
The following screen output shows that the telephone connected to port 1 has
hung up:
01:58:57: CSM_PROC_CONNECTED: CSM_EVENT_VDEV_ONHOOK, call id = 0x8004, port = 1
The following screen output shows an event pair indicating that the call has been
terminated:
01:58:57: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8004, ces=0x1 bchan=0xFFFFFFFF,
event=0x0, cause=0x0
01:58:57: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8004,
port = 1
813_local#
Call Scenario 2
In this scenario, port 1 is on-hook, the application dial is set to call 4085552221,
and the destination number is busy. The following example shows the Cisco IOS
command:
router# test pots 1 dial 4085552221#
router#
The following screen output shows that your dial application is using port 1:
01:59:42: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1
The following screen output shows the events indicating that the CSM is receiving
the application digits of the number to call:
01:59:42: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id =
0x0, port = 1
The following screen output shows an event indicating that the telephone
connected to port 1 is off-hook:
01:59:52: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_OFFHOOK, call id = 0x0, port = 1
The following screen output shows a call-proceeding event pair indicating that the
telephone at the far end is busy:
01:59:52: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0x0,
event=0x3, cause=0x11
01:59:52: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_PROC, call id = 0x8005, port = 1
The following screen output shows a call-progressing event pair indicating that
the calling telephone is receiving an in-band busy tone from the ISDN switch:
01:59:58: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0xFFFFFFFF,
event=0x5, cause=0x0
01:59:58: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_ISDN_CALL_PROGRESSING, call id = 0x8005, port
= 1
The following screen output shows an event indicating that the calling telephone
has hung up:
02:00:05: CSM_PROC_ENBLOC_DIALING: CSM_EVENT_VDEV_ONHOOK, call id = 0x8005, port = 1
The following screen output shows an event pair indicating that the call has
terminated:
02:00:05: EVENT_FROM_ISDN:dchan_idb=0x280AF38, call_id=0x8005, ces=0x1 bchan=0xFFFFFFFF,
event=0x0, cause=0x0
02:00:05: CSM_PROC_NEAR_END_DISCONNECT: CSM_EVENT_ISDN_DISCONNECTED, call id = 0x8005,
port = 1
Call Scenario 3
In this call scenario, port 1 is on-hook, the application dial is set to call
4086661112, the far end successfully connects, and the command test pots
disconnect terminates the call.
router# debug pots csm
router# test pots 1 dial 4086661112
router#
The following screen output follows the same sequence of events as shown in Call
Scenario 1:
1d03h: CSM_PROC_IDLE: CSM_EVENT_VDEV_APPLICATION_CALL, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
1d03h: CSM_PROC_APPLIC_DIALING: CSM_EVENT_VDEV_DIGIT, call id = 0x0, port = 1
The test pots disconnect command disconnects the call before you have to put
the telephone back on hook.
1d03h: CSM_PROC_CONNECTING: CSM_EVENT_VDEV_APPLICATION_HANGUP_CALL, call id = 0x8039,
port = 1
1d03h: EVENT_FROM_ISDN:dchan_idb=0x2821F38, call_id=0x8039, ces=0x1
bchan=0xFFFFFFFF, event=0x0, cause=0x0
Caller ID Display
This feature displays the caller ID information provided by the INS-NET-64
switch on analog telephones connected to the PHONE 1 or 2 port of the Cisco 813
router.
Note The caller ID display feature works only on Japanese language display
telephones.
where number is the telephone number to block. You can use a period (.) as a
wildcard to substitute for one or more numbers to block. For example, to block all
numbers ending in the number 5, you can enter the following:
block-caller .5
You can enter up to ten caller ID numbers for each LDN. However, you cannot
exceed the maximum of ten numbers. You must remove one or more numbers
before you can add any new numbers to block.
If no caller ID numbers are specified for a particular LDN, all voice calls to that
LDN are accepted.
The following example configures the router to block calls from the caller whose
caller ID number is 4085551234:
router(config)# pots country jp
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# block-caller 4085551234
To display caller IDs entered for call blocking, use the show run command. The
following is an example of caller ID configuration output:
!
dial-peer voice 1 pots
no forward-to-unused-port
call waiting
ring 0
registered-caller ring 1
port 1
block-caller 4085551234
block-caller 4085552345
The call waiting defaults to remote if this feature is not configured. In that case,
the call holding pattern follows the settings of the service provider rather than
those of the router.
To display the call waiting setting, use the show run or show pots status
command.
Note The ISDN call waiting service will be used if it is available on the ISDN line
connected to the router even if local call waiting is configured on the router. If
ISDN call waiting is used, the local call waiting configuration on the router is
ignored.
The following example configures the call waiting style to follow the local call
holding pattern that is set on the router:
router(config)# pots country jp
router(config)# pots call-waiting local
E Ya Yo
This feature conceals the caller ID of the outgoing call from the receiving device.
Configuring E Ya Yo
According to the NTT specification, dialing the prefix 184 followed by the
destination device number will render your caller ID invisible to the receiving
party.
Voice Warp
The voice warp feature on the INS-NET-64 switch forwards all incoming calls for
a terminal device to another device. Voice warp registration, activation, and
deactivation requests are sent to the switch for each LDN. The Cisco 813 router
supports the registration, activation, and deactivation requests for any device
attached to the PHONE 1 or 2 port. The forwarding function itself is performed
by the INS-NET-64 switch.
During the registration phase of the device, you can:
• Create a list of forwarding destination numbers and to select one as the active
destination.
• Specify whether an announcement will be made to the caller or forwarding
device, or both, at the time the call is forwarded.
• Set the no-answer timer parameter from 5 to 60 seconds at 5-second intervals.
This setting affects the redirection of calls once the voice warp feature is
activated.
During the activation phase of this feature, you determine whether calls are
redirected all the time or only if the receiving device is busy or does not answer
within the no-answer time period specified during registration.
This feature can be deactivated after its registration and activation phases.
Note The Cisco 813 router supports this feature for one LDN only. If more than one
LDN is configured, only the primary LDN can be used with this feature.
Note Activating the voice warp feature disables the support for the call waiting
feature for both local and network calls.
Note The Cisco 813 router supports this feature for one LDN only. If more than one
LDN is configured, only the primary LDN can be used with this feature.
Note Activating the voice select warp feature disables the support for the call
waiting feature for both local and network calls.
Nariwake
Nariwake checks for caller IDs that you register for each LDN and presents a
distinctive ring to the telephone port receiving the incoming call if a match is
detected. The Cisco 813 router provides three different ring cadences that you can
set for calls from registered and unregistered callers. The number of caller IDs
you can register for each LDN at one time is defined by the INS-NET-64 switch
and not by the router.
You can register this feature with the list of caller IDs for each LDN, cancel the
registration for the LDN, or get registration information from the INS-NET-64
switch.
Note The Cisco 813 router supports this feature for one LDN only. If more than one
LDN is configured, only the primary LDN can be used with this feature.
Note Activating the Nariwake feature disables support for the call waiting feature
for both local and network calls.
Configuring Nariwake
To configure the ring cadence for this feature, use the registered-caller ring
command in the dial-peer configuration mode:
registered-caller ring cadence
Note If your ISDN line is provisioned for the I Number or dial-in services, you must
also configure a dial-peer using the Cisco IOS command destination-pattern
not-provided. Either port 1 or 2 can be configured under this dial-peer. The
router will then forward the incoming call to the voice port 1 using the default
cadence 0. See the “Example of Nariwake Configuration” section for details.
To hear the caller ID registration details, use the keypad dialing sequence
specified in the NTT user manual. Information is transmitted only by voice.
The following example sets the ring cadence for registered callers to 2.
router(config)# pots country jp
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# registered-caller ring 2
To display the Nariwake ring cadence setting, use the show run command. The
following is an example of screen output for Nariwake configuration:
dial-peer voice 1 pots
no forward-to-unused-port
call waiting
ring 0
registered-caller ring 2
port 1
destination-pattern not-provided
block-caller 4085552222
block-caller 4085553333
Trouble-Call Blocking
The trouble-call blocking feature causes all future incoming calls from a
particular telephone number to be rejected by the network if the recipient activates
this feature after the initial call. As the recipient of the call, you are not required
to specify the telephone number of the caller and will not be notified of
subsequent connection attempts from that telephone number. When this feature is
activated, the caller will hear a standard telephone announcement and a
disconnect message. For information about the announcement or message, see
your NTT user manual.
The number of callers that you can block is defined by the service provider at the
time the service is provisioned. If you request an additional telephone number to
block after having reached the limit, the oldest number is discarded (unblocked)
before the latest telephone number is registered for blocking.
Note To activate this feature, you must dial the keypad sequence within 60 seconds
after you hang up from the call. You will be notified over the telephone
whether or not the activation is successful.
You can disable this feature for only the last registered number or for all numbers
registered for blocking. You will be notified over the telephone whether or not the
cancellation is successful.
You can request to hear the results of the trouble-call blocking. You will hear the
number of attempted calls that were blocked for the past two months.
I Number
This feature supports the use of multiple terminal devices with one subscriber
line. The telephone numbers of the subscriber line and router ports are assigned
by the service provider. Calls coming into any of the assigned numbers will route
through the same subscriber line to the terminal device attached to the target port.
Configuring I Number
To configure this feature, perform the following steps:
Step 1 Use the isdn i-number command in the BRI interface configuration mode to
configure the I number:
isdn i-number number ldn
where number is a value from 1 to 3 (based on NTT specifications) and ldn is your
local directory number configured under the dial-peer. The number variable maps
the I number to one of the LDNs.
Step 2 Use the destination-pattern command to set the dial-peer destination pattern to
the corresponding LDN:
destination-pattern ldn
The following example shows screen output for two LDNs configured under
interface BRI0:
router(config)# interface bri0
router(config-if)# isdn i-number 1 5551234
router(config-if)# isdn i-number 2 5556789
router(config-if)# exit
router(config)# dial-peer voice 1 pots
router(config-dial-peer)# destination-pattern 5551234
router(config-dial-peer)# exit
router(config)# dial-peer voice 2 pots
router(config-dial-peer)# destination-pattern 5556789
caller-id
no forward-to-unused-port
call-waiting
ring 0
no silent-fax
registered-caller ring 1
port 2
volume 3
destination-pattern 7773100
!
• Call holding
• Call transfer
• Call forwarding
• Call waiting
Note Caller ID for the Net3 switch is always enabled, provided that the POTS
country type is correctly defined. Caller ID cannot be disabled using the
Cisco IOS command-line interface (CLI).
To verify whether caller ID is enabled, use the show pots status command. The
following is an example of the output from that command:
router# show pots status
Country:Denmark
Note If you had configured call forwarding for a POTS port and the router finds that
a dial peer is also configured for that port, call forwarding works only for the
number defined in the destination-pattern dial-peer command and ignores all
other numbers for that telephone. If the router does not find a dial peer, or if
the destination pattern is not defined, call forwarding works for all numbers
allocated to the ISDN line.
Step 1 Enable and select the call forwarding method. See the “Configuring the Call
Forwarding Method” section on page 6-49.
Step 2 Configure your call forwarding service, depending on which method you
previously selected:
• Functional method—Enter DTMF commands on the telephone keypad. For
more information, see the “Configuring the Call Forwarding Service” section
on page 6-49.
• Keypad method—Follow the instructions in your Net3 switch documentation.
Note Use the pots forwarding-method command to configure only Net3 switch
types. This command does not work for other switch types. This feature is
disabled in the default setting.
The following example configures the call forwarding feature to give control to
the router:
router# configure terminal
router(config)# pots forwarding-method functional
where number is the telephone number to which your calls are forwarded
Deactivate CFU #21#
where number is the telephone number to which your calls are forwarded
Deactivate CFNR #61#
where number is the telephone number to which your calls are forwarded
Deactivate CFB #67#
You should hear a dial tone after you enter the DTMF commands if the call
forwarding service is successfully configured. If you hear a busy signal, the
command is invalid or the switch does not support that service.
Configuring CLIR
Configure CLIR by following these steps:
Step 1 Ensure that CLIR in temporary mode is enabled in the Net3 switch.
Step 2 Remove the handset and enter **31# on the keypad.
Step 3 Listen for the dial tone, and make your call.
Step 4 Repeat Steps 2 and 3 for each outgoing call for which you wish to restrict your
calling identification.
Prefix Dialing
Cisco 803 and Cisco 804 routers support prefix dialing. You can add a telephone
prefix and create a prefix filter to the dialed number for analog telephone calls.
When a telephone number is dialed through the telephone port, the router checks
for prefix filters. If the router finds a match, no prefix is added to the dialed
number. If no filter match is found, the router adds the user-defined prefix to the
called number.
where number is a prefix number from 1 to 5 digits in length. Only one prefix can
be configured at a time, and configuring a new number will overwrite the existing
one.
where number is a prefix filter from 1 to 8 digits in length. You can define up to
ten filters for your router. If you have reached the maximum number of filters
defined, no new filter configurations are accepted until you remove at least one
existing filter number using the no pots prefix filter number command.
The following are examples of how to set prefix filters:
router# configure terminal
router(config)# pots prefix filter 192
router(config)# pots prefix filter 1
router(config)# pots prefix filter 9
router(config)# pots prefix filter 0800
router(config)# pots prefix filter 08456
• The call waiting tone is not activated for the local telephone ports even if call
waiting is enabled locally or at the switch. An external calling party hears a
busy tone if the telephone ports are engaged.
B1 B2
POTS 1 POTS 2 Channel Channel Command Result
IDLE IDLE Free Free Press **0# from POTS 1 Intercom call is
or POTS 2 established.
IDLE IDLE Data call Free Press **0# from POTS 1 Intercom call is
in or POTS 2 established.
progress
IDLE IDLE Data call Data call Press **0# from POTS 1 Intercom call is
in in or POTS 2 established. But in
progress progress overlap mode, one data
call is bumped
IDLE IDLE Data call Data call Press **0# from POTS 1 Intercom call is
in in or POTS 2 established successfully
progress progress in enblock mode. User
gets busy tone in overlap
mode.
B1 B2
POTS 1 POTS 2 Channel Channel Command Result
IDLE IDLE Data call Data call Press **0# from POTS 1 Telephone port call is
in in or POTS 2 established successfully
progress progress in enblock mode. In
overlap mode, if both the
calls aredestined for same
location, then one data
call is bumped to
establish the intercom
mode successfully.
Otherwise, the user at
POTS 1 or 2 hears a busy
tone.
Intercom Intercom Free Free Press flash and any key at During the intercom call
POTS 1 flashhook/keys is not
detected.
Intercom Intercom Free/data Free/data An external voice call No call waiting tone is
call call comes to POTS 1 generated and the
external user hears a busy
tone. Data calls are not
bumped.
IDLE External Voice call Free Press **0# from POTS 1 Intercom fails and user
voice call hears a busy tone.
IDLE External Voice call Data call Press **0# from POTS 1 Intercom fails and the
voice call in user hears a busy tone. In
progress overlap mode, the data
call is bumped.
IDLE External Voice call Data call Press **0# from POTS 1 Intercom fails and the
voice call in user hears a busy tone.
progress
Redial
This feature enables you to redial the last number called on either telephone
port 1 or 2. The following conditions apply:
• This feature recalls only the last digits dialed, to a maximum of 65.
• The router does not store feature access codes starting with an asterisk (*),
interactive voice response (IVR) digits, or the pound (#) key.
Call Transfer
The call transfer feature enables you to transfer an external call from one
telephone port to the other. Call transfer does not require any subscription from
the switch.
Called
Event/Condition Port Command Result
External caller dialed IDLE Press flash hook The connection is established between
POTS 1 or POTS 2 port switch and **0# the external caller and POTS 1 or POTS 2
and the user decides to from POTS 1 or when the handset connected to the other
transfer the call to the POTS 2. POTS port goes to onhook.
other port.
External caller dialed BUSY Press FLASH **0# No connection is established between
POTS 1 or POTS 2 port. from POTS 1 or POTS 1 and POTS 2. The connection
POTS 1 or POTS 2 POTS 2. between the external call and called
decides to transfer the call POTS port is still valid, so the user can
to the other port, but that resume conversation with the external
port is busy with a call. called by pressing FLASH.
Called
Event/Condition Port Command Result
External caller dialed IDLE Press FLASH **0# This is an example of an unsupervised
POTS 1 or POTS 2. The from POTS 1 or call and is not supported. No connection
user decides to transfer POTS 2 will be made between the external caller
the call to the other port and the port to which they are being
and keep the phone on transferred.
hook without checking
the availability of the
port.
Volume Adjustments
The volume adjustment features enables you to adjust the receiver volume of the
POTS ports.
To configure the telephone receiver volume on each port, use the Cisco IOS
volume command in the dial-peer configuration mode:
volume number
where number is a numeric value from 1 to 5 representing the volume setting
ranging from -12 to 0 decibels (dB). The default setting is 3.
Table 6-12 lists the values and definitions of the number variable.
Note The distinctive ringing feature does not require subscription to any special
service on the ISDN switch. However, if the Nariwake subscription is already
active, then Nariwake takes precedence over this feature.
Cadence Description
1 1 sec on, 2 sec off (NTT defined regular ring)
2 0.25 sec on, 0.2 sec off, 0.25 sec on, 2.3 sec off
(NTT defined non-regular ring)
3 0.5 sec on, 0.25 sec off, 0.25 sec on, 2 sec off
(Cisco defined non-regular ring)
no subaddress number
where number is the subaddress of a POTS port. Only one subaddress can be
configured for each port. By default, no subaddresses are configured.
Subaddressing Scenarios
Table 6-15 shows scenarios for subaddresses for a POTS port.
Note The call forwarding feature uses the B channels to forward the voice call and
to connect the caller and the forwarded destination. If one or both B channels
are busy with data calls, the incoming voice call supersedes the data calls.
where number is the external telephone number to forward an incoming voice call,
and number of rings is the maximum number of ring cycles (from 0 to 7) before
the router forwards the call. By default, this feature is disabled.
ring 0
volume 2
caller 1111111 ring 1
caller 2223323 ring 2
caller 3213213 ring 3
caller 8552345ring 1
caller 2223456 ring 2
caller 3214567 ring 2
subaddress 10
forward 1234567 after 3
The table indicates that the Cisco 800 series routers will act only as a PIAFS speed
variable type 2 device for all the peers supporting PIAFS 2.2.
Configuring PIAFS
This feature is available by default in all images. It is enabled when the ISDN
switch type is set to INS (NTT) and PPP encapsulation is configured on the ISDN
interface.
PIAFS Scenarios
Table 6-18 shows scenarios for PIAFS. The feature is activated when the ISDN
switch type is set to INS(NTT) and PPP encapsulation is configured on the ISDN
interface.
PIAFS Status
The status of the PIAFS calls on the router can be checked by using the following
command in privileged mode:
show piafs status
Note Every feature described is not necessarily supported on every router model.
Where possible and applicable, feature limitations are listed.
If you prefer to use network scenarios to build a network, see Chapter 4, “Network
Scenarios.”
This chapter contains the following sections:
• Before You Configure Your Network, page 7-2
• Configuring Basic Parameters, page 7-3
• Configuring Bridging, page 7-14
• Configuring Static Routing, page 7-17
• Configuring Dynamic Routing, page 7-18
• Configuring IP EIGRP, page 7-20
• Configuring Addressing Parameters, page 7-22
• Configuring DHCP, page 7-27
• Configuring TACACS+, page 7-33
• Configuring an Extended Access List, page 7-34
• Configuring Quality of Service Parameters, page 7-36
For complete information on how to access global configuration mode, see the
“Entering Global Configuration Mode” section on page A-8. For more
information on the commands used in the following tables, refer to the Cisco IOS
Release 12.0 documentation set.
Command Task
Step 1 configure terminal Enter configuration mode.
Step 2 hostname name Specify the name for the router.
Step 3 enable secret password Specify an encrypted password to prevent
unauthorized access to the router.
Step 4 ip subnet-zero Configure the router to recognize zero subnet
range as valid range of addresses.
Step 5 no ip domain-lookup Disable the router from translating unfamiliar
words (typos) entered during a console
session into IP addresses.
Command Task
Step 1 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 2 ip address ip-address mask Set the IP address and subnet mask for the
Ethernet interface.
Command Task
Step 3 no shutdown Enable the Ethernet interface to change the
state from administratively down to up.
Step 4 exit Exit configuration mode for the Ethernet
interface.
Configuration Example
The following example shows the Ethernet interface configuration. You do not
need to enter the commands marked “default.” These commands appear
automatically in the configuration file that is generated when you use the show
running-config command.
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast (default)
!
Command Task
Step 1 interface dialer number Enter configuration mode for the dialer
interface.
Step 2 encapsulation ppp Specify the encapsulation type for the PVC as
PPP.
Step 3 ip address ip-address mask Set the IP address and subnet mask for the
dialer interface.
Step 4 dialer pool number Specify which dialer pool number you are
using.
Step 5 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Step 6 encapsulation aal5mux ppp dialer Specify the encapsulation type as AAL5MUX
PPP.
Step 7 dialer pool-member number Specify a dialer pool-member.
Step 8 dialer-group number Specify a dialer group. The dialer group is
required to fast-switch outgoing packets.
Step 9 exit Exit configuration mode for the ATM
interface.
Configuration Example
The following example shows the dialer interface configuration. You do not need
to input the commands marked “default.” These commands appear automatically
in the configuration file that is generated when you use the show running-config
command.
!
interface atm0
pvc 1/40
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
interface dialer 0
ip address 200.200.100.1 255.255.255.0
encapsulation ppp
dialer pool 1
!
Virtual-access 1 is up means that the interface is up and running. If you see the
output Virtual-access 1 is down, it means that the interface is “administratively
down,” and the interface is configured with the shutdown command. To bring the
interface up, you must enter the no shutdown command.
Configuration Tasks
Follow the steps below to configure the loopback interface.
Command Task
Step 1 interface Loopback 0 Enter configuration mode for the loopback
interface.
Step 2 ip address ip-address mask Set the IP address and subnet mask for the
loopback interface.
Step 3 ip nat outside Set the interface to be connected to the outside
network.
Step 4 exit Exit configuration mode for the loopback
interface.
Sample Configuration
The loopback interface in this sample configuration is used to support NAT on the
virtual-template interface. This sample configuration shows the loopback
interface configured on the Ethernet interface with an IP address of
200.200.100.1/24, which acts as a static IP address. The loopback interface points
back to virtual-template1, which has a negotiated IP address.
!
interface Loopback0
ip address 200.200.100.1 255.255.255.0 (static IP address)
ip nat outside
!
interface Virtual-Template1
ip unnumbered loopback0
no ip directed-broadcast
ip nat outside
!
Another way to verify the loopback interface is to send multiple ping packets to it:
Router#ping 200.200.100.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 200.200.100.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Note The default service class for configuring the ATM interface is unspecified bit rate
(ubr). You can change the service class to variable bit rate non-real time (vbr-nrt)
or variable bit rate real time (vbr-rt) by using one of these commands: vbr-nrt or
vbr-rt. Refer to the Cisco IOS Release 12.0 documentation set. For more
information on definitions of service classes, see Chapter 1, “Concepts.”
Command Task
Step 1 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 2 dsl equipment-type {co | cpe} Configure the DSL equipment type, if
applicable.
Step 3 dsl linerate {number | auto} Specify the G.SHDSL line rate, if applicable.
The range of valid numbers is between 72 and
2312.
Step 4 dsl operating-mode gshdsl symmetric Set the G.SHDSL operating mode, if
annex annex applicable, and select the G.991.2 annex.
Step 5 ip address ip-address mask Set the IP address and subnet mask for the
ATM interface.
Step 6 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Step 7 protocol ip ip-address broadcast Set the protocol broadcast for the IP address.
Step 8 encapsulation protocol Specify the encapsulation type for the PVC.
Encapsulations can be specified as
AAL5SNAP, AAL5MUX IP, or AAL5MUX
PPP.1
Step 9 tx-ring-limit number Configure the size of the PVC transmit queue.
The default setting is 6.
Step 10 no shutdown Enable the ATM interface.
Step 11 exit Exit configuration mode for the ATM
interface.
1. This step is optional. If you specify the AAL5MUX PPP encapsulation, you will need to add an additional step to specify the
dialer pool-member number using the command dialer-pool member number.
Virtual-access 1 is up means that the interface is up and running. If you see the
output Virtual-access 1 is down, it means that the interface is “administratively
down,” and the interface is configured with the shutdown command. To bring the
interface up, you must enter the no shutdown command.
Command Task
Step 1 line console 0 Enter line configuration mode, and specify the
console terminal line.
Step 2 password password Specify a unique password on the line.
Step 3 login Enable password checking at the terminal
session login.
Step 4 exec-timeout 10 0 Set the interval that the privileged EXEC
command interpreter waits until user input is
detected. Exec-timeout 10 0 is the default.
Step 5 line vty 0 4 Specify a virtual terminal for remote console
access.
Step 6 password password Specify a unique password on the line.
Step 7 login Enable password checking at virtual terminal
session login.
Step 8 end Exit line configuration mode, and return to
privileged EXEC mode.
Configuration Example
The following configuration shows the command-line access commands.
You do not need to input the commands marked “default.” These commands
appear automatically in the configuration file that is generated when you use the
show running-config command.
!
line con 0
exec-timeout 10 0
password 4youreyesonly
login
transport input none (default)
stopbits 1 (default)
line vty 0 4
password secret
login
!
Configuring Bridging
Bridges are store-and-forward devices that use unique hardware addresses to filter
traffic that would otherwise travel from one segment to another. You can configure
the routers as pure bridges.
Follow the steps below to configure bridging, beginning in global configuration
mode.
Command Task
Step 1 no ip routing Disable IP routing.
Step 2 bridge number protocol protocol Specify the bridge protocol to define the type
of Spanning-Tree Protocol (STP).
Step 3 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 4 bridge-group number Specify the bridge-group number to which the
Ethernet interface belongs.
Step 5 no shutdown Enable the Ethernet interface.
Step 6 exit Exit configuration mode for the Ethernet
interface and the router.
Step 7 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 8 dsl equipment-type {co | cpe} Configure the DSL equipment type, if
applicable.
Step 9 dsl linerate {number | auto} Specify the G.SHDSL line rate, if applicable.
The range of valid numbers is between 72 and
2312.
Command Task
Step 10 dsl operating-mode gshdsl symmetric Set the G.SHDSL operating mode, if
annex annex applicable, and select the G.991.2 annex.
Step 11 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Step 12 encapsulation type Specify the encapsulation type for the PVC.
Step 13 bridge-group number Specify the bridge-group number to which the
ATM interface belongs.
Step 14 no shutdown Enable the ATM interface.
Step 15 end Exit the configuration mode for the ATM
interface.
Configuration Example
The following configuration example uses bridging with AAL5SNAP
encapsulation. You do not need to enter the commands marked “default.” These
commands appear automatically in the configuration file that is generated when
you use the show running-config command.
This configuration example shows the Ethernet and ATM interfaces configured.
The Ethernet interface has IP addressing turned off for bridging, and IP directed
broadcast is disabled, which prevents the translation of directed broadcasts to
physical broadcasts. The bridge-group number to which the ATM interface is
associated is set to 1.
The ATM interface has a PVC of 8/35, and the encapsulation is set to AAL5SNAP.
The IP address is disabled for bridging and the IP directed broadcast is disabled,
which prevents the translation of directed broadcasts to physical broadcasts. The
bridge protocol is set to 1 to define the STP.
no ip routing
!
interface Ethernet0
no ip address
no ip directed-broadcast (default)
bridge-group 1
!
interface ATM0
no ip address
no ip directed-broadcast (default)
pvc 8/35
encapsulation aal5snap
!
bridge-group 1
!
ip classless (default)
!
bridge 1 protocol ieee
!
end
Command Task
Step 1 ip classless Set up a best route for packets destined for
networks unknown by the router.
Step 2 ip route network-number mask Specify the static route for the IP packets.
Step 3 end Exit router configuration mode.
Configuration Example
In the following configuration example, the static route is sending all IP packets
with a destination of 1.0.0.0 and a subnet mask of 255.0.0.0 out on the ATM
interface to another device with an IP address of 14.0.0.1. Specifically, the packets
are being sent to the configured PVC.
You do not need to enter the commands marked “default.” These commands
appear automatically in the configuration file that is generated when you use the
show running-config command.
!
ip classless (default)
ip route 1.0.0.0 255.0.0.0 atm0 14.0.0.1
no ip http server (default)
!
Configuring RIP
Follow the steps below to configure RIP routing protocol on the router, beginning
in global configuration mode.
Command Task
Step 1 router rip Enter router configuration mode and enable
RIP on the router.
Step 2 version 2 Specify use of RIP version 2.
Step 3 network network-number Specify the network number for each directly
connected network.
Step 4 no auto-summary Disable automatic summarization of subnet
routes into network-level routes. This allows
subprefix routing information to transmit
across classful network boundries.
Step 5 end Exit router configuration mode.
Configuration Example
The following configuration shows RIP version 2 enabled in IP network
10.10.10.0.
You do not need to enter the commands marked “default.” These commands
appear automatically in the configuration file that is generated when you use the
show running-config command.
!
router rip
version 2
network 10.0.0.0
no auto-summary
!
Configuring IP EIGRP
Follow the steps below to configure IP EIGRP, beginning in global configuration
mode.
Command Task
Step 1 router eigrp autonomous-system Enter router configuration mode and enable
EIGRP on the router. The autonomous-system
number identifies the route to other EIGRP
routers and is used to tag the EIGRP
information.
Step 2 network network-number Specify the network number for each directly
connected network.
Step 3 end Exit router configuration mode.
Configuration Example
The following configuration shows EIGRP routing protocol enabled in IP
networks 10.0.0.0 and 172.17.0.0. The EIGRP autonomous system number is
assigned as 100.
You do not need to enter the commands marked “default.” These commands
appear automatically in the configuration file that is generated when you use the
show running-config command.
!
router eigrp 100
network 10.0.0.0
network 172.17.0.0
!
Configuring NAT
You can configure NAT for either static or dynamic address translations.
Follow the steps below to configure static or dynamic inside source translation,
beginning in global configuration mode.
Command Task
Step 1 ip nat pool name start-ip end-ip {netmask Create pool of global IP addresses for NAT.
netmask | prefix-length prefix-length}
Step 2 access-list access-list-number permit source Define a standard access list permitting
[source-wildcard] addresses that need translation.
Step 3 ip nat inside source list access-list-number Enable dynamic translation of addresses
pool name permitted by access list to one of addresses
specified in pool.
Step 4 ip nat inside source static local-ip global-ip Enable static translation of specified inside
number extendable local address to globally unique IP address.
This command is optional.
Step 5 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 6 ip nat inside Establish the Ethernet interface as the inside
interface.
Step 7 exit Exit configuration mode for the Ethernet
interface.
Step 8 interface atm 0 Enter configuration mode for the ATM
interface.
Step 9 dsl equipment-type {co | cpe} Configure the DSL equipment type, if
applicable.
Command Task
Step 10 dsl linerate {number | auto} Specify the G.SHDSL line rate, if applicable.
The range of valid numbers is between 72 and
2312.
Step 11 dsl operating-mode gshdsl symmetric Set the G.SHDSL operating mode, if
annex annex applicable, and select the G.991.2 annex.
Step 12 ip nat outside Establish the ATM interface as the outside
interface.
Step 13 exit Exit configuration mode for the ATM
interface.
Note If you want to use NAT with a virtual template interface, you must configure a
loopback interface.
Configuration Example
The following configuration shows NAT configured for the Ethernet and ATM
interfaces.
The Ethernet 0 interface has an IP address of 192.168.1.1 with a subnet mask of
255.255.255.0. NAT is configured for inside, which means that the interface is
connected to the inside network that is subject to NAT translation.
The ATM 0 interface has an IP address of 200.200.100.1 and a subnet mask of
255.255.255.0. NAT is configured for outside, which means that the interface is
connected to an outside network, such as the Internet.
You do not need to enter the commands marked “default.” These commands
appear automatically in the configuration file that is generated when you use the
show running-config command.
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast (default)
ip nat inside
!
interface ATM0
ip address 200.200.100.1 255.255.255.0
no ip directed-broadcast (default)
ip nat outside
no atm ilmi-keepalive (default)
pvc 8/35
encapsulation aal5snap
!
ip route 0.0.0.0.0.0.0.0 200.200.100.254
!
ip nat pool test 200.200.100.1 200.200.100.1 netmask 255.255.255.0
ip nat inside source list 101 pool test overload
ip classless (default)
!
Command Task
Step 1 access-list access-list-number permit source Define a standard access list that permits
[source-wildcard] nonregistered IP addresses of hosts.
Step 2 ip nat inside source list access-list-number Set up translation of addresses identified by
interface interface overload the access list defined in Step 1.
Step 3 interface ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 4 ip nat inside Establish the Ethernet interface as the inside
interface for NAT.
Step 5 no shutdown Enable the Ethernet interface and the
configuration changes just made to it.
Step 6 exit Exit configuration mode for the Ethernet
interface.
Step 7 interface dialer Enter configuration mode for the dialer
interface.
Step 8 ip address negotiated Assign a negotiated IP address to the dialer
interface.
Step 9 ip nat outside Establish the dialer interface as the outside
interface for NAT.
Step 10 dialer pool number Specify which dialer pool number you are
using.
Step 11 exit Exit the dialer interface.
Step 12 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 13 dsl equipment-type {co | cpe} Configure the DSL equipment type, if
applicable.
Step 14 dsl linerate {number | auto} Specify the G.SHDSL line rate, if applicable.
The range of valid numbers is between 72 and
2312.
Command Task
Step 15 dsl operating-mode gshdsl symmetric Set the G.SHDSL operating mode, if
annex annex applicable, and select the G.991.2 annex.
Step 16 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Step 17 encapsulation aal5mux ppp dialer Specify the encapsulation type for the PVC to
be AAL5MUX PPP and point back to the
dialer interface.
Step 18 dialer pool-member number Specify which dialer pool-member you are
using.
Step 19 no shutdown Enable the interface and configuration
changes just made to the ATM interface.
Step 20 exit Exit configuration mode for the ATM
interface.
For complete information on the Easy IP commands, refer to the Cisco IOS
Release 12.0 documentation set. For general information on Easy IP (Phase 1)
concepts, see Chapter 1, “Concepts.”
2 4
Cisco 827 Cisco 3600
ATM
74583
3
1 5
Table 7-1 Key for Easy IP (Phase 2) — DHCP Server and Relay
Callout
Number Description
1 DHCP client
2 Remote office with Cisco 827 router
3 DHCP relay
4 Corporate office with Cisco 3600 router
5 DHCP server
Configuring DHCP
The following sections describe how to configure the router as a DHCP client,
server, or relay.
Step 1 Configure the BVI interface by entering the ip address dhcp client-id Ethernet
0 command.
Specifying the value client-id ethernet0 means that the MAC address of the
Ethernet interface is used as the client ID when the DHCP request is sent.
Otherwise, the MAC address of the BVI interface is used as the client ID.
Step 2 Configure NAT:
a. Configure the BVI interface by entering the ip nat outside command.
b. Configure the Ethernet interface by entering the ip nat inside command.
c. Create an access list under NAT by entering the access-list 1 permit ip
address command to match all Ethernet IP addresses.
d. Configure the source list under NAT by entering the
ip nat inside source list 1 interface BVI 1 overload command.
Step 3 Configure the Cisco router to act as a DHCP server. This step is optional.
a. At the config-if router prompt, enter the ip dhcp pool server name
command.
b. Enter the import all command to have the Cisco router retrieve the Microsoft
Windows nameserver (WINS) and domain name system (DNS) server
addresses for name resolution.
Configuration Example
The following example shows a configuration of the DHCP client.
Current configuration:
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname c827
!
!
ip subnet-zero
ip dhcp excluded-address 10.10.10.1
!
ip dhcp pool SERVER
network 10.10.10.0 255.255.255.0
default-router 10.10.10.1
import all
!
bridge irb
interface Ethernet0
ip address 10.10.10.1 255.255.255.0
no ip directed-broadcast
ip nat inside
!
interface ATM0
no ip address
no ip directed-broadcast
no atm ilmi-keepalive
bundle-enable
hold-queue 208 in
!
interface ATM0.1 point-to-point
no ip directed-broadcast
pvc 1/100
encapsulation aal5snap
!
bridge-group 1
!
interface ATM0.2 point-to-point
ip address 5.0.0.2 255.0.0.0
no ip directed-broadcast
pvc 1/101
protocol ip 5.0.0.1 broadcast
protocol ip 5.0.0.5 broadcast
encapsulation aal5snap
!
!
interface BVI1
ip address dhcp client-id Ethernet0
no ip directed-broadcast
ip nat outside
!
ip nat inside source list 1 interface BVI1 overload
ip classless
ip route 0.0.0.0 0.0.0.0 BVI1
no ip http server
!
access-list 1 permit 10.10.10.0 0.0.0.255
bridge 1 protocol ieee
bridge 1 route ip
!
voice-port 1
timing hookflash-in 0
!
voice-port 2
timing hookflash-in 0
!
voice-port 3
timing hookflash-in 0
!
voice-port 4
timing hookflash-in 0
!
!
line con 0
exec-timeout 0 0
transport input none
stopbits 1
line vty 0 4
password lab
login
!
scheduler max-task-time 5000
end
Command Task
Step 1 ip dhcp pool name Enter DHCP configuration mode, and create a
pool of IP addresses that can be assigned to
DHCP clients.
Step 2 network ip-address subnet-mask Specify a range of IP addresses that can be
assigned to the DHCP clients.
Step 3 domain-name domain name Configure the domain name.
Step 4 dns-server ip-address Designate the router as the default router, and
specify an IP address.
Step 5 netbios-name-server ip-address Configure the netbios name server.
Step 6 default-router ip-address Configure the DNS server.
Command Task
Step 7 lease days hours minutes Specify the duration of the lease.
Step 8 exit Exit DHCP configuration mode.
For more information on the features not used in this configuration, refer to the
Cisco IOS DHCP Server feature module. For more general information on DHCP
servers, refer to Chapter 1, “Concepts.”
Configuration Example
The following configuration shows a DHCP server configuration for the IP
address 20.1.1.2.
!
ip dhcp pool CLIENT
network 20.20.20.0 255.255.255.0
domain-name cisco.com
default-router 20.20.20.20
netbios-name-server 1.1.1.1
dns-server 1.1.1.2
lease 0 1
!
Follow the steps below to configure the DHCP relay, beginning in global
configuration mode.
Command Task
Step 1 interface Ethernet 0 Enter configuration mode for the Ethernet
interface.
Step 2 ip helper-address address Forward default UDP broadcasts including IP
configuration requests to the DHCP server.
Step 3 no shutdown Enable the Ethernet interface and the
configuration changes.
Step 4 exit Exit configuration mode for the Ethernet
interface.
Configuration Example
The following configuration contains commands relevant to DHCP relay only.
You do not need to enter the commands marked “default.” These commands
appear automatically in the configuration file that is generated when you use the
show running-config command.
!
int Ethernet0
ip address 192.168.100.1 255.255.255.0
ip helper-address 200.200.200.1
!
Configuring TACACS+
The Cisco 806, 827, 831, 836, 837, 827H, and 827-4V routers and the
Cisco SOHO 71, 91, 96, and 97 routers support the Terminal Access Controller
Access Control System Plus (TACACS+) protocol through Telnet. TACACS+ is a
Cisco proprietary authentication protocol that provides remote access
authentication and related network security services, such as event logging. User
passwords are administered in a central database rather than in individual routers.
TACACS+ also provides support for separate modular authentication,
authorization, and accounting (AAA) facilities that are configured at individual
routers.
To configure your router to support TACACS+, perform the following tasks:
Command Task
Step 1 aaa new-model Enter the global configuration command to
enable AAA. AAA must be configured to use
TACACS+.
Step 2 tacacs-server host Specify the IP address of one or more
TACACS+ daemons.
Step 3 tacacs-server key Specify an encryption key that will be used to
encrypt all exchanges between the network
access server and the TACACS+ daemon.
This same key must also be configured on the
TACACS+ daemon.
Command Task
Step 4 aaa authentication Define the method lists that use TACACS+ for
authentication.
Step 5 line Apply the defined method lists to various
interfaces.
You may need to perform other configuration steps to enable accounting for
TACACS+ connections. For instructions on configuring TACACS+, refer to the
Security Configuration Guide.
Command Task
Step 1 access-list 100 permit tcp any ip ip Permit any host on the network to access any
address-mask established Internet server.
Step 2 access-list 100 deny ip ip adddress-mask any Deny any Internet host from spoofing any host
on the network.
Step 3 access-list 100 permit tcp host ip Permit Internet DNS server to send TCP
address-mask replies to any host on the network.
Step 4 access-list 100 permit udp host ip Permit Internet DNS server to send UDP
address-mask replies to any host on the network.
Step 5 access-list 100 permit tcp any host ip Permit SMTP mail server to access any
address Internet server.
Step 6 access-list 100 permit tcp any host ip Permit web server to access any Internet
address server.
Step 7 access-list 100 permit tcp any host ip Permit FTP server to access any Internet
address server.
Step 8 access-list 100 deny tcp any ip address-mask Restrict any Internet host from making a
Telnet connection to any host on the network.
Command Task
Step 9 interface atm 0 Enter configuration mode for the ATM
interface.
Step 10 dsl equipment-type co/cpe Configure the DSL equipment type, if
applicable.
Step 11 dsl linerate number/auto Specify the G.SHDSL line rate, if applicable.
The range of valid numbers is between 72 and
2312.
Step 12 dsl operating-mode gshdsl symmetric Set the G.SHDSL operating mode, if
annex annex applicable, and select the G.991.2 annex.
Step 13 ip access-group 100 in Activate access list 100.
Step 14 no shutdown Enable the interface and configuration
changes made to the interface.
Step 15 exit Exit configuration mode for the ATM
interface.
For more complete information on the extended access list commands, refer to the
Cisco IOS Release 12.0 documentation set. For information on TCP and UDP
port assignments, see Appendix C, “Common Port Assignments.”
Configuration Example
This configuration shows an access list being applied to IP address 192.168.1.0.
You do not need to enter the commands marked “default.” These commands
appear automatically in the configuration file generated when you use the
show running-config command.
!
access-list 101 permit tcp any host 192.168.1.0 0.0.0.255
!
Note QoS parameters are supported only on routers with voice features.
For complete information on the QoS commands, refer to the Cisco IOS
documentation set. For general information on QoS concepts, see Chapter 1,
“Concepts.”
Configuring IP Precedence
IP Precedence gives voice packets a higher priority than other IP data traffic. The
ip precedence command is used by the router to differentiate voice traffic from
data traffic. Therefore, you need to ensure that the data IP packets do not have the
same IP precedence as that of the voice packets.
Follow the steps below to configure real-time voice traffic precedence over other
IP network traffic, beginning in global configuration mode.
Command Task
Step 1 dial-peer voice number voip Enter the dial peer configuration mode to
configure a VoIP dial peer.
Step 2 destination-pattern number Set a destination pattern.
Step 3 session target {ipv4:destination-address} Specify a destination IP address for the dial
peer.
Step 4 ip precedence number Select a precedence level for the voice traffic
associated with that dial peer.
Step 5 exit Exit configuration mode for the dial peer
interface.
Note In IP Precedence, the numbers 1 through 5 identify classes for IP flows; the
numbers 6 through 7 are used for network and backbone routing and updates. It is
recommended that IP Precedence 5 is used for voice packets.
Command Task
Step 1 access-list 101 permit ip any any precedence Configure an access list to match voice
5 packets.
Command Task
Step 2 class-map voice Configure a voice class.
Step 3 match access-group 101 Associate the voice class with the access list.
Command Task
Step 1 policy map name Configure a policy map.1
Step 2 class voice Specify the class for queuing.
Step 3 priority number Specify the priority for queuing.
1. Total bandwidth for the policy map may not exceed 75 percent of the total PVC bandwidth.
Configuring a Policy Map and Specifying Priority Queuing for Voice Class
Follow the steps below to associate the policy map to the ATM PVC and decrease
the MTU of the ATM interface so that large data packets are fragmented,
beginning in global configuration mode.
Command Task
Step 1 policy map name Configure a policy map.1
Step 2 class voice Specify the class for queuing.
Step 3 priority bandwidth Specify the priority for queuing.
Step 4 exit Exit configuration mode for the policy map.
1. Total bandwidth for the policy map may not exceed 75 percent of the total PVC bandwidth.
Associating the Policy Map to the ATM PVC and Decreasing the ATM Interface
MTU
Use the following table to associate the policy map to the ATM PVC and decrease
the MTU, beginning in global configuration mode. It is recommended that 300 is
used for the MTU size because it is larger than the size of the voice packets
generated by the different codecs.
Note The default service class for configuring the ATM interface is unspecified bit rate
(ubr). In order to attach the policy map to the ATM PVC, you must use a service
class of vbr-nrt or vbr-rt.
Command Task
Step 1 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 2 ip address ip-address mask Set the IP address and subnet mask for the
ATM interface.
Step 3 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Step 4 encapsulation protocol Specify the encapsulation type for the PVC.
Encapsulations can be specified as
AAL5SNAP or AAL5MUX PPP.
Step 5 service policy out name Associate the service policy name.
Step 6 vbr-rt pcr scr bs Specify the service class.
Step 7 exit Exit configuration mode for the ATM PVC.
Step 8 mtu number Specify the MTU for the ATM interface.
Step 9 no shutdown Enable the ATM interface.
Step 10 exit Exit configuration mode for the ATM
interface.
Configuration Example
The following example shows a voice QoS configuration in a single-PVC
environment using AAL5SNAP encapsulation.
!
dial-peer voice 105 voip
destination-pattern 3..
session target ipv4:10.1.2.3
ip precedence 5
class-map voice
match access-group 101
policy-map mypolicy
class voice
priority 480
int atm0
mtu 300
pvc 8/35
encapsulation aal5snap
service-policy out mypolicy
vbr-rt 640 640 10
!
• Associating the Policy Map with the ATM PVC and Using TCP MSS Adjust
• Fine-Tuning the Size of the PVC ATM Transmit Ring Buffer
Note In IP Precedence, the numbers 1 through 5 identify classes for IP flows; the
numbers 6 through 7 are used for network and backbone routing and updates. It is
recommended that IP Precedence 5 be used for voice packets.
Command Task
Step 1 access-list 101 permit ip any any precedence Configure an access list to match voice
packets.
Step 2 class-map voice Configure a voice class
Step 3 match access-group 101 Associate the voice class with the access list.
Command Task
Step 1 policy map name Configure a policy map.1
Step 2 class voice Specify the class for queuing.
Step 3 priority bandwidth Specify the bandwidth for this strict priority
queue.
1. Total bandwidth for the policy map may not exceed 75 percent of the total PVC bandwidth.
Associating the Policy Map with the ATM PVC and Using TCP
MSS Adjust
Perform the steps below to associate the policy map with the ATM PVC and to use
the TCP MSS adjust command to control delay, beginning in global
configuration mode.
Note The default service class for configuring the ATM interface is unspecified bit rate
(ubr). To attach the policy map to the ATM PVC, you must use a service class of
vbr (nrt) or vbr (rt).
Command Task
Step 1 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 2 dsl equipment-type {co | cpe} Configure the DSL equipment type.
Step 3 dsl linerate {number| auto} Specify the ADSL line rate. The range of
valid numbers is between 72 and 2312.
Step 4 ip address ip-address mask Set the IP address and subnet mask for the
ATM interface.
Command Task
Step 5 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Step 6 encapsulation protocol Specify the encapsulation type for the PVC.
Encapsulations can be specified as either
AAL5SNAP or AAL5MUX PPP.
Step 7 service policy out name Associate the service policy name.
Step 8 vbr-rt pcr scr bs Specify the service class.
Step 9 exit Exit configuration mode for the ATM PVC.
Step 10 ip tcp adjust-mss mss Specify the TCP maximum segment size
(MSS).
Step 11 no shutdown Enable the ATM interface.
Step 12 exit Exit configuration mode for the ATM
interface.
Configuration Example
The following example shows a voice QoS configuration in a single-PVC
environment using AAL5SNAP encapsulation.
access-list 101 permit ip any any precedence critical
class-map voice
match access-group 101
policy-map mypolicy
class voice
priority 480
int atm0
dsl equipment-type CPE
dsl linerate AUTO
ip tcp-mss 1452
pvc 8/35
encapsulation aaal5snap
service-policy out mypolicy
vbr-rt 1000 1000 1
tx-ring-limit 5
!
Note In IP Precedence, the numbers 1 through 5 identify classes for IP flows; the
numbers 6 through 7 are used for network and backbone routing and updates. It is
recommended that IP Precedence 5 be used for voice packets.
Command Task
Step 1 policy map name Configure a policy map.1
Step 2 class voice Specify the class for queuing.
Step 3 priority bandwidth Specify the bandwidth for this strict priority
queue.
1. Total bandwidth for the policy map may not exceed 75 percent of the total PVC bandwidth.
Command Task
Step 1 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 2 dsl equipment-type {co | cpe} Configure the DSL equipment type.
Step 3 dsl linerate {number| auto} Specify the ADSL line rate. The range of
valid numbers is between 72 and 2312.
Command Task
Step 4 ip address ip-address mask Set the IP address and subnet mask for the
ATM interface.
Step 5 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Step 6 encapsulation protocol Specify the encapsulation type for the PVC.
Encapsulations can be specified as either
AAL5SNAP or AAL5MUX PPP.
Step 7 service policy out name Associate the service policy name.
Step 8 vbr-rt pcr scr bs Specify the service class.
Step 9 exit Exit configuration mode for the ATM PVC.
Command Task
Step 1 bandwidth bandwidth-kpts Configure the dialer bandwidth, The
bandwidth configured under the dialer
interface must be the same as the bandwidth
allocated to its assigned PVC.
Step 2 ppp multilink Enable ppp multilink.
Step 3 ppp multilink interleave Specify ppp multilink interleaving.
Step 4 ppp multilink fragment-delay milliseconds Define the fragment delay.
Step 5 access-list access-list-number {permit | Create an access list.
deny} address mask precedence number
Step 6 class-map match-all voice Create a class map.
Step 7 match access-group number Link the class map to the access list.
Step 8 policy-map name Create a policy map.
Step 9 class name Define the class.
Step 10 priority number Assign priority bandwidth to the traffic.
Step 11 interface dialer number Define a dialer rotary group.
Step 12 service-policy {input | output} policy-map Create a service policy.
Note LFI should not be used when you have a link that exceeds 1 Mbps because, at this
high speed, the latency of sending a big packet is small enough that the benefit of
LFI is not required. Using LFI may actually increase latency because the extra
processing time required to fragments packets may become a bottleneck.
10.0.0.0
PVC 1/40 VBR (RT), Voice
Ethernet 0
c827
11.0.0.0
PVC 8/35 UBR, Data
33494
P1 P2 P3 P4
Command Task
Step 1 interface ATM 0.1 point-to-point Specify the ATM0.1 subinterface.
Step 2 ip address ip-address mask Set the IP address and subnet mask for the
ATM0.1 subinterface.
Step 3 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Command Task
Step 4 encapsulation type Specify the encapsulation type for the PVC.
Step 5 protocol ip address broadcast Set the protocol broadcast for the IP address.
Step 6 interface ATM 0.2 point-to-point Specify the ATM0.2 subinterface.
Step 7 ip address ip-address mask Set the IP address and subnet mask for the
ATM0.2 subinterface.
Step 8 pvc vpi/vci Create an ATM PVC for each end node with
which the router communicates.
Step 9 encapsulation type Specify the encapsulation type for the PVC.
Step 10 protocol ip address broadcast Set the protocol broadcast for the IP address.
Step 11 exit Exit configuration mode for the ATM
interface.
Configuration Example
The following example shows a voice QoS configuration with all data traffic on
the 30.0.0.1 network and all voice traffic on the 20.0.0.1 network.
You do not need to enter the commands marked “default.” These commands
appear automatically in the configuration file that is generated when you use the
show running-config command.
!
interface ATM0.1 point-to-point
ip address 20.0.0.1 255.0.0.0
no ip directed-broadcast (default)
pvc 1/100
protocol ip 20.0.0.2 broadcast
vbr-rt 424 424 5
encapsulation aal5snap
!
interface ATM0.2 point-to-point
ip address 30.0.0.1 255.0.0.0
no ip directed-broadcast (default)
pvc 1/101
protocol ip 30.0.0.2 broadcast
encapsulation aal5snap
Figure 7-3 Voice and Data on the Same Subnet with Virtual Circuit Bundling
1 3
c827
4
74586
P1 P2 P3 P4
Table 7-2 Key for Voice and Data on the Same Subnet with Virtual Circuit
Bundling
The tasks for configuring a voice and data network on the same subnet with virtual
circuit bundling are as follows:
• Configuring the ATM interface
• Configuring the PVC-bundle for voice
• Configuring the PVC-bundle for data
• Configuring IP Precedence for voice packets
Configuring the ATM Interface, PVC-Bundle for Voice and Data, and IP
Precedence for Voice Packets
Follow the steps below to configure the ATM interface, the PVC-bundle for voice
and data, and IP Precedence for the voice packets, beginning in global
configuration mode.
Command Task
Step 1 interface ATM 0 Enter configuration mode for the ATM
interface.
Step 2 dsl equipment-type co/cpe Configure the DSL equipment type.
Step 3 dsl linerate number/auto Specify the G.SHDSL line rate. The range of
valid numbers is between 72 and 2312.
Step 4 dsl operating-mode gshdsl symmetric Set the G.SHDSL operating mode, and select
annex annex the G.991.2 annex.
Step 5 ip address ip-address mask Set the IP address and subnet mask for the
ATM interface.
Step 6 bundle name Specify a bundle name.
Step 7 encapsulation type Specify the encapsulation type for the voice
bundle PVC.
Step 8 protocol ip ip-address broadcast Set the protocol broadcast for the IP address.
Step 9 pvc-bundle name vpi/vci Create a PVC for the voice bundle.
Step 10 vbr-rt pcr scr bs Set the service class for the voice bundle. 1
Step 11 ip precedence number Select an IP Precedence level specific to the
voice bundle that you created.
Command Task
Step 12 pvc-bundle name vpi/vci Create a PVC for the data bundle.
Step 13 ubr pcr Set the service class for the data2 bundle.
Step 14 precedence other Set the IP Precedence level other to the data
bundle that you created.
Step 15 exit Exit configuration mode for the ATM
interface.
1. For voice, the service class must be vbr-rt or vbr-nrt.
2. For data, the service class must be vbr-nrt or ubr.
Command Task
Step 1 dial-peer voice number voip Enter the dial peer configuration mode to
configure a VoIP dial peer.
Step 2 destination-pattern number Set a destination pattern.
Step 3 session target {ipv4:destination-address} Specify a destination IP address for the dial
peer.
Step 4 precedence number Select a precedence level for the voice traffic
associated with that dial peer.
Note In IP Precedence, the numbers 1 through 5 identify classes for IP flows; the
numbers 6 through 7 are used for network and backbone routing and updates. It is
recommended that IP Precedence 5 is used for voice packets.
Configuration Example
The following configuration shows both voice and data on the same subnet with
virtual circuit bundling. IP precedence is set to 5 for the voice packets, but not for
the data packets so that the traffic can be separated onto two different ATM PVCs.
!
interface atm0
ip address 20.0.0.1 255.0.0.0
bundle test
encapsulation aal5snap
protocol ip 20.0.0.2 broadcast
!
pvc-bundle voice 1/100
vbr-rt 424 424 5
precedence 5
!
pvc-bundle data 1/101
precedence other
!
Note When you use a BRI for a dial backup, neither of the B channels can be used while
the interface is in standby mode. In addition, when a BRI is used as a backup
interface and the BRI is configured for legacy DDR, only one B channel is usable.
Once the backup is initiated over one B channel, the second B channel is
unavailable. When the backup interface is configured for dialer profiles, both B
channels can be used.
For more information regarding the available dial backup mechanisms in IOS,
please go to the following URL:
http://www.cisco.com/warp/public/123/backup-main.html
Configuration Example
The following example shows configuration of dial backup and remote router
management on the Cisco 831 and Cisco 837 routers using the console port and
dialer watch.
!
username Router password !PASSWORD
!
modemcap entry MY_USR_MODEM:MSC=&F1S0=1
!
chat-script Dialout ABORT ERROR ABORT BUSY "" "AT" OK "ATDT 5555102\T"
TIMEOUT 60 CONNECT \c
!
interface Async1
no ip address
encapsulation ppp
dialer in-band
dialer pool-member 3
autodetect encapsulation ppp
async default routing
async dynamic routing
async mode dedicated
pap authentication pap callin
!
! Dialer3 is for dial backup and remote router management
!
interface Dialer3
ip address negotiated
encapsulation ppp
no ip route-cache
no ip mroute-cache
dialer pool 3
dialer remote-name !REMOTE-NAME
dialer idle-timeout 300
dialer string 5555102 modem-script Dialout
dialer watch-group 1
dialer-group 1
autodetect encapsulation ppp
peer default ip address 192.168.2.2
no cdp enable
ppp pap sent-username ! USER SPECIFIC password ! USER SPECIFIC
ppp ipcp dns request
ppp ipcp wins request
ppp ipcp mask request
!
! IP NAT over Dialer interface using route-map
Configuration Example
The following example shows dial backup and remote management configuration
on the Cisco 836 router, using the ISDN S/T port and dialer watch.
Cisco836#
!
vpdn enable
!
vpdn-group 1
accept-dialin
protocol pppoe
!
!Specifies the ISDN switch type
isdn switch-type basic-net3
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
hold-queue 100 out
!
!ISDN interface to be used as a backup interface
interface BRI0
no ip address
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
!
interface ATM0
no ip address
no atm ilmi-keepalive
pvc 1/40
encapsulation aal5snap
pppoe-client dial-pool-number 2
!
dsl operating-mode auto
!
! Dial backup interface, associated with physical BRI0 interface.
Dialer pool 1 associates it with BRI0’s dialer pool member 1. Note
“dialer watch-group 1” associates a watch list with corresponding
“dialer watch-list” command
interface Dialer0
ip address negotiated
encapsulation ppp
dialer pool 1
dialer idle-timeout 30
dialer string 384040
dialer watch-group 1
dialer-group 1
!
! Primary interface associated with physical ATM0 interface, dialer
pool 2 associates it with ATM0’s dial-pool-number2
interface Dialer2
ip address negotiated
ip mtu 1492
encapsulation ppp
dialer pool 2
dialer-group 2
no cdp enable
!
ip classless
Command Task
Step 1 ip multicast-routing Enable IP multicast forwarding.
Step 2 ip pim rp-address address Configure the Protocol Independent Multicast
(PIM) Rendezvous Point (RP) address.
Step 3 interface ethernet 0 Enter Ethernet 0 interface configuration
mode.
Step 4 ip address ip-address subnet-mask Configure an IP address and subnet mask for
the Ethernet 0 interface.
Step 5 ip pim { sparse |dense }-mode Configure the Ethernet 0 interface for PIM
sparse mode or PIM dense mode.
Step 6 interface Ethernet 1 Enter Ethernet 1 configuration mode.
Command Task
Step 7 ip address {ip-address subnet-mask Specify an IP address and subnet mask for the
negotiated} dialer interface, or indicate that the IP address
is to be negotiated.
Step 8 ip pim {sparse | dense} -mode Configure the dialer interface for PIM sparse
mode or PIM dense mode.
Step 9 ip igmp mroute-proxy loopback 0 When used with the ip igmp proxy-service
command, this command enables all
forwarding entries in the multicast forward
table of IGMP to report to a proxy service
interface.
Step 10 end Exit router configuration mode.
Step 11 interface loopback 0 Enter loopback interface configuration mode.
Step 12 ip address ip-address subnet-mask Configure an IP address and subnet mask for
the loopback 0 interface.
Step 13 ip pim sparse-mode Configure the loopback interface for PIM
sparse mode or PIM dense mode.
Step 14 ip igmp helper-address udl ethernet 0 Enter IGMP helper-address unidirectional
link to Ethernet 0
Step 15 ip igmp proxy-service Enable the multicast route proxy service.
Based on the IGMP query interval, the router
periodically checks the mroute table for
forwarding entries that match interfaces
configured with the ip igmp mroute-proxy
command. Where there is a match, one IGMP
report is created and received on this
interface. This command is intended to be
used with the ip igmp helper-address udl
command, which forwards the IGMP report to
an upstream router.
Configuration Example
The following example shows the relevant IGMP proxy and sparse mode
commands. The Ethernet 0, Ethernet 1, and loopback 0 interfaces have been
configured for PIM sparse mode; the PIM RP address has been defined as
10.5.1.1.
ip pim rp-address 10.5.1.1 5
access-list 5 permit 239.0.0.0 255.255.255.255
!
interface loopback 0
ip address 10.7.1.1 255.255.255.0
ip pim sparse-mode
ip igmp helper-address udl ethernet 0
ip igmp proxy-service
!
interface ethernet 0
ip address 10.2.1.2 255.255.255.0
ip pim sparse-mode
ip igmp unidirectional link
!
interface ethernet 1
ip address 10.5.1.1 255.255.255.0
ip pim sparse-mode
ip igmp mroute-proxy loopback 0
!
Command Task
Step 1 ip subnet-zero Configure the router to recognize the zero
subnet range as the valid range of addresses.
Step 2 no ip finger Block incoming IP finger packets.
Step 3 no ip domain-lookup Disable the router from interpreting
unfamiliar words (typographical errors) as
host names entered during a console session.
Step 4 ip classless Follow classless routing forwarding rules.
Configuring IPSec
Follow the steps below to configure IPSec, starting in global configuration mode.
Command Task
Step 1 crypto isakmp policy 10 Define an Internet Key Exchange (IKE)
policy, and assign the policy a priority. This
command places the router in IKE policy
configuration mode.
Step 2 hash md5 Specify the md5 hash algorithm for the
policy.
Step 3 authentication pre-share Specify pre-share key as the authentication
method.
Step 4 exit Exit IKE policy configuration mode.
Command Task
Step 5 crypto isakmp key name address ip-address Configure a pre-shared key and static IP
address for each VPN client.
Step 6 crypto ipsec transform-set name esp-des Define a combination of security associations
esp-md5-hmac to occur during IPSec negotiations.
Step 7 crypto map name local-address ethernet 1 Create a crypto map, and specify and name an
identifying interface to be used by the crypto
map for IPSec traffic.
Step 8 crypto map name seq-num ipsec-isakmp Enter crypto map configuration mode, and
create a crypto map entry in IPSec ISAKMP
mode.
Step 9 set peer ip-address Identify the remote IPSec peer.
Step 10 set transform-set name Specify the transform set to be used.
Step 11 match address access-list-id Specify an extended access list for the crypto
map entry.
Step 12 exit Exit crypto map configuration mode.
Command Task
Step 1 interface tunnel 0 Configure the tunnel 0 interface.
Step 2 ip address ip-address subnet-mask Set the IP address and subnet mask for the
tunnel 0 interface.
Step 3 tunnel source ethernet 1 Specify the Ethernet 1 interface as the tunnel
source.
Step 4 tunnel destination Specify the default gateway as the tunnel
default-gateway-ip-address destination.
Command Task
Step 5 crypto map name Associate a configured crypto map to the
tunnel 0 interface.
Step 6 exit Exit the tunnel 0 interface configuration.
Command Task
Step 1 interface ethernet 0 Configure the Ethernet 0 interface.
Step 2 ip address ip-address subnet-mask Set the IP address and subnet mask for the
Ethernet 0 interface.
Step 3 exit Exit the Ethernet 0 interface configuration.
Step 4 interface ethernet 1 Configure the Ethernet 1 interface.
Step 5 ip address ip-address subnet-mask Set the IP address and subnet mask for the
Ethernet 1 interface.
Step 6 crypto map name Associate a crypto map with the Ethernet 1
interface.
Step 7 end Exit router configuration mode.
Command Task
Step 1 ip route default-gateway-ip-address mask Create a static route for the Ethernet 1
ethernet 1 interface.
Step 2 ip route default-gateway-ip-address mask Create a static route for the tunnel 0 interface.
tunnel 0
Step 3 ip route default-gateway-ip-address mask Create a static route to the gateway of last
gateway-of-last-resort resort.
Step 4 end Exit router configuration mode.
For more information on configuring IPSec, refer to the Cisco IOS Security
Configuration Guide.
Configuration Example
This configuration example for the Cisco 831 router shows IPSec being used over
a GRE tunnel. The example also applies to a Cisco SOHO 91 router. You do not
need to enter the commands marked “default.” These commands appear
automatically in the configuration file that is generated when you use the show
running-config command.
!
version 12.2
no service pad
service timestamps debug datetime msec
!
access-list 151 permit gre host 100.1.1.2 host 100.1.1.1
!
line con 0
no modem enable
stopbits 1
line aux 0
line vty 0 4
!
scheduler max-task-time 5000
Command Task
Step 1 interface dialer Enter configuration mode for the dialer
interface.
Step 2 ppp multilink Enable multilink PPP for the dialer interface.
Command Task
Step 3 bandwidth n Specify the bandwidth number associated
with the PVC that is using the dialer interface,
where n is the value of the sustained cell rate
(SCR) parameter of the PVC using that dialer
interface.This is important because otherwise
the dialer interface will assume a value of
100 kbps if a specific class of service is
configured.
Step 4 ppp multilink interleave Enable interleaving for RTP packets among
the fragments of larger packets on a multilink
PPP bundle.
Step 5 ppp multilink fragment-delay milliseconds Configure a maximum fragment delay of
20 ms. This command is optional.
Step 6 ip rtp reserve lowest-UDP-port Reserve a special queue for real-time packet
range-of-ports [maximum-bandwidth] flows to specified destination UDP ports,
allowing real-time traffic to have higher
priority than other flows.
Step 7 exit Exit configuration mode for the dialer
interface.
Configuration Example
The following configuration defines a dialer interface that enables multilink PPP
with interleaving and a maximum real-time traffic delay of 20 ms. The
encapsulation type is defined as aal5mux.
You do not need to enter the commands marked “default.” These commands
appear automatically in the configuration file generated when you use the
show running-config command.
!
interface dialer 1
ppp multilink
encapsulated ppp
ppp multilink interleave
bandwidth 640
ppp multilink fragment-delay 20
ip rtp reserve 16384 100 64
!
interface ATM0
pvc 8/35
encapsulation aal5mux ppp dialer
dialer pool-member 1
Configuring IP Precedence
IP Precedence gives voice packets higher priority than other IP data traffic.
Complete the following steps to configure real-time voice traffic precedence over
other IP network traffic, beginning in global configuration mode.
Command Task
Step 1 configure terminal Enter configuration mode.
Step 2 dial-peer voice number voip Enter the dial peer configuration mode to
configure a VoIP dial peer.
Step 3 destination-pattern number Set a destination pattern.
Step 4 ip precedence number Select a precedence level for the voice traffic
associated with that dial peer.
Note In IP Precedence, the numbers 1 through 5 identify classes for IP flows; the
numbers 6 through 7 are used for network and backbone routing and updates.
For complete information on the IP Precedence commands, refer to the Cisco IOS
Release 12.0 documentation set. For general information on IP precedence, see
Chapter 1, “Concepts.”
Configuration Example
This configuration example shows a voice configuration with IP Precedence set.
The IP destination target is set to 8 dialing digits, which automatically sets the IP
precedence to 5 on the Cisco routers. The dial peer session target is RAS, which
is a protocol that runs between the H.323 voice protocol gateway and gatekeeper.
You do not need to enter the commands marked “default.” These commands
appear automatically in the configuration file that is generated when you use the
show running-config command.
!
access-list 101 permit
route-map data permit 10
set ip precedence routing
!
Configuring Voice
Command Task
Step 1 configure dial-peer Enter configuration mode for the dial peer.
Step 2 dial-peer voice number voip Assign the dial peer voice number to
configure a VoIP dial peer.
The Cisco 827 voice-enabled routers support voice using the H.323 signaling
protocol as the default signaling protocol.
Prerequisite Tasks
Before you can configure your router to use voice, you need to perform the
following tasks:
• Establish a working IP network.
• Complete your company dial plan.
• Establish a working telephony network based on your company dial plan.
• Integrate your dial plan and telephony network into your existing IP network
topology.
Command Task
Step 1 dial-peer voice number POTS Enter configuration mode for the dial peer.
Step 2 destination-pattern string Define the destination telephone number
associated with the VoIP dial peer.
Step 3 port number Specify the port number.
Command Task
Step 1 dial-peer voice number VoIP Enter configuration mode for the dial peer.
Step 2 destination-pattern string Define the destination telephone number
associated with each VoIP dial peer.
Step 3 codec string Specify a codec if you are not using the
default codec of g.729.
Step 4 session target {ipv4:destination-address} Specify a destination IP address for each dial
peer.
Command Task
Step 1 configure dial-peer Enter configuration mode for the dial peer.
Step 2 voice-port port Identify the voice port you want to configure
and enter the voice port configuration mode.
Step 3 cptone country Select the appropriate voice call progress tone
for this interface. The default country for this
command is us.
Step 4 ring frequency (25 \ 50) Select the ring frequency (in Hz) specific to
the equipment attached to this voice port and
appropriate to the country you are in.
Step 5 description string Attach descriptive text about this voice port
connection.
Step 6 comfort-noise If voice activity detection (VAD) is activated,
specify that background noise is generated.
Step 7 impedance Specify impedance, which is related to the
electrical characteristics of the device that is
plugged into a POTS port. Impedance is
measured in ohms.
To verify that you have mapped the telephone numbers correctly, enter the
show num-exp command.
After you have configured dial peers and assigned destination patterns to them,
enter the show dialplan number command to see how a telephone number maps
to a dial peer.
For complete information on the number expansion commands, refer to the
Cisco IOS documentation set.
Configuration Example
This configuration shows voice traffic configured. You do not need to enter the
commands marked “default.” These commands appear automatically in the
configuration file that is generated when you use the show running-config
command.
!
class-map voice
match access-group 101
!
policy-map mypolicy
class voice
priority 128
class class-default
fair-queue 16
!
ip subnet-zero
!
gateway
!
interface Ethernet0
timeouts call-disconnect 0
!
voice-port 3
local-alerting
timeouts call-disconnect 0
!
voice-port 4
local-alerting
timeouts call-disconnect 0
!
dial-peer voice 10 voip
destination-pattern........
ip precedence 5
session target ras
!
dial-peer voice 1 pots
destination-pattern 5258111
port 1
!
dial-peer voice 2 pots
destination-pattern 5258222
port 2
!
dial-peer voice 3 pots
destination-pattern 5258333
port 3
!
dial-peer voice 4 pots
destination-pattern 5258444
port 4
!
end
timeouts call-disconnect 0
!
voice-port 2
local-alerting
timeouts call-disconnect 0
!
voice-port 3
local-alerting
timeouts call-disconnect 0
!
voice-port 4
local-alerting
timeouts call-disconnect 0
!
dial-peer voice 101 pots
destination-pattern 14085271111
port 1
!
dial-peer voice 1100 voip
destination-pattern 12123451111
codec g711ulaw
session target ipv4:1.0.0.2
!
dial-peer voice 102 pots
destination-pattern 14085272222
port 2
!
dial-peer voice 1200 voip
destination-pattern 12123452222
codec g711ulaw
session target ipv4:1.0.0.2
!
dial-peer voice 103 pots
destination-pattern 14085273333
port 3
!
dial-peer voice 1300 voip
destination-pattern 12123453333
codec g711ulaw
session target ipv4:1.0.0.2
!
dial-peer voice 104 pots
destination-pattern 14085274444
port 4
!
dial-peer voice 1400 voip
destination-pattern 12123454444
codec g711ulaw
ip classless (default)
!
line con 0
exec-timeout 10 0
password 4youreyesonly
login
transport input none (default)
stopbits 1 (default)
line vty 0 4
password secret
login
!
end
network 30.0.0.0
no auto-summary
!
no ip http server (default)
ip classless (default)
!
protocol ip 2.0.0.1 broadcast
!
line con 0
exec-timeout 0 0
transport input none (default)
stopbits 1 (default)
line vty 0 4
password secret
login
!
end
!
voice-port 1/1/0
!
voice-port 1/1/1
!
dial-peer voice 101 pots
destination-pattern 5552222
port 1/0/0
!
dial-peer voice 102 pots
destination-pattern 5554444
port 1/0/1
!
dial-peer voice 103 pots
destination-pattern 5556666
port 1/1/0
!
dial-peer voice 104 pots
destination-pattern 5558888
port 1/1/1
dial-peer voice 1100 voip
destination-pattern 5551111
codec g711alaw
ip precedence 5
no vad
session target ipv4:2.0.0.3
!
dial-peer voice 1101 voip
destination-pattern 5553333
codec g711alaw
ip precedence 5
no vad
session target ipv4:2.0.0.3
!
dial-peer voice 1102 voip
destination-pattern 5555555
codec g711alaw
ip precedence 5
session target ipv4:2.0.0.3
!
dial-peer voice 1103 voip
destination-pattern 5557777
codec g711alaw
ip precedence 5
session target ipv4:2.0.0.3
!
process-max-time 200
!
interface Ethernet0/1
no ip address
no ip directed-broadcast (default)
shutdown
!
router rip
version 2
network 3.0.0.0
!
ip classless (default)
ip route 0.0.0.0 0.0.0.0 Ethernet 0/0
ip route 1.0.0.0 255.0.0.0 3.0.0.0
ip route 2.0.0.0 255.0.0.0 3.0.0.1
This chapter includes advanced configuration procedures for the Cisco 800 series
and Cisco SOHO series routers.
Note Every feature described is not necessarily supported on every router model.
Where possible and applicable, these feature limitations will be listed.
If you prefer to use network scenarios to build a network, see Chapter 4, “Network
Scenarios.” For basic router configuration topics, see Chapter 7, “Router Feature
Configuration.”
This chapter contains the following sections:
• Configuring Support for PPP over Ethernet, page 8-2
• Configuring TCP Maximum Segment Size for PPPoE, page 8-5
• Configuring Low Latency Queuing and Link Fragmentation and Interleaving,
page 8-6
• Configuring LFI, page 8-8
• Configuring Class-Based Traffic Shaping to Support Low Latency Queuing,
page 8-9
• Configuring the Length of the PVC Transmit Ring, page 8-12
• Configuring DHCP Server Import, page 8-14
• Configuring IP Control Protocol Subnet Mask Delivery, page 8-20
• Configuring the Service Assurance Agent, page 8-27
• Configuring Secure Shell, page 8-28
Step 1 Configure the virtual private dialup network (VPDN) group number.
a. Enter the vpdn enable command in global configuration mode.
b. Configure the VPDN group by entering the vpdn group tag command.
c. Specify the dialing direction by entering the request-dialin command in the
VPDN group.
d. Specify the type of protocol in the VPDN group by entering the protocol
pppoe command.
Step 2 Configure the ATM interface with PPPoE support.
a. Configure the ATM interface by entering the interface atm 0 command.
b. Specify the ATM PVC by entering the pvc number command.
c. Configure the PPPoE client and specify the dialer interface to use for cloning
by entering the pppoe-client dial-pool-number number command.
Step 3 Configure the dialer interface by entering the int dialer number command.
a. Configure the IP address as negotiated by entering the
ip address negotiated command.
b. (Optional) Configure authentication for your network by entering the ppp
authentication protocol command.
c. Configure the dialer pool number by entering the dialer pool number
command.
Note Multiple PPPoE clients can run on a different PVCs, in which case each client
has to use a separate dialer interface and a separate dialer pool, and the PPP
parameters need to be applied on the dialer interface.
A PPPoE session is initiated on the client side by the network. If the session has
a timeout or is disconnected, the PPPoE client immediately attempts to reestablish
the session.
If you enter the clear vpdn tunnel pppoe command with a PPPoE client session
already established, the PPPoE client session stops, and the PPPoE client
immediately tries to reestablish the session.
Configuration Example
The following example shows a configuration of a PPPoE client.
vpdn enable
vpdn-group 1
request-dialin
protocol pppoe
int atm0
pvc 1/100
pppoe-client dial-pool-number 1
int dialer 1
ip address negotiated
ppp authentication chap
dialer pool 1
dialer-group 1
Configuration Example
The following example shows a configuration of a PPPoE client.
vpdn enable
no vpdn logging
!
vpdn-group 1
request-dialin
protocol pppoe
!
interface Ethernet0
ip address 192.168.100.1 255.255.255.0
ip tcp adjust-mss 1452
ip nat inside
!
interface ATM0
no ip address
no atm ilmi-keepalive
pvc 8/35
pppoe-client dial-pool-number 1
!
dsl operating-mode auto
!
interface Dialer1
ip address negotiated
ip mtu 1492
ip nat outside
encapsulation ppp
dialer pool 1
dialer-group 1
ppp authentication pap callin
ppp pap sent-username sohodyn password 7 141B1309000528
!
ip nat inside source list 101 interface Dialer1 overload
ip route 0.0.0.0.0.0.0.0 Dialer1
access-list 101 permit ip 192.168.100.0.0.0.0.255 any
Step 1 Ensure that the voice and data packets have different IP precedence values so
that the router can differentiate between them. Normally, data packets should
have an IP precedence of 0, and voice packets should have an IP precedence of 5.
If the VoIP packets are generated from within the router, you may set the IP
precedence to 5 for these packets by entering the ip precedence number
command in dial-peer voice configuration mode as follows:
a. Enter the global configuration dial-peer voice 1 voip command.
b. Enter the ip precedence 5 command.
Step 2 Create an access list and a class map for the voice packets.
a. Create an access list by entering the access-list 101 permit ip any any
precedence 5 command.
b. Create a class map for the voice packets by entering class-map match-all
voice command.
c. Link the class map to the access list by entering the match access-group 101
command.
Step 3 Create LLQ for voice traffic.
a. Create a policy map by entering the policy-map mypolicy command.
b. Define the class by entering the class voice command.
c. Assign the priority bandwidth to the voice traffic. The priority bandwidth
assigned to the voice traffic depends on the codec used and the number of
simultaneous calls that you allow. For example, a G.711 codec call consumes
200 kbps; therefore, to support one G.711 voice call you would enter a
priority 200 command.
Step 4 Attach LLQ to the dialer interface.
a. Enter the global configuration interface dialer 1 command.
b. Create a service policy by entering the service-policy out mypolicy
command.
Configuring LFI
Follow the steps below to configure the router for LFI.
Note When you are configuring LFI, the data fragment size must be greater than the
voice packet size; otherwise, the voice packets fragment, and voice quality
deteriorates.
Step 1 Configure the dialer bandwidth. The dialer interface has a default bandwidth of
56 kbps, which may be less than the upstream bandwidth of your digital
subscriber line (DSL) connection. You can find the upstream bandwidth of your
DSL connection by entering the show dsl interface atm0 command in dialer
interface configuration mode. If you have two or more PVCs sharing the same
DSL connection, the bandwidth configured for the dialer interface must be the
same as the bandwidth allocated to its assigned PVC.
Step 2 Enable PPP multilink, and configure fragment delay and interleaving for the
dialer interface.
a. Enter the global configuration interface dialer 1 command.
b. Specify the dialer bandwidth by entering the bandwidth 640 command. The
bandwidth is specified in kilobits per second (kbps).
c. Enter the ppp multilink command.
d. Specify PPP multilink interleaving by entering the ppp multilink interleave
command.
e. Define the fragment delay by entering the ppp multilink fragment-delay 10
command.
f. Calculate the fragment size using the following formula:
fragment size = (bandwidth in kbps/ 8) * fragment-delay in milliseconds (ms)
In this case, the fragment size = (640/8) * 10, resulting in a fragment size of
800. The fragment size is greater than the maximum voice packet size of 200,
which is G.711 20 ms. A low fragment delay corresponds to a fragment size
that may be smaller than the voice packet size, resulting in reduced voice
quality.
Step 2 Define a policy map and associated classes for low-latency queuing.
a. Enter the policy-map map-name command in global configuration mode to
construct policies and to allocate different network resources for the defined
traffic classes. The name LLQ could be used to specify that this is the policy
map for LLQ.
b. Now in policy-map mode, define a class to handle voice traffic by entering
class QOS-class-name, using the class-map name you defined using the
class-map command in Step 1. This command places the router in QOS-class
configuration mode.
c. Enter priority number, where number is bandwidth in kilobits per second. A
value of 300, as shown in the example configuration, provides enough
bandwidth for two G.711 voice ports. Before setting a priority value, refer to
the specification for the CODEC used for voice calls.
d. Enter exit to return to policy-map configuration mode.
e. Enter class class-default to use the default class for all traffic other than
voice traffic. The name class-default is well known, and does not have to be
predefined using the class-map command.
f. Apply WFQ to non-voice traffic by entering the fair-queue command.
g. Enter exit twice to return to global configuration mode.
Step 3 Define a traffic-shaping policy map.
a. Enter policy-map map-name in global configuration mode. The name shape
should be used to indicate this map defines overall traffic shaping that is
compatible with the remote transmission rate bandwidth.
b. Enter class class-default to associate the default class with this policy map.
c. Set the transmission speed to be used after traffic shaping to match the speed
of the broadband modem or remote interface by entering the shape average
kbps command, where kbps is a value in kilobits per second.
Caution The transmission speed entered must be less than or equal to the TX
bandwidth of the DSL or cable modem to which the router is attached.
Specifying a value greater than the modem’s TX bandwidth will result
in the modem’s becoming congested, and the benefits of applying QOS
might be lost.
d. Enter service-policy name to associate the LLQ policy map with the
traffic-shaping policy map. If the map name for the low-latency queue were
LLQ, then name would be LLQ.
e. Enter exit twice to return to global configuration mode.
Step 4 Apply these policies to the Ethernet 1 interface.
a. Enter the interface Ethernet 1 command.
b. Apply the service policy to the Ethernet 1 interface by entering
service-policy output name, where name matches the policy defined in the
traffic-shaping policy map. If the traffic-shaping policy map name were
shape, the service-policy name would also be shape.
Step 5 Enter end to leave router configuration mode.
Configuration Example
The following example shows how a Cisco 806 router can be configured to
connect to a broadband modem with limited bandwidth, while ensuring voice line
quality. Two policy maps are configured:
• Policy map LLQ
• Policy map shape
Policy map LLQ ensures that voice traffic has a strict priority queue with
bandwidth of up to 300 kbps. The policy map shape limits the total throughput to
2.2 MBps.
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password encryption
!
hostname 806-uut
!
ip subnet-zero
!
class-map match-all voice
match ip precedence 5
!
!
policy-map LLQ
class voice
priority 300
class class-default
fair-queue
policy-map shape
class class-default
shape average 2250000
service-policy LLQ
!
interface Ethernet0
ip address 1.7.65.11 255.255.0.0
!
interface Ethernet1
ip address 192.168.1.101 255.255.255.0
service-policy output shape
!
ip classless
ip http server
ip pim bidir-enable
!
line con 0
stopbits 1
line vty 0 4
login
!
!
scheduler max-task-time 5000
end
!
If both voice and data packets share the same PVC, it is important to reduce the
PVC transmit (TX) ring size. This reduces the maximum number of data packets
and fragments that can be in front of a voice packet in the hardware queue, thus
reducing latency.
Follow these steps to reduce the PVC TX ring size:
Configuration Example
The following example combines LFI, LLQ, and the PVC TX ring configurations.
class-map match-all voice
match access-group 101
!
policy-map mypolicy
class voice
priority 200
class class-default
fair-queue
!
interface Ethernet0
ip address 70.0.0.1 255.255.255.0
no ip mroute-cache
!
interface ATM0
no ip address
bundle-enable
dsl operating-mode auto
!
interface ATM0.1 point-to-point
no ip mroute-cache
pvc 1/40
encapsulation aal5mux ppp dialer
dialer pool-member 1
tx-ring-limit 3
!
interface Dialer1
bandwidth 640
• Cisco SOHO 77, SOHO 77H, SOHO 78, SOHO 91, SOHO 96 and SOHO 97
• Cisco 828
Follow the steps below to configure the Cisco router for DHCP server import:
Step 1 Configure the asynchronous transfer mode (ATM) interface and the asymmetric
digital subscriber line (ADSL) operating mode.
Step 2 Create an ATM PVC for data traffic, enter virtual circuit configuration mode, and
specify the virtual path identifier/virtual channel identifier (VPI/VCI) values, the
encapsulation type, and the dial-pool member.
Step 3 Create a dialer interface.
a. Enter configuration mode for the dialer interface.
b. Specify the MTU size as 1492.
c. Assign ip address negotiated to the dialer interface.
d. Configure the dialer group number.
e. Configure PPP encapsulation and (if needed) Challenge Handshake
Authentication Protocol (CHAP).
f. Configure IP negotiation of DNS and WINS requests.
Step 4 Define an IP DHCP pool name.
a. Configure the network and domain name (if needed) for the DHCP pool.
b. Enter the import all command.
Step 5 Configure a dialer list and a static route for the dialer interface.
Configuration Examples
The following example shows a configuration of the DHCP server import on the
Cisco 800 series and Cisco SOHO series routers.
router-820#show run
Building configuration...
Current configuration :1510 bytes
version 12.1
no service single-slot-reload-enable
no service pad
call rsvp-sync
!
interface Ethernet0
ip address 192.150.2.100 255.255.255.0
ip nat inside
!
interface ATM0
no ip address
no atm ilmi-keepalive
pvc 0/16 ilmi
!
pvc 1/40
protocol pppoe
pppoe-client dial-pool-number 1
!
bundle-enable
dsl operating-mode auto
!
interface Dialer0
ip address negotiated
ip mtu 1492
ip nat outside
encapsulation ppp
dialer pool 1
dialer-group 1
ppp authentication chap
ppp ipcp dns request
ppp ipcp wins request
!
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer0
no ip http server
!
ip nat inside source list 101 interface Dialer0 overload
access-list 101 permit ip any any
dialer-list 1 protocol ip list 101
snmp-server manager
!
voice-port 1
voice-port 2
voice-port 3
voice-port 4
!
line con 0
transport input none
stopbits 1
line vty 0 4
scheduler max-task-time 5000
end
memory-size iomem 10
ip subnet-zero
!
no ip finger
!
ip address-pool dhcp-proxy-client
ip dhcp-server 192.150.1.101
vpdn enable
no vpdn logging
!
vpdn-group 1
accept-dialin
protocol pppoe
virtual-template 1
!
call rsvp-sync
cns event-service server
!
interface Ethernet0/0
ip address 192.150.1.100 255.255.255.0
half-duplex
!
interface Ethernet0/1
no ip address
shutdown
half-duplex
!
interface ATM1/0
no ip address
no atm scrambling cell-payload
no atm ilmi-keepalive
pvc 1/40
encapsulation aal5snap
protocol pppoe
!
interface Virtual-Template1
ip address 2.2.2.1 255.255.255.0
ip mtu 1492
peer default ip address dhcp
ppp authentication chap
!
ip kerberos source-interface any
ip classless
ip route 0.0.0.0 0.0.0.0 Ethernet0/0
no ip http server
!
dialer-list 1 protocol ip permit
dial-peer cor custom
!
line con 0
exec-timeout 0 0
transport input none
line aux 0
line vty 0 4
login
end
The following example shows a configuration on the remote DHCP server on the
Cisco 800 series and Cisco SOHO series routers.
2500ref-4#show run
version 12.1
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname 2500ref-4
!
no logging console
!
ip subnet-zero
no ip domain-lookup
ip host PAGENT-SECURITY-V3 45.41.44.82 13.15.0.0
ip dhcp excluded-address 2.2.2.1
!
ip dhcp pool 1
network 2.2.2.0 255.255.255.0
dns-server 53.26.25.23
netbios-name-server 66.22.66.22
domain-name ribu.com
lease 0 0 5
!
cns event-service server
!
interface Ethernet0
ip address 192.150.1.101 255.255.255.0
interface Ethernet1
ip address 192.168.254.165 255.255.255.0
interface Serial0
no ip address
shutdown
no fair-queue
interface Serial1
no ip address
shutdown
!
ip classless
ip route 0.0.0.0 0.0.0.0 1.1.1.1
ip route 0.0.0.0 0.0.0.0 Ethernet0
no ip http server
!
dialer-list 1 protocol ip permit
line con 0
exec-timeout 0 0
transport input none
line aux 0
transport input all
line vty 0 4
login
no scheduler max-task-time
end
• The provider edge or the edge router helps in providing the subnet through
IPCP.
DHCP is no longer supported on the client side because the CPE can now receive
both the IP address and the subnet mask during the PPP setup negotiation. If the
CPE uses the DHCP servers to allocate addresses for its own network, subnets can
be assigned through the node route processor (NRP) on the network access server
(NAS) and distributed to the remote CPE DHCP servers.
Follow the steps below to configure the CPE for IPCP:
Step 1 Configure the ATM interface, and enter the ADSL operating mode.
Step 2 Configure the ATM subinterface.
a. Create an ATM PVC for data traffic, enter virtual circuit configuration mode,
and specify the VPI and VCI values.
b. Set the encapsulation of the PVC as aal5mux ppp to support data traffic.
Step 3 Create a dialer interface.
a. Enter configuration mode for the dialer interface.
b. Specify the PPP encapsulation type for the PVC.
c. Enter the ip unnumbered Ethernet 0 command to assign the Ethernet
interface to the dialer interface.
d. Configure the dialer group number.
e. Configure CHAP.
f. Enter the ppp ipcp mask request command.
g. Assign a dialer list to this dialer interface.
Step 4 Define an IP DHCP pool name.
a. Enter the import all command.
b. Enter the origin ipcp command.
Step 5 Configure the Ethernet interface, and assign an IP address pool. Enter the pool
name that you defined in Step 4.
Step 6 Configure a dialer list and a static route for the dialer interface.
Configuration Examples
The following example shows a IPCP configuration on the Cisco 827-4V router:
router-8274v-1# show run
Building configuration...
Current configuration :1247 bytes
version 12.2
no service single-slot-reload-enable
no service pad
service timestamps debug datetime msec
service timestamps log uptime
no service password-encryption
!
hostname router-8274v-1
!
no logging buffered
logging rate-limit console 10 except errors
!
username 6400-nrp2 password 0 lab
ip subnet-zero
ip dhcp smart-relay
!
ip dhcp pool IPPOOLTEST
import all
origin ipcp
lease 0 0 1
!
no ip dhcp-client network-discovery
!
interface Ethernet0
ip address pool IPPOOLTEST
no shutdown
hold-queue 32 in
!
interface ATM0
no ip address
atm ilmi-keepalive
bundle-enable
dsl operating-mode auto
hold-queue 224 in
!
interface ATM0.1 point-to-point
pvc 1/40
no ilmi manage
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
interface Dialer0
ip unnumbered Ethernet0
encapsulation ppp
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication chap callin
ppp chap hostname router-8274v-1
ppp chap password 7 12150415
ppp ipcp accept-address
ppp ipcp dns request
ppp ipcp wins request
ppp ipcp mask request
!
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer0
no ip http server
!
dialer-list 1 protocol ip permit
!
line con 0
exec-timeout 0 0
stopbits 1
line vty 0 4
login
!
scheduler max-task-time 5000
end
The following example shows an IPCP configuration on the remote server for a
Cisco 827-4V router:
6400-nrp2#show run
Building configuration...
!
ip classless
no ip http server
!
ip radius source-interface FastEthernet0/0/0
!
radius-server host 192.168.100.100 auth-port 1645 acct-port 1646
radius-server retransmit 3
radius-server attribute nas-port format d
radius-server key foo
!
line con 0
exec-timeout 0 0
transport input none
line aux 0
line vty 0 4
password lab
!
end
The following example shows an IPCP configuration on the RADIUS server for a
Cisco 827-4V router (Cisco Access Registrar 1.5):
/opt/AICar1/usrbin-4 % ./aregcmd
Access Registrar Configuration Utility Version 1.5
Copyright (C) 1995-1998 by American Internet Corporation, and
1998-2000 by
Cisco Systems, Inc. All rights reserved.
Cluster:localhost
User:admin
Password:
Logging in to localhost
400 Login failed/opt/AICar1/usrbin-5 % ./aregcmd
Access Registrar Configuration Utility Version 1.5
Copyright (C) 1995-1998 by American Internet Corporation, and
1998-2000 by
Cisco Systems, Inc. All rights reserved.
Cluster:localhost
User:admin
Password:
Logging in to localhost
[ //localhost ]
LicenseKey = SBUC-7DQF-PM1E-5HPC (expires in 51 days)
Radius/
Administrators/
--> cd radius
[ //localhost/Radius ]
Name = Radius
Description =
Version = 1.6R1
IncomingScript~ =
OutgoingScript~ =
DefaultAuthenticationService~ = local-users
DefaultAuthorizationService~ = local-users
DefaultAccountingService~ = local-file
DefaultSessionService~ =
DefaultSessionManager~ =
UserLists/
UserGroups/
Policies/
Clients/
Vendors/
Scripts/
Services/
SessionManagers/
ResourceManagers/
Profiles/
Rules/
Translations/
TranslationGroups/
RemoteServers/
Advanced/
Replication/
--> cd profile
[ //localhost/Radius/Profiles ]
ls
Entries 1 to 6 from 6 total entries
Current filter:<all>
default-PPP-users/
default-SLIP-users/
default-Telnet-users/
StaticIP/
router-8274v-1/
TB2-8274v-2/
--> ls
[ //localhost/Radius/Profiles ]
Entries 1 to 6 from 6 total entries
Current filter:<all>
default-PPP-users/
default-SLIP-users/
default-Telnet-users/
StaticIP/
router-8274v-1/
TB2-8274v-2/
--> cd router-8274v-1
[ //localhost/Radius/Profiles/router-8274v-1 ]
Name = router-8274v-1
Description =
Attributes/
--> ls
[ //localhost/Radius/Profiles/router-8274v-1 ]
Name = router-8274v-1
Description =
Attributes/
--> cd attribute
[ //localhost/Radius/Profiles/router-8274v-1/Attributes ]
cisco-avpair = "ip:wins-servers=100.100.100.100 200.200.200.200"
cisco-avpair = "ip:dns-servers=60.60.60.60 70.70.70.70"
Framed-Compression = none
Framed-IP-Address = 40.1.2.30
Framed-IP-Netmask = 255.255.255.0
Framed-MTU = 1500
Framed-Protoc
l = ppp
Framed-Routing = None
Service-Type = Framed
• Caller ID devices:
– BRONDI INDOVINO
• Fax equipment:
– Canon FAX-B155
The following devices are supported in Denmark:
• Telephones:
– Tele Danmark dana classic
– Tele Danmark Danafon Topas
• Caller ID devices:
– DORO Danmark DOROX5
Follow the steps below to configure a voice port to support caller ID, international
cadence, impedance, and ring frequency, starting in global configuration mode:
Command Task
Step 1 voice-port number Enter voice-port configuration mode.
Step 2 cptone country-code Specify settings for call-progress tone, ring
cadence, line impedance, and ring frequency.
Step 3 caller-id enable Enable caller ID support, or enter the second
command to enable caller ID support and to
caller-id alerting alerting-method
specify the alerting method.
Step 4 caller-id block Request blocking of the display of caller ID
information at the far end of the call.
Step 5 end Exit router configuration mode.
Configuration Example
The following voice-port configuration example shows two voice ports
configured for the progress tone and line characteristics for Denmark. Caller ID
is enabled on both ports, and port 1 requests that caller ID information be blocked
at the other end when a phone call originates from this port. The second port uses
the line-reversal alerting method.
!
voice-port 1
cptone dk
caller-id enable
caller-id block
timeouts call-disconnect 0
!
voice-port 2
cptone dk
caller-id alerting line-reversal
timeouts call-disconnect 0
Value Meaning
define User-defined cadence
pattern01 2 seconds on, 4 seconds off
pattern02 1 second on, 4 seconds off
pattern03 1.5 seconds on, 3.5 seconds off
pattern04 1 second on, 2 seconds off
pattern05 1 second on, 5 seconds off
pattern06 1 second on, 3 seconds off
pattern07 0.8 second on, 3.2 seconds off
pattern08 1.5 seconds on, 3 seconds off
pattern09 1.2 seconds on, 3.7 seconds off
pattern10 1.2 seconds on, 4.7 seconds off
Value Meaning
pattern11 0.4 second on, 0.2 second off, then
0.4 second on, 2 seconds off
pattern12 0.4 second on, 0.2 second off, then
0.4 second on, 2.6 seconds off
Code Impedance
600c 600-ohm complex
600r 600-ohm real
900c 900-ohm complex
900r 900-ohm real
complex1 complex 1
complex2 complex 2
The country code specified in the cptone command must represent one of the
countries for which caller ID is supported. Caller ID is disabled by default.
The default alerting method is ring 1. If the country in which the router is
installed uses a different alerting method, the appropriate alerting method must be
configured. The caller-id alerting ring command can be used in countries using
the BellCore/Telcordia standard. The caller-id alerting line-reversal, the
caller-id alerting pre-ring, and caller-id alerting ring commands can be used in
countries that do not use the BellCore/Telcordia standard.
The caller-id alerting command automatically enables caller ID support for the
specific voice port.
Note The calling party information is included in the routed on-net call, as this
information is often required for other purposes, such as billing and call
blocking. The request to block display of the calling party information on
terminating FXS ports is normally accepted by Cisco routers, but no guarantee
can be made regarding the acceptance of the request by other equipment.
Configuration Example
The following example shows a CAR configuration:
interface ATM0.1 point-to-point
mtu 576
Configuration Example
The following example shows configuration of a Cisco 806 router supporting two
devices with the addresses 20.0.0.14, and 20.0.0.16, as shown in Figure 8-1.
Figure 8-1 Cisco 806 Router Performing Network Address Translation for Two
Devices
20.0.0.14
Cisco 806
20.0.0.0 10.0.0.0
NAT default
inside server
65369
20.0.0.16
Several NAT statements direct traffic to the address 20.0.0.14. All packets not
matching those NAT statements will be routed to 20.0.0.16.
Current configuration :942 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname c806-1
!
ip subnet-zero
!
ip ssh time-out 120
ip ssh authentication-retries 3
!
crypto mib ipsec flowmib history tunnel size 200
crypto mib ipsec flowmib history failure size 200
!
interface Ethernet0
ip address 20.0.0.1 255.0.0.0
ip nat inside
hold-queue 100 out
!
interface Ethernet1
ip address 10.0.0.1 255.0.0.0
ip nat outside
!
ip nat inside source static tcp 20.0.0.14 80 interface Ethernet1 80
ip nat inside source static udp 20.0.0.14 161 interface Ethernet1 161
!
ip nat inside source static 20.0.0.16 interface Ethernet1
! 20.0.0.16 is defined as the catch-all address
!
ip nat inside source static udp 20.0.0.14 1000 interface Ethernet1
1000
! udp port 1000 traffic will be routed to 20.0.0.14
!
ip nat inside source static tcp 20.0.0.14 23 interface Ethernet1 23
! telnet traffic will be routed to 20.0.0.14
!
ip classless
no ip http server
!
!
line con 0
stopbits 1
line vty 0 4
password lab
login
!
Command Task
Step 1 voice class permanent 1 Configure a voice class.
Step 2 signal timing oos timeout disabled Disable the assertion of the receive
out-of-service (oos) pattern to the PBX when
signaling packets are lost.
Step 3 exit Exit voice class configuration mode.
Step 4 voice service voatm Enter voice service configuration mode.
Step 5 session protocol aal2 Enter voice-service session configuration
mode, and specify AAL2 trunking.
Command Task
Step 6 mode bles Indicate that VOATM is to be used in
broadband loop emulation service (BLES)
mode.
Step 7 exit Enter the exit command to leave session
protocol mode. Enter exit again to leave voice
service configuration mode.
Step 8 interface atm0 Enter ATM 0 interface configuration mode.
Step 9 pvc vpi vci Specify the virtual path identifier (VPI) and
the virtual channel identifier (VCI) of the
PVC.
Step 10 vbr-rt pcr acr bcs Specify the variable bit rate-real time peak
cell rate and average cell rate in kbps, and the
burst cell size in number of cells.
Step 11 encapsulation aal2 Specify ATM adaptation layer 2 (AAL2) type
encapsulation.
Step 12 no atm cell-clumping-disable Ensure that sufficient bandwidth is allocated
for data packets when voice calls are in
progress.
Step 13 exit Exit ATM 0 interface configuration mode.
Step 14 dial-peer voice tag voatm Place the router in dial-peer voice
configuration mode.
Step 15 session protocol aal2-trunk Configure the session protocol to support
AAL2-trunk permanent (private line) trunk
calls.
Step 16 session target atm0 pvc vpi/vci cid cid This command has three parameters: vpi
(virtual path identifier), vci (virtual channel
identifier), and cid (AAL2 channel identifier).
Step 17 codec aal2 profile Enter codec aal2-profile atmf 9 g711alaw to
specify that only G.711 a-law is used for
voice dial peer. Enter codec aal2-profile
atmf 9 g711ulaw to specify that only G.711
mu-law is used for voice dial peer.
Command Task
Step 18 destination-pattern destination string Associate a dial-peer with a voice port. The
destination string is the phone number in
E.164 format that must match the destination
string configured for the voice-port.
Step 19 voice-class permanent 1 Associate this dial peer with the configured
voice class.
Step 20 no vad Specify no voice activity detection (VAD).
Step 21 exit Exit dial peer voice configuration mode.
Step 22 voice port # Enter voice port configuration mode.
Step 23 connection trunk destination-pattern Specify the dialer string. The destination
pattern must match the destination-string
configured for the dial peer.
Step 24 playout-delay mode fixed no-timestamps Play out the AAL2 packet at a fixed rate, and
ignore the time stamps carried in the packet.
Step 25 end Exit router configuration mode.
Note One phone line requires a minimum setting of 78 kbps for both peak cell rate
(PCR) and allowed cell rate (ACR) values.
Configuration Example
The following example shows the configuration for two voice ports using
Profile 9, and the G.711 a-law codec. VBR-RT, PCR, and ACR values are 312 to
accommodate four phone lines, although only two phone lines are currently
configured.
voice service voatm
!
session protocol aal2
mode bles
!
!
voice class permanent 1
signal timing oos timeout disabled
!
interface atm 0
no atm cell-clumping-disable
pvc 1/100
vbr-rt 312 312 32
encapsulation aal2
!
voice-port 1
playout-delay mode fixed no-timestamps
cptone DK
timeouts wait-release 3
connection trunk 8881052
caller-id enable
!
voice-port 2
playout-delay mode fixed no-timestamps
cptone DK
timeouts wait-release 3
connection trunk 8881053
caller-id enable
!
!dial-peer voice 1000 voatm
destination-pattern 8881052
voice-class permanent 1
session protocol aal2-trunk
session target ATM0 pvc 1/100 16
codec aal2-profile ATMF 9 g711alaw
no vad
!
dial-peer voice 1001 voatm
destination-pattern 8881053
voice-class permanent 1
session protocol aal2-trunk
session target ATM0 pvc 1/100 17
codec aal2-profile ATMF 9 g711alaw
no vad
!
Use the no form of this command to disable continuity checking on the segment.
no oam-pvc manage cc segment direction [ source | sink | both ]
Configuration Example
The following configuration example activates CC over the segment and causes
the router to function as the source.
interface ATM0
ip address 10.0.0.3 255.255.255.0
pvc 0/33
The following configuration example activates CC over the segment and causes
the router to function as the sink.
interface ATM0
ip address 10.0.0.3 255.255.255.0
pvc 0/33
oam-pvc manage cc segment direction sink
!
end
The following configuration example activates CC over the segment and causes
the router to function both as the source of CC cells and as the sink:
interface ATM0
ip address 10.0.0.3 255.255.255.0
pvc 0/33
oam-pvc manage cc segment direction both
!
end
interface ATM0
ip address 10.0.0.3 255.255.255.0
pvc 0/33
no oam-pvc manage cc
!
end
Configuration Example
The following configuration example sets the CC activation and deactivation
counts, as well as the retry frequency:
interface ATM0
ip address 10.0.0.3 255.255.255.0
pvc 0/33
oam-pvc manage cc segment direction source
retry activation-count 10 deactivation-count 10 retry-frequency 3
!
end
Configuration Example
The following configuration example denies segment CC:
interface ATM0
ip address 10.0.0.3 255.255.255.0
pvc 0/33
oam-pvc manage cc deny
!
end
Command Task
Step 1 interface atm 0 Enter configuration mode for the ATM
interface.
Step 2 pvc routerA vpi/vci Assign PVC to the name router A with the vpi
and vci values.
Step 3 oam-pvc manage 3 Enable OAM management with a frequency
of 3 seconds between OAM cell
transmissions.
Step 4 oam retry 5 5 10 Configure the up count, down count, and retry
frequency.
The following example enables OAM management on an ATM PVC. The PVC is
assigned the name router A and the VPI and VCI are assigned 0 and 32,
respectively. OAM management is enabled with a frequency of 3 seconds between
OAM cell transmissions.
interface atm 2/0
pvc routerA 0/32
oam-pvc manage 3
oam retry 5 5 10
Example Output
The following example output of the debug atm oam cc command records activity
beginning with the entering of the oam-pvc manage cc command, and ending
with the entering of the no oam-pvc manage cc command. The ATM 0 interface
is specified, and the “both” segment direction is specified. The output shows an
activation request sent and confirmed, a series of CC cells sent by the routers on
each end of the segment, and a deactivation request and confirmation.
router#debug atm oam cc interface atm0
Generic ATM:
ATM OAM CC cells debugging is on
router#
00:15:05: CC ACTIVATE MSG (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM
Type:8 OAM Func:1 Direction:3 CTag:5
00:15:05: CC ACTIVATE CONFIRM MSG (ATM0) O:VCD#1 VC 1/40 OAM Cell
Type:4 OAM Type:8 OAM Func:1 Direction:3 CTag:5
00:15:06: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1
00:15:07: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:08: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:09: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:10: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:11: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:12: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:13: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:14: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:15: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:16: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:17: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:18: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:19: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:4
00:15:19: CC DEACTIVATE MSG (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM
Type:8 OAM Func:1 Direction:3 CTag:6
00:15:19: CC DEACTIVATE CONFIRM MSG (ATM0) O:VCD#1 VC 1/40 OAM Cell
Type:4 OAM Type:8 OAM Func:1 Direction:3 CTag:6
The following table describes significant fields.
Field Description
00:15:05 Time stamp.
CC ACTIVATE MSG Message type and interface.
(ATM0)
0 Source.
1 Sink.
Field Description
VC 1/40 Virtual circuit identifier.
Direction:3 Indication of the direction in which the cells are
traveling. 1 indicates local router operates as a sink.
2 indicates local router operates as a source. 3
indicates both routers operate as source and sink.
The Cisco Easy VPN client feature supports two modes of operation:
• Client—Specifies that Network Address Translation/Port Address
Translation (NAT/PAT) be done, so that the PCs and other hosts at the client
end of the VPN tunnel form a private network that does not use any IP
addresses in the destination server’s IP address space.
• Network Extension—Specifies that the PCs and other hosts at the client end
of the VPN tunnel should be given IP addresses in the destination enterprise
network’s IP address space, so that they form one logical network.
Both modes of operation also optionally support split tunneling, which allows
secure access to corporate resources through the VPN tunnel while also allowing
Internet access through a connection to an ISP or other service (thereby
eliminating the corporate network from the path for Web access). This
configuration is enabled by a simple access list implemented on the IPSec server.
Note Cisco 800 series routers are supported as IPSec clients of VPN 3000
concentrators. Support for other IPSec servers will be available in a future
release. Be sure to refer to the Cisco IOS release notes for the current release
to determine if there are any other limitations on the use of Cisco Easy VPN
Client.
The release note Cisco EZVPN Client for the Cisco uBR905/uBR925 Cable Access
Routers provides instructions for configuring the DHCP server pool and the
Easy VPN client profile required for implementing Easy VPN. The release note
also provides configuration examples for the IPSec server and descriptions of
commands for managing Easy VPN.
Configuration Example
This section provides a client mode configuration example for the Cisco 827
router.
The following example configures a Cisco 827 router as an IPSec client, using the
Cisco Easy VPN feature in the client mode of operation. This example shows the
following components of the Cisco Easy VPN client configuration:
• DHCP server pool—The ip dhcp pool command creates a pool of IP
addresses to be assigned to the PCs connected to the router’s Ethernet 1
interface. The pool assigns addresses in the class C private address space
Note If DNS is also configured on the router, the peer option also
supports a host name instead of an IP address.
• The second crypto ipsec client ezvpn hw-client command (ATM 0 interface
configuration mode) assigns the EzVPN client configuration to the ATM 0
interface, so that all traffic received and transmitted on that interface is sent
through the VPN tunnel.
The following is an example output of the show running-config command:
default-router 192.168.100.1
!
ip ssh time-out 120
ip ssh authentication-retries 3
!
crypto ipsec client ezvpn hw-client
group hw-client-groupname key hw-client-password
mode client
peer 188.185.0.5
!
interface Ethernet0
ip address 192.168.100.1 255.255.255.0
hold-queue 100 out
!
interface ATM0
ip address 192.168.101.18 255.255.255.0
no atm ilmi-keepalive
protocol ip 192.168.101.19 broadcast
encapsulation aal5snap
!
dsl operating-mode auto
crypto ipsec client ezvpn hw-client
!
ip classless
ip route 0.0.0.0 0.0.0.0 ATM0
ip route 50.0.0.0 255.0.0.0 40.0.0.19
ip http server
ip pim bidir-enable
!
line con 0
stopbits 1
line vty 0 4
login
!
Note A value of 0 specifies that the timer will never expire and that the
connection will always be up.
g. Enter dialer hold-queue 100 to set the queue to a size that will hold packets
of interest before the connection is established.
h. Enter dialer-group 1 to specify the dialer list that defines traffic of interest.
i. Leave Dialer 1 interface configuration mode by entering exit.
Step 5 In the global configuration mode, enter the dialer-list 1 protocol ip permit
command to define IP traffic as the traffic of interest.
Step 6 Create a static route for the Dialer 1 interface by entering the ip route
0.0.0.0 0.0.0.0 dialer 1 permanent command.
Step 7 Enter end to leave configuration mode.
Configuring WFQ
Follow the steps below to apply WFQ to the ATM interface of a Cisco router.
Example Configuration
The following configuration applies WFQ to PVC 0/33 on the ATM 0.1 interface.
The policy map named wfq is created, and WFQ is applied to the default class
referenced in that policy map. Then, wfq is referenced in the ATM 0.1 interface
configuration.
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password encryption
!
hostname 806-uut
!
ip subnet-zero
!
policy-map wfq
class class-default
fair-queue
!
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
!
interface atm0.1
no ip address
pvc 0/33
service-policy output wfq
!
ip classless
ip http server
ip pim bidir-enable
!
line con 0
stopbits 1
line vty 0 4
login
!
scheduler max-task-time 5000
end
!
Command Task
Step 1 dsl noise-margin Set the noise margin offset.
Step 2 max-tone-bits Set the maximum bits per tone limit.
Step 3 gain-setting rx-offset Set the receive gain offset.
Step 4 gain-setting tx-offset Set the transmit gain offset.
Configuration Example
The following is a configuration example for the dsl command.
interface ATM0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
dsl noise-margin 0
dsl max-tone-bits 14
dsl gain-setting tx-offset 0
dsl gain-setting rx-offset 1
of time to the training process, and retrieval is not always necessary after the
router has successfully trained. You must use the dsl enable-training-log
command to enable the retrieval of this log. The no form of this command disables
retrieval of the DSL training log.
dsl enable-training-log
no dsl enable-training-log
Retrieving the DSL Training Log and Then Disabling Further Retrieval of the
Training Log
Complete the following tasks to retrieve the training log, examine it, and then
disable the router from retrieving the training log the next time it trains with the
DSLAM.
To revert to using the primary firmware, enter the no form of this command.
no dsl firmware secondary
Note The router must retrain in order for the configuration changes to take effect.
To retrain the line, you can unplug the DSL cable from the DSL socket on the
back of the router and then plug the DSL cable back in again.
You can use the show dsl interface atm number command to compare firmware
versions in use before retraining the DSL line, and after retraining.
Output Example
The following example output contains show dsl interface atm command output
before the dsl secondary firmware command is added to the configuration.
827-sus2#sh dsl int atm0
ATU-R (DS) ATU-C (US)
Modem Status: Showtime (DMTDSL_SHOWTIME)
DSL Mode: ITU G.992.1 (G.DMT)
ITU STD NUM: 0x01 0x01
Vendor ID: 'ALCB' 'GSPN'
Vendor Specific:0x0000 0x0002
Vendor Country: 0x00 0x00
Capacity Used: 66% 74%
Noise Margin: 16.5 dB 17.0 dB
Output Power: 8.0 dBm 12.0 dBm
Attenuation: 0.0 dB 4.0 dB
Defect Status: None None
Last Fail Code: None
Selftest Result:0x49
Subfunction: 0x02
Interrupts: 652 (1 spurious)
Activations: 1
SW Version: 3.8129
FW Version: 0x1A04
After adding the dsl firmware secondary command to the configuration and
retraining, the show dsl interface ATM0 output shows that the software version
has changed to 3.7123.
827-sus2#sh dsl int atm0
ATU-R (DS) ATU-C (US)
Modem Status: Showtime (DMTDSL_SHOWTIME)
DSL Mode: ITU G.992.1 (G.DMT)
ITU STD NUM: 0x01 0x01
Vendor ID: 'ALCB' 'GSPN'
Vendor Specific:0x0000 0x0002
Vendor Country: 0x00 0x00
Capacity Used: 71% 74%
Noise Margin: 18.0 dB 17.0 dB
Output Power: 7.5 dBm 12.0 dBm
Attenuation: 0.0 dB 4.0 dB
Defect Status: None None
Last Fail Code: None
Selftest Result:0x00
Subfunction: 0x02
Interrupts: 1206 (2 spurious)
Activations: 2
SW Version: 3.7123
FW Version: 0x1A04
Configuration Example
The following example shows configuration of a Cisco 827 router using
secondary DSL firmware.
827-sus2#sh run
Building configuration...
!
ip ssh time-out 120
ip ssh authentication-retries 3
!
interface Ethernet0
ip address 192.168.5.23 255.255.255.0
no cdp enable
hold-queue 100 out
!
interface Virtual-Template1
ip address 2.2.3.4 255.255.255.0
!
interface ATM0
no ip address
no atm ilmi-keepalive
pvc 1/40
encapsulation aal5mux ppp Virtual-Template1
!
dsl operating-mode itu-dmt
dsl firmware secondary ===========> New CLI
!
ip classless
ip http server
ip pim bidir-enable
!
line con 0
exec-timeout 0 0
stopbits 1
line vty 0 4
login
!
scheduler max-task-time 5000
end
827-sus2#
Caution CRWS is unable to perform automatic updates if the FTP username and
password values it places in the configuration file are changed.
If you need to use FTP to manually copy system images to Flash memory, see the
instructions for adding an FTP username and password to the configuration file at
the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
ffun_c/ffcprt2/fcf008.htm
With the authentication proxy feature, users can log into the network or access the
Internet via HTTP. Their specific access profiles are automatically retrieved and
applied from a Cisco Secure ACS or other RADIUS or TACACS+ authentication
server. The user profiles are active only when there is active traffic from the
authenticated users.
The authentication proxy is compatible with other Cisco IOS security features
such as Network Address Translation (NAT), Context-based Access Control
(CBAC), IP Security (IPSec) encryption, and VPN client software.
For instructions on configuring authentication proxy, refer to the
Cisco IOS Security Configuration Guide.
Using CBAC inspection rules, you can configure alerts and audit trail information
on a per-application protocol basis. For example, if you want to generate audit
trail information for HTTP traffic, you can specify that in the CBAC rule covering
HTTP inspection.
For instructions on configuring CBAC audit trails and alerts, refer to the
Cisco IOS Security Configuration Guide.
Use the information in this chapter to help isolate problems you might encounter
with Cisco 800 series and Cisco SOHO series routers or to rule out the router as
the source of the problem. This chapter contains the following sections:
• Before Contacting Cisco or Your Reseller, page 9-2
• ADSL Troubleshooting, page 9-2
• G.SHDSL Troubleshooting, page 9-3
• ATM Troubleshooting Commands, page 9-6
• Troubleshooting Telephone Interfaces, page 9-15
• Troubleshooting Serial Line Problems, page 9-16
• Software Upgrade Methods, page 9-54
• Recovering a Lost Password, page 9-54
• Managing the Cisco Router Web Setup Tool, page 9-59
Before troubleshooting a software problem, you must connect a terminal or PC to
the router via the light-blue console port. (For information on making this
connection, see the documentation listing in the “Related Documents” section on
page xxv.) With a connected terminal or PC, you can read status messages from
the router and enter commands to troubleshoot a problem.
You can also remotely access the interface (Ethernet, ADSL, or telephone) by
using Telnet. The Telnet option assumes that the interface is up and running.
ADSL Troubleshooting
This section describes some asymmetric digital service line (ADSL)
troubleshooting checks that you can perform if the router is not working properly.
If you experience trouble with the ADSL connection, make sure to verify the
following:
• That the ADSL line is connected and is using pins 3 and 4. For more
information on the ADSL connection, refer to the hardware guide for your
router.
• That the ADSL CD LED is on. If it is not on, the router may not be connected
to the digital subscriber line access multiplexer (DSLAM). For more
information on the ADSL LEDs, refer to the hardware installation guide
specific to your router.
• That you are using the correct Asynchronous Transfer Mode (ATM) variable
path indentifier/variable circuit identifier (VPI/VCI).
• That the DSLAM supports discrete multi-tone (DMT) Issue 2.
G.SHDSL Troubleshooting
Symmetrical high-data-rate digital subscriber line (G.SHDSL) is available on
Cisco 828 and Cisco SOHO 78 routers. This section describes some G.SHDSL
troubleshooting checks that you can perform if the router is not working properly.
If you experience trouble with the G.SHDSL connection, verify the following:
• That the G.SHDSL line is connected and is using pins 3 and 4. For more
information on the G.SHDSL connection, refer to the Cisco 828 Router and
SOHO 78 Router Hardware Installation Guide.
• That the G.SHDSL CD LED is on. If it is not on, the router may not be
connected to the DSLAM. For more information on the G.SHDSL LEDs,
refer to the Cisco 828 Router and SOHO 78 Router Hardware Installation
Guide.
• That you are using the correct ATM VPI/VCI.
• That the DSLAM supports G.SHDSL.
Table 9-1 describes possible command output for the show dsl interface
command. Each line in the command output example corresponds to a row in this
table.
Output Description
Equipment Type • Customer premises equipment (CPE), if
connected to a DSLAM.
• Central offices (COs); if the routers are
connected back to back, then one of the routers
can act as a CO.
Operating Mode G.SHDSL annex configuration
Clock Rate Mode Upstream and downstream bit rate configuration.
Either AUTO for fixed.
Reset Count Number of times the G.SHDSL chip has been reset
since power-up.
Output Description
Requested rate User-specified bit rate requirement.
Actual rate The actual bit rate that the transceiver is using.
Modem Status • Handshake, when local transceiver tries to reach
the far-end transceiver.
• Training; indicates that the startup training is in
progress.
• Data, if successfully trained.
Received SNR The received signal-to-noise ratio (SNR).
Loop Attenuation The difference in decibels (dB) between the power
received at the near-end and the power transmitted
from the far-end.
Transmit Power Local symmetric digital subscriber line transmission
unit (STU) transmit power.
Receiver Gain Total receiver gain.
Last Activation Status Defines the last failure state of the G.SHDSL chip.
CRC Errors Cyclic redundancy check (CRC) errors.
Chipset Version Vendor’s chipset information.
Firmware Version Vendor’s firmware release version.
Country Code The country identification for the far end.
Provider Code Identification of the vendor.
Vendor data Vendor-specific information.
Number of LOS failures Loss of synchronization counter increased when it
contains one or more error in the framing bits. If the
counter continues to increase during or after
training, the line might be noisy or the cable is not
connected.
Number of LOSQ failures Loss of signal quality counter is increased when
SNR is below the threshold.
Output Description
Number of code violations Code violation is defined as a count of the CRC
anomalies occurring during the accumulation
period.
Number of errored seconds An errored second is a count of 1-second intervals
during which one or more CRC anomalies/loss of
sync words are declared.
Number of severely errored seconds A severely errored second is a count of 1-second
intervals during which 50 or more CRC anomalies
are declared.
Number of unavailable seconds An unavailable second is a count of 1-second
intervals for which the DSL line is unavailable.
This command sends five OAM F5 loopback packets to the DSLAM (segment
OAM packets). If the PVC is configured at the DSLAM, the ping is successful.
To test whether the PVC is being used at the aggregator, enter the following
command:
Router# ping atm interface atm 0 1 200 end-loopback
This command sends end-to-end OAM F5 packets, which are echoed back by the
aggregator.
Table 9-2 describes possible command output for the show interface command.
Each line in the command output example corresponds to a row in this table.
.
Table 9-2 show interface Command Output Description
Output Description
ATM0 is up, line protocol is up • The ATM line is up and operating correctly.
Other possible messages:
ATM0 is down, line protocol is down • The ATM interface has been disabled with the
shutdown command.
ATM0 is down, line protocol is down • The ATM line is down, possibly because the
ADSL cable is disconnected or because the
wrong type of cable is connected to the ATM
port.
ATM0.1 is up, line protocol is up • The first ATM subinterface is up and operating
Other possible messages: correctly.
Output Description
Ethernet0 is up, line protocol is up • The Ethernet interface is connected to the
network and operating correctly.
Other possible messages:
Ethernet0 is up, line protocol is down • The Ethernet interface has been correctly
configured and enabled, but the Ethernet cable
might be disconnected from the LAN.
Ethernet0 is administratively down, line
protocol is down • The Ethernet interface has been disabled with
the shutdown command, and the interface is
disconnected.
Dialer1 is up, line protocol is up • Dialer1 is up and operating correctly.
Another possible message:
Dialer1 is down, line protocol is down • Dialer1 is not operating, possibly because the
interface has been brought down with the
shutdown command or the ADSL cable is
disconnected.
Dialer1 is down, line protocol is down • This is a standard message and does not indicate
anything wrong with the configuration
The following is an example of output from the show interface atm command:
tw_820#sh atm int atm 0
Interface ATM0:
AAL enabled: AAL5 , Maximum VCs:11, Current VCCs:0
Field Description
ATM interface Interface number. Always 0 for the Cisco 827 routers.
AAL enabled Type of AAL enabled. The Cisco 827 routers support AAL5.
Maximum VCs Maximum number of virtual connections this interface
supports.
Current VCCs Number of active virtual channel connections (VCCs).
Maximum Maximum number of transmit channels.
Transmit
Channels
Max Datagram The configured maximum number of bytes in the largest
Size datagram.
PLIM Type Physical layer interface module (PLIM) type
Caution Debugging is assigned a high priority in your router CPU process, and it can
render your router unusable. For this reason, use debug commands only to
troubleshoot specific problems. The best time to use debug commands is during
periods of low network traffic so that other activity on the network is not adversely
affected.
Additional documentation You can find additional information and documentation about the
debug commands in the Debug Command Reference document on
the Cisco IOS software documentation CD-ROM that came with
your router.
If you are not sure where to find this document on the CD-ROM, use
the Search function in the Verity Mosaic browser that comes with
the CD-ROM.
Disabling debugging To turn off any debugging, enter the undebug all command.
Viewing debug message To view debug messages on the console, enter the logging console
debug command.
Telnet sessions If you want to use debug commands during a Telnet session with
your router, you must first enter the terminal monitor command.
This command displays ATM events that occur on the ATM interface processor
and is useful for diagnosing problems in an ATM network. It provides an overall
picture of the stability of the network.
If the interface is successfully communication with the DSLAM at the telephone
company, the modem state is 0x10. If the interface is not communicating with the
DSLAM, the modem state is 0x8.
The following output indicates that the ADSL line is up (training successful):
00:02:57: DSL: Send ADSL_OPEN command.
00:02:57: DSL: Using subfunction 0xA
00:02:57: DSL: Using subfunction 0xA
00:02:57: DSL: Sent command 0x5
00:02:57: DSL: Received response: 0x26
00:02:57: DSL: Unexpected response 0x26
00:02:57: DSL: Send ADSL_OPEN command.
00:02:57: DSL: Using subfunction 0xA
00:02:57: DSL: Using subfunction 0xA
00:02:57: DSL: Sent command 0x5
00:03:00: DSL: 1: Modem state = 0x8
00:03:02: DSL: 2: Modem state = 0x10
00:03:05: DSL: 3: Modem state = 0x10
00:03:07: DSL: 4: Modem state = 0x10
00:03:09: DSL: Received response: 0x24
00:03:09: DSL: Showtime!
00:03:09: DSL: Sent command 0x11
00:03:09: DSL: Received response: 0x61
00:03:09: DSL: Read firmware revision 0x1A04
00:03:09: DSL: Sent command 0x31
00:03:09: DSL: Received response: 0x12
00:03:09: DSL: operation mode 0x0001
00:03:09: DSL: SM: [DMTDSL_DO_OPEN -> DMTDSL_SHOWTIME]
In case of failure, you may see the modem state remain at 0x8 and not move to
0x10:
00:02:57: DSL: Send ADSL_OPEN command.
00:02:57: DSL: Using subfunction 0xA
00:02:57: DSL: Using subfunction 0xA
The debug atm packet command displays all process-level ATM packets for both
outbound and inbound packets. This command is useful for determining whether
packets are being received and transmitted correctly.
Caution Because the debug atm packet command generates a significant amount of
output for every packet processed, use it only when network traffic is low so that
other system activities are not adversely affected.
Table 9-5 describes the fields shown in the debug atm packet command output.
Field Description
ATM0 Interface that is generating the packet.
(O) Output packet. (I) would mean receive packet.
Pak size Packet size in bytes.
VCD: 0xn Virtual circuit associated with this packet, where n is some
value.
VPI: 0xn Virtual path identifier for this packet, where n is some value.
DM: 0xn Descriptor mode bits, where n is some value.
MUXETYPE: Multiplex type.
n
Length: n Total length of the packet (in bytes) including the ATM
header(s).
Detecting Problems
Use the following steps to detect clocking conflicts on your serial interface:
Step 1 Enter the show interfaces serial 0 privileged EXEC command on the routers at
both ends of the link.
Step 2 Examine the output for cyclic redundancy check (CRC) or framing errors and
aborts.
If the number of CRC or framing errors exceeds an approximate range of 0.5 to
2.0 percent of traffic on the serial interface, clocking problems are likely to exist
somewhere in the WAN.
Step 3 Isolate the source of the clocking conflicts by performing a series of ping tests and
loopback tests (both local and remote).
Step 4 Reenter the show interfaces serial 0 privileged EXEC command on the routers at
both ends of the link. Determine if CRC and framing errors are increasing and if
so, where they are accumulating.
If input errors are accumulating on both ends of the connection, clocking of the
CSU is the likely problem. If input errors are accumulating on one end of the
connection, clocking of the DSU or cabling are the likely problems. If aborts are
occurring on one end of the connection, the other end could be sending bad
information or there could be a problem with the serial line.
Table 9-8 describes possible CSU/DSU clocking problems your router might be
experiencing and the solutions for solving those problems.
Symptom Solution
Incorrect CSU configuration Perform the following tasks in the following order:
• Determine whether the CSUs at both ends of the serial line
agree on the clock source (local or line).
• If the CSUs do not agree, configure them to do so.
• Check the line build out (LBO) setting on the CSU to ensure
that the impedance matches that of the physical line. For
information on configuring your CSU, refer to your CSU
documentation.
Incorrect DSU configuration Perform the following steps in the following order:
• Determine whether the DSUs at both ends of the serial line have
serial clock transmit external (SCTE) mode enabled.
• If SCTE is not enabled on both ends of the connection, enable
it.
• For any interface that is connected to a line of 128 kbps or
faster, SCTE must be enabled.
• Make sure that ones density is maintained, which requires that
the DSU use the same framing and coding schemes (for
example, Extended Superframe Format [ESF] and Binary
8-Zero Substitution [B8ZS]) that are used by the leased line or
other carrier service.
• Check with your leased line provider for information on its
framing and coding schemes.
• If your carrier service uses Alternate Mark Inversion (AMI)
coding, either invert the transmit clock on both sides of the link
or run the DSU in bit-stuff mode. For information on
configuring your DSU, refer to your DSU documentation.
Step 1 Place the CSU/DSU in local loop mode (refer to your CSU/DSU documentation).
In local loop mode, the use of the line clock (from the T1 service) is terminated,
and the DSU is forced to use the local clock.
Step 2 Enter the show interfaces serial 0 privileged EXEC command to determine if the
line status changes from “line protocol is down” to “line protocol is up (looped),”
or if it remains down.
If the line protocol comes up when the CSU or DSU is in local loopback mode, a
problem could be occurring on the remote end of the serial connection. If the
status line does not change state, there is a possible problem in the router,
connecting cable, or CSU/DSU.
If the problem appears to be local, enter the debug serial interface privileged
EXEC command and go on to the next step.
Step 3 Take the CSU/DSU out of local loop mode.
When the line protocol is down, the debug serial interface command output will
indicate that keepalive counters are not incrementing.
Step 4 Place the CSU/DSU in local loop mode again.
This action should cause the keepalive packets to begin to increment. Specifically,
the values for mineseen and yourseen keepalives will increment every 10 seconds.
This information will appear in the debug serial interface output.
If the keepalives do not increment, there may be a timing problem on the interface
card or on the network.
Step 5 Check the local router and CSU/DSU hardware, and any attached cables.
Make certain the cables are within the recommended lengths (no more than 50 feet
[15.24 meters], or 25 feet [7.62 meters] for a T1 link). Make certain the cables are
attached to the proper ports. Swap faulty equipment as necessary.
Step 1 Put the remote CSU or DSU into remote loopback mode (refer to the your
CSU/DSU documentation).
Step 2 Enter the show interfaces serial 0 privileged EXEC command to determine if the
line protocol remains up with the status line indicating “Serial x is up, line
protocol is up (looped),” or if it goes down with the status line indicating “line
protocol is down.”
If the line protocol remains up (looped), the problem is probably at the remote end
of the serial connection (between the remote CSU/DSU and the remote router).
Perform both local and remote tests at the remote end to isolate the problem
source.
If the line status changes to “line protocol is down” when remote loopback mode
is activated, make certain that ones density is being properly maintained. The
CSU/DSU must be configured to use the same framing and coding schemes used
by the leased-line or other carrier service (for example, ESF and B8ZS).
Step 1 From privileged EXEC command mode, enter the show interfaces serial 0
command.
If you see the line Serial0 is up, line protocol is up, the serial line is
functioning properly. You do not need to take further action.
Step 2 If you see one of the following messages, refer to Table 9-9:
• Serial 0 is down, line protocol is down.
• Serial 0 is up, line protocol is down.
• Serial 0 is up, line protocol is up (looped).
• Serial 0 is administratively down, line protocol is up.
Step 1 In privileged EXEC command mode, enter the show line 1 command.
Check the Modem state field in the output. If the modem state is Idle and CTS
noDSR DTR RTS, the connection between your modem and router is functioning
properly.
Step 2 If you see one of the following modem states, see Table 9-10:
• Ready –
• Ready not CTS noDSR DTR RTS
• Ready CTS DSR DTR RTS
• Ready CTS* DSR* DTR RTS
Problem Solution
Incorrect cabling. Check the cabling between the modem and the router. Refer to the
Cisco 805 Router Hardware Installation Guide for information on how to
select the serial cable and how to connect the modem.
Hardware problem. • Check the cabling between the modem and the router. Refer to the
Cisco 805 Router Hardware Installation Guide for information on
how to select the serial cable and how to connect the modem.
• Check all hardware for damage, including cabling (broken wires),
adapters (loose pins), ports, and modem.
Modem control is not • Use the show line 1 privileged EXEC command on the router. The
enabled on the router. output should show inout or RIisCD in the Modem column, which
indicates that modem control is enabled on the line of the router.
• If necessary, configure modem control by using the modem inout
command in asynchronous line configuration mode.
Problem Solution
Incorrect cabling Check the cabling between the modem and the router. Refer to the
Cisco 805 Router Hardware Installation Guide for information on how to
select the serial cable and how to connect the modem.
Modem hardware problem Check the modem's physical connection. Make sure the modem is on and
is connected securely to the correct port. Make sure the transmit and
receive indicator lights flash when the chat script is running.
Problem Solution
No packets of interest • Use the show running-config privileged EXEC command to view the
defined router configuration. Check the dialer-list command entries to see
which access lists, if any, are being used to define interesting traffic.
• Make sure that the access lists referenced by the dialer-list
commands specify all traffic that should bring the link up (interesting
traffic).
• If necessary, modify the access list commands so that they define the
proper traffic as interesting.
Missing chat script • Use the debug chat privileged EXEC command to check whether
there is a chat script running.
• If there is no chat script running, use the start-chat privileged EXEC
command or another appropriate command to start the chat script on
the line.
Bad chat script • Establish a reverse Telnet session to the modem, and step through
each step of the chat script.
• Verify that the command response to each chat script step is correct.
• Fix any inconsistencies you find in the chat script.
Problem Solution
Incorrect cabling Check the cabling between the modem and the router. Refer to the
Cisco 805 Router Hardware Installation Guide for information on how to
select the serial cable and how to connect the modem.
Modem control not • Observe the remote modem to see whether it is receiving a data
enabled on router terminal ready (DTR) signal from the router. Most modems have a
DTR indicator light. Check the modem documentation to interpret the
indicator lights.
• If the DTR indicator light is on, the modem is seeing a DTR signal
from the router. You can also enter the show line 1 privileged EXEC
command to check for DTR. If the Modem state shows the string
noDTR, then the router is configured to hold DTR low, and the
modem is not seeing a DTR signal.
• Configure modem control by entering either the modem inout or the
modem ri-is-cd command in the asynchronous line configuration
mode.
Remote modem not set to • Check the remote modem to see if it is set to auto-answer. Usually, an
auto-answer AA indicator light will be on when auto-answer is set.
• Set the remote modem to auto-answer if it is not already set. To find
out how to verify and change the modem’s settings, refer to your
modem documentation.
Wrong telephone line • Make sure that you are using the correct telephone line. Replace the
attached to remote modem remote modem with a telephone, and call again. If the phone rings,
you are using the correct telephone line.
• Contact the telephone company to make sure that the line is good.
Remote modem not • Make sure that the remote modem is attached to a router or other
attached to a router device that is asserting DTR.
• Most modems have an LED indicator for DTR. Check to make sure
that this indicator comes on.
Problem Solution
Modem speed setting is not • Enter the show line 1 privileged EXEC command on the router. The
locked. output for the serial port should indicate the currently configured
transmit (Tx) and receive (Rx) speeds.
• If the line is not configured to the correct speed, use the speed
command in asynchronous line configuration mode to set the speed on
the router line. Set the value to the highest speed in common between
the modem and the router port. If for some reason you cannot use flow
control, limit the line speed to 9600 bps. Faster speeds are likely to
result in lost data.
• Use the show line 1 command again, and confirm that the line speed
is set to the desired value.
• When you are certain that the router line is configured for the desired
speed, initiate a reverse Telnet session to the modem on that line.
• Use a modem command string that includes the lock DTE speed
command for your modem. See your modem documentation for exact
configuration command syntax.
The lock DTE speed command, which might also be referred to as
port rate adjust or buffered mode, is often related to the way in which
the modem handles error correction. This command varies widely
between modems.
Locking the modem speed ensures that the modem always
communicates with the Cisco router at the speed configured on the
Cisco serial port. If this command is not used, the modem will revert
to the speed of the data link (the telephone line) instead of
communicating at the speed configured on the router.
Problem Solution
Modem control is not • Use the show line 1 privileged EXEC command on the router. The
enabled on the router. output for the port should show inout or RIisCD in the Modem
column, which indicates that modem control is enabled on the line of
the router.
• If necessary, configure modem control by using the modem inout
command in asynchronous line configuration mode.
PPP authentication fails. • Use the debug ppp chap privileged EXEC command to see whether
PPP authentication was successful. Check the output for the phrase
Passed authentication with remote. If you see this output,
authentication was successful.
• If PPP authentication was not successful, verify the username and
password configured on the router. The username and password you
enter must be identical to those configured on the router. Usernames
and passwords are case-sensitive.
Local router not waiting • Enter the show dialer privileged EXEC command to see the
long enough to connect. configured dialer timeout. A timeout value of less than 120 seconds
will not be long enough.
• Configure the local router to wait longer for the connection by
entering the dialer wait-for-carrier-time command in the serial
interface configuration mode. Make sure that you specify at least a
120-second timeout.
Chat script problem. • Enter the debug chat privileged EXEC command. If you see the
output “Success” at the end of the chat script, the chat script
completed successfully.
• Make the timeout in the chat script longer at the point where it fails.
• If the problem persists, verify that the command response to each chat
script step is correct. Open a reverse Telnet session to the modem and
step through the chat script.
• Fix any inconsistencies you find in the chat script.
Problem Solution
Autoselect is enabled on Try to access privileged EXEC mode by entering a carriage return.
the line
Line is configured with the • Use the show line 1 privileged EXEC command to view the status of
no exec command. the appropriate line. Check the Capabilities field for the phrase says
EXEC suppressed. If this is the case, the no exec line configuration
command is enabled.
• Configure the exec command in asynchronous line configuration
mode to allow EXEC sessions to be initiated.
Flow control is not • Enter the show line 0 privileged EXEC command, and look for the
enabled, is enabled only on following in the Capabilities field:
one device (either DTE or Capabilities: Hardware Flowcontrol In, Hardware Flowcontrol
DCE), or is misconfigured. Out...
Problem Solution
Modem speed setting is not • Enter the show line 1 privileged EXEC command on the router. The
locked. output for the serial port should indicate the currently configured
transmit (Tx) and receive (Rx) speeds.
• If the line is not configured to the correct speed, use the speed
command in asynchronous line configuration mode to set the speed
on the router line. Set the value to the highest speed in common
between the modem and the router port. If for some reason you cannot
use flow control, limit the line speed to 9600 bps. Faster speeds are
likely to result in lost data.
• Use the show line 1 command again, and confirm that the line speed
is set to the desired value.
• When you are certain that the router line is configured for the desired
speed, initiate a reverse Telnet session to the modem on that line.
• Use a modem command string that includes the lock DTE speed
command for your modem. See your modem documentation for the
exact configuration command syntax.
The lock DTE speed command, which might also be referred to as
port rate adjust or buffered mode, is often related to the way in which
the modem handles error correction. This command varies widely
between modems.
Locking the modem speed ensures that the modem always
communicates with the Cisco router at the speed configured on the
Cisco serial port. If this command is not used, the modem will revert
to the speed of the data link (the telephone line) instead of
communicating at the speed configured on the router.
Problem Solution
Modem speed setting is not • Enter the show line 1 privileged EXEC command on the router. The
locked. output for the serial port should indicate the currently configured
transmit (Tx) and receive (Rx) speeds.
• If the line is not configured to the correct speed, use the speed
command in asynchronous line configuration mode to set the speed
on the router line. Set the value to the highest speed in common
between the modem and the router port. If for some reason you cannot
use flow control, limit the line speed to 9600 bps. Faster speeds are
likely to result in lost data.
• Use the show line 1 command again, and confirm that the line speed
is set to the desired value.
• When you are certain that the router line is configured for the desired
speed, initiate a reverse Telnet session to the modem on that line.
• Use a modem command string that includes the lock DTE speed
command for your modem. See your modem documentation for the
exact configuration command syntax.
The lock DTE speed command, which might also be referred to as
port rate adjust or buffered mode, is often related to the way in which
the modem handles error correction. This command varies widely
between modems.
Locking the modem speed ensures that the modem always
communicates with the Cisco router at the speed configured on the
Cisco serial port. If this command is not used, the modem will revert
to the speed of the data link (the telephone line) instead of
communicating at the speed configured on the router.
Problems Solutions
Incorrect cabling. Check the cabling between the modem and the router. Refer to the
Cisco 805 Router Hardware Installation Guide for information on how to
select the serial cable and how to connect the modem.
Modem control is not • Enter the show line 1 privileged EXEC command on the router. The
enabled on the router. output for the serial port should show inout or RIisCD in the Modem
column, which indicates that modem control is enabled on the router
line.
• Configure modem control by entering either the modem inout or the
modem ri-is-cd command in the asynchronous line configuration
mode.
Modem configured for • The modem should be reconfigured to have DCD high only on CD,
DCD is always high. which is usually configured with the &C1 modem command string.
Check your modem documentation for the exact syntax for your
modem.
• You might have to configure the router line to which the modem is
connected with the no exec command in asynchronous line
configuration mode. Clear the line with the clear line privileged
EXEC command, initiate a reverse Telnet session with the modem,
and reconfigure the modem so that DCD is high only on CD.
• End the Telnet session by entering disconnect and reconfigure the
router line with the exec line configuration command.
Problem Solution
Modem speed setting is not • Enter the show line 1 privileged EXEC command on the router. The
locked. output for the serial port should indicate the currently configured
transmit (Tx) and receive (Rx) speeds.
• If the line is not configured to the correct speed, use the speed
command in asynchronous line configuration mode to set the speed
on the router line. Set the value to the highest speed in common
between the modem and the router port. If for some reason you cannot
use flow control, limit the line speed to 9600 bps. Faster speeds are
likely to result in lost data.
• Use the show line 1 command again, and confirm that the line speed
is set to the desired value.
• When you are certain that the router line is configured for the desired
speed, initiate a reverse Telnet session to the modem on that line.
• Use a modem command string that includes the lock DTE speed
command for your modem. See your modem documentation for the
exact configuration command syntax.
The lock DTE speed command, which might also be referred to as
port rate adjust or buffered mode, is often related to the way in which
the modem handles error correction. This command varies widely
between modems.
Locking the modem speed ensures that the modem always
communicates with the Cisco router at the speed configured on the
Cisco serial port. If this command is not used, the modem will revert
to the speed of the data link (the telephone line) instead of
communicating at the speed configured on the router.
Problem Solution
Hardware flow control not • Enter the show line 0 privileged EXEC command, and look for the
configured on local or following in the Capabilities field:
remote modem or router Capabilities: Hardware Flowcontrol In, Hardware Flowcontrol
Out...
Problem Solution
IP routing not enabled on Make sure that IP routing is enabled on the local and remote routers.
local or remote router
No default gateway • Enter the show slip privileged EXEC command. Make sure that the
specified on PC specified IP address is the same as the default gateway specification
on the PC.
• Check the specified default gateway address on the PC. If the IP
address is not correct, specify the correct address. For instructions on
verifying and changing the default gateway address on the
workstation, refer to the vendor documentation.
Hardware flow control not • Enter the show line 0 privileged EXEC command, and look for the
configured on local or following in the Capabilities field:
remote modem or router Capabilities: Hardware Flowcontrol In, Hardware Flowcontrol
Out...
Problem Solution
Static routes not • Use the show ip route privileged EXEC command to check whether
configured there is a static route to the remote network in the routing table.
• If there is no static route to the remote network, configure one, using
the ip route command. The static route should point to the remote
network.
Domain Name System • Check whether the workstation and router both have DNS
(DNS) server not specified information specified. On the router, use the show running-config
on router or workstation privileged EXEC command to see if DNS is configured. For
information on verifying the workstation configuration, refer to the
vendor documentation.
• If the router and workstation are not configured to use DNS, use the
ip domain-lookup, ip domain-name, and ip name-server
commands to configure the router.
• Configure a DNS server address in the TCP/IP software on the PC.
For more information, refer to the vendor documentation.
Problem Solution
Modem is not sensing Enter the hangup DTR modem command string. This command tells
DTR. the modem to drop carrier when the DTR signal is no longer being
received. For the exact syntax of this command, see the your modem
documentation.
Problem Solution
Modem control is not • Use the show line 1 privileged EXEC command on the router. The
enabled on the router. output should show inout or RIisCD in the Modem column, which
indicates that modem control is enabled on the line of the router.
• If necessary, configure modem control by using the modem inout
command in asynchronous line configuration mode.
Problem Solution
Dialer timeout is too short • Use the show running-config privileged EXEC command to view the
router configuration. Check the value configured with the dialer
idle-timeout command.
• Increase the timeout value, using the dialer idle-timeout seconds
command. The default is 120 seconds.
Dialer lists are too • Use the show running-config privileged EXEC command to view the
restrictive router configuration. Check the access lists, if any, referenced by
dialer list commands.
• Make sure that the access lists describe all the traffic that should keep
the link active. Reconfigure the access lists to include additional
traffic if necessary.
Table 9-22 Link Does Not Deactivate or Stays Activated Too Long
Problem Solution
Dialer lists not restrictive • Use the show running-config privileged EXEC command to view the
enough router configuration. Check the access lists, if any, referenced by
dialer list commands.
• Make sure that the access lists do not describe traffic that should not
keep the link active. Reconfigure the access lists if necessary.
Modems misconfigured Make sure that the local and remote modems are properly configured. In
particular, both modems should be configured to disconnect on loss of
DTR (Hangup DTR). For the exact syntax of this command, see your
modem documentation.
Problem Solution
Error correction is not Make certain the modem is configured for error correction. For the exact
configured on the modem. syntax of the command, see your modem documentation.
Flow control is not • Enter the show line 0 privileged EXEC command, and look for the
enabled, is enabled only on following in the Capabilities field:
one device (either DTE or Capabilities: Hardware Flowcontrol In, Hardware Flowcontrol
DCE), or is misconfigured. Out...
Problem Solution
Cabling, hardware, or carrier Perform these steps on the local and remote routers.
problem
• Use the show interfaces serial 0 command to see if the interface
and line protocol are up.
• If the interface and line protocol are down, refer to the Cisco 805
Router Hardware Installation Guide to confirm that you are using
the correct serial cable to connect the CSU/DSU and that you
connected the CSU/DSU correctly. Make sure that cables are
securely attached.
• If the cable is correct, try moving it to a different port. If that port
works, then the first port is defective. Replace the router.
• If the cable does not work on the second port, replace the cable. If
it still does not work, there might be a problem with the DCE.
Contact your carrier about the problem.
Problem Solution
Local management interface • Use the show interfaces serial 0 command to check the state of
(LMI) type mismatch the interface.
• If the output shows the interface is up but the line protocol is down,
enter the show frame-relay lmi privileged EXEC command to see
which LMI type is configured on the Frame Relay interface.
• Make sure that the LMI type is the same for all devices in the path
from source to destination. Enter the frame-relay lmi-type {ansi
| cisco | q933a} command in serial interface configuration mode to
change the LMI type on the router.
Keepalives not being sent • Enter the show interfaces serial 0 command to find out if
keepalives are configured. If you see a line that says “keepalives
not set,” keepalives are not configured.
• Use the keepalive seconds command in serial interface
configuration mode to configure keepalives. The default value for
this command is 10 seconds.
Encapsulation mismatch • When connecting Cisco devices with non-Cisco devices, you must
use Internet Engineering Task Force (IETF) encapsulation on both
devices. Check the encapsulation type on the Cisco device by
using the show frame-relay map privileged EXEC command.
• If the Cisco device is not using IETF encapsulation, use the
encapsulation frame-relay ietf command in serial interface
configuration mode to configure IETF encapsulation on the
Cisco Frame Relay interface. For information on viewing or
changing the configuration of the non-Cisco device, refer to the
vendor documentation.
Problem Solution
Data-link connection • Enter the show frame-relay pvc privileged EXEC command to
identifier (DLCI) inactive or view the status of the interface PVC.
deleted
• If the output shows that the PVC is inactive or deleted, there is a
problem along the path to the remote router. Check the remote
router or contact your carrier to check the status of the PVC.
DLCI assigned to wrong • Use the show frame-relay pvc privileged EXEC command to
subinterface check the assigned DLCIs. Make sure that the correct DLCIs are
assigned to the correct subinterface.
• If the DLCIs appear to be correct, shut down the main interface by
entering the shutdown command in serial interface configuration
mode, then bring the interface back up entering the no shutdown
command.
Problem Solution
Encapsulation mismatch • When connecting Cisco devices to non-Cisco devices, you must
use IETF encapsulation on both devices. Check the encapsulation
type on the Cisco device by using the show frame-relay map
privileged EXEC command.
• If the Cisco device is not using IETF encapsulation, use the
encapsulation frame-relay ietf command in serial interface
configuration mode to configure IETF encapsulation on the
Cisco Frame Relay interface. For information on viewing or
changing the configuration of the non-Cisco device, refer to the
vendor documentation.
Problem Solution
DLCI inactive or deleted • Enter the show frame-relay pvc privileged EXEC command to
view the status of the interface PVC.
• If the output shows that the PVC is inactive or deleted, there is a
problem along the path to the remote router. Check the remote
router, or contact your carrier to check the status of the PVC.
DLCI assigned to wrong • Use the show frame-relay pvc privileged EXEC command to
subinterface check the assigned DLCIs. Make sure that the correct DLCIs are
assigned to the correct subinterface.
• If the DLCIs appear to be correct, shut down the main interface by
entering the shutdown command in serial interface configuration
mode. Then bring the interface back up by entering the no
shutdown command.
Misconfigured access list • Enter the show access-list privileged EXEC command to see
whether there are access lists configured on the router.
• If access lists are configured, test connectivity by disabling access
lists by entering the no access-group command in global
configuration mode. Check to see whether connectivity is
restored.
• If connections work, reenable access lists one at a time, checking
connections after enabling each access list.
• If enabling an access list blocks connections, make sure that the
access list does not deny necessary traffic. Make sure to configure
explicit permit statements for any traffic you want to pass.
• Continue testing access lists until all access lists are restored and
connections still work.
Problem Solution
frame-relay map command • Enter the show frame-relay map privileged EXEC command to
missing see whether an address map is configured for the DLCI.
• If you do not see an address map for the DLCI, enter the clear
frame-relay-inarp privileged EXEC command. Then enter the
show frame-relay map command again to see if there is now a
map to DLCI.
• If there is no map to the DLCI, add a static address map by
entering the frame-relay map command in serial interface
configuration mode.1 For complete information on configuring
Frame Relay address maps, refer to the Cisco IOS Wide-Area
Networking Configuration Guide publication.
• Make sure that the DLCIs and next-hop addresses specified in
frame-relay map commands are correct. The specified protocol
address should be in the same network as your local Frame Relay
interface.
No broadcast keyword in • Enter the show running-config privileged EXEC command on
frame-relay map statements the local and remote routers to view the router configuration.
Check frame-relay map command entries to see if the broadcast
keyword is specified.
• If the keyword is not specified, add the broadcast keyword to all
frame-relay map commands. By default, the broadcast keyword
is added to dynamic maps learned via Inverse ARP.
1. You can eliminate the need for static Frame Relay address maps by using Inverse Address Resolution Protocol (ARP) instead.
Use the frame-relay interface-dlci dlci broadcast interface configuration command to configure an interface to use Inverse
ARP. For more information about the use of this command, refer to the Cisco IOS Wide-Area Networking Configuration
Guide and Wide-Area Networking Command Reference.
Problem Solution
Split horizon problem In a partially meshed Frame Relay environment, you must configure
subinterfaces to avoid problems with split horizon. For detailed
information on configuring subinterfaces, refer to the Wide-Area
Networking Configuration Guide and Wide-Area Networking
Command Reference.
No default gateway on • From a local workstation or server, try to ping the remote
workstation workstation or server. Make several attempts to ping the remote
device if the first ping is unsuccessful.
• If all your attempts fail, check to see whether the local workstation
or server can ping the Frame Relay interface of the local router.
• If you are unable to ping the Frame Relay interface of the local
router, check the local workstation or server to see whether it is
configured with a default gateway specification.
• If there is no default gateway specified, configure the device with
a default gateway. The default gateway should be the address of the
LAN interface of the local router. For information on viewing or
changing the default gateway of the workstation or server, refer to
the vendor documentation.
X.25 Problems
This section describes how to troubleshoot the following X.25 symptoms:
• No Connections over X.25 Link
• Excess Serial Errors on X.25 Link
Problem Solution
Incorrect cabling or bad • Check all cabling and hardware for damage or wear. Replace cabling
router hardware or hardware as required. For more information on the Cisco 805
router and serial cables, refer to the Cisco 805 Router Hardware
Installation Guide.
• Enter the show interfaces serial 0 privileged EXEC command to
determine the status of the interface.
• If the interface is down, see the “Troubleshooting Serial Line
Problems” section on page 9-16. If the interface is up but the line
protocol is down, check the Link Access Procedure, Balanced
(LAPB) state in the output of the show interfaces serial 0 command.
• If the LAPB state is not CONNECT, use the debug lapb privileged
EXEC command (or attach a serial analyzer) to look for set
asynchronous balance mode requests (SABMs) being sent, and for
UA packets being sent in reply to SABMs. If UAs are not being sent,
one of the other possible problems described in this table is the likely
cause.
• If the show interfaces serial 0 command indicates that the interface
and line protocol are up but no connections can be made, there is
probably a router or switch misconfiguration. Refer to the other
possible problems outlined in this table.
Link is down Enter the show interfaces serial 0 privileged EXEC command to
determine whether the link is down. If the link is down, see the
“Troubleshooting Serial Line Problems” section on page 9-16.
Problem Solution
Misconfigured protocol • Enable the debug lapb privileged EXEC command and look for set
parameters asynchronous balance mode requests (SABMs) being sent. If no
SABMs are being sent, disable the debug lapb command and enable
the debug x25 events privileged EXEC command.
• Look for RESTART messages (for PVCs) or CLEAR REQUESTS with
non-zero cause codes (for SVCs).
• To interpret X.25 cause and diagnostic codes provided in the debug
x25 events output, refer to the Debug Command Reference document.
• Verify that all critical LAPB parameters (modulo, T1, N1, N2, and k)
and the critical X.25 parameters (modulo, X.121 addresses, SVC
ranges, PVC definitions, and default window and packet sizes) match
the parameters required by the X.25 service provider.
Misconfigured x25 map • Use the show running-config privileged EXEC command to view the
command router configuration. Look for x25 map command entries under the
serial interface.
• Make sure that x25 map commands specify the correct address
mappings.
• If dynamic routing is being used in the network, verify that the
broadcast keyword is included in the x25 map command.
• Make sure that all router X.25 configuration options match the
settings of attached switches. Reconfigure the router or the switch as
necessary.
• Enable the debug x25 events privileged EXEC command and look
for RESTART messages (for PVCs) or CLEAR REQUESTS with non-zero
cause codes (for SVCs). To interpret X.25 cause and diagnostic codes
provided in the debug x25 events output, refer to the Debug
Command Reference document.
Note If any of these fields is increasing and represents more than 0.5 percent of the
number of IFRAMEs, there is likely a problem somewhere in the X.25 network.
There should always be at least one SABM. However, if there are more than 10,
the packet switch probably is not responding.
Table 9-28 outlines causes of this problem and describes possible solutions.
Problem Solution
Incorrect cabling or bad • Check all cabling and hardware for damage or wear. Replace cabling
router hardware or hardware as required. For more information on the Cisco 805
router and serial cables, refer to the Cisco 805 Router Hardware
Installation Guide.
• Enter the show interfaces serial 0 privileged EXEC command to
determine the status of the interface.
• If the interface is down, see the “Troubleshooting Serial Line
Problems” section on page 9-16. If the interface is up but the line
protocol is down, check the LAPB state in the output of the show
interfaces serial 0 command.
• If the LAPB state is not CONNECT, use the debug lapb privileged
EXEC command (or attach a serial analyzer) to look for SABMs
being sent, and for UA packets being sent in reply to SABMs. If UAs
are not being sent, one of the other possible problems described in
this table is the likely cause.
• If the show interfaces serial 0 command indicates that the interface
and line protocol are up but no connections can be made, there is
probably a router or switch misconfiguration. Refer to the other
possible problems outlined in this table.
Note These procedures can be done only when you are connected to the router through
the console port. These procedures cannot be performed through a Telnet session.
Note See the “Hot Tips” section on Cisco Connection Online (CCO) for additional
information on replacing enable secret passwords.
Step 4 Record the setting of the configuration register. It is usually 0x2100 or 0x100.
Note To enable break, enter the config-register 0x01 command while in privileged
EXEC mode.
Step 1 If break is enabled, go to Step 2. If break is disabled, turn the router off ( O ), wait
5 seconds, and turn it on ( | ) again. Within 60 seconds, press the Break key. The
terminal displays the ROM monitor prompt. Go to Step 3.
Note Some terminal keyboards have a key labeled Break. If your keyboard does
not have a Break key, refer to the documentation that came with the
terminal for instructions on how to send a break.
The router cycles its power, and the configuration register is set to 0x142. The
router uses the boot ROM system image, indicated by the system configuration
dialog:
--- System Configuration Dialog ---
Step 5 Enter no in response to the prompts until the following message is displayed:
Press RETURN to get started!
Step 7 Enter the enable command to enter enable mode. Configuration changes can be
made only in enable mode:
Router> enable
Step 8 Enter the show startup-config command to display an enable password in the
configuration file:
Router# show startup-config
If you are recovering an enable password, skip the following “Resetting the
Password and Saving Your Changes” section on page 9-58, and complete the
password recovery process by performing the steps in the “Resetting the
Configuration Register Value” section on page 9-58.
If you are recovering an enable secret password, it is not displayed in the
show startup-config command output. Complete the password-recovery process
by performing the steps in the following “Resetting the Password and Saving Your
Changes” section on page 9-58.
Step 2 Enter the enable secret command to reset the enable secret password in the
router:
Router(config)# enable secret password
Step 2 Enter the configure register command and the original configuration register
value that you recorded.
Router(config)# config-reg value
Note To return to the configuration being used before you recovered the lost
enable password, do not save the configuration changes before rebooting
the router.
Understanding how to use Cisco IOS software saves time when you are
configuring your router. If you need a refresher, take a few minutes to read this
chapter. If you are already familiar with Cisco IOS software, see Chapter 7,
“Router Feature Configuration,” and Chapter 8, “Advanced Router
Configuration.”
This chapter describes what you need to know before you begin configuring your
Cisco 800 series routers with Cisco IOS software (the software that runs your
router).
This chapter contains the following sections:
• Configuring the Router from a PC, page A-2
• Understanding Command Modes, page A-3
• Getting Help, page A-6
• Enable Secret and Enable Passwords, page A-7
• Entering Global Configuration Mode, page A-8
• Using Commands, page A-9
• Saving Configuration Changes, page A-10
You can use the terminal emulation software to change settings for the type of
device that is connected to the PC, in this case a router. Configure the software to
the following standard VT-100 emulation settings so that your PC can
communicate with your router:
• 9600 baud
• 8 data bits
• No parity
• 1 stop bit
• No flow control
These settings should match the default settings of your router. To change the
router baud, data bits, parity, or stop bits settings, you must reconfigure
parameters in the ROM monitor. For more information, refer to Appendix B,
“ROM Monitor.” To change the router flow control setting, use the flowcontrol
line configuration command.
For information on how to enter global configuration mode so that you can
configure your router, see the “Entering Global Configuration Mode” section on
page A-8.
Exit/Entrance
Mode Access Method Prompt Method About this Mode
User EXEC Begin a session with Router> To exit router Use this mode to:
your router. session, enter the
• Change terminal
logout command.
settings.
• Perform basic tests.
• Display system
information.
Privileged Enter the enable Router# To exit to user Use this mode to:
EXEC command from user EXEC mode, enter
• Configure your
EXEC mode. the disable
router operating
command.
parameters.
To enter global
• Perform the
configuration
verification steps
mode, enter the
shown in this guide.
configure
command. • To prevent
unauthorized
changes to your
router
configuration,
access to this mode
should be protected
with a password as
described in
“Enable Secret and
Enable Passwords”
later in this chapter.
Exit/Entrance
Mode Access Method Prompt Method About this Mode
Global Enter the configure Router To exit to Use this mode to
configuration command from (config)# privileged EXEC configure parameters
privileged EXEC mode, enter the exit that apply to your router
mode. or end command, as a whole.
or press Ctrl-Z. Also, you can access the
To enter interface following modes, which
configuration are described later in
mode, enter the this table:
interface
• Interface
command.
configuration
• Router
configuration
• Line configuration
Interface Enter the interface Router To exit to global Use this mode to
configuration command (with a (config-if)# configuration configure parameters
specific interface, mode, enter the exit for the router Ethernet
such as interface command. and serial interfaces or
ethernet 0) from subinterfaces.
To exit to
global configuration
privileged EXEC
mode.
mode, enter the end
command, or press
Ctrl-Z.
To enter
subinterface
configuration
mode, specify a
subinterface with
the interface
command.
Exit/Entrance
Mode Access Method Prompt Method About this Mode
Router Enter your router Router To exit to global Use this mode to
configuration command followed (config- configuration configure an IP routing
router)#
by the appropriate mode, enter the exit protocol.
keyword, for example command.
router rip, from
To exit to
global configuration
privileged EXEC
mode.
mode, enter the end
command, or press
Ctrl-Z.
Line Specify the line Router To exit to global Use this mode to
configuration command with the (config- configuration configure parameters
line)#
desired keyword, for mode, enter the exit for the terminal line.
example, line 0, from command.
global configuration
To enter privileged
mode.
EXEC mode, enter
the end command,
or press Ctrl-Z.
Getting Help
You can use the question mark (?) and arrow keys to help you enter commands.
For a list of available commands at that command mode, enter a question mark:
router> ?
access-enableCreate a temporary access-list entry
access-profileApply user-profile to interface
clearReset functions
...
For a list of command variables, enter the show command followed by a space and
a question mark:
router> show ?
clock Display the system clock
dialerDialer parameters and statistics
exceptionexception information
...
To redisplay a command you previously entered, press the up-arrow key. You can
continue to press the up arrow key for more commands.
Step 1 After your router boots up, answer no when the following question displays:
Would you like to enter the initial configuration dialog [yes]: no
Step 3 If you have configured your router with an enable password, enter it when you are
prompted.
The enable password does not show on the screen when you enter it. This example
shows how to enter privileged EXEC mode:
Password: enable_password
router#
Enable mode is indicated by the # in the prompt. You can now make changes to
your router configuration.
Step 4 Enter the configure terminal command to enter global configuration mode,
indicated by (config)# in the prompt:
router# configure terminal
router (config)#
Using Commands
This section provides some tips about entering Cisco IOS commands at the
command-line interface (CLI).
Abbreviating Commands
You only have to enter enough characters for the router to recognize the command
as unique. This example shows how to enter the show version command:
router # sh v
Undoing Commands
If you want to disable a feature or undo a command you entered, you can enter the
keyword no before most commands; for example, no ip routing.
It might take a minute or two to save the configuration to NVRAM. After the
configuration has been saved, the following message appears:
Building configuration...
router #
Command Task
Step 1 router(config)# no partition flash-filesystem Remove all partitions on the specific Flash
file system. The reason for removing
partitions is to ensure that the entire Flash file
system is erased. The squeeze command can
be used in a Flash file memory with partitions
after the Flash file memory has been erased.
Step 2 router# erase filesystem Erase all of the files on the specified Flash
system.
Note The squeeze function is applicable only to the Cisco 831, Cisco 837,
Cisco SOHO 91, and Cisco SOHO 97 routers.
Summary
Now that you have reviewed some Cisco IOS software basics, you can begin to
configure your router. Remember the following:
• 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 are having
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.
• If you want to disable a feature, enter the keyword no before the command;
for example, no ip routing.
• Save your configuration changes to NVRAM so that they are not lost if there
is a system reload or power outage.
Where to Go Next
To configure your router, see Chapter 7, “Router Feature Configuration,” and
Chapter 8, “Advanced Router Configuration.”
This appendix describes the Cisco 820 series routers ROM monitor (also called
the bootstrap program). The ROM monitor firmware runs when the router is
powered up or reset. The firmware helps to initialize the processor hardware and
boot the operating system software. You can use the ROM monitor to perform
certain configuration tasks, such as recovering a lost password or downloading
software over the console port. If there is no Cisco IOS software image loaded on
the router, the ROM monitor runs the router.
This appendix contains the following sections:
• Entering the ROM Monitor, page B-2
• ROM Monitor Commands, page B-5
• Command Descriptions, page B-6
• Disaster Recovery with TFTP Download, page B-7
• Using the TFTP Download Command Without Writing the Image to Flash
Memory, page B-10
• Configuration Register, page B-11
• Console Download, page B-12
• Debug Commands, page B-14
• Disaster Recovery with Console Download of Cisco IOS Software,
page B-16
Command Task
Step 1 enable If an enable password is configured, enter the
enable command and the enable password to
enter privileged EXEC mode.
Step 2 configure terminal Enter global configuration mode.
Step 3 config-reg 0x0 Reset the configuration register.
Step 4 exit Exit global configuration mode.
Step 5 reload Reboot the router with the new configuration
register value. The router remains in ROM
monitor and does not boot the Cisco IOS
software.
As long as the configuration value is 0x0, you
must manually boot the operating system
from the console. See the boot command in
the “Command Descriptions” section on
page B-6.
After the router reboots, it is in ROM monitor
mode. The number in the prompt increments
with each new line.
Timesaver Break (system interrupt) is always enabled for 60 seconds after the router reboots,
regardless of whether it is set to on or off in the configuration register. During this
60-second window, you can break to the ROM monitor prompt by pressing the
Break key.
Step 1 Download the ROMMON image from CCO, and place it on your TFTP server.
Step 2 Connect the Ethernet cable to the same hub that the TFTP server is attached to.
Step 3 Place your Cisco router in ROMMON mode by sending the Telnet command
break during a router reboot sequence. Make sure that all the parameters are exact
and are in capital letters. The following prompt is displayed when the router is in
ROMMON mode:
rommon 1 >
Parameter Value
IP_ADDRESS= IP address of the router
IP_SUBNET_MASK= Router subnet mask
DEFAULT_GATEWAY= IP address of the router default
gateway
TFTP_SERVER= IP address of the TFTP server on which
the ROMMON image is located
TFTP_FILE= The path and file name of the
ROMMON image
Step 5 Verify parameter settings, using the set command. Correct any errors by
reentering the parameters and their values. For example:
rommon > set
TFTP_CHECKSUM=0
IP_SUBNET_MASK=255.255.255.0
DEFAULT_GATEWAY=1.6.0.1
TFTP_SERVER=223.255.254.254
IP_ADDRESS=1.6.97.20
TFTP_FILE=/auto/tftpload/ROMMON/C820_RM_ALT.srec.122-1r.XE2
Note You might be prompted to reset the router in ROMMON mode by entering
the reset command. If you receive this prompt, reset the router before you
perform Step 1 througth Step 5 again.
rommon >tftpdnld -u
IP_ADDRESS:1.6.97.20
IP_SUBNET_MASK:255.255.255.0
DEFAULT_GATEWAY:1.6.0.1
TFTP_SERVER:223.255.254.254
TFTP_FILE:/auto/tftpload/ROMMON/C820_RM_ALT.srec.122-1r.XE2
WARNING: alternate copy of rommon exists, filename:C820_RM_ALT.srec
all existing data in the alternate copy of rommon will be lost.
Do you wish to continue? y/n: [n]:
Step 7 Enter y to start the download. Successive exclamation points (!!!!!!) indicate that
the download is occurring. The router reboots when the download is complete.
Step 1 Download the ROMMON image from CCO, and place it on your TFTP server.
Step 2 In EXEC mode, save the current configuration, using the copy running-config
startup-config command.
Step 3 Enter the copy tftp rommon command, and answer the prompts. Replace the
variables shown in the following example with the correct values for your router:
820-2#copy tftp:rommon:
Address or name of remote host []? IP_address_of_remote_host
Source filename []? rommon_image_source_file_name
Destination filename [rommon]? rommon_image_destination_file_name
Commands are case sensitive. You can halt any command by pressing the Break
key on a terminal. If you are using a PC, most terminal emulation programs halt
a command when you press the Ctrl and the Break keys at the same time. If you
are using another type of terminal emulator or terminal emulation software, refer
to the documentation for that product for information on how to send a Break
command.
Command Descriptions
Table B-1 describes the most commonly used ROM monitor commands.
Command Description
help or ? Displays a summary of all available ROM monitor commands.
-? Displays information about command syntax; for example:
rommon 16 > dis -?
usage : dis [addr] [length]
The output for this command is slightly different for the xmodem download
command:
rommon 11 > xmodem -?
xmodem: illegal option -- ?
usage: xmodem [-cyrxu] <destination filename>
-c CRC-16
-y ymodem-batch protocol
-r copy image to dram for launch
-x do not launch on download completion
-u upgrade ROMMON, System will reboot after upgrade
Command Description
reset or i Resets and initializes the router, similar to a power up.
dev Lists boot device identifications on the router; for example:
rommon 10> dev
Devices in device table:
id name
flash: flash
dir device: Lists the files on the named device; flash, for example:
rommon 4 > dir flash:
File size Checksum File name
2835276 bytes (0x2b434c) 0x2073 c806-oy6-mz
boot commands For more information about the ROM monitor boot commands, refer to the
Cisco IOS Configuration Guide and the Cisco IOS Command Reference.
b Boots the first image in Flash memory.
b flash:[filename] Attempts to boot the image directly from the first partition of Flash memory. If
you do not enter a filename, this command will boot this first image in Flash.
Note The commands described in this section are case sensitive and must be entered
exactly as shown.
Required Variables
These variables must be set with these commands before using the tftpdnld
command.
Variable Command
IP address of the router. IP_ADDRESS=ip_address
Subnet mask of the router IP_SUBNET_MASK=ip_address
IP address of the default gateway of the DEFAULT_GATEWAY=ip_address
router.
IP address of the TFTP server from TFTP_SERVER=ip_address
which the software will be
downloaded.
The name of the file that will be TFTP_FILE=filename
downloaded to the router.
Optional Variables
The following variables should be set with these commands before using the
tftpdnld command.
Variable Command
Configures how the router displays file TFTP_VERBOSE= setting
download progress.
0—No progress is displayed.
1—Exclamation points (!!!) are
displayed to indicate file download
progress. This is the default setting.
2—Detailed progress is displayed
during the file download process; for
example:
• Initializing interface.
• Interface link state up.
• ARPing for 1.4.0.1
• ARP reply for 1.4.0.1 received.
MAC address 00:00:0c:07:ac:01
Number of times the router attempts TFTP_RETRY_COUNT=
ARP and TFTP download. The default retry_times
is 7.
Amount of time, in seconds, before the TFTP_TIMEOUT= time
download process times out. The
default is 7,200 seconds
(120 minutes).
Whether or not the router performs a TFTP_CHECKSUM=setting
checksum test on the downloaded
image:
1—Checksum test is performed.
0—No checksum test is performed.
Step 1 Use the appropriate commands to enter all the required variables and any optional
variables described earlier in this section.
Step 2 Enter the tftpdnld command as follows:
rommon 1 > tftpdnld [-r]
Note The -r variable is optional. Entering this variable downloads and boots the
new software but does not save the software to Flash memory. You can
then use the image that is in Flash memory the next time you enter the
reload command.
Step 3 If you are sure that you want to continue, enter y in response to the question in the
output:
Do you wish to continue? y/n: [n]:y
Configuration Register
The virtual configuration register is in nonvolatile RAM (NVRAM) and has the
same functionality as other Cisco routers. You can view or modify the virtual
configuration register from either the ROM monitor or the operating system
software. Within ROM monitor, you can change the configuration register by
entering the register value in hexadecimal format, or by allowing the ROM
monitor to prompt you for the setting of each bit.
You must reset or power cycle for new config to take effect
rommon 2 >
Configuration Summary
enabled are:
console baud: 9600
Configuration Summary
enabled are:
diagnostic mode
console baud: 9600
boot: the ROM Monitor
You must reset or power cycle for new config to take effect
Console Download
You can use console download, a ROM monitor function, to download over the
router console port either a software image or a configuration file. Make sure that
the Cisco IOS image is in the same PC where you are to perform this function.
After download, the file is either saved to the mini-Flash memory module or to
main memory for execution (image files only).
Use console download when you do not have access to a TFTP server.
Note If you want to download a software image or a configuration file to the router over
the console port, you must use the ROM monitor command.
Note If you are using a PC to download a Cisco IOS image over the router console port
at 115,200 bps, ensure that the PC serial port is using a 16550 universal
asynchronous transmitter/receiver (UART). If the PC serial port is not using a
16550 UART, we recommend using a speed of 38,400 or less when downloading
a Cisco IOS image over the console port.
Command Description
The following are the syntax and descriptions for the xmodem console download
command:
xmodem [-cyrx] destination_file_name
Step 1 Move the image file to the local drive where the Xmodem will execute.
Step 2 Enter the xmodem command.
Error Reporting
Because the ROM monitor console download uses the console to perform the data
transfer, error messages are displayed on the console only when the data transfer
is terminated.
If an error does occur during a data transfer, the transfer is terminated, and an
error message is displayed. If you have changed the baud rate from the default
rate, the error message is followed by a message telling you to restore the terminal
to the baud rate specified in the configuration register.
Debug Commands
Most ROM monitor debugging commands are functional only when the Cisco IOS
software has crashed or is halted. If you enter a debugging command and
Cisco IOS crash information is not available, you see the following error message:
"xxx: kernel context state is invalid, cannot proceed."
Note If you want to download a software image or a configuration file to the router over
the console port, you must use the rom monitor command.
Note If you are using a PC to download a Cisco IOS image over the router console port
at 115,200 bps, ensure that the PC serial port is using a 16550 UART. If the PC
serial port is not using a 16550 UART, we recommend using a speed of 38,400 or
less when downloading a Cisco IOS image over the console port.
Command Description
Following are the syntax and descriptions for the xmodem console download
command:
xmodem [-cyrx] destination_file_name
Error Reporting
Because the ROM monitor console download uses the console to perform the data
transfer, error messages are displayed on the console only when the data transfer
is terminated.
If an error does occur during a data transfer, the transfer is terminated, and an
error message is displayed. If you have changed the baud rate from the default
rate, the error message is followed by a message telling you to restore the terminal
to the baud rate specified in the configuration register.
Debug Commands
Most ROM monitor debugging commands are functional only when the Cisco IOS
software has crashed or is halted. If you enter a debugging command and
Cisco IOS crash information is not available, you see the following error message:
“xxx:kernel context state is invalid, cannot proceed.”
You must reset or power cycle for new config to take effect
rommon 2 >boot
The router will boot the Cisco IOS image in Flash memory. The configuration
register will change to 0x2101 the next time the router is reset or power cycled.
Table C-1 lists currently assigned Transmission Control Protocol (TCP) port
numbers. To the extent possible, the User Datagram Protocol (UDP) uses the same
numbers.
Table C-1 Currently Assigned TCP and UDP Port Numbers (continued)
Table C-1 Currently Assigned TCP and UDP Port Numbers (continued)
This appendix describes ISDN lines and switches, the features available, and how
to order your ISDN line.
The term provisioning refers to the features that you can order for the ISDN line.
If you are in North America and do not use an NI1 switch, Cisco strongly
recommends familiarizing yourself with provisioning terminology related to
other switch types so that communication with your telephone service provider
goes more smoothly.
If you have any problems with your ISDN NI1 provisioning, visit the Cisco ISDN
website at http://www.cisco.com/isdn.
Note If you do not need voice capability on your ISDN line, Cisco recommends
provisioning your ISDN line for only data applications.
Feature Description
Caller ID calling party identification Identifies the remote system that
originated the call.
Subaddressing Provides locally addressed terminals
within a specific ISDN access area.
Feature Description
Speech/3.1-kHz audio-bearer Cisco 803 and Cisco 804 routers support
capability voice applications.
Multiple subscriber numbers (MSN) Supports multiple directory numbers on
the same ISDN line. Each piece of
terminal equipment is assigned its own
directory number.
Call holding and retrieving A call in progress can be put on hold and
then retrieved.
Call waiting During a voice call, the call-waiting tone
is generated when a second voice call is
received.
Call bumping When two data calls are in progress and
additional call offering (ACO) is
provisioned, the router either ignores a
voice call or disconnects a data call to
accept the voice call. (Also referred to as
voice priority.)
Call transferring Transfers an active call to another
telephone number.
Three-way call conferencing Adds a third party to an existing call.
Call forwarding Forwards an incoming call to a third
party.
Caller ID, calling party Identifies the billing number associated
identification with the line that originated the call.
Caller ID Displays telephone number of remote
system that originated the call on a device
connected to a telephone port.
The data and voice applications described in this section might be referred to by
different names, depending on the telephone service provider. The terms can
differ even within a country. Table D-3 lists the names and codes that could be
used by telephone service providers outside of North America.
Note Switches that comply with the NI1 standard provide the best
performance with the call-bumping feature. If you order this feature,
Cisco recommends using an NI1 switch.
• Lucent 5ESS custom switches can run in either custom mode or NI1 mode. In
custom mode, the switch can operate in either a point-to-point or a multipoint
configuration. Point-to-point configuration supports one piece of terminal
equipment on the BRI line and does not require service profile identifiers
(SPIDs). Multipoint configuration supports multiple pieces of terminal
equipment on the same BRI line and requires SPIDs.
Note When ordering a Lucent 5ESS ISDN line to support multiple voice
calls, provision the line for call appearances 1 and 2.
• Nortel DMS-100 custom switches support a custom mode used with older
terminal equipment.
International Switches
Cisco 800 series routers support most ISDN BRI lines outside North America,
which generally use one of the following switch types:
• EURO-ISDN
• 1TR6
• VN3
• TPH
• Nippon Telegraph and Telephone (NTT)
Note The Cisco 800 series routers support 1TR6 switches for data applications only.
The routers do not support 1TR6 switches for voice applications.
Note Cisco 803 and Cisco 804 routers require two SPIDs for the telephone ports to
operate simultaneously, so that you can have a data and a voice call at the same
time. If a line is assigned only one SPID, the analog telephone ports cannot
operate simultaneously.
If you are not using an NI1 switch, you must order your ISDN line configured as
described in the “Other Switches” section later in this appendix.
If you have any problems with your ISDN NI1 provisioning, contact Cisco ISDN
Support Services (U.S. only). To access this service or to obtain more
information, call (800) 553-NETS (6387) and select the Customer Service option,
or visit the Cisco ISDN web site at http://www.cisco.com/isdn.
Capability Package R
Package R provides circuit-switched data on both B channels (no voice
capabilities). Data capabilities include calling number identification. Cisco
recommends this NI1 capability package for Cisco 801 and Cisco 802 routers.
Capability Package S
Package S provides alternate voice and circuit-switched data with no additional
features. Cisco recommends this NI1 capability package for Cisco 803 and
Cisco 804 routers when you want a minimum feature set.
Other Switches
This section contains provisioning summaries for other switches. Each summary
is a list of codes used by the telephone service provider when installing and
configuring your line. When you order your ISDN line, photocopy the appropriate
summary for your ISDN switch type, and attach it to your order form, which will
ensure that your ISDN line is ordered correctly.
The term provisioning refers to the features that can be ordered and configured on
the ISDN BRI line before terminal equipment, such as the router, can use the
features.
Cisco recommends using the BRI switch provisions listed in the “Lucent 5ESS
Custom Provisioning” and “Nortel DMS-100 Custom Provisioning” sections in
this appendix to support voice priority on one BRI B channel.
Table D-4 provides a list of commonly used ISDN terms and their definitions that
you might find helpful when deciding how to provision your ISDN line and when
ordering your ISDN line.
Term Definition
CSD Circuit-switched data—Number of B channels that can be
simultaneously connected for circuit-switched data calls.
CSD CHL Circuit-switched data channel—B channels used for data calls.
CSD LIMIT Circuit-switched data limit—Number of data calls made
simultaneously.
CSV Circuit-switched voice—Number of B channels
simultaneously connected for voice calls.
CSV ACO Circuit-switched voice additional call offering—Indicates an
additional call when the B channel is being used.
CSV CHL Circuit-switched voice channel—B channels used for voice
calls.
CSV LIMIT Circuit-switched voice limit—Number of voice calls made
simultaneously.
CSV Circuit-switched voice notification busy limit—Number of
NBLIMIT additional voice calls allowed.
EKTS Key system option—Whether or not a key system is being
used. (In a key system, multiple telephone numbers are shared
across terminals.)
MAXB CHL Maximum B channels—Number of B channels used
simultaneously.
MTERM Maximum terminals—Number of terminals active on the BRI
line.
TERMTYP Terminal type—Terminal type used on the BRI line. Valid
types for NI1 switches are Type A and Type C.
Note Incoming voice priority is not available with Lucent 5ESS custom switches.
You can order the following additional features with the Lucent 5ESS custom
switch:
• Caller ID, calling party identification
• Call forwarding
• Call pickup
Step 1 Order a single 128-kbps ISDN BRI line for your router.
The ISDN BRI service provides two bearer channels (B channels) and one data
channel (D channel). B channel service operates at 64 kbps and carries user data.
D-channel service operates at 16 kbps and carries control and signaling
information, although it can support user data transmission.
Step 2 Order the data and voice features that you want.
If you are planning to use an NI1 switch, you can order a capability package
described in the “NI1 Capability Packages and National ISDN Ordering Codes”
section in this appendix. If you are planning to use a switch other than an NI1
switch, refer to the provisioning summary information described in either the
“Lucent 5ESS Custom Switch” and “Nortel DMS-100 Custom Provisioning”
sections in this appendix to select features.
Step 3 If you have Cisco 803 or Cisco 804 routers, order the additional call offering
option if desired.
With this feature, the router can handle voice calls while in use.
Step 4 Obtain and record the following information from your telephone service
provider:
a. ISDN switch type.
b. Service profile identifiers (SPIDs). SPIDs are numbers assigned only by
North American telephone service providers. SPIDS identify the ISDN B
channels. The SPID format is generally an ISDN telephone number with
NI1 Switch
The following table lists the router configuration requirements when using
Cisco 800 series routers with a Lucent 5E NI1 switch in a multipoint
configuration.
Point-to-Point Configuration
Table D-9 lists the router configuration requirements for using a Lucent 5ESS
custom switch in a point-to-point configuration.
Multipoint Configuration
Table D-10 lists the router configuration requirements for using Lucent 5ESS
custom switch in a multipoint configuration.
2. If the automatic detection of SPIDs is enabled, you do not need to specify the actual SPID number
provided by your telephone service provider; instead, you can specify any number or numerical
string, such as 0.
Note In this configuration, the router can use only one B channel.
1TR6 Switch
The 1TR6 lines can be configured for multiple subscriber numbers, usually
referred to as “extended addressing” in Germany. The line is usually assigned a
group of eight sequential directory numbers that can be used for the different
pieces of terminal equipment used on the BRI line. These numbers are also used
for allocation to the analog telephone port and for call routing.
This appendix describes ISDN BRI standard cause values that might be received
from the ISDN switch when using Cisco 800 series routers. These values are sent
from the ISDN switch to the router to indicate ISDN call status.
Although telephone service providers generally define cause messages with
decimal values, Cisco 800 series routers display the hexadecimal (or hex)
translation of the decimal value.
Cause values are standardized; however, each telephone service provider uses its
own version of the cause message wording. Therefore, the cause messages shown
in Table E-1 might not match the messages exactly as they appear on the terminal.
Table E-1 lists the ISDN BRI cause values, the hexadecimal translation, the cause
message, and a short definition of the cause message.
Table E-1 ISDN BRI Cause Values and Cause Messages (continued)
Table E-1 ISDN BRI Cause Values and Cause Messages (continued)
Table E-1 ISDN BRI Cause Values and Cause Messages (continued)
Table E-1 ISDN BRI Cause Values and Cause Messages (continued)
Table E-1 ISDN BRI Cause Values and Cause Messages (continued)
Table E-1 ISDN BRI Cause Values and Cause Messages (continued)
Table E-1 ISDN BRI Cause Values and Cause Messages (continued)
queues 1-22
C
troubleshooting commands 9-6 to 9-14
ATM adaptation layer call 1-19
See AAL caller ID devices 6-12
ATM interface caller ID on the Cisco 813 router 6-65
See ATM call forwarding for Net3 switch 6-48
ATM OAM F5 continuity check support, calling between telephone ports 6-53
configuring 8-44 call leg, defining a 1-19
audience, user xxii call transfer 6-57
authentication protocols call transferring 6-17
See PPP authentication protocols call waiting 6-15, D-2
CAPI
default settings 5-5
B
features 5-2
basic calls, making 6-13 overview 5-1
basic telephone service RVS-COM 5-2
See POTS dial peer supported applications 5-4
b flash command B-7 supported B channel protocols 5-3
boot commands B-7 supported D channel protocols 5-4
bootstrap program CAR
See ROM monitor configuring, configuration example 8-36
bridge, replacing 4-9 to 4-12 description 1-23
bridging caution, described xxiv
configuration example 7-15 CBWFQ 1-21
configuring 7-13 to 7-17 CD-ROM, documentation xxvii
broadcast intervals, RIP 1-8 Central RADIUS Server, configuring 4-61
broadcasts, UDP 3-24, 3-27 Challenge Handshake Authentication Protocol
See CHAP
CHAP
DHCP server
D
configuration example 7-31
data over voice bearer service 6-9 configuring 2-5, 3-11 to 3-18
DDR configuring routers as 7-26 to 7-31
configuring 2-5, 3-20 description 3-5
description 2-5, 2-14, 2-23 illustrated 7-27
DDR ISDN line activation 3-26, 3-27 DHCP server import, configuring 8-14
debug ATM commands 9-10 to 9-14 dial backup
debug atm errors command 9-11 configuration example 4-31 to 4-54
debug atm events command 9-12 configuring 4-24
debug atm packet command 9-13 to 9-14 configuring dial backup and remote
debug commands, ROM monitor B-14 to B-16, management 4-28, 4-48
B-18 dialer watch 4-26
debug message floating static routes 4-25
cause values 6-26 dialer interfaces 4-21, 7-6 to 7-12
CSM events 6-25 dial-on-demand routing for PPPoE client,
CSM states 6-23 configuring 8-53
activation 3-22
configuring 3-22
N
LFQ 1-22
line configuration mode A-6 NAT
Link Control Protocol configuration example 7-23
See LCP configuration scenario 4-23
lists, access network example 4-19, 4-23 to 4-24
IP traffic 3-30 overview 1-15 to 1-16
network access restrictions 3-31 See also Easy IP (Phase 1)
UDP broadcasts control 3-27 national ISDN-1 switches
local call forwarding 6-65, 6-66 See NI1 switches
loopback interface, configuring 7-7 to 7-9 NAT overload 3-13
low latency queuing NCP 1-9
See LFQ Net3 switch
requirements 6-47
supplementary telephone services 6-46
V WFQ
configuring 8-55
variable bit rate non-real time description 1-24
See vbr-nrt Windows NT, configuring 3-23
variables, command listing A-7
vbr-nrt
command 7-10 X
service class 7-10
xmodem command B-13
virtual configuration register B-11