topic Re: MSA1000 configuration problems in MSA Storage

MSA1000 configuration problems

Adel Elamin — Tue, 29 Apr 2008 15:28:16 GMT

Dear all
I have the following scenario
1- MSA with redundant controller and I/O Module
2- Four DL380 G5 Servers with Linux Enterprise 4 update 5 OS and redundant HBA Qlogic FC card “AE311A” on each server
3- Two HP Storage Work 4/8 SAN Switch “A8000A” which is the I/O Module and HBAs connected to the both SAN Switch for redundancy

I thing the HBA drivers are installed correctly because when I go to the directory /proc/scsi/qla2xxx I can find two files for the two HBAs “0” and “1”
Then I installed HP System Management Homepage & HP Array Configuration Utility ACU
I started the ACU http://127.0.0.1:2301 and it lunch OK but I can see only the Server controller P400 and I can’t see the MSA controller
I turned off every things and I followed the procedure of the MSA to power it ON, I turned ON the MSA at the first and I waited for some time then I powered ON the Servers but it stop when the Linux OS startup, this is the procedure in order the servers to see the MSA, if the MSA is OFF Linux OS boot OK but if the MSA is ON Linux stop at booting.

Please any reply could help about how to configure, create a new array, and present it to the servers by using the ACU
Thanks

Re: MSA1000 configuration problems

Adel Elamin — Wed, 30 Apr 2008 10:11:39 GMT

Hi again
I have checked the firmware version of the MSA, it is as follow:
MSA firmware v 7.00
EMU firmware v 1.1.86

Thanks

Re: MSA1000 configuration problems

Ganesh Chichakar_1 — Thu, 01 May 2008 04:57:05 GMT

Hi Adel

Just by looking at the issue you described here it is hard to guess what is going wrong but we need to do some trial n error.

1.>First thing to check whether HBA you using is compatible with LD380G5? as I found it is not listed in compatibility matrix. Is it possible for you to order the compatible one?

I have attached the list of compatible HBAs i found in one of the article.

2.>And if the one which you using currently is compatible are you able to detect MSA in Qlogic HBA BIOS ?

3.>At what stage does the OS hangs?

3.> Can you connect only one HBA to MSA switch and try booting OS.

4.> Have you tried the same with other OS like windows.

5.> Can you run show tech support and upload the configuration

6.>You can boot from smart start CD and if you are able to detect the MSA controllers you can create new array and the preent it to the server.

7.> If you planning to use MSA across multiple servers you need to use SSP feature.

Once we resolve your first issue reply back and I will help you in array configuration

Regards
Ganesh

Re: MSA1000 configuration problems

Adel Elamin — Mon, 05 May 2008 13:28:54 GMT

Dear Ganesh
I'm sorry for late reply due to my health status
Any way
1- HBS is compatible with the DL380 G5 and the Drivers is installed correctly in the Linux OS as well as there is a light I can see coming out from both side SAN Switch and HBA
2- /proc/scsi/qla2xxx ---> I can see 2 files 0 & 1 and I can see the WWN for the HBA inside the files
3- The OS hang at Initializing Hardware
4- Yes whenever the OS hang at Initializing Hardware, I remove the fiber cable form one HBA and the OS boot normally and I can detect the MSA in the /proc/scsi/scsi
5- No I tried only Linux OS Update 5
6- I promise you I'll run the command show tech_support and upload the result next time but now I donâ t have chance (the MSA still new and I did not do any thing on it)
7- Yes I boot from Smart start CD and ran ACU but it is also detect the Server RAID controller only
I'm very thankful Mr. Ganesh and I'm looking forward to hear form you soon

Re: MSA1000 configuration problems

John Kufrovich — Mon, 05 May 2008 23:12:33 GMT

Hello Adel,

First off, the latest SmartStarts no long support FC HBA when booting the CD. So, ACU on the SS CD will not detect MSA.

Here are a few suggestions,
1). Use HP Qlogic drivers. They include a library that allows our Applications to talk to the MSA.

