This chapter is designed to assist you in final preparation for the CCNA exam by providing

additional practice with the core coverage of the exam. These exercises and tasks require a

broad perspective, which means that you will need to draw on knowledge you acquired in

each of Chapters 2 through 8. This chapter also focuses on configuration and verification

commands in ways that will help you learn and review much better than another set of

questions could. These scenarios are designed with the following assumptions in mind:

•

You might forget many details by the time you have completed your study of the other

chapters. These scenarios cover the entire breadth of topics to remind you about many

of these details.

•

Your understanding of the concepts at this point in your study is complete; practice

and repetition is useful so that you can answer quickly and confidently on the exam.

This chapter is not the only chapter you should use when doing your final preparation

for the CCNA exam. The concepts in Chapter 3, “OSI Reference Model & Layered

Communication,” are not covered in this chapter, mainly because Chapter 3 deals with

concepts and theory; however, Chapter 3 concepts are a very important part of the

CCNA exam. Review the questions at the end of that chapter, and look at the tables that

detail the functions of each OSI layer and the example protocols at each layer, as a final

review of OSI.

The “Foundation Summary” section in each chapter is another great way to review the

topics as your exam date approaches. Figure 9-1 describes your final preparation options

with this book.

As shown, if you want even more final preparation, many practice questions are located in

each chapter and on the CD. All prechapter quizzes and chapter-ending questions, with

answers, are listed in Appendix A, “Answers to the ‘Do I Know This Already?’ Quizzes and

Q&A Sections.” You can quickly read and review these conveniently located questions and

go over the answers and explanations. In addition, the CD includes testing software and

many other additional questions in the format of the CCNA exam (multiple-choice

questions). These questions should be a valuable resource when you are performing final

preparations.

Chapter 9: Scenarios for Final Preparation

The focus of these scenarios is on easily forgotten items. The first such items are the

and

commands. Their options are often ignored, mainly because you can get online help

about the correct option easily when using the Cisco CLI. However, questions about the exact

command options used to see a particular piece of information are scattered throughout the

exam. Take care to review the output of the commands in these scenarios.

You should not count on the CCNA exam to have only multiple-choice questions—it also can

have fill-in-the blank questions, with particular emphasis on commands and command options.

Another focus of this chapter is a review of command-line tricks and acronym trivia. Like it or

not, part of the preparation involves memorization; hopefully, these reminders will help you

answer a question or two on the exam.

Additional examples for IP and IPX addressing are included with each scenario. You can be sure

that IP addressing, subnetting, and broadcast addresses will be on the exam. Also, take care to

recall the Novell encapsulation options, which are also reviewed in these scenarios.

Scenario 9-1

Finally, this chapter contains more configurations for almost all options already covered in the

book. If you can configure these options without online help, you should feel confident that you

can choose the correct command from a list of five options in a multiple-choice question.

If you have enough time, review all parts of each scenario. However, if you have limited time,

you can review only part of a scenario. For example, the solutions to Part A of each scenario

are the background information for Part B; the solutions to Part B of each scenario are the

background information for Part C. So, if you read Part A or B, decide you already know those

details, and don’t want to take the time to wade through your own answer, just look at the

answer in the book; it will lead you into the next part of the scenario.

If you are reading this chapter as your final review before taking the exam, let me take this

opportunity to wish you success. Hopefully you will be relaxed and confident for your exam—

and hopefully this book has helped you build your knowledge and confidence.

Part A of Scenario 9-1 begins with some planning guidelines that include planning IP addresses,

IPX network numbers, the location of SAP filters, and the location of IP standard access lists.

After you complete Part A, Part B of the scenario asks you to configure the three routers to

implement the planned design and a few other features. Finally, Part C asks you to examine

router command output to discover details about the current operation. Part C also lists some

questions related to the user interface and protocol specifications.

Your job is to deploy a new network with three sites, as shown in Figure 9-2.

The decision to use point-to-point serial links, as well as the product choices, has already been

made. For Part A of this scenario, perform the following tasks:

Plan the IP addressing and subnets used in this network. Class B network 163.1.0.0 has

been assigned by the NIC. The maximum number of hosts per subnet is 100. Assign IP

addresses to the PCs as well.

Plan the IPX network numbers to be used. You can choose the internal network numbers

of the servers as well.

Plan the location and logic of IP access lists to filter for the following criteria: Hosts on

the Ethernet attached to R1 are not allowed to send or receive IP traffic to or from hosts

on the Ethernet attached to R3. (Do not code the access lists; just code the location and

logic for the access lists. Part B will ask for configuration, and because the answer to Part

B will be based on where the access lists are placed, you probably will want to see the

answer in Part A before configuring.)

Chapter 9: Scenarios for Final Preparation

Plan the location and logic of SAP filters to prevent clients on the Ethernet off R2 from

logging in to Server 2. Again, do not create the configuration, but simply make notes about

the logic and location of the access lists.

Assume that a single VLAN is used on the switches near Router 1 (R1).

Table 9-1 and Table 9-2 are provided as a convenient place to record your IP subnets, IPX

networks, and IP addresses when performing the planning tasks for this scenario.

Scenario 9-1

R1 Ethernet

R2 Ethernet

R3 Ethernet

Serial between R1 and R2

Serial between R1 and R3

Serial between R2 and R3

Server 1 internal

Server 2 internal

Server 3 internal

PC11

PC12

PC13

PC21

PC31

PC32

R1-E0

R1-S0

R1-S1

R2-E0

R2-S0

R2-S1

R3-E0

R3-S0

R3-S1

Chapter 9: Scenarios for Final Preparation

Keeping the design as simple as possible, yet without making it too simple so as not to be useful

as the network evolves, is a good practice. In these suggested answers, the numbering scheme

is chosen to help those of us with fading memories.

The IP subnet design includes the use of mask 255.255.255.128. The design criteria leaves

enough ambiguity that you could argue that any mask with at least 7 host bits was valid;

therefore, the much easier mask of 255.255.255.0 would be valid. However, I chose a

more challenging mask, just to give you more difficult practice.

The IPX network number assignment is simply a matter of choosing numbers; these

are recorded, along with the IP addresses, in Table 9-3. The IP addresses are assigned in

Table 9-4.

R1 Ethernet 255.255.255.128 163.1.1.128 1

R2 Ethernet 255.255.255.128 163.1.2.128 2

R3 Ethernet 255.255.255.128 163.1.3.128 3

Serial between R1 and R2 255.255.255.128 163.1.12.128 12

Serial between R1 and R3 255.255.255.128 163.1.13.128 13

Serial between R2 and R3 255.255.255.128 163.1.23.128 23

Server 1 internal — — 101

Server 2 internal — — 102

Server 3 internal — — 103

PC11 163.1.1.211

PC12 163.1.1.212

PC13 163.1.1.213

PC21 163.1.2.221

PC31 163.1.3.231

PC32 163.1.3.232

R1-E0 163.1.1.201

R1-S0 163.1.12.201

Scenario 9-1

As usual, the access lists can be placed in several areas to achieve the desired function.

Also as usual, the criteria for the access list is subject to interpretation. One solution is to

filter packets sent from hosts on the Ethernet off R3, filtering them as they enter R1, on

either of R1’s serial interfaces. By filtering packets in only one direction, applications that

require a two-way flow will not successfully communicate. By filtering on both of R1’s

serial interfaces for inbound traffic, any valid route for the incoming packets will be

checked.

For the SAP filter, several options also exist; one is shown here. By stopping R2 from

adding the SAP for Server 2 to its SAP table, R2 will never advertise that server in a GNS

request, nor will Server 3 learn about Server 2’s SAPs from R2’s SAP updates. So, the

plan is to place incoming SAP filters on both serial interfaces on R2, to filter Server 2 from

being added to R2’s SAP table.

The next step in your job is to deploy the network designed in Scenario 9-1, Part A. Use the

solutions for Part A of Scenario 9-1 to direct you in identifying IP and IPX addresses and

determining the logic behind the access lists. For Scenario 9-1, Part B, perform the following

tasks:

Configure IP, IPX, and IP access lists and IPX SAP filters based on Scenario 9-1, Part A’s

design.

Use RIP as the IP routing protocol.

Use PPP as the data link protocol on the link between R2 and R3. Use the default serial

encapsulation elsewhere.

R1-S1 163.1.13.201

R2-E0 163.1.2.202

R2-S0 163.1.12.202

R2-S1 163.1.23.202

R3-E0 163.1.3.203

R3-S0 163.1.13.203

R3-S1 163.1.23.203

Chapter 9: Scenarios for Final Preparation

Example 9-1, Example 9-2, and Example 9-3 show the configurations for Scenario 9-1, Part B,

given the criteria in Tasks 1, 2, and 3.

hostname R1

!

ipx routing 0200.1111.1111

!

interface Serial0

ip address 163.1.12.201 255.255.255.128

ipx network 12

ip access-group 83 in

!

interface Serial1

ip address 163.1.13.201 255.255.255.128

ipx network 13

ip access-group 83 in

!

Ethernet0

ip address 163.1.1.201 255.255.255.128

ipx network 1

!

router rip

network 163.1.0.0

!

access-list 83 deny 163.1.3.128 0.0.0.127

access-list 83 permit any

hostname R2

!

ipx routing 0200.2222.2222

!

interface Serial0

ip address 163.1.12.202 255.255.255.128

ipx network 12

ipx input-sap-filter 1010

!

interface Serial1

encapsulation ppp

ip address 163.1.23.202 255.255.255.128

ipx network 23

ipx input-sap-filter 1010

!

Ethernet0

ip address 163.1.2.202 255.255.255.128

ipx network 2

!

router rip

network 163.1.0.0

Scenario 9-1

The CCNA exam tests you on your memory of the kinds of information you can find in the

output of various

commands. Using Example 9-4, Example 9-5, and Example 9-6 as

references, answer the questions following the examples.

In the network from which these commands were captured, several administrative settings not

mentioned in the scenario were configured. For instance, the enable password was configured.

Any

commands in the examples in this chapter might have other

unrelated configurations.

!

access-list 1010 deny 102

access-list 1010 permit -1

hostname R3

!

ipx routing 0200.3333.3333

!

interface Serial0

ip address 163.1.13.203 255.255.255.128

ipx network 13

!

interface Serial1

