Any once can give me sizing tool for MSA1000/1500??
thanks you in advance

Hi,

We have a single controller MSA with two switches (cascaded - 12 ports available to hosts) and 2 * DL580s with 4*FC HBA 2101 each. Pl. check the attached diagram for the connection details. I created a simple zone comprising only 2 FC HBAs from both servers mapping to port 1 and 2 of both the switches. After enabling the configuration I can't see the LUNs and also can't see MSA from ACU. What could be the problem? Pl. help.

Thanks,
Karthik S S

Zone:


-switch1:admin> cfgshow
Defined configuration:
cfg: bootcfg bootzone
zone: bootzone
bootalias; 2,1; 2,2
alias: bootalias
20:00:00:00:c9:39:7b:8a; 20:00:00:00:c9:39:d9:6b;
20:00:00:00:c9:39:81:22; 20:00:00:00:c9:39:d9:83

Effective configuration:
no configuration in effect

-switch1:admin>

-switch1:admin> cfgenable "bootcfg"
Starting the Commit operation...
cfgEnable successfully completed

We are trying to create Windows 2012 Failover Cluster with HP P2000 G3 and HP DL380 G7. We installed latest HP MSA DSM and latest Qlogic drivers for the OS.

Our configuration is 3 node cluster with only one Fiber Channel adapter connected directly to the storage.(we don't use MPIO or SAN Switch)

When we try to validate the cluster we receive an error message.

 

Test Disk 0 does not support SCSI-3 Persistent Reservations commands needed to support clustered Storage Pools. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.

 

It seems that SCSI-3 persistent reservation is not working fine with Server 2012 . Is there anyone facing the same issue and is there an option fix that error?

We need to implement that cheap cluster solution as soon as possible.

Hello everybody,

 

for two days we're having this error displayed on one of our two active/active configured msa1000-controllers. I'm quite uneasy because of this error, since it is a live system at the core of our infrastructure. There have been no notable performance errors so far, but I'm wondering how to diagnose further.

I have attached an output of the "show tech_support" command. If you need any further information, please let me know!

 

Thanks,

 

stefan

Hi all,
complicated question here, i need a very good disks expert... This is my challenge ;-)

I'm trying to configure partition alignment on a MSA 1000 fw 7.20 Active/Active dual controller 512MB cache per controller.

attached chassis fully populated.
2x msa30 shelf fully populated.
__________________________________
total: 42 Disks

I'm following these specs:
http://msdn.microsoft.com/en-us/library/dd758814%28v=sql.100%29.aspx

and i noticed a thing on most of the LUNs:
on MSA1000 (ACU)
-stripe unit size: 128KB
-sectors: 32

on windows
-cluster size: 128KB
-partition offset: 128KB

dmdiag reveal a strange thing:

---------- Partition Table Info Disk 2 ----------


8,855 Cylinders
255 Tracks/Cylinder
63 Sectors/Track
512 Bytes/Sector
12 MediaType
142,255,575 Sectors (total)
72,834,854,400 Bytes (total)
71,127,788 KB
69,461 MB
67.8 GB

0 StartingOffset
72,837,857,280 PartitionLength
0 HiddenSectors
0 PartitionNumber
0 PartitionType
0 BootIndicator
0 RecognizedPartition
0 RewritePartition

MBR PartitionStyle
4 PartitionCount
21b45337 Signature

Starting Partition Hidden Total Partition Partition Boot Recognized Rewrite
Offset (bytes) Length (bytes) Sectors Sectors Number Type (HEX) Indicator Partition Partition

131,072 72,834,723,328 256 142,255,319 0 0x07 0 1 0
0 0 0 0 1 0x00 0 0 0
0 0 0 0 2 0x00 0 0 0
0 0 0 0 3 0x00 0 0 0

72,834,854,400 Bytes (142255575 sectors) Geometric size
72,837,857,280 Bytes (142261440 sectors) True size (measured)
72,837,857,280 Bytes (142261440 sectors) Reported size (Partition0)
0 Bytes ( 0 sectors) missing/wasted
---------------------------------------------


dmdiag thinks sectors are 63, while MSA asserts they're 32... this could be the source of a misalignment!!! (am i wrong?)

Wow, so i'm waiting for someone shading some light on the question... i'm stumped -_-'


Thanks in advance to any brave sysAdmin trying to resolve this one... :-D

dears,
MAS 1500 cs dual controllers one of them makes troubles on transactions and make system v.slow my intervention that i replaced the controller immediately with a new cash battery 256MB but still the same and i replaced also the fiber cable and SFP's and also replaced the I/O module now the system with redundant controller it's critical on the business.
i attached the CLI command file for more information

thanks in advance

Below is all of the show tech_support I could obtain. Received the error MSA 1000: External Array Accelerator Status Change. Status 1=other

Thank you

2 15 0 2 14 72.8 COMPAQ BD0728A4C4 HPB4 3KT5QPQY00009716QXR2


CLI-2> 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-2> show globals

Global Parameters:
System Name:
Rebuild Priority: high
Expand Priority: medium
Surface Delay: 3.0 seconds

Total Cache: 256MB
50% Read Cache: 128MB
50% Write Cache: 128MB

Temperature:
No temperature sensor support.
FIBRE BAY: 30 Celsius, 86 Fahrenheit

CLI-2> show acl

