[Free] 2018(Jan) EnsurePass Pass4sure Cisco 300-135 Dumps with VCE and PDF 41-50

Ensurepass.com : Ensure you pass the IT Exams
2018 Jan Cisco Official New Released 300-135
100% Free Download! 100% Pass Guaranteed!
http://www.EnsurePass.com/300-135.html

Troubleshooting and Maintaining Cisco IP Networks (TSHOOT)

Question No: 41 – (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 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 isolated the cause of this fault and answer the following questions.

On which device is the fault condition located?

1. R1

2. R2

3. R3

4. R4

5. DSW1

6. DSW2

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

Question No: 42 – (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?

1. BGP

2. NTP

3. IP NAT

4. IPv4 OSPF Routing

5. IPv4 OSPF Redistribution

6. IPv6 OSPF Routing

7. IPv4 layer 3 security

Answer: C 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 amp; 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 amp; 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 amp; 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 amp; 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 amp; 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 amp; 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.

Question No: 43 – (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.

What is the solution to the fault condition?

1. Under the interface Serial0/0/1 enter the ip access-group edge_security out command.

2. Under the ip access-list extended edge_security configuration add the permit ip 209.65.200.224 0.0.0.3 any command.

3. Under the ip access-list extended edge_security configuration delete the deny ip

   10.0.0.0.0 0.255.255.255 any command.

4. Under the interface Serial0/0/0 configuration delete the ip access-group edge_security in command and enter the ip access-group edge_security out command.

Answer: B Explanation:

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

Question No: 44 – (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.

On which device is the fault condition located?

1. R1

2. R2

3. R3

4. R4

5. DSW1

6. DSW2

7. ASW1

Answer: A Explanation:

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

Question No: 45 – (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?

1. BGP

2. NTP

3. IP NAT

4. IPv4 OSPF Routing

5. IPv4 OSPF Redistribution

6. IPv6 OSPF Routing

7. IPv4 layer 3 security

Answer: G Explanation:

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

Topic 12, Ticket 7 : Port Security

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 amp; 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 amp; 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 amp; 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 amp; 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 amp; 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 amp; 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 amp; Fa1/0/2 access port VLAN 10 was assigned but when we checked interface it was showing down

Sh run —- check for running config of int fa1/0/1 amp; fa1/0/2 (switchport access Vlan 10 will be there with switch

port security command). Now check as below Sh int fa1/0/1 amp; sh int fa1/0/2

-> As seen on interface the port is in err-disable mode so need to clear port.

-> Change required: On ASW1, we need to remove port-security under interface fa1/0/1 amp; fa1/0/2.

————————————————————-

—

Question No: 46 – (Topic 12)

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?

1. NTP

2. Switch-to-Switch Connectivity

3. Access Vlans

4. Port Security

5. VLAN ACL / Port ACL

6. Switch Virtual Interface

Answer: D

Explanation: Port security is causing the connectivity issues. On ASW1, we need to remove port-security under interface fa1/0/1 amp; fa1/0/2.

Question No: 47 – (Topic 12)

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?

1. R1

2. R2

3. R3

4. R4

5. DSW1

6. DSW2

7. ASW1

8. ASW2

Answer: G Explanation:

port security needs is configured on ASW1.

Question No: 48 – (Topic 12)

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.

What is the solution to the fault condition?

1. In Configuration mode, using the interface range Fa 1/0/1 – 2, then no switchport port- security interface configuration commands. Then in exec mode clear errdisable interface fa 1/01 – 2 vlan 10 command

2. In Configuration mode, using the interface range Fa 1/0/1 – 2, then no switchport port- security, followed by shutdown, no shutdown interface configuration commands.

3. In Configuration mode, using the interface range Fa 1/0/1 – 2, then no switchport port- security interface configuration commands.

4. In Configuration mode, using the interface range Fa 1/0/1 – 2, then no switchport port- security interface configuration commands. Then in exec mode clear errdisable interface fa 1/0/1, then clear errdisable interface fa 1/0/2 commands.

Answer: B Explanation:

On ASW1, we need to remove port-security under interface fa1/0/1 amp; fa1/0/2.

Reference: http://www.cisco.com/en/US/tech/ABC389/ABC621/technologies_tech_note09186a00806c d87b.shtml

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

==========

Topic 13, Ticket 8 : Redistribution of EIGRP to 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 amp; 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 amp; 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 amp; 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 amp; 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 amp; 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 amp; 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 , but cannot ping from R3, R2, R1

-> This clearly shows problem at R4 since EIGRP is between DSW1, DSW2 amp; R4 and OSPF protocol is running between R4, R3, R2, R1 so routes from R4 are not propagated to R3, R2, R1

-> Since R4 is able to ping 10.2.1.3 it means that routes are received in EIGRP amp; same needs to be advertised in OSPF to ping from R3, R2, R1.

-> Need to check the routes are being advertised properly or not in OSPF amp; EIGRP

vice-versa.

-> From above snap shot it clearly indicates that redistribution done in EIGRP is having problem amp; by default all routes are denied from ospf to EIGRP… so need to change route-map name.

-> Change required: On R4, in the redistribution of EIGRP routing protocol, we need to change name of route-map to resolve the issue. It references route-map OSPF_to_EIGRP but the actual route map is called OSPF-gt;EIGRP.

————————————————————-

—

Question No: 49 – (Topic 13)

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?

1. NTP

2. IP DHCP Server

3. IPv4 OSPF Routing

4. IPv4 EIGRP Routing

5. IPv4 Route Redistribution

6. IPv6 RIP Routing

7. IPv6 OSPF Routing

8. IPv4 and IPv6 Interoperability

9. IPv4 layer 3 security

Answer: E Explanation:

On R4, in the redistribution of EIGRP routing protocol, we need to change name of route- map to resolve the issue. It references route-map OSPF_to_EIGRP but the actual route map is called OSPF-gt;EIGRP.

Question No: 50 – (Topic 13)

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.

Which is the solution to the fault condition?

1. Under the EIGRP process, delete the redistribute ospf 1 route-map OSPF_ to_ EIGRP command and enter the redistribute ospf 1 route-map OSPF – gt; EIGRP command.

2. Under the EIGRP process, delete the redistribute ospf 1 route-map OSPF_ to_ EIGRP command and enter the redistribute ospf 6 metric route-map OSPF – gt; EIGRP command.

3. Under the OSPF process, delete the redistribute eigrp10 subnets route-map EIGPR –

   gt;OSPF command and enter the redistribute eigrp10 subnets route-map OSPF – gt; EIGRP command.

4. Under the OSPF process, delete the redistribute eigrp10 subnets route-map EIGPR –

   gt;OSPF command and enter the redistribute eigrp10 subnets route-map EIGPR – gt; OSPF command.

5. Under the EIGRP process, delete the redistribute ospf 1 route-map OSPF _to_ EIGRP command and enter redistribute ospf 1 metric 100000 100 100 1 15000 route_ map OSPF

_to _EIGRP command

Answer: A Explanation:

On R4, in the redistribution of EIGRP routing protocol, we need to change name of route- map to resolve the issue. It references route-map OSPF_to_EIGRP but the actual route map is called OSPF-gt;EIGRP.

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

==========

100% Ensurepass Free Download!
–Download Free Demo:300-135 Demo PDF
100% Ensurepass Free Guaranteed!
–300-135 Dumps

	EnsurePass	ExamCollection	Testking
Lowest Price Guarantee	Yes	No	No
Up-to-Dated	Yes	No	No
Real Questions	Yes	No	No
Explanation	Yes	No	No
PDF VCE	Yes	No	No
Free VCE Simulator	Yes	No	No
Instant Download	Yes	No	No