We are on a later code and using the EX4400's but when we have one on a different code, we see it in the show virtual chassis but it says not provisioned. We actually have to connect the OOB or mgmt individually and upgrade/downgrade to match but that there winds up being downtime while the VC reconfigures. It sure would be nice if we could swap chassis or change code without needing a reboot.
Original Message:
Sent: 11-15-2024 08:24
From: fb35523
Subject: Upgrading EX4300 from 18.4 to 19.4, VC-ports down after one member is upgraded
Well, this isn't some Cisco or Extreme crap that doesn't even have the capability to upgrade individual members. I fully understand that stepping from 18.4 to 19.4 is a big step. The fact that all 18.x and 19.x releases are EEOL releases, this means that I can only skip two and I skipped three. "For both standard EOL and EEOL releases, you can upgrade to the next three subsequent releases or downgrade to the previous three releases."
Upgrading a VC to a newer release should be possible without rebooting the whole thing (I know that's the safest way, though). I just might have to crank up the 4300's I have in the attic to test this. I know I have upgraded other EX VCs where the ones with differing versions go into linecard mode. The thing here is that the VC ports didn't even link up, so hence my specific question: was there such a huge change between 18.4 and 19.4 that the QSFP+ VC ports don't even link between those versions?
Original Message:
Sent: 11-15-2024 07:39
From: SURAJ SINGH
Subject: Upgrading EX4300 from 18.4 to 19.4, VC-ports down after one member is upgraded
Hi,
Whenever you are upgrading VC, Make sure upgrade all member and reboot entire VC in single shot. Because you upgraded members and reboot, due to different version it was happens once both device comes up on same version VC form.
Regards
Suraj Kant Singh
------------------------------
SURAJ SINGH
Original Message:
Sent: 11-15-2024 05:22
From: fb35523
Subject: Upgrading EX4300 from 18.4 to 19.4, VC-ports down after one member is upgraded
I'm upgrading some EX4300-32F VCs that are just setup and ready to replace (even more) ageing EX4200's. I was meaning to upgrade them one member at a time in order to be able to control the process but that didn't go according to plan. Did the whole QSFP+ VC port protocol change to the extent that the not yet upgraded EX4300 couldn't even get a link on them? This is what I did:
Member 0 and 1 on 18.4R3-S1, only member 0 had management port connected (nothing else, no real traffic, VC OK with dual QSFP+)
Member 1 upgraded to 19.4R3-S14, member 0 didn't even see link on VC ports, member 1 rebooted again after upgrade but no luck (thought it was a goner at this point)
Member 0 upgraded to 19.4R3-S14 and the VC is complete with both links up!
So, to settle my curiosity, was there such a major change in the VC port protocol or something that you don't even get link between an 18.4 member and a 19.4 one?