SoftwareStatus = Software Status
cli_software_reservedMemory.name = Checking memory reservation
cli_software_reservedMemory.method = Step 1 Log in to the device as user admin.\nStep 2 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 3 Run the debug command to go to the diagnose mode.\nStep 4 Run the sys showmem command to check the memory reservation.\nStep 5 Log in to the other controller, and repeat steps 2 to 4.
cli_software_reservedMemory.criterion = 1 Check items in the RsvMemType, excluding the name field whose value is RsvMemType: RpcDbgInfo, or ends with _Const. If the used value of the reserved memory in any item is greater than or equal to the value of struct num, the reserved memory in the system is insufficient. Therefore, the check is not passed.\n2 If logging in to the other controller fails, the check result is Warning.\n3 Otherwise, the check is passed.
cli_software_reservedMemory.suggestion = Consequence: If this check item is not passed, an upgrade failure and service interruption may occur. Rectify the fault, and check again.\n1 If the alarm "Failed to connect to the controller" is displayed, redeploy the network correctly. For details, see Enterprise Huawei Storage Product Networking Assistant. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_software_reservedMemory.helphref = Enterprise Huawei Storage Product Networking Assistant{http://support.huawei.com/onlinetool/datums/nettool/index.en.jsp}

tlv_software_sysCompatible.name = Checking system software compatibility
tlv_software_sysCompatible.method = Step 1 Log in to the device as user admin. \nStep 2 Check whether the system software versions are compatible.
tlv_software_sysCompatible.criterion = If any software version in the version mapping list is inconsistent with that in the memory, the check is not passed.
tlv_software_sysCompatible.suggestion = Consequence: If this check item is not passed, an online upgrade is not allowed. Rectify the fault, and check again. \nIf the system software version is inconsistent, contact technical support engineers.

tlv_software_fwCompatible.name = Checking the compatibility (for the firmware version)
tlv_software_fwCompatible.method = Step 1 Log in to the device as user admin. \nStep 2 Run the show version all command to check the firmware version. \nStep 3 Run the change user_mode current_mode user_mode=developer command to go to the developer mode. \nStep 4 Run the minisystem command to go to the minisystem mode. \nStep 5 Run the cat /OSM/conf/versions.conf command to check the version mappings.\nStep 6 Run the exit command to exit the minisystem mode.
tlv_software_fwCompatible.criterion = If any firmware version displayed in step 2 is inconsistent with that displayed in step 5, the check is not passed.
tlv_software_fwCompatible.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again. \n1 If BBU versions are inconsistent, check whether a BBU intermixing alarm (ID: 0x000E01F40007ULL) exists on the DeviceManager. If yes, contact technical support engineers. If no, check the version mappings when the BBU status check items are passed. Remove the BBU that is inconsistent with the firmware version, and check again 10 minutes later. \n2 If the versions are still inconsistent after the recheck, replace the BBU that is inconsistent with the firmware version. For details, see the case. \n3 If other firmware versions are inconsistent, contact technical support engineers.\n\nNote: Run the exit command to exit the minisystem mode. Otherwise, a residual process may be left.
tlv_software_fwCompatible.helphref = case{/helpCase/en/topic/check_BBUVersion.html}

tlv_software_sysStatus.name = Checking system faults
tlv_software_sysStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 3 Run the debug command to go to the diagnose mode.\nStep 4 Run the sys showcls command to query the cluster status.\nStep 5 Run the sys showobjstatus command to query the object status.
tlv_software_sysStatus.criterion = 1 Check the mode value in the sys showcls command output. If the value is not normal, the check is not passed.\n2 Check the values of ClusterServiceStatus and ClusterServiceMode in the sys showobjstatus command output. If normal is not displayed, the check is not passed.
tlv_software_sysStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\nIf you have any questions, please contact technical support engineers for further handling.

tlv_software_sysResource.name = Checking system resources (CPUs and memory)
tlv_software_sysResource.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show controller general command to check the CPU usage.\nStep 3 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 4 Run the minisystem command to go to the minisystem mode.\nStep 5 Run the free -m command to check the free memory of the free field.\nStep 6 Run the exit command to exit the minisystem mode.
tlv_software_sysResource.criterion = 1 If the online upgrade is selected, the CPU usage is greater than 60%, or the free memory is smaller than 270 MB, the check is not passed.\n2 If the offline upgrade is selected, the CPU usage is greater than 85%, or the free memory is smaller than 270 MB, the check is not passed.
tlv_software_sysResource.suggestion = Consequence: If this item does not pass the check, services may be interrupted. Rectify the fault, and check again.\n1 If the CPU usage is high, reduce the service pressure, and check again. If this check item is still not passed, contact technical support engineers.\n2 If the free memory is insufficient, contact technical support engineers.\n\nNote: Run the exit command to exit the minisystem mode. Otherwise, a residual process may be left.

cli_software_sysProcesses.name = Checking system processes
cli_software_sysProcesses.method = Step 1 Log in to the device as user admin.\nStep 2 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 3 Run the debug command to go to the diagnose mode.\nStep 4 Run the sys showcmdlist command every 10s to check whether some processes are being executed. The command can only be run for three times at most.\nStep 5 Log in to the other controller, and repeat steps 2 to 4.
cli_software_sysProcesses.criterion = 1 If no commands that are being executed or to be executed are detected in RUNQ and WaitQ for once, checking on the current controller is passed. Otherwise, the check is not passed.\n2 If logging in to the other controller fails, the check result is Warning.\n3 Otherwise, the check is passed.
cli_software_sysProcesses.suggestion = Consequence: If this check item is not passed, an upgrade failure and service interruption may occur. Rectify the fault, and check again.\n1 If some processes in the system cannot pass the check, recheck when all processes have been executed.\n2 If the alarm "Failed to connect to the controller" is displayed, redeploy the network correctly. For details, see Enterprise Huawei Storage Product Networking Assistant. \n3 If you have any questions, please contact technical support engineers for further handling.
cli_software_sysProcesses.helphref = Enterprise Huawei Storage Product Networking Assistant{http://support.huawei.com/onlinetool/datums/nettool/index.en.jsp}

tlv_software_versionConsistance.name = Checking controller version consistency
tlv_software_versionConsistance.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show upgrade package command to check the current version of each node.
tlv_software_versionConsistance.criterion = Query the current version (Current Version) of each controller in Software Version. If the controller versions are inconsistent, the check is not passed.
tlv_software_versionConsistance.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\nIf you have any questions, please contact technical support engineers for further handling.

tlv_software_doubleCtrl.name = Checking whether each pair has dual controllers
tlv_software_doubleCtrl.method = Step 1 Log in to the device as user admin.\nStep 2 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 3 Run the debug command to go to the diagnose mode.\nStep 4 Run the sys showcls command to query the cluster status.
tlv_software_doubleCtrl.criterion = Compare the value of node cfg in the command output with the ID list in the current cluster. If the value of node cfg is the same as the number of IDs, the check is passed. Otherwise, the check is not passed.
tlv_software_doubleCtrl.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Check whether an alarm exists on the controller using the DeviceManager. If yes, replace the faulty controller. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
tlv_software_doubleCtrl.helphref = case{/helpCase/en/topic/check_DoubleController.html}

tlv_software_xnetPressure.name = Checking XNET pressure
tlv_software_xnetPressure.method = Step 1 Log in to the device as user admin.\nStep 2 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 3 Run the debug command to go to the diagnose mode.\nStep 4 Run the cmm show prlist 80 130 command to check the CMM memory.\nStep 5 Log in to the other controller, and repeat steps 2 to 4.
tlv_software_xnetPressure.criterion = 1 The following five items are displayed when you view the PartitionName:\nXNET_DATA_MSG\nXNET_RESPONSE\nXNET_ETH_MSG\nXNET_ETH_3K_MSG\nXNET_ETH_BIG_MSG\nIf the value of UsedCnt/TotalCnt*100% of any item is larger than 70%, the check is not passed.\n2 If logging in to the other controller fails, the check result is Warning.\n3 Otherwise, the check is passed.
tlv_software_xnetPressure.suggestion = Consequence: If this check item is not passed, data errors may occur. Rectify the fault, and check again.\n1 If the pressure of XNET is too high, reduce the service pressure, and check again five minutes later.\n2 If the alarm "Failed to connect to the controller" is displayed, redeploy the network correctly. For details, see Enterprise Huawei Storage Product Networking Assistant.\n3 If you have any questions, please contact technical support engineers for further handling.
tlv_software_xnetPressure.helphref = Enterprise Huawei Storage Product Networking Assistant{http://support.huawei.com/onlinetool/datums/nettool/index.en.jsp}

cli_software_sysConfigLog.name = Checking system configuration logs
cli_software_sysConfigLog.method = Step 1 Log in to the device as user admin.\nStep 2 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 3 Run the debug command to go to the diagnose mode.\nStep 4 Run the sys showcls command to view the value in the local node id field. If the value is 0, 1, 2, or 3, proceed to step 5.\nStep 5 Run the sys showcfglog command to check whether system configuration logs exist.
cli_software_sysConfigLog.criterion = 1 If the value in the local node id field is not 0, 1, 2, or 3 displayed in step 4, the check result is Warning.\n2 If the values of Total log num and Remain free log num field displayed in step 5 are equal, system configuration logs do not exist. Therefore, the check is passed.\n3 Otherwise, the check is not passed.
cli_software_sysConfigLog.suggestion = Consequence: If this check item is not passed, controller reset exception may occur after the upgrade. Rectify the fault, and check again.\nIf you have any questions, please contact technical support engineers for further handling.

tlv_software_frontPressure.name = Checking front-end pressure
tlv_software_frontPressure.method = Step 1 Log in to the device as user admin. \nStep 2 Check whether the front-end pressure is too high.
tlv_software_frontPressure.criterion = If the port usage exceeds 80% of the maximum bandwidth (theoretical), the check is not passed.
tlv_software_frontPressure.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again. \n1 If the front-end pressure is too high, reduce the service pressure, and check again five minutes later. \n2 If you have any questions, please contact technical support engineers for further handling.

tlv_software_sysAlarm.name = Checking system alarms
tlv_software_sysAlarm.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show alarm level=major number=10 command to check major alarms.\nStep 3 Run the show alarm level=critical number=10 command to check critical alarms.
tlv_software_sysAlarm.criterion = If major or critical alarms exist, the check is not passed.
tlv_software_sysAlarm.suggestion = Consequence: If this check item is not passed, an online upgrade is not allowed. Rectify the fault, and check again.\n1 If major or critical alarms exist, restore the alarms. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
tlv_software_sysAlarm.helphref = case{/helpCase/en/topic/check_UnrecoveredAlarms.html}

cli_software_hotSpareCapacity.name = Checking the Hotspare
cli_software_hotSpareCapacity.method = Step 1 Log in to the device as user admin.\nStep 2 Run show disk_domain general, and record the DiskDomainID. \nStep 3 Run show disk in_domain disk_domain_id=[DiskDomainID].
cli_software_hotSpareCapacity.criterion = 1 It is normal if there is no disk domain.\n2 If the value of Used Hot Spare Capacity is 0, it is normal. Or if disks in the disk domain are normal (The Health Status of disks is Normal, and the Running Status is Online), it is normal.\n3 Otherwise, it is abnormal.
cli_software_hotSpareCapacity.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Refer to the case to handle if the check does not pass.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_software_hotSpareCapacity.helphref = case{/helpCase/en/topic/check_HotSpareCapacity.html}

cli_software_lunStatus.name = LUN status
cli_software_lunStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show lun general |filterRow column=Health\\sStatus predict=not predict2=equal_to value=Normal logicOp=or column=Running\\sStatus predict=not predict2=equal_to value=Online command.
cli_software_lunStatus.criterion = 1 If the LUN does not exist, it is normal.\n2 If Health Status is Normal and Running Status is Online, the LUN status is normal. Otherwise, it is abnormal.
cli_software_lunStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal LUN.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_software_lunStatus.helphref = case{/helpCase/en/topic/check_LUNStatus.html}

cli_software_poolStatus.name = Checking the status of storage pool
cli_software_poolStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show storage_pool general command.
cli_software_poolStatus.criterion = 1 It is normal if there is no POOL.\n2 If Health Status is Normal and Running Status is Online or Balancing, the pool status is normal. \n3 Otherwise, it is abnormal.
cli_software_poolStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal POOL.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_software_poolStatus.helphref = case{/helpCase/en/topic/check_PoolStatus.html}

HardwareStatus = Hardware Status
cli_hardware_controllerStatus.name = Controller status
cli_hardware_controllerStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show controller general command.
cli_hardware_controllerStatus.criterion = If all controllers are online, Health Status is Normal, and Running Status is Online, the controllers are normal. Otherwise, they are abnormal.
cli_hardware_controllerStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Log in to DeviceManager to check whether there are alarms about controllers. If there are, recover the alarms based on the alarm handling suggestions. If you need to replace the controllers, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_controllerStatus.helphref = case{/helpCase/en/topic/check_ControllerStatus.html}

cli_hardware_enclosureStatus.name = Enclosure status
cli_hardware_enclosureStatus.method = Step 1 Log in to the device as user admin.\nStep2 Run the show enclosure command.
cli_hardware_enclosureStatus.criterion = 1 If the value of Logic Type of a enclosure equals to Data Switch, the enclosure is a data switch enclosure, it does not need to be checked. \n2 If Health Status is Normal and Running Status is Online, the enclosure is normal. Otherwise, it is abnormal.
cli_hardware_enclosureStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal enclosure. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_enclosureStatus.helphref = case{/helpCase/en/topic/check_EnclosureStatus.html}

cli_hardware_powerStatus.name = Power supply status
cli_hardware_powerStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show power_supply command.
cli_hardware_powerStatus.criterion = If Health Status is Normal and Running Status is Online, the power supply is normal. Otherwise, it is abnormal.
cli_hardware_powerStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal power supply. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_powerStatus.helphref = case{/helpCase/en/topic/check_PowerStatus.html}

cli_hardware_bbuStatus.name = BBU status
cli_hardware_bbuStatus.method = Step 1 Log in to the device as user admin.\nStep2 Run the show bbu general command.
cli_hardware_bbuStatus.criterion = The quantity of BBU in position meets specification requirements. Health Status is Normal and Running Status is Online, Charging or Discharging, the BBU is normal. Otherwise, it is abnormal.
cli_hardware_bbuStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal BBU. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_bbuStatus.helphref = case{/helpCase/en/topic/check_BBUStatus.html}

cli_hardware_bbuRemainLife.name = BBU remaining lifetime
cli_hardware_bbuRemainLife.method = Step 1 Log in to the device as user admin.\nStep 2 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 3 Run the show bbu life command.
cli_hardware_bbuRemainLife.criterion = The quantity of BBU in position meets specification requirements. Remaining Lifetime is less than 90 days, meaning that the BBU is expiring, please replace it as soon as possible.
cli_hardware_bbuRemainLife.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 If the Remaining Lifetime of a BBU is less than 90 days, please refer to the case to handle with it.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_bbuRemainLife.helphref = case{/helpCase/en/topic/check_BBURemainLife.html}

tlv_hardware_bbuPower.name = Checking BBU power
tlv_hardware_bbuPower.method = Step 1 Log in to the device as user admin. \nStep 2 Run the show file export_path file_type=log command. \nStep 3 In the /OSM/export_import path, download the collected logs, and open the IP_MAIN.tar.bz2/msg_other.zip/msg_other.tar.bz2/Other/pangea_mmlinfo file to check the MML command output: \nS5600T/S5800T/S6800T: bmc singlealarmget 6\nS2600T/S5500T: r2sas singlealarmget 6
tlv_hardware_bbuPower.criterion = Check the value of BBU backup alarm. 0 indicates that the system power backup is sufficient, the check is passed. 1 indicates that the system power backup is insufficient, the check is not passed.
tlv_hardware_bbuPower.suggestion = Consequence: If this check item is not passed, an upgrade may time out. Rectify the fault, and check again. \n1 If the BBU power is insufficient for the system power backup, resolve this issue. For details, see case. \n2 If you have any questions, please contact technical support engineers for further handling.
tlv_hardware_bbuPower.helphref = case{/helpCase/en/topic/check_BBUPower.html}

cli_hardware_fanStatus.name = Fan status
cli_hardware_fanStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show enclosure command.\nStep 3 Run the show fan command.
cli_hardware_fanStatus.criterion = The number of fan in every enclosure is not less than 2 , and Health Status is Normal and Running Status is Running, the fan is normal. Otherwise, it is abnormal.
cli_hardware_fanStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal fan. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_fanStatus.helphref = case{/helpCase/en/topic/check_FanStatus.html}

tlv_hardware_pcieLinkStatus.name = Checking PCIe links
tlv_hardware_pcieLinkStatus.method = Step 1 Log in to the device as user admin. \nStep 2 Run the show controller general command to check the number of controllers. If the device has four or more controllers, continue the check. \nStep 3 Run the change user_mode current_mode user_mode=developer command to go to the developer mode. \nStep 4 Run the debug command to go to the diagnose mode. \nStep 5 Run the sys showcls command to check the cluster information. \nStep 6 Run the xnet connect command to check the link status. \nStep 7 If current version is V100R001C00SPC300, continue the check. Run the dev dswgetip command to check the switch IP addresses.\nStep 8 Run the exit command to exit the diagnose mode. \nStep 9 Run the minisystem command to go to the minisystem mode. \nStep 10 Run the ping [switch IP] command separately based on the switch IP addresses. \nStep 11 Run the exit command to exit the minisystem mode. 
tlv_hardware_pcieLinkStatus.criterion = 1 If the device displayed in step 2 has dual controllers, the check is passed. \n2 If the device has four or more controllers, check the node ID (for example, 0, 1, 2, 3) whose status is normal displayed in step 5, and check whether the logic status displayed in step 6 from the local controller id to other normal nodes is running. If no, the check is not passed. For example, the local node ID is 0, if any logical status from the node 0 to node 1, 2, 3 is not running, the check is not passed. \n3 If the switch IP address cannot be pinged in step 10, the GE links are blocked. Therefore, the check is not passed.
tlv_hardware_pcieLinkStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again. \n1 Check the status of the PCIe link1 and PCIe link 2 displayed in step 6. If the status is not running, an error occurs on the link between the PCIe interface module and the switch.\n2 Check the two nodes displayed in step 5 who have the same engine ID, and then check the related PCIe link 0 status displayed in step 6. If the status is not running, the PCIe mirror is faulty. \n3 If the switch IP address displayed in step 10 cannot be pinged, the GE links are blocked. \n4 For details about how to resolve these issues, see the case. \n5 If you have any questions, please contact technical support engineers for further handling.\n\nNote: Run the exit command to exit the minisystem mode. Otherwise, a residual process may be left.
tlv_hardware_pcieLinkStatus.helphref = case{/helpCase/en/topic/check_PCIeLink.html}

cli_hardware_diskHealthDegree.name = Disk health mark
cli_hardware_diskHealthDegree.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show disk health command.
cli_hardware_diskHealthDegree.criterion = If Health Mark ranges from 0 to 60, it is abnormal. If it ranges from 61 to 100, it is normal. If it is 255 or --, it is normal.
cli_hardware_diskHealthDegree.suggestion = Consequence: If this check item is not passed, an upgrade may time out. Rectify the fault, and check again.\n1 Refer to the case to replace a disk whose Health Mark is smaller than or equals to 60.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_diskHealthDegree.helphref = case{/helpCase/en/topic/check_DiskHealthDegree.html}

cli_hardware_pciePortStatus.name = PCIe port status
cli_hardware_pciePortStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show port general physical_type=PCIE command.
cli_hardware_pciePortStatus.criterion = 1 If the number of controller enclosure is 1, it is normal that you do not find PCIe ports.\n2 If Health Status is Normal, PCIe ports are normal. \n3 Otherwise, they are abnormal.
cli_hardware_pciePortStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal PCIe port.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_pciePortStatus.helphref = case{/helpCase/en/topic/check_PCIePortStatus.html}

cli_hardware_diskStatus.name = Disk status
cli_hardware_diskStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show disk general or show disk general |filterRow column=Health\\sStatus predict=not predict2=equal_to value=Normal logicOp=or column=Running\\sStatus predict=not predict2=equal_to value=Online command.
cli_hardware_diskStatus.criterion = If Health Status is Normal and Running Status is Online, the disk is normal. Otherwise, it is abnormal.
cli_hardware_diskStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with the disk whose status is abnormal.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_diskStatus.helphref = case{/helpCase/en/topic/check_DiskStatus.html}

cli_hardware_fibreModule.name = Optical module status
cli_hardware_fibreModule.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show port fibre_module|filterColumn include columnList=PortID,Health\sStatus command.
cli_hardware_fibreModule.criterion = 1 It is normal if there is no optical module.\n2 If Health Status is Normal, the optical module is normal. \n3 Otherwise, it is abnormal.
cli_hardware_fibreModule.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Refer to the case to handle with the abnormal optical module. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_fibreModule.helphref = case{/helpCase/en/topic/check_FibreModule.html}

cli_hardware_fcPort.name = Fibre channel port
cli_hardware_fcPort.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show port general physical_type=FC command.
cli_hardware_fcPort.criterion = 1 It is normal if there is no fibre channel port.\n2 The Health Status of fibre channel port must be Normal, Otherwise, it is abnormal.\n3 Running status is Link Down, it is normal. When it is Link Up, the Working Rate must be 2000Mbps, 4000Mbps, 8000Mbps or 16000Mbps.\n4 Otherwise, it is abnormal.
cli_hardware_fcPort.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal fibre channel port. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_fcPort.helphref = case{/helpCase/en/topic/check_FCPort.html}

cli_hardware_sasPort.name = SAS port
cli_hardware_sasPort.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show port general physical_type=SAS command.
cli_hardware_sasPort.criterion = 1 Health Status of all ports must be Normal, Otherwise, it is abnormal. \n2 Running status is Link Down, it is normal. When it is Link Up, the port A and B must have the same link up number.\n3 Otherwise, it is abnormal.
cli_hardware_sasPort.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal SAS port. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_sasPort.helphref = case{/helpCase/en/topic/check_SASPort.html}

cli_hardware_iscsiPort.name = iSCSI port
cli_hardware_iscsiPort.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show port general physical_type=ETH logic_type=Host_Port command.
cli_hardware_iscsiPort.criterion = 1 If the iSCSI port does not exist, it is normal.\n2 Health Status of Host Port in ETH Port must be Normal, Otherwise, it is abnormal. \n3 Running status is link down, it is normal. When it is link up, the Working Rate must be 10 Mbit/s, 100 Mbit/s, 1,000 Mbit/s or 10,000 Mbit/s. \n4 Otherwise, they are abnormal.
cli_hardware_iscsiPort.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal iSCSI port. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_iscsiPort.helphref = case{/helpCase/en/topic/check_iSCSIPort.html}

tlv_hardware_intfCardFaultStatus.name = Checking interface module faults
tlv_hardware_intfCardFaultStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show alarm |filterRow column=ID predict=equal_to value=0xF0D10006 command to check whether an alarm exists.
tlv_hardware_intfCardFaultStatus.criterion = If an alarm corresponding to the specified ID exists on the device, interface module faults occur. Therefore, the check is not passed.
tlv_hardware_intfCardFaultStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 If the interface module is faulty, replace the faulty one. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
tlv_hardware_intfCardFaultStatus.helphref = case{/helpCase/en/topic/check_InterfaceModule.html}

cli_hardware_pcieSwitchStatus.name = PCIe switch status
cli_hardware_pcieSwitchStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show enclosure command.
cli_hardware_pcieSwitchStatus.criterion = 1 If Logic Type is not Data Switch, the enclosure is not a switch enclosure. You do not need to check it.\n2 If the number of controller enclosure is 1, it is normal that you do not find PCIe ports.\n3 If Health Status is Normal and Running Status is Online, the PCIe switch is normal. \n4 Otherwise, it is abnormal.
cli_hardware_pcieSwitchStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Log in to DeviceManager to check whether there are alarms about PCIe switches. If there are, recover the alarms according to the alarm handling suggestions. Replace switches if necessary by referring to the case.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_hardware_pcieSwitchStatus.helphref = case{/helpCase/en/topic/check_PCIeSwitchStatus.html}

tlv_hardware_ctrlFaultStatus.name = Checking controller faults
tlv_hardware_ctrlFaultStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show alarm |filterRow column=ID predict=equal_to value=0xF0CF0003 command to check whether an alarm exists.
tlv_hardware_ctrlFaultStatus.criterion = If an alarm corresponding to the specified ID exists on the device, controller faults occur. Therefore, the check is not passed.
tlv_hardware_ctrlFaultStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 If the controller is faulty, replace the faulty one. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
tlv_hardware_ctrlFaultStatus.helphref = case{/helpCase/en/topic/check_ControllerFaulty.html}

tlv_hardware_enclosureLinkStatus.name = Checking the single-link disk enclosure
tlv_hardware_enclosureLinkStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show alarm |filterRow column=ID predict=equal_to value=0xF00CE002A command to check whether an alarm exists.
tlv_hardware_enclosureLinkStatus.criterion = If an alarm corresponding to the specified ID exists on the device, the single-link disk enclosure exists. Therefore, the check is not passed.
tlv_hardware_enclosureLinkStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 If the single-link disk enclosure exists, resolve this issue. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
tlv_hardware_enclosureLinkStatus.helphref = case{/helpCase/en/topic/check_diskexclosuresinglelink.html}

tlv_hardware_cascadedBoardFaultStatus.name = Checking expansion module faults
tlv_hardware_cascadedBoardFaultStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show alarm |filterRow column=ID predict=equal_to value=0xF0050003 command to check whether an alarm exists.
tlv_hardware_cascadedBoardFaultStatus.criterion = If an alarm corresponding to the specified ID exists on the device, expansion module faults exist. Therefore, the check is not passed.
tlv_hardware_cascadedBoardFaultStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 If the expansion module is faulty, replace the faulty one. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
tlv_hardware_cascadedBoardFaultStatus.helphref = case{/helpCase/en/topic/check_ExpansionModule.html}

DiskStatus = Disk Status
tlv_disk_diskUsage.name = Checking disk usage
tlv_disk_diskUsage.method = Step 1 Log in to the device as user admin. \nStep 2 Run the change performance statistic_enabled enabled=yes command. \nStep 3 Run the show disk general to check the disk ID. \nStep 4 Run the show performance disk disk_id=[disk ID] command, enter 1 to check the Usage Ratio, and enter q to exit.
tlv_disk_diskUsage.criterion = Check the disk usage within 60 seconds. If the disk usage exceeds 80%, the check is not passed.\n
tlv_disk_diskUsage.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again. \n1 If the disk usage is too high, reduce the service pressure, and check again five minutes later. \n2 If you have any questions, contact technical support engineers.

tlv_disk_slowDisk.name = Checking whether slow disks exist
tlv_disk_slowDisk.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show alarm |filterRow column=ID predict=equal_to value=0xF00A000D command to check whether an alarm exists.
tlv_disk_slowDisk.criterion = If an alarm corresponding to the specified ID exists on the device, the system contains slow disks. Therefore, the check is not passed.
tlv_disk_slowDisk.suggestion = Consequence: If this check item is not passed, an upgrade may time out. Rectify the fault, and check again.\n1 If a slow disk exists, resolve this issue. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
tlv_disk_slowDisk.helphref = case{/helpCase/en/topic/check_slowdisk.html}

tlv_disk_linkStatus.name = Checking single-link disks
tlv_disk_linkStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show alarm |filterRow column=ID predict=equal_to value=0xF00A000C command to check whether an alarm exists.
tlv_disk_linkStatus.criterion = If an alarm corresponding to the specified ID exists on the device, a single link failure occurs. Therefore, the check is not passed.
tlv_disk_linkStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 If the disk single link exists, resolve this issue. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
tlv_disk_linkStatus.helphref = case{/helpCase/en/topic/check_disksinglelink.html}

tlv_disk_isDiskInDiagnose.name = Checking whether disks is being diagnosed online
tlv_disk_isDiskInDiagnose.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show event |filterRow column=ID predict=equal_to value=0x100F000A004A command to check events indicating that the online disk diagnosis starts.\nStep 3 Run the show event |filterRow column=ID predict=equal_to value=0x100F000A004C command to check events indicating that the online disk diagnosis ends.
tlv_disk_isDiskInDiagnose.criterion = If the number of events in step 3 is less than two times of that in step 2, the disks are diagnosed online. Therefore, the check is not passed.
tlv_disk_isDiskInDiagnose.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 If the disk is being diagnosed online, check whether the online diagnosis event is cleared five minutes later.\n2 If you have any questions, please contact technical support engineers for further handling.

tlv_disk_domainStatus.name = Checking the disk domain status
tlv_disk_domainStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show disk_domain general command to check the disk domain.
tlv_disk_domainStatus.criterion = 1 If the disk domain does not exist, the check is passed.\n2 If the Health Status is Normal, and the Running Status is Online, the check is passed.\n3 Otherwise, the check is not passed.
tlv_disk_domainStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted, and an upgrade failure may occur. Rectify the fault, and check again.\n1 If the disk domain status is abnormal, restore the disk domain. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
tlv_disk_domainStatus.helphref = case{/helpCase/en/topic/check_diskdomainstatus.html}

ServiceStatus = Service Status
cli_service_remoteReplicationStatus.name = Remote replication status
cli_service_remoteReplicationStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show remote_replication general command.
cli_service_remoteReplicationStatus.criterion = 1 If the remote replication does not exist, it is normal.\n2 If Health Status is Normal, the remote replication status is normal.\n3 Otherwise, it is abnormal.
cli_service_remoteReplicationStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal remote replication.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_service_remoteReplicationStatus.helphref = case{/helpCase/en/topic/check_RemoteReplicationStatus.html}

cli_service_replicationLinkStatus.name = Replication link status
cli_service_replicationLinkStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show remote_device link command.
cli_service_replicationLinkStatus.criterion = 1 If the replication link does not exist, it is normal.\n2 If Health Status is Normal, the replication link status is normal. \n3 Otherwise, it is abnormal.
cli_service_replicationLinkStatus.suggestion = Consequence: If this check item is not passed, the replication service before the upgrade cannot be stopped. Therefore, no upgrade operation can be performed. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal replication link.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_service_replicationLinkStatus.helphref = case{/helpCase/en/topic/check_ReplicationLinkStatus.html}

cli_service_virtualSnapshotHealthStatus.name = Snapshot health status
cli_service_virtualSnapshotHealthStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show snapshot general command.
cli_service_virtualSnapshotHealthStatus.criterion = 1 If the snapshot does not exist, it is normal.\n2 If Health Status is Normal, the snapshot is normal. \n3 Otherwise, it is abnormal.
cli_service_virtualSnapshotHealthStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal snapshot.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_service_virtualSnapshotHealthStatus.helphref = case{/helpCase/en/topic/check_VirtualSnapshotHealthStatus.html}

cli_service_lunCopyHealthStatus.name = LUN copy health status
cli_service_lunCopyHealthStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show lun_copy general command.
cli_service_lunCopyHealthStatus.criterion = 1 If the LUN copy does not exist, it is normal.\n2 If Health Status is Normal, the LUN copy health is normal.\n3 Otherwise, it is abnormal.
cli_service_lunCopyHealthStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal LUN copy.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_service_lunCopyHealthStatus.helphref = case{/helpCase/en/topic/check_LUNCopyHealthStatus.html}

cli_service_cloneHealthStatus.name = Clone health status
cli_service_cloneHealthStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show clone general command.
cli_service_cloneHealthStatus.criterion = 1 If the clone does not exist, it is normal.\n2 If Health Status is Normal, the clone health is normal.\n3 Otherwise, it is abnormal.
cli_service_cloneHealthStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal clone.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_service_cloneHealthStatus.helphref = case{/helpCase/en/topic/check_CloneHealthStatus.html}

cli_service_consistencyGroupStatus.name = Consistency group status
cli_service_consistencyGroupStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show consistency_group general command.
cli_service_consistencyGroupStatus.criterion = 1 If the consistency group does not exist, it is normal.\n2 If Health Status is Normal, the consistency group status is normal. \n3 Otherwise, they are abnormal.
cli_service_consistencyGroupStatus.suggestion = Consequence: If this check item is not passed, services may be interrupted. Rectify the fault, and check again.\n1 Refer to the case to handle with an abnormal consistency group.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_service_consistencyGroupStatus.helphref = case{/helpCase/en/topic/check_ConsistencyGroupStatus.html}

cli_software_hotPatch.name = Checking hot patches
cli_software_hotPatch.method = Step 1 Log in to the device as user admin.\nStep 2 Run the show upgrade package command to view the hot patch version (HotPatch Version).
cli_software_hotPatch.criterion = 1 The current system software version is V100R001C00. If the hot patch V100R001C00SPH002 or later has been installed, the check is passed. Otherwise, the check is not passed.\n2 The current system software version is V100R001C00SPC100. If the hot patch V100R001C00SPH101 or later has been installed, the check is passed. Otherwise, the check is not passed.\n3 If the current system software version is others, the check is passed.
cli_software_hotPatch.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 Install the related hot patch. For details, see the case.\n2 If you have any questions, please contact technical support engineers for further handling.
cli_software_hotPatch.helphref = case{/helpCase/en/topic/check_hotpatch.html}

cli_service_ioStatus.name = Checking I/O status
cli_service_ioStatus.method = Step 1 Log in to the device as user admin.\nStep 2 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 3 Run the debug command to go to the diagnose mode.\nStep 4 Run the writehole showlist command to query the I/O status.\nStep 5 Log in to the other controller, and repeat steps 2 to 4.
cli_service_ioStatus.criterion = 1 If the writehole wait io num field exists, and its value is not 0, the check is not passed.\n2 If logging in to the other controller fails, the check result is Warning.\n3 Otherwise, the check is passed.
cli_service_ioStatus.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 If the check is not passed, resolve this issue. For details, see the case.\n2 If the alarm "Failed to connect to the controller" is displayed, redeploy the network correctly. For details, see Enterprise Huawei Storage Product Networking Assistant. \n3 If you have any questions, please contact technical support engineers for further handling.
cli_service_ioStatus.helphref = case{/helpCase/en/topic/IO_status_check.html}&&Enterprise Huawei Storage Product Networking Assistant{http://support.huawei.com/onlinetool/datums/nettool/index.en.jsp}

cli_service_cachePartitionFaultPage.name = Checking Fault Pages in a Cache Partition
cli_service_cachePartitionFaultPage.method = Step 1 Log in to the device as user admin.\nStep 2 Run the change user_mode current_mode user_mode=developer command to go to the developer mode.\nStep 3 Run the debug command to go to the diagnose mode.\nStep 4 Run the quota show pttinfo all command to view the value of the blockedCnt field.\nStep 5 Log in to the other controller, and repeat steps 2 to 4.
cli_service_cachePartitionFaultPage.criterion = 1 If any of the values in the blockedCnt field is not 0, the check is not passed. \n2 If logging in to the other controller fails, the check result is Warning.\n3 Otherwise, the check is passed.
cli_service_cachePartitionFaultPage.suggestion = Consequence: If this check item is not passed, an upgrade failure may occur. Rectify the fault, and check again.\n1 If the alarm "Failed to connect to the controller" is displayed, redeploy the network correctly. For details, see Enterprise Huawei Storage Product Networking Assistant. \n2 If you have any questions, please contact technical support engineers for further handling.
cli_service_cachePartitionFaultPage.helphref = Enterprise Huawei Storage Product Networking Assistant{http://support.huawei.com/onlinetool/datums/nettool/index.en.jsp}

cli_hardware_port_fcoe.name = Checking FCoE Ports
cli_hardware_port_fcoe.method = Step1 Log in to the device as user admin.\nStep2 Run the show system general command to check the device model and current version.\nStep3 Run the show port general physical_type=FCoE command to check FCoE port information.
cli_hardware_port_fcoe.criterion = 1. This check item is required only for versions that meet the following conditions. Otherwise, the check result is Passed.\n1.1 The device model is 18000 V1 series, and the target version is earlier than V1R1C30SPC300.\n1.2 The device model is T series, and the target version is earlier than V200R002C30SPC300.\n1.3 The device model is V3 series, and the target version is earlier than V300R002C10SPC200.\n2. If no port information is obtained in step 2 or all the values of Running Status in the command output are Link Down, the check result is Passed. In other cases, the check result is Not passed.
cli_hardware_port_fcoe.suggestion = Impact: If the check result is Not passed, services may be interrupted during the upgrade in the FCoE networking scenario. \nContact technical support engineers.