
- •Warning and Disclaimer
- •Feedback Information
- •Trademark Acknowledgments
- •About the Author
- •About the Technical Reviewers
- •Dedication
- •Acknowledgments
- •Contents at a Glance
- •Contents
- •Icons Used in This Book
- •Command Syntax Conventions
- •Cisco’s Motivation: Certifying Partners
- •Format of the CCNA Exams
- •What’s on the CCNA Exams
- •ICND Exam Topics
- •Cross-Reference Between Exam Topics and Book Parts
- •CCNA Exam Topics
- •INTRO and ICND Course Outlines
- •Objectives and Methods
- •Book Features
- •How This Book Is Organized
- •Part I: LAN Switching
- •Part II: TCP/IP
- •Part III: Wide-Area Networks
- •Part IV: Network Security
- •Part V: Final Preparation
- •Part VI: Appendixes
- •How to Use These Books to Prepare for the CCNA Exam
- •For More Information
- •Part I: LAN Switching
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Brief Review of LAN Switching
- •The Forward-Versus-Filter Decision
- •How Switches Learn MAC Addresses
- •Forwarding Unknown Unicasts and Broadcasts
- •LAN Switch Logic Summary
- •Basic Switch Operation
- •Foundation Summary
- •Spanning Tree Protocol
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Spanning Tree Protocol
- •What IEEE 802.1d Spanning Tree Does
- •How Spanning Tree Works
- •Electing the Root and Discovering Root Ports and Designated Ports
- •Reacting to Changes in the Network
- •Spanning Tree Protocol Summary
- •Optional STP Features
- •EtherChannel
- •PortFast
- •Rapid Spanning Tree (IEEE 802.1w)
- •RSTP Link and Edge Types
- •RSTP Port States
- •RSTP Port Roles
- •RSTP Convergence
- •Edge-Type Behavior and PortFast
- •Link-Type Shared
- •Link-Type Point-to-Point
- •An Example of Speedy RSTP Convergence
- •Basic STP show Commands
- •Changing STP Port Costs and Bridge Priority
- •Foundation Summary
- •Foundation Summary
- •Virtual LANs and Trunking
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Review of Virtual LAN Concepts
- •Trunking with ISL and 802.1Q
- •ISL and 802.1Q Compared
- •VLAN Trunking Protocol (VTP)
- •How VTP Works
- •VTP Pruning
- •Foundation Summary
- •Part II: TCP/IP
- •IP Addressing and Subnetting
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •IP Addressing Review
- •IP Subnetting
- •Analyzing and Interpreting IP Addresses and Subnets
- •Math Operations Used to Answer Subnetting Questions
- •Converting IP Addresses from Decimal to Binary and Back Again
- •The Boolean AND Operation
- •How Many Hosts and How Many Subnets?
- •What Is the Subnet Number, and What Are the IP Addresses in the Subnet?
- •Finding the Subnet Number
- •Finding the Subnet Broadcast Address
- •Finding the Range of Valid IP Addresses in a Subnet
- •Finding the Answers Without Using Binary
- •Easier Math with Easy Masks
- •Which Subnet Masks Meet the Stated Design Requirements?
- •What Are the Other Subnet Numbers?
- •Foundation Summary
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Extended ping Command
- •Distance Vector Concepts
- •Distance Vector Loop-Avoidance Features
- •Route Poisoning
- •Split Horizon
- •Split Horizon with Poison Reverse
- •Hold-Down Timer
- •Triggered (Flash) Updates
- •RIP and IGRP
- •IGRP Metrics
- •Examination of RIP and IGRP debug and show Commands
- •Issues When Multiple Routes to the Same Subnet Exist
- •Administrative Distance
- •Foundation Summary
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Link-State Routing Protocol and OSPF Concepts
- •Steady-State Operation
- •Loop Avoidance
- •Scaling OSPF Through Hierarchical Design
- •OSPF Areas
- •Stub Areas
- •Summary: Comparing Link-State and OSPF to Distance Vector Protocols
- •Balanced Hybrid Routing Protocol and EIGRP Concepts
- •EIGRP Loop Avoidance
- •EIGRP Summary
- •Foundation Summary
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Route Summarization and Variable-Length Subnet Masks
- •Route Summarization Concepts
- •VLSM
- •Route Summarization Strategies
- •Sample “Best” Summary on Seville
- •Sample “Best” Summary on Yosemite
- •Classless Routing Protocols and Classless Routing
- •Classless and Classful Routing Protocols
- •Autosummarization
- •Classful and Classless Routing
- •Default Routes
- •Classless Routing
- •Foundation Summary
- •Advanced TCP/IP Topics
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Scaling the IP Address Space for the Internet
- •CIDR
- •Private Addressing
- •Network Address Translation
- •Static NAT
- •Dynamic NAT
- •Overloading NAT with Port Address Translation (PAT)
- •Translating Overlapping Addresses
- •Miscellaneous TCP/IP Topics
- •Internet Control Message Protocol (ICMP)
- •ICMP Echo Request and Echo Reply
- •Destination Unreachable ICMP Message
- •Time Exceeded ICMP Message
- •Redirect ICMP Message
- •Secondary IP Addressing
- •FTP and TFTP
- •TFTP
- •MTU and Fragmentation
- •Foundation Summary
- •Part III: Wide-Area Networks
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Review of WAN Basics
- •Physical Components of Point-to-Point Leased Lines
- •Data-Link Protocols for Point-to-Point Leased Lines
- •HDLC and PPP Compared
- •Looped Link Detection
- •Enhanced Error Detection
- •Authentication Over WAN Links
- •PAP and CHAP Authentication
- •Foundation Summary
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •ISDN Protocols and Design
- •Typical Uses of ISDN
- •ISDN Channels
- •ISDN Protocols
- •ISDN BRI Function Groups and Reference Points
- •ISDN PRI Function Groups and Reference Points
- •BRI and PRI Encoding and Framing
- •PRI Encoding
- •PRI Framing
- •BRI Framing and Encoding
- •DDR Step 1: Routing Packets Out the Interface to Be Dialed
- •DDR Step 2: Determining the Subset of the Packets That Trigger the Dialing Process
- •DDR Step 3: Dialing (Signaling)
- •DDR Step 4: Determining When the Connection Is Terminated
- •ISDN and DDR show and debug Commands
- •Multilink PPP
- •Foundation Summary
- •Frame Relay
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Frame Relay Protocols
- •Frame Relay Standards
- •Virtual Circuits
- •LMI and Encapsulation Types
- •DLCI Addressing Details
- •Network Layer Concerns with Frame Relay
- •Layer 3 Addressing with Frame Relay
- •Frame Relay Layer 3 Addressing: One Subnet Containing All Frame Relay DTEs
- •Frame Relay Layer 3 Addressing: One Subnet Per VC
- •Frame Relay Layer 3 Addressing: Hybrid Approach
- •Broadcast Handling
- •Frame Relay Service Interworking
- •A Fully-Meshed Network with One IP Subnet
- •Frame Relay Address Mapping
- •A Partially-Meshed Network with One IP Subnet Per VC
- •A Partially-Meshed Network with Some Fully-Meshed Parts
- •Foundation Summary
- •Part IV: Network Security
- •IP Access Control List Security
- •“Do I Know This Already?” Quiz
- •Foundation Topics
- •Standard IP Access Control Lists
- •IP Standard ACL Concepts
- •Wildcard Masks
- •Standard IP ACL: Example 2
- •Extended IP Access Control Lists
- •Extended IP ACL Concepts
- •Extended IP Access Lists: Example 1
- •Extended IP Access Lists: Example 2
- •Miscellaneous ACL Topics
- •Named IP Access Lists
- •Controlling Telnet Access with ACLs
- •ACL Implementation Considerations
- •Foundation Summary
- •Part V: Final Preparation
- •Final Preparation
- •Suggestions for Final Preparation
- •Preparing for the Exam Experience
- •Final Lab Scenarios
- •Scenario 1
- •Scenario 1, Part A: Planning
- •Solutions to Scenario 1, Part A: Planning
- •Scenario 2
- •Scenario 2, Part A: Planning
- •Solutions to Scenario 2, Part A: Planning
- •Part VI: Appendixes
- •Glossary
- •Answers to the “Do I Know This Already?” Quizzes and Q&A Questions
- •Chapter 1
- •“Do I Know This Already?” Quiz
- •Chapter 2
- •“Do I Know This Already?” Quiz
- •Chapter 3
- •“Do I Know This Already?” Quiz
- •Chapter 4
- •“Do I Know This Already?” Quiz
- •Chapter 5
- •“Do I Know This Already?” Quiz
- •Chapter 6
- •“Do I Know This Already?” Quiz
- •Chapter 7
- •“Do I Know This Already?” Quiz
- •Chapter 8
- •“Do I Know This Already?” Quiz
- •Chapter 9
- •“Do I Know This Already?” Quiz
- •Chapter 10
- •“Do I Know This Already?” Quiz
- •Chapter 11
- •“Do I Know This Already?” Quiz
- •Chapter 12
- •“Do I Know This Already?” Quiz
- •Using the Simulation Software for the Hands-on Exercises
- •Accessing NetSim from the CD
- •Hands-on Exercises Available with NetSim
- •Scenarios
- •Labs
- •Listing of the Hands-on Exercises
- •How You Should Proceed with NetSim
- •Considerations When Using NetSim
- •Routing Protocol Overview
- •Comparing and Contrasting IP Routing Protocols
- •Routing Through the Internet with the Border Gateway Protocol
- •RIP Version 2
- •The Integrated IS-IS Link State Routing Protocol
- •Summary of Interior Routing Protocols
- •Numbering Ports (Interfaces)

