Monthly Archives: May 2012

After minimal installation what i will do on Centos :)

Minimal configuration looks like good for need less package upgrade needs also for safe the OS but after over many commands are not there i was try to figure out something and please add command who read it i will update the article

First give ip address like below ;

ifconfig eth0 netmask
route add default gw

vi /etc/resolve.conf


yum upgrade

This is first round restart the server and go on …

yum install telnet

yum install bind-utils

yum install system-config-network-tui
….then run system-config-network-tui to configure ip address

before restart the system to check everything work

vi /etc/sysconfig/network-scripts/ifcfg-eth0  : Please set onboot=yes

chkconfig –level 3 iptables off
chkconfig –level 3 ip6tables off

yum install perl

yum install wget

Edit selinux config file

vi /etc/selinux/config and update SELINUX section like this SELINUX=disable

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

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



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 -gw -mask

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 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

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