Alcatel-Lucent 7750 SR-OS, Configuration Manual

Page: 29 / 674

IP Router Configuration
7750 SR OS Router Configuration Guide Page 29
• 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 evident from above, 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 address families listed below:
• IPv4 (AFI=1, SAFI=1)
• IPv6 (AFI=2, SAFI=1)
• VPN-IPv4 (AFI=1, SAFI=128)
• VPN-IPv6 (AFI=2, SAFI=128)
Note that 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 and then the BGP import policy, so the QPPB QoS is based on the
BGP import policy entry.
This feature also introduces the ability to associate a forwarding-class and optionally priority with
IPv4 and IPv6 static routes. This is achieved using the following modified versions of the static-
route commands:
• static-route { ip-prefix / prefix-length | ip-prefix netmask } [fc fc-name [priority {low | high}]]
next-hop ip-int-name | ip-address
• static-route { ip-prefix / prefix-length | ip-prefix netmask } [fc fc-name [priority {low | high}]]
indirect ip-address