Upgrading from 2.5 to 3.2.1 or 3.x -- experiences?

  • 1
  • Question
  • Updated 1 year ago
Greetings everyone,

we are getting ready to upgrade our first pair of Cumulus switches (they are an MLAG pair) from 2.5 to 3.2.1 -- the release notes are pretty brief as to how this upgrade goes:

  1. boot secondary switch to ONIE
  2. Install 3.2.1 on secondary, and reprovision (we use Ansible for this).  During this all traffic expected to flow via primary
  3. boot primary switch to ONIE, causing all traffic to fail over to Secondary
  4. install 3.2.1 on primary and reprovision
  5. This is the step that is a bit confusing.  we have to disable clagd, restart networking and quagga, then re-enable clagd?  Presumably on both systems.  This bit is unclear, and seems it would cause some level of outage impact.  do we have to do it to both at the same time, or one then the other?

Curious if anyone else has gone through the process and what their experience was.


Photo of Will McLendon

Will McLendon

  • 440 Points 250 badge 2x thumb

Posted 1 year ago

  • 1
Photo of Eric Pulvino

Eric Pulvino, Official Rep

  • 3,868 Points 3k badge 2x thumb
I would also add that you want to down the host-facing links on the secondary immediately before the upgrade and similarly keep them down until you're ready to turn up the secondary on 3.2.1. Keep in mind CLAG compatibility is not tested between 2.5 and 3.x so there will likely be some minimal downtime there, so reserve this activity for a proper maintenance window. 

I'll ask our support folks to chime in here for any additional info.