[25108] in North American Network Operators' Group
Re: IS-IS reference
daemon@ATHENA.MIT.EDU (Dave Cooper)
Mon Sep 13 19:34:36 1999
Date: Mon, 13 Sep 1999 16:31:13 -0700
From: Dave Cooper <dcooper@gulp.org>
To: Randy Bush <randy@psg.com>
Cc: nanog@merit.edu
Mail-Followup-To: Randy Bush <randy@psg.com>, nanog@merit.edu
In-Reply-To: <m11QfRP-0008G4C@rip.psg.com>; from Randy Bush on Mon, Sep 13, 1999 at 04:23:19PM -0700
Errors-To: owner-nanog-outgoing@merit.edu
Randy Bush wrote:
> > 1. Use IBGP and redistribute connected/static and when you can, aggregate
> > those statics/connecteds at each router.
> > 2. Use IGP (IS-IS level-2 or OSPF area0) for the backbone links and
> > IBGP, Any-RP loopbacks. Don't add instability to your
> > IGP when you have IBGP that can take care of it much more efficiently.
> > As long as IGP can reach/see each router's loopback, IBGP will
> > work great for connecteds/statics (just make sure you don't announce
> > these specifics to your peers).
> > 3. Don't use static routing for backbone links.... i am not sure how that
> > even came up. Remember this is a NSP of some sorts.
>
> vadim's english was not so bad it needed reinterpreting
not reinterpreting... just enhancing.:)
>
> > 4. Do multicasting, just make sure you get clueful on it. Its not rocket
> > science... and with PIM sparse/dense, its much easier than the DVMRP
> > days. (and make sure you get on a good IOS release and stay off the
> > buggy releases)
>
> that's anything since the lost stanford backup tapes? and msdp worked
> almost as well on that release as it does now.
msdp/mbgp has its own definition of "good IOS release"... but it works.
-dave
>
> randy
