Reset Search
 

 

Article

A M2 module is stucked in HOST-OS mode (Ubuntu mode) when inserted with different OS bit version with M1 module while M1 is online

« Go Back

Information

 
TitleA M2 module is stucked in HOST-OS mode (Ubuntu mode) when inserted with different OS bit version with M1 module while M1 is online
Symptoms
When M1 is online and M2 is inserted with different OS version (e.g. M1 is 64bit OS and M2 is 32bit OS), then the M2 module will go into the HOST-OS mode (Ubuntu mode) and stucked in that mode.

[From M1]
SLX# show version
 
SLX-OS Operating System Software
SLX-OS Operating System Version: 18r.1.00
Copyright (c) 1995-2019 Extreme Networks Systems, Inc.
Firmware name:      18r.1.00b
Build Time:         17:36:32 Feb 28, 2019
Install Time:       08:55:36 Jun  4, 2019
Kernel:             2.6.34.6
 
Control Processor:  GenuineIntel
Memory Size:        SLXVM: 11724 MB   System Total: 32174 MB
 
System Uptime:   0days 0hrs 22mins 4secs
 
Slot    Name    Primary/Secondary Versions                         Status
---------------------------------------------------------------------------
M1      SLX-OS  18r.1.00b                                          ACTIVE*
                18r.1.00b              
         --> M2 is not displayed
 
SLX# sh mm
 
Slot  Type         Description                 ID      Status
----------------------------------------------------------------------
M1   MM v6        Management Module           179     ENABLED
M2   MM v6        Management Module           179     ENABLED        

               --> MM2 still recognized but in Ubuntu mode

[Console from M2]
Ubuntu 14.04 LTS HOST ttyS0
 
HOST login: root
Password:
Welcome to Ubuntu 14.04 LTS (GNU/Linux 3.14.17 x86_64)
Environment
  • SLX9850 Chassis
  • Version mismatch with M1 (64bit OS) and M2 (32bit OS) or vice-versa
  • When inserting M2 with different bit OS version while M1 is online
Cause
In dual MM environment, mixed bit-OS version between MMs is not supported.
Resolution
The MM stucked in HOST-OS mode should be recovered by netinstall with 64bit OS versions (e.g. 17r.2 or higher).
Please note that the netinstall should be done with 64bit OS versions due to another DEFECT.

Please refer following articles regarding how to netinstall:

How to perform netinstall on SLX9850 using USB:
How to perform netinstall on SLX platforms using NFS:

Both MM should be running on the same version and standby MM should be upgraded separately to the same version with primary MM. And same OS-bit version should be used in dual MM chassis to function correctly.
Additional notes
When mixed version (32bit/64bit) are seated in dual MM slot in power-off status and then power-on the chassis, the second M2 module will go into Faulty (53) status:
SLX# sh mm
 
Slot  Type         Description                 ID      Status
----------------------------------------------------------------------
M1   MM v6        Management Module           179     ENABLED
M2   MM v6        Management Module           179     FAULTY (53)
In this case, even though the M2 is in Faulty status, but the M2 module is not in stucked status with HOST-OS mode and also it can be online normally with its original version when trying to boot it alone.

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255