Tecnologías WAN

Unidad 1 – Tarea 2

Ángela Natalia Arévalo González – 1070968800

Diego Fernando Guillen – 1070947815

Johan Arley Jiménez – 1038359373

Grupo: 2150521_2

Universidad Nacional Abierta y a Distancia

Acceso a la WAN

2018
 Tabla de contenido

1.4.1.2 Packet Tracer - Skills Integration Challenge OSPF .......................... 4

1.4.1.3 Packet Tracer - Skills Integration Challenge EIGRP ....................... 18

3.1.2.7 Packet Tracer - Troubleshooting Serial Interfaces .......................... 30

3.3.2.7 Packet Tracer - Configuring PAP and CHAP Authentication .......... 36

3.4.1.4 Packet Tracer - Troubleshooting PPP with Authentication ............. 43

3.5.1.2 Packet Tracer - Skills Integration Challenge ................................... 49

4.2.1.4 Packet Tracer - Configuring Static Frame Relay Maps ................... 57

4.2.2.6 Packet Tracer - Configuring Frame Relay Point-to-Point

Subinterfaces ........................................................................................................ 62

4.4.1.2 Packet Tracer - Skills Integration Challenge ................................... 69

 Introducción.

En el presente trabajo se abordaran los temas, que darán solución a cada uno de

los ejercicios planteados por el tutor en la guía de actividades, apropiando los

conceptos presentados en los contenidos de formación en la página web de cisco

y posterior se relacionaran en el contexto de las telecomunicaciones respecto a su

aplicación en las redes de área extendida, también se comprenderá el uso que

tienen las tecnologías WAN en el desarrollo de proyectos de conectividad de redes

empresariales.
 1.4.1.2 Packet Tracer - Skills Integration Challenge OSPF

Note: This activity and the similar Packet Tracer - Skills Integration Challenge -

EIGRP activity are meant as resources for you to determine what skills you may

not have yet mastered from the previous courses. Refer to your notes and previous

content if you need assistance. But it may be fun initially to see just how much you

retained.

Topology.
Addressing Table
Scenario
Your business has just expanded into a different town and needs to expand its

presence across the Internet. You are tasked with completing the upgrades to the

enterprise network, which includes dual-stacked IPv4 and IPv6, and a variety of

addressing and routing technologies.

Requeriments
Note: Although not required, adding additional labeling to the topology may help

you as you proceed. All names and passwords are case-sensitive.

Basic Device Configuration

 Configure the following on R1 and R4.

 Set the device names to match the Addressing Table.

 Set cisco as the encrypted privileged EXEC mode password.

 Set a banner MOTD which includes the word warn.

 Set the IPv4 and IPv6 addresses according to the Addressing Table.

 Assign the link local address to each interface.

SSH

 Configure SSH on R4.

 Set a domain name of R4.

 Create a user of admin with an encrypted password of cisco.

 Create a 2,048-bit RSA key.

 Configure all vty lines to use SSH and a local login.

DHCPv4

 Configure R4 to act as a DHCP server for its LAN.

 Create a DHCP pool using the name R4.

 Assign the appropriate addressing information to the pool including the

209.165.44.2 as the DNS server.

 Prevent the address used by the router from being distributed to end

devices.

NAT

 Configure NAT/PAT on R4 so that all devices on the LAN use the IP

address on the Serial 0/0/1 to access the Internet.

 Use a single statement in access list 1 to define the addresses that will

participate in NAT. Allow only the 10.10.4.0/24 address space.

 Enable NAT/PAT using the access list.

 Configure the appropriate interfaces as NAT inside or outside

 Configure PAT on R1.

 Use a single statement in access list 1 to define the addresses that will

participate in NAT. Allow only the 10.10.0.0/16 address space.

 Define a pool named R1 to use all four addresses in the 64.102.139.4/30

address space.

 Assign access list 1 to the R1 pool.

 Configure the appropriate interfaces as NAT inside or outside.

 Configure static NAT on R1 for remote access to Intranet.pka server.

 Use a static NAT statement to redirect TCP port 80 traffic from 64.102.139.2
to 10.10.10.10.

 Use a static NAT statement to redirect TCP port 443 traffic from
64.102.139.2 to 10.10.10.10.
Default Routing

 On R1, configure an IPv4 default route using the next-hop IP address

64.102.139.1.

 On R1, configure an IPv6 default route using the exit interface.

 On R4, configure an IPv4 and IPv6 default route using the exit interface.

OSPF Routing

 Configure OSPFv2 area 0 on R1.

 Use process ID 1.

 Advertise directly connected networks. Do not include the link to the