ACL is enabled:
Connection WWPN Units
ILEXCH2 10000000-C963C3CE 0, 4
unknown 10000000-C93AE557 1
ILGRAPH2 10000000-C94253C9 3
ILGRAPH1 210000E0-8B859CE3 3
ILSERVDATA 210000E0-8B1EB7EB 2
SWSILSRV2 210000E0-8B8552E3 1
SWSILSRV1 210000E0-8B1E09DD 1
ILEXCH1 10000000-C94253C3 0, 4
Inaccessible Units: None

CLI-2> show connections

Connection Name: SWSILSRV1
Host WWNN = 200000E0-8B1E09DD
Host WWPN = 210000E0-8B1E09DD
Profile Name = Windows
Unit Offset = 0
Controller 2 Port 1 Status = Online
Controller 1 Port 1 Status = Offline

Connection Name: ILEXCH1
Host WWNN = 20000000-C94253C3
Host WWPN = 10000000-C94253C3
Profile Name = Default
Unit Offset = 0
Controller 2 Port 1 Status = Online
show disks Controller 1 Port 1 Status = Offline


Connection Name: ILGRAPH2
Host WWNN = 20000000-C94253C9
Host WWPN = 10000000-C94253C9
Profile Name = Default
Unit Offset = 0
Controller 2 Port 1 Status = Online
Disk List: (box,bay) (B:T:L) Size Speed Units
show boxEnclosure 1: SCSI (0:07:00) PROLIANT 4L7I DB1.86

Disk101 (1,01) (0:00:00) 300.0GB 160 MB/s 2
Disk102 (1,02) (0:01:00) 300.0GB 160 MB/s 2
Disk103 (1,03) (0:02:00) 300.0GB 160 MB/s 2
Disk104 (1,04) (0:03:00) 300.0GB 160 MB/s 2
Disk105 (1,05) (0:04:00) 300.0GB 160 MB/s 2
Disk106 (1,06) (0:05:00) 300.0GB 160 MB/s 2
Disk109 (1,09) (1:01:00) 146.8GB 160 MB/s 0
Disk110 (1,10) (1:02:00) 146.8GB 160 MB/s 0
Disk111 (1,11) (1:03:00) 146.8GB 160 MB/s 0
Disk112 (1,12) (1:04:00) 146.8GB 160 MB/s 0
Disk113 (1,13) (1:05:00) 146.8GB 160 MB/s 0
Disk114 (1,14) (1:08:00) 146.8GB 160 MB/s 0
Enclosure 2: SCSI (2:07:00) PROLIANT 4LEE CP20
Disk201 (2,01) (2:00:00) 300.0GB 160 MB/s 3
Disk202 (2,02) (2:01:00) 300.0GB 160 MB/s 3
Disk203 (2,03) (2:02:00) 300.0GB 160 MB/s 3
Disk204 (2,04) (2:03:00) 300.0GB 160 MB/s 3
Disk205 (2,05) (2:04:00) 72.8GB 160 MB/s 4
Disk206 (2,06) (2:05:00) 72.8GB 160 MB/s 4
Disk207 (2,07) (2:08:00) 72.8GB 160 MB/s 1
Disk208 (2,08) (2:09:00) 72.8GB 160 MB/s 1
Disk209 (2,09) (2:10:00) 72.8GB 160 MB/s 1
Disk210 (2,10) (2:11:00) 72.8GB 160 MB/s 1
Disk211 (2,11) (2:12:00) 72.8GB 160 MB/s 1
Disk212 (2,12) (2:13:00) 72.8GB 160 MB/s 1
Disk213 (2,13) (2:14:00) 72.8GB 160 MB/s 1
Disk214 (2,14) (2:15:00) 72.8GB 160 MB/s 1

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.
Box #2:
SCSI enclosure at bus 2 channel 0 target 7
Firmware ID string: PROLIANT 4LEE
Firmware revision: CP20
Serial number: M0CNLMPX5F
Environmental Status:
Redundant power supply not present
Controller 1 Port 1 Status = Offline

Connection Name: RBNNT
Host WWNN = 20000000-C94013D1
Host WWPN = 10000000-C94013D1
Profile Name = Windows
Unit Offset = 0
Controller 2 Port 1 Status = Offline
show units Controller 1 Port 1 Status = Online


Connection Name: ILSERVDATA
Host WWNN = 200000E0-8B1EB7EB
Host WWPN = 210000E0-8B1EB7EB
Profile Name = Windows
Unit Offset = 0
Controller 2 Port 1 Status = Offline

Unit 0:
show this_controllerIn PDLA mode, Unit 0 is Lun 1; In VSA mode, Unit 0 is Lun 0.


Unit Identifier :
Device Identifier : 600805F3-0012D8D0-A6EBA9D0-1D070004
Preferred Path : Controller 1 (other controller)
Cache Status : Enabled
Max Boot Partition: Disabled
Volume Status : VOLUME OK
Mirror Init Status: Complete
6 Data Disk(s) used by lun 0:
Disk109: Box 1, Bay 09, (B:T:L 1:01:00)
Disk110: Box 1, Bay 10, (B:T:L 1:02:00)
Disk111: Box 1, Bay 11, (B:T:L 1:03:00)
Disk112: Box 1, Bay 12, (B:T:L 1:04:00)
Disk113: Box 1, Bay 13, (B:T:L 1:05:00)
Disk114: Box 1, Bay 14, (B:T:L 1:08:00)
Spare Disk(s) used by lun 0:
No spare drive is designated.
Logical Volume Raid Level: MIRROR FAULT TOLERANCE (RAID 1)
stripe_size=128kB
Logical Volume Capacity : 420,041MB

