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 V3 Series V300R006

This document is applicable to OceanStor 18500 V3 and 18800 V3. Based on the CLI, this document describes how to use various commands classified by functions and how to set the CLI and manage the storage system through these commands. The document that you browse online matches the latest C version of the product. Click Download to download documents of other C versions.
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 ] | [ savememorydata ] | [ showsyslog ] | [ redoobjflow -i ] | [ disablebbustatuscheck ] | [ showflowstatus ] | [ modifyvnodepairinfo [ vnodeId ] [ vnodeWork ] ] | [ setabvnodecheck [ switch ] ] | cleanarbdisk | clearnode [ optype ] | resetengine [ optype ] | showinstrucheckflag | setinstrucheckflag [ flag ] | setabarbdiskcheck [switch]}

Parameters

Parameter

Description

Value

showflowstatus

Queries the status of an object.

-

modifyvnodepairinfo [vnodeId] [vnodeWork]

Modifies the virtual node information.

-

setabvnodecheck [switch]

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

-

-h

Shows help information.

-

-a

Displays functions of each subcommand of the SYS module.

-

showxnetref

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

-

showrpcref

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

-

cleardirtydataflag

Clears dirty data validity flags from the local engine.

-

clearvnodedirtydataflag [vnodeid]

Clears the dirty data validity flag of a specified virtual node.

-

showvnode

Queries virtual node information.

-

showflowtrace [flowid]

Queries the process of an object.

-

savememorydata

Saves the current node memory data to the coffer disk.

-

showsyslog

Shows information about system process logs.

-

redoobjflow -i

Is used to redo system processes.

-

disablebbustatuscheck

Disables the BBU status check during system power-on.

-

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".

-

clearnode

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

-

resetengine

1:resetengine -n: clears all controllers of the engine where the local controller resides. 2:resetengine -nf: clears all controllers of the engine where the local controller resides (not checking whether the controller is present). 3:resetengine -p: clears the local controller and its peer physical controller.

-

showinstrucheckflag

Query the CPU instruction check flag.

-

setinstrucheckflag [flag]

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

-

setabarbdiskcheck[switch]

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

-

Modes

Minisystem mode

Usage Guidelines

The sys.sh disablebbustatuscheck command enables users to manually disable 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 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.
  • Display responses to 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
  • Display RPC messages that the local controller does not respond to.
    Storage: minisystem> sys.sh showrpcref  
    admin:/diagnose>rpc showproc 
    admin:/diagnose>exit
  • Clear dirty data validity flags from the local engine.
    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
  • 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 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 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
  • View 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
  • 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> 
  • Show information about system process logs.
    Storage: minisystem> sys.sh showsyslog 
    admin:/diagnose>redolog showalllog 
         LogId        FlowType           LogInfo 
     ------- --------------- --------------- 
     0          NodeFaultPreLog ProcFaultNodeId: 0. 
    admin:/diagnose>exit
  • 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>
  • 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>
  • 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>
  • 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>
  • After a controller fails to be expanded 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>
  • 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 
    ..
  • 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 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>
  • Set the switch that is not to check the status of quorum disks 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> 

System Response

None

Translation
Download
Updated: 2019-07-12

Document ID: EDOC1000138389

Views: 497419

Downloads: 85

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next