Internet.

 Prevent routing updates from being sent across the LAN interfaces.

 Propagate the default route.

 Configure OSPFv3 area 0 on R1.

 Use process ID 1.

 Assign 1.1.1.1 as the router ID.

 Prevent routing updates from being sent across the LAN interfaces.

 Complete any required OSPFv3 or IPv6 routing configurations.

Verify Connectivity
 Configure PC5 and PC6 to use DHCP for IPv4 and Autoconfig for IPv6.
 Verify web access to Internet.pka and Intranet.pka from each six PCs. Be
sure to test both IPv4 and IPv6. Pings are not forwarded from PC5 and PC6
to Intranet.pka.
 1.4.1.3 Packet Tracer - Skills Integration Challenge EIGRP

Topology

Addressing Table

IP Address Subnet Mask

Device Interface IPv6 Address/Prefix Default Gateway

S0/0/0 192.168.3.241 255.255.255.252 N/A

Branch0
S0/0/1 192.168.3.254 255.255.255.252 N/A
G0/0 DHCP Assigned DHCP Assigned N/A
Branch1 S0/0/0 192.168.3.245 255.255.255.252 N/A
S0/0/1 192.168.3.253 255.255.255.252 N/A
G0/0 192.168.2.1 255.255.255.0 N/A
Branch2 S0/0/0 192.168.3.246 255.255.255.252 N/A
S0/0/1 192.168.3.249 255.255.255.252 N/A
G0/0.10 192.168.1.1 255.255.255.128 N/A
 G0/0.20 192.168.1.129 255.255.255.192 N/A
G0/0.30 192.168.1.193 255.255.255.224 N/A
G0/0.88 192.168.1.225 255.255.255.240 N/A
Branch3 G0/0.99 192.168.1.241 255.255.255.252 N/A
G0/1 192.168.0.1 255.255.255.0 N/A
S0/0/0 192.168.3.250 255.255.255.252 N/A
S0/0/1 192.168.3.242 255.255.255.252 N/A
S0/0/0 2001:DB8:4::4/64 N/A
S0/0/1 2001:DB8:3::4/64 N/A
Branch4 S0/1/0 2001:DB8:5::4/64 N/A
Router N/A
ID 4.4.4.4
S0/0/0 2001:DB8:1::5/64 N/A
S0/0/1 2001:DB8:3::5/64 N/A
Branch5 Link-local FE80::5 N/A
Router N/A
ID 5.5.5.5
S0/0/0 2001:DB8:4::6/64 N/A
S0/0/1 2001:DB8:2::6/64 N/A
Branch6 Link-local FE80::6 N/A
Router N/A
ID 6.6.6.6
G0/0 2001:DB8:7:A::1/64 N/A
G0/1 2001:DB8:7:B::1/64 N/A
S0/0/0 2001:DB8:1::7/64 N/A

Branch7 S0/0/1 2001:DB8:2::7/64 N/A

Link- N/A
Local FE80::7
Router N/A
ID 7.7.7.7
ISP G0/0 209.165.202.129 255.255.255.224 N/A
S1 VLAN 88 192.168.1.226 255.255.255.240 192.168.1.225
S2 VLAN 88 192.168.1.227 255.255.255.240 192.168.1.225
S3 VLAN 88 192.168.1.228 255.255.255.240 192.168.1.225
Host-A NIC DHCP assigned DHCP assigned DHCP assigned
 Host-B NIC 192.168.1.130 255.255.255.192 192.168.1.129
Host-C NIC 192.168.1.194 255.255.255.224 192.168.1.193
PC-A NIC 2001:DB8:7:A::A/64 FE80::7
PC-B NIC 2001:DB8:7:B::B/64 FE80::7

VLAN and Port Assignments Table

VLAN Name Interface

10 Students F0/5-11
20 Faculty/Staff F0/12-17, G0/1-2
30 Guest(Default) F0/18-24
88 Management N/A
99 Native F0/1-4

Scenario
You are a network technician new to a company that has lost its last technician in
the middle of a system upgrade. You are tasked with completing upgrades to the
network infrastructure that has two locations. Half of the enterprise network uses
IPv4 addressing and the other half uses IPv6 addressing. The requirements also
include a variety of routing and switching technologies.

Requirements
You have console access to Branch3, Branch7, and S3. You can remotely access
other devices with the username admin and password adminpass. The password
for accessing privileged EXEC mode is class.

IPv4 Addressing
 Finish designing the IPv4 addressing scheme. Subnets already assigned
are using the 192.168.1.0/24 address space. Use the remaining space to
meet the following criteria:
 120 hosts for the Student VLAN attached to the Branch3 G0/0.10 interface.
 60 hosts for the Faculty/Staff VLAN attached to the Branch3 G0/0.20
