In this lesson I’m going to walk you through a full lab that is based on the official Cisco CCNP TSHOOT topology. This lab is “broken” so that we have something to fix.
- Manual Configuration Settings
- Configuration Files In Linux
- Ccnp Tshoot Lab Manual Configuration Files In Linux Windows 7
- Ccnp Tshoot Lab Manual Configuration Files In Linux Pdf
- Network Configuration Files In Linux
CCNP Security Free Download Ccnp Security Firewall Lab Manual Pdf Ccnp Security Firewall Lab Manual Pdf. Network Security, VPN Security, Unified Communications, Hyper-V, Windows 2012, Routing, Switching, Network Management, Cisco Lab, Linux Administration. Cisco CCNP Routing & Switching v2.0 – Official Cert Guide Library Review. CCNP TShoot 300-135; Linux (RHEL6 & RHEL7) PFSense; Sunday, January 18, 2015 ← Newer Post. Older Post → Home. In CCNA (R/S 200-120) by Shubham Kumar 2 comments. Vlan and Inter-Vlan Configuration Configuring Vlans and VTP Configure trunks. Click Here To Download The PDF File. 2 comments: Farhan Javed July 18, 2016 at 12:00 PM.
The official Cisco CCNP TSHOOT topology can be found here:
I recreated this topology in GNS3 as best as I could. Cisco released the topology pictures but without any configurations. I recreated the configurations so it will probably be 95% the same as what you might encounter on the exam. You can find my GNS3 topology right here:
Let’s troubleshoot one of those full labs! Before you continue reading I would highly suggest first giving this full lab a try yourself. If you get stuck you can continue reading and see how and why I solve it. Here’s the lab we are going to fix:
Enough talking, let’s get labbing!
Its Monday morning 8 AM. You slept great and there’s a lovely croissant and cup of coffee waiting for you. Suddenly the phone rings…it’s your colleague!
His voice sounds like he’s in panic. There are users complaining that they can’t access the network and he is unable to solve the problems by himself…he seriously needs your help.
You throw your croissant out of the window…it’s time to show what a network troubleshooting rockstar looks like!
The first thing you do is grab a copy of the network diagram. You want to know the layer2 and layer3 topology so you don’t have to do everything off top of your head.
Here’s what the network diagrams look like:
Then you open your helpdesk application and you’ll find the following troubleshooting tickets waiting for you:
- Ticket #1: One of the users was working on Client1 but he’s complaining that there is no connectivity. He left a comment that he saw a message on the windows taskbar that said something like “no network connectivity”. One of your colleagues looked into the problem and told you it had probably something to do with DHCP.
- Ticket #2: After fixing the issue with Client1 you receive another ticket that users from VLAN 10 are complaining that they are unable to connect to the FTP server.
- Ticket #3: Your users are happy that they can connect to the FTP server but they are still unable to reach the webserver.
- Ticket #4: The IPv6 team left a ticket for you that they are unable to reach 2026::12:/122 from DSW1 or DSW2.
You decide to start with ticket #1. “no network connectivity” probably has something to do with the client not receiving an IP address.
Ticket 1
To solve this problem there are a number of devices we might have to check:
- DHCP server: The pool could be misconfigured, DHCP might not be running, maybe some of the interfaces are not working.
- Client: Maybe the client is configured to use a static IP address.
- ASW1, DSW1 and/or DSW2: These are devices that are in between our client and the DHCP server.
The ticket told us that client1 has an issue but didn’t tell us anything about other clients in VLAN 10 like client2. We can take a quick look if client2 can get a DHCP lease or not. If this is the case then we at least know the DHCP server is fine.
Let’s check this:
It seems client2 has the same issue, lucky for us nobody reported this issue yet.
Client1 is configured for DHCP so to me this machine is looking good. If this were a real computer you might want to check other settings like the firewall. We will move our focus to the DHCP server:
First I’ll check if the DHCP server has received and sent any DHCP related messages. This doesn’t seem to be the case but doesn’t have to be an issue.
Maybe the router was rebooted and hasn’t received any DHCP discover messages since then. I do see that there is a DHCP pool. Let’s check if the DHCP service is running:
This router doesn’t support the “show ip sockets” command so I’ll take a look at the running processes. The DHCP service is running so we know this is not the issue. Let’s take a look at the DHCP pool:
We’ll take a look at the pool. The first thing that I notice is that the address range is incorrect. This pool is configured to use 10.2.10.0 /24 but VLAN 10 is using 10.2.1.0 /24. Let’s fix this:
This is looking better. The DHCP configuration itself is looking good now to me. Still, the DHCP server didn’t receive any DHCP discover messages. Let’s check if there is connectivity between R4 and DSW1 / DSW2. We’ll use a quick ping:
This is working fine so to me R4 is 100% operational when it comes to DHCP. This means we’ll have to move our focus to the switches in between the client and R4. I’ll start with ASW1:
First we’ll check the interface that is connected to client1. It seems to be up/up. Let’s check its switchport configuration:
Here’s an error. The interface is in access mode which is good but it has been assigned to VLAN 200. Client1 should be in VLAN 10:
We’ll put the interface in VLAN 10. Now this probably doesn’t fix this error since client1 isn’t the only device that didn’t get an IP address through DHCP. Client2 was also having issues. We need to verify connectivity from ASW1 to DSW1 and DSW2. Let’s take another look at the network diagram:
This is the area of the topology where I will focus on. Client1 is connected to ASW1 and is in VLAN 10. VLAN 10 is configured on ASW1, ASW2, DSW1 and DSW3. R4 is our DHCP server but it’s not directly connected to VLAN 10, it’s in another subnet. This means that DSW1 and DSW2 require the IP helper command so that DHCP discover messages can be relayed to the the DHCP server. This is what we’ll have to check:
- Is VLAN 10 configured and operational on all switches? Even if only ASW1 and DSW1 would work, I still want to have redundancy so we’ll check DSW2 too.
- Is IP helper configured on DSW1 and DSW2 for VLAN 10?
We’ll start with IP helper. It’s only a single command so if this is the issue we’ll save a lot of time by not having to check all the interfaces between the switches.
That’s not looking good. DSW1 and DSW2 don’t have IP helper configured.
Let’s fix it:
This is how we configure IP helper. This would be a good moment to check if the clients are receiving IP addresses through DHCP.
Still no DHCP action. This looks like one of those Mondays where everything goes wrong…we’ll have to check all the interfaces between the switches:
In between the switches we are using etherchannels. We can see that port-channel 1 and 2 are up and running. This doesn’t tell me anything about the VLANS though. Let’s take a closer look:
I can see that VLAN 10 is operational. Interface Fa1/4 and Fa1/5 are assigned to it. Let’s see if this VLAN is active on the trunk:
Now we are onto something! When we look at the trunk information of the Etherchannels we can see that VLAN 10 is not active. Let’s add it to the trunks:
This will add VLAN 10 to the etherchannels. Let’s check the other switches as well:
Manual Configuration Settings
The etherchannels on DSW1 and DSW2 are operational. Next step is to check if they are in trunk mode and if VLAN 10 is allowed or not:
Interface port-channel 1 is the one that is connected between ASW1 and DSW1. VLAN 10 is allowed on it so this should normally be enough. To make sure redundancy is intact I’m going to check the other interfaces as well:
We can verify that VLAN 10 is now operational on ASW1, DSW1 and DSW2. I didn’t bother with the interfaces that are connected to ASW2 because VLAN 10 is not active there. Did our hard work pay off?
We fixed all layer 2 and DHCP related issues but the clients are still not getting an IP address. What else could be wrong?
Let’s check if our DHCP server is receiving the DHCP messages from our clients:
Great! At least R4 is receiving the DHCP discover messages from our clients. I don’t see any DHCP ACK messages so something somewhere is going wrong. Let’s do a debug:
We’ll enable the debug to see DHCP packets.
R4 is receiving and sending DHCP messages for VLAN 10 and they are relayed to IP address 10.2.1.1 (DSW1) and 10.2.1.2 (DSW2). Is R4 able to reach these IP addresses?
R4 is unable to reach these IP addresses so that’s why DHCP is not working now. Back to the drawing board:
Our topology picture shows up that DSW1, DSW2 and R4 are configured for EIGRP AS 10. R4 should learn about the 10.2.1.0 /24 prefix through EIGRP. Let’s see if R4 has any neighbors:
R4 doesn’t have any EIGRP neighbors. Let’s check its EIGRP configuration:
We’ll do a quick show ip protocols to see if we can find anything. There are two interesting things here:
- The passive interface for FastEthernet1/0 (that’s the interface to DSW1).
- No network command for 10.1.4.8 /30 (that’s the interface to DSW2).
Let’s fix these two issues:
Configuration Files In Linux
Let’s see if this made any difference:
Seems we now have EIGRP neighbors! Let’s see if this solves our DHCP problem:
This is looking better! R4 is now sending DHCP ACKs so we know that the DHCP Offer makes it to the client. Let’s see if they finally got an IP address:
Ccnp Tshoot Lab Manual Configuration Files In Linux Windows 7
Finally the clients are receiving IP addresses through DHCP! This ticket is solved.
To solve this ticket I tried to get a “quick win” by looking at the DHCP configuration on R4. After fixing it, it still wasn’t working. When this occurs it’s best to jump to the bottom of the OSI-model and check everything layer-by-layer. Start with the cabling, connectors and then move on to layer 2. Check the VLANs, interfaces, trunks, spanning-tree, etc. When this is OK, check layer 3….IP addresses, routing, etc.
Let’s solve the next ticket!
Ticket 2
Here’s the ticket again:
Ccnp Tshoot Lab Manual Configuration Files In Linux Pdf
• Ticket #2: After fixing the issue with Client1 you receive another ticket that users from VLAN 10 are complaining that they are unable to connect to the FTP server.
Network Configuration Files In Linux
DHCP is working but it seems our clients are unable to reach the FTP server. This FTP server is in another subnet so traffic has to be routed. The first thing I would check is to see if they can reach their default gateway or not.
Cisco Packet Tracer Mobile 3.0 has been released by Cisco on may 12th, 2017. This is the fourfth Packet Tracer version released by Cisco for android and apple mobile devices. Cisco Packet Tracer Mobile 3.0 is still not available for windows phones. However, Packet Tracer 7.0 PC version is available and fully functionnal on Windows 10 tablets.
This mobile version is based on the new Cisco Packet Tracer 7.0 simulation engine including IoT capabilities and is thus compatible with Cisco Packet Tracer 6.3 and 7.0 labs. This new version also corrects bugs fonds in previous the previous Packet Tracer Mobile 2.1 version. Limitations and differences with Cisco Packet Tracer 7.0 desktop version can be found in the release notes available on Cisco netacad website. A free Cisco Networking Academy Netspace account is required to use the full features of the simulation software.
Packet Tracer mobile 3.0 requires Android > 4.2 on ARMv7 CPU tablets. User interface is optimized for screens with a minimum size of 7 inches and is as such difficultly usable (but working) on a phone.