No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S5600T started failed and reported: ctrl mac in db diff from base board

Publication Date:  2012-11-05 Views:  60 Downloads:  0
Issue Description
There was a new set of S5600T, we configured it with a disk enclosure, cascaded the correlative devices and powered on, 30 minutes later, we login in the device, it still reported: device is starting, leads to can’t login in it normally.
Alarm Information
None
Handling Process
1. Exchange the two disk enclosures on site and power on again.
2. Clear out the device DB, restart. Login in the device command: “admin”, password: “Admin@storage”, while there appearing the note shows that we can’t login in the device normally, press the composite key “shift 9” immediately and enter into the debug mode. Then enter:  “mml” , execute the command: “nvram clearhead” to clear out the DB, then the device will restart automatically.

Root Cause
Login in the command interface of the device, command: “admin”, password: “Admin@storage”. While there appearing the note shows that we can’t login, press the composite key “shift 9” immediately and enter into the debug mode. Then enter: “mml”, execute the command: “sys status” to check the system’s status, and command “dev state” to check the cause of the starting failed. The onsite device prints the outcome is as follow: 


From the device’s status, we can see “master start DEV failed”, which means the device master start failed; the cause of this fault, see “ctrl mac in db diff from base board”, which means that the MAC address of the disk enclosure in the DB recorded in the controller is different with the reality.
Because there is a SSD hard disk in the S5600T controller’s management module and it contains the device’s DB information and records about the device while the device powering off unconventionally, when the device powering on, firstly, it will read the DB information in the controller, then match the DB information in the coffer, and then try to start. Combined the condition on site, the two sets of S5600T are both have only one disk enclosure, we doubt they have been powered on by the dealer and then sent to the site, and when they were installing on the site, the operators hadn’t noticed if the disk enclosure was matched with the controller enclosure, then caused the MAC address of the disk enclosure on site is different with the DB record in the controller enclosure, and finally leaded to start failed.
Suggestions
If the device started failed and reported: “ctrl sn in db diff from base board”. It’s the same reason with the above fault, and we solve it by the same process.

END