IBM 3000 6.0.2, Руководство по обслуживанию

Страница: 60 / 88

code IBM Spectrum Scale 5.0.4.3 must be verified by using the gssinstallcheck or
essinstallcheck command).
• The system must be healthy before the ESS 3000 storage MES upgrade.
• The existing ESS 3000 must be a properly installed 12 NVMe system with 12 NVMe drives correctly
located in slots 1 - 6 and 13 - 18.
• If the canister servers are allocated as quorum servers, understand the implications of losing a quorum
server on one canister server at a time during this operation. If you do not want to lose the quorum,
move the quorum to different servers during this procedure.
• It is recommended to wear an ESD wrist band when you work on the hardware, for example, inserting
NVMe drives.
MES upgrade considerations
GPFS uses preferentially the new network shared disks (NSDs) to store data of a new file system. GPFS
has four new NSDs that are the same as the four original NSDs and the workload on each server is the
same as it was before. The new file system data goes to the four new NSDs, like before the resizing, the
original file system data goes to the four original NSDs. Consider the necessity of restriping and the
current demands on the system. New data that is added to the file system is correctly striped. Restriping a
large file system requires many insert operations and delete operations, which might affect the system
performance. Restripe a large file system, when the system demand is low.
Concurrent MES upgrade steps
1. Ensure that the technical delivery assessment (TDA) process is complete before you start the MES
upgrade.
2. Ensure that the system is at the ESS 3000 6.0.0.2 or later level for the storage MES.
3. If losing quorum on each canister server during MES upgrade causes an issue with the customer
configuration, move the quorum to other supported nodes in the system.
4. Ensure that the 12 new NVMe drive FRUs are of the same capacity as the original 12 NVMe drives.
5. Insert the 12 new NVMe drive FRUs into slots 7 - 12 and 19 - 24.
Do not move the original 12 NVMe drives to different slots!
6. Verify the new 24 NVMe disk topology on both canisters by issuing the following command:
# mmvdisk server list --disk-topology --node-class this ESS 3000 node class
Example
[ess3ka ~]# mmvdisk server list --disk-topology --node-class ess_x86_64_mmvdisk_5_mySN
node needs matching
number server attention metric disk topology
------ -------------------------------- --------- -------- -------------
21 ess3ka-ib.example.net no 100/100 ESS3K SN0 24 NVMe
22 ess3kb-ib.example.net no 100/100 ESS3K SN0 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 latest firmware level, issue the following command
from one of the canisters:
# mmlsfirmware --type drive
Example
enclosure firmware available
type product id serial number level firmware location
---- ---------- ------------- -------- -------- --------
drive 3.84TB NVMe G3 Tier-1 Flash mySN SN1ISN1I SN1ISN1I ess3ka-ib Rack myrack U37-38, Enclosure 5141-AF8-mySN Drive 10
48 IBM Elastic Storage System 3000: Service Guide