AR169 is not accepting exported routes via OSPF
Created: Nov 17, 2021 08:18:35Latest reply: Nov 18, 2021 13:08:58
220
8
0
0
0
Rewarded HiCoins：
0
(problem resolved)
Hi,
Our customer has multiple sites connecting each other via VPLS.
They run OSPF to exchange their LAN subnets.
Also each site have static routes points a device in their LAN. They are exporting these static routes to OSPF.
All sites have Juniper except 1 site which has AR169.
Juniper has all exported static routes including the ones exported by Huawei.
But Huawei doesn't have these exported static routes. They are not even in LSDB of the Huawei.
Weirdly enough it has these empty entries in its routing table.
No filter is configured.
I followed the below
On the 5th step it says if it is not in LSDB contact support, I don't have support contract.
Any thoughts much appreciated.
Thanks.
- x
- convention：
- Emotion(0)
Featured Answers
fuzi_yao
Reply alicenahi Created Nov 17, 2021 09:03:16
(0)
(0)
alright, Is a VPN instance bound to your interface? Check whether a VPN instance is configured for the static route. Also, what is the specific version of your device? All I can think of is these configuration problems. If the configuration is correct, the compatibility between the two vendors cannot be ruled out.
alicenahi
Reply fuzi_yao Created Nov 17, 2021 09:20:29
(0)
(0)
Yes, all configuration exist as you said. All ospf neighborships are up. To make a summary Huawei sends its static routes to Juniper via OSPF and Juniper accepts it. Juniper sends its static routers to Huawei but it doesn't accept it (It accepts the other routes, like the loopback address of the Juniper) I am starting to believe it is a compatibility issue too.
fuzi_yao
Reply alicenahi Created Nov 17, 2021 09:48:09
(1)
(0)
Add the following command to the OSPF process and run the vpn-instance-capability simple command to ignore the VPN check in the OSPF process: The root cause is that OSPF on the local device is bound to a VPN instance. Therefore, the local device checks the route tag value and finds that the local process tag is the same as that in the LSDB, and routes are not calculated.
|
All Answers
fuzi_yao
Reply alicenahi Created Nov 17, 2021 09:03:16
(0)
(0)
alright, Is a VPN instance bound to your interface? Check whether a VPN instance is configured for the static route. Also, what is the specific version of your device? All I can think of is these configuration problems. If the configuration is correct, the compatibility between the two vendors cannot be ruled out.
alicenahi
Reply fuzi_yao Created Nov 17, 2021 09:20:29
(0)
(0)
Yes, all configuration exist as you said. All ospf neighborships are up. To make a summary Huawei sends its static routes to Juniper via OSPF and Juniper accepts it. Juniper sends its static routers to Huawei but it doesn't accept it (It accepts the other routes, like the loopback address of the Juniper) I am starting to believe it is a compatibility issue too.
fuzi_yao
Reply alicenahi Created Nov 17, 2021 09:48:09
(1)
(0)
Add the following command to the OSPF process and run the vpn-instance-capability simple command to ignore the VPN check in the OSPF process: The root cause is that OSPF on the local device is bound to a VPN instance. Therefore, the local device checks the route tag value and finds that the local process tag is the same as that in the LSDB, and routes are not calculated.
|
Comment
Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
- Politically sensitive content
- Content concerning pornography, gambling, and drug abuse
- Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