Unit 1:
In PDLA mode, Unit 1 is Lun 2; In VSA mode, Unit 1 is Lun 1.
Unit Identifier :
Device Identifier : 600805F3-0012D8D0-A2A316E4-FA400006
Preferred Path : Controller 1 (other controller)
Cache Status : Enabled
Max Boot Partition: Disabled
Volume Status : VOLUME OK
Parity Init Status: Complete
8 Data Disk(s) used by lun 1:
Disk207: Box 2, Bay 07, (B:T:L 2:08:00)
Disk208: Box 2, Bay 08, (B:T:L 2:09:00)
Disk209: Box 2, Bay 09, (B:T:L 2:10:00)
Disk210: Box 2, Bay 10, (B:T:L 2:11:00)
Disk211: Box 2, Bay 11, (B:T:L 2:12:00)
Disk212: Box 2, Bay 12, (B:T:L 2:13:00)
Disk213: Box 2, Bay 13, (B:T:L 2:14:00)
Disk214: Box 2, Bay 14, (B:T:L 2:15:00)
Spare Disk(s) used by lun 1:
No spare drive is designated.
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)
stripe_size=64kB
Logical Volume Capacity : 486,250MB

Unit 2:
In PDLA mode, Unit 2 is Lun 3; In VSA mode, Unit 2 is Lun 2.
Unit Identifier :
Device Identifier : 600805F3-0012D8D0-AE443DC2-4A380007
Preferred Path : Controller 1 (other controller)
Cache Status : Enabled
Max Boot Partition: Disabled
Volume Status : VOLUME OK
Parity Init Status: Complete
6 Data Disk(s) used by lun 2:
Disk101: Box 1, Bay 01, (B:T:L 0:00:00)
Disk102: Box 1, Bay 02, (B:T:L 0:01:00)
Disk103: Box 1, Bay 03, (B:T:L 0:02:00)
Disk104: Box 1, Bay 04, (B:T:L 0:03:00)
Disk105: Box 1, Bay 05, (B:T:L 0:04:00)
Disk106: Box 1, Bay 06, (B:T:L 0:05:00)
Spare Disk(s) used by lun 2:
No spare drive is designated.
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)
stripe_size=64kB
Logical Volume Capacity : 1,430,508MB

Unit 3:
In PDLA mode, Unit 3 is Lun 4; In VSA mode, Unit 3 is Lun 3.
Unit Identifier :
Device Identifier : 600805F3-00059EA0-A7EA9555-5DAD0006
Preferred Path : Controller 2 (this controller)
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Parity Init Status: Complete
4 Data Disk(s) used by lun 3:
Disk201: Box 2, Bay 01, (B:T:L 2:00:00)
Disk202: Box 2, Bay 02, (B:T:L 2:01:00)
Disk203: Box 2, Bay 03, (B:T:L 2:02:00)
Disk204: Box 2, Bay 04, (B:T:L 2:03:00)
Spare Disk(s) used by lun 3:
No spare drive is designated.
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)
stripe_size=16kB
Logical Volume Capacity : 858,305MB

Unit 4:
In PDLA mode, Unit 4 is Lun 5; In VSA mode, Unit 4 is Lun 4.
Unit Identifier :
Device Identifier : 600805F3-00059EA0-A5651E25-EE180007
Preferred Path : Controller 1 (other controller)
Cache Status : Enabled
Max Boot Partition: Disabled
Volume Status : VOLUME OK
Mirror Init Status: Complete
2 Data Disk(s) used by lun 4:
Disk205: Box 2, Bay 05, (B:T:L 2:04:00)
Disk206: Box 2, Bay 06, (B:T:L 2:05:00)
Spare Disk(s) used by lun 4:
No spare drive is designated.
Logical Volume Raid Level: MIRROR FAULT TOLERANCE (RAID 1)
stripe_size=128kB
Logical Volume Capacity : 69,463MB
Controller 2 (left controller):
MSA1000(c) Hewlett-Packard P56350DX3PT00Z Version 7.00 Build 1500 Hardware 7
Build Time: 2007-01-24 16:13:17
Integrated Enclosure.
Controller Identifier:
NODE_ID = 500805F3-0012D8D0
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 500805F3-0012D8D9
PORT_1_TOPOLOGY = F_Port
Cache:
128 megabyte read cache 128 megabyte write cache Version 2
Cache is GOOD, and Cache is enabled.
No unflushed data in cache
Batteries are enabled
Module #1 is fully charged and turned on.
Controller Up Time:
218 Days 05 Hours 15 Minutes 27 Seconds
Health:
Surface Scan: Complete.
Rebuild Status: Complete.
Expansion: Complete.
Controller 1 Port 1 Status = Online

Connection Name: ILGRAPH1
Host WWNN = 200000E0-8B859CE3
Host WWPN = 210000E0-8B859CE3
Profile Name = Windows
Unit Offset = 0
Controller 2 Port 1 Status = Offline
show other_controller Controller 1 Port 1 Status = Online


Connection Name: SWSILSRV2
Host WWNN = 200000E0-8B8552E3
Host WWPN = 210000E0-8B8552E3
Profile Name = Windows
Unit Offset = 0
Controller 2 Port 1 Status = Offline
show eventlog Controller 1 Port 1 Status = Online