encapsulation ppp

ip address 163.1.23.203 255.255.255.128

ipx network 23

!

Ethernet0

ip address 163.1.3.203 255.255.255.128

ipx network 3

!

router rip

network 163.1.0.0

R1#

show ip interface brief

Interface IP-Address OK? Method Status Protocol

Serial0 163.1.12.201 YES NVRAM up up

Serial1 163.1.13.201 YES NVRAM up up

Ethernet0 163.1.1.201 YES NVRAM up up

R1#

show access-lists

Chapter 9: Scenarios for Final Preparation

Standard IP access list 83

deny 163.1.3.0, wildcard bits 0.0.0.127

permit any

R1#

R1#

debug ipx sap event

IPX service events debugging is on

R1#

IPXSAP: positing update to 1.ffff.ffff.ffff via Ethernet0 (broadcast) (full)

IPXSAP: positing update to 13.ffff.ffff.ffff via Serial1 (broadcast) (full)

IPXSAP: positing update to 12.ffff.ffff.ffff via Serial0 (broadcast) (full)

IPXSAP: positing update to 1.ffff.ffff.ffff via Ethernet0 (broadcast) (full)

R1#

undebug all

All possible debugging has been turned off

R1#

R1#

debug ipx sap activity

IPX service debugging is on

R1#

IPXSAP: positing update to 13.ffff.ffff.ffff via Serial1 (broadcast) (full)

IPXSAP: Update type 0x2 len 224 src:13.0200.1111.1111 dest:13.ffff.ffff.ffff(452)

type 0x4, “Server3“, 103.0000.0000.0001(451), 4 hops

type 0x4, “Server1“, 101.0000.0000.0001(451), 3 hops

type 0x4, “Server2“, 102.0000.0000.0001(451), 3 hops

IPXSAP: positing update to 12.ffff.ffff.ffff via Serial0 (broadcast) (full)

IPXSAP: Update type 0x2 len 160 src:12.0200.1111.1111 dest:12.ffff.ffff.ffff(452)

type 0x4, “Server1“, 101.0000.0000.0001(451), 3 hops

type 0x4, “Server2“, 102.0000.0000.0001(451), 3 hops

R1#

undebug all

All possible debugging has been turned off

R1#

R1#

R1#

debug ipx routing event

IPX routing events debugging is on

R1#

IPXRIP: positing full update to 1.ffff.ffff.ffff via Ethernet0 (broadcast)

IPXRIP: positing full update to 13.ffff.ffff.ffff via Serial1 (broadcast)

IPXRIP: positing full update to 12.ffff.ffff.ffff via Serial0 (broadcast)

IPXRIP: 13 FFFFFFFF not added, entry in table is static/connected/internal

IPXRIP: 12 FFFFFFFF not added, entry in table is static/connected/internal

IPXRIP: positing full update to 1.ffff.ffff.ffff via Ethernet0 (broadcast)

R1#

undebug all

All possible debugging has been turned off

R1#

R1#

debug ipx routing activity

IPX routing debugging is on

R1#

IPXRIP: update from 1.0000.0c89.b130

102 in 2 hops, delay 2

101 in 2 hops, delay 2

Scenario 9-1

IPXRIP: positing full update to 13.ffff.ffff.ffff via Serial1 (broadcast)

IPXRIP: src=13.0200.1111.1111, dst=13.ffff.ffff.ffff, packet sent

network 103, hops 4, delay 14

network 23, hops 2, delay 13

network 2, hops 3, delay 8

network 101, hops 3, delay 8

network 102, hops 3, delay 8

network 1, hops 1, delay 7

network 12, hops 1, delay 7

IPXRIP: positing full update to 12.ffff.ffff.ffff via Serial0 (broadcast)

IPXRIP: src=12.0200.1111.1111, dst=12.ffff.ffff.ffff, packet sent

network 3, hops 2, delay 13

network 2, hops 3, delay 8

network 101, hops 3, delay 8

network 102, hops 3, delay 8

network 1, hops 1, delay 7

network 13, hops 1, delay 7

IPXRIP: update from 12.0200.2222.2222

103 in 3 hops, delay 8

IPXRIP: 13 FFFFFFFF not added, entry in table is static/connected/internal

13 in 2 hops, delay 13

3 in 2 hops, delay 13

23 in 1 hops, delay 7

2 in 1 hops, delay 7

IPXRIP: update from 13.0200.3333.3333

103 in 4 hops, delay 14

IPXRIP: 12 FFFFFFFF not added, entry in table is static/connected/internal

12 in 2 hops, delay 13

3 in 1 hops, delay 7

2 in 2 hops, delay 13

23 in 1 hops, delay 7

IPXRIP: positing full update to 1.ffff.ffff.ffff via Ethernet0 (broadcast)

IPXRIP: src=1.0000.0ccf.21cd, dst=1.ffff.ffff.ffff, packet sent

network 103, hops 4, delay 9

network 3, hops 2, delay 8

network 23, hops 2, delay 8

network 13, hops 1, delay 2

network 12, hops 1, delay 2

IPXRIP: update from 1.0000.0c89.b130

102 in 2 hops, delay 2

101 in 2 hops, delay 2

2 in 2 hops, delay 2

R1#

undebug all

All possible debugging has been turned off

R1#

R1#

debug ip rip events

RIP event debugging is on

R1#

RIP: received v1 update from 163.1.13.203 on Serial1

RIP: Update contains 4 routes

Chapter 9: Scenarios for Final Preparation

RIP: sending v1 update to 255.255.255.255 via Serial0 (163.1.12.201)

RIP: Update contains 4 routes

RIP: Update queued

RIP: Update sent via Serial0

RIP: sending v1 update to 255.255.255.255 via Serial1 (163.1.13.201)

RIP: Update contains 4 routes

RIP: Update queued

RIP: Update sent via Serial1

RIP: sending v1 update to 255.255.255.255 via Ethernet0 (163.1.1.201)

RIP: Update contains 7 routes

RIP: Update queued

RIP: Update sent via Ethernet0

RIP: received v1 update from 163.1.12.202 on Serial0

RIP: Update contains 4 routes

All possible debugging has been turned off

R1#

RIP protocol debugging is on

R1#

RIP: received v1 update from 163.1.12.202 on Serial0

163.1.2.128 in 1 hops

163.1.3.128 in 2 hops

163.1.23.128 in 1 hops

163.1.23.203 in 1 hops

RIP: received v1 update from 163.1.13.203 on Serial1

163.1.2.128 in 2 hops

163.1.3.128 in 1 hops

163.1.23.128 in 1 hops

163.1.23.202 in 1 hops

RIP: sending v1 update to 255.255.255.255 via Serial0 (163.1.12.201)

subnet 163.1.3.128, metric 2

subnet 163.1.1.128, metric 1

subnet 163.1.13.128, metric 1

host 163.1.23.202, metric 2

RIP: sending v1 update to 255.255.255.255 via Serial1 (163.1.13.201)

subnet 163.1.2.128, metric 2

subnet 163.1.1.128, metric 1

subnet 163.1.12.128, metric 1

host 163.1.23.203, metric 2

RIP: sending v1 update to 255.255.255.255 via Ethernet0 (163.1.1.201)

subnet 163.1.2.128, metric 2

subnet 163.1.3.128, metric 2

subnet 163.1.12.128, metric 1

subnet 163.1.13.128, metric 1

subnet 163.1.23.128, metric 2

host 163.1.23.203, metric 2

host 163.1.23.202, metric 2

All possible debugging has been turned off

R1#

Serial0 is up, line protocol is up

Hardware is HD64570

Internet address is 163.1.12.202/25

MTU 1500 bytes, BW 56 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation HDLC, loopback not set, keepalive set (10 sec)

Last input 00:00:04, output 00:00:00, output hang never

Last clearing of “show interface” counters never

Queuing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

1242 packets input, 98477 bytes, 0 no buffer

Received 898 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

1249 packets output, 91395 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 output buffer failures, 0 output buffers swapped out

12 carrier transitions

DCD=up DSR=up DTR=up RTS=up CTS=up

Serial1 is up, line protocol is up

Hardware is HD64570

Internet address is 163.1.23.202/25

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation PPP, loopback not set, keepalive set (10 sec)

LCP Open

Open: IPCP, CDPCP, LLC2, IPXCP

Last input 00:00:02, output 00:00:02, output hang never

Last clearing of “show interface” counters never

Input queue: 0/75/0 (size/max/drops); Total output drops: 0

Queuing strategy: weighted fair

Output queue: 0/1000/0 (size/max total/drops)

Conversations 0/1/64 (active/max active/threshold)

Reserved Conversations 0/0 (allocated/max allocated)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

1654 packets input, 90385 bytes, 0 no buffer

Received 1644 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

1674 packets output, 96130 bytes, 0 underruns

0 output errors, 0 collisions, 8 interface resets

0 output buffer failures, 0 output buffers swapped out

13 carrier transitions

DCD=up DSR=up DTR=up RTS=up CTS=up

Ethernet0 is up, line protocol is up

Hardware is MCI Ethernet, address is 0000.0c89.b170 (bia 0000.0c89.b170)

Internet address is 163.1.2.202, subnet mask is 255.255.255.128

MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255

Encapsulation ARPA, loopback not set, keepalive set (10 sec)

ARP type: ARPA, ARP Timeout 4:00:00

Last input 00:00:00, output 00:00:04, output hang never

Last clearing of “show interface” counters never

Queuing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

2274 packets input, 112381 bytes, 0 no buffer

Received 1913 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

863 packets output, 110146 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 output buffer failures, 0 output buffers swapped out

6 transitions

Interface IPX Network Encapsulation Status IPX State

Serial0 12 HDLC up [up]

Serial1 23 PPP up [up]

Ethernet0 2 SAP up [up]

Codes: C - Connected primary network, c - Connected secondary network

S - Static, F - Floating static, L - Local (internal), W - IPXWAN

R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate

s - seconds, u - uses

9 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.

No default route known.

C 2 (SAP), E0

C 12 (HDLC), Se0

C 23 (PPP), Se1

R 1 [07/01] via 12.0200.1111.1111, 59s, Se0

R 3 [07/01] via 23.0200.3333.3333, 5s, Se1

R 13 [07/01] via 23.0200.3333.3333, 5s, Se1