ISDN Protocols and Design 335
BRI and PRI Encoding and Framing
The physical layer always includes some specifications about encoding and framing. Without those specifications, the devices attached to the network would not know how to send and receive bits across the medium. In some cases, you can just ignore those details. Unless you are building hardware for a networking vendor, you seldom think about those details.
However, to configure an ISDN PRI, you need to know something about encoding and framing at Layer 1, because you need to pick between two options for each when configuring a PRI on a Cisco router.
In some parts of the world, the telco bases its networks on T1 services, and other parts of the world use E1 services. In fact, the Cisco router hardware used for PRIs consists mostly of chips and software used by T1 and E1 lines. When configuring these cards, you need to know what to configure for the encoding and framing options. If you code a value different from what the telco uses, the line will not work.
PRI Encoding
For any physical layer specification, the line encoding defines which energy levels sent over the cable mean a 1 and which energy levels mean a 0. For instance, an early and simple encoding scheme simply used a +5 volt signal to mean a binary 1 and a –5 volt signal to mean a binary 0. Today, encoding schemes vary greatly from one Layer 1 technology to another. Some consider a signal of a different frequency to mean a 1 or 0. Others examine amplitude (signal strength), look for phase shifts in the signal, or look for more than one of these differences in electrical signals.
ISDN PRI in North America is based on a digital T1 circuit. T1 circuits use two different encoding schemes—Alternate Mark Inversion (AMI) and Binary 8 with Zero Substitution (B8ZS). You will configure one or the other for a PRI; all you need to do is make the router configuration match what the telco is using. For PRI circuits in Europe, Australia, and other parts of the world that use E1s, the only choice for line coding is High-Density Bipolar 3 (HDB3).
PRI Framing
PRI lines send and receive a serial stream of bits. So how does a PRI interface know which bits are part of the D channel, or the first B channel, or the second, or the third, and so on? In a word—framing.
Framing, at ISDN’s physical layer, defines how a device can decide which bits are part of each channel. As is true of encoding, PRI framing is based on the underlying T1 or E1 specifications. The two T1 framing options define 24 different 64-kbps DS0 channels, plus an 8-kbps management channel used by the telco, which gives you a total speed of 1.544 Mbps. That’s true regardless of which of the two framing methods are used on the T1. With E1s, framing defines 32 64-kbps channels, for a total of 2.048 Mbps, regardless of the type of framing used.

