4e_02_5_1_ppp

Procedural Lab Template, Student Version, Required Components

CCNA ExplorationAccessing the WAN: PPP

Lab 2.5.1: Basic PPP Configuration Lab

Lab 2.5.1: Basic PPP Configuration Lab (Instructor Version) Sthnte si lohu4e_02_5_1_ppp.pdfz

http://skola.bernkopf.czOdkaz Pedmty Cisco Materily lohy

Vypracujte podle pipojench pokyn.

Navc do kadho smrovae (router) a pepnae (switch) vlote hlku, kter se vype pi kadm pihlen.

Pouijte pkaz banner login, hlka bude Vae pjmen bez diakritiky, tj. napklad Pechacek msto Pechek.

Vsledn soubor pojmenujte 4e_02_5_1_ppp_Prijmeni.pkt, kde Prijmeni je Vae pjmen bez diakritiky.

Soubor zalete e-mailem do plnoci nedle 23. nora na adresu [email protected] .

Topology Diagram

Addressing Table

DeviceInterfaceIP AddressSubnet MaskDefault Gateway

R1Fa0/1192.168.10.1255.255.255.0N/A

S0/0/010.1.1.1255.255.255.252N/A

R2Lo0209.165.200.225255.255.255.224N/A

S0/0/010.1.1.2255.255.255.252N/A

S0/0/110.2.2.1255.255.255.252N/A

R3Fa0/1192.168.30.1255.255.255.0N/A

S0/0/110.2.2.2255.255.255.252N/A

PC1NIC192.168.10.10255.255.255.0192.168.10.1

PC3NIC192.168.30.10255.255.255.0192.168.30.1

Objectives Basic configuration tasks on a router. Configure and activate interfaces. Configure OSPF routing. Configure PPP encapsulation. Learn how to change the encapsulation on the serial interfaces from PPP to HDLC. Intentionally break and restore PPP encapsulation. Configure PPP PAP and CHAP authentication. Intentionally break and restore PPP PAP and CHAP authentication.Task 1: Prepare the Network

Step 1: Cable the network.

You can use any router as long as it has the required interfaces. Tady nm neekli, s m to dlali oni. Vyberte takov router, kter bude mt stejn oznaen sriovch rozhran, nap. 0/0/0.Step 2: Clear any existing configurations on the routers.

Task 2: Perform Basic Router Configuration

Configure the R1, R2, and R3 routers according to the following guidelines:

Configure the router hostname.

Disable DNS lookup.

Configure an EXEC mode password.

Configure a password for console connections. Configure synchronous logging. Configure a password for vty connections.enableconfigure terminalno ip domain-lookupenable secret class!!line con 0 exec-timeout 0 0 logging synchronous password cisco login!line vty 0 4password ciscologinendcopy running-config starting-configTask 3: Configure and Activate Serial and Ethernet Addresses

Step 1: Configure interfaces on R1, R2, and R3.

Configure the interfaces on the routers with the given IP addresses. Include the clock rate on the serial DCE interfaces.R1!

interface FastEthernet0/1

ip address 192.168.10.1 255.255.255.0

no shutdown

!

interface Serial0/0/0

ip address 10.1.1.1 255.255.255.252

no shutdown

clock rate 64000

R2

!

interface Loopback0

ip address 209.165.200.225 255.255.255.224

!

!


ip address 10.1.1.2 255.255.255.252

no shutdown

!


ip address 10.2.2.1 255.255.255.252

clock rate 64000

no shutdown

R3

!

interface FastEthernet0/1

ip address 192.168.30.1 255.255.255.0

no shutdown

!


ip address 10.2.2.2 255.255.255.252

no shutdown

Step 2: Verify IP addressing and interfaces.

Use the show ip interface brief command to verify that the IP addressing is correct and that the interfaces are active. Save the running configuration to the NVRAM.

Step 3: Configure the Ethernet interfaces of PC1 and PC3.

Configure the Ethernet interfaces of PC1 and PC3 with the given IP addresses and default gateways.

Step 4: Test the configuration by pinging the default gateway from the PC.

Task 4: Configure OSPF on the Routers

Step 1: Enable OSPF routing on R1, R2, and R3.

Use the router ospf command with a process ID of 1. Be sure to advertise the networks.

R1(config)#router ospf 1R1(config-router)#network 192.168.10.0 0.0.0.255 area 0R1(config-router)#network 10.1.1.0 0.0.0.3 area 0

