Scribd
Upload
168 views4 pages

IBM V7K Upgrade Manual V0.1

1) The upgrade process for an IBM V7K storage system requires verifying prerequisites such as component compatibility and multipathing redundancy. It can take over an hour during which performance will be lower. 2) Backups of the configuration and logs must be taken before rebooting the nodes to apply the upgrade. The upgrade packages, containing software, utilities, and microcode, must be obtained from fix central. 3) Once prerequisites are verified and backups completed, the automatic upgrade procedure can be launched from the management GUI to upgrade both nodes in a coordinated process with no intervention required.

Uploaded by

imenhidouri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
168 views4 pages

IBM V7K Upgrade Manual V0.1

1) The upgrade process for an IBM V7K storage system requires verifying prerequisites such as component compatibility and multipathing redundancy. It can take over an hour during which performance will be lower. 2) Backups of the configuration and logs must be taken before rebooting the nodes to apply the upgrade. The upgrade packages, containing software, utilities, and microcode, must be obtained from fix central. 3) Once prerequisites are verified and backups completed, the automatic upgrade procedure can be launched from the management GUI to upgrade both nodes in a coordinated process with no intervention required.

Uploaded by

imenhidouri
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Upgrade Storage system procedure

Platform : IBM V7K

I-Prerequisites

1-Change Management

The amount of time for the upgrade can vary depending on the amount of preparation
work required and the size of the environment. Generally allow slightly over 1 hour for an
upgrade. During this time machine performance will be lower as both node canisters will
be restarted one by one to apply new code.

2-SSIC and compatibility matrix

The compatibility of the platform components (San, Storage, Hosts, Network...) must be
verified before deciding to upgrade the system. These checks could be done through the
tool IBM SSIC and Code reference compatibility
http://www-03.ibm.com/systems/support/storage/ssic/interoperability.wss

Code cross reference compatibility is available on below link:


http://www-01.ibm.com/support/docview.wss?uid=ssg1S1003705£

3- Upgrade method

Customer must decide whether the upgrade will be done automatically or manually (During
an automatic upgrade procedure, the clustered system upgrades each of the nodes
systematically. The automatic method is the preferred procedure for upgrading software on
nodes. However, you can also upgrade each node manually. )

4-Fixing Errors

Ensure that you have no unfixed errors in the log and that the system date and time are
correctly set. Start the fix procedures, and ensure that you fix any outstanding errors
before you attempt to concurrently upgrade the code.

5-Multipathing and dependencies checks

Ensure that multipathing drivers in the environment are fully redundant.


Multipathing software must be active and ready to takeover the paths to the storage, when
a node storage is unavailable during the firmware upgrade.
There must not be volumes dependant from one node (#lsdependentvdisks command)

You could check on Storage system Settings> network > FC To check connectivity of each
host to nodes with details
SDDPCM is a loadable path control module designed to support the multipath configuration
environment in the IBM TotalStorage Enterprise Storage Server, the IBM System Storage SAN
Volume Controller, the IBM Storwize family, the IBM Flash System V840 and V9000, the IBM
TotalStorage DS family and IBM BladeCenter S SAS Raid Controller Module (RSSM).

SDDPCM manages the paths to provide:


- High availability and load balancing of storage I/O
- Automatic path-failover protection
- Concurrent download of licensed internal code
- Prevention of a single-point-failure caused by host bus adapter, fibre channel cable, Ethernet
cable, or host-interface adapter on supported storage

a- AIX Hosts

Important SDDPCM commands and their functions:


• pcmpath: Display and manage SDDPCM devices.
• pcmpath query adapter: show adapter configuration
• pcmpath query version: show the version of the SDDPCM
• pcmpath query device: show the SDDPCM devices

b- Linux

Most used SDD commands for a linux Host system :

cfgvpath Configures SDD vpath devices.


cfgvpath queryDisplays all SCSI disk devices.
Lsvpcfg Displays the current devices that are configured and theircorresponding paths.
Rmvpath Removes one or all SDD vpath devices.
Addpaths Adds any new paths to an existing SDD vpath device.
This command is only supported for Linux 2.4 kernels.
For Linux 2.6 kernels, the functionality of theaddpathscommandhas been added to thecfgvpath
command. If you need to addpaths to an existing SDD vpath device with a Linux 2.6 kernel,
runthecfgvpath command.
sdd startLoads the SDD driver and automatically configures disk devicesfor multipath access.
sdd stopUnloads the SDD driver (requires that no SDD vpath devicescurrently be in use).
sdd restartUnloads the SDD driver (requires that no SDD vpath devicescurrently be in use), and then
loads the SDD driver andautomatically configures disk devices for multipath access

c- Windows

Open the DOS prompt window

On a Windows Server 2008: Click Start →Program →Subsystem DeviceDriver DSM


→Subsystem Device Driver DSM.

On a Windows Server 2012: Click Start Screen →Apps →Subsystem DeviceDriver DSM.

On a Windows Server 2016: Click Start →SubsystemDevice Driver DSM →Subsystem


Device Driver DSM.
On a Windows Server2012 or Windows Server 2016 Server Core CLI:
Go to%PROGRAMFILES%\IBM\SDDDSM.3.Enter datapath query adapter and press
Enter.
The output includes information about all the installed adapters. In the following example,
the output shows that one HBA is installed

6-backup Config

Right before code upgrade please logon to Machine CLI SSH to Cluster IP and issue
following commands:
svctask cleardumps -prefix /dumps
svctask cleardumps -prefix /home/admin/upgrade
svcconfig backup
logon to service assistant GUI (http://service_ip/service or http://cluster_ip/service ) and
go to collect logs section of config node (on home tab select the node which has
configuration node=yes) go to collect logs, show available files and offload all files that
have config in name(config.xml, config back etc.).

7-Backup Logs

Please also generate and offload SNAP option 3 (standard logs plus most recent
statesaves).
When all above actions completed please login to service assistant GUI of config node:
and reboot node (on home tab make sure node with config=yes is selected and from
dropdown menu select reboot and click go)
when node will come back to cluster please perform same reboot action for second node

II- Steps
1- Obtaining The Storwize V7000 Software packages

You can check to see if a newer release of software is available by using the management
GUI. Select Settings > General > Upgrade Software. Click Check for updates.

You can download it from fix central : https://www-945.ibm.com/support/fixcentral

The Upgrade Packages comprises the Software Package, The upgradetestUtility and the
Drives Microcode. The UpgradetestUtility will check for any possible errors or warnings,
that could impact the Upgrade.

It is recommended to upgrade Drives Firmware before Upgrading Storage System.

2- Upgrading the Software automatically

This automatic procedure provides a unified mechanism to upgrade the entire system in a
coordinated process with no user intervention.

Below is GUI sequence to launch upgrade:


Settings > General > Upgrade Software > Launch Upgrade Wizard
III-Tests

You could check on hosts (Volumes access, paths...) and on Storage system (event logs) if
the upgrade has finished successfully

You might also like