No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

After the NE80 Is Upgraded from VRP3.10 to V3R5, OSPF and IS-IS Fail to Learn Routes from Each Other

Publication Date:  2012-07-27 Views:  39 Downloads:  0
Issue Description
 1. After the NE80 deployed on a MAN is upgraded from VRP3.10 to V3R5, the configurations of the import of OSPF routes to IS-IS and the import of IS-IS routes to OSPF exist on the NE80.
2. Check the NE80 after the upgrade. It is found that OSPF and IS-IS cannot import routes from each other, and the relevant routing entries cannot be found in the routing table. 

 
Alarm Information
 Null 

 
Handling Process
 1. After consultation and check, it is confirmed that the unsuccessful import of OSPF and IS-IS routes from each other is not due to the specifications of the version V3R5.
2. Compare the original configurations and the new configurations, and it is found that before the upgrade, the IS-IS process ID is 7785. In VRP3.10, by default, no IS-IS process ID is specified when OSPF is configured to import IS-IS routes.
ospf
import-route isis route-policy 32bit-isis-rout
3. After the version is upgraded to V3R5, in this version, the IS-IS process ID needs to be specified when OSPF is configured to import IS-IS routes. If the import-route isis route-policy 32bit-isis-rout command is configured in this version, the IS-IS process ID 1 is added by default. That is, import-route isis 1 route-policy 32bit-isis-rout. This, however, is not taken into consideration during the script making. As a result, after the upgrade, the IS-IS process ID becomes 1, not 7785. Thus, routes cannot be imported. After the following command is run, the services become normal: import-route isis 7785 route-policy 32bit-isis-rout 

 
Root Cause
 1. It may be due to the specifications of the software version after the upgrade.
2. The configuration may be incorrect. 

 
Suggestions
 When the version is upgraded from an earlier one to a much later one, pay attention to the change in the configurations before and after the upgrade. If a certain aspect is ignored, you must compare the scripts used before and after the upgrade when the upgrade is complete to find problems in time and solve the problems. 

 

END