[c-nsp] Sup1A/MSFC2 - Prefix or flow based routing?

[lee.e.rian at census.gov]

Jared Mauch <jared at puck.nether.net> wrote on 11/23/2006 10:09:25 AM:

> On Thu, Nov 23, 2006 at 08:46:17AM -0500, lee.e.rian at census.gov wrote:
> > Sam Stickland <sam_mailinglists at spacething.org> wrote on 11/23/2006
> > 06:32:41 AM:
> >
> > > Hi,
> > >
> > > Does anybody know what the routing characteristics of this combo is?
I
> > > know that Sup1A/MSFC1 = flow based, and Sup2/MSFC2 = prefix based,
but I
> > > don't know what Sup1A/MSFC2 is.
> > >
> > > I suspect it's flow based, since the Sup is actually handling the MLS
> > > switching side of things, but I haven't seen anything that says for
> > certain.
> >
> > I'd guess flow based just because it is a Sup1A.  And doing a "sh mls
l3
> > stat" on the sup still lists shortcuts, candidate hits & failed to
create
> > shortcut counters just like a sup1a/msfc1.
>
>    yup, to optimize forwarding performance you want to configure
>
>    mls flow ip destination
>
> here's some timers i've used in the past as well:
>
> mls aging fast time 30 threshold 128
> mls aging long 600

I went by the output of
  show mls l3 stat

Unless "#Failed to create SC(all pages are full)" was incrementing I left
the timers alone.

Lee