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

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

QUESTION 73The 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.What is the solution to fault condition?

Ticket 12 : HSRP IssueTopology 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 SwitchesThe 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 solutionSolution:Steps need to follow as below:Since the problem is raised that DSW1 will not become active router for HSRP group 0 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.

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

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

Answer: EExplanation:DSW references the wrong track ID number.

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

Answer: BExplanation:On DSW1, related to HSRP, under VLAN 10 change the given track 1 command to instead use the track 10 command.

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?

Answer: DExplanation:On DSW1, related to HSRP, under VLAN 10 change the given track 1 command to instead use the track 10 command.

Ticket 13 : DHCP IssueTopology 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 SwitchesThe 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 solutionSolution:– 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?

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

Ticket 14 : EIGRP Passive InterfaceTopology 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 SwitchesThe 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 solutionThe neighborship between R4 and DSW1 wasn’t established. Client 1 can’t ping R4 TheConfiguration on R4router eigrp 10passive-interface defaultredistribute ospf 1 route-map OSPF->EIGRP network 10.1.4.4 0.0.0.3network 10.1.4.8 0.0.0.3default-metric 10000 100 255 1 10000no auto-summary