interface.
 Configure inter-VLAN routing and assign the first available address from
each subnet to subinterfaces on the Branch3 router.

 Assign the second available address in the Faculty/Staff VLAN to Host-B.

IPv4 Routing
 Configure EIGRP for IPv4 on Branch3.
 Enable EIGRP 22.
 Advertise each of the directly connected networks and disable automatic
summarization.

 Prevent routing updates from being sent out the LAN interfaces.

 Configure a summary route for the Branch3 LANs and advertise the route to
Branch1 and Branch2.
  Configure a directly connected default route on Branch1 pointing to the ISP
and propagate it within the EIGRP updates.

DHCP
 Configure Branch3 to act as a DHCP server for VLAN 10 on S3.

 The case-sensitive pool name is Students.

 The DNS server is 209.165.201.14.

 Exclude the first 10 addresses from the pool.

 Configure Branch1 to receive an IPv4 address from the ISP.

  Configure PC Host-A to receive an IPv4 address from Branch3.

IPv6 Routing

 Configure EIGRP for IPv6 on Branch7.

 Enable IPv6 routing and EIGRP for IPv6 using ASN 222.

 Assign router ID 7.7.7.7.

 Advertise directly connected networks.

 Configure IPv6 summary routes for the LANs and advertise them to directly
connected routers.
  Configure a fully specified default route on Branch4 pointing to the ISP and
propagate it within the EIGRP updates.

Basic Switch Security

 Configure S3 with the following security settings.

 Banner MOTD that includes the word warning.

 Console port login and password of cisco.

 Encrypted enable password of class.

 Encrypt plain text passwords.

 Shut down all unused ports.

 Enable port security on S3 on the interfaces that the PCs are connected to.

 Configure as access ports.

 Only allow 1 host per port.

 Enable dynamic learning that stores the MAC address in the running

configuration.

 Ensure that port violations disable ports.

 Configure PortFast and BPDU Guard.

VLAN

 Create and name the VLANs on S3 based on the VLAN Table.

 Assign the switch ports on S3 to VLANs according to the VLAN Table.

  Configure the connection between Branch3 and S1 as a trunk and assign it

to VLAN 99.

Spanning Tree

 Configure S3 to use RSTP as the STP mode.

 Assign S3 as the root bridge and S1 as the backup root bridge for VLANs 10

and 20.

 Assign S1 as the root bridge and S3 as the backup root bridge for VLANs
30.Conclusiones.
Trunking and EtherChannel
 Set S3 interfaces connected to S1 and S2 as trunks and assign the native
VLAN.
 Configure EtherChannel on S3 as desirable.
 Use channel group 2 for trunks to S2.
 Use channel group 3 for trunks to S1.
 Assign the native VLAN.
 3.1.2.7 Packet Tracer - Troubleshooting Serial Interfaces

Topology
Addressing Table

Device Interface IP Address Subnet Mask Default Route

S0/0/0 (DCE) 64.100.34.17 255.255.255.252 N/A

S0/0/1 (DCE) 64.100.34.21 255.255.255.252 N/A
Telco
S0/1/0 (DCE) 64.100.34.25 255.255.255.252 N/A
S0/1/1 (DCE) 64.100.34.29 255.255.255.252 N/A
R1 S0/0/0 64.100.34.18 255.255.255.252 64.100.34.17
R2 S0/0/1 64.100.34.22 255.255.255.252 64.100.34.21
R3 S0/0/0 64.100.34.26 255.255.255.252 64.100.34.25
R4 S0/0/1 64.100.34.30 255.255.255.252 64.100.34.29

Part 1: Diagnose and Repair the Physical Layer

Step 1: Diagnose and repair the cabling.

a. Examine the Addressing Table to determine the location of the DCE connections.

b. Each serial connection has a DCE and a DTE connection. To determine if each

Telco interface is using the correct end of the cable look on the third line of output

following the show controllers command.

Telco# show controllers [interface_type interface_num]

 c. Reverse any cables that are incorrectly connected.

Se realiza la corrección en la conexión entre Telco y R4, las interfaces estaban

mal conectadas.

Note: In real network settings, the DCE (which sets the clock rate) is typically a
CSU/DSU.
Step 2: Diagnose and repair incorrect port connections.

a. Examine the Addressing Table to match each router port with the correct

Telco port.

b. Hold the mouse over each wire to ensure that the wires are connected as

specified. If not, correct the connections.

Se realiza la corrección entre Telco y R2.

Step 3: Diagnose and repair ports that are shutdown.

a. Show a brief interface summary of each router. Ensure that all of the ports

that should be working are not administratively down.

 b. Enable the appropriate ports that are administratively down:

R3(config)# interface s0/0/0

R3(config-if)# no shutdown

