Replacing MSM: Software incompatible
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-27-2015 04:36 PM
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?
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-28-2015 11:44 AM
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
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-28-2015 11:44 AM
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:
SysLocation:
SysContact:
System MAC:
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
Got both MSMs In Sync and all versions sorted out? Here's an example from one of my lab cores.
# show switch
SysName:
SysLocation:
SysContact:
System MAC:
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-28-2015 11:44 AM
Thanks for the info.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-28-2015 09:00 AM
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).
