IBM v7000 WebUI not responding

I ran into the case of non-responding WebUI to manage LUNs (and other things) on a IBM Storwize v7000.
You can only run satask commands if you connected to the CLI using the SSH private key which is associated with the user called superuser. No other SSH key will allow you to run satask commands:

IBM_Storwize:SAN1:superuser>sainfo lsservicenodes
panel_name cluster_id cluster_name node_id node_name relation node_status error_data
01-1 00000100204029A2 SAN1 1 node1 local Active
01-2 00000100204029A2 SAN1 2 node2 partner Active

To find out which node is the configuration node, run the following command

sainfo lsservicestatus <Active panel name>

the following line tells you which node is the config node:

IBM_Storwize:SAN1:superuser>sainfo lsservicestatus 01-1
panel_name 01-1
cluster_id 00000100204029a2
cluster_name SAN1
cluster_status Active
cluster_ip_count 2
cluster_port 1
cluster_ip 172.xx.xx.33
cluster_gw 172.xx.xx.252

Use the following command to restart the web service on the configuration node

satask restartservice -service tomcat 01-1

Wait at least 5 minutes for the service to restart before assuming that this has failed

If this do no’t solve your problems, you should restart the cannister with configuration node on it. Remember to connect to the Node that’s not configuration node. And restart the “partner”. If unable to get it reset, reset the canister physically. that is, pull it out a few inches from the chassis and then insert it again after 30 seconds.


#ibm, #storage-2, #v7000, #webui

How to extend a volume on an IBM DS3400

I inherited an old array that seems easy to manage using Storage Mangement Suite called IBM DS Storage Manager.

I had to extend one of the volumes hosted on that box. So I started up the management GUI, found the box, the correct array, and volume (“Logical drive”), and expected to just right click and add capacity.

I could add disks hence capacity to the array using the GUI but could not find anything about extending the volume.

I had to use my favorite search engine – duckduckgo– and found out that this operation can only be performed from the Shell. Which is actually a special shell utility.

PS C:\Program Files (x86)\IBM_DS\client> .\SMcli.exe -p $#$#@$password
Please type desired command.

show logicaldrive[“COMPANY-FS2-F”]


Logical Drive name: COMPANY-FS2-F

Logical Drive status: Optimal

Capacity: 557.793 GB
Logical Drive ID: 60:0a:0b:80:00:75:26:3d:00:00:01:c7:4d:9e:d3:d0
Subsystem ID (SSID): 0
Associated array: RAID5_ARRAY1
RAID level: 5

Drive type: Serial Attached SCSI (SAS)
Enclosure loss protection: No

Preferred owner: Controller in slot A
Current owner: Controller in slot A
Segment size: 128 KB
Capacity reserved for future segment size changes: Yes
Maximum future segment size: 2,048 KB
Modification priority: High
Read cache: Enabled
Write cache: Enabled
Write cache without batteries: Disabled
Write cache with mirroring: Enabled
Flush write cache after (in seconds): 10.00
Dynamic cache read prefetch: Enabled

Enable background media scan: Enabled
Media scan with redundancy check: Disabled

Pre-Read redundancy check: Disabled

After checking the details about the volume, I was able to extend the volume using:

set logicalDrive [COMPANY-TOR-FS2-F”] addCapacity=500 GB;

show logicalDrive [“COMPANY-TOR-FS2-F”] actionProgress;
Logical Drive COMPANY-TOR-FS2-F
Action: Initialization
Percent Complete: 53%

when growing the volume it does tell you much. Be sure to use the other command to verify the status.

And if you are looking for more information, I found the CLI manual here and not on the IBM website.


#cli, #ds3400, #ibm, #management, #smcli, #storage-2

ESXi5.5u2 install fail on new x240 m5 – failed to resolve circular relocation

The other day I ran into a strange issue. Just received a bunch of Flex Blade x240 for a Vmware cluster and trying to get ESXi installed I was stopped by the following message: Failed to Resolve circular relocation.

vmware esxi failure - failed to resolve circular relocation

failed to resolve circular relocation

It happened on one server so I tried the next one and the next, same thing!

I opened a case with Vmware which resulted in the following KB:2050443

It seems like ESXi doesn’t support MMIO regions above 4GB.

It took me for ever to find the relevant IBM/Lenovo information. Eventually found it at not thanks to Lenovo support!

So I made the following changes in my BIOS, from 64-Bit resource allocation: Enabled to Disabled. And MM Config Base from 2GB to 3GB.

You will find the above settings under the BIOS>System Settings> Devices and IO ports

vmware esxi failure - lenovo good config

I hope this helps.

#esx, #flex, #ibm, #lenovo, #server, #vmware