Part 2: Diagnose and Repair the Data Link Layer

Step 1: Examine and set clock rates on DCE equipment.

a. All of the DCE cables should be connected to Telco. Show the running
configuration of Telco to verify that a clock rate has been set on each
interface.
 b. Set the clock rate of any serial interfaces that requires it:

Telco(config)# interface s0/0/0

Telco(config-if)# clock rate 4000000
Telco(config-if)# interface s0/1/1
Telco(config-if)# clock rate 4000000

Step 2: Examine the encapsulation on DCE equipment.

a. All of the serial interfaces should be using HDLC as the encapsulation type.

Examine the protocol setting of the serial interfaces.

Telco# show interface [interface_type interface_num]

 b. Change the encapsulation type to HDLC for any interface that is set
otherwise:
R4(config)# interface s0/0/1
R4(config-if)# encapsulation hdlc

Part 3: Diagnose and Repair the Network Layer

Step 1: Verify the IP addressing.

a. Show a brief interface summary of each router. Check the IP addresses

against the Addressing Table and ensure that they are in the correct subnet
with their connecting interface.
b. Correct any IP addresses that overlap, or are set to the host or broadcast
address:

R1(config)# interface s0/0/0

R1(config-if)# ip address 64.100.34.18 255.255.255.252
 3.3.2.7 Packet Tracer - Configuring PAP and CHAP Authentication

Topology

Addressing Table

Device Interface IP Address Subnet Mask Default Gateway

G0/0 192.168.10.1 255.255.255.0 N/A

R1
S0/0/0 10.1.1.1 255.255.255.252 N/A
G0/0 192.168.30.1 255.255.255.0 N/A
R2
S0/0/1 10.2.2.2 255.255.255.252 N/A
S0/0/0 10.1.1.2 255.255.255.252 N/A
R3 S0/0/1 10.2.2.1 255.255.255.252 N/A
S0/1/0 209.165.200.225 255.255.255.252 N/A
S0/0/0 209.165.200.226 255.255.255.252 N/A
ISP
G0/0 209.165.200.1 255.255.255.252 N/A
 Web NIC 209.165.200.2 255.255.255.252 209.165.200.1
PC NIC 192.168.10.10 255.255.255.0 192.168.10.1
Laptop NIC 192.168.30.10 255.255.255.0 192.168.30.1

Part 1: Review Routing Configurations

Step 1: View running configurations on all routers.

While reviewing the router configurations, note the use of both static and dynamic

routes in the topology.

Step 2: Test connectivity between computers and the web server.

From PC and Laptop, ping the web server at 209.165.200.2. Both ping commands

should be successful. Remember to give enough time for STP and EIGRP to

converge.

Part 2: Configure PPP as the Encapsulation Method

Step 1: Configure R1 to use PPP encapsulation with R3.

Enter the following commands on R1:

R1(config)# interface s0/0/0

R1(config-if)# encapsulation ppp

Step 2: Configure R2 to use PPP encapsulation with R3.

Enter the appropriate commands on R2:

R2(config)# interface s0/0/1

R2(config-if)# encapsulation ppp
Step 3: Configure R3 to use PPP encapsulation with R1, R2, and ISP.

Enter the appropriate commands on R3:

R3(config)# interface s0/0/0

R3(config-if)# encapsulation ppp
R3(config)# interface s0/0/1
R3(config-if)# encapsulation ppp
R3(config)# interface s0/1/0
R3(config-if)# encapsulation ppp

Step 4: Configure ISP to use PPP encapsulation with R3.

a. Click the Internet cloud, then ISP. Enter the following commands:

Router(config)# interface s0/0/0

Router(config-if)# encapsulation ppp

b. Exit the Internet cloud by clicking Back in the upper left corner or by

pressing Alt+left arrow.

Step 5: Test connectivity to the web server.

PC and Laptop should be able to ping the web server at 209.165.200.2. This may

take some time as interfaces start working again and EIGRP reconverges.

Part 3: Configure PPP Authentication

Step 1: Configure PPP PAP Authentication Between R1 and R3.

Note: Instead of using the keyword password as shown in the curriculum, you will

use the keyword secret to provide a better encryption of the password.

 a. Enter the following commands into R1:
R1(config)# username R3 secret class
R1(config)# interface s0/0/0
R1(config-if)# ppp authentication pap
R1(config-if)# ppp pap sent-username R1 password cisco

b. Enter the following commands into R3:

R3(config)# username R1 secret cisco

R3(config)# interface s0/0/0
R3(config-if)# ppp authentication pap
R3(config-if)# ppp pap sent-username R3 password class

Step 2: Configure PPP PAP Authentication Between R2 and R3.

