"but once it's up" Yeah, that's the problem. Where we need it is on a production network that is serving customers who are very sensitive to downtime. We are close enough to Brocade that maybe I will see if I can run through the upgrade process in their Proof of Concept Lab first before we do it in that particular network. I think we can configure a couple of MLX to the same configuration we have in production and run through the upgrade process a couple of times in the lab first.
On Wed, Jan 12, 2011 at 5:53 AM, Jonathan Brashear <[email protected]> wrote: > In the last deployment I did involving MCT(it was a 2-level MCT config on the > MLX platform as well as between MLX & CES platforms) we used 5.1.00b and it > worked quite well. The technology has a little bit of a learning curve(at > least it did for me), but once it's up it runs like a champ. > > Jonathan Brashear > Brocade Resident Consultant, Americas BRCs, Advanced Services > [email protected] > Office: 214-887-7719 > Cell: 214-850-5986 > www.brocade.com > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Chris Marlatt > Sent: Wednesday, January 12, 2011 6:18 AM > To: George B. > Cc: [email protected] > Subject: Re: [f-nsp] XMR Software Upgrade Path from 4.0.1a > > On 01/11/2011 10:49 PM, George B. wrote: >> Is anyone here using the MCT feature on MLX/XMR ? > > We just deployed our first pair of CES switches using MCT and they're > running great so far. They're doing OSPF, VRRPE, etc - however no BGP. > > We'll be deploying a pair of core level MLX's using MCT (along with > pairs of CES's also running MCT) sometime this month. Our testing has > been quite positive with even some better than expected behaviour on a > simulated portion of our network that will need to continue to run PVST. > > It is still a new technology on Brocade gear but so far it seems stable > enough to take a chance and reap the benefits. > > Regards, > > Chris > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > > > > The information contained in this transmission may contain privileged and > confidential information. > It is intended only for the use of the person(s) named above. If you are not > the intended > recipient, you are hereby notified that any review, dissemination, > distribution or > duplication of this communication is strictly prohibited. If you are not the > intended recipient, > please contact the sender by reply email and destroy all copies of the > original message. > To reply to our email administrator directly, please send an email to > [email protected]. > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
