Category Archives: V7000(Storwize)

IBM v7000 Disk Firmware update cause any performance issue or effect anything?

to whom want to upgrade Storwize v7000 disk firmware (microcode)¬† ūüôā

to whom wonder any down time or performance issue should be expected or not¬† ūüôā

aaaa shortly yes ! you will see interesting chart like below ; IOPS values what you see in chart is measured after disk firmware update over

Screen Shot 2013-05-27 at 11.24.29 PM

For how to upgrade please read https://www.ibm.com/developerworks/community/blogs/anthonyv/entry/updating_storwize_v7000_drive_code1?lang=en

You can find out putty,pscp,puttygen from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

For not to me or quickly memorize or shortly such article

pscp -i you.generated.file.with.puttygen.for.auth.ppk IBM2076_INSTALL_upgradetest_9.15 username.which.has.sshkey@9.191.0.78:/home/username/upgrade
Not: This folder at the upgrade time cleared by system because of space need and puttygen will help you to create a file for auth and you have to assign this key with a username what you create on v7000

After upload upgrade test file execute such command step by step
svcservicetask applysoftware -file IBM2076_INSTALL_upgradetest_9.15
svcupgradetest -f 
Not: This command show the count of drive need to be upgrade , you can also add -d parameter to see everything  as a list 

pscp -i you.generated.file.with.puttygen.for.auth.ppk IBM2076_DRIVE_You.Downloaded.Code username.which.has.sshkey@9.191.0.78:/home/username/upgrade

To list the disk drives
svcinfo lsdrive -nohdr |while read did error use;do svcinfo lsdrive $did |while read id value;do if [[ $id == "firmware_level" ]];then echo $did" "$value;fi;done;done

To Upgrade single drive
svctask applydrivesoftware -file IBM2076_DRIVE_You.Downloaded.Code -type firmware -drive 23

To Upgrade some of disks

for did in 100 101;do echo "Updating drive "$did;svctask applydrivesoftware -file IBM2076_DRIVE_20110928 -type firmware -drive $did;sleep 10s;done

VM

IBM Tivoli Storage Productivity Center and Storwize v7000 PerfomanceMonitoring

Tivoli version 5.1.0.0
V7000 version 6.3.0.3 also i tried 6.4.1.3 too

First login management GUI of v7000 and left site “Access->Users” section (Lock Image) click New User ;

set what name you want, myself created admin
set auth mode local
set usergroup how you want but i selected SecurityAdmin
do not set pass we have set public key , to create a key download puttygen open it click Generate , move your mouse on blank area or take a coffee end of the generation pls save the public key and private key then use the public key at the generation of user.

Screen Shot 2013-02-15 at 9.08.01 PM

This is the user creation screen , here you have to provider generated SSH Public Key

Screen Shot 2013-02-15 at 9.06.37 PM

Now, go to Tivoli GUI

Step 1

Under Administrative Services –> Data Sources –> Storage Subsystems click Add
Device type should be IBM SAN Volume Controller / IBM Storwize V7000
Software Version 5+
IP Address , set you v7000 ip
Select Key, it should be Upload New Key
Administrator User Name , i used superuser
Administrator Password, give the superuser pass
User Name, i used new created user on top
Private SSH Key, i used puttygen generated private key, ppk extension
Click Add and wait little
You will see additional table become and show the storage, click next below

Discovery Process will be start, it should be success and then click next again

A new page will be appear which storage already selected , go next

Next page about data collection, you have a choose for custom or ready to use , choose Subsystem Advanced Group

Summary, next

Finish and click View job History and wait running job over success

Go to IBM Tivoli Storage Productivity Center –> Monitoring –> Probes –> TPCUser.Subsystem Advanced Probe you will see that newly added storage subsystem is under ¬†Current selections, if you want you can remove or add storage subsystem to under another monitoring probe.

Also you can see the schedule under When to Run tab and can create an alerts too  !

Screen Shot 2013-02-15 at 9.09.07 PM Screen Shot 2013-02-15 at 9.15.44 PM Screen Shot 2013-02-15 at 9.16.31 PM Screen Shot 2013-02-15 at 9.16.55 PM Screen Shot 2013-02-15 at 9.17.04 PM Screen Shot 2013-02-15 at 9.19.29 PM

Step 2

Lets read to collect performance info from newly added storage subsystem

From Disk Manager tree go to Monitoring and open Subsystem Performance Monitors, right click on and select Create Subsystem Performance Monitors,
choose storage and move to right site, click Sampling and Scheduling do not change something only change the duration “Continue indefinitely”
save the config, set a performance monitor name, confirm creation, wait for job over and give some multiple 5 mins to get many data

Thats it !

Screen Shot 2013-02-15 at 9.38.36 PM Screen Shot 2013-02-15 at 9.39.34 PM Screen Shot 2013-02-15 at 9.40.34 PM Screen Shot 2013-02-15 at 9.40.57 PM Screen Shot 2013-02-15 at 9.49.44 PM Screen Shot 2013-02-15 at 9.49.54 PM

