Professional Documents
Culture Documents
Q3 - Ospf
Q3 - Ospf
Q3 - Ospf
When R1 tries to access the network 123.45.67.48/29, which is between R21 and R22, the
traffic should be load balanced as shown in the exhibit.
R1#traceroute 134.56.78.49
Strategy
1. Check Each Connection can Ping and the Mask is correct
1. Check each interface status and IP address, and subnet mask.
NOTE: The link between R21 and R22 is 255.255.255.248
1. Hello/Dead time
2. Area ID
3. Authentication
4. ACL
5. Passive Interface
6. Stub Area Flag
ANS Q3 – OSPF
# Device Commands Validations
1 Perform Initial Test
R1 sh ip ospf database
summary
R3 sh ip ospf nei IP address of e2/0 as 134.56.78.37 is normal
Found only 1 neighbor to R1. There is no
neighbor with R21. Check direct connected
interface
R1 sh ip ospf nei Three neighbors (R2, R3, R5) must appear with
following neighbor IDs:
123.5.5.5, 123.3.3.3, 123.2.2.2
R5 sh ip ospf neighbor If two neighbors, it is is normal
R21 sh ip ospf neighbor No neighbors to R3 is an issue
R22 sh ip ospf neighbor FULL/ - means mismatch network type
Fix R1
int e/0
no ip ospf cost 1
clear ip route *
sh ip route ospf /--Check whether 134.56.78.48 is load balancing.
Fix R3
int e2/0
no ip ospf hello-interval 11
Fix R22
int 2/0
ip address 134.56.78.49 255.255.255.248
Fix R22
int e0/0
no ip ospf network point-to-point
R5
R1
sh ip ospf database summary
/-- If 134.56.78.48 with /29 from R3 shows up, that entry is normal. There
may be is still an issue with the first entry, which is supposed to be from R5 -/
Fix R21
R1
T Perform Testing
R1 sh ip route ospf 134.56.78.48/29 should be load balanced
R1 sh ip ospf database
summary
tr 134.56.78.49
Troubleshooting Tips
R1 sh ip route If 123.45.67.48/29 missing on the routing table,
problem could be with OSPF interface
R1 sh ip ospf database If 134.56.78.0 present with /24, from R3, need
summary to remove #area range from R3
R1 sh ip ospf database The prefix must be coming from both R3 and R5
summary 134.56.78.48
R5 sh ip ospf database Check whether 134.56.78.48 is coming from R3
R5 sh ip ospf database The prefix could be coming from both R3. Also
summary 134.56.78.48 check whether the prefix is Router LSA
R5 sh ip route Two entries may appear
O IA 134.56.78.48/29 via 123.45.67.17, E0/0
O 134.56.78.48/30 via 134.56.78.42, E1/0
R3 sh ip route ospf Metric 65545 from R3 is the fault. Question says
it needs to be 20
R22 sh ip ospf nei Ensure no Problems with R5. Missing neighbor
to R21 is OK
R22 sh ip ospf int br Check the State. If P2P, Fault 4 is confirmed
Check whether the mask for 134.56.78.49 is 30.
R21 sh ip route ospf 134.56.78.48 [110/65545] confirms the issue
R21 sh run | s r o All of the metric 65545 confirms the issue
Concepts
The traffic from R1 to R22 must be load-balanced.
First step is to make sure that the OSPF neighbors come up.