[Refresh] tshoot 300 135 pdf

Exam Code: ccnp tshoot 300 135 dumps pdf (Practice Exam Latest Test Questions VCE PDF)
Exam Name: Troubleshooting and Maintaining Cisco IP Networks (TSHOOT)
Certification Provider: Cisco
Free Today! Guaranteed Training- Pass tshoot 300 135 pdf Exam.

♥♥ 2021 NEW RECOMMEND ♥♥

Free VCE & PDF File for Cisco 300-135 Real Exam (Full Version!)

★ Pass on Your First TRY ★ 100% Money Back Guarantee ★ Realistic Practice Exam Questions

Free Instant Download NEW 300-135 Exam Dumps (PDF & VCE):
Available on: http://www.surepassexam.com/300-135-exam-dumps.html

Q1. - (Topic 19)

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.

The fault condition is related to which technology?

A. NTP

B. IPv4 OSPF Routing

C. IPv6 OSPF Routing

D. IPv4 layer 3 security

Answer: C

Explanation:

Since we are unable to ping the IPv6 address, the problem is with IPv6 OSPF Routing.

Q2. - (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: E

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

Q3. - (Topic 14)

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. Disable auto summary on the EIGRP process

B. Enable EIGRP on the FastEthernet0/0 and FastEthernet0/1 interface using the no passive-interface command.

C. Change the AS number on the EIGRP routing process from 1 to 10 to much the AS number used on DSW1 and DSW2.

D. Under the EIGRP process, delete the network 10.1.4.0 0.0.0.255 command and enter the network 10.1.4.4 0.0.0.252 and 10.1.4.8 0.0.0.252 commands.

Answer: C

Explanation:

On R4, IPV4 EIGRP Routing, need to change the EIGRP AS number from 1 to 10 since DSW1 & DSW2 is configured to be in EIGRP AS number 10.

Q4. - (Topic 14)

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: D

Explanation:

The EIGRP AS number configured on R4 is wrong.

Q5. - (Topic 7)

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. In Configuration mode, using the interface range Fastethernet 1/0/1 – 2, then switchport mode access vlan 10 command.

B. In Configuration mode, using the interface range Fastethernet 1/0/1 – 2, then switchport access mode vlan 10 command.

C. In Configuration mode, using the interface range Fastethernet 1/0/1 – 2, then switchport vlan 10 access command.

D. In Configuration mode, using the interface range Fastethernet 1/0/1 – 2, then switchport access vlan 10 command.

Answer: D

Explanation:

The problem here is that VLAN 10 is not configured on the proper interfaces on switch ASW1.

Q6. - (Topic 9)

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 BGP process, enter the bgp redistribute-internal command.

B. Under the BGP process, bgp confederation identifier 65001command.

C. Deleted the current BGP process and reenter all of the command using 65002 as the AS number.

D. Under the BGP process, delete the neighbor 209.56.200.226 remote-as 65002 command and enter the neighbor 209.65.200.226 remote-as 65002 command.

Answer: D

Explanation:

On R1 under router BGP change neighbor 209.56.200.226 remote-as 65002 statement to neighbor 209.65.200.226 remote-as 65002

Topic 10, Ticket 5 : NAT 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. Redistrution is enabled where necessary.

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 established state & will be able to receive I prefix (209.65.200.241)

. As per troubleshooting we are able to ping ip 10.2.1.3 from R1 & BGP is also receiving prefix of webserver & we are able to ping the same from R1. Further troubleshooting needs to be done on R1 on serial 0/0/1

. Check for running config. i.e sh run for interface serial 0/0/1..

From above snapshot we are able to see that IP needs to be PAT to serial 0/0/1 to reach web server IP (209.65.200.241). But in access-list of NAT IP allowed IP is 10.1.0.0/16 is allowed & need 10.2.0.0 /16 to

. As per troubleshooting we are able to ping ip 10.2.1.3 from R1 & BGP is also receiving prefix of web server & we are able to ping the same from R1. Its should be checked further for running config of interface for stopping

. Change required: 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.

Q7. - (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: D

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: B

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:

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)

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: C

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:

\psfHome.TrashScreen Shot 2014-10-18 at 9.56.12 PM.png

Q9. - (Topic 3)

You have been brought in to troubleshoot an EIGRP network. A network engineer has made configuration changes to the network rendering some locations unreachable. You are to locate the problem and suggest solution to resolve the issue.

R5 has become partially isolated from the remainder of the network. R5 can reach devices on directly connected networks but nothing else. What is causing the problem?

A. An outbound distribute list in R3

B. Inbound distribute lists in R5

C. An outbound distribute list in R6

D. Incorrect EIGRP routing process ID in R5

Answer: B

Explanation:

Here we see that distribute list 3 has been applied to EIGRP on router R%, but access-list 3 contains only deny statements so this will effectively block all routing advertisements from its two EIGRP neighbors, thus isolating R5 from the rest of the EIGRP network:

Topic 4, Troubleshooting HSRP

13. - (Topic 4)

Scenario:

You have been asked by your customer to help resolve issues in their routed network. Their network engineer has deployed HSRP. On closer inspection HSRP doesn't appear to be operating properly and it appears there are other network problems as well. You are to provide solutions to all the network problems.

Examine the configuration on R4. The routing table shows no entries for 172.16.10.0/24 and 172.16.20.0/24. Identify which of the following is the issue preventing route entries being installed on R4 routing table?

A. HSRP issue between R4 and R2

B. This is an OSPF issue between R4 and R2

C. This is a DHCP issue between R4 and R2

D. The distribute-list configured on R4 is blocking route entries

E. The ACL configured on R4 is blocking inbound traffic on the interface connected to R2

Answer: D

Explanation:

If we look at the configuration on R4 we see that there is a distribute list applied to OSPF, which blocks the 172.16.20.0/24 and 172.16.10.0/24 networks.

Q10. - (Topic 6)

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, and FHRP services, 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. NTP

B. Switch-to-Switch Connectivity

C. Access Vlans

D. Port Security

E. VLAN ACL / Port ACL

F. Switch Virtual Interface

Answer: B

Explanation:

Since the Clients are getting an APIPA we know that DHCP is not working. However, upon closer examination of the ASW1 configuration we can see that the problem is not with DHCP, but the fact that the trunks on the port channels are only allowing VLANs 1-9, when the clients belong to VLAN 10. VLAN 10 is not traversing the trunk on ASW1, so the problem is with switch to switch connectivity, specifically the trunk configuration on ASW1.

Topic 7, Ticket 2 : ACCESS VLAN

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.

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 getting 169.X.X.X

. On ASW1 port Fa1/0/ 1 & Fa1/0/2 access port VLAN 10 was assigned which is using IP address 10.2.1.0/24

Sh run ------- & check for running config of int fa1/0/1 & fa1/0/2

====================================================

. Here we are not able to see access Vlan10 configured for Port Fa1/0/1 & Fa1/0/2

. Change required: On ASW1, for configuring Access Vlan under interface fa1/0/1 & 1/0/2 we have to enable command switchport access vlan 10

To see all sample questions go to: 300-135 Exam dumps

Related 300-135 posts: