[c-nsp] upgrading stack of 3750E's

[Tony Varriale]

In this example, there are only 2 switches.

The first switch comes up as sees the second as  incompatible.  Hence, the 
reload of that second.

After the first comes up and the stack "is aware", the first switch is 
functioning and has it's config.  The second...not so much.

Note this isn't a normal process and this problem only occurs across certain 
IOS.

Lab it up see if you get the same thing.  I've had to do this (from 35 to 
46) to about 40 3750E and 3750s recently.

tv
----- Original Message ----- 
From: "Peter Rathlev" <peter at rathlev.dk>
To: "Tony Varriale" <tvarriale at comcast.net>
Cc: <cisco-nsp at puck.nether.net>
Sent: Monday, January 26, 2009 12:37 PM
Subject: Re: [c-nsp] upgrading stack of 3750E's


> On Mon, 2009-01-26 at 08:45 -0600, Tony Varriale wrote:
>> This is how I normally do it.
>>
>> 1) archive software to first switch /overwrite (from TFTP) without 
>> reload.
>> 2) archive software to second switch /overwrite without reload.
>> 3) reload slot 1
>> 4) wait until switch 1 is operational and you are happy
>> 5) reload slot 2
>
> Will this work? Wouldn't Stackwise see the two switches as incompatible?
> We've started using pairs of 3750E with a CX4 link between them and just
> plain rapid PVST+. Then we have some "guarantees" as to how the system
> functions during upgrades.
>
> Regards,
> Peter
>
>