Connection Name: ILEXCH2
Host WWNN = 20000000-C963C3CE
Host WWPN = 10000000-C963C3CE
Profile Name = Windows
Unit Offset = 0
Controller 2 Port 1 Status = Offline
Controller 1 (right controller):
MSA1000(c) Hewlett-Packard P56350GX3QN0CO Version 7.00 Build 1500 Hardware A
Build Time: 2007-01-24 16:13:17
Integrated Enclosure.
Controller Identifier:
NODE_ID = 500805F3-0012D8D0
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 500805F3-0012D8D1
PORT_1_TOPOLOGY = F_Port
Cache:
128 megabyte read cache 128 megabyte write cache Version 2
Cache is GOOD, and Cache is enabled.
No unflushed data in cache
Batteries are disabled
Module #1 is fully charged and turned off.
Controller Up Time:
218 Days 04 Hours 57 Minutes 17 Seconds
Health:
Surface Scan: Complete.
Rebuild Status: Complete.
Expansion: Complete.
show preferred_path Controller 1 Port 1 Status = Online


Connection Name:
CLI-2> bad
show auto_path_change Host WWNN =
10000000-C93216B7
Host WWPN = 10000000-C93216B7
Profile Name = Windows
Unit Offset = 0

Implicit (automatic load-based) LUN ownership changes are currently ENABLED.
Implicit LUN ownership change preferences are as follows:
Minimum % of proxied requests to trigger implicit path change..: 75%
Minimum number of requests to LUN before path change enabled...: 65536
Minimum time to wait before changing ownership after power-up..: 30 minutes
Minimum time between ownership changes for LUN.................: 30 minutes

Connection Name: bad
Host WWNN = 10000000-C932175E
Host WWPN = 10000000-C932175E
Profile Name = Windows
Unit Offset = 0

Connection Name: unknown
Host WWNN = 10000000-C93AE557
Host WWPN = 10000000-C93AE557
Profile Name = Windows
Unit Offset = 0

Hi,
we have a win2k8 R2 server with MSA2324i storage. Server has 2 NIC (1GB each) that are dedicated to storage (have different address from the main company network). Storage is connected, we can mount the drive, everything is OK. When we tried to configure MPIO, it works for failover purpose (we start copying a large file, then disconnect one NIC, and the other takes up and continues). But we wanted to add multipath support in order to have 2GB transfer between the storage and server. And I just can't get it to work.
I followed all the procedures I could find, mainly the ones described in "iSCSI user guide", but I can't get the 2GB connection, no way, no how.
What am I doing wrong?

