mmlsnvmestatus

The mmlsnvmestatus command is used to list the status of all the NVMe controllers or a specific NVMe controller.

Synopsis

mmlsnvmestatus {all | SerialNumber}
[-N {Node,[Node...] | NodeFile | NodeClass}]
[--not-ok][-Y]

Availability

Available on all IBM Storage Scale editions.

Description

Use the command to list the status of all the NVMe controllers or a specific NVMe controller of all the nodes that are specified, or the nodes of the node file or node class specified. By default, if no nodes are specified, the mmlsnvmestatus command finds the server nodes of all the configured Recovery Groups (RGs) and list the status of the NVMe controller of those nodes.

Use the mmlsnvmestatus command to perform the following functions on the specified node:
  • To find the status of all NVMe controller or a specific NVMe controller.
  • To display the status of only the NVMe controllers that are reporting an unusual condition.
  • To view the individual categorize and summary status of NVMe controller in colon separated form.

Parameters

all | SerialNumber
Specifies that the status of NVMe controller must be displayed. The option all specifies that the status of all NVMe controllers on the specified nodes must be displayed. SerialNumber indicates the serial number of the NVMe controller for which the status must be displayed.

-N {Node, [Node...]|NodeFile | NodeClass}
Specifies the list of nodes or nodes of node file or node class from which NVMe controller status must be displayed. By default, the NVMe controller status information from all the server nodes of the all Recovery Groups (RGs) configured is displayed.
--not-ok
Specifies to display the status of only those NVMe controllers that are reporting an unusual condition.
-Y

Specifies that the output needs to be displayed in colon separated form. The output displays the colon separated status of all the individual categories, including the summary status of the NVMe controllers.

If -Y is specified, all individual NVMe controller's status including the summary status is displayed as shown in the following example. 

[root@c145f02n01 bin]# mmlsnvmestatus all -Y
mmlsnvmestatus:vaultBackup:HEADER:version:reserved:reserved:node:NVMeCtrl:serialNumber:
spareSpace:availableSpare:usedSpare:
mmlsnvmestatus:tempSensor:HEADER:version:reserved:reserved:node:NVMeCtrl:serialNumber:
operationalTemp:cpuTemp:systemTemp:supercapTemp:
mmlsnvmestatus:backupFail:HEADER:version:reserved:reserved:node:NVMeCtrl:serialNumber:
vaultOperationFail:operationalMode:mediaErrors:
mmlsnvmestatus:ioMode:HEADER:version:reserved:reserved:node:NVMeCtrl:serialNumber:
readOnly:backupPowerLow:backupInProgress:noSpareBlocks:
mmlsnvmestatus:ioOperations:HEADER:version:reserved:reserved:node:NVMeCtrl:serialNumber:
dataRead:dataWritten:cmdsRead:cmdsWritten:
mmlsnvmestatus:deviceOpMode:HEADER:version:reserved:reserved:node:NVMeCtrl:serialNumber:
operationalMode:mediaErrors:
mmlsnvmestatus:summary:HEADER:version:reserved:reserved:node:NVMeCtrl:serialNumber:
status:needsService:permReadOnly:tempReadOnly:OptimalLinkState:OptimalLBAFormats
mmlsnvmestatus:backupFail:0:1:::c145f02n01:/dev/nvme0:040000185FD2:NO:NORMAL:0:
mmlsnvmestatus:backupFail:0:1:::c145f02n02:/dev/nvme0:04000017F900:NO:NORMAL:0:
mmlsnvmestatus:deviceOpMode:0:1:::c145f02n01:/dev/nvme0:040000185FD2:NORMAL:0:
mmlsnvmestatus:deviceOpMode:0:1:::c145f02n02:/dev/nvme0:04000017F900:NORMAL:0:
mmlsnvmestatus:ioMode:0:1:::c145f02n01:/dev/nvme0:040000185FD2:NO:NO:NO:NO:
mmlsnvmestatus:ioMode:0:1:::c145f02n02:/dev/nvme0:04000017F900:NO:NO:NO:NO:
mmlsnvmestatus:ioOperations:0:1:::c145f02n01:/dev/nvme0:040000185FD2:637330:89904863:4263413:3680839965:
mmlsnvmestatus:ioOperations:0:1:::c145f02n02:/dev/nvme0:04000017F900:634037:76631284:4164896:3499213369:
mmlsnvmestatus:summary:0:1:::c145f02n01:/dev/nvme0:040000185FD2:NORMAL:NO:NO:NO:YES:YES:
mmlsnvmestatus:summary:0:1:::c145f02n02:/dev/nvme0:04000017F900:NORMAL:NO:NO:NO:YES:YES:
mmlsnvmestatus:tempSensor:0:1:::c145f02n01:/dev/nvme0:040000185FD2:NORMAL:313:306:298:
mmlsnvmestatus:tempSensor:0:1:::c145f02n02:/dev/nvme0:04000017F900:NORMAL:313:307:301:
mmlsnvmestatus:vaultBackup:0:1:::c145f02n01:/dev/nvme0:040000185FD2:NORMAL:98:2:
mmlsnvmestatus:vaultBackup:0:1:::c145f02n02:/dev/nvme0:04000017F900:NORMAL:99:1:

If -Y option is not specified, then the mmlsnvmestatus command displays human readable summary status of the NVMe controllers as shown in the following example.

[root@c145f02n01 bin]# mmlsnvmestatus all
                                              Optimal     Optimal      needs
 node        NVMe device    serial number     Link State  LBS Formats  service
 ------      -----------    -------------     ----------  -----------  -------
 c145f02n01  /dev/nvme0     040000185FD2      YES         YES          NO
 c145f02n02  /dev/nvme0     04000017F900      YES         YES          NO
[root@c145f02n01 bin]#

Exit status

0
Successful completion.
nonzero
A failure has occurred.

Security

You must have root authority to run the mmlsnvmestatus command.

The node on which the command is issued must be able to run remote shell commands on any other node in the cluster without the use of a password and without producing any extraneous messages. For more information, see Requirements for administering IBM Storage Scale RAID.

Example

The following example shows the usage of mmlsnvmestatus command to view status of a NVMe controller whose serial number is specified.

[root@c202f06fs03a fab_tools]# mmlsnvmestatus  S43RNE0KC00152
                                                Optimal     Optimal      needs
 node          NVMe device    serial number     Link State  LBA Format   service
 ------        -----------    -------------     ----------  ----------   -------
 c202f06fs03a  /dev/nvme8     S43RNE0KC00152    YES         YES          NO
[root@c202f06fs03a fab_tools]#

See also

See also the following IBM Spectrum® Scale RAID: Administration topics.

Location

/usr/lpp/mmfs/bin