As tempting as it is, I would suggest... NO!
Multiple changes at the same time are rarely a good idea on critical infrastructure.
You end up not knowing which change broke what when it comes time to
troubleshoot. While overlapping problems are unlikely in this case, I would
say it's still best to do the renumbering as more of an over-time process.
There's no reason to do renumbering as a flag day.
Owen
On Aug 21, 2012, at 12:28 , Doug McIntyre <[log in to unmask]> wrote:
> On Mon, Aug 20, 2012 at 11:51:10AM -0500, Mike Horwath wrote:
>> On Mon, Aug 20, 2012 at 10:43:43AM -0500, Justin Krejci wrote:
>>> That said any time can be convenient if we have some time to adjust BGP
>>> configs to move traffic away in advance, which during business hours is
>>> typically convenient.
>>
>> A shutdown of the routing daemons on the reflectors should take care
>> of things and no manual BGP configuratin adjustments are needed.
>
> Do we want to maybe do the big renumbering at the same time as this
> switch swapout too? Since things are going to be down, everybody stays
> down until they manually redo their interface and BGP configurations
> after the switch change?
>
> Or do we want to do it more gradually?
>
> --
> Doug McIntyre <[log in to unmask]>
> -- ipHouse/Goldengate/Bitstream/ProNS --
> Network Engineer/Provisioning/Jack of all Trades
>
> ########################################################################
>
> To unsubscribe from the MICE-DISCUSS list, click the following link:
> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
########################################################################
To unsubscribe from the MICE-DISCUSS list, click the following link:
http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1
|