cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1001
Views
0
Helpful
4
Replies

Adjusting FIB size on 6500 with Sup2T-XL

johnnylingo
Level 5
Level 5

We have a SUP2T VSS, with the XL version of the supervisors.  I was under the impression that this platform will hold up to 1,000,000 routes, but apparently it only supports 256K in the default configuration:

 

#show platform hardware cef resource-level
Global watermarks: apply to Fib shared area only.
Protocol watermarks: apply to protocols with non-default max-routes

Fib-size: 256k (262144), shared-size: 248k (253952), shared-usage: 54k(55303)

Global watermarks:
            Red_WM: 95%,   Greem_WM: 80%,   Current usage: 21%

Protocol watermarks:

 Protocol           Red_WM(%)      Green_WM(%)     Current(%)
 --------           ---------      ----------      ----------
 IPV4                --             --              22% (of shared)
 IPV4-MCAST          --             --              0 % (of shared)
 IPV6                --             --              0 % (of shared)
 IPV6-MCAST          --             --              0 % (of shared)
 MPLS                --             --              0 % (of shared)
 EoMPLS              --             --              0 % (of shared)
 VPLS-IPV4-MCAST     --             --              0 % (of shared)
 VPLS-IPV6-MCAST     --             --              0 % (of shared)

We migrated from 7604s, where this setting would be adjusted with the mls cef maximum-routes command.  What's the equivilent way of doing this on the Sup2T?

2 Accepted Solutions

Accepted Solutions

Jon Marshall
Hall of Fame
Hall of Fame

What modules do you have in the chassis ie. if they are DFC enabled is this DFC or DFC-XL ?

Do you have any CFC cards in the chassis ?

Jon

View solution in original post

Your DFC module is DFC only ie. not DFC-XL.

When you use non XL DFC modules in a chassis with an XL sup2T the sup has to run in non XL mode.

This is because it downloads it's FIB to the DFCs on each module but obviously it cannot download more FIB entries than the DFC can hold in it's FIB.

So you would have to upgrade that module to XL to be able to get the maximum routes that XL supports. 

The CFC module is not an issue because it does not have a DFC.

Jon

 

View solution in original post

4 Replies 4

Jon Marshall
Hall of Fame
Hall of Fame

What modules do you have in the chassis ie. if they are DFC enabled is this DFC or DFC-XL ?

Do you have any CFC cards in the chassis ?

Jon

Each chassis has a WS-X6908-10G/WS-F6K-DFC4-E and WS-X6748-GE-TX/WS-F6700-CFC

 

So the X6908 would be distributed but the X6748 would be centralized.

Your DFC module is DFC only ie. not DFC-XL.

When you use non XL DFC modules in a chassis with an XL sup2T the sup has to run in non XL mode.

This is because it downloads it's FIB to the DFCs on each module but obviously it cannot download more FIB entries than the DFC can hold in it's FIB.

So you would have to upgrade that module to XL to be able to get the maximum routes that XL supports. 

The CFC module is not an issue because it does not have a DFC.

Jon

 

Ahh, makes sense.  Yes I noticed the 10GB line cards were non-XL so that negates having an XL supervisor.  I'll yell at our reseller for that one, although fortunately we don't need a full internet route table; I was just curious. 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card