2). Make sure your switch aren't zoned. Remove all MSA connections to switches. You can take one port from your HBA and attach it the the MSA Controller 1. If ACU works then you switch is zoned.

Can you provide the file in the qla2xxx/0 directory.

Re: MSA1000 configuration problems

Adel Elamin — Tue, 06 May 2008 06:48:39 GMT

Thank you Mr: John Kufrovich
I used the Latest SS CD which comes with servers â SmartStart V 7.9â

1- the drivers of the FC HBA detected automatically by the Linux OS at the first time of installing the OS, I see there is a Q-Logic drivers for Linux comes with the MSA support pack, I did install them in fail over mode "./INSTALL -f" in one server only, but still whenever I reboot the server hang in "Initializing Hardware" status, till I remove one fiber cable or switch off the MSA then it proceed.
2- Yes I did access the SAN switch through GUI and there is no zoning configuration, I did create a zone for all servers first HBA + firs MSA controller and another zone for all servers second HBA + anther MSA controller. but still same problem exist so I removed all zones again
3- Next time when I go to the site I will copy /proc/scsi, directory and upload it, but I have a problem that there is no Serial connection in my laptop to access the CLI of the MSA, so it is quite difficult to take my desktop computer every time to the site but I will try again.
I hope to hear your voice again
thanks

Re: MSA1000 configuration problems

Adel Elamin — Wed, 07 May 2008 08:08:49 GMT

Hi all
here are some useful information
1- I found a laptop with serial connection and I did access the CLI of the MSA here is the result of show tech_shpport:

##########################
# start of the command #
##########################

CLI-1> show tech_support

CLI-1> show version -all
MSA1000 Firmware Revision: 7.00b1500 (SGM0709DL4)
Build Time: 2007-01-24 16:13:17
MSA1000 Hardware Revision: a [AutoRev: 0x030000]
Fibre Module AutoRev: 0x010000
Box 1a PROLIANT 4L7I DB Rev: 1.86 (SGM0709DL4)
Box 1b PROLIANT 4L7I DT Rev: 1.86 (SGM0709DL4)

Disk Drives:
B T L BOX BAY GB Model Rev. Serial No.
0 0 0 1 1 146.8 COMPAQ BF1468B26B HPB9 3LN3MFXM00009827NZ9W
0 1 0 1 2 146.8 COMPAQ BF1468B26B HPB9 3LN3LW4W00009826JRMM
0 2 0 1 3 146.8 COMPAQ BF1468B26B HPB9 3LN3MXTV00009827PNX7
0 3 0 1 4 146.8 COMPAQ BF1468B26B HPB9 3LN3LSZ20000982604D9

CLI-1> show profile
Profile name = Default (Default) Mode value = (00002405)

Mode 0 = Peripheral Device LUN Addressing
Mode 1 = Legacy Failover
Mode 2 = Logical volumes connect as available on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = Normal bad block handling
Mode 5 = Logout selected initiators on TPRLO
Mode 6 = Fault management events not reported through Unit Attention
Mode 7 = Do not send FCP response info with SCSI status
Mode 8 = Do not send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Ignore Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

Profile name = Windows
Type = Standard Mode value = (00002405)

Mode 0 = Peripheral Device LUN Addressing
Mode 1 = Legacy Failover
Mode 2 = Logical volumes connect as available on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = Normal bad block handling
Mode 5 = Logout selected initiators on TPRLO
Mode 6 = Fault management events not reported through Unit Attention
Mode 7 = Do not send FCP response info with SCSI status
Mode 8 = Do not send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Ignore Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

Profile name = Windows (degraded performance)
Type = Standard Mode value = (00003405)

Mode 0 = Peripheral Device LUN Addressing
Mode 1 = Legacy Failover
Mode 2 = Logical volumes connect as available on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = Normal bad block handling
Mode 5 = Logout selected initiators on TPRLO
Mode 6 = Fault management events not reported through Unit Attention
Mode 7 = Do not send FCP response info with SCSI status
Mode 8 = Do not send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Enforce Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

Profile name = OpenVMS
Type = Standard Mode value = (00003473)

