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>Search

Reminder

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

upgrade

Advanced O&M Command Reference

OceanStor 18000 and 18000F V5 Series V500R007

This document is applicable to OceanStor 18500 V5, 18800 V5, 18500F V5, and 18800F V5. Based on the CLI, this document describes how to use various commands classified by functionsand how to set the CLI and manage the storage system through these commands.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
sys.sh

sys.sh

Function

The sys.sh command is used to run commands related to the SYS module.

Format

sys.sh { -h | -a | showxnetref | showrpcref | cleardirtydataflag | clearvnodedirtydataflag [ vnodeid ] | showvnode | showflowtrace [ flowid ] | showfailedflowtrace | showtrace [traceid] | showfailedtrace | savememorydata | showsyslog | redoobjflow | disablebbustatuscheck | showflowstatus | modifyvnodepairinfo [ vnodeId ] [ vnodeWork ] | setabvnodecheck [ switch ] | cleanarbdisk | clearnode [ optype ] | resetengine [ optype ] | showinstrucheckflag | setinstrucheckflag [ flag ] | setabarbdiskcheck [switch] | shownofcls | showexpinfo | clearexpinfo | showallspecdiskinfo | showbmckey | clearbmckey [slotId] | modifyvnodeversion [ver] | showmsg [opt] | regbmckey [slotId] | releaselockhandle [optype] [right/id] [lockPid] [lockFuc] | showlockreqtmo [time] | showlockholdtmo [time]}

Parameters

Parameter

Description

Value

showsyslog Queries information about system process logs.

-

disablebbustatuscheck Disables the BBU status check during system power-on.

-

showexpinfo Queries controller expansion flow information.

-

clearnode
  • "clearnode -d": clears all data and configurations of the local controller and rolls back controller expansion information.
  • "clearnode -df": clears all data and configurations of the local controller and rolls back controller expansion information (not checking controller status).
  • "clearnode -b": clears all data and configurations of the local controller (not recovering the "bay_config" configuration file).
  • "clearnode -bf": clears all data and configurations of the local controller (not checking controller status and not recovering the "bay_config" configuration file).

-

showinstrucheckflag Queries the CPU instruction check flag.

-

setabarbdiskcheck[switch]
  • "setabarbdiskcheck 0": checks the status of quorum disks during system power-on.
  • "setabarbdiskcheck 1": does not check the status of quorum disks during system power-on.

-

showallspecdiskinfo Queries coffer disk information.

-

showbmckey Displays the quorum key value.

-

showflowstatus Queries the status of an object.

-

setabvnodecheck [switch] Sets the switch for the controller not to check abnormal virtual nodes when the controller restores power supply.

-

-a Displays functions of each subcommand of the SYS module.

-

showrpcref Displays RPC messages that the local controller does not respond to.

-

clearvnodedirtydataflag [vnodeid] Clears the dirty data validity flag of a specified virtual node.

-

showflowtrace [flowid] Queries the process of an object.

-

showfailedflowtrace Queries the failed process information about an object.

-

showtrace [traceid] Queries process information about a cluster.

-

showfailedtrace Queries the failed process information about a cluster.

-

savememorydata Saves the current node memory data to the coffer disk.

-

redoobjflow -i Redoes system processes.

-

cleanarbdisk
  • "cleanarbdisk -a": clears all quorum disk information.
  • "cleanarbdisk -l": clears local quorum disk information.
  • "cleanarbdisk -d [diskID]": clears information about the quorum disk whose ID is "diskID".

-

clearexpinfo Clears controller expansion flow information.

-

modifyvnodepairinfo [vnodeId] [vnodeWork] Modifies the virtual node information.

-

-h Displays help information.

-

showxnetref Displays responses to the XNET messages of the local node and other nodes.

-

cleardirtydataflag Clears dirty data validity flags from the local controller enclosure.

-

showvnode Queries virtual node information.

-

