Scribd
Upload
31 views

CCNP Route Lab Deliverables

This document summarizes the checkpoints for several labs involving router configuration exercises. The checkpoints involve demonstrating connectivity, load balancing, route summarization, default route injection, and other routing concepts through commands like ping, traceroute, and show route. Completing the checkpoints proves the expected routing behavior is achieved after each configuration step.

Uploaded by

Kobe Martinez
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
31 views

CCNP Route Lab Deliverables

This document summarizes the checkpoints for several labs involving router configuration exercises. The checkpoints involve demonstrating connectivity, load balancing, route summarization, default route injection, and other routing concepts through commands like ping, traceroute, and show route. Completing the checkpoints proves the expected routing behavior is achieved after each configuration step.

Uploaded by

Kobe Martinez
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Lab 2-1 Checkpoint 1 (Step 2D): By using TCL script, verify full connectivity to all

the interface address configured, when EIGRP routing was enabled on all
routers.
Checkpoint 2 (Step 4C and Step 5): Prove that load balancing is in effect
when R3 is pinging 10.1.102.1 by using the traceroute utility and the
show ip eigrp topology command
Checkpoint 3 (Step 6G): Demonstrate that unequal load balancing is now
in effect when R3 is now reaching the 10.1.2.1 interface.
Lab 2-2 Checkpoint 1 (Step 3C): Demonstrate that when R2 was configured as an
EIGRP stub router, R1 will only show EIGRP routes for R2’s connected
networks and R2’s summary route.
Checkpoint 2 (Step 4E): Demonstrate that when R2 was modified to
include connected, summary and static routes in its EIGRP stub routing,
R1 will now send its connected, summarized and static routes to R2.
Checkpoint 3 (Step 5B): Demonstrate that when R2 was modified as
EIGRP stub receive-only, R1 will show no EIGRP route in its routing table.
Lab 2-3 Checkpoint 1 (Step 6C and Step 6D): Demonstrate that routes have been
summarized on R1’s IPv6 routing table after executing the command on
Step6B and that all loopback interfaces of R3 can be reached by R1.
Checkpoint 2 (Step 7B and Step 7C): Demonstrate that the default route
is present after executing the command on Step 7A and the interface
2001:db8:feed:77::1 can be reached by R1.
Lab 2-4 Checkpoint 1 (Step 8E): Verify end-to-end reachability of R1. R1# ping
192.168.5.1 and R1# ping 2001:db8:cafe:5::1 must both be successful.

Note: Setup R4 as loopback interface, instead.