I have a total of 4 addresses on my storage:
A1 10.0.0.83, A2 10.0.0.84, B1 10.0.0.85, B2 10.0.0.86.
A1 & B1 are connected to a GB switch 1, and A2, B2 to a GB switch 2. Also, server's NIC are connected one to each switch.
In iSCSI initiator, when I put "target portal" under "Discovery" tab, I put only one IP (10.0.0.83). When I move to "targets" tab, I see a target. When I click "log on" and "advanced", then select "MS iSCSI initiator" as "local adapter", then one NIC IP as "source IP", under "target portal" I can see all four of storage's IP adresses (all with the same default port). I select one of them, at random, and that works perfectly.
Then, followind the instructions, I select the "details" button, select the (only one) identifier there is, and then "connections". I see a "round robin" as load balance policy, and only one connection assigned to the session. As it should be.
Then, I click on "add" and "advanced", and since the "local adapter" is grayed out (MS iSCSI selected), I can only choose "source IP" (where I can see all my local network connections, and I choose the other NIC", but under "target portal" I don't see all 4 of the storage IP's but just the one I have already set up.

Any ideas on what I'm doing wrong?
thanx a lot!!!

We have a 6 hr CTR contract on our msa2324sa.

On Friday, controller A failed. HP sent out a field engineer with a new part. Upon replacing that part, we lost all access to the MSA drives. Troubleshot with HP until midnight and nothing was resolved. Sat morning re-engaged with HP support, and we tried removing the new controller. Working with the one good controller, we were able to use the MSA. This morning the field engineer came out with another controller. Again, when both controllers are in the msa we can not access the disks. Troubleshooting required power cycling the msa multiple times.

We've had more that 24 hrs of down time for 20 production servers on what is supposed to be a hot-swap fault tolerant system.

Last update is that we have been waiting over 4 hours for a call back from level 2 on this case. (#4614517008)

We have a limited window to work with hp troubleshooting on this as tomorrow we will be compelled to run the msa with the one good controller.

Can any one give me contact information for somebody at HP who can get our system back to optimal operating state?

Thank you.

Has naybody experienced this problem.

Dual controller MSA 1500 firmware v 7.0 attached to 8 MSA 20 enclosures configured with 10 RAID 5 Arrays with a dedicated 1x spare per shelf.

Problem is when disk fails, rebuild using spare starts, but after aprox 3 hours it fails whole shelf where affected disk resides.
I would put it down to MSA not able to carry on rebuild during heavy I/O load.


I have attached CLI capture report after failure attached.

Any advise would be appreciated.

Tomas

Hi,

I have recently relocated our MSA1500 (+msa30+msa20) to our DR datacenter. Originally it was configured under windows based ACU but due to no windows based connections at our DR site I have had to configure via the CLI. Once installed, it seemed ok and the front lights acted normally but since then the MSA30 is alternating flashing between the first 6 disks and the last 8 and the MSA20 drives are just showing a constant blue light. I have ran a 'show tech_support' but nothing on there is telling me I have problems. Would someone mind having a look and let me know if I have missed something please?

### BEGIN LOG - DATE: 090715, TIME: 113258 ###

show tech_support

CLI-1> show version -all
MSA1500 Firmware Revision: 7.00b1500 (SGA053501T)
Build Time: 2007-01-24 16:13:17
MSA1500 Hardware Revision: a [AutoRev: 0x030000]
Fibre Module AutoRev: 0x020000
SCSI I/O Module Bus 0 Revision: 2.02
SCSI I/O Module Bus 1 Revision: <>
SCSI I/O Module Bus 2 Revision: 2.02
SCSI I/O Module Bus 3 Revision: <>
Fan Control Module A Revision: 2.38
Fan Control Module B Revision: 2.38
Box 3 PROLIANT 4LEE Rev: CP20 (MBNDLMPX9C)
Box 5 PROLIANT 8LCE Rev: 2.02 (E00SMLJ193)
Box 5 Fan Control Module A Rev: 2.38
Box 5 Fan Control Module B Rev: 2.38

Disk Drives:
B T L BOX BAY GB Model Rev. Serial No.
0 4 1 5 1 500.0 Unknown GB0500C4413 HPG 9QG3BZPC
0 4 2 5 2 500.0 Unknown GB0500C4413 HPG 9QG2HSS7
0 4 3 5 3 500.0 Unknown GB0500C4413 HPG 9QG2E0H8
0 4 4 5 4 500.0 Unknown GB0500C4413 HPG 9QG2GPVS
0 4 5 5 5 500.0 Unknown GB0500C4413 HPG 9QG3BVW0
0 4 6 5 6 500.0 Unknown GB0500C4413 HPG 9QG2291C
0 4 7 5 7 500.0 Unknown GB0500C4413 HPG 9QG3BWSX
0 4 8 5 8 500.0 Unknown GB0500C4413 HPG 9QG3C5CF
0 4 9 5 9 500.0 Unknown GB0500C4413 HPG 9QG3BWYQ
0 4 10 5 10 500.0 Unknown GB0500C4413 HPG 9QG3BX2W
0 4 11 5 11 500.0 Unknown GB0500C4413 HPG 9QG0HMJ8
0 4 12 5 12 500.0 Unknown GB0500C4413 HPG 9QG2C311
2 0 0 3 1 300.0 COMPAQ BD30089BBA HPB1 DA01P780DMM00732
2 1 0 3 2 300.0 COMPAQ BD30089BBA HPB1 DA01P780DNPC0732
2 2 0 3 3 300.0 COMPAQ BD30089BBA HPB1 DA01P780DRN60733
2 3 0 3 4 300.0 COMPAQ BD30089BBA HPB1 DA01P780DNKJ0732
2 4 0 3 5 300.0 COMPAQ BD30089BBA HPB1 DA01P810GSHR0805
2 5 0 3 6 300.0 COMPAQ BD30089BBA HPB1 DA01P780DMWB0732
2 8 0 3 7 300.0 COMPAQ BD30089BBA HPB1 DA01P780DMW50732
2 9 0 3 8 300.0 COMPAQ BD30089BBA HPB1 DA01P780DNRL0732
2 10 0 3 9 300.0 COMPAQ BD30089BBA HPB1 DA01P780DNUU0732
2 11 0 3 10 300.0 COMPAQ BD30089BBA HPB1 DA01P780DNY10732
2 12 0 3 11 300.0 COMPAQ BD30089BBA HPB1 DA01P780DNP70732
2 13 0 3 12 300.0 COMPAQ BD30089BBA HPB1 DA01P780DMPF0732
2 14 0 3 13 300.0 COMPAQ BD30089BBA HPB1 DA01P780DNR30732
2 15 0 3 14 300.0 COMPAQ BD30089BBA HPB1 DA01P780DNY50732


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: DAR-MSA1500
Rebuild Priority: low
Expand Priority: medium
Surface Delay: 3.0 seconds

Total Cache: 512MB
50% Read Cache: 256MB
50% Write Cache: 256MB

Temperature:
EMU: 25 Celsius, 77 Fahrenheit
PS1: 24 Celsius, 75 Fahrenheit
PS2: 25 Celsius, 77 Fahrenheit

CLI-1> show acl

ACL is enabled:
Connection WWPN Units
DARVM01 50014380-029C2296 0, 1, 2, 3, 4, 5, 6
DARVM02 50014380-03AEC41A 0, 1, 2, 3, 4, 5, 6
Inaccessible Units: None

CLI-1> show connections

Connection Name: DARVM02
Host WWNN = 50014380-03AEC41B
Host WWPN = 50014380-03AEC41A
Profile Name = Linux
Unit Offset = 0
Controller 1 Port 1 Status = Online
Controller 2 Port 1 Status = Online

Connection Name: DARVM01
Host WWNN = 50014380-029C2297
Host WWPN = 50014380-029C2296
Profile Name = Linux
Unit Offset = 0
Controller 1 Port 1 Status = Online
show disks Controller 2 Port 1 Status = Online

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

CLI-1> Enclosure 3: SCSI (2:06:00) PROLIANT 4LEE CP20
show box Disk301 (3,01) (2:00:00) 300.0GB 160 MB/s
3
Disk302 (3,02) (2:01:00) 300.0GB 160 MB/s 3
Disk303 (3,03) (2:02:00) 300.0GB 160 MB/s 3
Disk304 (3,04) (2:03:00) 300.0GB 160 MB/s 3
Disk305 (3,05) (2:04:00) 300.0GB 160 MB/s 4
Disk306 (3,06) (2:05:00) 300.0GB 160 MB/s 4
Disk307 (3,07) (2:08:00) 300.0GB 160 MB/s 4
Disk308 (3,08) (2:09:00) 300.0GB 160 MB/s 4
Disk309 (3,09) (2:10:00) 300.0GB 160 MB/s 5
Disk310 (3,10) (2:11:00) 300.0GB 160 MB/s 5
Disk311 (3,11) (2:12:00) 300.0GB 160 MB/s 5
Disk312 (3,12) (2:13:00) 300.0GB 160 MB/s 5
Disk313 (3,13) (2:14:00) 300.0GB 160 MB/s 6
Disk314 (3,14) (2:15:00) 300.0GB 160 MB/s 3, 4, 5 (spare)
Enclosure 5: SATA (0:04:00) PROLIANT 8LCE 2.02
Disk501 (5,01) (0:04:01) 500.0GB 160 MB/s 0
Disk502 (5,02) (0:04:02) 500.0GB 160 MB/s 0
Disk503 (5,03) (0:04:03) 500.0GB 160 MB/s 0
Disk504 (5,04) (0:04:04) 500.0GB 160 MB/s 0
Disk505 (5,05) (0:04:05) 500.0GB 160 MB/s 1
Disk506 (5,06) (0:04:06) 500.0GB 160 MB/s 1
Disk507 (5,07) (0:04:07) 500.0GB 160 MB/s 1
Disk508 (5,08) (0:04:08) 500.0GB 160 MB/s 1
Disk509 (5,09) (0:04:09) 500.0GB 160 MB/s 2
Disk510 (5,10) (0:04:10) 500.0GB 160 MB/s 2
Disk511 (5,11) (0:04:11) 500.0GB 160 MB/s 2
Disk512 (5,12) (0:04:12) 500.0GB 160 MB/s 0, 1, 2 (spare)

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.


CLI-1> Box #3:
SCSI enclosure at bus 2 channel 0 target 6
show units Firmware ID string: PROLIANT 4LEE

Firmware revision: CP20
Serial number: MBNDLMPX9C
Environmental Status:
No alert conditions reported

Box #5:
SATA enclosure at bus 0 channel 1 target 4
Firmware ID string: PROLIANT 8LCE
Firmware revision: 2.02
Serial number: E00SMLJ193
Environmental Status:
No alert conditions reported
Cache Information:
Total Memory: 112MB
Read Cache: 56MB
Write Cache: 56MB
Cache Status: Enabled
Battery #1 (lower): OK
Battery #2 (upper): OK

Unit 0:

CLI-1> In PDLA mode, Unit 0 is Lun 1; In VSA mode, Unit 0 is Lun 0.
show this_controllerUnit Identifier : DAR-VMSTORAGE1

Device Identifier : 600508B3-0091A190-0D1BEC97-B7540002
Preferred Path : Controller 1 (this controller)
Cache Status : Enabled
Max Boot Partition: Disabled
Volume Status : VOLUME OK
Parity Init Status: Complete
4 Data Disk(s) used by lun 0:
Disk501: Box 5, Bay 01, (B:T:L 0:04:01)
Disk502: Box 5, Bay 02, (B:T:L 0:04:02)
Disk503: Box 5, Bay 03, (B:T:L 0:04:03)
Disk504: Box 5, Bay 04, (B:T:L 0:04:04)
Spare Disk(s) used by lun 0:
Disk512: Box 5, Bay 12, (B:T:L 0:04:12)
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)
stripe_size=64kB
Logical Volume Capacity : 1,430,721MB

Unit 1:
In PDLA mode, Unit 1 is Lun 2; In VSA mode, Unit 1 is Lun 1.
Unit Identifier : DAR-VMSTORAGE2
Device Identifier : 600508B3-0091A190-F8B985C9-D1090003
Preferred Path : Controller 1 (this controller)
Cache Status : Enabled
Max Boot Partition: Disabled
Volume Status : VOLUME OK
Parity Init Status: Complete
4 Data Disk(s) used by lun 1:
Disk505: Box 5, Bay 05, (B:T:L 0:04:05)
Disk506: Box 5, Bay 06, (B:T:L 0:04:06)
Disk507: Box 5, Bay 07, (B:T:L 0:04:07)
Disk508: Box 5, Bay 08, (B:T:L 0:04:08)
Spare Disk(s) used by lun 1:
Disk512: Box 5, Bay 12, (B:T:L 0:04:12)
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)
stripe_size=64kB
Logical Volume Capacity : 1,430,721MB