R 101 [08/03] via 12.0200.1111.1111, 0s, Se0

R 102 [08/03] via 12.0200.1111.1111, 0s, Se0

R 103 [02/02] via 2.0000.0cac.70ef, 21s, E0

Routing Protocol is “rip“

Sending updates every 30 seconds, next due in 6 seconds

Invalid after 180 seconds, hold down 180, flushed after 240

Outgoing update filter list for all interfaces is not set

Incoming update filter list for all interfaces is not set

Redistributing: rip

Default version control: send version 1, receive any version

Interface Send Recv Key-chain

Serial0 1 1 2

Serial1 1 1 2

Ethernet0 1 1 2

Routing for Networks:

163.1.0.0

Routing Information Sources:

Gateway Distance Last Update

163.1.13.201 120 00:00:02

163.1.23.202 120 00:00:09

Distance: (default is 120)

Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail

3 Total IPX Servers

Table ordering is based on routing and server info

Type Name Net Address Port Route Hops Itf

P 4 Server3 103.0000.0000.0001:0451 2/02 2 E0

P 4 Server1 101.0000.0000.0001:0451 8/03 3 Se0

P 4 Server2 102.0000.0000.0001:0451 8/03 3 Se0

Building configuration...

Current configuration:

!

version 11.2

no service password-encryption

no service udp-small-servers

no service tcp-small-servers

!

hostname R3

!

enable secret 5 $1$kI1V$NkybGlP9tzP7BYvAKYT.c1

!

no ip domain-lookup

ipx routing 0200.3333.3333

!

interface Serial0

ip address 163.1.13.203 255.255.255.128

ipx network 13

no fair-queue

!

interface Serial1

ip address 163.1.23.203 255.255.255.128

encapsulation ppp

ipx network 23

!

interface Ethernet0

ip address 163.1.3.203 255.255.255.128

ipx network 3

!

router rip

network 163.1.0.0

!

no ip classless

!

!

!

!

line con 0

password cisco

login

line aux 0

line vty 0 4

password cisco

login

!

end

Protocol Address Age (min) Hardware Addr Type Interface

Internet 163.1.3.203 - 0000.0c89.b1b0 SNAP Ethernet0

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default

U - per-user static route, o - ODR

Gateway of last resort is not set

163.1.0.0/16 is variably subnetted, 7 subnets, 2 masks

R 163.1.2.128/25 [120/1] via 163.1.23.202, 00:00:22, Serial1

C 163.1.3.128/25 is directly connected, Ethernet0

R 163.1.1.128/25 [120/1] via 163.1.13.201, 00:00:28, Serial0

R 163.1.12.128/25 [120/1] via 163.1.13.201, 00:00:28, Serial0

[120/1] via 163.1.23.202, 00:00:22, Serial1

C 163.1.13.128/25 is directly connected, Serial0

C 163.1.23.128/25 is directly connected, Serial1

C 163.1.23.202/32 is directly connected, Serial1

Type escape sequence to abort.

Tracing the route to 163.1.13.203

1 163.1.13.201 16 msec 16 msec 16 msec

2 163.1.13.203 44 msec * 32 msec

Answer the following questions. Use Example 9-4, Example 9-5, and Example 9-6 as

references when the question refers directly to this scenario.

switches, which ports will be considered to be root ports?

so that it can forward on its E1 port? In what interim Spanning Tree states will E1 be

before it forwards?

provide the details of what is in the RIP update?

provide the details of what is in the IPX RIP update?

addresses?

networks?

IPX RIP? What in the command identifies these routing protocols?

updates? Which options just provide messages referring to the fact that an update is sent,

without listing the details?

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 163.1.13.203, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 64/66/68 ms

Type escape sequence

to abort.

Sending 5, 100-byte IPX Cisco Echoes to 13.0200.3333.3333, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 68/69/72 ms

255.255.255.0). If the user was in user mode, what steps would be necessary to change the

IP address?

be updated, based on the change in the previous question. List the steps necessary to make

this change.

list all commands that start with C? List the steps; assume that you are in privileged mode.

is reloaded.

The answers to the questions for Scenario 9-1, Part C are as follows:

the lowest bridge priority—or, if a tie occurs, the bridge or switch with the lowest value

for root bridge ID—is considered to be the root.

E1/0. Likewise, Switch3 will be receiving CBPDUs with a lower cost on its E1/0 port. So,

each switch will consider its E1/0 port to be its root port; this port is placed in a forwarding

state.

messages onto its E1 (the Ethernet segment that Switch2 and Switch3 have in common).

Switch3 then transitions its E1 port to listening state, then to learning state, and finally to

forwarding state.

in Example 9-4. This example shows four routes being described in the update to R3. One

of the routes (appropriately) missing in the update is 163.1.13.128, which is the subnet on

the serial link between R1 and R3. The other (appropriately) missing route is the route to

163.1.3.128—thus, R1’s best route to that subnet is through R3. Split-horizon rules

prevent either route from being advertised.

output. This output is also shown in Example 9-4. Two routes from R1’s routing table are

not included in the update: namely, networks 12 and 2. Network 12 is on the common

serial link, and R1’s route to network 2 points through R2. Both networks are not included

due to split-horizon rules.

not IPX addresses, because IPX does not use a concept like ARP on LANs.

Examples 9-5 and 9-6). The metric value for each IP subnet is the second of the two

numbers inside brackets. Two IPX metrics are located between brackets for IPX routes:

the number of timer ticks and the number of hops.

information (refer to Examples 9-5 and 9-6). The source of the routing information is

coded in a field on the left side of the output line and is based on the legend of such codes

that appear at the beginning of the command output before the actual routing table entries

are listed.

the details of what is sent in the update (refer to Example 9-4).

Example 9-4).

password: password

R3#

R3#

clear clock configure connect copy

R3#c

the ticks metric, the hop count is considered.

issued by clients. Both R2 and R3 will reply by default; R2’s response is unlikely to be

used because its GNS delay will ensure that its reply is slower than the server on the same

Ethernet.

This scenario uses the familiar Frame Relay network with three routers and a full mesh of

virtual circuits. Some planning exercises begin the scenario (Scenario 9-2, Part A), followed by

Your job is to deploy a new network with three sites, as shown in Figure 9-3. The choice to use

Frame Relay, as well as the product choices, have already been made. For Part A of this

scenario, perform the following tasks:

providing a list for the local LAN administrators defining the IP addresses that they can

assign to hosts. Using Table 9-5, derive the subnet numbers and broadcast addresses, and

define the range of valid IP addresses. A static mask of 255.255.255.192 is used on all

subnets.

the types of headers used by each PC. Plan the encapsulation types to be used, including

the correct keywords used in the IOS.

addresses in each subnet become obvious. One important item to note is that the three

Frame Relay interfaces are in the same subnet, which is a clue that subinterfaces will not

be used and that the Frame Relay interfaces will be treated as a single network. Table 9-7

provides the answers to this question.

R1 E0 168.11.11.101

R2 E0 168.11.12.102

R3 E0 168.11.13.103

R1 S0 168.11.123.201

R2 S0 168.11.123.202

R3 S0 168.11.123.203

Attached to R1 E0

Attached to R2 E0

Attached to R3 E0

Frame Relay

Server 1 Internal

Server 2 Internal

Server 3 Internal

R1 E0 168.11.11.101 168.11.11.64 168.11.11.127 65 to 126 in last octet

R2 E0 168.11.12.102 168.11.12.64 168.11.12.127 65 to 126 in last octet

R3 E0 168.11.13.103 168.11.13.64 168.11.13.127 65 to 126 in last octet

Ethernet. The important item here is to correlate the headers used by the devices to the

correct name used by Cisco in the encapsulation command. Table 9-8 summarizes the

encapsulations for the four PCs.

realizing that two network numbers are needed on R1’s E0 and on R2’s E0 is the hidden

part of the objective. As long as your network numbers are not duplicated, and as long as

you planned for two IPX networks for the two aforementioned Ethernet interfaces, any

network numbers are fine. Table 9-9 lists the network numbers that will be used as the

basis of the configuration in Scenario 9-2, Part B.

R1 S0 168.11.123.201 168.11.123.192 168.11.123.255 193 to 254 in last octet

R2 S0 168.11.123.202 168.11.123.192 168.11.123.255 193 to 254 in last octet

R3 S0 168.11.123.203 168.11.123.192 168.11.123.255 193 to 254 in last octet

PC11 ARPA

PC12 Novell-ether

PC21 SAP

PC22 SNAP

R1 E0 110 (ARPA)

R1 E0 111 (Novell-ether)

R2 E0 120 (SAP)

R2 E0 121 (SNAP)

R3 E0 130

Frame Relay 123

Server 1 internal 101

Server 2 internal 102

Server 3 internal 103

The next step in your job is to deploy the network designed in Scenario 9-2, Part A. Use the

solutions to Scenario 9-2, Part A to direct you in identifying IP and IPX addresses and the

encapsulations to be used. For Scenario 9-2, Part B, perform the following tasks:

Use IGRP process-id 1.

described in Scenario 9-2, Part A.

type ANSI. Cisco encapsulation should be used for all routers.

Define the required IP static routes to allow hosts on all three Ethernets to communicate.

(This is unlikely in real life; it’s just an excuse to review IP static routes!)

R2. Define static mappings as necessary for all hosts to communicate.

Example 9-7, Example 9-8, and Example 9-9 show the configurations for Tasks 1, 2, and 3.

ipx routing 0200.aaaa.aaaa

!

interface serial0

encapsulation frame-relay

ip address 168.11.123.201 255.255.255.192

ipx network 123

frame-relay interface-dlci 502

frame-relay interface-dlci 503

!

interface ethernet 0

ip address 168.11.11.101 255.255.255.192

!

ipx network 110 encapsulation arpa

ipx network 111 encapsulation novell-ether secondary

!

router igrp 1

network 168.11.0.0

For Task 4 in Scenario 9-2, Part B, static routes need to be defined in all three routers. R2 will

need routes to the two LAN-based subnets at the other sites. Likewise, R1 and R3 will need

routes to 168.11.12.64 (Ethernet off R2). Example 9-10 lists the routes in all three routers.

ipx routing 0200.bbbb.bbbb

!

interface serial0

encapsulation frame-relay