Repeat step 1 to configure authentication between R2 and R3 changing the

usernames as needed. Note that each password sent on each serial port matches

the password expected by the opposite router.

R2(config-if)# username R3 secret class

R2(config)# interface s0/0/1

R2(config-if)# ppp authentication pap

R2(config-if)# ppp pap sent-username R2 password cisco

R3(config-if)# username R2 secret cisco

R3(config)# interface s0/0/1

R3(config-if)# ppp authentication pap

R3(config-if)# ppp pap sent-username R3 password class

Step 3: Configure PPP CHAP Authentication Between R3 and ISP.

a. Enter the following commands into ISP. The hostname is sent as the

username:

Router(config)# hostname ISP

ISP(config)# username R3 secret cisco
ISP(config)# interface s0/0/0
ISP(config-if)# ppp authentication chap
 b. Enter the following commands into R3. The passwords must match for
CHAP authentication:

R3(config)# username ISP secret cisco

R3(config)# interface serial0/1/0
R3(config-if)# ppp authentication chap

Step 4: Test connectivity between computers and the web server.

From PC and Laptop, ping the web server at 209.165.200.2. Both ping commands

should be successful. Remember to give enough time for STP and EIGRP to

converge.
 3.4.1.4 Packet Tracer - Troubleshooting PPP with Authentication

Topology
Addressing Table

Device Interface IP Address Subnet Mask Default Gateway

G0/1 10.0.0.1 255.255.255.128 N/A

R1 S0/0/0 172.16.0.1 255.255.255.252 N/A
S0/0/1 172.16.0.9 255.255.255.252 N/A
G0/1 209.165.200.161 255.255.255.224 N/A
R2 S0/0/0 172.16.0.2 255.255.255.252 N/A
S0/0/1 172.16.0.5 255.255.255.252 N/A
G0/1 10.0.0.129 255.255.255.128 N/A
R3 S0/0/0 172.16.0.10 255.255.255.252 N/A
S0/0/1 172.16.0.6 255.255.255.252 N/A
ISP G0/1 209.165.200.162 255.255.255.224 N/A
PC1 NIC 10.0.0.10 255.255.255.128 10.0.0.1
PC3 NIC 10.0.0.139 255.255.255.128 10.0.0.129
Web Server NIC 209.165.200.2 255.255.255.252 209.165.200.1

Part 1: Diagnose and Repair the Physical Layer

Step 1: Diagnose and repair the cabling.

a. Examine the Addressing Table to determine the location of the all

connections.
b. Verify cables are connected as specified.
c. Diagnose and repair any inactive interfaces.
Part 2: Diagnose and Repair the Data Link Layer

Step 1: Examine and set clock rates on the DCE equipment.

Examine the configuration of each router to verify that a clock rate has been set on

appropriate interfaces. Set the clock rate of any serial interfaces that requires it.

Step 2: Examine the encapsulation on the DCE equipment.

All of the serial interfaces should be using PPP as the encapsulation type. Change
the encapsulation type to PPP for any interface that is set otherwise.

Step 3: Examine and set CHAP usernames and passwords.

Examine each link to verify that routers are logging into each other correctly. All
CHAP passwords are set to cisco. Use the debug ppp authentication command if
needed. Correct or set any usernames and passwords that need it.

Part 3: Diagnose and Repair the Network Layer

Step 1: Verify the IP addressing.

Check IP addresses against the Addressing Table and ensure that they are in the
correct subnet with their connecting interface. Correct any IP addresses that
overlap, are on the wrong interface, have the wrong subnet address, or are set to
the host or broadcast address.
Usuarios y contraseñas. (Login)
R1

R3

R2
Encapsulation, Autehenticacion Y Repair Layer Of Network
R1

R2
R3

Step 2: Verify full connectivity by tracing a path from PC1 and PC3 to the web

server.

PC1 AL WEB SERVER

PC3 AL WEB SERVER

 3.5.1.2 Packet Tracer - Skills Integration Challenge

Topology
Addressing Table

IPv4 Address Subnet Mask

IPv4 and IPv6
Device Interface
Default Gateway
IPv6 Address/Prefix

10.1.1.2 255.255.255.252 N/A

