[c-nsp] ISIS routing

[Saku Ytti]

On (2012-11-26 10:55 +0100), sthaug at nethelp.no wrote:

> Even if all of your interfaces towards customers/transit/peering block
> IS-IS traffic?

I don't think you can block ISIS in any practical way in PFC3 or Trio.

In Trio you'd need to make your L3 interfaces L2 and put L3 in IRB, then
you could filter ISIS in L2 interfaces.
In PFC3 CoPP your ISIS will hit 'class-default' and you can't discriminate
good or bad ISIS there.

So much less than 10Mbps of ISIS will kill your MX80, MX960, T4000. PFC3
can handle quite bit more as it does not force 'mls rate-limit unicast ref
receive 10000' to you, like JNPR does, which is about most stupid thing you
can do, forcing control-plane to crap-out artificially early.

-- 
  ++ytti