ip address 168.11.123.202 255.255.255.192

ipx network 123

frame-relay interface-dlci 501

frame-relay interface-dlci 503

!

interface ethernet 0

ip address 168.11.12.102 255.255.255.192

ipx network 120 encapsulation sap

ipx network 121 encapsulation snap secondary

!

router igrp 1

network 168.11.0.0

ipx routing 0200.cccc.cccc

!

interface serial0

encapsulation frame-relay

ip address 168.11.123.203 255.255.255.192

ipx network 123

frame-relay interface-dlci 501

frame-relay interface-dlci 502

!

interface ethernet 0

ip address 168.11.13.103 255.255.255.192

ipx network 130

!

router igrp 1

network 168.11.0.0

that packets that would normally be broadcast, such as routing updates, will be sent as unicasts

across each VC for each protocol. Example 9-11 lists the additional commands.

The CCNA exam tests your memory of the kinds of information you can find in the output of

answer the questions following the examples.

mentioned in the scenario were configured. For instance, the enable password was configured.

unrelated configuration.

Interface IPX Network Encapsulation Status IPX State

Serial0 123 FRAME-RELAY up [up]

Serial1 unassigned not config’d administratively down n/a

Ethernet0 110 ARPA up [up]

Ethernet0 111 Novell-ether up [up]

Interface IP-Address OK? Method Status Protocol

Serial0 168.11.123.201 YES NVRAM up up

Serial1 unassigned YES unset administratively down down

Ethernet0 168.11.11.101 YES NVRAM up up

IPX service debugging is on

R1#

IPXSAP: positing update to 110.ffff.ffff.ffff via Ethernet0 (broadcast) (full)

IPXSAP: Update type 0x2 len 96 src:110.0000.0ccf.21cd dest:110.ffff.ffff.ffff(452)

type 0x4, “Server3“, 103.0000.0000.0001(451), 4 hops

IPXSAP: positing update to 111.ffff.ffff.ffff via Ethernet0 (broadcast) (full)

IPXSAP: Update type 0x2 len 224 src:111.0000.0ccf.21cd

dest:111.ffff.ffff.ffff(452)

type 0x4, “Server3“, 103.0000.0000.0001(451), 4 hops

type 0x4, “Server1“, 101.0000.0000.0001(451), 3 hops

type 0x4, “Server2“, 102.0000.0000.0001(451), 3 hops

IPXSAP: Response (in) type 0x2 len 160 src:110.0000.0c89.b130

dest:110.ffff.ffff.ffff(452)

type 0x4, “Server2“, 102.0000.0000.0001(451), 2 hops

type 0x4, “Server1“, 101.0000.0000.0001(451), 2 hops

IPXSAP: positing update to 123.ffff.ffff.ffff via Serial0 (broadcast) (full)

IPXSAP: Update type 0x2 len 160 src:123.0200.aaaa.aaaa

dest:123.ffff.ffff.ffff(452)

type 0x4, “Server1“, 101.0000.0000.0001(451), 3 hops

type 0x4, “Server2“, 102.0000.0000.0001(451), 3 hops

IPXSAP: Response (in) type 0x2 len 96 src:123.0200.bbbb.bbbb

dest:123.ffff.ffff.ffff(452)

type 0x4, “Server3“, 103.0000.0000.0001(451), 3 hops

All possible debugging has been turned off

R1#

IPX routing debugging is on

R1#

IPXRIP: positing full update to 123.ffff.ffff.ffff via Serial0 (broadcast)

IPXRIP: src=123.0200.aaaa.aaaa, dst=123.ffff.ffff.ffff, packet sent

network 555, hops 2, delay 8

network 101, hops 3, delay 8

network 102, hops 3, delay 8

network 111, hops 1, delay 7

network 110, hops 1, delay 7

IPXRIP: update from 123.0200.3333.3333

130 in 1 hops, delay 7

IPXRIP: update from 123.0200.bbbb.bbbb

444 in 2 hops, delay 8

103 in 3 hops, delay 8

121 in 1 hops, delay 7

120 in 1 hops, delay 7

IPXRIP: positing full update to 110.ffff.ffff.ffff via Ethernet0 (broadcast)

IPXRIP: src=110.0000.0ccf.21cd, dst=110.ffff.ffff.ffff, packet sent

network 120, hops 2, delay 8

network 121, hops 2, delay 8

network 103, hops 4, delay 9

network 444, hops 3, delay 9

network 130, hops 2, delay 8

network 111, hops 1, delay 2

network 123, hops 1, delay 2

IPXRIP: positing full update to 111.ffff.ffff.ffff via Ethernet0 (broadcast)

IPXRIP: src=111.0000.0ccf.21cd, dst=111.ffff.ffff.ffff, packet sent

network 120, hops 2, delay 8

network 121, hops 2, delay 8

network 103, hops 4, delay 9

network 444, hops 3, delay 9

network 130, hops 2, delay 8

network 555, hops 2, delay 3

network 101, hops 3, delay 3

network 102, hops 3, delay 3

network 110, hops 1, delay 2

network 123, hops 1, delay 2

IPXRIP: update from 110.0000.0c89.b130

102 in 2 hops, delay 2

101 in 2 hops, delay 2

555 in 1 hops, delay 2

R1#

All possible debugging has been turned off

R1#

IGRP protocol debugging is on

R1#

IGRP: sending update to 255.255.255.255 via Serial0 (168.11.123.201)

subnet 168.11.123.192, metric=180571

subnet 168.11.11.64, metric=688

subnet 168.11.13.64, metric=180634

subnet 168.11.12.64, metric=180634

IGRP: sending update to 255.255.255.255 via Ethernet0 (168.11.11.101)

subnet 168.11.123.192, metric=180571

subnet 168.11.13.64, metric=180634

subnet 168.11.12.64, metric=180634

IGRP: received update from 168.11.123.202 on Serial0

subnet 168.11.123.192, metric 182571 (neighbor 180571)

subnet 168.11.11.64, metric 182634 (neighbor 180634)

subnet 168.11.13. 64, metric 182634 (neighbor 180634)

subnet 168.11.12. 64, metric 180634 (neighbor 688)

IGRP: received update from 168.11.123.203 on Serial0

subnet 168.11.123.192, metric 182571 (neighbor 8476)

subnet 168.11.11. 64, metric 182634 (neighbor 8539)

subnet 168.11.13. 64, metric 180634 (neighbor 688)

subnet 168.11.12. 64, metric 182634 (neighbor 8539)

IGRP: sending update to 255.255.255.255 via Serial0 (168.11.123.201)

subnet 168.11.123.192, metric=180571

subnet 168.11.11. 64, metric=688

subnet 168.11.13. 64, metric=180634

subnet 168.11.12. 64, metric=180634

IGRP: sending update to 255.255.255.255 via Ethernet0 (168.11.11.101)

subnet 168.11.123.192, metric=180571

subnet 168.11.13. 64, metric=180634

subnet 168.11.12. 64, metric=180634

All possible debugging has been turned off

Serial0 is up, line protocol is up

Hardware is HD64570

Internet address is 168.11.123.202/26

MTU 1500 bytes, BW 56 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)

LMI enq sent 1657, LMI stat recvd 1651, LMI upd recvd 0, DTE LMI up

LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0

LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE

Broadcast queue 0/64, broadcasts sent/dropped 979/0, interface broadcasts 490

Last input 00:00:01, output 00:00:01, output hang never

Last clearing of “show interface” counters never

Queuing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

4479 packets input, 165584 bytes, 0 no buffer

Received 1 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

4304 packets output, 154785 bytes, 0 underruns

0 output errors, 0 collisions, 4 interface resets

0 output buffer failures, 0 output buffers swapped out

12 carrier transitions

DCD=up DSR=up DTR=up RTS=up CTS=up

Serial1 is administratively down, line protocol is down

Hardware is HD64570

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation PPP, loopback not set, keepalive set (10 sec)

LCP Closed

Closed: CDPCP, LLC2

Last input never, output never, output hang never

Last clearing of “show interface” counters never

Input queue: 0/75/0 (size/max/drops); Total output drops: 0

Queuing strategy: weighted fair

Output queue: 0/1000/0 (size/max total/drops)

Conversations 0/0/64 (active/max active/threshold)

Reserved Conversations 0/0 (allocated/max allocated)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 5 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions

DCD=down DSR=down DTR=down RTS=down CTS=down

Ethernet0 is up, line protocol is up

Hardware is MCI Ethernet, address is 0000.0c89.b170 (bia 0000.0c89.b170)

Internet address is 168.11.12.102/26, subnet mask is 255.255.255.192

MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255

Encapsulation ARPA, loopback not set, keepalive set (10 sec)

ARP type: ARPA, ARP Timeout 4:00:00

Last input 00:00:04, output 00:00:04, output hang never

Last clearing of “show interface” counters never

Queuing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

6519 packets input, 319041 bytes, 0 no buffer

Received 5544 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

2055 packets output, 192707 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 output buffer failures, 0 output buffers swapped out

6 transitions

Interface IPX Network Encapsulation Status IPX State

Serial0 123 FRAME-RELAY up [up]

Serial1 unassigned not config’d administratively down n/a

Ethernet0 120 SAP up [up]

Ethernet0 121 SNAP up [up]

Routing Protocol is “igrp 1“

Sending updates every 90 seconds, next due in 6 seconds

Invalid after 270 seconds, hold down 280, flushed after 630

Outgoing update filter list for all interfaces is not set

Incoming update filter list for all interfaces is not set

Default networks flagged in outgoing updates

Default networks accepted from incoming updates

IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0

IGRP maximum hopcount 100

IGRP maximum metric variance 1

Redistributing: igrp 1

Routing for Networks:

168.11.0.0

Routing Information Sources:

Gateway Distance Last Update

168.11.123.201 100 00:00:02

168.11.123.203 100 00:00:09

Distance: (default is 100)

Codes: C - Connected primary network, c - Connected secondary network

S - Static, F - Floating static, L - Local (internal), W - IPXWAN

R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate

s - seconds, u - uses

9 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.

No default route known.

C 120 (SAP), E0

c 121 (SNAP), E0

C 123 (FRAME-RELAY), Se0

R 101 [08/03] via 123.0200.aaaa.aaaa, 21s, Se0

