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.
Correct Answer: C
Explanation/Reference:
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)
o
Client Should have IP 10.2.1.3 o
EIGRP 100 is running between switch DSW1 & DSW2
o
OSPF (Process ID 1) is running between R1, R2, R3, R4
o
Network of OSPF is redistributed in EIGRP
o
BGP 65001 is configured on R1 with Webserver cloud AS 65002 o
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:-
1. 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
2. From Client PC we can ping 10.2.1.254….
3. But IP 10.2.1.3 is able to ping from R4, R3, R2, R1.
4. Since the problem is R1 (2026::111:1) is not able to ping loopback of DSW1 (2026::102:1).
5. 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
6. 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
7. Change required: On R2, IPV6 OSPF routing, Configuration is required to add ipv6 ospf 6 area 0 under interface serial 0/0/0.23
——————————————————————————————————————————
People, just D is correct. We are talking about troubleshooting, so identifying the issue, the first suspect is vacl filter per se, not its components, especially as the steps to troubleshoot in this exam are of the same importance as the troubleshooting per se. also why block just 1 ip (the 1.4) ? in the entire scenario it is in forward, so D is correct