# mmvdisk nodeclass list
Verify the new 24 NVMe disk topology on both canisters by issuing the following command:
# mmvdisk server list --disk-topology --node-class <node class name>
Example
The following example is a case of a missing drive.
# mmvdisk server list --disk-topology --node-class ess3200_x86_64_mmvdisk_78E400K
node needs matching
number server attention metric disk topology
------ -------------------------------- --------- -------- -------------
6 ess3200rw3a-hs.gpfs.ess yes 95/100 ESS 3200 FN1 24 NVMe
7 ess3200rw3b-hs.gpfs.ess yes 95/100 ESS 3200 FN1 24 NVMe
To identify what needs attention, use the following commands:
mmvdisk server list -N ess3200rw3a-hs.gpfs.ess --disk-topology -L
mmvdisk server list -N ess3200rw3b-hs.gpfs.ess --disk-topology -L
Example
# mmvdisk server list -N ess3200rw3a-hs.gpfs.ess --disk-topology -L
GNR server: name ess3200rw3a-hs.gpfs.ess arch x86_64 model ESS3200-5141-FN1 serial 78E400KA
GNR enclosures found: 78E400K
Enclosure 78E400K (IBM-ESS 5141-FN1, number 1):
Enclosure 78E400K expander sg0[E113]
Enclosure 78E400K expander sg0 23 disks diskset "00751"
Enclosure 78E400K sees 23 disks (23 SSDs, 0 HDDs)
GNR server disk topology: ESS 3200 FN1 24 NVMe (match: 95/100)
GNR configuration: 1 enclosure, 23 SSDs, 1 empty slot, 23 disks total, 0 NVRAM partitions
Location 78E400K-7 appears empty but should have an SSD
To rectify the error, reseat the drive in that slot and rerun the command:
# mmvdisk server list --disk-topology --node-class ess3200_x86_64_mmvdisk_78E400K
node needs matching
number server attention metric disk topology
------ -------------------------------- --------- -------- -------------
6 ess3200rw3a-hs.gpfs.ess no 100/100 ESS 3200 FN1 24 NVMe
7 ess3200rw3b-hs.gpfs.ess no 100/100 ESS 3200 FN1 24 NVMe
• Both canisters must show a 24 NVMe disk topology.
• If any errors such as a new disk is bad or does not show up are reported, the errors must be fixed
before proceeding.
7. To check whether all 24 NVMe drives have the current firmware version, issue the following
command from one of the canisters. For more information about the current firmware version, see
the Drives section in IBM Elastic Storage System documentation.
Note: For FCM drives, the minimum drive firmware level is 2.1.7 (2_1_7).
# mmlsfirmware --type <component type>
Example
# mmlsfirmware --type drive
enclosure firmware available
type product id serial number level firmware location
---- ---------- ------------- -------- -------- --------
drive a8241014065c 78E400K SN5ASN5A SN5ASN5A ess3200rw3a-hs Rack Bodhi-Rack-1520 U25-26,
Enclosure 5141-FN1-78E400K Drive 10
drive a8241014065c 78E400K SN5ASN5A SN5ASN5A ess3200rw3a-hs Rack Bodhi-Rack-1520 U25-26,
Enclosure 5141-FN1-78E400K Drive 11
drive a8241014065c 78E400K SN5ASN5A SN5ASN5A ess3200rw3a-hs Rack Bodhi-Rack-1520 U25-26,
Enclosure 5141-FN1-78E400K Drive 12
22 IBM Elastic Storage System 3200: Service Guide
Summary of Contents for Elastic Storage System 3200
Page 1: ...IBM Elastic Storage System 3200 6 1 3 Service Guide IBM SC27 9862 00 ...
Page 4: ...iv ...
Page 8: ...viii ...
Page 12: ...xii IBM Elastic Storage System 3200 Service Guide ...
Page 42: ...30 IBM Elastic Storage System 3200 Service Guide ...
Page 46: ...34 IBM Elastic Storage System 3200 Service Guide ...
Page 50: ...38 IBM Elastic Storage System 3200 Service Guide ...
Page 58: ...46 IBM Elastic Storage System 3200 Service Guide ...
Page 60: ...48 IBM Elastic Storage System 3200 Service Guide ...
Page 62: ...50 IBM Elastic Storage System 3200 Service Guide ...
Page 63: ......
Page 64: ...IBM Product Number 5765 DME 5765 DAE SC27 9862 00 ...