R 102 [02/02] via 123.0200.0cac.70ef, 22s, E0

R 103 [08/03] via 120.0000.aaaa.aaaa, 29s, Se0

R 110 [07/01] via 123.0200.aaaa.aaaa, 22s, Se0

R 111 [07/01] via 123.0200.aaaa.aaaa, 22s, Se0

R 130 [07/01] via 123.0200.cccc.cccc, 19s, Se0

Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail

2 Total IPX Servers

Table ordering is based on routing and server info

Type Name Net Address Port Route Hops Itf

P 4 Server3 103.0000.0000.0001:0451 8/03 3 Se0

P 4 Server1 101.0000.0000.0001:0451 8/03 3 Se0

P 4 Server2 102.0000.0000.0001:0451 2/02 2 E0

PVC Statistics for interface Serial0 (Frame Relay DTE)

DLCI = 501, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0

input pkts 780 output pkts 529 in bytes 39602

out bytes 29260 dropped pkts 0 in FECN pkts 0

in BECN pkts 0 out FECN pkts 0 out BECN pkts 0

in DE pkts 0 out DE pkts 0

out bcast pkts 525 out bcast bytes 28924

pvc create time 04:36:40, last time pvc status changed 04:34:54

DLCI = 503, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0

input pkts 481 output pkts 493 in bytes 30896

out bytes 34392 dropped pkts 0 in FECN pkts 0

in BECN pkts 0 out FECN pkts 0 out BECN pkts 0

in DE pkts 0 out DE pkts 0

out bcast pkts 493 out bcast bytes 34392

pvc create time 04:36:41, last time pvc status changed 04:34:55

Serial0 (up): ipx 123.0200.aaaa.aaaa dlci 501(0x1F5,0x7C50), dynamic,

broadcast,, status defined, active

Serial0 (up): ipx 123.0200.cccc.cccc dlci 503(0x1F7,0x7C70), dynamic,

broadcast,, status defined, active

Serial0 (up): ip 168.11.123.201 dlci 501(0x1F5,0x7C50), dynamic,

broadcast,, status defined, active

Serial0 (up): ip 168.11.123.203 dlci 503(0x1F7,0x7C70), dynamic,

broadcast,, status defined, active

Building configuration...

Current configuration:

!

version 11.2

no service password-encryption

no service udp-small-servers

no service tcp-small-servers

!

hostname R3

!

enable secret 5 $1$kI1V$NkybGlP9tzP7BYvAKYT.c1

!

no ip domain-lookup

ipx routing 0200.cccc.cccc

!

interface Serial0

ip address 168.11.123.203 255.255.255.192

encapsulation frame-relay

ipx network 123

no fair-queue

frame-relay interface-dlci 501

frame-relay interface-dlci 502

!

interface Serial1

no ip address

encapsulation ppp

shutdown

clockrate 56000

!

interface Ethernet0

ip address 168.11.13.103 255.255.255.192

ipx network 130

ring-speed 16

!

router igrp 1

network 168.11.0.0

!

no ip classless

!

!

!

!

line con 0

password cisco

login

line aux 0

line vty 0 4

password cisco

login

!

end

Protocol Address Age (min) Hardware Addr Type Interface

Internet 168.11.13.103 - 0000.0c89.b1b0 SNAP Ethernet0

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default

U - per-user static route, o - ODR

Gateway of last resort is not set

168.11.0.0/26 is subnetted, 4 subnets

C 168.11.123.192 is directly connected, Serial0

I 168.11.11.64 [100/8539] via 168.11.123.201, 00:00:06, Serial0

C 168.11.13. 64 is directly connected, Ethernet0

I 168.11.12. 64 [100/8539] via 168.11.123.202, 00:00:46, Serial0

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 168.11.11.80, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 76/76/76 ms

Type escape sequence to abort.

Tracing the route to 168.11.11.80

1 168.11.123.201 44 msec 44 msec 44 msec

2 168.11.11.250 44 msec * 40 msec

Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail

3 Total IPX Servers

Table ordering is based on routing and server info

Type Name Net Address Port Route Hops Itf

P 4 Server1 101.0000.0000.0001:0451 8/03 3 Se0

P 4 Server2 102.0000.0000.0001:0451 8/03 3 Se0

P 4 Server3 103.0000.0000.0001:0451 2/02 2 E0

Serial0 (up): ipx 123.0200.aaaa.aaaa dlci 501(0x1F5,0x7C50), dynamic,

broadcast,, status defined, active

Serial0 (up): ipx 123.0200.bbbb.bbbb dlci 502(0x1F6,0x7C60), dynamic,

broadcast,, status defined, active

Using Example 9-12, Example 9-13, and Example 9-14 as references, answer the following

questions:

sent by a router?

with IPX RIP? What in the command output identifies these routing protocols?

provide the details of what is in the IGRP update?

configuration command(s) can be used to set the password that is required?

how can you get help to list all commands that start with D? List all steps; assume that you

are in privileged mode.

your configuration. Name the two commands that can be used.

mode from privileged mode, changing the host name from R1 to R2, and then getting back

to privileged mode.

how would the subnet mask information be entered?

Serial0 (up): ip 168.11.123.201 dlci 501(0x1F5,0x7C50), dynamic,

broadcast,, status defined, active

Serial0 (up): ip 168.11.123.202 dlci 502(0x1F6,0x7C60), dynamic,

broadcast,, status defined, active

LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = CISCO

Invalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0

Invalid Status Message 0 Invalid Lock Shift 0

Invalid Information ID 0 Invalid Report IE Len 0

Invalid Report Request 0 Invalid Keep IE Len 0

Num Status Enq. Sent 1677 Num Status msgs Rcvd 1677

Num Update Status Rcvd 0 Num Status Timeouts 0

routers continually, what stops the packet from rotating forever? Are any notification

messages sent when the routers notice what is happening? If so, what is the message(s)?

PC11 and PC21.

interfaces?

changes would be needed?

Relay interface?

The answers to the questions for Scenario 9-2, Part C are as follows:

Examples 9-5 and 9-6). The metric value for each IP subnet is the second of the two

numbers inside brackets. Two IPX metrics are located between brackets for IPX routes:

the number of timer ticks and the number of hops.

advertised because split horizon is disabled on the serial interface when no subinterfaces

are used.

dce-terminal-timing-enable default delay description dialer

dialer-group down-when-looped dspu dxi

R3#

could be used.

R2#

The most important part of this question is to realize that configuration changes are

mask. In this network, mask 255.255.255.192 implies 6 host bits. A Class B network is

used, which implies 16 network bits, leaving 10 subnet bits.

is decremented to 0, the router discards the packet. That router also sends an ICMP TTLexceeded

message to the host that originally sent the packet.

responsible for the TCP processing.

a common routing protocol, which consolidates routing updates.

used for Frame Relay. The Inverse ARP message is sent over the VC between the two

routers. R2 learns based on receiving the message.

are used, or if no subinterfaces are used, split horizon is off by default.

sent. No keepalive messages pass from router to router.

Part A of the final review scenario begins with some planning guidelines that include planning

IP addresses, IPX network numbers, the location of SAP filters, and the location of IP standard

access lists. After you complete Part A, Part B of Scenario 9-3 asks you to configure the three

routers to implement the planned design and a few other features. Finally, in Part C of Scenario

9-3, some errors have been introduced into the network, and you are asked to examine router

command output to find the errors. Part C of Scenario 9-3 also lists some questions relating to

the user interface and protocol specifications.

Your job is to deploy a new network with three sites, as shown in Figure 9-5. The decision to

use Frame Relay, as well as the product choices, has already been made. To complete Scenario

9-3, Part A, perform the following tasks:

been assigned by the NIC. The maximum number of hosts per subnet is 300. Assign IP

addresses to the PCs as well. Use Table 9-10 and Table 9-11 to record your answers.

of the servers as well. Each LAN should support both SAP and SNAP encapsulations.

anywhere else.

on the Ethernet off R2.

valid IP addresses in each subnet. Use Table 9-12, if convenient.

Ethernet off R1

Ethernet off R2

Ethernet off R3

Ethernet off R4

Virtual circuit between R1

and R2

Virtual circuit between R1

and R3

Virtual circuit between R1

and R4

Server 1 internal

Server 2 internal

Server 3 internal

PC11

PC12

PC21

PC31

PC32

PC41

PC42

R1-E0

R1-S0-sub ____

R1-S0-sub ____

R1-S0-sub ____

R2-E0

R2-S0-sub ____

R3-E0

R3-S0-sub ____

R4-E0

R4-S0-sub ____

Server 1

Server 2

Server 3

The IP subnet design includes the use of mask 255.255.254.0. The same mask is used

throughout the network, therefore at least 9 host bits are needed because at least one subnet

contains 300 hosts.

The IPX network number assignment process is straightforward when using multiple

encapsulations on the same Ethernet—you simply have to chose two different network

numbers, one per encapsulation type. Each encapsulation type on the router requires the use of

a separate IPX network. The subnets, networks, and IP addresses are recorded in Table 9-13 and

Table 9-14.

Ethernet off R1 255.255.254.0 170.1.2.0 2, 3

Ethernet off R2 255.255.254.0 170.1.4.0 4, 5

Ethernet off R3 255.255.254.0 170.1.6.0 6, 7

Ethernet off R4 255.255.254.0 170.1.8.0 8, 9

Virtual circuit between R1

and R2

255.255.254.0 170.1.10.0 10

Virtual circuit between R1

and R3

255.255.254.0 170.1.12.0 12

Virtual circuit between R1

and R4

255.255.254.0 170.1.14.0 14

Server 1 internal — — 101

The choice of IP addresses can conform to any standard you like, as long as the addresses are

in the correct subnets. Refer to Table 9-15 for the list of valid addresses for the subnets chosen.

In Table 9-14, a convention is used such that the numbers reflect the number of the PC. For the

routers, the convention uses addresses in the second half of the range of addresses in each

subnet; this convention is used simply as a reminder of the addresses that are valid in this

subnetting scheme.

Server 2 internal — — 102

Server 3 internal — — 103

PC11 170.1.2.11

PC12 170.1.2.12

PC21 170.1.4.21

PC31 170.1.6.31

PC32 170.1.6.32

PC41 170.1.8.41

PC42 170.1.8.42

R1-E0 170.1.3.1

