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>Search

Reminder

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

upgrade

AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Routing Policies Delivered by a PE Do Not Take Effect Because There Are Multiple Routing Policies with the Same Name

Routing Policies Delivered by a PE Do Not Take Effect Because There Are Multiple Routing Policies with the Same Name

Fault Symptom

As shown in Figure 19-13, a PE is connected to VPN 1 and is connected to Router B in the upstream direction. VPN 1 routes of the PE need to be advertised to the MAN. The PE controls which routes to be advertised to Router B using routing policies. According to the configured routing policies, Router B needs to learn only the VPN 1 summary route advertised by the PE instead of specific routes. After the routing policies are configured, Router B learns both the VPN 1 summary route and specific routes.

Figure 19-13  Routing policies delivered by a PE failing to take effect

Fault Analysis

  1. Run the display current-configuration command on the PE to view the routing policy configuration. The command output shows that no fault occurs.

  2. According to the fault symptom, it is possible that Router B learns the specific VPN 1 routes advertised by the PE because the delivered routing policies do not take effect.

  3. Run the display bgp vpnv4 vpn-instance vpn-instance-name routing-table peer peer-address { advertised-routes | received-routes [ active ] } command on the PE to view the routes of other VPNs to which the PE is connected. Routes learned on Router B are summary routes of these VPNs. Therefore, it can be concluded that the routing policies for VPN 1 are incorrect.

  4. Check the configuration file of the PE. The result shows that there are three routing policies with the same name for the PE to advertise the routes of VPN 1. The ip-prefix NGN-A referenced by the first routing policy is defined, and this routing policy is valid. The ip-prefix NGN-A1 and ip-prefix NGN-A2 referenced by the other two routing policies are not defined, and therefore the two routing policies are invalid. The following is the detailed configuration:

    ipv4-family vpn-instance CDMA-NGN
    peer 10.247.0.1 route-policy PE_NGN_OUT_MASTER export
    route-policy PE_NGN_OUT_MASTER permit node 10
     if-match ip-prefix NGN-A
    route-policy PE_NGN_OUT_MASTER permit node 20
     if-match ip-prefix NGN-A1
    route-policy PE_NGN_OUT_MASTER permit node 30
     if-match ip-prefix NGN-A2
    ip ip-prefix NGN-A index 10 permit 10.247.0.0 21
    

    The rules for referencing routing policies dictate that the relationship between the three routing policies with the same name must be OR. That is, VPN 1 routes can be correctly advertised as long as one of the routing policies with the same name is valid. However, the redundant invalid routing policies with the same name can still cause VPN 1 routes to be incorrectly advertised.

  5. After deleting the other two invalid routing policies, Router B learns only one summary route, namely, the route with a prefix that is in the IP prefix list NGN-A. The fault is cleared.

Procedure

  1. Run the system-view command on the PE to enter the system view.
  2. Run the undo route-policy route-policy-name [ node node ] command to delete the two redundant routing policies.
  3. Run the display bgp vpnv4 vpn-instance vpn-instance-name routing-table peer peer-address advertised-routes command to view the routes of VPN 1 to which the PE is connected. Only one summary route is found. The fault is cleared.

Summary

According to the rules for referencing routing policies, the relationship between routing policies with the same name must be OR. However, redundant routing policies still need to be deleted to prevent routes from being incorrectly advertised.

Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 444002

Downloads: 4295

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next