Mode 0 = Peripheral Device LUN Addressing
Mode 1 = Asymmetric Failover
Mode 2 = Logical volumes connect as unavailable on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = VMS shadow style bad block handling
Mode 5 = Logout all initiators on TPRLO
Mode 6 = Fault management events reported through Unit Attention
Mode 7 = Do not send FCP response info with SCSI status
Mode 8 = Do not send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Enforce Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

Profile name = Tru64
Type = Standard Mode value = (00003563)

Mode 0 = Peripheral Device LUN Addressing
Mode 1 = Asymmetric Failover
Mode 2 = Logical volumes connect as unavailable on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = Normal bad block handling
Mode 5 = Logout all initiators on TPRLO
Mode 6 = Fault management events reported through Unit Attention
Mode 7 = Do not send FCP response info with SCSI status
Mode 8 = Send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Enforce Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

Profile name = Linux
Type = Standard Mode value = (000034a7)

Mode 0 = Peripheral Device LUN Addressing
Mode 1 = Asymmetric Failover
Mode 2 = Logical volumes connect as available on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = Normal bad block handling
Mode 5 = Logout all initiators on TPRLO
Mode 6 = Fault management events not reported through Unit Attention
Mode 7 = Send FCP response info with SCSI status
Mode 8 = Do not send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Enforce Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

Profile name = Solaris
Type = Standard Mode value = (000034a7)

Mode 0 = Peripheral Device LUN Addressing
Mode 1 = Asymmetric Failover
Mode 2 = Logical volumes connect as available on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = Normal bad block handling
Mode 5 = Logout all initiators on TPRLO
Mode 6 = Fault management events not reported through Unit Attention
Mode 7 = Send FCP response info with SCSI status
Mode 8 = Do not send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Enforce Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

Profile name = Netware
Type = Standard Mode value = (000034a7)

Mode 0 = Peripheral Device LUN Addressing
Mode 1 = Asymmetric Failover
Mode 2 = Logical volumes connect as available on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = Normal bad block handling
Mode 5 = Logout all initiators on TPRLO
Mode 6 = Fault management events not reported through Unit Attention
Mode 7 = Send FCP response info with SCSI status
Mode 8 = Do not send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Enforce Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

Profile name = HP
Type = Standard Mode value = (00003ca6)

Mode 0 = Volume Set Addressing
Mode 1 = Asymmetric Failover
Mode 2 = Logical volumes connect as available on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = Normal bad block handling
Mode 5 = Logout all initiators on TPRLO
Mode 6 = Fault management events not reported through Unit Attention
Mode 7 = Send FCP response info with SCSI status
Mode 8 = Do not send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = No Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Enforce Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

Profile name = XP Storage Array
Type = Standard Mode value = (00003563)

Mode 0 = Peripheral Device LUN Addressing
Mode 1 = Asymmetric Failover
Mode 2 = Logical volumes connect as unavailable on Backup Controller
Mode 3 = Product ID of 'MSA1000 VOLUME' (only if Active-Standby mode)
Mode 4 = Normal bad block handling
Mode 5 = Logout all initiators on TPRLO
Mode 6 = Fault management events reported through Unit Attention
Mode 7 = Do not send FCP response info with SCSI status
Mode 8 = Send Unit Attention on failover
Mode 9 = SCSI inquiry revision field contains the actual version
Mode 10 = SCSI inquiry vendor ID='HP'
Mode 11 = Power On Reset Unit Attention generated on FC Login or Logout
Mode 12 = Enforce Force Unit Access on Write
Mode 13 = Admit Target Port on Reservation
Mode 14 = Asymmetrical Active/Active Operating Mode

CLI-1> show globals

Global Parameters:
System Name:
Rebuild Priority: low
Expand Priority: low

Cache is NOT configured - use 'set globals/unit' to configure cache!

Temperature:
No temperature sensor support.

CLI-1> show acl

No units exist!

CLI-1> show connections
Global_ris doesn't exist. No named connections exist.

