642-832 Troubleshooting and Maintaing Cisco IP Networks (Exam 2)

(Ticket 3: OSPF Authentication)Scenario: The implementation group has been using the test bed to do a 'proof-of-concept' that requires bothClient 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the networkaddressing, routing schemes, DHCP services, layer 2 connectivity, FHRP services, and, device security, atrouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address.Figure 1Figure 2Use the supported commands to isolate the cause of this fault and answer the following questions.Configuration on R1 and R2The fault condition is related to which techonology?

IPv6 OSPF Routing

IPv4 OSPF Redistribution

IPv4 layer 3 security

BGP

IP NAT

NTP

IPv4 OSPF Routing

The implementations group has been using the test bed to do a `proof-of-concept' t...

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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.What is the solution to the fault condition?

(Ticket 6: ACL)Scenario: The implementation group has been using the test bed to do a 'proof-of-concept' that requires bothClient 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the networkaddressing, routing schemes, DHCP services, layer 2 connectivity, FHRP services, and, device security, atrouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address.Figure 1Figure 2Trouble Ticket StatementConfiguration on R1On Which device is the fault condition located?

DSW2

DSW1

ASW1

R1

R3

R2

R4

The implementations group has been using the test bed to do a `proof-of-concept' t...

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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.What is the solution to the fault condition?

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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.What is the solution to the fault condition?

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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.What is the solution to the fault condition?

Under the interface Serial0/0/1 enter the ip access-group edge_security out command.

Under the interface Serial0/0/0 configuration delete the ip access-group edge_security in command andenter the ip access-group edge_security out command.

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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.What is the solution to the fault condition?

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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?

IPv6 RIP Routing

IPv4 Route Redistribution

IPv6 OSPF Routing

NTP

IPv4 and IPv6 InteroperabilityI. IPv4 layer 3 security

IPv4 OSPF Routing

IP DHCP Server

IPv4 EIGRP Routing

The implementations group has been using the test bed to do a `proof-of-concept' t...

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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.Which is the solution to the fault condition?

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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.What is the solution to the fault condition?

Disable auto summary on the EIGRP process

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.252 and 10.1.4.8 0.0.0.252 commands.

Enable EIGRP on the FastEthernet0/0 and FastEthernet0/1 interface using the no passive- interfacecommand.

Change the AS number on the EIGRP routing process from 1 to 10 to much the AS number used on DSW1and DSW2.

The implementations group has been using the test bed to do a `proof-of-concept' t...

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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?

The implementations group has been using the test bed to do a `proof-of-concept'. After several changes to thenetwork addressing, routing schemes, a trouble ticket has been opened indicating that the loopback address onR1 (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?

NTP

IPv4 layer 3 security

IPv4 OSPF Routing

IPv6 OSPF Routing

The implementations group has been using the test bed to do a `proof-of-concept'. ...

The implementations group has been using the test bed to do a `proof-of-concept'. After several changes to thenetwork addressing, routing schemes, a trouble ticket has been opened indicating that the loopback address onR1 (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?

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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?

IPv4 layer 3 security

IPv6 RIP Routing

Switch-to-Switch Connectivity

NTP

Loop PreventionI. Access Vlans

IP DHCP Helper

HSRP

IPv4 EIGRP Routing

The implementations group has been using the test bed to do a `proof-of-concept' t...

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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 implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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?

Ipv6 RIP Routing

Ipv4 Route Redistribution.

Ipv6 OSPF Routing

NTP

Ipv4 and Ipv6 InteroperabilityI. Ipv4 layer 3 security.

Ipv4 OSPF Routing

IP DHCP Server

Ipv4 EIGRP Routing.

The implementations group has been using the test bed to do a `proof-of-concept' t...

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1and 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, atrouble 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?

Under the global configuration, delete the no ip dhcp use vrf connected command.

% LINK-3-UPDOWN: Interface Serial0/0, change state to up% LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0, changed state to upRefer to te graphic shown above. whate statement is correct regarding the output shown in the graphic?

These two log messages will not have serverity level. They are not erros but are just informationalmessages.

The second message would be shown if the logging console warning command had been issued.

The first log message is an error message with a severity level of 3.

The first log message is categorized as a warning message.

These messages regarding interface status are normal output and will always be displayed when you exitconfig mode.