(I'm the one who posted the original question). Just tested it again with a second stack of 3750E's ; this gave the same result : Upgrading from 12.2.2(35) to 12.2.(46) and reload of second switch gave a Version Mismatch with left the second switch hanging. Only a reload of the master restored full functionality. After that, I replaced the ip base image with the one with encryption (k9 version), however same versionnumber 12.2(46). This went as described below, second one came back online and became again member of the stack without problem allowing reload of first one. So my conclusion is that the possibility to upgrade a stack without losing full connectivity is different for each upgrade and you can't tell in advance if it will result in a version mismatch or not.
Feel free to comment if you have different experiences. Wim Holemans -----Original Message----- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Peter Rathlev Sent: maandag 26 januari 2009 19:38 To: Tony Varriale Cc: cisco-nsp@puck.nether.net 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 _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/