Hello,
In this case, we found that the keywords needed to be added when IBGP was imported into OSPF.
Problem Details
In the scenario we have three routers, AR1 runs only OSPF, and AR2 and AR3 run both OSPF and iBGP. The default route is advertised in BGP on AR3 and BGP is imported to OSPF on AR2. However, there is not a default route in the routing table of AR1.
Process
1. Check the BGP routing table on the AR2, it's confirmed that the default route was received from AR3.
<AR2>display bgp routing-table peer 33.33.33.33 received-routes
BGP Local router ID is 22.22.22.22
Status codes: * - valid, > - best, d -damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? -incomplete
Total Number of Routes: 1
Network NextHop MED LocPrf PrefVal Path/Ogn
*>i 0.0.0.0 33.33.33.33 0 100 0 i
2. Check the import configuration.
3. Check the OSPF routing table on AR1, the default route is not received.
Solution
On a non-PE device, only EBGP routes are imported after the import-route bgp command is configured. IBGP routes are also imported after the import-route bgp permit-ibgp command is configured.
See https://support.huawei.com/hedex/hdx.do?docid=EDOC1000163385&id=import-route_ospf_1&lang=en
So the command should change to:
[AR2-ospf-1]import-route bgp permit-ibgp
Furthermore, the import-route command cannot be used to import a default route from another AS. To advertise a non-OSPF default route in a common OSPF area, run the default-route-advertise command on the ASBR
[AR2-ospf-1]default-route-advertise
After the modification, AR1 can receive the default route.
