QUESTION 76The 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 DSW1 will not become the active router for HSRP group 10.Use the supported commands to isolated the cause of this fault and answer the following questions.What is the solution to the fault condition?

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:

– When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4 ipconfig —– Client will be receiving Private IP address 169.254.X.X– From ASW1 we can ping 10.2.1.254….– On ASW1 VLAN10 is allowed in trunk & access command will is enabled on interface but DHCP IP address is not recd.On R4 DHCP ip address is not allowed for network 10.2.1.0/24 which clearly shows the problem lies on R4 & the problem is of DHCP

QUESTION 77The 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.On which device is the fault condition located?

A. R1B. R2C. R3D. R4E. DSW1F. DSW2G. ASW1H. ASW2

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

QUESTION 78The 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.The fault condition is related to which technology?

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

QUESTION 79The 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?

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

A. Remove “Passive interface” in Interface f0/1 and f0/0B. Disable auto summary on the EIGRP processC. Change the AS number on the EIGRP routing process from 1 to 10 to much the AS number used on DSW1 and DSW2D. 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.

QUESTION 85Drag and Drop QuestionsMatch the items on the left to their purpose on the right

Answer:

Ticket 15 : IPv6 GRE TunnelTROUBLE TICKET STATEMENT: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.show runStart 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 routing table of R3, we see that there is no OSPF neighbor to R4:

This is due to mismatched tunnel modes between R3 and R4:

Problem is with R3, and to resolve the issue we should delete the “tunnel mode ipv6” under interface Tunnel 34.

Ticket 16 : IPv6 RIPng OSPFv3 RedistributionTROUBLE TICKET STATEMENT: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.show runStart 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.