S0/0/0
2001:DB8:A:A::2/64 FE80::1
R1
209.165.200.226 255.255.255.252 N/A
S0/0/1
2001:DB8:B:1::2/64 FE80::1
192.168.1.193 255.255.255.224 N/A
G0/0.1
2001:DB8:A:1::1/64 FE80::2
192.168.1.1 255.255.255.128 N/A
G0/0.15
2001:DB8:A:15::1/64 FE80::2
192.168.1.129 255.255.255.192 N/A
R2 G0/0.25
2001:DB8:A:25::1/64 FE80::2
192.168.1.225 255.255.255.224 N/A
G0/0.99
2001:DB8:A:99::1/64 FE80::2
10.1.1.1 255.255.255.252 N/A
S0/0/0
2001:DB8:A:A::1/64 FE80::2
S1 VLAN 99 192.168.1.226 255.255.255.224 192.168.1.225
192.168.1.2 255.255.255.128 192.168.1.1
PC15 NIC
2001:DB8:A:15::2/64 FE80::2
192.168.1.130 255.255.255.192 192.168.1.129
PC25 NIC
2001:DB8:A:25::2/64 FE80::2
192.168.1.190 255.255.255.192 192.168.1.129
L25 NIC
2001:DB8:A:25::A/64 FE80::2

Addressing
 The addressing scheme uses the 192.168.1.0/24 address space. Additional
address space is available between VLAN 15 and VLAN 1. VLAN 25 needs
enough addresses for 50 hosts. Determine the subnet and complete the
subnet table below.
 VLAN IPv4 Subnet Address Subnet Mask Hosts

1 192.168.1.192 255.255.255.224 20
15 192.168.1.0 255.255.255.128 100
25 192.168.1.128 255.255.255.192 50
99 192.168.1.224 255.255.255.224 20

 Complete the Addressing Table by assigning the following addresses to

VLAN 25:
 R2 G0/0.25 - First IPv4 address
 PC25 - 2nd IPv4 address
 L25 - Last IPv4 address
 Configure IPv4 addressing on the necessary end devices.
 On R2, create and apply IPv4 and IPv6 addressing to the G0/0.25
subinterface.

VLANs
 On S1, create VLAN 86 and name it BlackHole.
 Configure S1 ports in static mode with the following requirements
 F0/1 is the native trunk for VLAN 99.
 F0/7 - F0/18 as access ports in VLAN 15.
 F0/19 - F0/24 as access ports in VLAN 25.
  G0/1 - 2 and F0/2 - F0/6 are unused. They should be properly
secured and assigned to the BlackHole VLAN.
 On R2, configure inter-VLAN routing. VLAN 99 is the native VLAN.
PPP
 Configure R1 and R2 to use PPP with CHAP for the shared link. The
password for CHAP is cisco.

Routing
 On R1, configure IPv4 and IPv6 default routes using the appropriate exit
interface.

 On R2, configure an IPv6 default route using the appropriate exit interface.
 Configure IPv4 OSPF using the following requirements:
 Use process ID 1.
 Routers R1 and R2 are in area 0.
 R1 uses router ID 1.1.1.1.

 -R2 uses router ID 2.2.2.2.

 Advertise specific subnets.

 On R1, propagate the IPv4 default route created.
 Configure IPv6 OSPF using the following requirements:
 Use process ID 1.
 Routers R1 and R2 are in area 0.
 Configure OSPF on appropriate interfaces on R1 and R2.
 R1 uses router ID 1.1.1.1.
 R2 uses router ID 2.2.2.2.
Connectivity
 All devices should be able to ping the web server.

Scripts
Configure PC25 and L25 with IPv4 Addressing
 4.2.1.4 Packet Tracer - Configuring Static Frame Relay Maps

Topology
Addressing Table

Device Interface IP Address Subnet Mask Default Gateway

G0/0 192.168.10.1 255.255.255.0 N/A

R1
S0/0/0 10.1.1.1 255.255.255.0 N/A
G0/0 192.168.30.1 255.255.255.0 N/A
R2
S0/0/0 10.1.1.2 255.255.255.0 N/A
S0/0/0 10.1.1.3 255.255.255.0 N/A
R3
S0/1/0 209.165.200.225 255.255.255.224 N/A
ISP S0/0/0 209.165.200.226 255.255.255.224 N/A
Web NIC 209.165.200.2 255.255.255.252 209.165.200.1
PC NIC 192.168.10.10 255.255.255.0 192.168.10.1
Laptop NIC 192.168.30.10 255.255.255.0 192.168.30.1

Part 1: Configure Frame Relay

Step 1: Configure Frame Relay encapsulation on the S0/0/0 interface of R1.

R1(config)# interface s0/0/0

R1(config-if)# encapsulation frame-relay

Step 2: Configure Frame Relay encapsulation on the S0/0/0 interfaces of R2
and R3.

R2(config)# interface s0/0/0

R2(config-if)# encapsulation frame-relay

R3(config)# interface s0/0/0

R3(config-if)# encapsulation frame-relay

