From: Scott Morris (swm@emanon.com)
Date: Fri Jul 02 2004 - 17:53:39 GMT-3
That, though, would affect how you were advertising yourself to everyone
except other sub-confed peers. Local-AS is the best solution on
individually-controlled basis.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, CISSP,
JNCIP, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Tom
Martin
Sent: Friday, July 02, 2004 4:20 PM
To: ccielab@groupstudy.com
Cc: ccienj
Subject: RE: BGP AS-Migration
It is tough to follow Howard and offer any kind of practical advice on
BGP... But I will throw my idea out on the assumption that you're studying
for the lab and just looking for options for "what if"
scenarios...
You could configure the existing AS 100 as a confederation AS within AS 200
by adding a single line:
router bgp 100
bgp confederation identifier 200
That would also have the effect of advertising AS 200 to EBGP peers, without
reconfiguration of any existing neighbors. That assumes that you aren't
going to have new neighbors, that your neighbors will be correctly
configured for your "new" AS, etc.
-- Tom
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccienj
Sent: Friday, July 02, 2004 2:54 PM
To: ccielab@groupstudy.com
Subject: BGP AS-Migration
An ISP currently on AS 100 will move to AS 200 next year, to avoid
reconfiguration for this year's customer's what would be best solution to
minimize reconfiguration.
I think BGP Local-as would be the best way to handle this any other ideas ?
thanks,
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:45 GMT-3