storage:svc_upgrade
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
storage:svc_upgrade [2021/02/06 12:51] manu created |
storage:svc_upgrade [2022/02/03 15:16] (current) manu |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Easier way to upgrade is using GUI to upgrade | Easier way to upgrade is using GUI to upgrade | ||
| - | Precheck: | + | ===== Precheck: ===== |
| * depending on hardware, check the required level available | * depending on hardware, check the required level available | ||
| + | <code>Ex: => google: Hardware Interoperability Matrix v7000 </code> | ||
| * check the upgrade steps, maybe you cannot update in one step from 8.1.7 to 8.3.1.3 ! | * check the upgrade steps, maybe you cannot update in one step from 8.1.7 to 8.3.1.3 ! | ||
| + | <code>Ex: => google: Concurrent Compatibility and Code Cross Reference for Spectrum Virtualize </code> | ||
| Download the test utility (required) and package upgrade | Download the test utility (required) and package upgrade | ||
| Start the upgrade in full automatic (best practice) | Start the upgrade in full automatic (best practice) | ||
| + | |||
| + | **Duration:** about 30 minutes per controler , depending on packages, and maybe also BIOS upgrades on SVC | ||
| During install, you have to check | During install, you have to check | ||
| Line 29: | Line 34: | ||
| </cli> | </cli> | ||
| - | On storage arrays | + | === On storage arrays === |
| <cli prompt='>'> | <cli prompt='>'> | ||
| IBM_Storwize:V7K01:admin>lsnodecanister | IBM_Storwize:V7K01:admin>lsnodecanister | ||
| Line 39: | Line 44: | ||
| </cli> | </cli> | ||
| - | Sur le cluster SVC | + | ===== On SVC cluster (Spectrum Virtualize) ===== |
| <cli prompt='>'> | <cli prompt='>'> | ||
| IBM_2145:SVC01:admin>lsnode | IBM_2145:SVC01:admin>lsnode | ||
| Line 52: | Line 58: | ||
| 13 SVC02_4B 500507680C00xxx online 3 io_grp3 no SV1 iqn.1986-03.com.ibm:2145.svc02_4b 78GLxxx 1 2 site2 | 13 SVC02_4B 500507680C00xxx online 3 io_grp3 no SV1 iqn.1986-03.com.ibm:2145.svc02_4b 78GLxxx 1 2 site2 | ||
| </cli> | </cli> | ||
| + | |||
| + | ===== check IP quorums ===== | ||
| On Hyperswap cluster : v7k... and on SVC, check quorums, specificaly IP (an update is maybe useful) | On Hyperswap cluster : v7k... and on SVC, check quorums, specificaly IP (an update is maybe useful) | ||
| - | All quorums must be **online** and one IP quorum **active** | + | All quorums must be **online** and one IP quorum **active** when upgrade is finished |
| <cli prompt='>'> | <cli prompt='>'> | ||
| IBM_Storwize:V7K01:admin>lsquorum | IBM_Storwize:V7K01:admin>lsquorum | ||
| Line 62: | Line 70: | ||
| 3 online yes device no quorum01.intra/10.10.10.10 | 3 online yes device no quorum01.intra/10.10.10.10 | ||
| </cli> | </cli> | ||
| + | |||
| + | When all nodes are updated, and the system is updated, the | ||
| + | <cli prompt='>'> | ||
| + | IBM_Storwize:V7K01:admin>lsupdate | ||
| + | status enclosures | ||
| + | event_sequence_number | ||
| + | progress 0 | ||
| + | estimated_completion_time 210206130607 | ||
| + | suggested_action wait | ||
| + | system_new_code_level | ||
| + | system_forced no | ||
| + | system_next_node_status none | ||
| + | system_next_node_time | ||
| + | system_next_node_id | ||
| + | system_next_node_name | ||
| + | system_next_pause_time | ||
| + | </cli> | ||
| + | |||
| + | New code is active on the system | ||
| + | <cli prompt='>'> | ||
| + | IBM_Storwize:V7K01:admin>lssystem | grep code | ||
| + | code_level 8.3.1.3 (build 150.25.2012041757000) | ||
| + | </cli> | ||
| + | |||
| + | On arrays, next step, the system 'll update firmaware on axpansions, there is no progress bar, just have to wait... | ||
| + | |||
| + | ===== Next step on arrays ===== | ||
| + | |||
| + | Check and maybe update drives firmwares | ||
| + | * download the packages for SAS and/or NVMe drives depending on your hardware | ||
| + | |||
| + | Then go into | ||
| + | Pools --> Internal Storage --> Actions --> Upgrade All | ||
| + | |||
| + | If you got a message: | ||
| + | CMMVC7241E System code update cannot start because a component firmware update is in progress. | ||
| + | | ||
| + | Then wait ... | ||
| + | |||
| + | When upgrade starts, follow the progress with (about 4 minutes per drive): | ||
| + | <cli prompt='>'> | ||
| + | IBM_Storwize:V7K01:admin>lsdriveupgradeprogress | ||
| + | id status estimated_completion_time | ||
| + | 12 not_scheduled | ||
| + | 13 not_scheduled | ||
| + | 14 not_scheduled | ||
| + | 15 not_scheduled | ||
| + | 16 not_scheduled | ||
| + | 17 not_scheduled | ||
| + | 18 not_scheduled | ||
| + | </cli> | ||
| + | |||
| + | ===== Quorum IP ===== | ||
| + | |||
| + | Create a service with downloaded file **ip_quorum.jar** from storage SVC or v7000, and open firewall port :**1260** | ||
| + | |||
| + | ==== On windows: ==== | ||
| + | |||
| + | <cli prompt='>'> | ||
| + | sc.exe create "IBM_IP_quorum" binPath= "F:\<javapath>\java -jar ip_quorum.jar" | ||
| + | </cli> | ||
| + | |||
| + | To delete service: | ||
| + | <cli prompt='>'> | ||
| + | sc.exe delete SERVICE NAME | ||
| + | </cli> | ||
| + | |||
| + | ==== On Linux: ==== | ||
| + | |||
| + | |||
storage/svc_upgrade.1612612316.txt.gz · Last modified: 2021/02/06 12:51 by manu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
