READ Free Dumps For Cisco- 300-135
| Question ID 15463 | 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?
|
| Option A | NTP
|
| Option B | IP DHCP Server
|
| Option C | IPv4 OSPF Routing
|
| Option D | IPv4 EIGRP Routing
|
| Option E | IPv4 Route Redistribution
|
| Option F | IPv6 OSPF Routing
|
| Correct Answer | D |
Explanation 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. Topic 15, Ticket 10 : VLAN Access Map 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 ISPs network. Because the companys 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 R4s 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
| Question ID 15464 | 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?
|
| Option A | R1
|
| Option B | R2
|
| Option C | R3
|
| Option D | R4
|
| Option E | DSW1
|
| Option F | DSW2
|
| Correct Answer | E |
Explanation 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