376
•
A limit configured in VPN instance view is applicable to both the IPv4 VPN and the IPv6 VPN.
•
A limit configured in IPv6 VPN view is applicable to only the IPv6 VPN.
•
A limit configured in IPv6 VPN view takes precedence over that configured in VPN instance view. If
you configure a limit in both IPv6 VPN view and VPN instance view, the limit configured in IPv6
VPN view is applied to the IPv6 VPN.
Syntax
routing-table
limit
number
{
warn-threshold
|
simply-alert
}
undo routing-table limit
View
VPN instance view, IPv6 VPN view
Default level
2: System level
Parameters
number
: Specifies the maximum number of routes supported. The value ranging from 1 to 8192.
warn-threshold
: Specifies a threshold for warning, ranging from 1 to 100, in percentages. When the
percentage of the number of existing routes to the maximum number of routes supported exceeds the
specified threshold, the system gives an alarm message but still allows new routes. If the number of routes
in the VPN instance reaches the maximum supported, no more routes are added.
simply-alert
: Specifies that when the number of routes exceeds the maximum number of routes supported,
the system still accepts routes but generates a Syslog message.
Examples
# Configure VPN instance
vpn1
to support up to 1000 routes and receive new routes after the number of
existing routes exceeds the limit.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] route-distinguisher 100:1
[Sysname-vpn-instance-vpn1] routing-table limit 1000 simply-alert
# Specify that the IPv6 VPN of VPN instance
vpn3
supports up to 1000 routes, and can receive new
routes after the number of existing routes exceeds the limit.
<Sysname> system-view
[Sysname] ip vpn-instance vpn3
[Sysname-vpn-instance-vpn3] route-distinguisher 100:3
[Sysname-vpn-instance-vpn3] ipv6-family
[Sysname-vpn-ipv4-vpn3] routing-table limit 1000 simply-alert
rr-filter
Description
Use the
rr-filter
command to create an RR reflection policy.
Use the
undo rr-filter
command to remove the configuration.
With an RR reflection policy, only IBGP routes whose Extended Communities attribute matches the
specified one are reflected. This provides a way to implement load balancing between RRs.