R1-S0-sub __2__ 170.1.10.1

R1-S0-sub __3__ 170.1.12.1

R1-S0-sub __4__ 170.1.14.1

R2-E0 170.1.5.2

R2-S0-sub __2__ 170.1.10.2

R3-E0 170.1.7.3

R3-S0-sub __3__ 170.1.12.3

R4-E0 170.1.9.4

R4-S0-sub __4__ 170.1.14.4

Server 1 170.1.2.101

Server 2 170.1.2.102

Server 3 170.1.4.103

The IP access lists can be placed in several places effectively. Stopping packets in one of the

two directions will succeed in stopping users from actually connecting to the servers. For the

first set of criteria, an access list stopping packets from entering the serial interface of R1, thus

stopping packets destined to PC11 and PC12, will suffice. For the second criteria to disallow

traffic between Site 2 and Site 3, the access lists are also placed in R1. The access lists will stop

the packets earlier in their life if they are placed in R2 and R3, but the traffic will be minimal

because no true application traffic will ever successfully be generated between IP hosts at Sites

2 and 3.

So, the design shown here calls for all filtered packets to be filtered via access lists enabled on

subinterfaces on R1’s S0 interface. Other options are valid as well.

The SAP filter can be placed in several places, but there is one very obvious location. A SAP

filter is added on R2 to filter Server 3 from the SAP table. The filter could filter incoming SAPs

on R2’s E0 or filter outgoing SAP updates out R2’s S0 port. In this case, anticipating the day

that a second Ethernet port is used on R2, and anticipating the fact that the objective probably

meant that local clients should have access to Server 3, the plan in this case is to filter outbound

SAPs on R2’s S0 interface.

Finally, the broadcast addresses for each subnet are shown in Table 9-15. As a reminder, to

calculate the broadcast address, you should write down the subnet number in binary. Then copy

down the network and subnet portions of the subnet number directly below it, leaving the host

bit positions empty. Then write all binary 1s in the host bit positions. Finally, convert the

number back to decimal, 8 bits at a time. The result is the subnet broadcast address and is the

high end of the range of assignable addresses in that subnet.

Table 9-15 shows the answers, which include the subnet numbers, their corresponding

broadcast addresses, and the range of valid assignable IP addresses.

170.1.2.0 170.1.3.255 2.1 through 3.254

170.1.4.0 170.1.5.255 4.1 through 5.254

170.1.6.0 170.1.7.255 6.1 through 7.254

170.1.8.0 170.1.9.255 8.1 through 9.254

170.1.10.0 170.1.11.255 10.1 through 11.254

170.1.12.0 170.1.13.255 12.1 through 13.254

170.1.14.0 170.1.15.255 14.1 through 15.254

The next step in your job is to deploy the network designed in Scenario 9-3, Part A. Use the

solutions to Scenario 9-3, Part A to direct you in identifying IP and IPX addresses, access lists,

and the encapsulations to be used. For Scenario 9-3, Part B, perform the following tasks:

Use IGRP process-id 1.

described in Scenario 9-3, Part A.

switch uses LMI type ANSI. Cisco encapsulation should be used for all routers, except for

the VC between R1 and R4.

Examples 9-15 through 9-18 show the configurations for Tasks 1, 2, and 3 for Part B of

Scenario 3.

ipx routing 0200.aaaa.aaaa

!

interface serial0

encapsulation frame-relay

interface serial 0.2 point-to-point

ip address 170.1.10.1 255.255.254.0

ipx network 10

frame-relay interface-dlci 302

ip access-group 102 in

!

interface serial 0.3 point-to-point

ip address 170.1.12.1 255.255.254.0

ipx network 12

frame-relay interface-dlci 303

ip access-group 103 in

!

interface serial 0.4 point-to-point

ip address 170.1.14.1 255.255.254.0

ipx network 14

frame-relay interface-dlci 304 ietf

ip access-group 104 in

!

interface ethernet 0

ip address 170.1.3.1 255.255.254.0

ipx network 2 encapsulation sap

ipx network 3 encapsulation snap secondary

!

router igrp 1

network 170.1.0.0

!

access-list 102 permit tcp any host 170.1.2.11 eq ftp

access-list 102 permit tcp any host 170.1.2.11 eq www

access-list 102 permit tcp any host 170.1.2.12 eq ftp

access-list 102 permit tcp any host 170.1.2.12 eq www

access-list 102 deny ip any host 170.1.2.11

access-list 102 deny ip any host 170.1.2.12

access-list 102 deny ip 170.1.4.0 0.0.1.255 170.1.6.0 0.0.1.255

access-list 102 permit ip any any

access-list 103 permit tcp any host 170.1.2.11 eq ftp

access-list 103 permit tcp any host 170.1.2.11 eq www

access-list 103 permit tcp any host 170.1.2.12 eq ftp

access-list 103 permit tcp any host 170.1.2.12 eq www

access-list 103 deny ip any host 170.1.2.11

access-list 103 deny ip any host 170.1.2.12

access-list 103 deny ip 170.1.6.0 0.0.1.255 170.1.4.0 0.0.1.255

access-list 103 permit ip any any

access-list 104 permit tcp any host 170.1.2.11 eq ftp

access-list 104 permit tcp any host 170.1.2.11 eq www

access-list 104 permit tcp any host 170.1.2.12 eq ftp

access-list 104 permit tcp any host 170.1.2.12 eq www

access-list 104 deny ip any host 170.1.2.11

access-list 104 deny ip any host 170.1.2.12

access-list 104 permit ip any any

ipx routing 0200.bbbb.bbbb

!

interface serial0

encapsulation frame-relay

interface serial 0.1 point-to-point

ip address 170.1.10.2 255.255.254.0

ipx network 10

frame-relay interface-dlci 301

ipx output-sap-filter 1001

!

interface ethernet 0

ip address 170.1.5.2 255.255.254.0

ipx network 4 encapsulation sap

ipx network 5 encapsulation snap secondary

!

router igrp 1

network 170.1.0.0

!

access-list 1001 deny 103

access-list 1001 permit -1

Three different access lists are shown on R1. List 102 is used for packets entering subinterface

2. List 103 is used for packets entering subinterface 3, and list 104 is used for packets entering

subinterface 4. Lists 102 and 103 check for packets between sites 2 and 3, and they also check

for packets to PC11 and PC12. The mask used to check all hosts in subnets 170.1.4.0 and

170.1.6.0 is rather tricky. The mask represents 23 binary 0s and 9 binary 1s, meaning that the

first 23 bits of the number in the access list must match the first 23 bits in the source or

destination address in the packet. This matches all hosts in each subnet because there are 23

combined network and subnet bits.

Two IPX networks are used on each Ethernet because two encapsulations are used.

ipx routing 0200.cccc.cccc

!

interface serial0

encapsulation frame-relay

interface serial 0.1 point-to-point

ip address 170.1.12.3 255.255.254.0

ipx network 12

frame-relay interface-dlci 301

!

interface ethernet 0

ip address 170.1.7.3 255.255.254.0

ipx network 6 encapsulation sap

ipx network 7 encapsulation snap secondary

!

router igrp 1

network 170.1.0.0

ipx routing 0200.dddd.dddd

!

interface serial0

encapsulation frame-relay ietf

interface serial 0.1 point-to-point

ip address 170.1.14.4 255.255.254.0

ipx network 14

frame-relay interface-dlci 301

!

interface ethernet 0

ip address 170.1.9.4 255.255.254.0

ipx network 8 encapsulation sap

ipx network 9 encapsulation snap secondary

!

router igrp 1

network 170.1.0.0

The Frame Relay configuration was relatively straightforward. The LMI type is autosensed.

The CCNA exam tests your memory of the kinds of information you can find in the output of

questions following the examples.

Interface IP-Address OK? Method Status Protocol

Serial0 unassigned YES unset up up

Serial0.2 170.1.10.1 YES NVRAM up up

Serial0.3 170.1.12.1 YES NVRAM up up

Serial0.4 170.1.14.1 YES NVRAM up up

Serial1 unassigned YES unset administratively down down

Ethernet0 170.1.3.1 YES NVRAM up up

-------------------------

Device ID: R2

Entry address(es):

IP address: 170.1.10.2

Novell address: 10.0200.bbbb.bbbb

Platform: cisco 2500, Capabilities: Router

Interface: Serial0.2, Port ID (outgoing port): Serial0.1

Holdtime : 132 sec

Version :

Cisco Internetwork Operating System Software

IOS (tm) 2500 Software (C2500-AINR-L), Version 11.2(11), RELEASE SOFTWARE (fc1)

Copyright 1986-1997 by Cisco Systems, Inc.

Compiled Mon 29-Dec-97 18:47 by ckralik

-------------------------

Device ID: R3

Entry address(es):

IP address: 170.1.12.3

Novell address: 12.0200.cccc.cccc

Platform: Cisco 2500, Capabilities: Router

Interface: Serial0.3, Port ID (outgoing port): Serial0.1

Holdtime : 148 sec

Version :

Cisco Internetwork Operating System Software

IOS (tm) 2500 Software (C2500-AINR-L), Version 11.2(11), RELEASE SOFTWARE (fc1)

Copyright 1986-1997 by Cisco Systems, Inc.

Compiled Mon 29-Dec-97 18:47 by ckralik

-------------------------

Device ID: R4

Entry address(es):

IP address: 170.1.14.4

Novell address: 14.0200.dddd.dddd

Platform: Cisco 2500, Capabilities: Router

Interface: Serial0.4, Port ID (outgoing port): Serial0.1

Holdtime : 149 sec

Version :

Cisco Internetwork Operating System Software

IOS (tm) 2500 Software (C2500-AINR-L), Version 11.2(11), RELEASE SOFTWARE (fc1)

Copyright 1986-1997 by Cisco Systems, Inc.

Compiled Mon 29-Dec-97 18:47 by ckralik

Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail

2 Total IPX Servers

Table ordering is based on routing and server info

Type Name Net Address Port Route Hops Itf

P 4 Server1 101.0000.0000.0001:0451 2/02 2 E0

P 4 Server2 102.0000.0000.0001:0451 2/02 2 E0

R1#

IPX service debugging is on

R1#

IPXSAP: positing update to 2.ffff.ffff.ffff via Ethernet0 (broadcast) (full)

