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. IPv4 layer 3 security
• B. NTP
• C. IPv4 OSPF Routing
• D. IP NAT
• E. IPv6 OSPF Routing
• F. IPv4 OSPF Redistribution
• G. BGP

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 isolate the cause of this fault and answer the following question.
On which device is the fault condition located?

• A. R3
• B. R4
• C. ASW1
• D. ASW2
• E. DSW2
• F. R1
• G. DSW1
• H. R2

The following command is issued on a Cisco Router:
Router(configuration)#logging console warnings
Which alerts will be seen on the console?

• A. warnings, errors, critical, alerts
• B. Warnings only
• C. notifications, warnings, errors
• D. debugging, informational, notifications, warnings
• E. warnings, errors, critical, alerts, emergencies

說明：（僅 Fast2test 成員可見）

What is the result of configuring the logging console warning command?

• A. Warning, error, critical, and informational messages will be logged on the console.
• B. The logging console warning command needs to be followed in the configuration with logging buffered byte size to specify the message buffer size for the console.
• C. Warning, critical, alert, and emergency messages will be logged on the console.
• D. Messages with a severity level of 4 and higher will be logged to all available TTY lines.
• E. Only warning messages will be logged on the console.

Topic 14, Ticket 12 : HSRP Issue
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
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:
Since the problem is raised that DSW1 will not become active router for HSRP group 10
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. & use track 10 command.


So in ticket Answer to the fault condition will be as below for