Qn3 – OSPF (2 Points)

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#sh ip ospf database summary 134.56.78.48

           OSPF Router with ID (123.1.1.1) (Process ID 12345)

               Summary Net Link States (Area 0)

 Routing Bit Set on this LSA in topology Base with MTID 0

 LS age: 348
 Options: (No TOS-capability, DC, Upward)
 LS Type: Summary Links(Network)
 Link State ID: 134.56.78.48 (summary Network Number)
 Advertising Router: 123.3.3.3
 LS Seq Number: 80000045
 Checksum: 0x52D7
 Length: 28
  Network Mask: /29
       MTID: 0        Metric: 20

 Routing Bit Set on this LSA in topology Base with MTID 0

 LS age: 99
 Options: (No TOS-capability, DC, Upward)
 LS Type: Summary Links(Network)
 Link State ID: 134.56.78.48 (summary Network Number)
 Advertising Router: 123.5.5.5
 LS Seq Number: 80000045
 Checksum: 0x28FB
 Length: 28
 Network Mask: /29
       MTID: 0        Metric: 20

R1#traceroute 134.56.78.49

Type escape sequence to abort.

Tracing the route to 134.56.78.49
VRF info: (vrf in name/id, vrf out name/id)
 1 123.45.67.6 [MPLS: Label 21 Exp 0] 0 msec
   123.45.67.18 [MPLS: Label 21 Exp 0] 0 msec
   123.45.67.6 [MPLS: Label 21 Exp 0] 0 msec
 2 134.56.78.42 0 msec
   134.56.78.38 1 msec *

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

2. Check OSPF Neighbor is Normal

2.1. OSPF Neighbor Necessary Conditions

1. Hello/Dead time
 2. Area ID
3. Authentication
4. ACL
5. Passive Interface
6. Stub Area Flag

2.2. Other Factors

1. Interface Network Type

2. Don’t network the subnet

3. Check Routing and Load Balancing

1. Check COST on the OSPF interface
a. R21 e2/0
b. R22 e2/0
c. R3 e2/0
d. R5 e1/0
e. R1 e1/0, R1 e2/0
2. Check for the following command on OSPF configuration
#max-metric router-lsa
3. CIDR area 1 range 134.56.78.0 255.255.255.0

4. Resolve Data Transfer

1. Check whether there are any ACL deny

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

2 Check OSPF Interfaces for IP, COST, Network Type

R3 sh ip ospf int br Ensure OSPF is configured on all required
R5 interfaces
R21
R22
R1
R3 sh run e2/0 Check IP Address and Mask
R21 sh run e0/0 Check #ip ospf hello-interval
R22 Check #ip ospf cost
Check #ip ospf network point-to-
point

Fault 1: Incorrect network type on e2/0 of R22

Fault 2: The mask for 134.56.78.49 is 30. But, in

the diagram, it is /29

Fault 3: Hello-interval 11 on R3, e2/0

R5 sh run e1/0 Check IP Address and Mask

sh run e0/0 Check #ip ospf hello-interval
Check #ip ospf cost
Check #ip ospf network point-to-
point

R1 sh run e2/0 Check IP Address and Mask

sh run e1/0 Check #ip ospf hello-interval
Check #ip ospf cost

Fault 4: ip ospf cost 1

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

sh ip ospf neighbor /--Still no neighbor with R21--/

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

sh ip ospf database router 134.56.78.48 /--Check if it appears.

3 Check OFPS Configurations
R3 sh run | s r o Check whether router is stub (or nssa). If not, it
R5 is normal
R21 Check #passive-interface
R22 Check #area 1 range
R1 Check #max-metric router-lsa
Fault 5: #area range on R3
Fault 6: #passive-interface default
Fault 7: #max-metric router-lsa
Fix R21

router ospf 12345

no passive-interface E0/0
 sh ip ospf nei
Fix R3
router ospf 12345
no area 1 range 134.56.78.0 255.255.255.0

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

router ospf 12345

no max-metric router-lsa
clear ip route *

R1

sh ip route ospf /--Check whether 134.56.78.48 is load balancing. Also

check the cost (21 ?)--/

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

TS1 Q3 – OSPF Fault Summary and Remediation

# Device Fault Remediation

1 R22 Network Type Remove point-to-point network type from int config
2 R22 Network Mask Change network mask for 134.56.78.48 to 255.255.255.248
3 R3 Hello-Interval Remove hello-interval from int config
4 R1 OSPF Cost Remove ip ospf cost from interface e1/0
5 R1 route summary Remove #area range from router process
6 R21 Passive Interface Remove #passive-interface from ospf config
7 R21 OSPF Metric/Cost Remove #max-metric router-lsa from ospf process

Concepts
 The traffic from R1 to R22 must be load-balanced.
 First step is to make sure that the OSPF neighbors come up.