IPXSAP: suppressing null update to 2.ffff.ffff.ffff

IPXSAP: positing update to 3.ffff.ffff.ffff via Ethernet0 (broadcast) (full)

IPXSAP: Update type 0x2 len 160 src:3.0000.0ccf.21cd dest:3.ffff.ffff.ffff(452)

type 0x4, “Server2“, 102.0000.0000.0001(451), 3 hops

type 0x4, “Server1“, 101.0000.0000.0001(451), 3 hops

IPXSAP: Response (in) type 0x2 len 160 src:2.0000.0c89.b130

dest:2.ffff.ffff.ffff(452)

type 0x4, “Server1“, 101.0000.0000.0001(451), 2 hops

type 0x4, “Server2“, 102.0000.0000.0001(451), 2 hops

IPXSAP: positing update to 10.ffff.ffff.ffff via Serial0.2 (broadcast) (full)

IPXSAP: Update type 0x2 len 160 src:10.0200.aaaa.aaaa dest:10.ffff.ffff.ffff(452)

type 0x4, “Server2“, 102.0000.0000.0001(451), 3 hops

type 0x4, “Server1“, 101.0000.0000.0001(451), 3 hops

IPXSAP: positing update to 14.ffff.ffff.ffff via Serial0.4 (broadcast) (full)

IPXSAP: Update type 0x2 len 160 src:14.0200.aaaa.aaaa dest:14.ffff.ffff.ffff(452)

type 0x4, “Server2“, 102.0000.0000.0001(451), 3 hops

type 0x4, “Server1“, 101.0000.0000.0001(451), 3 hops

IPXSAP: positing update to 12.ffff.ffff.ffff via Serial0.3 (broadcast) (full)

IPXSAP: Update type 0x2 len 160 src:12.0200.aaaa.aaaa dest:12.ffff.ffff.ffff(452)

type 0x4, “Server2“, 102.0000.0000.0001(451), 3 hops

type 0x4, “Server1“, 101.0000.0000.0001(451), 3 hops

All possible debugging has been turned off

R1#

IPX routing debugging is on

R1#

IPXRIP: update from 12.0200.cccc.cccc

7 in 1 hops, delay 7

6 in 1 hops, delay 7

IPXRIP: positing full update to 14.ffff.ffff.ffff via Serial0.4 (broadcast)

IPXRIP: src=14.0200.aaaa.aaaa, dst=14.ffff.ffff.ffff, packet sent

network 4, hops 2, delay 13

network 5, hops 2, delay 13

network 103, hops 4, delay 14

network 10, hops 1, delay 7

network 6, hops 2, delay 13

network 7, hops 2, delay 13

network 3, hops 1, delay 7

network 2, hops 1, delay 7

network 101, hops 3, delay 8

network 102, hops 3, delay 8

network 12, hops 1, delay 7

IPXRIP: positing full update to 12.ffff.ffff.ffff via Serial0.3 (broadcast)

IPXRIP: src=12.0200.aaaa.aaaa, dst=12.ffff.ffff.ffff, packet sent

network 8, hops 2, delay 13

network 9, hops 2, delay 13

network 14, hops 1, delay 7

network 4, hops 2, delay 13

network 5, hops 2, delay 13

network 103, hops 4, delay 14

network 10, hops 1, delay 7

network 3, hops 1, delay 7

network 2, hops 1, delay 7

network 101, hops 3, delay 8

network 102, hops 3, delay 8

IPXRIP: update from 14.0200.dddd.dddd

9 in 1 hops, delay 7

8 in 1 hops, delay 7

IPXRIP: update from 10.0200.bbbb.bbbb

444 in 2 hops, delay 8

103 in 3 hops, delay 8

5 in 1 hops, delay 7

4 in 1 hops, delay 7

IPXRIP: positing full update to 3.ffff.ffff.ffff via Ethernet0 (broadcast)

IPXRIP: src=3.0000.0ccf.21cd, dst=3.ffff.ffff.ffff, packet sent

network 8, hops 2, delay 8

network 9, hops 2, delay 8

network 14, hops 1, delay 2

network 4, hops 2, delay 8

network 5, hops 2, delay 8

network 103, hops 4, delay 9

network 10, hops 1, delay 2

network 6, hops 2, delay 8

network 7, hops 2, delay 8

network 2, hops 1, delay 2

network 101, hops 3, delay 3

network 102, hops 3, delay 3

network 12, hops 1, delay 2

IPXRIP: update from 2.0000.0c89.b130

102 in 2 hops, delay 2

101 in 2 hops, delay 2

IPXRIP: positing full update to 2.ffff.ffff.ffff via Ethernet0 (broadcast)

IPXRIP: src=2.0000.0ccf.21cd, dst=2.ffff.ffff.ffff, packet sent

network 8, hops 2, delay 8

network 9, hops 2, delay 8

network 14, hops 1, delay 2

network 4, hops 2, delay 8

network 5, hops 2, delay 8

network 103, hops 4, delay 9

network 10, hops 1, delay 2

network 6, hops 2, delay 8

network 7, hops 2, delay 8

network 3, hops 1, delay 2

network 12, hops 1, delay 2

IPXRIP: positing full update to 10.ffff.ffff.ffff via Serial0.2 (broadcast)

IPXRIP: src=10.0200.aaaa.aaaa, dst=10.ffff.ffff.ffff, packet sent

network 8, hops 2, delay 13

network 9, hops 2, delay 13

network 14, hops 1, delay 7

network 6, hops 2, delay 13

network 7, hops 2, delay 13

network 3, hops 1, delay 7

network 2, hops 1, delay 7

network 101, hops 3, delay 8

network 102, hops 3, delay 8

network 12, hops 1, delay 7

R1#

All possible debugging has been turned off

R1#

IGRP protocol debugging is on

R1#

IGRP: received update from 170.1.14.4 on Serial0.4

subnet 170.1.8.0, metric 8539 (neighbor 688)

IGRP: sending update to 255.255.255.255 via Serial0.2 (170.1.10.1)

subnet 170.1.8.0, metric=8539

subnet 170.1.14.0, metric=8476

subnet 170.1.12.0, metric=8476

subnet 170.1.2.0, metric=688

subnet 170.1.6.0, metric=8539

IGRP: sending update to 255.255.255.255 via Serial0.3 (170.1.12.1)

subnet 170.1.10.0, metric=8476

subnet 170.1.8.0, metric=8539

subnet 170.1.14.0, metric=8476

subnet 170.1.2.0, metric=688

subnet 170.1.4.0, metric=8539

IGRP: sending update to 255.255.255.255 via Serial0.4 (170.1.14.1)

subnet 170.1.10.0, metric=8476

subnet 170.1.12.0, metric=8476

subnet 170.1.2.0, metric=688

subnet 170.1.6.0, metric=8539

subnet 170.1.4.0, metric=8539

IGRP: sending update to 255.255.255.255 via Ethernet0 (170.1.3.1)

subnet 170.1.10.0, metric=8476

subnet 170.1.8.0, metric=8539

subnet 170.1.14.0, metric=8476

subnet 170.1.12.0, metric=8476

subnet 170.1.6.0, metric=8539

subnet 170.1.4.0, metric=8539

IGRP: received update from 170.1.10.2 on Serial0.2

subnet 170.1.4.0, metric 8539 (neighbor 688)

IGRP: received update from 170.1.12.3 on Serial0.3

subnet 170.1.6.0, metric 8539 (neighbor 688)

R1#

All possible debugging has been turned off

Serial0 is up, line protocol is up

Hardware is HD64570

MTU 1500 bytes, BW 56 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)

LMI enq sent 144, LMI stat recvd 138, LMI upd recvd 0, DTE LMI up

LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0

LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE

Broadcast queue 0/64, broadcasts sent/dropped 73/0, interface broadcasts 48

Last input 00:00:04, output 00:00:04, output hang never

Last clearing of “show interface” counters never

Input queue: 0/75/0 (size/max/drops); Total output drops: 0

Queuing strategy: weighted fair

Output queue: 0/1000/0 (size/max total/drops)

Conversations 0/1/64 (active/max active/threshold)

Reserved Conversations 0/0 (allocated/max allocated)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

232 packets input, 17750 bytes, 0 no buffer

Received 1 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

225 packets output, 12563 bytes, 0 underruns

0 output errors, 0 collisions, 4 interface resets

0 output buffer failures, 0 output buffers swapped out

12 carrier transitions

DCD=up DSR=up DTR=up RTS=up CTS=up

--More--

Serial0.1 is up, line protocol is up

Hardware is HD64570

Internet address is 170.1.10.2/23

MTU 1500 bytes, BW 56 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation FRAME-RELAY

--More--

Serial1 is administratively down, line protocol is down

Hardware is HD64570

MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255

Encapsulation PPP, loopback not set, keepalive set (10 sec)

LCP Closed

Closed: CDPCP, LLC2

Last input never, output never, output hang never

Last clearing of “show interface” counters never

Input queue: 0/75/0 (size/max/drops); Total output drops: 0

Queuing strategy: weighted fair

Output queue: 0/1000/0 (size/max total/drops)

Conversations 0/0/64 (active/max active/threshold)

Reserved Conversations 0/0 (allocated/max allocated)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

0 packets input, 0 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

0 packets output, 0 bytes, 0 underruns

0 output errors, 0 collisions, 5 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier transitions

DCD=down DSR=down DTR=down RTS=down CTS=down

--More--

Ethernet0 is up, line protocol is up

Hardware is TMS380, address is 0000.0c89.b170 (bia 0000.0c89.b170)

Internet address is 170.1.5.2/23

MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255

Encapsulation ARPA, loopback not set, keepalive set (10 sec)

ARP type: ARPA, ARP Timeout 4:00:00

Last input 00:00:00, output 00:00:01, output hang never

Last clearing of “show interface” counters never

Queuing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

583 packets input, 28577 bytes, 0 no buffer

Received 486 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

260 packets output, 31560 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 output buffer failures, 0 output buffers swapped out

6 transitions

Interface IPX Network Encapsulation Status IPX State

Serial0 unassigned not config’d up n/a

Serial0.1 10 FRAME-RELAY up [up]

Serial1 unassigned not config’d administratively down n/a

Ethernet0 4 SAP up [up]

Ethernet0 5 SNAP up [up]

