Thursday, March 10, 2016

CCNAv2 Chapter 6 RSE Packet Tracer TUTORIAL

Greetings, and welcome to Seeseenayy.
I have found that there is no good tutorial on how to do Chapter 6's RSE Packet Tracer for CCNA2, so I made one. I've only seen the PDF with the commands underneath them, but no text tutorial for those who don't understand how to complete it. First, it's an easy packet tracer, but some do need explanations. Second, the video tutorials, while they do help, can not be easily accessed for some, and text alternatives are better, as presented here.
Anyways, if you have an issue, comment below. Thanks.

Here's an image guide to refer to. The addressing table, however, is not present. That can be found on the PT itself. Please, if you don't understand why we use routes to where, or whatnot, use this image. It may help you.




COMMANDS & TUTORIAL BELOW
Basically, this PT wants us to use both IPV6 and IPV4 routing with additional requirements such as administrative distance, etc. All from Chapter six. 

Directions, Part I: 
Use Address Space 10.10.16.0/24 to design an addressing scheme 
>> "Split this address space into two equal-sized networks by subnetting it again.
>> Assign the first of these new subnets to PC1 LAN.
>> Assign the second of these new subnets subnet to PC2 LAN.
>> For each subnet, assign the first usable IP address to R2 and the last usable IP address to the PCs."

Start by placing console cables. Yes, we can place cables in PTs now? Woah!
a. PC3 to R3
b. PC2 to R1
c. PC1 to R2 

Assign IP Addresses to PC1 and PC2:
            IP Address    Subnet Mask      Default Gateway
PC1 = 10.10.16.126, 255.255.255.128, 10.10.16.1
PC2 = 10.10.16.254, 255.255.255.128, 10.10.16.129

Using PC1's terminal connection to R2, configure G0/0 & G0/1's ports as follows: 
R2>en
R2>conf t
R2(config)# int g0/0
R2(config-if)# ip addr 10.10.16.1 255.255.255.128
R2(config-if)# no sh
R2(config-if)# int g0/1
R2(config-if)# ip addr 10.10.16.129 255.255.255.128
R2(config-if)# no sh
R2(config-if)# ex

Then, Step 2 for the requirements.
R2(config)# ip route 0.0.0.0 0.0.0.0 10.10.20.1

Go to R1 to complete Step 2's IPV4 route on R1.
R1>en
R1#conf t
R1(config)#ip route 0.0.0.0 0.0.0.0 s0/0/0
%Default route without gateway, if not a point-to-point interface, may impact performance



Then for the Summary Route on R1...
R1(config)#ip route 10.10.16.0 255.255.255.0 s0/1/1

Finally, Step three of the configurations:
1. Configure an IPv6 default route on R3 using the exit interface.
2. Configure an IPv6 default route on R1 using Serial 0/0/1 as the exit interface.
3. Configure an IPv6 summary route on R1 for the internal  LANs. Use the exit interface. 

So, go to PC3 and open up PC3s' terminal connection to R3, and enter as follows. Note that this is an IPV6 route!
R3>en
R3#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
R3(config)#ipv6 route ::/0 s0/0/0
R3(config)#

Now, we have to configute the IPV6 default route on R1 using our terminal connection from PC2. See Step 2 above. This is also IPV6:
R1(config)#ipv6 route ::/0 s0/0/1

Finally, the last step on this requirement. So in R1, we need to configure IPV6 summary route on R1 for our internal lans using: 
R1(config)#ipv6 route 2001:db8:1:a::/63 S0/1/0

The last step is to... 
Configure an IPv4 floating static route on R1 to the 64.100.100.0/24 network using the Serial 0/0/1 as the exit interface. Make the floating static route less trustworthy than the default route by one unit of AD:

Easy! Redirect traffic as so.
R1(config)#ip route 64.100.100.0 255.255.255.0 s0/0/1 2

If all is configured correctly, we can verify system  functionality. Open PC2's command line and enter "ping  64.100.100.10", the first request should/will time out as always, but the three following pings should be a successful reply. 

If your ping is good, you should get 100%.
This was a pretty easy packet tracer, it was really like one of the first few PTs from this chapter. If you have issues, review my notes or try some more PTs from Chapter 6.

No comments:

Post a Comment

Feel free to comment if you have a question, commendation, or concern. We love to hear your feedback!

Please do not share links to external websites if it not relevant to discussion. We reserve our right to remove any content we deem advertising.