Checkpoint 2 (Step 8F): Present the output of R3 similar to that of the
output presented on R3, step 8F.
Lab 3-1 Checkpoint 1 (Step 3H): Present the network type of R2’s interface as a
virtual link. Show that R1#ping 192.168.103.1 and R3#ping 10.1.1.1 are
both successful.
Checkpoint 2 (Step 5M and Step 5N): Present the default route injected
into R3 and a summarized route present as well. Show that R3#ping
172.30.30.1 is successful.
Lab 3-2 Checkpoint 1 (Step 2I): Show that the default route and subnet
192.168.99.0 have been injected in R1’s routing table.
Checkpoint 2 (Step 3C): Prove that when OSPF stub routing is enabled,
LSA 4 and LSA 5 are suppressed on the internal route. Demonstrate that
the default route is injected by the ABR.
Checkpoint 3 (Step 4E): Prove that when totally stub routing is enabled,
LSA 3, LSA 4 and LSA 5 are suppressed on the internal route.
Demonstrate that the default route is injected by the ABR.
Checkpoint 4 (Step 5I): Show that the default route and IPv6 static route
have been injected in R1’s routing table.
Checkpoint 5 (Step 7C): Prove that when totally IPV6 totally stub routing
is enabled, LSA 3, LSA 4 and LSA 5 are suppressed on the internal route.
Demonstrate that the default route is injected by the ABR.
Lab 3-3 Checkpoint 1 (Step 2I): Show that the default route and static route have
been injected on R1’s routing table.
Checkpoint 2 (Step 4D): Using the address-family feature, prove that
when totally IPV6 totally stub routing is enabled, LSA 3, LSA 4 and LSA 5
are suppressed on the internal route. Demonstrate that the default route
is injected by the ABR.
Lab 4-1 Checkpoint 1 (Step 6D and Step 6E): Demonstrate that both EIGRP and
OSPF routes are present on the routing table of R1 and R3.
Lab 4-2 Checkpoint 1 (Step 3D): Show that 192.168.8.0 is not present on R1’s
routing table when R2 has been configured with a distribute list and ACL
as shown on Steps 3B and Steps 3C.
Checkpoint 2 (Step 4D): Confirm that only the 172.16.0.0/16 networks
are being advertised to R3 when R2 has been configured with a distribute
list and prefix-list as shown on Steps 4B and Steps 4C.
Checkpoint 3 (Step 5E): Confirm that the 192.168.25.0/24 and
192.168.30.0/24 networks are no longer in the routing table of R1 when
R2 has been configured with a route-map and ACL as shown on Steps 5C
and Steps 5D.
Checkpoint 4 (Step 6E): Confirm that the 172.16.12.0/24 route is now a
type 1 route and calculates the actual metric on R3’s routing table when
R2 has been configured with a route-map and prefix list as shown on
Steps 6B, 6C and Steps 6D.
Lab 4-3 Checkpoint 1 (Step 5D and Step 5E): Demonstrate that both EIGRP and
OSPF routes are present on the routing table of R1 and R3. Upon loading
the tcl script, all pings on R1 must be successful.
Lab 5-2 Checkpoint 1 (Step 3): Present screenshot that R1 has been configured
using 2 SLA probes.
Checkpoint 2 (Step 4): Present screenshot that the administrative
distance of R1’s default route has been modified from 5 to 2.
Checkpoint 3 (Step 5b and 5c): Verify from the debug output that R1’s
default route will now use a next hop IP address of 209.165.202.129 and
administrative distance of 3.
Checkpoint 4 (Step 5f): Verify from the debug ip routing output that R1
will establish s’s default route will now use an administrative distance of
2.
Lab 7-1 Checkpoint 1 (Step 4): Prove the BGP operation on the ITA and ISP1
routers thru the show ip bgp command.
Checkpoint 2 (Step 5d): Present the output similar to ISP2’s routing table.
Checkpoint 3 (Step 5e): Present the output ITA#clear ip bgp *and
ISP2#show ip route similar as shown on your manual.
Checkpoint 4 (Step 4): Present the output that the default route was
received by ITA using BGP.
Lab 7-2 Checkpoint 1 (Step 3F): Show that 10.3.3.0 is present as a BGP route and
ping 10.3.3.1 source lo0 must be successful.
Checkpoint 2 (Step 4F): Run the following Tcl script on all routers to verify
whether there is connectivity. All pings from ISP should be successful.
SanJose should not be able to ping the CustRtr loopback 10.3.3.1 or the
WAN link 172.24.1.16/30. CustRtr should not be able to ping the SanJose
loopback 10.1.1.1 or the WAN link 192.168.1.5/30 and 192.168.1.6/30.
Lab 7-3 Checkpoint 1 (Step 6J): Execute all ping test from the ISP router and show
that they are all successful.
Checkpoint 2 (Step 7I and Step 7J): Show that 192.168.100.0/24 is
present as a BGP route in SanJose2and will take two different next hop
addresses when the BGP attribute has been configured.
Checkpoint 3 (Step 8B): Demonstrate that routing to the loopback
segment for ISP 192.168.100.0 /24 can be reached only through the link
common to SanJose1 and ISP.
Checkpoint 4 (Step 9D): Show that the ISP now prefers SanJose1 for
return traffic.
Checkpoint 5 (Step 10G): Verify the new path using the traceroute
command to 10.0.0.1 from SanJose1 and show that the default route is
now through SanJose2.
Lab 7-5 Checkpoint 1 (Step 5A and Step 5B): Present the ISP IPV4 and IPv6 BGP
table.
Checkpoint 2 (Step 6D): Verify IPv4 and IPv6 reachability pinging ISP’s
LAN interface from the LAN interface on SanJose2.

You might also like