[c-nsp] 1Gig->10Gig port-channel migration

[Tom Storey]

If minimal impact is the worst you want to experience, is there any reason
this cant be done during network trough, i.e. (usually) early morning?

To pop a couple of 1g links out of the bundle then add the 10g links in
couldnt take more than a couple of minutes. Send a memo to your most
important users/customers and/or stick something up on your website a month
in advance and let people know about an impending brief disruption to enable
improvements to the network.

Thats what I'd do anyway, and take the the day off, come in later, or work
from home.

I just get the feeling that if you want to go to the trouble of migrating
the old links to a new Po interface for the sake of cosmetics, you might
aswell just go for broke. :-)


On 13 October 2011 16:03, Tim Durack <tdurack at gmail.com> wrote:

> I'm looking for ideas on a "smart" way to upgrade a 4x 1Gig
> port-channel to a 2x 10Gig port-channel with minimal/no impact.
>
> Port-channel connects two 6500s, 12.2(33)SXI6, collapsed
> core/aggregation/WAN/Internet/P/PE (we like to maximize ROI :-)
>
> The port-channel is the pop backbone, trunking a bunch of L2 VLANs,
> and one L3 VLAN for routing. MSTP is used and stable, 10s-100s of
> access and server switches are redundantly connected back to a pair of
> core 6500s.
>
> I had hoped I could add the 10Gig links to the existing port-channel,
> and remove the 1Gig links.
>
> Next best idea is to migrate the 1Gig port-channel to Po2, and create
> a new Po1 with 10Gig links (I would like to maintain Po1 as the pop
> backbone.)
>
> Any suggestions?
>
> --
> Tim:>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>