R2(config)#router ospf 1R2(config-router)#network 10.1.1.0 0.0.0.3 area 0R2(config-router)#network 10.2.2.0 0.0.0.3 area 0R2(config-router)#network 209.165.200.224 0.0.0.31 area 0

R3(config)#router ospf 1R3(config-router)#network 10.2.2.0 0.0.0.3 area 0R3(config-router)#network 192.168.30.0 0.0.0.255 area 0Step 2: Verify that you have full network connectivity.

Use the show ip route and ping commands to verify connectivity.

Task 5: Configure PPP Encapsulation on Serial InterfacesStep 1: Use the show interface command to check whether HDLC is the default serial encapsulation.

R1#show interface serial0/0/0

Serial0/0/0 is up, line protocol is up

Hardware is GT96K Serial

Internet address is 10.1.1.1/30

MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation HDLC, loopback not set... a stejn na rozhranch R2, R3.Step 2: VynechnoStep 3: Change the encapsulation of the serial interfaces mezi R1 a R2 from HDLC to PPP.

Hlavn rozdly mezi HDLC a PPP

PPP m ovovn totonosti (authentication), HDLC ne.

PPP nen Cisco proprietary => funguje i na neCisco zazench.

Change the encapsulation type on the link between R1 and R2, and observe the effects.

R1(config)#interface serial 0/0/0R1(config-if)#encapsulation pppR2(config)#interface serial 0/0/0R2(config-if)#encapsulation ppp

What happens when one end of the serial link is encapsulated with PPP and the other end of the link is encapsulated with HDLC? Me to fungovat s HDLC na jedn stran, PPP na druh?_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________The link goes down, and the OSPF adjacency is broken. PPP keeps trying to establish a connection with the opposite end of the link. However, because it keeps receiving a non-NCP packet, it discards the packet and does not bring the link up.

What happens when PPP encapsulation is configured on each end of the serial link? Co se stane, kdy dme PPP na oba konce?_____________________________________________________________________

_____________________________________________________________________The link comes up, and the OSPF adjacency is restored.

Step 4: VynechnoStep 5: Change the encapsulation from HDLC to PPP on both ends of the serial link between R2 and R3.

When does the line protocol on the serial link come up and the OSPF adjacency is restored? Kdy linkov protokol oije a sousedsk vztahy protokolu OSPF se obnov?_____________________________________________________________________

_____________________________________________________________________

Only after both ends of the serial link are encapsulated with PPP.

Step 6: Verify that PPP is now the encapsulation on the serial interfaces.R1#show interface serial0/0/0Serial0/0/0 is up, line protocol is up

Hardware is GT96K Serial

Internet address is 10.1.1.1/30

MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation PPP, LCP Open

Open: CDPCP, IPCP, loopback not set... stejn na ostatnch rozhranch ostatnch smrova.Task 6: Break and Restore PPP Encapsulation

By intentionally breaking PPP encapsulation, you will learn about the error messages that are generated.Kdy si zkusme, co to udl, kdy to mme schvln patn nastaven, nebudeme pekvapeni, a to budeme mt patn neschvln.Step 1: Return both serial interfaces on R2 to their default HDLC encapsulation.

R2(config)#interface serial 0/0/0R2(config-if)#encapsulation hdlc

Why is it useful to intentionally break a configuration? Pro je uiten schvln si to zkusit?_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________By seeing the ways in which you can intentionally break a protocol it will help you see the ways in which you could unintentionally break a protocol. You will find this very helpful when you have to solve the problems in the Troubleshooting lab.

Why do both serial interfaces go down, come back up, and then go back down?

Pro jdou sriov rozhran dol, znovu nahoru, a nakonec definitivn dol?

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________The interfaces initially go down because they have mismatched encapsulation types. The interfaces then come back up so that they can seek to reestablish a connection. When the interfaces are unable to successfully re-establish a connection, they go back down.

Can you think of another way to change the encapsulation of a serial interface from PPP to the default HDLC encapsulation other than using the encapsulation hdlc command? (Hint: It has to do with the no command.) Jak jinak by se dalo pejt z PPP na HDLC? (Bude tam njak no pkaz)

_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

R2(config)#interface serial 0/0/0

R2(config-if)#no encapsulation ppp

R2(config-if)#interface serial 0/0/1

R2(config-if)#no encapsulation ppp

Protoe HDLC je na zazench Cisco default, sta jen zruit PPP.

Step 2: Return both serial interfaces on R2 to PPP encapsulation.

R2(config)#interface s0/0/0

R2(config-if)#encapsulation pppR2(config-if)#interface s0/0/1R2(config-if)#encapsulation pppTask 7: Configure PPP Authentication

