cancel
Showing results for 
Search instead for 
Did you mean: 

VoSS version Mismatch the BCB & BEB and implications for Multicast

VoSS version Mismatch the BCB & BEB and implications for Multicast

Larry_S
New Contributor

 

A VSP supported campus requires an Upgrade.
The Campus is highly utilising multicast traffic.
Looking for information on Multicast traffic traversing the Fabric when the BCB and BEB are running differing Voss version for a period of time.

1 ACCEPTED SOLUTION

EXTR_Paul
Extreme Employee

Hi Larry. 

 

I recently went through this with a few other customers. 

I would not upgrade your cores all the way to v7.1.9, then try to upgrade the edge switches.

I am sure it will work, but there is no knowing how a vIST core running v7.1.9 is going to behave when all the edge switches are still running v4.X.  I can assure you that no one has tested that. 


Extreme engineering does regression testing, but not 7 years of regression testing. 

 

I would do the following

Upgrade the core to v5.1.X, then all the edge switches to v5.1.X.   Make sure everything is stable.

Then upgrade Core to v6.1.X. and Edge to v6.1.X.   Make sure everything is stable.

Then do the final v7.1.X for the core and edge.

View solution in original post

6 REPLIES 6

Larry_S
New Contributor

Miguel

Thank you form your reply.

Legacy VSP4.2.1.1 upgrading to Voss 7.1.9.x. Multiple upgrades

The intention is for the Core to Upgrade to Voss 7.1.9.x. immediately with the Edge being upgraded over a couple of hours. Multicast traffic can be lost for the respective edge VSP following the re-establishment of Multicast streams once Core are Upgrades and come back online.

Any thoughts or stability during the staggered Edge Upgrades.

Larry_S

 

 

Miguel-Angel_RO
Valued Contributor II

No issue as far as I know but you should provide the SW version you run.

Maybe there are some known issues on those.

Mig

GTM-P2G8KFN