resetengine
  • "resetengine -n": clears all controllers in the controller enclosure where the local controller resides.
  • "resetengine -nf": clears all controllers in the controller enclosure where the local controller resides (not checking whether the controller is present).
  • "resetengine -p": clears the local controller and its peer physical controller.

-

setinstrucheckflag [flag]
  • "setinstrucheckflag 0": sets the CPU instruction check flag to the clear flag.
  • "setinstrucheckflag 1": sets the CPU instruction check flag to the isolated flag.
  • "setinstrucheckflag 2": sets the CPU instruction check flag to the skip flag.

-

shownofcls Queries node information about smart disk enclosures.

-

clearbmckey [slotId] Clears the quorum key value.

-

modifyvnodeversion [ver] Manually changes the multi-vnode version.

-

showmsg [opt] Displays details about the system msg process.

-

regbmckey [slotId] Registers the quorum key value.

-

releaselockhandle [optype] [right/id] [lockPid] [lockFuc] Forcibly unlocks system lock resources.

-

showlockreqtmo [time] Displays the lock application timeout list.

-

showlockholdtmo [time] Displays the lock holding timeout list.

-

Modes

Minisystem mode

Usage Guidelines

The "sys.sh disablebbustatuscheck" command enables users to manually disable the BBU status check. After this command is executed, dirty data may be lost if system power-off occurs. This command must be executed on the primary controller of a cluster.

