Explanation/Reference:
Explanation:
The problem here is that VLAN 10 is not configured on the proper interfaces on switch ASW1.
Testlet 1
Topic 8, Ticket 3 : OSPF Authentication
Topology Overview (Actual Troubleshooting lab design is for below network design) oClient Should have IP 10.2.1.3
oEIGRP 100 is running between switch DSW1 & DSW2
oOSPF (Process ID 1) is running between R1, R2, R3, R4
oNetwork of OSPF is redistributed in EIGRP
oBGP 65001 is configured on R1 with Webserver cloud AS 65002
oHSRP 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


Client is unable to ping IP 209.65.200.241
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.IP 10.2.1.3 will be able to ping from R4 , R3, R2 but not from R1

3.Check for neighborship of ospf
sh ip ospf nei ----- Only one neighborship is forming with R2 & i.e. with R3 Since R2 is connected to R1 & R3 with routing protocol ospf than there should be 2 neighbors seen but only one is seen
4.Need to check running config of R2 & R3 for interface
Sh run -------------------------- Interface Serial0/0/0/0.12 on R2

Sh run -------------------------- Interface Serial0/0/0/0 on R1
.Change required: On R1, for IPV4 authentication of OSPF command is missing and required
5
to configure------ ip ospf authentication message-digest