336 Chapter 10: ISDN and Dial-on-Demand Routing
The two options for framing on T1s are to use either Extended Super Frame (ESF) or the older option—Super Frame (SF). In most cases today, new T1s use ESF. For PRIs in Europe and Australia, based on E1s, the line uses CRC-4 framing or the original line framing defined for E1s. You simply need to tell the router whether to enable CRC-4 or not.
As soon as the framing details are known, the PRI can assign some channels as B channels and one channel as the D channel. For PRIs based on T1s, the first 23 DS0 channels are the B channels, and the last DS0 channel is the D channel, giving you 23B+D. With PRIs based on E1 circuits, the D channel is channel 15. The channels are counted from 0 to 31. Channel 31 is unavailable for use because it is used for framing overhead. That leaves channels 0 through 14 and 16 through 30 as the B channels, which results in a total of 30B+1D.
Table 10-8 summarizes the key concepts behind framing and encoding, along with the options for each with T1 and E1 circuits.
Table 10-8 Definitions for Encoding and Framing
Term |
Description |
Examples |
|
|
|
Encoding |
Electrical signals sent over a medium that |
B8ZS and AMI (T1), HDB3 (E1) |
|
mean either a binary 0 or 1. |
|
|
|
|
Framing |
The use of a standard for how to interpret a |
SF and ESF (T1), CRC4 (E1) |
|
serial bit stream to identify the individual |
|
|
component channels of that bit stream. |
|
|
|
|
BRI Framing and Encoding
ISDN BRI uses a single encoding scheme and a single option for framing. Because of this, there are no configuration options for either framing or encoding in a router.
ISDN Configuration and Dial-on-Demand Routing
This section covers ISDN configuration and the related DDR configuration that causes Cisco IOS software to use the BRI interface. You must understand DDR configuration and concepts for the ISDN configuration topics to make sense. ISDN configuration can be very brief. In spite of the noise surrounding all the protocols and terminology, you can configure just a few ISDN options in a router. However, the DDR configuration to tell the router when to dial and when to tear down the call can become quite involved.
This section first covers DDR configuration when using BRI interfaces, and then it covers the ISDN configuration for both BRI and PRI. After that, a different style of DDR configuration, DDR dialer profiles, is discussed. A feature called multilink PPP (MLP), which allows multiple B channels to be connected to the same remote site, closes the chapter.

