•
o is the number of VRF directly provisioned/configured on the card, (n is greater than or equal to o)
•
R is routes per VRF
•
x is the ratio of SVD local: total routes
•
Y is the number of VRFs dependant on directly provisioned VRFs (o), (Y is greater than or equal to 0)
Here is an example calculation:
A customer has 100 VRFs configured on the system, with five line cards. For the IPv4 address family, four
line cards are working as customer facing with equal VRF distribution, while one is core facing. Inter-table
dependencies do not exist. In this example, n = 100, o = 25, x = 3/10, Y = 0, and R = 1000.
Number of routes downloaded:
•
Without SVD: (nR) = 100,000
•
On customer-facing card: (o+Y)R = 25,000
•
On core-facing card: (nxR) = 30,000
In this example, the SVD feature brings close to 70 per cent savings.
The total number of VRFs present (n) can be found by using the show cef tables summary location node-id
command on the RSP card.
RP/0/RSP0/CPU0:router#show cef tables summary location 0/rsp0/cpu0
Role change timestamp : Apr 3 07:21:46.759
Current Role : Core
No. of times Eod received : 2
Eod received : Apr 3 07:21:46.980
No. of Tables : 106
No. of Converged Tables : 106
No. of Deleted Tables : 0
No. of Bcdl Subscribed Tables : 106
No. of Marked Tables : 0
The number of VRFs provisioned on the line card (o) is derived from the "No. Of Tables" field in the show
cef tables summary location 0/0/cpu0. This provides the tables specific to the Linecard 0/0/cpu0.
The routes per VRF (R) can be found using the show cef tables location node-id command.
RP/0/RSP0/CPU0:router#show cef tables location 0/1/CPU0
Sat Apr 6 01:22:32.471 UTC
Codes: L - SVD Local Routes, R - SVD Remote Routes
T - Total Routes
C - Table Converged, D - Table Deleted
M - Table Marked, S - Table Subscribed
Table Table ID L R T C D M S
default 0xe0000000 9 3 23 Y N N Y
**nVSatellite 0xe0000010 1 0 6 Y N N Y
cdn 0xe0000011 0 0 5 Y N N Y
oir 0xe0000012 0 0 5 Y N N Y
vrf1 0xe0000013 3 1 11 Y N N Y
For the vrf "vrf1" the total routes is in the "T" column which is 11. So if the number of routes per VRF are
not the same for all vrfs then total of "routes in all non-default" vrfs will have to be calculated and divided by
the number of VRFs, to arrive at the Average Routes per VRF.
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide, Release 5.1.x
60 OL-30423-03
Implementing BGP
Selective VRF Download Disable
To Next Page
Loading...
Need help?
General