Match v7000 presented volume as a mdisk on SVC

Its really hard to play with storage when production data on it

To whom need to be remove , unmap volumes which presented to SVC via v7000 need to be know that UID numbers of mdisks on SVC and v7000 is same but with little modification.

These are volume UIDs on v7000

These are mdisk

You can see that SVC add additional 00000 behind the value which come from v7000 UID

You can easily and safely unmap if you need from v7000 to take the space back

VM

Put Storwize(v7000) behind the SVC and do not confuse what you see

When you configure your SAN configuration and zone the SVC and v7000 together  you will see that two v7000 controllers will be appear, after i check on the internet is it true and maybe before i have to check this link first

https://www.ibm.com/developerworks/mydeveloperworks/blogs/anthonyv/entry/virtualizing_a_storwize_v7000_with_an_ibm_svc?lang=en

i have extra words, all presented volumes on v7000 without what preferred owner set  appear under configuration v7000 node controller on SVC, pls see below

Don’t worry that load balance is always working , check SAN traffic to find out ….

Also before configure mdisks and mdiskgroups pls read best practice paper before implement but shortcut for your all

On v7000 site :

Create 1 mdiskgroup

svctask mkmdiskgrp -ext 256 -name name_of_mdiskgroup -warning 80%

Create 1 array and assign it to such mdiskgroup

svctask mkarray -drive 12:36:34:19:20:18:16:15 -level raid5 -sparegoal 1 name_of_mdiskgroup

Numbers are disk you can list it under v7000

On SVC site:

You will see  mdisks under v7000 controller, create mdiskgroup from this mdisks and start to create volumes ..

 

My full commands ;

 

IBM_2076:EMPIRE2:superuser>svctask mkmdiskgrp -name mdiskgroup1 -ext 32 -warning 80%

MDisk Group, id [0], successfully created

IBM_2076:EMPIRE2:superuser>svctask mkmdiskgrp -name mdiskgroup2 -ext 32 -warning 80%

MDisk Group, id [1], successfully created

IBM_2076:EMPIRE2:superuser>svctask mkmdiskgrp -name mdiskgroup3 -ext 32 -warning 80%

MDisk Group, id [2], successfully created

IBM_2076:EMPIRE2:superuser>svctask mkmdiskgrp -name mdiskgroup4 -ext 32 -warning 80%

MDisk Group, id [3], successfully created

IBM_2076:EMPIRE2:superuser>svctask mkmdiskgrp -name mdiskgroup5 -ext 32 -warning 80%

MDisk Group, id [4], successfully created

 

svctask mkarray -drive 12:36:34:19:20:18:16:15 -level raid5 -strip 128 mdiskgroup1

svctask mkarray -drive 14:17:35:46:40:39:42:45 -level raid5 -strip 128 mdiskgroup2

svctask mkarray -drive 43:44:37:38:47:0:41:24 -level raid5 -strip 128 mdiskgroup3

svctask mkarray -drive 11:10:8:7:31:30:29:33 -level raid5 -strip 128 mdiskgroup4

svctask mkarray -drive 32:28:27:26:6:5:3:2 -level raid5 -strip 128 mdiskgroup5

 

VM

Storwize First Time Installation Step1

Now, i have a v7000

First you need to download and copy the tool to your USB drive, pls be careful your USB drive should be formated FAT32, if you format NTFS like me V7000 can not write down the response file and you start to hate from such process, be careful ….

V7000 Initial Tool Link

Execute it and you will see the configuration window like below, choose required one, my system is block because of this i will choose first one

Set the ip informations want to assign

Now, interesting need to be remove the usb drive and go to the behind of Storwize and plug the USB there and lets see the LEDs behind flashing and stopping ūüôā very funny

Pls click finish and remove the USB drive, don’t think that which port to plug, just one them

You will see that a file which name is satask.txt create when you look inside you will see the line below

satask mkcluster -clusterip 10.110.1.20 -gw 10.110.1.1 -mask 255.255.255.0

Because of V7000 do not have a Front Panel like on SVC then need to do it , but instead of COM port or such other i think its a good way to do.

Not: if you execute the tool again , do something or not , tool delete the initial file and need to reconfigure it.

if everything is okay then you will have satask_result.html file, if inside there is no error message out then everything should be okay.

try to access v7000 like https://10.110.1.20(replace it with your ip)

After login set the service ip first or use again initial utility to set it. Service mode are really useful because my v7000 is demo and i couldn’t configure v7000 with initial tool because its pre-configured and because of some error on system my all requests redirected to¬†https://10.110.1.20/service

Default password is passw0rd

via service; you can create the cluster , change the node mode like candidate , update the firmware , re-install , collect the logs bla bla …

IBM documents is very well i just want to indicate USB Format issue and if you have demo system instead of use initial tool use service mode to create cluster and upgrade or re-install the system

Pls contact me if something wrong or you are looking other then what i wrote
VM