Unit 2:
In PDLA mode, Unit 2 is Lun 3; In VSA mode, Unit 2 is Lun 2.
Unit Identifier : DAR-VMSTORAGE3
Device Identifier : 600508B3-0091A190-61F1F724-E8F20004
Preferred Path : Controller 2 (other controller)
Cache Status : Enabled
Max Boot Partition: Disabled
Volume Status : VOLUME OK
Parity Init Status: Complete
3 Data Disk(s) used by lun 2:
Disk509: Box 5, Bay 09, (B:T:L 0:04:09)
Disk510: Box 5, Bay 10, (B:T:L 0:04:10)
Disk511: Box 5, Bay 11, (B:T:L 0:04:11)
Spare Disk(s) used by lun 2:
Disk512: Box 5, Bay 12, (B:T:L 0:04:12)
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)
stripe_size=64kB
Logical Volume Capacity : 953,811MB

Unit 3:
In PDLA mode, Unit 3 is Lun 4; In VSA mode, Unit 3 is Lun 3.
Unit Identifier :
Device Identifier : 600508B3-0091A190-7C3ABE8E-51C70006
Preferred Path : Controller 1 (this controller)
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Parity Init Status: Complete
4 Data Disk(s) used by lun 3:
Disk301: Box 3, Bay 01, (B:T:L 2:00:00)
Disk302: Box 3, Bay 02, (B:T:L 2:01:00)
Disk303: Box 3, Bay 03, (B:T:L 2:02:00)
Disk304: Box 3, Bay 04, (B:T:L 2:03:00)
Spare Disk(s) used by lun 3:
Disk314: Box 3, Bay 14, (B:T:L 2:15:00)
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)
stripe_size=64kB
Logical Volume Capacity : 858,300MB

