Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
4 replies Latest Post - ‏2014-06-17T02:20:50Z by 163zsm
SystemAdmin
SystemAdmin
4779 Posts
ACCEPTED ANSWER

Pinned topic DS4700 - SubmodMis lockdown

‏2012-10-23T21:02:30Z |
The second controller (B) of my DS4700, going to SubmodMis lockdown state every time when i try to reboot it.
I can start my DS4700 with single controller (A or B - doesn't matter) and storage works fine. But when i try to use both controllers - controller B is going to lockdown state.
As i can see through controller shell, the Submodel ID is not set for the controller B. Previously, the NVSRAM of the controller B was reinitialized, and the NVSRAM was reflashed from the file by XMODEM.
Is there a way to set Submodel Id through the controller shell or via SMcli?
I have supportData for this array.
Updated on 2012-11-10T15:38:04Z at 2012-11-10T15:38:04Z by SystemAdmin
  • Tulein
    Tulein
    33 Posts
    ACCEPTED ANSWER

    Re: DS4700 - SubmodMis lockdown

    ‏2012-10-25T02:48:38Z  in response to SystemAdmin
    Try these commands via shell with the working controller (A or B)

    loadDebug
    lemClearLockdown
    • SystemAdmin
      SystemAdmin
      4779 Posts
      ACCEPTED ANSWER

      Re: DS4700 - SubmodMis lockdown

      ‏2012-10-25T09:58:51Z  in response to Tulein
      After lemClearLockdown the working controller goes to reboot and then reports: Controller B Invalid-SubModel ID, and then lock controller B down

      When i run the following commands on failed controller (B):
      getCurrentSubModelId
      its reports
      value = 0 = 0x0
      And getCurrentSubModelId reports the same
      value = 0 = 0x0
      On the working controller (A) i have a different output for these commands
      getCurrentSubModelId
      value = 19 = 0x13
      getMfgSubModelId
      value = 19 = 0x13

      I was able to set CurrentSubModelId on the failed controller (B) via
      setCurrentSubModelId and bcmNvsramSet_Current_SubModel and now
      getCurrentSubModelId reports the value = 19 = 0x13
      But getMfgSubModelId reports the value = 0 = 0x0 and after running lemClearLockdown controller B reports SubmodMis Lockdown

      Is there way to set MfgSubModelId via controller shell? I think the main reason of the lockdown is Incorrect Mfg SubModelId record.
      • SystemAdmin
        SystemAdmin
        4779 Posts
        ACCEPTED ANSWER

        Re: DS4700 - SubmodMis lockdown

        ‏2012-11-10T15:38:04Z  in response to SystemAdmin
        Hi,

        I have same problem.
        Can you tell me the syntax of setCurrentSubModelId and bcmNvsramSet_Current_SubModel command ?

        I think we need to update the following NVSRAM section:
        NVSRAM 'MfgSec' group, size=64:

        +0000: 13 00 00 00 33 39 4D 35 38 39 36 00 00 00 00 00 |....39M5896.....|
        +0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
        +0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
        +0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      • 163zsm
        163zsm
        2 Posts
        ACCEPTED ANSWER

        Re: DS4700 - SubmodMis lockdown

        ‏2014-06-17T02:20:50Z  in response to SystemAdmin

        can you tell me how to use setCurrentSubModelId,  and  do you know password of 15) Manufacturing Setup Menu