The Rebirth Guide To 300-135 pdf

300-135 Dumps

300-135 Exam Questions - Online Test

300-135 Premium VCE File

Learn More 100% Pass Guarantee - Dumps Verified - Instant Download
150 Lectures, 20 Hours

We provide real 300 135 tshoot exam questions and answers braindumps in two formats. Download PDF & Practice Tests. Pass Cisco 300 135 tshoot pdf Exam quickly & easily. The 300 135 dumps PDF type is available for reading and printing. You can print more and practice many times. With the help of our Cisco ccnp 300 135 dumps pdf and vce product and material, you can easily pass the ccnp tshoot 300 135 pdf exam.

Q1. - (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.

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

Q3. - (Topic 18)

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 indicating that Client 1 cannot ping the 209.65.200.241

address.

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 global configuration, delete the no ip dhcp use vrf connected command.

B. Under the IP DHCP pool configuration, delete the default -router 10.2.1.254 command and enter the default-router 10.1.4.5 command.

C. Under the IP DHCP pool configuration, delete the network 10.2.1.0 255.255.255.0 command and enter the network 10.1.4.0 255.255.255.0 command.

D. Under the IP DHCP pool configuration, issue the no ip dhcp excluded-address 10.2.1.1

10.2.1.253 command and enter the ip dhcp excluded-address 10.2.1.1 10.2.1.2 command.

Answer: D

Explanation:

On R4 the DHCP IP address is not allowed for network 10.2.1.0/24 which clearly shows the problem lies on R4 & the problem is with DHCP

Q4. - (Topic 10)

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

Answer: A

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.

Q5. - (Topic 9)

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

Answer: A

Explanation:

The BGP neighbor statement is wrong on R1.

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.

The fault condition is related to which technology?

A. Under the global configuration mode enter no access-list 10 command.

B. Under the global configuration mode enter no access-map vlan 10 command.

C. Under the global configuration mode enter no vlan access-map test1 10 command.

D. Under the global configuration mode enter no vlan filter test1 vlan-list 10 command.

Answer: C

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

Q7. - (Topic 16)

The implementations group has been using the test bed to do a ‘proof-of-concept'. After several changes to the network addressing, 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 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: B

Explanation:

R2 is missing the needed IPV6 OSPF for interface s0/0/0.23

Topic 17, Ticket 12 : HSRP Issue

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

. Since the problem is raised that DSW1 will not become active router for HSRP group 10

. we will check for the HSRP configuration…

. From snapshot we see that the track command given needs to be changed under active VLAN10 router

. Change Required: On DSW1, related to HSRP, under vlan 10 change the given track 1 command to instead use the track 10 command.

Q8. - (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.

Q9. - (Topic 5)

Scenario:

A customer network engineer has edited their OSPF network configuration and now your customer is experiencing network issues. They have contacted you to resolve the issues and return the network to full functionality.

After resolving the issues between R3 and R4. Area 2 is still experiencing routing issues. Based on the current router configurations, what needs to be resolved for routes to the networks behind R5 to be seen in the company intranet?

A. Configure R4 and R5 to use MD5 authentication on the Ethernet interfaces that connect to the common subnet.

B. Configure Area 1 in both R4 and R5 to use MD5 authentication.

C. Add ip ospf authentication-key 7 BEST to the R4 Ethernet interface that connects to R5 and ip ospf authentication-key 7 BEST to R5 Ethernet interface that connects to R4.

D. Add ip ospf authentication-key CISCO to R4 Ethernet 0/1 and add area 2 authentication to the R4 OSPF routing process.

Answer: D

Explanation:

Here, we see from the running configuration of R5 that OSPF authentication has been configured on the link to R4:

However, this has not been done on the link to R5 on R4:

Q10. - (Topic 19)

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

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 SerialO/0/0.23 configuration enter the ipv6 ospf 6 area 0 command.

B. Under the interface SerialO/0/0.12 configuration enter the ipv6 ospf 6 area 12 command.

C. Under ipv6 router ospf 6 configuration enter the network 2026::1:/122 area 0 command.

D. Under ipv6 router ospf 6 configuration enter the no passive-interface default command

Answer: A

Explanation:

As explained in question one of this ticket, we can then see that OSPFv3 has not been enabled on the interface to R3:

So the problem is with R2, related to IPV6 Routing, and the fix is to enable the "ipv6 ospf 6 area 0"command under the serial 0/0/0.23 interface. We need to enable this interface for area 0 according to the topology diagram.

Topic 20, Ticket 15: IPv6 Routing Issue 2

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

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