[c-nsp] Troubleshooting Lag between GigE interfaces

[Daniel Roesen]

On Thu, Sep 23, 2004 at 01:31:57PM -0400, Rodney Dunn wrote:
> It's only for traffic to/from that slot.

OK, this was my understanding too. Thanks for confirmation.

> But if you want to do a lot of features (ie: QOS,
> MLPPP, etc.) then you must have dCEF or we don't support
> it.

Understood.

> My advice to customers is you do it one of two ways:
> 
> a) Get an RSP fast enough to run in centralized CEF mode
> or
> b) Make sure all your cards are dCEF capable and have
>    the CPU power to handle the features and run in dCEF mode.

Or:

c) Use a reasonable fast RSP (4 upwards) and use VIPs for all
   higher-speed interfaces, and maybe reuse some old SSIP/FSIP
   for slow-speed interfaces you don't need those dCEF-only
   features on.

I see no reason for the OP to throw out the FSIP as you suggested,
because his problem was disabled dCEF on the VIP^WGEIP due to lack
of RAM on it. An SSIP/FSIP can't make an RSP4 sweat when using CEF.

> If I have an RSP that can do features at X rate which
> is more than the cards can do at Y rate I'm better off
> in centralized RSP mode.  If the VIPs can do the work
> distributed much faster than I can do it centrally then
> I should go with dCEF mode.
> 
> I see the most problems when customers try to run it
> in some hybrid mode.

As long as they know the constraints, this is no problem at all.
The problem is missing knowhow, not a technical problem. It's a
problem of not "using the right tool in the right way for the
job" -- I guess you'll agree here. :-)

BTW, thanks for your very valuable contributions to this mailing
list here, appreciated!


Best regards,
Daniel