Applying a Route-Policy

A route-policy takes effect only when it is applied to a routing protocol.

Context

A route-policy can be applied to direct, static, RIP/RIPng, IS-IS, OSPF/OSPFv3, BGP/BGP4+, and BGP/MPLS IP VPN routes. In addition, a route-policy can be applied to an FRR scenario. Perform one of the following configurations as needed:

Procedure

  • Apply a route-policy to direct routes.
    1. Run system-view

      The system view is displayed.

    2. To apply a route-policy to specific direct routes, see Table 1.

      Table 1 Applying a route-policy to direct routes

      Objectives

      Command

      Reference

      To configure a device to advertise ARP Vlink direct routes that match a route-policy (specified by the route-policy route-policy-name parameter) on the public network

      arp vlink-direct-route advertise [ route-policy route-policy-name ]

      Configuring the Advertisement of IPv4 ARP Vlink Direct Routes on the Public Network

      To configure a device to advertise Neighbor Discovery Protocol (NDP) Vlink direct routes that match a route-policy (specified by the route-policy route-policy-name parameter) on the public network

      ipv6 nd vlink-direct-route advertise [ route-policy route-policy-name ]

      Configuring the Advertisement of IPv6 NDP Vlink Direct Routes on the Public Network

      To apply a route-policy to direct routes on the public network

      NOTE:

      Currently, QoS information, such as the traffic behavior or local ID, can be configured for direct routes only based on a route-policy. A router applies different QoS policies to packets based on the QoS information while forwarding these packets. In this manner, traffic statistics can be collected, and authentication and accounting can be performed based on the direct routes.

      ip direct-routing-table route-policy route-policy-name

      -

    3. Run commit

      The configuration is committed.

  • Apply a route-policy to static routes.
    1. Run system-view

      The system view is displayed.

    2. Run ip static-routing-table route-policy route-policy-name

      A route-policy is applied to static routes on the public network.

    3. Run commit

      The configuration is committed.

  • Apply a route-policy to RIP routes.
    1. Run system-view

      The system view is displayed.

    2. Run rip [ process-id ]

      A RIP process is enabled, and the RIP view is displayed.

    3. To apply a route-policy to specific RIP routes, see Table 2.

      Table 2 Applying a route-policy to RIP routes

      Objectives

      Command

      Reference

      To configure a device to generate a default route or advertise a default route in the routing table to neighbors only when the matching conditions of a route-policy (specified by the route-policy route-policy-name parameter) are met

      default-route originate [ cost cost | tag tag | route-policy route-policy-name [ avoid-learning ] ] *

      Configuring RIP to Advertise Default Routes

      To configure RIP to import the BGP routes that match a route-policy (specified by the route-policy route-policy-name parameter)

      import-route bgp [ permit-ibgp ] [ cost { cost | transparent } | route-policy route-policy-name ] *

      Configuring RIP to Import External Routes

      To configure RIP to import the routes from another routing protocol that match a route-policy (specified by the route-policy route-policy-name parameter)

      import-route { static | direct | unr | { isis | ospf | rip } [ process-id ] } [ cost cost | route-policy route-policy-name ] *

      Configuring RIP to Import External Routes

      To set a priority for RIP routes that match a route-policy (specified by the route-policy route-policy-name parameter)

      preference { preference | route-policy route-policy-name } *

      Configuring the RIP Priority

    4. Run commit

      The configuration is committed.

  • Apply a route-policy to RIPng routes.
    1. Run system-view

      The system view is displayed.

    2. Run ripng [ process-id ]

      A RIPng process is enabled, and the RIPng view is displayed.

    3. To apply a route-policy to specific RIPng routes, see Table 3.

      Table 3 Applying a route-policy to RIPng routes

      Objectives

      Command

      Reference

      To configure RIPng to import the routes from another routing protocol that match a route-policy (specified by the route-policy route-policy-name parameter)

      import-route { static | direct | bgp [ permit-ibgp ] | unr | { isis | ospfv3 | ripng } [ process-id ] } [ cost cost | route-policy route-policy-name ] *

      Configuring RIPng to Import External Routes

      To set a priority for RIPng routes that match a route-policy (specified by the route-policy route-policy-name parameter)

      preference { preference | route-policy route-policy-name } *

      Configuring the RIPng Priority

    4. Run commit

      The configuration is committed.

  • Apply a route-policy to IPv4 IS-IS routes.

    • To apply a route-policy in the IS-IS view, perform the following operations:
      1. Run the system-view command to enter the system view.
      2. Run the isis [ process-id ] command to enter the IS-IS view.
      3. To apply a route-policy to IPv4 IS-IS routes in the IS-IS view, see Table 4.
        Table 4 Applying a route-policy to IPv4 IS-IS routes in the IS-IS view

        Objectives

        Command

        Reference

        To configure IS-IS to generate and advertise default routes to the IS-IS domain only when external routes that match a route-policy (specified by the route-policy route-policy-name parameter) exist in the routing table of a Level-1-2 router

        default-route-advertise route-policy route-policy-name [ cost cost | tag tag | [ level-1 | level-1-2 | level-2 ] ] * [ avoid-learning ]

        Configuring IS-IS to Generate IPv4 Default Routes

        To configure IS-IS to advertise the routes that are imported from another routing protocol and match a route-policy

        filter-policy route-policy route-policy-name export [ protocol [ process-id ] ]

        -

        To configure IS-IS to accept the routes that match a route-policy

        filter-policy route-policy route-policy-name import

        Configuring IPv4 IS-IS to Import External Routes

        To configure IS-IS to import the routes from another routing protocol that match a route-policy

        import-route { direct | static | unr | { ospf | rip | isis } [ process-id ] | bgp [ permit-ibgp ] } [ cost-type { external | internal } | cost cost | tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] *

        import-route { { ospf | rip | isis } [ process-id ] | bgp [ permit-ibgp ] | direct | unr } inherit-cost [ { level-1 | level-2 | level-1-2 } | tag tag | route-policy route-policy-name ] *

        import-route { ospf | isis } [ process-id ] [ cost-type { external | internal } | cost cost | tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] | no-sid ] *

        import-route { ospf | isis } [ process-id ] inherit-cost [ { level-1 | level-2 | level-1-2 } | tag tag | route-policy route-policy-name | no-sid ] *

        Configuring IPv4 IS-IS to Import External Routes

        To configure Level-1 routes that match a route-policy to leak to a Level-2 area

        import-route isis level-1 into level-2 [ filter-policy route-policy route-policy-name | direct allow-filter-policy | tag tag | no-sid ] *

        Configuring IPv4 IS-IS Route Leaking

        To configure Level-2 routes that match a route-policy to leak to a Level-1 area

        import-route isis level-2 into level-1 [ filter-policy route-policy route-policy-name | direct allow-filter-policy | tag tag | no-sid ] *

        Configuring IPv4 IS-IS Route Leaking

        To configure a priority for the IS-IS routes that match a route-policy

        preference { route-policy route-policy-name | preference } *

        Configuring a Preference Value for IPv4 IS-IS
      4. Run the commit command to commit the configuration.
    • To apply a route-policy in the IS-IS FRR view, perform the following operations:
      1. Run the system-view command to enter the system view.
      2. Run the isis [ process-id ] command to enter the IS-IS view.
      3. Run the frr command to enter the IS-IS FRR view.

      4. Run the frr-policy route route-policy route-policy-name command to configure IS-IS to add the backup routes that match a route-policy to the IP routing table.

        For details on how to configure IS-IS Auto FRR (IPv4), see Configuring IS-IS Auto FRR.

      5. Run the commit command to commit the configuration.

  • Apply a route-policy to IPv6 IS-IS routes.

    • To apply a route-policy in the IS-IS view, perform the following operations:
      1. Run the system-view command to enter the system view.
      2. Run the isis [ process-id ] command to enter the IS-IS view.
      3. To apply a route-policy to IPv6 IS-IS routes in the IS-IS view, see Table 5.
        Table 5 Applying a route-policy to IPv6 IS-IS routes in the IS-IS view

        Objectives

        Command

        Reference

        To configure IS-IS to generate and advertise default IPv6 routes to the IS-IS domain only when external routes that match a route-policy (specified by the route-policy route-policy-name parameter) exist in the routing table of a Level-1-2 router

        ipv6 default-route-advertise route-policy route-policy-name [ cost cost | tag tag | [ level-1 | level-2 | level-1-2 ] ] * [ avoid-learning| learning-avoid-loop ]

        Configuring IS-IS to Generate IPv6 Default Routes

        To configure IS-IS to advertise the IPv6 routes that are imported from another routing protocol and match a route-policy

        ipv6 filter-policy route-policy route-policy-name export [ protocol [ process-id ] ]

        -

        To configure IS-IS to accept the IPv6 routes that match a route-policy

        ipv6 filter-policy route-policy route-policy-name import

        Configuring IPv6 IS-IS to Import External Routes

        To configure IS-IS to import the IPv6 routes from another routing protocol that match a route-policy

        ipv6 import-route { direct | static | unr | { ripng | isis | ospfv3 } [ process-id ] } | bgp [ permit-ibgp ] } [ cost cost | tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] *

        ipv6 import-route { { ospfv3 | ripng | isis } [ process-id ] | bgp [ permit-ibgp ] | direct | unr } inherit-cost [ tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] *

        Configuring IPv6 IS-IS to Import External Routes

        To configure Level-1 IPv6 routes that match a route-policy to leak to a Level-2 area

        ipv6 import-route isis level-1 into level-2 [ filter-policy route-policy route-policy-name | direct allow-filter-policy | tag tag ] *

        Configuring IPv6 IS-IS Route Leaking

        To configure Level-2 IPv6 routes that match a route-policy to leak to a Level-1 area

        ipv6 import-route isis level-2 into level-1 [ filter-policy route-policy route-policy-name | direct allow-filter-policy | tag tag ] *

        Configuring IPv6 IS-IS Route Leaking

        To configure a priority for the IPv6 IS-IS routes that match a route-policy

        ipv6 preference { route-policy route-policy-name | preference } *

        Configuring a Preference Value for IPv6 IS-IS
      4. Run the commit command to commit the configuration.
    • To apply a route-policy in the IS-IS IPv6 topology view, perform the following operations:
      1. Run the system-view command to enter the system view.
      2. Run the isis [ process-id ] command to enter the IS-IS view.
      3. Run the ipv6 topology topology-name [ topology-id { multicast | topology-id } ] command to bind the IS-IS process to an IPv6 topology and enter the IS-IS IPv6 topology view.

      4. Run the import-route { direct | isis [ process-id ] inherit-cost [ tag tag | route-policy route-policy-name | { level-1 | level-2 | level-1-2 } ] * command to configure IS-IS to import routes from another protocol into the current topology.

        For details on how to configure IPv6 IS-IS multi-topology, see Enabling MT for an IS-IS Process.

      5. Run the commit command to commit the configuration.

  • Apply a route-policy to OSPF routes.

    • To apply a route-policy in the OSPF view, perform the following operations:

      1. Run the system-view command to enter the system view.
      2. Run the ospf [ process-id ] command to enable an OSPF process and enter the OSPF view.
      3. To apply a route-policy to OSPF routes in the OSPF process view, see Table 6.
        Table 6 Applying a route-policy to OSPF routes

        Objectives

        Command

        Reference

        To configure OSPF to advertise the default routes in the routing table that are not generated by OSPF to a common area based on the parameters of a route-policy (specified by the route-policy route-policy-name parameter)

        default-route-advertise [ [ always | permit-calculate-other ] | cost cost | type type | route-policy route-policy-name | distribute-delay delay-time ] *

        default-route-advertise [ permit-calculate-other | cost cost | type type | route-policy route-policy-name | distribute-delay delay-time | permit-ibgp ] *

        default-route-advertise summary cost cost

        Configuring OSPF to Import a Default Route

        To configure OSPF to accept the routes that match a route-policy

        filter-policy route-policy route-policy-name [ secondary ] import

        Configuring OSPF to Filter Received Routes

        To configure OSPF to import the routes that match a route-policy

        filter-policy route-policy route-policy-name export [ protocol [ process-id ] ]

        Configuring OSPF to Filter the Routes to Be Advertised

        To configure OSPF to import routes from another protocol

        import-route { bgp [ permit-ibgp ] | direct | unr | rip [ process-id-rip ] | static | isis [ process-id-isis ] | ospf [ process-id-ospf ] [ cost cost | route-policy route-policy-name | tag tag | type type ] * }

        Configuring OSPF to Import External Routes

        To configure a route-policy for OSPF local MT so that only the routes that match the route-policy (specified by the route-policy route-policy-name parameter) are added to the MIGP routing table

        local-mt filter-policy route-policy route-policy-name

        -

        To configure a priority for OSPF routes that match a route-policy

        preference [ ase | inter | intra ] { preference | route-policy route-policy-name } *

        Setting the OSPF Priority
      4. Run the commit command to commit the configuration.

    • To apply a route-policy in the OSPF area view, perform the following operations:

      1. Run the system-view command to enter the system view.

      2. Run the ospf [ process-id ] command to enable an OSPF process and enter the OSPF view.

      3. Run the area area-id command to enter the OSPF area view.

      4. Perform either of the following operations to apply a route-policy in the OSPF area view:

        • Run the filter route-policy route-policy-name export command to apply a route-policy to outgoing Type 3 LSAs (summary LSAs) in the area.

        • Run the filter route-policy route-policy-name import command to apply a route-policy to incoming Type 3 LSAs in the area.

        For details on the configuration of applying a route-policy to Type-3 LSAs, see Configuring OSPF to Filter LSAs in an Area

      5. Run the commit command to commit the configuration.

    • To apply a route-policy in the OSPF FRR view, perform the following operations:

      1. Run the system-view command to enter the system view.

      2. Run the ospf [ process-id ] command to enable an OSPF process and enter the OSPF view.

      3. Run the frr command to enter the OSPF FRR view.

      4. Run the loop-free-alternate command to enable OSPF IP FRR to generate a loop-free backup link.

      5. Run the frr-policy route route-policy route-policy-name command to configure OSPF to add the backup routes that match a route-policy to the IP routing table.

        For details on how to configure OSPF IP FRR, see Configuring OSPF IP FRR.

      6. Run the commit command to commit the configuration.

  • Apply a route-policy to OSPFv3 routes.

    • To apply a route-policy in the OSPFv3 view, perform the following operations:

      1. Run the system-view command to enter the system view.

      2. Run the ospfv3 [ process-id ] command to enable an OSPFv3 process and enter the OSPFv3 view.

      3. To apply a route-policy to OSPFv3 routes in the OSPFv3 view, see Table 7.

        Table 7 Applying a route-policy to OSPFv3 routes

        Objectives

        Command

        Reference

        To configure OSPFv3 to advertise the default routes in the routing table that are not generated by OSPFv3 to an OSPFv3 routing area based on the parameters of a route-policy (specified by the route-policy route-policy-name parameter)

        default-route-advertise [ always | permit-calculate-other | cost cost | type type | tag tag | distribute-delay delay | route-policy route-policy-name ] *

        Configuring OSPFv3 to Filter the Routes to Be Advertised

        To configure OSPFv3 to accept the routes that match a route-policy

        filter-policy route-policy route-policy-name [ secondary ] import

        Configuring OSPFv3 to Filter Received Routes

        To configure OSPFv3 to import the routes that match a route-policy

        filter-policy route-policy route-policy-name export [ protocol [ process-id ] ]

        Configuring OSPFv3 to Filter the Routes to Be Advertised

        To configure OSPFv3 to import routes from another protocol

        import-route { bgp [ permit-ibgp ] | direct | unr | static | isis [ process-id ] | ripng [ process-id ] | ospfv3 [ process-id ] } [ cost cost | tag tag | type type | route-policy route-policy-name ] * }

        Configuring OSPFv3 to Import External Routes

        To configure a priority for OSPF routes that match a route-policy

        preference [ ase ] { preference | route-policy route-policy-name } *

        -
      4. Run the commit command to commit the configuration.

    • To apply a route-policy in the OSPFv3 area view, perform the following operations:

      1. Run the system-view command to enter the system view.

      2. Run the ospfv3 [ process-id ] command to enable an OSPFv3 process and enter the OSPFv3 view.

      3. Run the area area-id command to enter the OSPFv3 area view.

      4. Perform either of the following operations to apply a route-policy in the OSPFv3 area view:

        • Run the filter route-policy route-policy-name export command to apply a route-policy to outgoing Type 3 LSAs (Inter-Area-Prefix-LSAs) in the area.

        • Run the filter route-policy route-policy-name import command to apply a route-policy to incoming Type 3 LSAs in the area.

        For details on how to apply a route-policy to Type 3 LSAs, see Configuring OSPFv3 to Filter LSAs in an Area.

      5. Run the commit command to commit the configuration.

    • To apply a route-policy in the OSPFv3 FRR view, perform the following operations:

      1. Run the system-view command to enter the system view.

      2. Run the ospfv3 [ process-id ] command to enable an OSPFv3 process and enter the OSPFv3 view.

      3. Run the frr command to enter the OSPFv3 IP FRR view.

      4. Run the loop-free-alternate command to enable OSPFv3 IP FRR.

      5. Run the frr-policy route route-policy route-policy-name command to configure OSPFv3 to add the backup routes that match a route-policy to the IP routing table.

        For details on how to configure OSPFv3 IP FRR, see Configuring OSPFv3 IP FRR.

      6. Run the commit command to commit the configuration.

  • Apply a route-policy to BGP routes.
    1. Run the system-view command to enter the system view.
    2. Run the bgp { as-number-plain | as-number-dot } command to enter the BGP view.
    3. Run the ipv4-family unicast command to enter the IPv4 unicast address family view.
    4. To apply a route-policy to specific BGP routes, see Table 8.

      Table 8 Applying a route-policy to BGP routes

      Objectives

      Command

      Reference

      To configure a summary BGP route

      aggregate ipv4-address { mask | mask-length } [ as-set | attribute-policy route-policy-name1 | detail-suppressed | origin-policy route-policy-name2 | suppress-policy route-policy-name3 ] *

      Configuring BGP Route Summarization

      To configure BGP route dampening

      dampening [ half-life-reach reuse suppress ceiling | route-policy route-policy-name ] *[ update-standard ]

      Configuring BGP Route Dampening

      To configure BGP to import the routes from another routing protocol that match a route-policy

      import-route protocol [ process-id ] [ med med | route-policy route-policy-name ] *[ non-relay-tunnel ]

      Configuring BGP to Import Routes

      To import local routes that match a route-policy to the BGP routing table and advertise them to BGP peers

      network ipv4-address [ mask | mask-length ] [ route-policy route-policy-name ] [ non-relay-tunnel ]

      Configuring BGP to Import Routes

      To enable BGP route recursion based on a route-policy

      nexthop recursive-lookup route-policy route-policy-name

      Setting Next_Hop Attributes for Routes

      To configure a device to send a default route to a peer or a peer group and use a route-policy (specified by the route-policy route-policy-name parameter) to modify the attributes of the default route

      peer { group-name | ipv4-address } default-route-advertise [ route-policy route-policy-name ] [ conditional-route-match-all { ipv4-address1 { mask1 | mask-length1 } } &<1-4> | conditional-route-match-any { ipv4-address2 { mask2 | mask-length2 } } &<1-4> ]

      Configuring a BGP Device to Send a Default Route to Its Peer

      To prevent a device from performing bit-error-triggered protection switching when a route-policy is used as an export policy

      NOTE:

      When bit-error-triggered protection switching is configured, bit errors occur, and Local_Pref or MED is modified using an export route-policy, run the command to apply the Local_Pref or MED in the export route-policy.

      peer { group-name | ipv4-address } route-policy route-policy-name export ignore-bit-error

      -

      To configure a device to accept the routes that match a route-policy from a peer or peer group or advertise the routes that match a route-policy to a peer or peer group

      peer { group-name | ipv4-address } route-policy route-policy-name { import | export }

      Configuring to Control the Advertisement of BGP Routing Information

      Controlling the Acceptance of BGP Routing Information

      To use a route-policy to set a BGP priority

      preference route-policy route-policy-name

      Setting the BGP Priority

      To prevent the BGP routes that match a route-policy from being added to the IP routing table

      routing-table rib-only [ route-policy route-policy-name ]

      Preventing a Device from Adding BGP Routes to the IP Routing Table

    5. Run the commit command to commit the configuration.
  • Apply a route-policy to BGP4+ routes.
    1. Run system-view

      The system view is displayed.

    2. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    3. Run ipv6-family [ unicast ]

      The IPv6 unicast address family view is displayed.

    4. To apply a route-policy to specific BGP4+ routes, see Table 9.

      Table 9 Applying a route-policy to BGP4+ routes

      Objectives

      Command

      Reference

      To configure a summary BGP4+ route

      aggregate ipv6-address prefix-length [ as-set | attribute-policy route-policy-name1 | detail-suppressed | origin-policy route-policy-name2 | suppress-policy route-policy-name3 ] *

      Configuring BGP4+ Route Summarization

      To configure BGP4+ route dampening and apply dampening parameters to the routes that match a route-policy (specified by the route-policy route-policy-name parameter) so that specified-requirement dampening can be performed by BGP based on the applied route-policy

      dampening [ half-life-reach reuse suppress ceiling | route-policy route-policy-name ] *

      Configuring BGP4+ Route Dampening

      To configure BGP4+ to import the routes from another routing protocol that match a route-policy

      import-route protocol [ process-id ] [ med med | route-policy route-policy-name ] *

      Configuring BGP4+ to Import Routes

      To import local routes that match a routing policy to the BGP4+ routing table and advertise them to BGP4+ peers

      network ipv6-address prefix-length [ route-policy route-policy-name ]

      Configuring BGP4+ to Import Routes

      To enable BGP4+ route recursion based on a route-policy

      nexthop recursive-lookup route-policy route-policy-name

      Setting the Next_Hop Attribute

      To configure a device to send a default route to a peer or a peer group and use a route-policy (specified by the route-policy route-policy-name parameter) to modify the attributes of the default route

      peer { group-name | ipv6-address } default-route-advertise [ route-policy route-policy-name ] { conditional-route-match-all | conditional-route-match-any } { ipv6-address mask-length } } &<1-4>

      Configuring BGP4+ to Advertise Default Routes to Peers or peer groups

      To configure a device to accept the routes that match a route-policy from a peer or peer group or advertise the routes that match a route-policy to a peer or peer group

      peer { group-name | ipv6-address } route-policy route-policy-name { import | export }

      Configuring a Policy for Advertising BGP4+ Routes

      Configuring a Policy for Receiving BGP4+ Routes

      To use a route-policy to set a BGP4+ priority

      preference route-policy route-policy-name

      Setting the BGP4+ Priority

      To prevent the BGP4+ routes that match a route-policy from being added to the IPv6 routing table

      routing-table rib-only [ route-policy route-policy-name ]

      Preventing BGP4+ from Adding Routes to the IPv6 Routing Table

    5. Run commit

      The configuration is committed.

  • Apply a route-policy to BGP/MPLS IP VPN routes.

    • To apply a route-policy in the BGP-VPNv4 address family view, perform the following operations:

      1. Run the system-view command to enter the system view.
      2. Run the bgp { as-number-plain | as-number-dot } command to enter the BGP view.
      3. Run the ipv4-family vpnv4 command to enter the BGP-VPNv4 address family view.

      4. Run the nexthop recursive-lookup bit-error-detection { med + med-adjust-value | local-preference - localpref-adjust-value } * [ route-policy route-policy-name ] command to associate bit error events with the adjustment of the local preference or MED value for routes that match a route-policy. If route-policy route-policy-name is not specified in the command, the local preferences or MED values of all routes are adjusted.

        For details on how to configure bit-error-triggered L3VPN route switching, see Configuring Bit-Error-Triggered L3VPN Route Switching.

      5. Run the commit command to commit the configuration.

    • To apply a route-policy in the VPN instance view, perform the following operations:

      1. Run the system-view command to enter the system view.
      2. Run the ip vpn-instance vpn-instance-name command to enter the VPN instance view.
      3. Perform either of the following operations as required:

        • To associate a VPN instance address family with one export route-policy, run the export route-policy route-policy-name [ add-ert-first ] command.

          The export command can control route transmission between different VPN instances on a PE, while the peer route-policy export command can control only the VPNv4 or VPNv6 routes that a PE sends to other PE peers.

        • To associate the VPN instance IPv4 or IPv6 address family with one import route-policy, run the import route-policy route-policy-name command.

          The import route-policy command can control route transmission between different VPN instances on a PE, while the peer route-policy import command can control only the VPNv4 or VPNv6 routes that a PE sends to other PE peers.

        • To configure a device to advertise ARP Vlink direct routes that match a route-policy on a VPN, run the arp vlink-direct-route advertise [ route-policy route-policy-name ] command. For details, see Configure a direct route between a PE and a CE.

      4. Run the commit command to commit the configuration.

    • To apply a route-policy in the VPN instance IPv4 address family view, perform the following operations:

      1. Run the system-view command to enter the system view.
      2. Run the ip vpn-instance vpn-instance-name command to enter the VPN instance view.
      3. Run the ipv4-family command to enable the IPv4 address family for the VPN instance and enter the VPN instance IPv4 address family view.

      4. Run the ip { direct-routing-table | static-routing-table } route-policy route-policy-name command to apply a route-policy to direct or static routes in the VPN instance IPv4 address family.

        After the ip route-policy command is run, a device can modify attributes of direct or static routes based on the route-policy.

      5. Run the commit command to commit the configuration.

    • To apply a route-policy in the VPN instance IPv6 address family view, perform the following operations:

      1. Run the system-view command to enter the system view.
      2. Run the ip vpn-instance vpn-instance-name command to enter the VPN instance view.
      3. Run the ipv6-family command to enable the IPv6 address family for the VPN instance and enter the VPN instance IPv6 address family view.
      4. Run the nd vlink-direct-route advertise [ route-policy route-policy-name ] command to configure a device to advertise NDP Vlink direct routes that match a route-policy on a VPN. For details, see Configure a direct route between a PE and a CE.

      5. Run the commit command to commit the configuration.

Parent Topic: Configuring a Route-Policy
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >