NE80 VRP3.10 0426
NE80E VRP5.30 31002S.03
Two NE80E based on OSPFMD5 authentication of interface establish OSPF neighbor. NE80 and NE80E have built common OSPF neighbor relation. It is required to change it as OSPF MD5 authentication based on interface. After the configuration NE80 and NE80E cannot establish neighbor relation.
1. Check MD5 configuration of NE80 and NE80E and it is not problematic.
2. Disp ospf error on NE80 and there is ospf authentication mode mistake.
3. Debug ospf events on NE80 and there is similar information.
4. Change MD5 authentication on NE80 as the configuration based on AREA and the neighbor relation can be built. Current version of NE80 does not support MD5 authentication based on interface but based on AREA.
NE80 and NE80E can build common OSPF neighbor relation. The interface and the link are not problematic. The neighbor relation cannot be built after the configuration of MD5 authentication. It is possible that MD5 interface authentication is wrongly configured, e.g. the password of peers is inconsistent or MD5 authentication negotiation of peers is problematic.
For OSPF neighbor not built, it can be located by disp ospf error and debug ospf event.
NE80 version is old and cannot support OSPF MD5 authentication based on interface. The software version can be upgraded to VRP3.10 23XX or VRP5.