Connection Name:
Host WWNN = 50014380-00C418BB
Host WWPN = 50014380-00C418BA
Profile Name = Default
Unit Offset = 0
Controller 1 Port 1 Status = Online
Controller 2 Port 1 Status = Offline

Connection Name:
Host WWNN = 50014380-00C418A1
Host WWPN = 50014380-00C418A0
Profile Name = Default
Unit Offset = 0
Controller 1 Port 1 Status = Offline
show disks Controller 2 Port 1 Status = Online

Disk List: (box,bay) (B:T:L) Size Speed Units

CLI-1> Enclosure 1: SCSI (0:06:00) PROLIANT 4L7I DB1.86
show box Disk101 (1,01) (0:00:00) 146.8GB 160 MB/s
none
Disk102 (1,02) (0:01:00) 146.8GB 160 MB/s none
Disk103 (1,03) (0:02:00) 146.8GB 160 MB/s none
Disk104 (1,04) (0:03:00) 146.8GB 160 MB/s none

Notes:
The speed is the currently negotiated speed to the disk. This may
be less than the maximum speed supported by the device due to bus
faults, loss of signal integrity, etc.
No external storage boxes are attached.

CLI-1> show units
No unit is configured on the
CLI-1> MSA1000.
show this_controller

CLI-1> Controller 1 (right controller):
MSA1000(c) Hewlett-Packard PB9840TX3U708F Version 7.00 Build 1500 Hardware A
Build Time: 2007-01-24 16:13:17
Integrated Enclosure.
Controller Identifer: 123
NODE_ID = 50060B00-00859AC0
SCSI_VERSION = SCSI-3
Supported Redundancy Mode: Active/Standby Asym-Active/Active
Current Redundancy Mode: Asym-Active/Active
Device Port SCSI address 6
Terminal speed for the CLI is set to 19200.
Host Port_1:
REPORTED PORT_ID 50060B00-00859AC1
PORT_1_TOPOLOGY = F_Port
Cache:
Unconfigured Version 2
Cache is GOOD, but Cache is NOT configured.
No unflushed data in cache
Batteries are disabled
Module #1 is fully charged and turned off.
Controller Up Time:
0 Days 00 Hours 14 Minutes 39 Seconds
show other_controller

CLI-1> Controller 2 (left controller):
MSA1000(c) Hewlett-Packard PB984ABX3VF089 Version 7.00 Build 1500 Hardware A
Build Time: 2007-01-24 16:13:17
Integrated Enclosure.
Controller Identifier:
NODE_ID = 50060B00-00859AC0
SCSI_VERSION = SCSI-3
Supported Redundancy Mode: Active/Standby Asym-Active/Active
Current Redundancy Mode: Asym-Active/Active
Device Port SCSI address 7
Terminal speed for the CLI is set to 19200.
Host Port_1:
REPORTED PORT_ID 50060B00-00859AC9
PORT_1_TOPOLOGY = F_Port
Cache:
Unconfigured Version 2
Cache is GOOD, but Cache is NOT configured.
No unflushed data in cache
Batteries are disabled
Module #1 is fully charged and turned off.
Controller Up Time:
0 Days 00 Hours 14 Minutes 37 Seconds
show eventlog
No Events Logged.

CLI-1> show preferred_path

CLI-1> No units exist!
show auto_path_change

CLI-1> No configuration exists!
###########################
# end of the command #
###########################

2- please find my attachment which include the directory /proc/scsi you can see all details about FC card and MSA
Thanks

Re: MSA1000 configuration problems

John Kufrovich — Fri, 09 May 2008 09:50:40 GMT

Adel,
On the MSA can you correctly assign each HBA connection to the appropriate OS profile. All your connections are set to default(Windows) they should be set to Linux.

Re: MSA1000 configuration problems

John Kufrovich — Fri, 09 May 2008 10:08:49 GMT

You can use the MSA cli

set connection unknown WWPN=50014380-00C418A0
profile=linux

you will need to do this for all you Linux conections. Just change the wwpn to the next hba.

Re: MSA1000 configuration problems

