Get Smart with tshoot 300 135 pdf

It is more faster and easier to pass the Cisco cisco 300 135 exam by using High value Cisco Troubleshooting and Maintaining Cisco IP Networks (TSHOOT) questuins and answers. Immediate access to the Abreast of the times cisco 300 135 Exam and find the same core area tshoot 300 135 questions with professionally verified answers, then PASS your exam with a high score now.


The article at Testaimer.com going over http://www.testaimer.com/300-135-test is very comprehensive.

Q1. - (Topic 11) 

The implementations group has been using the test bed to do a ‘proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing scheme, DHCP services, NTP services, layer 2 connectivity, FHRP services, and device security, a trouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address. 

Use the supported commands to isolated the cause of this fault and answer the following questions. 

The fault condition is related to which technology? 

A. BGP 

B. NTP 

C. IP NAT 

D. IPv4 OSPF Routing 

E. IPv4 OSPF Redistribution 

F. IPv6 OSPF Routing 

G. IPv4 layer 3 security 

Answer:

Explanation: 

On R1, we need to permit IP 209.65.200.222/30 under the access list. 


Q2. - (Topic 20) 

The implementation group has been using the test bed to do an IPv6 'proof-of-concept1.

After several changes to the network addressing and routing schemes, a trouble ticket has been opened indicating that the loopback address on R1 (2026::111:1) is not able to ping the loopback address on DSW2 (2026::102:1).

Use the supported commands to isolate the cause of this fault and answer the following question.

On which device is the fault condition located?

A. R1

B. R2

C. R3

D. R4

E. DSW1

F. DSW2

G. ASW1

H. ASW2

Answer: D

Explanation:

Start to troubleshoot this by pinging the loopback IPv6 address of DSW2 (2026::102:1). This can be pinged from DSW1, and R4, but not R3 or any other devices past that point. If we look at the diagram, we see that R4 is redistributing the OSPF and RIP IPV6 routes. However, looking at the routing table we see that R4 has the 2026::102 network in the routing table known via RIP, but that R3 does not have the route:

When we look more closely at the configuration of R4, we see that it is redistributing OSPF routes into RIP for IPv6, but the RIP routes are not being redistributed into OSPF. That is why R3 sees R4 as an IPV6 OSPF neighbor, but does not get the 2026::102 network installed.

So, problem is with route redistribution on R4.


Q3. - (Topic 10) 

The implementations group has been using the test bed to do a ‘proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing scheme, DHCP services, NTP services, layer 2 connectivity, FHRP services, and device security, a trouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address. 

Use the supported commands to isolated the cause of this fault and answer the following questions. 

The fault condition is related to which technology? 

A. BGP 

B. NTP 

C. IP NAT 

D. IPv4 OSPF Routing 

E. IPv4 OSPF Redistribution 

F. IPv6 OSPF Routing 

G. IPv4 layer 3 security 

Answer:

Explanation: 

On R1 we need to add the client IP address for reachability to server to the access list that is used to specify which hosts get NATed. 

Topic 11, Ticket 6 : R1 ACL 

Topology Overview (Actual Troubleshooting lab design is for below network design) 

. Client Should have IP 10.2.1.3 

. EIGRP 100 is running between switch DSW1 & DSW2 

. OSPF (Process ID 1) is running between R1, R2, R3, R4 

. Network of OSPF is redistributed in EIGRP 

. BGP 65001 is configured on R1 with Webserver cloud AS 65002 

. HSRP is running between DSW1 & DSW2 Switches 

The company has created the test bed shown in the layer 2 and layer 3 topology exhibits. 

This network consists of four routers, two layer 3 switches and two layer 2 switches. 

In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1. 

DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary. 

R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the ISP's network. Because the company's address space is in the private range. 

R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and outside (209.65.0.0/24) network. 

ASW1 and ASW2 are layer 2 switches. 

NTP is enabled on all devices with 209.65.200.226 serving as the master clock source. 

The client workstations receive their IP address and default gateway via R4's DHCP server. 

The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1 and DSW2. 

In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6. 

DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE. 

The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the underlying IPv4 OSPF domain. Redistribution is enabled where necessary. 

Recently the implementation group has been using the test bed to do a ‘proof-of-concept' on several implementations. This involved changing the configuration on one or more of the devices. You will be presented with a series of trouble tickets related to issues introduced during these configurations. 

Note: Although trouble tickets have many similar fault indications, each ticket has its own issue and solution. 

Each ticket has 3 sub questions that need to be answered & topology remains same. 

Question-1 Fault is found on which device, 

Question-2 Fault condition is related to, 

Question-3 What exact problem is seen & what needs to be done for solution 

Client is unable to ping IP 209.65.200.241… 

Solution 

Steps need to follow as below:-

. When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4 

. Ipconfig ----- Client will be receiving IP address 10.2.1.3 

. IP 10.2.1.3 will be able to ping from R4 , R3, R2, R1 

. Look for BGP Neighbourship 

. Sh ip bgp summary ----- State of BGP will be in active state. This means connectivity issue between serial 

