Hi team!
Here's a case that When the storage system is started, an engine is not powered on.
Possible Causes
Check method: run the showsysstatus command in the mini-system to check the value of the node cfg field.
The value indicates the number of nodes configured for the storage array while the number of IDs indicates the number of nodes actually configured for the storage array.
Storage: minisystem> showsysstatus
Show system status
admin:/diagnose>sys showcls
mode : normal
status : none
node cfg : 2 //Number of controllers configured for the system
node max : 4 //Maximum number of nodes supported by the system
group cfg : 1 //Number of engines configured for the system
group max : 2 //Maximum number of engines supported by the system
product : 0
serial : 21XXXXXXXXXXXXXXXXXX
WWN : 0xXXXXXXXXXXXXXXXX
local node id : 0
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>
1. Scenario 1: The number of nodes that are configured is the same as that of actual nodes.
a. Cause 1: Some nodes are powered on relatively late.
b. Cause 2: An engine is not powered on.
2. Scenario 2: The number of nodes that are configured is different with that of actual nodes.
a. Cause 3: The configuration file that contains the number of nodes is modified after controllers are expanded.
b. Cause 4: The configuration file that contains the number of nodes is incorrectly set before delivery.
Recommended Actions
● Causes 1 and 2: Power on the engine and reset all nodes when all nodes can access the mini-system.
Run the rebootsys command on each node to reset them.
Storage:minisystem>rebootsys
Are you sure to restart this controller?(y/n)
y
● Causes 3 and 4: Modify the configuration file of the device in the mini-system.
(Perform this operation on each node.)
1. Modify the node configuration (applicable to different hardware types).
os_write_bay_cfg.sh[-i BayID] [-c ControllerTotal] [-t BayType] [-n] [-l] [-s] [-d]|[-a]
BayId: physical engine ID (one physical engine for one enclosure)
ControllerTotal: correct number of nodes that are configured
For example:
Physical engine 0 in a 6 U 4-controller enclosure: os_write_bay_cfg.sh-i 0 -c 4
Physical engine 1 in a 3 U 4-controller enclosure: os_write_bay_cfg.sh-i 1 -c 4
2. Synchronize the configuration to BMC.
(This operation is necessary for a device with a 3 U or 6 U enclosure but not necessary for a device with a 2 U enclosure.)
os_change_bayconfig.sh sync
3. Run the rebootsys command on each node to restart all nodes.
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.