Unit 4:
In PDLA mode, Unit 4 is Lun 5; In VSA mode, Unit 4 is Lun 4.
Unit Identifier :
Device Identifier : 600508B3-0091A190-A51E53C5-8CD80007
Preferred Path : Controller 2 (other controller)
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Parity Init Status: Complete
4 Data Disk(s) used by lun 4:
Disk305: Box 3, Bay 05, (B:T:L 2:04:00)
Disk306: Box 3, Bay 06, (B:T:L 2:05:00)
Disk307: Box 3, Bay 07, (B:T:L 2:08:00)
Disk308: Box 3, Bay 08, (B:T:L 2:09:00)
Spare Disk(s) used by lun 4:
Disk314: Box 3, Bay 14, (B:T:L 2:15:00)
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)
stripe_size=64kB
Logical Volume Capacity : 858,300MB

Unit 5:
In PDLA mode, Unit 5 is Lun 6; In VSA mode, Unit 5 is Lun 5.
Unit Identifier :
Device Identifier : 600508B3-0091A190-4D6A6F64-525B0008
Preferred Path : Controller 2 (other controller)
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Parity Init Status: Complete
4 Data Disk(s) used by lun 5:
Disk309: Box 3, Bay 09, (B:T:L 2:10:00)
Disk310: Box 3, Bay 10, (B:T:L 2:11:00)
Disk311: Box 3, Bay 11, (B:T:L 2:12:00)
Disk312: Box 3, Bay 12, (B:T:L 2:13:00)
Spare Disk(s) used by lun 5:
Disk314: Box 3, Bay 14, (B:T:L 2:15:00)
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (RAID 5)
stripe_size=64kB
Logical Volume Capacity : 858,300MB

Unit 6:
In PDLA mode, Unit 6 is Lun 7; In VSA mode, Unit 6 is Lun 6.
Unit Identifier :
Device Identifier : 600508B3-0091A190-28A209DE-E4700009
Preferred Path : Controller 2 (other controller)
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
1 Data Disk(s) used by lun 6:
Disk313: Box 3, Bay 13, (B:T:L 2:14:00)
Spare Disk(s) used by lun 6:
No spare drive is designated.
Logical Volume Raid Level: NO FAULT TOLERANCE (RAID 0)
stripe_size=128kB
Logical Volume Capacity : 286,095MB

CLI-1> Controller 1 (right controller):
MSA1500(c) Hewlett-Packard PB9840TX3V109A Version 7.00 Build 1500 Hardware A
Build Time: 2007-01-24 16:13:17
Component Enclosure.
Controller Identifier:
NODE_ID = 500508B3-0091A190
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 500508B3-0091A191
PORT_1_TOPOLOGY = F_Port
Cache:
256 megabyte read cache 256 megabyte write cache Version 2
Cache is GOOD, and Cache is enabled.
Unflushed data in cache
Batteries are enabled
Module #1 is fully charged and turned on.
Module #2 is fully charged and turned on.
Controller Up Time:
6 Days 16 Hours 26 Minutes 48 Seconds
Health:
Surface Scan: Complete.
Rebuild Status: Complete.
Expansion: Complete.
show other_controller

CLI-1> Controller 2 (left controller):
MSA1500(c) Hewlett-Packard P56350HX3SP04W Version 7.00 Build 1500 Hardware 7
Build Time: 2007-01-24 16:13:17
Component Enclosure.
Controller Identifier:
NODE_ID = 500508B3-0091A190
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 500508B3-0091A199
PORT_1_TOPOLOGY = F_Port
Cache:
256 megabyte read cache 256 megabyte write cache Version 2
Cache is GOOD, and Cache is enabled.
No unflushed data in cache
Batteries are disabled
Module #1 is fully charged and turned off.
Module #2 is fully charged and turned off.
Controller Up Time:
6 Days 16 Hours 30 Minutes 53 Seconds
Health:
Surface Scan: Complete.
Rebuild Status: Complete.
Expansion: Complete.
show eventlog
TIME CLASS SUB DETL MESSAGE

CLI-1> 0d 01:29:31.2 0006 0000 0000 Redundant operation state change.
show preferred_path0d 01:36:13.2 0006 0000 0000 Redundant operation state change.

0d 02:15:48.4 0005 0002 0000 Parity/consistency initialization complete, volume: 3
0d 13:40:37.8 0006 0000 0000 Redundant operation state change.



CLI-1> Controller 1 (this_controller) is the current optimal path for these units:
show auto_path_change0
,1,3
Controller 2 (other_controller) is the current optimal path for these units:
2,4,5,6
Implicit (automatic load-based) LUN ownership changes are currently ENABLED.


CLI-1> Implicit (automatic load-based) LUN ownership changes are currently ENABLED.
Implicit LUN ownership change preferences are as follows:
Minimum % of proxied requests to trigger implicit path change..: 75%
Minimum number of requests to LUN before path change enabled...: 65536
Minimum time to wait before changing ownership after power-up..: 30 minutes
Minimum time between ownership changes for LUN.................: 30 minutes


### END LOG - DATE: 090715, TIME: 113343 ###

