Associating an FC and priority with a route

This feature uses the fc command in the route-policy hierarchy to set the forwarding class and, optionally, the priority associated with routes accepted by a route-policy entry. The command has the following structure:

 - fc fc-name [priority {low | high}]

The use of the fc command is shown by the following example:

config>router>policy-options
    begin
    community gold members 300:100
    policy-statement qppb_policy
        entry 10
            from
                protocol bgp
                community gold
            exit
            action accept
                fc h1 priority high
            exit
        exit
    exit
    commit

The fc command is supported with all existing from and to match conditions in a route policy entry, with any action other than reject, and with next-entry, next-policy, and accept actions. If a next-entry or next-policy action results in multiple matching entries, then the last entry with a QPPB action determines the forwarding class and priority.

A route policy that includes the fc command in one or more entries can be used in any import or export policy, but the fc command has no effect except in the following types of policies:

• VRF import policies

  config>service>vprn>vrf-import

• BGP import policies:

  • config>router>bgp>import

  • config>router>bgp>group>import

  • config>router>bgp>group>neighbor>import

  • config>service>vprn>bgp>import

  • config>service>vprn>bgp>group>import

  • config>service>vprn>bgp>group>neighbor>import

• RIP import policies:

  • config>router>rip>import

  • config>router>rip>group>import

  • config>router>rip>group>neighbor>import

  • config>service>vprn>rip>import

  • config>service>vprn>rip>group>import

  • config>service>vprn>rip>group>neighbor>import

As shown, QPPB route policies support routes learned from RIP and BGP neighbors of a VPRN, as well as for routes learned from RIP and BGP neighbors of the base/global routing instance.

QPPB is supported for BGP routes belonging to any of the following address families:

• IPv4 (AFI=1, SAFI=1)

• IPv6 (AFI=2, SAFI=1)

• VPN-IPv4 (AFI=1, SAFI=128)

• VPN-IPv6 (AFI=2, SAFI=128)

A VPN-IP route may match both a VRF import policy entry and a BGP import policy entry (if vpn-apply-import is configured in the base router BGP instance). In this case, the VRF import policy is applied first, then the BGP import policy, so the QPPB QoS is based on the BGP import policy entry.

This feature also provides the ability to associate a forwarding-class and, optionally, priority with IPv4 and IPv6 static routes. This is achieved by specifying the forwarding-class within the static-route-entry>next-hop or static-route-entry>indirect context.

Priority is optional when specifying the forwarding class of a static route, but when configured it can only be deleted and returned to unspecified by deleting the entire static route.