. Check for running config. i.e sh run --- over here check for access-list configured on interface as BGP is down (No need to check for NAT configuration as its configuration should be right as first need to bring BGP up) 

. In above snapshot we can see that access-list of edge_security on R1 is not allowing wan IP network 

. Change required: On R1, we need to permit IP 209.65.200.222/30 under the access list. 


Q4. - (Topic 17) 

The implementations group has been using the test bed to do a ‘proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing schemes, DHCP services, NTP services, layer 2 connectivity, FHRP services, and device security, a trouble ticket has been opened DSW1 will not become the active router for HSRP group 10. 

Use the supported commands to isolated the cause of this fault and answer the following questions. 

What is the solution to the fault condition? 

A. Under the interface vlan 10 configuration enter standby 10 preempt command. 

B. Under the track 1 object configuration delete the threshold metric up 1 down 2 command and enter the threshold metric up 61 down 62 command. 

C. Under the track 10 object configuration delete the threshold metric up 61 down 62 command and enter the threshold metric up 1 down 2 command. 

D. Under the interface vlan 10 configuration delete the standby 10 track1 decrement 60 command and enter the standby 10 track 10 decrement 60 command. 

Answer:

Explanation: 

On DSW1, related to HSRP, under VLAN 10 change the given track 1 command to instead use the track 10 command. 


Q5. - (Topic 21) 

The implementation group has been using the test bed to do an IPv6 'proof-of-concept1. After several changes to the network addressing and routing schemes, a trouble ticket has been opened indicating that the loopback address on R1 (2026::111:1) is not able to ping the loopback address on DSW2 (2026::102:1).

Use the supported commands to isolate the cause of this fault and answer the following question.

What is the solution to the fault condition?

A. Under the interface Tunnel34 configuration delete the tunnel mode ipv6 command.

B. Under the interface Serial0/0/0.34 configuration enter the ipv6 address 2026::34:1/122 command.

C. Under the interface Tunnel34 configuration enter the ip address unnumbered Serial0/0/0.34 command.

D. Under the interface Tunnel34 configuration delete the tunnel source Serial0/0/0.34 command and enter the tunnel source 2026::34:1/122 command.

Answer: A

Explanation:

As explained earlier, the problem is with route misconfigured tunnel modes on R3. R3 is using tunnel mode ipv6, while R4 is using the default of GRE. We need to remove the "tunnel mode ipv6" command under interface Tunnel34


Q6. - (Topic 15) 

The implementations group has been using the test bed to do a ‘proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing scheme, DHCP services, NTP services, layer 2 connectivity, FHRP services, and device security, a trouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address. 

Use the supported commands to isolated the cause of this fault and answer the following questions. 

On which device is the fault condition located? 

A. R1 

B. R2 

C. R3 

D. R4 

E. DSW1 

F. DSW2 

G. ASW1 

H. ASW2 

Answer:

Explanation: 

On DSW1, VALN ACL, Need to delete the VLAN access-map test1 whose action is to drop access-list 10; specifically 10.2.1.3 

Topic 16, Ticket 11 : IPV6 OSPF 

Topology Overview (Actual Troubleshooting lab design is for below network design) 

. Client Should have IP 10.2.1.3 

. EIGRP 100 is running between switch DSW1 & DSW2 

. OSPF (Process ID 1) is running between R1, R2, R3, R4 

. Network of OSPF is redistributed in EIGRP 

. BGP 65001 is configured on R1 with Webserver cloud AS 65002 

. HSRP is running between DSW1 & DSW2 Switches 

The company has created the test bed shown in the layer 2 and layer 3 topology exhibits. 

This network consists of four routers, two layer 3 switches and two layer 2 switches. 

In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1. 

DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary. 

R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the ISP's network. Because the company's address space is in the private range. 

R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and outside (209.65.0.0/24) network. 

ASW1 and ASW2 are layer 2 switches. 

NTP is enabled on all devices with 209.65.200.226 serving as the master clock source. 

The client workstations receive their IP address and default gateway via R4's DHCP server. 

The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1 and DSW2. 

In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6. 

DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE. 

The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the underlying IPv4 OSPF domain. Redistrution is enabled where necessary. 

Recently the implementation group has been using the test bed to do a ‘proof-of-concept' on several implementations. This involved changing the configuration on one or more of the devices. You will be presented with a series of trouble tickets related to issues introduced during these configurations. 

Note: Although trouble tickets have many similar fault indications, each ticket has its own issue and solution. 

Each ticket has 3 sub questions that need to be answered & topology remains same. 

Question-1 Fault is found on which device, 

Question-2 Fault condition is related to, 

Question-3 What exact problem is seen & what needs to be done for solution 

Solution 

Steps need to follow as below:-

. When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4 

ipconfig ----- Client will be receiving IP address 10.2.1.3 

. From Client PC we can ping 10.2.1.254…. 

. But IP 10.2.1.3 is able to ping from R4, R3, R2, R1. 

. Since the problem is R1 (2026::111:1) is not able to ping loopback of DSW1 (2026::102:1). 

. Kindly check for neighbourship of routers as IPV6…. As per design below neighbourship should be present for IPV6 

R1 ---R2 --- R3 --- R4--- DSW1 & DSW2 ----- Neighbourship between devices of IPV6 

R2 IPV6 OSPF neighbourship is with R1 

R3 IPV6 OSPF neighbourship is with R4 

. As per above snapshot we cannot see IPV6 neighbourship between R2 & R3 when checked interface configuration ipv6 ospf area 0 is missing on R2 which is connected to R3 

. Change required: On R2, IPV6 OSPF routing, Configuration is required to add ipv6 ospf 6 area 0 under interface serial 0/0/0.23 


Q7. - (Topic 1)

Exhibit:

A network administrator is troubleshooting an EIGRP connection between RouterA, IP address 10.1.2.1, and RouterB, IP address 10.1.2.2. Given the debug output on RouterA, which two statements are true? (Choose two.)

A. RouterA received a hello packet with mismatched autonomous system numbers.

B. RouterA received a hello packet with mismatched hello timers.

C. RouterA received a hello packet with mismatched authentication parameters.

D. RouterA received a hello packet with mismatched metric-calculation mechanisms.

E. RouterA will form an adjacency with RouterB.

F. RouterA will not form an adjacency with RouterB.

Answer: D,F


Q8. - (Topic 1)

Which statement is true about an IPsec/GRE tunnel?

A. The GRE tunnel source and destination addresses are specified within the IPsec transform set.

B. An IPsec/GRE tunnel must use IPsec tunnel mode.

C. GRE encapsulation occurs before the IPsec encryption process.

D. Crypto map ACL is not needed to match which traffic will be protected.

Answer: C

Topic 2, Troubleshooting VTP 

7. - (Topic 2) 

A customer network engineer has made configuration changes that have resulted in some loss of connectivity. You have been called in to evaluate a switch network and suggest resolutions to the problems. 

PC2 in VLAN 200 is unable to ping the gateway address 172.16.200.1; identify the issue. 

A. VTP domain name mismatch on SW4 

B. VLAN 200 not configured on SW1 

C. VLAN 200 not configured on SW2 

D. VLAN 200 not configured on SW4 

Answer:

Explanation: 

By looking at the configuration for SW2, we see that it is missing VLAN 200, and the "switchport access vlan 200" command is missing under interface eth 0/0: 

\\psf\Home\.Trash\Screen Shot 2014-10-18 at 9.56.12 PM.png 


Q9. - (Topic 2) 

A customer network engineer has made configuration changes that have resulted in some loss of connectivity. You have been called in to evaluate a switch network and suggest resolutions to the problems. 

You have configured PVST+ load balancing between SW1 and the New_Switch in such a way that both the links E2/2 and E2/3 are utilized for traffic flow, which component of the configuration is preventing PVST+ load balancing between SW1 and SW2 links 

A. Port priority configuration on SW1 

B. Port priority configuration on the New_Switch 

C. Path cost configuration on SW1 

D. Path cost configuration on the New_Switch 

Answer:

Explanation: 

Here is the configuration found on the New_Switch: 

This causes the port cost for link eth 1/3 to increase the path cost to 250 for all VLANs, making that link less preferred so that only eth 1/2 will be used. 

Topic 3, Troubleshooting EIGRP 

11. - (Topic 3) 

Scenario: 

You have been brought in to troubleshoot an EIGRP network. You have resolved the initial issue between routers R2 and R4, but another issue remains. You are to locate the problem and suggest solution to resolve the issue. 

The customer has disabled access to the show running-config command. 

The network segment between R2 and R4 has become disconnected from the remainder of the network. How should this issue be resolved? 

A. Change the autonomous system number in the remainder of the network to be consistent with R2 and R4. 

B. Move the 192.168.24.0 network to the EIGRP 1 routing process in R2 and R4. 

C. Enable the R2 and R4 router interfaces connected to the 192.168.24.0 network. 

D. Remove the distribute-list command from the EIGRP 200 routing process in R2. 

E. Remove the distribute-list command from the EIGRP 100 routing process in R2. 

Answer:

Explanation: 

When issuing the "show ip eigrp neighbor" command (which is about the only command that it lets you do in this question) you will see that all other routers are configured for EIGRP AS 1. However, the 192.16824.0 network between R2 and R4 is incorrectly configured for EIGRP AS 100: 


Q10. - (Topic 17) 

The implementations group has been using the test bed to do a ‘proof-of-concept' 

that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing schemes, DHCP services, NTP services, layer 2 connectivity, FHRP services, and device security, a trouble ticket has been opened DSW1 will not become the active router for HSRP group 10. 

Use the supported commands to isolated the cause of this fault and answer the following questions. 

The fault condition is related to which technology? 

A. NTP 

B. HSRP 

C. IP DHCP Helper 

D. IPv4 EIGRP Routing 

E. IPv6 RIP Routing 

F. IPv4 layer 3 security 

G. Switch-to-Switch Connectivity 

H. Loop Prevention 

I. Access Vlans 

Answer:

Explanation: 

On DSW1, related to HSRP, under VLAN 10 change the given track 1 command to instead use the track 10 command.