Replacing MSM: Software incompatible

  • 0
  • 1
  • Problem
  • Updated 3 years ago
  • Solved
We replaced an MSM on a BD8810. When we first installed it, It upgraded firmware and then came online. We had though that it had just installed new firmware to the new card and it was working as expected. However, now I have noticed that it actually pushed the updated firmware to the primary (currently unused) partition on the working MSM and now MSM-A and MSM-B have different firmware. The active MSM is using the secondary image at 12.2.2.7 (primary = 12.5.4.5), while the inactive MSM has both images at 12.5.4.5. If the active MSM fails will it now reboot because the images are incompatible?
Photo of craymond

craymond

  • 608 Points 500 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of Paul Russo

Paul Russo, Alum

  • 9,694 Points 5k badge 2x thumb
hello Craymond

So the switch is booted off the master secondary image on 12.2.2.7 and you just uploaded 12.5.4.5 into the primary image of the active MSM and it is then also added to the primary container of the secondary MSM. 

If that is correct you can do a show switch and see which image is set on next reboot.  Yes as of right now if the primary fails it will require an outage for the secondary to load the new image.  In order for the switch to have a new image it requires a reboot. ( yes there are certain instances where you can do it hitlessly)

If you want the secondary MSM to be just like the primary where it also has 12.2.2.7 in the primary then you can do a sync command to make them both the same.  The code and configs. Note that this will affect the CPU and may cause delay in some protocols so I recommend doing it on a off hour. 

I hope that helps

P
Photo of craymond

craymond

  • 608 Points 500 badge 2x thumb
Thanks Paul-
We didn't actually upload new firmware. All we did was install the blade, and it pushed the firmware to the active MSM's inactive partition, or it grabbed the image from the inactive partition and installed it. I don't remember the secondary version before hand, but I do remember the log saying something about syncing software versions. I also typed the image version wrong. the current active version is 15.2.2.7 not 12.2.2.7! Would doing a sync be better than downloading and installing the images to the inactive MSM?
Photo of OscarK

OscarK, ESE

  • 7,912 Points 5k badge 2x thumb
The Synchronize command is just designed for this purpose, it syncs the backup MSM with the active MSM to have the same software versions and files (like policy files and so on).
Photo of Paul Russo

Paul Russo, Alum

  • 9,694 Points 5k badge 2x thumb
Hello Craymond

Sync makes the two MSMs exactly the same without having to connect to a TFTP server and uploading and downloading the files to and from the MSMs.

You absolutely can download the code to the other MSM if you like with no issues. 

Thanks
P
Photo of craymond

craymond

  • 608 Points 500 badge 2x thumb
Thanks for the info.
Photo of Drew C.

Drew C., Community Manager

  • 40,674 Points 20k badge 2x thumb
Were you able to get everything sorted out with the info here in the thread?
Got both MSMs In Sync and all versions sorted out?  Here's an example from one of my lab cores.
# show switch

SysName: <snip>
SysLocation: <snip>
SysContact: <snip>
System MAC: <snip>
System Type: BD-8806

SysHealth check: Enabled (Normal)
Recovery Mode: All
System Watchdog: Enabled

Current Time: Thu Jul 30 15:18:22 2015
Timezone: [Auto DST Enabled] GMT Offset: -300 minutes, name is EST.
DST of 60 minutes is currently in effect, name is not set.
DST begins every second Sunday March at 2:00
DST ends every first Sunday November at 2:00

Boot Time: Wed Nov 19 06:08:15 2014
Boot Count: 47
Next Reboot: None scheduled
System UpTime: 253 days 8 hours 10 minutes 31 seconds

Slot: MSM-A * MSM-B
------------------------ ------------------------
Current State: MASTER BACKUP (In Sync)

Image Selected: primary primary
Image Booted: primary primary
Primary ver: 15.4.2.8 15.4.2.8
patch1-3 patch1-3
Secondary ver: 15.4.1.3 15.4.1.3

Config Selected: primary.cfg primary.cfg
Config Booted: primary.cfg primary.cfg

primary.cfg Created by ExtremeXOS version 15.4.2.8
578077 bytes saved on Thu Jul 9 14:40:06 2015