MSM B does not synchonize with MSM A


Hello,

We have a BD8806 with two MSM-48c slots. but Backup slot B is not syncing with slot A,
I checked Memory usage and only 4% is used!

Omurga_SW02.18 # show slot
Slots Type Configured State Ports Flags
-------------------------------------------------------------------------------
Slot-1 8900-10G24X-c 8900-10G24X-c Operational 24 M
Slot-2 8900-10G24X-c 8900-10G24X-c Operational 24 M
Slot-3 10G2Xc 10G2Xc Operational 2 M
Slot-4 10G2Xc Initializing 2
Slot-5 Empty 0
Slot-6 G48Tc(PoE) G48Tc(PoE) Operational 48 M
MSM-A MSM-48c Operational 0
MSM-B MSM-48c Present 0

Omurga_SW02.17 # show sw

SysName: Omurga_SW02
SysLocation: SAMULAS
SysContact: support@vegaalarm.com,+903224562228
System MAC: 00:04:96:99:55:75
System Type: BD-8806

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

Current Time: Tue Mar 6 16:04:52 2018
Timezone: [Auto DST Disabled] GMT Offset: 180 minutes, name is not set.
Boot Time: Tue Jan 2 11:51:13 2018
Boot Count: 14
Next Reboot: None scheduled
System UpTime: 63 days 4 hours 13 minutes 39 seconds

Slot: MSM-A * MSM-B
------------------------ ------------------------
Current State: MASTER BACKUP

Image Selected: primary primary
Image Booted: primary primary
Primary ver: 12.5.4.5 16.2.3.5
patch1-6
Secondary ver: 12.5.4.5 16.1.3.6

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

primary.cfg Created by ExtremeXOS version 12.5.4.5
487068 bytes saved on Tue Mar 6 08:59:51 2018

Your help is highly appriciated!
Yusuf

5 replies

Userlevel 6
Hello Yusuf,

Is it giving you an error? or failing during the synchronization?
Userlevel 6
Image differences ... you can't have one running 12.5 and the backup running 16.2.

You will need to downgrade B or update A.

To downgrade B to A's image you could force a sync. This should be not effect network and be non-impacting. A will copy it's primary and secondary images over to B and B will reboot and come back up synced. It would be better to upgrade to current code but you would have to have a system reboot for that due to code differences
EtherMAN wrote:

Image differences ... you can't have one running 12.5 and the backup running 16.2.

You will need to downgrade B or update A.

To downgrade B to A's image you could force a sync. This should be not effect network and be non-impacting. A will copy it's primary and secondary images over to B and B will reboot and come back up synced. It would be better to upgrade to current code but you would have to have a system reboot for that due to code differences

Hello@EtherMAN,

I cannot find 16.2, could you please help downloading it!?

Thank you
Yusuf
EtherMAN wrote:

Image differences ... you can't have one running 12.5 and the backup running 16.2.

You will need to downgrade B or update A.

To downgrade B to A's image you could force a sync. This should be not effect network and be non-impacting. A will copy it's primary and secondary images over to B and B will reboot and come back up synced. It would be better to upgrade to current code but you would have to have a system reboot for that due to code differences

And
- What if I did a , would I be able to run on B slot and upgrade A slot later?

- Is there any way to sync A from B?
Userlevel 6
you will need a valid support contract to access the downloading of images... You will need to call TAC if you do not have a contract and this is a new card to see what options you may have.

Reply