ISDN Configuration and Dial-on-Demand Routing 337
Tables 10-9 and 10-10 summarize the commands used throughout this section.
Table 10-9 ISDN Configuration Commands
|
|
Configuration |
Command |
Description |
Mode |
|
|
|
isdn switch-type switch-type |
Defines to the router the type of |
Global or |
|
ISDN switch to which the ISDN |
interface |
|
line is connected at the central |
|
|
office. |
|
|
|
|
isdn spid1 spid |
Defines the first SPID. |
Interface |
|
|
|
isdn spid2 spid |
Defines the second SPID. |
Interface |
|
|
|
isdn caller phone-number [callback] |
Defines a valid number for |
Interface |
|
incoming calls when using call |
|
|
screening. |
|
|
|
|
dialer-list dialer-group protocol |
Defines the types of traffic that are |
Global |
protocol-name {permit | deny | list |
considered interesting. |
|
access-list-number | access-group} |
|
|
|
|
|
dialer-group n |
Enables a dialer list on this |
Interface |
|
interface. |
|
|
|
|
dialer string string |
The dial string used when dialing |
Interface |
|
only one site. |
|
|
|
|
dialer map protocol next-hop-address |
The dial string to reach the next |
Interface |
[name host-name] [spc] [speed 56 | |
hop. The map command is used |
|
speed 64] [broadcast] [dial- |
when dialing more than one site. |
|
string[:isdn-subaddress]] |
This also is the name used for |
|
|
authentication. The broadcast |
|
|
option ensures that copies of |
|
|
broadcasts go to this next-hop |
|
|
address. |
|
|
|
|
dialer idle-timeout seconds [inbound | |
Defines how long to wait with no |
Interface |
either] |
interesting traffic before |
|
|
terminating a dial. |
|
|
|
|
dialer fast-idle seconds |
If all lines are in use, and new |
Interface |
|
interesting traffic arrives for which |
|
|
another line must be dialed, no dial |
|
|
can occur. fast-idle defines how |
|
|
long to wait to time out the |
|
|
existing dialed lines when this |
|
|
occurs, allowing for a quicker |
|
|
timeout than the normal idle |
|
|
timeout. |
|
|
|
|
controller t1 int-number |
Selects the channelized T1 interface |
Global |
|
to be used as a PRI. |
|
|
|
|
continues

338 Chapter 10: ISDN and Dial-on-Demand Routing
Table 10-9 ISDN Configuration Commands (Continued)
pri-group timeslots range |
Defines which of the DS0 channels |
Controller |
|
will be used in this PRI. |
interface |
|
|
subcommand |
|
|
|
framing sf | esf |
Defines the type of framing used on |
Controller |
|
T1-based PRI. |
interface |
|
|
subcommand |
|
|
|
linecode ami | b8zs |
Defines the type of encoding on T1- |
Controller |
|
based PRI. |
interface |
|
|
subcommand |
|
|
|
Table 10-10 ISDN-Related EXEC Commands
Command |
Description |
|
|
show interfaces bri number [:B channel] |
Includes a reference to the access lists enabled on |
|
the interface. |
|
|
show controllers bri number |
Shows Layer 1 statistics and status for B and D |
|
channels. |
|
|
show isdn {active | history | memory | |
Shows various ISDN status information. |
status | timers} |
|
|
|
show interfaces bri number[[:bchannel] | |
Displays interface information about the D |
[first] [last]] [accounting] |
channel or the B channel(s). |
|
|
show dialer interface bri number |
Lists DDR parameters on the BRI interface. Shows |
|
whether a number is currently dialed by indicating |
|
the current status. Also shows previous attempts |
|
to dial and whether they were successful. |
|
|
debug isdn q921 |
Lists ISDN Layer 2 messages. |
|
|
debug isdn q931 |
Lists ISDN Layer 3 messages (call setup/ |
|
teardown). |
|
|
debug dialer {events | packets | map} |
Lists information when a packet is directed out a |
|
dial interface, specifying whether the packet is |
|
interesting. |
|
|
DDR Legacy Concepts and Configuration
You can configure DDR in several ways, including Legacy DDR and DDR dialer profiles. The main difference between the two is that Legacy DDR associates dial details with a physical interface, whereas DDR dialer profiles disassociate the dial configuration from a physical interface, allowing a great deal of flexibility. The concepts behind Legacy DDR apply to DDR dialer profiles as well, but Legacy DDR configuration is a little less detailed. Legacy DDR is covered first. Dialer profiles are covered later in this chapter. (Another very useful DDR feature, called dialer watch, is very interesting and useful if you have a requirement for DDR.)