Got it

The product model is inconsistent with the system configuration.

137 0 0 0 0

Hi team!

Here's a case that The product model is inconsistent with the system configuration.


Possible Causes

The product model must be consistent with the system configuration to ensure that the system can run properly. 

When the system is started, the system checks whether the product model is consistent with the system configuration. 

If the product model is inconsistent with the system configuration, the check is not passed and the system fails to be started.



Recommended Actions

Clear the configuration data and power on the system again. The operation procedure is as follows:

1. Use an SSH tool, such as Xshell 5, PuTTY 0.63, SecureCRT 6.7, or one of their later versions, to log in as user admin 

    (the default password is Admin@storage) to the management network port on the storage device.


2. Run the showsysstatus command to check whether the current node ID is the same as that of the master node in the cluster. 

If the current node ID is the same as that of the master node in the cluster, the current node is the master node.

Storage: minisystem> showsysstatus

Show system status

admin:/diagnose>sys showcls

mode             : normal             

status           : none               

node cfg         : 2                  

node max         : 4                  

group cfg        : 1                  

group max        : 2                   

product          : 0                  

serial           : SNxxxxxxxxxxxxxxxxxxxx

WWN              : 0xxxxxxxxxxxxxxxxxxx

local node id    : 1

normalNodeBitmap : 3

faultNodeBitmap  : 0

offlineNodeBitmap: 0

standbyNodeBitmap: 0

     id          role        status        group       engine    

 ----------   ----------   ----------   ----------   ----------

 0            master       normal       0            0           

 1            slave1       normal       0            0           

admin:/diagnose>exit

Storage: minisystem>


3. Run the cleardb command on the master node to clear the configuration data in the system.

Storage: minisystem> cleardb

DANGER: You are going to clear the configuration data of the storage system and the previous configuration data will be lost.

Suggestion: Before you perform this operation, export the configuration data .

Have you read danger alert message carefully?(y/n)

y

Clear db in all mediums begin......

admin:/diagnose>db clearall

This is DB (cluster master) controller .

Success !!

admin:/diagnose>exit

Storage: minisystem>


4. Run the rebootsys command respectively on each controller to restart the system.

Storage: minisystem> rebootsys

Are you sure to restart?(y/n)

y



Check After Recovery

After restarting all nodes, check whether the same error code appears. 

If no, the fault is rectified and no action is required. 

If yes, contact R&D engineers

Comment

You need to log in to comment to the post Login | Register

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.