From: Steven Weber (itweber@xxxxxxxxxxxxx)
Date: Sun Mar 04 2001 - 19:18:08 GMT-3
agreed. there's more than one way to eat a Reese's :-)
----- Original Message -----
From: Mark Salmon
To:
Cc: Groupstudy
Sent: 3/4/01 4:50:37 PM
Subject: Re: BGP no sync and Bootcamp
Labs
Not necessarily. It depends on your design. Here is
how I do it. I configure one
ip address in my as with a VLSM (eg /24). I then use aggregate
address command on
my BGP routers with summary only. I make sure that all the necessary
addresses are
reachable via IGP by all BGP routers. But again it sdepends on
the design. If
there is only 1 BGP router in the AS (as long as I am not prevented from
doing so) I
will disable sync rather that redistribute IGP into BGP.
Steven Weber wrote:
If I'm understanding no sync correctly your only other option is that
you
redistribute your entire IGP into BGP, leaving you with a very messy
routing
table. I view no sync as a good way of keeping your routes neat. I
don't think
that not using it is practical or advised, although I have been told
many a time
that it is on by default for a reason.
My $.02
Steve
----- Original Message -----
From: crl
To: Groupstudy
Sent: 3/4/01 3:14:43 PM
Subject: BGP no sync and Bootcamp
Labs
Just finished my first run through Bootcamp Lab #6. Not a very
tough
one
anymore if you skip the protocols that are irrelevant to today's
lab...
To
shake things up a bit, I decided to try to get the BGP configs
all
working
without using the no sync command (I know that it wasn't outlawed
in
the
lab.)
Well I had a terrible time of this. I admit, BGP is a weak area for
me,
and
I likely won't be doing anymore Bootcamp labs until I polish my
BGP
core
knowledge. Has anyone else done these labs leaving syncronization
enabled?
I
could get about half my routes into the routing table, but the other
half
I
just couldn't.
I know it's been brought up before, but if the odds are that the
lab
is
going to outlaw the "no sync" command, why do so many people turn it
on
when
doing scenarios?
That's my thought of the day...
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:20 GMT-3