R2#

Codes: C - Connected primary network, c - Connected secondary network

S - Static, F - Floating static, L - Local (internal), W - IPXWAN

R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate

s - seconds, u - uses

14 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.

No default route known.

C 4 (SAP), E0

c 5 (SNAP), E0

C 10 (FRAME-RELAY), Se0.1

R 2 [07/01] via 10.0200.aaaa.aaaa, 47s, Se0.1

R 3 [07/01] via 10.0200.aaaa.aaaa, 48s, Se0.1

R 6 [13/02] via 10.0200.aaaa.aaaa, 48s, Se0.1

R 7 [13/02] via 10.0200.aaaa.aaaa, 48s, Se0.1

R 8 [13/02] via 10.0200.aaaa.aaaa, 48s, Se0.1

R 9 [13/02] via 10.0200.aaaa.aaaa, 48s, Se0.1

R 12 [07/01] via 10.0200.aaaa.aaaa, 48s, Se0.1

R 14 [07/01] via 10.0200.aaaa.aaaa, 48s, Se0.1

R 101 [08/03] via 10.0200.aaaa.aaaa, 48s, Se0.1

R 102 [08/03] via 10.0200.aaaa.aaaa, 48s, Se0.1

R 103 [02/02] via 4.0000.0cac.70ef, 42s, E0

Translating “14.0200.dddd.dddd“

Type escape sequence to abort.

Sending 5, 100-byte IPX Cisco Echoes to 14.0200.dddd.dddd, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 140/144/148 ms

Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail

3 Total IPX Servers

Table ordering is based on routing and server info

Type Name Net Address Port Route Hops Itf

P 4 Server3 103.0000.0000.0001:0451 2/02 2 E0

P 4 Server1 101.0000.0000.0001:0451 8/03 3 Se0.1

P 4 Server2 102.0000.0000.0001:0451 8/03 3 Se0.1

PVC Statistics for interface Serial0 (Frame Relay DTE)

DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.1

input pkts 102 output pkts 82 in bytes 16624

out bytes 11394 dropped pkts 0 in FECN pkts 0

in BECN pkts 0 out FECN pkts 0 out BECN pkts 0

in DE pkts 0 out DE pkts 0

out bcast pkts 76 out bcast bytes 10806

pvc create time 00:25:09, last time pvc status changed 00:23:15

LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = ANSI

Invalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0

Invalid Status Message 0 Invalid Lock Shift 0

Invalid Information ID 0 Invalid Report IE Len 0

Invalid Report Request 0 Invalid Keep IE Len 0

Num Status Enq. Sent 151 Num Status msgs Rcvd 145

Num Update Status Rcvd 0 Num Status Timeouts 7

R2#

Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail

2 Total IPX Servers

Table ordering is based on routing and server info

Type Name Net Address Port Route Hops Itf

P 4 Server1 101.0000.0000.0001:0451 8/03 3 Se0.1

P 4 Server2 102.0000.0000.0001:0451 8/03 3 Se0.1

Protocol Address Age (min) Hardware Addr Type Interface

Internet 170.1.7.3 - 0000.0c89.b1b0 SNAP Ethernet0

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default

U - per-user static route, o - ODR

Gateway of last resort is not set

170.1.0.0/23 is subnetted, 7 subnets

I 170.1.10.0 [100/10476] via 170.1.12.1, 00:00:57, Serial0.1

I 170.1.8.0 [100/10539] via 170.1.12.1, 00:00:57, Serial0.1

I 170.1.14.0 [100/10476] via 170.1.12.1, 00:00:57, Serial0.1

C 170.1.12.0 is directly connected, Serial0.1

I 170.1.2.0 [100/8539] via 170.1.12.1, 00:00:57, Serial0.1

C 170.1.6.0 is directly connected, Ethernet0

I 170.1.4.0 [100/10539] via 170.1.12.1, 00:00:57, Serial0.1

Type escape sequence to abort.

Tracing the route to 170.1.9.4

1 170.1.12.1 40 msec 40 msec 44 msec

2 170.1.14.4 80 msec * 80 msec

Type escape sequence to abort.

Tracing the route to 170.1.5.2

1 170.1.12.1 40 msec 40 msec 40 msec

2 170.1.10.2 72 msec * 72 msec

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 170.1.5.2, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 136/136/140 ms

Protocol [ip]:

Target IP address: 170.1.5.2

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: 170.1.7.3

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 170.1.5.2, timeout is 2 seconds:

UUUUU

Success rate is 0 percent (0/5)

LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = CISCO

Invalid Unnumbered info 0 Invalid Prot Disc 0

Invalid dummy Call Ref 0 Invalid Msg Type 0

Invalid Status Message 0 Invalid Lock Shift 0

Invalid Information ID 0 Invalid Report IE Len 0

Invalid Report Request 0 Invalid Keep IE Len 0

Num Status Enq. Sent 172 Num Status msgs Rcvd 172

Num Update Status Rcvd 0 Num Status Timeouts 0

Serial0.1 (up): point-to-point dlci, dlci 301(0x12D,0x48D0), broadcast

status defined, active

Interface IP-Address OK? Method Status Protocol

Serial0 unassigned YES unset up up

Serial0.1 170.1.14.4 YES NVRAM up up

Serial1 unassigned YES unset administratively down down

Ethernet0 170.1.9.4 YES NVRAM up up

Interface IPX Network Encapsulation Status IPX State

Serial0 unassigned not config’d up n/a

Serial0.1 14 FRAME-RELAY up [up]

Serial1 unassigned not config’d administratively down n/a

Ethernet0 8 SAP up [up]

Ethernet0 9 SNAP up [up]

Codes: S - Static, P - Periodic, E - EIGRP, N - NLSP, H - Holddown, + = detail

2 Total IPX Servers

Table ordering is based on routing and server info

Type Name Net Address Port Route Hops Itf

P 4 Server1 101.0000.0000.0001:0451 8/03 3 Se0.1

P 4 Server2 102.0000.0000.0001:0451 8/03 3 Se0.1

Codes: C - Connected primary network, c - Connected secondary network

S - Static, F - Floating static, L - Local (internal), W - IPXWAN

R - RIP, E - EIGRP, N - NLSP, X - External, A - Aggregate

s - seconds, u - uses

14 Total IPX routes. Up to 1 parallel paths and 16 hops allowed.

No default route known.

C 8 (SAP), E0

c 9 (SNAP), E0

C 14 (FRAME-RELAY), Se0.1

R 2 [07/01] via 14.0200.aaaa.aaaa, 33s, Se0.1

Using Examples 9-19 through 9-22 as references, answer the following questions:

Why was it successful if the access lists in R1 are enabled as shown in its configuration?

described?

of R1?

R 3 [07/01] via 14.0200.aaaa.aaaa, 34s, Se0.1

R 4 [13/02] via 14.0200.aaaa.aaaa, 34s, Se0.1

R 5 [13/02] via 14.0200.aaaa.aaaa, 34s, Se0.1

R 6 [13/02] via 14.0200.aaaa.aaaa, 34s, Se0.1

R 7 [13/02] via 14.0200.aaaa.aaaa, 34s, Se0.1

R 10 [07/01] via 14.0200.aaaa.aaaa, 34s, Se0.1

R 12 [07/01] via 14.0200.aaaa.aaaa, 34s, Se0.1

R 101 [08/03] via 14.0200.aaaa.aaaa, 34s, Se0.1

R 102 [08/03] via 14.0200.aaaa.aaaa, 34s, Se0.1

R 103 [14/04] via 14.0200.aaaa.aaaa, 34s, Se0.1

-------------------------

Device ID: R1

Entry address(es):

IP address: 170.1.14.1

Novell address: 14.0200.aaaa.aaaa

Platform: Cisco 2500, Capabilities: Router

Interface: Serial0.1, Port ID (outgoing port): Serial0.4

Holdtime : 178 sec

Version :

Cisco Internetwork Operating System Software

IOS (tm) 2500 Software (C2500-AINR-L), Version 11.2(11), RELEASE SOFTWARE (fc1)

Copyright 1986-1997 by Cisco Systems, Inc.

Compiled Mon 29-Dec-97 18:47 by ckralik

PVC Statistics for interface Serial0 (Frame Relay DTE)

DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0.1

input pkts 85 output pkts 63 in bytes 14086

out bytes 8464 dropped pkts 0 in FECN pkts 0

in BECN pkts 0 out FECN pkts 0 out BECN pkts 0

in DE pkts 0 out DE pkts 0

out bcast pkts 53 out bcast bytes 7614

pvc create time 00:18:40, last time pvc status changed 00:18:40

networks?

router?

the user mode command prompt?

steps to do so, taking the least amount of keystrokes.

taking the least amount of keystrokes.

affected?

to R1?

other end of the PVC in this network?

match?

logging in to that router?

The answers to the questions for Scenario 9-3, Part C are as follows:

packet, which in this case would be 170.1.12.3. Access lists 102 and 103 check the source

and destination IP addresses, looking for the subnets on the Ethernet segments. Therefore,

source IP address 170.1.7.3 (R3’s E0 IP address), and see that it fails. That’s because the

simply shows that the SAP filter on R2 is working properly.

the IP and IPX addresses of the neighboring routers. Because only point-to-point

IPX addresses.

a C in the left column signify connected subnets.

Examples 9-21 and 9-20, respectively). The metric value for each IP subnet is the second

of the two numbers inside brackets. Two IPX metrics are located between brackets for IPX

routes: the number of timer ticks and the number of hops.

network layer (Layer 3) protocols (refer to Example 9-21).

on the command line. Press Enter.

IOS. The file is placed into the default directory on some TFTP server accessible to the

questions to tell the router the name and location of the new IOS. Flash memory is updated

as a result of this process. The new IOS is not used until the router is reloaded.

TCP provides error recovery.

subinterface; therefore, R2 can learn of R1’s IP and IPX addresses only with CDP, or by

looking at the source addresses of the IPX RIP and IP IGRP routing updates.

defined, with a 10-bit number being the most typically implemented size.

misdirection that you might expect to see on some of the exam questions. Read the

questions slowly, and read them twice.

see the addresses in either case.

PRI stands for Primary Rate Interface.

points. S and T are combined in many cases and together are called the S/T reference

point.

to OSI Layer 3.