Adel Elamin — Thu, 15 May 2008 06:21:13 GMT

Dear all
I have contact some one and he advice me with the folloing:

1) The driver version that you mention you are running doesnâ t match with what you have mentioned in the e-mail.

The logs specifies that you are using driver is 8.01.04-d8 which is the built-in driver and is not recommended by HP.

Please download the proper driver for your HBA from the HP site and follow the default installation procedure. The driver must be in the failover mode. A default install of that driver will automatically put it in failover/multipath mode. (You can contact us if you need any help on this).

2) One of the HBAs is seeing both the controllers [scsi-qla1-adapter-node=5001438000c418a1;

scsi-qla1-adapter-port=5001438000c418a0;

scsi-qla1-target-0=50060b0000859ac1;

scsi-qla1-target-1=50060b0000859ac9;]

This is incorrect and will not work. Each HBA must only see one controller. (First HBA should go to the first controller, i.e. the controller left-hand side from the back, and second HBA go to the second

Controller, i.e. the controller right-hand side from the back)

3) The host OS mode must be set to Linux, to do this enable SSP (Selective Storage Presentation) and set the host OS mode.

If you follow the above steps the issue should get resolved

I'm going to do some actions next time and I will tell the news

thanks

Re: MSA1000 configuration problems

Adel Elamin — Thu, 15 May 2008 09:38:41 GMT

Dear John Kufrovich
today I went to the site and I did as you told me

CLI-1> show connections
Global_ris doesn't exist. No named connections exist.

Connection Name:
Host WWNN = 50014380-00C418BB
Host WWPN = 50014380-00C418BA
Profile Name = Default
Unit Offset = 0
Controller 1 Port 1 Status = Online
Controller 2 Port 1 Status = Offline

Connection Name:
Host WWNN = 50014380-00C418A1
Host WWPN = 50014380-00C418A0
Profile Name = Default
Unit Offset = 0
Controller 1 Port 1 Status = Offline
Controller 2 Port 1 Status = Online

CLI-1> set connection Unknown wwpn=50014380-00C418BA profile=Linux
Connection Unknown doesn't exist. No connection attributes are modified.

CLI-1> add connection app2-0 wwpn=50014380-00c418ba profile=linux
Cannot save any connection information because global_ris is NULL.

CLI-1> set globals rebuild_priority=medium system_name="msa-1" read_cache=50 write_cahche=50
Setting System Name to: 'msa-1'
Could not modify global parameters since no logical units exist!

Global Parameters:
System Name: msa-1
Rebuild Priority: low
Expand Priority: low

Cache is NOT configured - use 'set globals/unit' to configure cache!

Temperature:
No temperature sensor support.

CLI-1> show globals

Global Parameters:
System Name: msa-1
Rebuild Priority: low
Expand Priority: low

Cache is NOT configured - use 'set globals/unit' to configure cache!

Temperature:
No temperature sensor support.

=====================================

I did uninstall HBA old drivers form the server and install new version but still problem exists, when ever I reboot the server it will hang in initializing hardware till I remove one fiber connection
Please advice any help
Thanks

Re: MSA1000 configuration problems

John Kufrovich — Thu, 15 May 2008 15:39:24 GMT

No global RIS means you lost all your Array configuration.

What were you doing when this occurred. Did you up date MSA FW?

Re: MSA1000 configuration problems

Uwe Zessin — Thu, 15 May 2008 16:38:07 GMT

This message also comes up on a new box - you need to create at least one "unit" (logical disk).

Re: MSA1000 configuration problems

Adel Elamin — Sun, 18 May 2008 09:46:13 GMT

The problem has been solved, but I need an explanation for this

I only add one unit (logical drive) as you told me by using this command
add unit 0 data="disk101-disk102" raid_level=0

as soon as I did that and I reboot the servers, the servers never hang again as well as the logical drive on the MSA appear in the severs and the ACU can detect the MSA controller

I need an explanation for that before I close this thread
Thanks Uwe Zessin, John Kufrovich, and Ganesh Chichakar
I'm really glad for your support and I hope to hear form you again