Step 1: Configure PPP PAP authentication on the serial link between R1 and R2.

R1(config)#username R1 password cisco ;mluv jen s tm, kdo ti pole tuto kombinaciR1(config)#int s0/0/0R1(config-if)#ppp authentication papR1(config-if)#ppp pap sent-username R2 password cisco; a ty na druhou stranu poslej zase tuto kombinaciWhat happens when PPP PAP authentication is only configured on one end of the serial link? Co kdy ovovn nastavme jen na jedn stran?_____________________________________________________________________

_____________________________________________________________________

The line protocol on interface serial 0/0/0 goes down, and the OSPF adjacency goes into a DOWN state.

R2(config)#username R2 password ciscoR2(config)#interface Serial0/0/0R2(config-if)#ppp authentication papR2(config-if)#ppp pap sent-username R1 password cisco

What happens when PPP PAP authentication is configured on both ends of the serial link? A co kdy to nastavme sprvn na obou stranch?_____________________________________________________________________

_____________________________________________________________________

The line protocol on interface serial 0/0/0 comes up, and the OSPF adjacency is established.

Step 2: Configure PPP CHAP authentication on the serial link between R2 and R3.

In PAP authentication, the password is not encrypted. While this is certainly better than no authentication at all, it is still highly preferable to encrypt the password that is being sent across the link. CHAP encrypts the password. Na rozdl od PAP (ve), ovovn CHAP ifruje heslo a proto je bezpenj.R2(config)#username R3 password ciscoR2(config)#int s0/0/1R2(config-if)#ppp authentication chapR2(config-if)#

R3(config)#username R2 password cisco*Aug 23 18:07:13.074: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/1, changed state to upR3(config)#int s0/0/1R3(config-if)#

*Aug 23 18:07:22.174: %OSPF-5-ADJCHG: Process 1, Nbr 209.165.200.225 on Serial0/0/1 from LOADING to FULL, Loading Done

R3(config-if)#ppp authentication chapR3(config-if)#Notice that the line protocol on interface serial 0/0/1 changes state to UP even before the interface is configured for CHAP authentication. Can you guess why this is the case? Linkov protokol na serial 0/0/1 jde nahoru jet pedtm, ne je to rozhran konfigurovno pro CHAP. Pro?_____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

CHAP is able to do either one-way or two-way authentication. Therefore, as soon as the correct username and password are configured, the link comes up.

Step 3: VynechnoTask 8: Intentionally Break and Restore PPP CHAP Authentication

Step 1: Break PPP CHAP authentication.

On the serial link between R2 and R3, change the authentication protocol on interface serial 0/0/1 to PAP.

R2(config)#int s0/0/1R2(config-if)#ppp authentication papR2(config-if)#^ZR2#

R2#copy run startR2#reloadDoes changing the authentication protocol to PAP on interface serial 0/0/1 break authentication between R2 and R3? _____________________________________________________________________

_____________________________________________________________________

_____________________________________________________________________

Kdybychom nerestartovali, linkov protokol by zstal up. Pro?R2#show ip int briefInterface IP-Address OK? Method Status Protocol

FastEthernet0/0 unassigned YES NVRAM administratively down down


Serial0/0/0 10.1.1.2 YES NVRAM up up

Serial0/0/1 10.2.2.1 YES NVRAM up down

Serial0/1/0 unassigned YES NVRAM administratively down down


Loopback0 209.165.200.225 YES NVRAM up up Step 2: Restore PPP CHAP authentication on the serial link.

Notice that it is not necessary to reload the router for this change to take effect.

R2(config)#int s0/0/1

R2(config-if)#ppp authentication chap

Step 3: Intentionally Break PPP CHAP authentication by changing the password on R3.

R3(config)#username R2 password ciscoR3(config)#^ZR3#

R3#copy run startR3#reloadAfter reloading, what is the status of the line protocol on serial 0/0/1?

_____________________________________________________________________

_____________________________________________________________________

Down. Verify using the show ip interface brief command.

R3#show ip int brief

Interface IP-Address OK? Method Status Protocol


FastEthernet0/1 192.168.30.1 YES NVRAM up up


Serial0/0/1 10.2.2.2 YES NVRAM up down

Step 4: Restore PPP CHAP authentication by changing the password on R3.

R3(config)#username R2 password ciscoR3(config)#

All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.Page 1 of 9All contents are Copyright 19922007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.Page 7 of 9

4e_02_5_1_ppp

Documents