Example

  • Display functions of each subcommand of the SYS module.

    Storage: minisystem> sys.sh -a
    sys.sh showxnetref                               : show xnet messages response information.
    sys.sh showrpcref                                : show RPC messages without response.
    sys.sh cleardirtydataflag                        : clear local-engine dirty data flag.
    sys.sh clearvnodedirtydataflag [vnodeid]         : clear vnode dirty data flag.
    sys.sh showvnode                                 : show vnode information.
    sys.sh showflowtrace [flowid]                    : show flow call trace info.
    sys.sh showfailedflowtrace                       : show failed flow call trace info.
    sys.sh showtrace [traceid]                       : show trace call trace info.
    sys.sh showfailedtrace                           : show failed trace call trace info.
    sys.sh savememorydata                            : save memory data when system power on failed.
    sys.sh showsyslog                                : show system failed flow.
    sys.sh redoobjflow                               : redo system failed flow,usage: sys.sh redoobjflow -i logId.
    sys.sh disablebbustatuscheck                     : ignore BBU state when system power on.
    sys.sh showflowstatus                            : show flow status.
    sys.sh modifyvnodepairinfo [vnodeId] [vnodeWork] : modify vnode pair information.
    sys.sh setabvnodecheck [switch]                  : set no check abnormal vnode switch.
    sys.sh cleanarbdisk                              : clear arbitration disks.
    sys.sh clearnode [optype]                        : clear all data of this node.
    sys.sh resetengine [optype]                      : reset all controllers of this engine.
    sys.sh showinstrucheckflag                       : show instruction check flag.
    sys.sh setinstrucheckflag [flag]                 : set instruction check flag.
    sys.sh setabarbdiskcheck [switch]                : set no check abnormal arbdisk force power on switch.
    sys.sh shownofcls                                : show ip enclosure node info.
    sys.sh showexpinfo                               : show expand-bay info.
    sys.sh clearexpinfo                              : clear expand-bay info.
    sys.sh showallspecdiskinfo                       : show all spec disk info.
    sys.sh clearbmckey                               : clear the quorum key value.
    sys.sh showbmckey                                : display the quorum key value.
    sys.sh modifyvnodeversion[ver]                   : manual modify vnode version.
    sys.sh showmsg [opt]                             : show sys msg info.
    sys.sh regbmckey [slotId]                        : register the quorum key value.
    sys.sh releaselockhandle [optype] [right/id] [lockPid] [lockFuc] : release system lock resource.
    sys.sh showlockreqtmo [time]                     : show system lock req time info.
    sys.sh showlockholdtmo [time]                    : show system lock hold time info.
  • Display responses to the XNET messages of the local node and other nodes.

    Storage: minisystem> sys.sh showxnetref
    admin:/diagnose>c_xnet showxnetref
    DstNid: 0, ref: 0
    DstNid: 1, ref: 0
    DstNid: 2, ref: 0
    DstNid: 3, ref: 0
    DstNid: 4, ref: 0
    DstNid: 5, ref: 0
    DstNid: 6, ref: 0
    DstNid: 7, ref: 0
    DstNid: 8, ref: 0
    DstNid: 9, ref: 0
    DstNid: 10, ref: 0
    DstNid: 11, ref: 0
    DstNid: 12, ref: 0
    DstNid: 13, ref: 0
    DstNid: 14, ref: 0
    DstNid: 15, ref: 0
    admin:/diagnose>exit
  • Clear dirty data validity flags from the local controller enclosure.

    Storage: minisystem> sys.sh cleardirtydataflag
    You are about to clear the dirty data flag.
    1.This operation will cause service data loss. Do you know the severity and still want to continue? (y/n)
    y
    2.This command brings irreversible results. The system cannot be restored to the original status after this command is executed. Do you know the severity and still want to continue? (y/n)
    y
    admin:/diagnose>sys cleardirtydataflag
    Clear dirty data flag succeeded.
    admin:/diagnose>exit
  • Query virtual node information.

    Storage: minisystem> sys.sh showvnode 
    admin:/diagnose>sys showvnode
    VnodeId WorkNode MirrorNode HomeNode PairStatus VnodeStatus 
    -------------------- -------------------- -------------------- -------------------- -------------------- --------------------
    0 0 1 0 double clean 
    1 1 0 1 double clean 
    admin:/diagnose>exit
  • Query details about process "8".

    Storage: minisystem> sys.sh showtrace 8
    admin:/diagnose>sys showtrace 8
    NODE_POWER_ON : 
     TotalRunCnt   TotalFailCnt   CurStatus 
     -----------   ------------   --------- 
     1             0              Success
     id         date time             second            current trace              
     ----   -------------------   -------------   ---------------------------------------- 
     0000   2000-01-15 14:16:35   433.053127    NODE_POWER_ON: Wait OS hotpatch active  
     0001   2000-01-15 14:16:35   433.053157    NODE_POWER_ON: clean soft ac down flag  
     0002   2000-01-15 14:16:35   433.053171    NODE_POWER_ON: Notify CMM Start Work    
     0003   2000-01-15 14:16:40   437.848390    NODE_POWER_ON: Recover mem data         
     0004   2000-01-15 14:16:40   438.060808    NODE_POWER_ON: Notify SWM UpgradeFW     
     0005   2000-01-15 14:16:50   448.147055    NODE_POWER_ON: Start cls fencing        
     0006   2000-01-15 14:16:50   448.274387    NODE_POWER_ON: Join In Cluster          
     0007   2000-01-15 14:16:50   448.274402    NODE_POWER_ON: Compete Role             
     0008   2000-01-15 14:16:52   450.274537    NODE_POWER_ON: Task Over                
    admin:/diagnose>exit
    Storage: minisystem>
  • Query failed process details of a cluster.

    Storage: minisystem> sys.sh showfailedtrace
    admin:/diagnose>sys showfailedtrace
       ID          Date Time            Failed Flow Name                 Failed Action Name  
     ------  ---------------------  ------------------------------  ------------------------------
    admin:/diagnose>exit
    Storage: minisystem>
  • Query details about process "57".

    Storage: minisystem> sys.sh showflowtrace 57
    admin:/diagnose>sys showflowtrace 57
    FLOW_DISK_EVENT_IN : 
    TotalRunCnt TotalFailCnt CurStatus 
    ----------- ------------ --------- 
    9 0 Success
    id date time phase current step 
    ---- ------------------- ----- --------------------------------------------
    0000 2015-08-03 11:23:26 0 disk event handle 
    2015-08-03 11:23:26 DiskIn-1 GetDiskInfo 
    2015-08-03 11:23:26 DiskIn-2 DiskInHandle 
    2015-08-03 11:23:26 DiskEvent SetHandleEventTime 
    2015-08-03 11:23:26 DiskEvent TaskOver 
    admin:/diagnose>exit
  • Query failed process details of an object.

    Storage: minisystem> sys.sh showfailedflowtrace
    admin:/diagnose>sys showfailedflowtrace
       ID          Date Time             Flowid: Failed Flow Name             Phaseid: Failed Phase Name            Stepid: Failed Step Name            Failed Action Name      
     ------  ---------------------  -----------------------------------  -----------------------------------  -----------------------------------  -----------------------------------
    admin:/diagnose>exit
    Storage: minisystem>
  • Query information about system process logs.

    Storage: minisystem> sys.sh showsyslog
    admin:/diagnose>redolog showalllog
         LogId        FlowType           LogInfo
        -------    ---------------    ---------------
        0          NodeFaultPreLog    ProcFaultNodeId: 0.
    admin:/diagnose>exit
  • Modify the virtual node information.

    Storage: minisystem> sys.sh modifyvnodepairinfo 0 0
    admin:/diagnose>sys modifyvnodepairinfo 0 0
    Please input sys.sh showvnode to check pairinfo after modifying vnode pairinfo.
    admin:/diagnose>exit
    Storage: minisystem>
  • Clear all quorum disk information.

    Storage: minisystem> sys.sh cleanarbdisk -a
    You are about to clear arbitration disks.
    This operation may cause dual cluster masters to result in data inconsistency or may cause a power-on failure. Are you sure you want to perform this operation? (y/n)
    y
    admin:/diagnose>sys cleanarbdisk -a
    Clean ArbDisk: Clean arbdisk: return result(0)
    admin:/diagnose>exit
    Storage: minisystem>
  • Reset a controller enclosure.

    Storage: minisystem> sys.sh resetengine
    Are you sure to restart all the controllers of this engine? (y/n)
    y
    admin:/diagnose>sys resetengine
    WARNING: Parameter error! The operation cannot be performed.
    All parameters must be correct and maximum 1 parameters.
    Please input: sys.sh resetengine [optype]
    Parameter interpretation: -n - reset engine, check engine all node alive
                  -nf - reset engine force, ignore node not alive
                  -p - reset pair control, check pair node alive
    admin:/diagnose>exit
    Storage: minisystem>
    Storage: minisystem> sys.sh resetengine -n
    Are you sure to restart all the controllers of this engine? (y/n)
    y
    admin:/diagnose>sys resetengine -n
    ..
  • Set the CPU instruction check flag.

    Storage: minisystem> sys.sh setinstrucheckflag 0
    admin:/diagnose>sys setinstrucheckflag 0
    Record flag(code 0) to dmi success and should reboot controller to take effect.
    admin:/diagnose>exit
    Storage: minisystem>
  • Query node information about smart disk enclosures.

    Storage: minisystem> sys.sh shownofcls
    admin:/diagnose>sys shownofcls
    local node id    : 0
              id                    role                  status                 frameId
     --------------------   --------------------   --------------------   --------------------
     1131                   work                   normal                 65                  
     1130                   comm                   normal                 65                  
    admin:/diagnose>exit
    Storage: minisystem>
  • Query controller expansion flow information.

    Storage: minisystem> sys.sh showexpinfo
    admin:/diagnose>sys showexpinfo
    Local node(0) expand bay info:
    Expand bay state        :(0) [0:INIT,1:EXPANDING,2:PAUSE,3:ROLLBACK,4:ROLLBACK FAIL].
    Network mode            :(0) [0:DIRECT,1:SWITCH].
    Node num before expand  :(0).
    Total node num          :(0).
    Current step            :(0) [0:INIT,1:PARA_CHECK,2:NEW_CTRL_HANDLE,3:MODIFY_BAY,4:SYNC_VERSION,5:ORI_CTRL_HANDLE,6:REBOOT_NEW_CTRL,7:WAIT_POWER_ON].
    Current step result     :(0) [0:INIT,1:SUCCESS,2:FAIL].
    Current step remain time:(0S).
    admin:/diagnose>exit
    Storage: minisystem>
  • Query coffer disk information.

    Storage: minisystem> sys.sh showallspecdiskinfo
    admin:/diagnose>specdisk showallinfo
     Engine ID: 0
     diskId frame ftype slot disk SN state health node link disk Bom disk BarCode
     ------------ ------ ------ ------ -------------------------------- ------ ------ ---------------- ------------------------ --------------------------------
     1090519040 0 0 0 HS000000000000029838 0 0 0,1,-1,-1 02352UNW 2102352UNW2019071704
     1090519042 0 0 2 2102350STQ10G7000141 0 0 0,1,-1,-1 02352UNW 2102352UNW2019071701
     1090519041 0 0 1 HS000000000000195692 0 0 1,0,-1,-1 02352UNW 2102352UNW2019071702
     1090519043 0 0 3 2102350SSK10GA004891 0 0 1,0,-1,-1 02352UNW 2102352UNW2019071703
     --------------------------------- 
     Engine ID: 1
     diskId frame ftype slot disk SN state health node link disk Bom disk BarCode
     ------------ ------ ------ ------ -------------------------------- ------ ------ ---------------- ------------------------ --------------------------------
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     --------------------------------- 
     Engine ID: 2
     diskId frame ftype slot disk SN state health node link disk Bom disk BarCode
     ------------ ------ ------ ------ -------------------------------- ------ ------ ---------------- ------------------------ --------------------------------
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     --------------------------------- 
     Engine ID: 3
     diskId frame ftype slot disk SN state health node link disk Bom disk BarCode
     ------------ ------ ------ ------ -------------------------------- ------ ------ ---------------- ------------------------ --------------------------------
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     --------------------------------- 
     Engine ID: 4
     diskId frame ftype slot disk SN state health node link disk Bom disk BarCode
     ------------ ------ ------ ------ -------------------------------- ------ ------ ---------------- ------------------------ --------------------------------
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     --------------------------------- 
     Engine ID: 5
     diskId frame ftype slot disk SN state health node link disk Bom disk BarCode
     ------------ ------ ------ ------ -------------------------------- ------ ------ ---------------- ------------------------ --------------------------------
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     --------------------------------- 
     Engine ID: 6
     diskId frame ftype slot disk SN state health node link disk Bom disk BarCode
     ------------ ------ ------ ------ -------------------------------- ------ ------ ---------------- ------------------------ --------------------------------
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     --------------------------------- 
     Engine ID: 7
     diskId frame ftype slot disk SN state health node link disk Bom disk BarCode
     ------------ ------ ------ ------ -------------------------------- ------ ------ ---------------- ------------------------ --------------------------------
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     4294967295 65535 2 65535 3 3 -1,-1,-1,-1 
     ---------------------------------
  • Clear the quorum key value.

    Storage: minisystem> sys.sh clearbmckey 0
    You are about to clear bmc key info.
    This operation may cause dual cluster masters to result in data inconsistency or may cause a power-on failure. Are you sure you want to perform this operation? (y/n)
    y
    admin:/diagnose>sys clearbmckey 0
    Clear bmc slot(0) ret(0).
     admin:/diagnose>exit
  • Upgrade multi-vnode manually.

    Storage: minisystem> sys.sh modifyvnodeversion V2
    DANGER: You are going to perform a danger command, this behavior will force modify system Multi-vnode configurations.
    If not by the engineer, it is strongly recommended that you do not perform this operation. Are you sure you really want to perform the operation?(y/n)
    y
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    admin:/diagnose>sys modifyvnodeversion V2
    Upgrade quest add success, please wait for seconds.
    Human upgrade vnode config to Multi-vnode success.
    admin:/diagnose>exit
    Storage: minisystem>
  • Display RPC messages that the local controller does not respond to.

    Storage: minisystem> sys.sh showrpcref 
    admin:/diagnose>rpc showproc
    admin:/diagnose>exit
  • Clear the dirty data validity flag of a specified virtual node.

    Storage: minisystem> sys.sh clearvnodedirtydataflag 0
    You are about to clear the dirty data flag.
    1.This operation will cause service data loss. Do you know the severity and still want to continue? (y/n)
    y
    2.This command brings irreversible results. The system cannot be restored to the original status after this command is executed. Do you know the severity and still want to continue? (y/n)
    y
    admin:/diagnose>sys clearvnodedirtydataflag 0
    admin:/diagnose>exit
  • Query the process of an object.

    Storage: minisystem> sys.sh showflowtrace
    admin:/diagnose>sys showflowtrace
    Date Time FlowId FlowName RunCnt FailCnt Status 
    ------------------- ------ ------------------------------ ------ ------- ------ 
    2015-08-03 11:23:10 3 FLOW_OBJ_CLS_PWR_ON 1 0 Success 
    2015-08-03 11:23:26 57 FLOW_DISK_EVENT_IN 9 0 Success 
    admin:/diagnose>exit
  • Save the current node memory data to the coffer disk.

    Storage: minisystem> sys.sh savememorydata
    admin:/diagnose>sys savememorydata
    Create save memory data flow succeeded.
    admin:/diagnose>exit
    Storage: minisystem>
  • Redo system processes.

    Storage: minisystem> sys.sh redoobjflow -i 0
    admin:/diagnose>sys redoobjflow -i 0
    admin:/diagnose>exit
  • Disable the BBU status check during system power-on.

    Storage: minisystem> sys.sh disablebbustatuscheck
    admin:/diagnose>sys disablebbustatuscheck
    Set power on not check BBU status succeeded.
    admin:/diagnose>exit
    Storage: minisystem>
  • Query the status of an object.

    Storage: minisystem> sys.sh showflowstatus
    admin:/diagnose>sys showflowstatus
    sequenceNumber       :    33
    FlowClusterServiceStatus  :    Normal
    FlowNodeServiceStatus(id 0):    Normal
    FlowNodeServiceStatus(id 1):    Normal
    FlowNodeServiceStatus(id 2):    Normal
    FlowNodeServiceStatus(id 3):    Normal
    admin:/diagnose>exit
    Storage: minisystem>
  • Set the switch for the controller not to check abnormal virtual nodes when the controller restores power supply.

    Storage: minisystem> sys.sh setabvnodecheck 1
    admin:/diagnose>sys setabvnodecheck 1
    set no check abnormal vnode switch is (1) (0: FALSE 1:TRUE).
    admin:/diagnose>exit
    Storage: minisystem>
  • After a controller fails to be added and is rolled back, clear all data of the controller.

    Storage: minisystem> sys.sh clearnode
    You are about to clear all data of this node.
    1.This operation will cause service data loss and roll back cluster configurations. Do you know the severity and still want to continue? (y/n)
    y
    2.This command brings irreversible results. The system cannot be restored to the original status after this command is executed. Do you know the severity and still want to continue? (y/n)
    y
    admin:/diagnose>sys clearnode
    WARNING: Parameter error! The operation cannot be performed.
    All parameters must be correct and maximum 1 parameter.
    Please input: sys.sh clearnode [optype]
    Parameter interpretation: -d - clear node with first four disk, check node status
                  -df - clear node with first four disk, ignore node status
                  -b - clear node without restore bay-config, check node status
                  -bf - clear node without restore bay-config, ignore node status
    admin:/diagnose>exit
    Storage: minisystem> sys.sh clearnode -d
    You are about to clear all data of this node.
    1.This operation will cause service data loss and roll back cluster configurations. Do you know the severity and still want to continue? (y/n)
    y
    2.This command brings irreversible results. The system cannot be restored to the original status after this command is executed. Do you know the severity and still want to continue? (y/n)
    y
    admin:/diagnose>sys clearnode -df
    Start clear, local nid(Id: 2), wait ........................
    ******************* Clear Node info: ******************
    Proc: Clear Mem Recovery, Result: PASS
    Proc: Clear CCDB, Result: PASS
    Proc: Stop DB, Result: PASS
    Proc: Stop LOGZONE, Result: PASS
    Proc: Clear OM, Result: PASS
    Proc: Clear Vmms, Result: PASS
    Proc: Clear NAS, Result: PASS
    Proc: Clear Coffer, Result: PASS
    Proc: Clear Disk, Result: PASS
    Proc: Clear Bay-Config, Result: PASS
    Clear node succeeded.
    admin:/diagnose>exit
    Storage: minisystem>
  • Query the CPU instruction check flag.

    Storage: minisystem> sys.sh showinstrucheckflag
    admin:/diagnose>sys showinstrucheckflag
    The check flag is 0x0(0:clear 1:isolation 2: bypass other:default).
    admin:/diagnose>exit
  • Set the switch of not checking quorum disk status during power-on.

    Storage: minisystem> sys.sh setabarbdiskcheck 1
    admin:/diagnose>sys setabarbdiskcheck 1
    set no check abnormal arbdisk switch is(1) (0: FALSE 1:TRUE)
    admin:/diagnose>exit
    Storage: minisystem>
  • Clear controller expansion flow information.

    Storage: minisystem> sys.sh clearexpinfo
    Are you sure to clear all the expand-bay info of this engine? (y/n)
    y
    admin:/diagnose>sys clearexpinfo
    Clear expand bay info finish.
  • Display the quorum key value.

    Storage: minisystem> sys.sh showbmckey
    admin:/diagnose>sys showbmckey
    Slot[0] key(0x00fec00000000000).
    Slot[1] key(0x10fec00000000000).
    Slot[2] key(0xffffffffffffffff).
    Slot[3] key(0xffffffffffffffff).
    Slot[4] key(0xffffffffffffffff).
    Slot[5] key(0xffffffffffffffff).
    Slot[6] key(0xffffffffffffffff).
    Slot[7] key(0xffffffffffffffff).
  • Display system message records.

    Storage: minisystem> sys.sh showmsg
    admin:/diagnose>sys showmsg
    Please input: sys showmsg [optype] 
                  0 - show all 
                  1 - show latest 
                  2 - show err 
                  3 - show send 
                  4 - show recv 
    admin:/diagnose>exit
    Storage: minisystem>
  • Register the quorum key value.

    Storage: minisystem> sys.sh regbmckey 0
    You are about to register arbitration information.
    This operation may cause dual cluster masters to result in data inconsistency or may cause a power-on failure. Are you sure you want to perform this operation? (y/n)
    y
    admin:/diagnose>sys regbmckey 0
    Reg bmc slot(0) key(0xfec00000000000) ret(0).
    admin:/diagnose>exit
    Storage: minisystem>
  • Release system lock resources.

    Storage: minisystem> sys.sh releaselockhandle 0 1 47 diagReleaseLockhandle
    DANGER: You are going to perform a danger command, this behavior will force release system lock resource.
    If the operation is incorrect, data may be damaged or the controller will restart unexpectedly. Are you sure you want to continue?
    If not by the engineer, it is strongly recommended that you do not perform this operation. Are you sure you really want to perform the operation?(y/n)
    y
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    admin:/diagnose>sys releaselockhandle 0 1 47 diagReleaseLockhandle
    Command execute success, please check the result after a moment.
    admin:/diagnose>exit
  • Display the lock application timeout list.

    Storage: minisystem> sys.sh showlockreqtmo 5
    admin:/diagnose>sys showlockreqtmo 5
    No time out(5 sec) CLM lock.
    admin:/diagnose>exit
    Storage: minisystem>
  • Display the lock holding timeout list.

    Storage: minisystem> sys.sh showlockholdtmo 5
    admin:/diagnose>sys showlockholdtmo 5
    No time out(5 sec) CLM lock.
    admin:/diagnose>exit
    Storage: minisystem>

System Response

None

Translation
Download
Updated: 2020-01-17

Document ID: EDOC1000181602

Views: 757171

Downloads: 66

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next