Step 3: Test connectivity.
From the command prompt on PC, verify connectivity to the Laptop, located at
192.168.30.10, using the ping
command.
The ping from PC to Laptop should fail because R1 does not have a route to reach
the 192.168.30.0 network. R1 must be configured with a Frame Relay map so that
it can find the next hop destination to reach that network.
Part 2: Configure Static Frame Relay Maps and LMI Types
Each router requires two static maps to reach the other routers. The DLCIs to
reach these routers are provided below.
Step 1: Configure static maps on R1, R2, and R3.
a. Configure R1 to use static frame relay maps. Use DLCI 102 to communicate
from R1 to R2. Use DLCI 103 to communicate from R1 to R3. The routers
must also support EIGRP multicast on 224.0.0.10; therefore, the broadcast
keyword is required.
R1(config)# interface s0/0/0

R1(config-if)# frame-relay map ip 10.1.1.2 102 broadcast

R1(config-if)# frame-relay map ip 10.1.1.3 103 broadcast

b. Configure R2 to use static Frame Relay maps. Use DLCI 201 to

communicate from R2 to R1. Use DLCI 203 to communicate from R2 to R3.
Use the correct IP address for each map.

R2(config)# interface s0/0/0

R2(config-if)# frame-relay map ip 10.1.1.1 201 broadcast

R2(config-if)# frame-relay map ip 10.1.1.3 203 broadcast
 c. Configure R3 to use static Frame Relay maps. Use DLCI 301 to
communicate from R3 to R1. Use DLCI 302 to communicate from R3 to R2.
Use the correct IP address for each map.

R3(config)# interface s0/0/0

R3(config-if)# frame-relay map ip 10.1.1.1 301 broadcast

R3(config-if)# frame-relay map ip 10.1.1.2 302 broadcast

Step 2: Configure ANSI as the LMI type on R1, R2, and R3.

Enter the following command on the serial interface for each router:
R1(config-if)# frame-relay lmi-type ansi
R2(config-if)# frame-relay lmi-type ansi
R3(config-if)# frame-relay lmi-type ansi
Step 3: Verify connectivity.
The PC and Laptop should now be able to ping each other and the Web Server.

4.2.2.6 Packet Tracer - Configuring Frame Relay Point-to-Point

Subinterfaces
Topology
Addressing Table

Device Interface IP Address Subnet Mask Default Gateway

G0/0 192.168.10.1 255.255.255.0 N/A

R1 S0/0/0.2 10.1.1.1 255.255.255.252 N/A
S0/0/0.3 10.1.3.2 255.255.255.252 N/A
G0/0 192.168.30.1 255.255.255.0 N/A
R2 S0/0/0.1 10.1.1.2 255.255.255.252 N/A
S0/0/0.3 10.1.2.1 255.255.255.252 N/A
S0/0/0.1 10.1.3.1 255.255.255.252 N/A
R3 S0/0/0.2 10.1.2.2 255.255.255.252 N/A
S0/1/0 209.165.200.225 255.255.255.224 N/A
ISP S0/0/0 209.165.200.226 255.255.255.224 N/A
Web NIC 209.165.200.2 255.255.255.252 209.165.200.1
PC NIC 192.168.10.10 255.255.255.0 192.168.10.1
Laptop NIC 192.168.30.10 255.255.255.0 192.168.30.1

Part 1: Configure Frame Relay

Step 1: Configure Frame Relay encapsulation on the S0/0/0 interface of R1.

Step 2: Configure Frame Relay encapsulation on the S0/0/0 interfaces of R2

and R3.
Step 3: Test connectivity.

From the command prompt on PC, verify connectivity to the Laptop, located at

192.168.30.10, using the ping command.

The ping from PC to Laptop should fail because the R1 router does not have to

route to reach the 192.168.30.0 network. R1 must be configured with a Frame

Relay on subinterfaces so that it can find the next hop destination to reach that

network.

Part 2: Configure Frame Relay Point-to-Point Subinterfaces

Each router requires two subinterfaces to reach the other routers. The DLCIs to

reach these routers are provided below.

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

a. Configure R1 to use subinterfaces. DLCI 102 is used to communicate from

R1 to R2, while DLCI 103 is used to communicate from R1 to R3.

b. Add network entries to EIGRP autonomous system 1 to reflect the IP

addresses above.
Enrutamiento Dinámico EIGRP

c. Configure R2 to use subinterfaces. DLCI 201 is used to communicate from

R2 to R1, while DLCI 203 is used to communicate from R2 to R3. Use the
correct IP address in the Address Table for each subinterface.

d. Add the appropriate EIGRP entries to R2 for autonomous system of 1.

 e. Configure R3 to use subinterfaces. DLCI 301 is used to communicate from
R3 to R1, while DLCI 302 is used to communicate from R3 to R2. Use the
correct IP address for each subinterface.

f. Add the appropriate EIGRP entries to R3 for autonomous system of 1.