Hello,
I set up a new DL320 g5 with an FC1142SR on SuSE 10 SP2 and I want to add additional storage from an MSA1500 SAN Starter Kit.

ACU has been configured through the HomePage and the array has been configured. I'm not sure how to make the logical disks on the MSA available to the OS. Is there something I need to configure in HBA?

Thanks for any help,

Warren

I have 5 ESX 3.5 hosts connected (using Multi pathing) to an old MSA1000. Each ESX host has two fibre mezzanine cards connected to two external Brocade 32 port FC switches, these in turn connect to each I/O module in the back of the MSA1000. Every so often, the ESX hosts lose connection to the SAN, we then have to power down all virtual servers, followed by all ESX hosts, then followed by the MSA1000. We the bring them all back in the reverse order which temporarily resumes the service. Is there anywhere I can start looking to see if there are any problems within the infrastructure.

Many thanks in advance.

p2000コントローラーのFWをダウンロードしたいのですが、HPEにログインしFirmware(Entitlement Required)よりCP018819やcp024276のダウンロードをしているのですが０KBで正常にダウンロード出来ません。

解決策等ご存知の方いましたら教えてください。

Hi all.

I have a question.

I'm having disk space problems on one of our servers (Windows 2003). We have a MSA1000 with two array's configured as following:

Array A
Logical drive 1 99 MB
Logical drive 2 175 GB server1
Logical drive 3 56 gb server1
Logical drive 4 49 gb server2
Logical drive 5 50 gb server1
Logical drive 6 55 gb server3
Logical drive 7 44 gb server3
Unused space 21 GB

Array B
Logical drive 8 49 server2
Logical drive 9 49 server1
Logical drive 10 108 server1
Unused space 390 GB

To solve the problem i want to extend Lun 8 with 101 GB from the 390 unused space. so i have a total of 150 GB available on lun 8.

But can i just extend the LUN 8 with the Unused space (390 GB)? Does Windows 2003 just see the free disk space on the logical disk (LUN 8)or do i have to do more?

I hope someone can help me.

I seem to have lost my post, so I'm going to throw this up again.

We have an MSA1500 with (3) MSA30 shelves and (2) MSA20 shelves running firmware 5.02/1.48. There are (4) servers connected running Windows Server 2003 w/SP1. We have redundant Brocade 4GB switches with the second switch currently turned off.

When I try to load MPIO Basic 1.1, I get an NTVDM error.

I have been searching everywhere, but cannot find the full featured version for MSA although the full featured MPIO Manager software hints that there is a version for the MSA.

So, I guess my questions are:

Any ever get the NTVDM error trying to install MPIO 1.1 for the MSA1500?

Anyone know where the full featured version is for the MSA?

Is there something in my configuration that isn't jiving? When I downloaded firmware 5.02, it came with 1.42 for the MSA20, but the MSA20 itself shipped with 1.48 so I left it.

Any help is greatly appreciated.

Mike

We have an MSA8000 (2) sets of dual-HSG80 controllers running firmware V87F-3. (42) 72.8 GB Disks per SAN. We carved out (6) 339 LUNs, and are presenting them to (4) HP DL580G2 servers running Windows 2000 Advanced Server, SP4. 580s have (2) Compaq FCA2101 2GB HBAs each, running driver 5.4.82.16. Multipathed using Compaq SecurePath V4.0c. Connected through (2) redundant Compaq Fibre Channel SAN Switch 16's, firmware V2.6.1c. No database or application hosting. Pure file shares. Okay, now to my question. Does Compaq publish a recommended volume maintenance schedule for a similar environment? Defrag, file cleanup, etc.? Is it best practice to use the default Windoes defrag program, or does Compaq recommend a third party utility? I'm currently dumping cookies, temp Internet files before running backups, but that's about it.

If anyone has any problems, please let me know.

I am concerned about the "Stop" error on the MSA device. The error text reads:
"Unexpected Win32 error encountered during I/O scanning: 317"
Details:
Event ID: 0x800040A/53
Context ID: 2
Detail Level: Normal/8

Prior to corrections to the library configuration (remove the router AF LUN to prevent scanning error using STORport driver):
"This device has been hot-swapped: the old driver may not work fo rthe new device"

Additional error in L&TT scan (note spelling error!)
"Redunant device listing. Device P56350HX3SR020 listed with paths 2/0.0.1 and 2/0.0.2."
This is reflected in the server registry HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 2\Scsi Bus 0\Target Id 0\Logical Unit Id 1
Is this a concern, on an artifact of how Windows registers two SCSI LUN targets from the same SAN device?

Additional error from the SAN switch config:
Device entry as Unknown(initiator/target) results in it not being included in a zone (though the zone config includes the port)

Additional error in the Windows Device Manager:
Under System Devices is an entry for "StorageWorks MSA1000/1500" with the error "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"

Where to I attack this issue? Presumably, the fact that MSA is not detected correctly by the SAN switch is the root of the problem. How do I correct this?
This is part of an ongoing issue with the SAN configuration and Symantec BackupExec 10.1(d) errors.

Thanks for any assistance,
Barnaby Arnott
Gen-i Senior Engineer
Client: SDHB
Configuration: HP DL360 G4p Windows Server 2003 SP1 with hotfix 908980
FCA2214 STORport v9.0.1.18 - SAN switch port 1
MSL6060 through NSR E1200 - SAN switch port 3
MSA1500cs - SAN switch port 0

HP StorageWorks SAN switch 2/8
Zones: Port 1 and Port 0
Port 1 and Port 3
No other devices connected.

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