Part 3: Verify Configuration and Connectivity

Step 1: Verify the Frame Relay configuration.
Show information about Frame Relay and the connections that have been made.
Note the fields for BECN, FECN, DE, DLCI, and LMI TYPE.
R1# show frame-relay map
R1# show frame-relay pvc
R1# show frame-relay lmi
Step 2: Verify end-to-end connectivity.
The PC and Laptop should be able to ping each other and the Web Server.
 4.4.1.2 Packet Tracer - Skills Integration Challenge
Topology
Addressing Table

Device Interface IPv4 Address Subnet Mask Default Gateway

S0/0/0 10.0.0.1 255.255.255.248 N/A

R1
S0/0/1 209.165.201.2 255.255.255.252 N/A

G0/0 10.1.100.1 255.255.255.0 N/A

R2
S0/0/0 10.0.0.2 255.255.255.248 N/A

G0/0 10.1.150.1 255.255.255.0 N/A

R3
S0/0/0 10.0.0.3 255.255.255.248 N/A

G0/0 10.1.200.1 255.255.255.0 N/A

R4
S0/0/0 10.0.0.4 255.255.255.248 N/A

Web NIC 209.165.200.226 255.255.255.252 209.165.200.225

PC2 NIC 10.1.100.10 255.255.255.0 10.1.100.1

PC3 NIC 10.1.150.10 255.255.255.0 10.1.150.1

Tablet PC NIC 10.1.150.20 255.255.255.0 10.1.150.1

Laptop NIC 10.1.200.10 255.255.255.0 10.1.200.1

DLCI Mappings
From / To R1 R2 R3 R4
R1 - 102 103 104
R2 201 - 203 204
R3 301 302 - 304
R4 401 402 403 -

Requirements
R1
 Configure R1 to use PPP with CHAP on the link to the Internet. ISP is the
router hostname. The password for CHAP is cisco.
  Configure a default route to the Internet. Use the exit interface.
 Configure a static route to the LAN on R4. Use the next-hop IP address.

 Configure EIGRP.
 Use AS number 100.
 Advertise the entire 10.0.0.0/8 network and disable automatic
summarization.
Propagate the default route.
 Configure full mesh Frame Relay.
 Configure Frame Relay encapsulation.
 Configure a map to each of the other routers. The PVC to R4 uses
IETF encapsulation.
 The LMI type is ANSI.
R2 and R3
 Configure EIGRP.
 Use AS number 100.
 Advertise the entire 10.0.0.0/8 network and disable automatic
summarization.
 Do not send EIGRP messages out the LAN interfaces.
 Configure full mesh Frame Relay.
 Configure Frame Relay encapsulation.
 Configure a map to each of the other routers. The PVC to R4 uses
IETF encapsulation.
 The LMI type is ANSI.
R2
R3

R4
 Configure static and default routing.
 Configure a static route for each of the LANs on R2 and R3. Use the
next-hop IP address.
 Configure a default route to R1. Use the next-hop IP address.
  Configure full mesh Frame Relay.
 Configure Frame Relay encapsulation using IETF.
 Configure a map to each of the other routers.
 The LMI type is ANSI.

Verify End-to-End Connectivity

R1
R2
R3
R4
 Conclusiones.

 Entiendo que el comportamiento del protocolo de resolución de direcciones

inverso, o bien conocido como RARP en Frame-relay hace la asignación

dinámica de los DLCI, esta el feature por default en los routers cisco.

 RARP es el método de mapeo de direcciones ip a direcciones físicas en las

redes de datos.

 Comprendo que los DLCI solo tienen significancia Local.

 Evaluo que en redes NBMA siempre deben estar en una misma subred la

asignación de Frame-relay.

 Descubro que por el horizonte dividido, en redes NBMA Hub and spoke no

es posible el paso de diferentes mensajes de protocolos de enrutamiento.

 Observo que para evitar el horizonte divido en redes NBMA Hub and spoke,

la asignación de mas DLCI generaría mas costo la implementación. Y la

solución correcta seria las subinterfaces.

 Designo los login en cada router PPP inverso en el hostname de cada uno

de ellos.

 Evidencio que el protocolo de autenticación CHAP es mejor que PAP por el

cifrado MD5 y HASH de tres etapas.

 La Multiplexacion TDM es de vital importancia en redes de fibra óptica en

redes WAN.
 Bibliografía.

CISCO. (2018). Cisco Networking Academy. Obtenido de

https://www.netacad.com/

CISCO. (2018). Cisco Networking Academy. Obtenido de Modulos del capitulo 1 al

4: https://static-course-

assets.s3.amazonaws.com/CN503/es/index.html#1.1.2.1