Hi all.
I have an old dualcontroller MSA2012i with 2 encloseres.

System Information
------------------
Vendor Name      : HP StorageWorks
Product ID       : MSA2012i
Product Brand    : MSA Storage
SCSI Vendor ID   : HP
Enclosure Count  : 3

Controller A
------------
Serial Number           : 3CL925S477
Hardware Version        : LCA 56
CPLD Version            : 27
Cache Memory Size(MB)   : 1024
Host Channels           : 2
Host Bus Type           : iSCSI
Drive Channels          : 1
Drive Bus Type          : SAS

Controller B
------------
Serial Number           : 3CL818C412
Hardware Version        : LCA 56
CPLD Version            : 27
Cache Memory Size(MB)   : 1024
Host Channels           : 2
Host Bus Type           : iSCSI
Drive Channels          : 1
Drive Bus Type          : SAS

Controller A Versions
---------------------
Storage Controller CPU Type   : Celeron 566MHz
Storage Controller Firmware   : J212P01
Storage Controller Memory     : F300R22
Storage Controller Loader     : 15.010
Management Controller Firmware: W421R46
Management Controller Loader  : 12.013
Expander Controller Firmware  : 3218
CPLD Revision                 : 27
Hardware Revision             : LCA 56
Host Interface Module         : 50
Host Interface Module Model   : 2

Controller B Versions
---------------------
Storage Controller CPU Type   : Celeron 566MHz
Storage Controller Firmware   : J212P01
Storage Controller Memory     : F300R22
Storage Controller Loader     : 15.010
Management Controller Firmware: W421R46
Management Controller Loader  : 12.013
Expander Controller Firmware  : 3218
CPLD Revision                 : 27
Hardware Revision             : LCA 56
Host Interface Module         : 50
Host Interface Module Model   : 2

 I have planed sheduled maintanance and rebuild with full configuration reset.
Thus I shut down storage controllers and has powered him off.
After power on one of controllers is dissapeared.

I power off storage again and remove it from rack to my lab.

1. After assebly in lab I power on him but management network connection doesnt work to any modules.
   Im trying connect by console cable.

    Controller module A - doesnt answer.
    Controller module B - shows booting process, but CLI session hangs up after commands like:

• show versions
• show configuration

result for show versions was:

# show versions
Controller A Versions
---------------------
Storage Controller CPU Type   : No_data
Storage Controller Firmware   :
Storage Controller Memory     :
Storage Controller Loader     :
Management Controller Firmware:
Management Controller Loader  :
Expander Controller Firmware  : Not Ready
CPLD Revision                 :
Hardware Revision             :
Host Interface Module         :
Host Interface Module Model   :

Controller B Versions
---------------------
Storage Controller CPU Type   : No_data
Storage Controller Firmware   :
Storage Controller Memory     :
Storage Controller Loader     :
Management Controller Firmware:
Management Controller Loader  :
Expander Controller Firmware  : Not Ready
CPLD Revision                 :
Hardware Revision             :
Host Interface Module         :
Host Interface Module Model   :

or sometimes some strange like that: 

each time this output dlay from entering command to output very long - a few minutes.

If i enter show configuration - system hangs up finally.

If i enter restore defaults - system hangs up finally.

2. A also tried to change power supplys and place controller boards to other enclosures chasis.
   Still the same.

3. Have tried to flash controller by console cable:
   When A/B modeles installed - FW sending hangs up in a few seconds after start.
   When I remove module A and upload FW by console cable i got message

File received OK
SC code on MC processor.
FILE CORRUPT!
Hit <ENTER><ENTER> to continue.

I tried download FW for single controller array - the same. Aslo i have compred this FW (MC and SC - they are idenntical)

No more ideas. :(  Please help.

Hello, 

MSA2312i won't work with web interface.

SSH works.

After restart of both controllers with the CLI the issue occurs again (restart mc a / restart mc b)

Thank You.

Hello,

I am trying to access the latest firmware (GL220R005) for the MSA 2040 however the download link just takes me to the download for GL210R004 which is the older firmware I am already running.

I started on this page: http://h20565.www2.hpe.com/hpsc/swd/public/readIndex?sp4ts.oid=5442232&swLangOid=8&swEnvOid=4168

Then clicked "Obtain Software" next to the latest version.

Does anyone know the correct URL?

Thanks!

Hi All,

Trying an interesting project here and i'm trying to see if this is something that can work before attempting. 

We have an MSA2040 FC which we're trying to direct attach to and old alphaserver Rx3600.  Is there a compatible FC HBA out there capable of attaching these two together?  Is this even a thing that makes sense to try?  Would it be easier to use a fiber switch?

Thanks!

We had an issue with an aging P2000 MSA G3 with dual combo ICSCI/FC controllers in it. One of the controllers failed. The array has continued to operate normally on one controller (this controller b was running old firmware T201P02 from 2011). A replacement controller was sent. We were told it was downgraded to be close to the existing controller. Partner firmware update was disabled. The replacement controller was placed into slot A. It turns out its running T251R04-01 which is from 2014.

My understanding is that is could be a problem and that no controller with a f/w newer than TS250 should not be placed into the chassis. Currently since the controller running T251R04-01 was inserted it is flagging all the SFF drives in its associated chassis as having an unknown state. It also appears to be constantly rebooting the management controller in b (running T201P02).  Its showing controller B (old firmware) as unavailble on the network. However i was able to ssh into it. It appears that it cannot see anything other then itself. SHOW FRUS just returns nothing and SHOW SYSTEM only returns basic chassis information, most of which is not populated. However the ISCSI ports appear to be online and working so it is operating, just not communucating with anything else.

Can anyone tell me if its safe to enable partner firmware update and allow the new controller running T251R04-01  and allow it to update controller B running T201P02?

The alternative it to take everything down (All the connected hosts) and then power down the storage and remove the controller running T251R04-1 and get it downgraded to a closer firmware before re-inserting.

The main shelf also has 5 x D2700 SAS AJ941A enclosures on it,

I am seeing the following messages....

Error logs…(repeatedly)

 Enclosure event: fault. (enclosure: 1, WWN: 500c0ff0125XXXXX) I/O module A, I/O module status: The firmware version is not compatible, HP SPS-CHASSIS 2028

Warning logs… (repeatedly)

 2016-05-18 06:35:30 B6585 156

The Management Controller was restarted automatically by the Storage Controller for the purpose of error recovery.

2016-05-18 06:35:30 B6584 152

The Storage Controller is not receiving data from the Management Controller. (This is normal during firmware update.)

  Is this what you would expect to see if partner firmware update is off?

#
#
# show system (run from CONTROLLER-A - new firmware)
System Information
------------------
System Name: SXXXXX
System Contact: XX
System Location: XXXXX
System Information: HP P2000 G3 FC iSCSI Combo
Midplane Serial Number: 00XXXXXX
Vendor Name: HP
Product ID: P2000G3 FC/iSCSI
Product Brand: MSA Storage
SCSI Vendor ID: HP
SCSI Product ID: P2000G3 FC/iSCSI
Enclosure Count: 6
Health: Degraded
Health Reason: A subcomponent of this component is unhealthy.
Supported Locales: English (English), Spanish (español), French (français), German (Deutsch), Italian (italiano), Japanese (æ¥æ¬èª), Dutch (Nederlands), Chinese-Simplified (ç®ä½ä¸­æ), Chinese-Traditional (ç¹é«ä¸­æ), Korean (íêµ­ì´)

Unhealthy Component
-------------------
Component ID: Enclosure 1, Current Health: Degraded
Health Reason: The current sensor's status is unknown or its value is unexpected. It may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.16
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.6
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended act
Unhealthy Component
-------------------
Component ID: Disk 1.4
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.19
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.24
Health: Degraded Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.11
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.13
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.
Unhealthy Component
-------------------
Component ID: Disk 1.20
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.8
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.3
Health: Degraded
Health Reason: The disk in this sloane may be unhealthy. Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.18
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.12
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component -------------------
Component ID: Disk 1.1
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.7
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.21
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy. Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.9
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.17
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
------------------- Component ID: Disk 1.15
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.2
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.5
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in tponent and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.23
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.22
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.10 Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.14
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Enclosure 1, Controller B, Management Port
Health: Degraded
Health Reason: The network port Ethernet cable is unplugged, or the network is inoperable.
Health Recommendation: - Check that the controller network port is properly connected to the network. - If it is, then check for network problems.

Unhealthy Component
-------------------
Component ID: Enclosure 1, Temperature Loc: lower-IOM B
Health: Degraded
Health Reason: The temperature sensor's status is unknown or its value is unexpected. It may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Enclosure 1, Voltage 5V Loc: lower-IOM B
Health: Degraded
Health Reason: The voltage sensor's status is unknown or its value is unexpected. It may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Enclosure 1, Voltage Health: Degraded
Health Reason: The voltage sensor's status is unknown or its value is unexpected. It may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Success: Command completed successfully. (2016-05-18 07:53:08)

Any advice appreciated. thanks

Adam.

I am trying to add 11 new disks to my 2ed enclosure but when I plug them in they does not light up.

The enclusure is now filled with disks but is only showing the 14 that I had there before.

the disks is not responding physicaly or in the Storage Management Utility.

I have rescanned the disk chanels but there is no change.

Am I missing some thing?

Hello

Current SAN configuration: Cisco MDS FC switch with 32 ports as backbone, several Cisco MDS 8Gb Fabric Switchs for HP BladeSystem c-Class in NPV mode connected to backbone switch. Each blade switch has 2 or 4 ports in port channel group for connection to main switch.

Now I have to add C7000 with Brocade blade FC switches to existing fabrics.

That means that Brocade FC switch should be in AG mode which is simular to NPV mode.

Does anyone have experience with that? 

HPE is hosting an Online Storage Expert Day on June 29^th& 30th, 2016!  Mark this on your calendars!

What is an Online Expert Day? 

An Online Expert Day is an event where HPE Product Specialists, Consultants and other senior support team members join our online forums to answer your technical questions, even for products that are out of warranty. Online Expert Days give you a chance to talk directly to the HPE Experts!

What products are covered during the Storage Expert Day event?

• 3PAR StoreServ Storage
• StoreVirtual (LeftHand) Storage 
• StoreOnce (D2D) Systems
• StoreEver Tape Storage
• StoreFabric (SAN) portfolio

Why should you come to the HPE Storage Expert Day?

The Storage Expert Day gives you the best chance to interact with Product Experts @ HPE, whilst giving you an opportunity to learn more about your storage product.

We’ll share our knowledge in the best ways to:

• Troubleshoot a storage issue you are having;
• Address hardware and software compatibility issues;
• Answer queries on planning, installation, setup and configuration;
• Identify spare & option part numbers;
• Utilize diagnostic tools/utilities, understand error codes, interpret LEDs and analyze logs;
• Choose the right storage box, backup device/application or even add the right amount of storage space;
• Optimize your storage and fix other common problems.

Moreover, this event is touted as the “Super Bowl” of expert assistance, providing you access to an elite pool of internal and external product experts.

It doesn’t matter how old the Storage Device is or what it is connected to, we will do our best to help. 

How does the Online Expert Day event work?  

Starting on June 29, 2016 7am EDT / 12pm GMT, log on to the HPE Storage Forum and create new posts to ask your questions.

The Online Expert Day will end on June 30th, 2016 at 7am EDT / 12pm GMT. 

HPE Experts will be online in the forum and will do their best to answer your queries. They may need to get some more information from you, so please check the box "email me when someone replies". 

An online conversation will be born!

 If you need assistance using the forums, there are tips and tricks here.

Hi

When using replication on MSA 2040, I have configured the iSCSI ports on both controllers.I have the replication link setup on controller A.  For redundancy how do I configure  the ports on both controllers for failover?

Thanks

D

Hi!

HP P2000G3 FC/iSCSI DualController SFF

After firmware upgrade from old TS201P007 to merged version TS230P008 (and new TS250P003, TS251R004 and current TS252P001) i can't define the Explicit Mappings. Only Default Mappings.

I select volume, choose Provisioning -> Explicit Mappings... and see only Default Mappings.

In old TS201P007 version i used Explicit Mappings successfully.

I tried to downgrade firmware, but i can't downgrade to merged-befor version: only to TS230P008.

Whats wrong? How define Explicit Mappings now? Maybe it become the lisensed feature now?

Thanks

^{Hi all,}

^{I am trying to get my MSA 2040 into SCVMM.}

^{I'm using domain admin credentials, MSA credentials, Local Admin Cedentials on the SCVMM host, Trying the IP address and host name of Controllers A or B of the MSA. 
I've also tried the above with SMI-S WMI WMI and SMI-S CIMXML.}

^{I dont have the error message to hand right now.} 

^{Does anyone have any pointers for me at all?}

^Thankyou.

Hello and thanks for this excellent forum!

I am helping in the management of an HP MSA P2000 SAN and have an issue with one of the vDisks.

This vDisk is configured in a RAID 6 and recently lost one of its disks.  We contactly a widely known hardware reseller and obtained a replacement disk for it that was deemed compatible by the reseller.

When I removed the bad disk and inserted the new disk, I logged into the SMU and saw that the RAID was rebuilding.  Knowing that this usually takes some time, I logged off and made a note to check on it the next day.

Well, my counterpart notified me that the drive had not turned green the next day and when I logged into the SMU, the vDisk is still showing as a "Degraded" state.  Also, now the drive which is inserted into Controller 1, Slot 10 is now missing and not showing up as an available drive any longer.

I have attached a screenshot of the error log from the rebuild process.  You can see clearly on there that the rebuild did encounter an error, but I don't know what to do next and certainly don't want to continue running in a degraded state.

Thanks in advance for any support that you can provide.  See attached JPG for the error/warning log.

Hello,

We have a MSA P2000 G3, we had tried to upgrade the firmware from 100 to 250 without following the recomended sequence (100 -> 201 -> 230 -> 250 -> 252), so we get an error showen that one controller is updated and the second one not. we had lost 4 VDISK and all its disks are now available. It is possible to rebuild the vdisk whitout formating disks and wer wehen we reboot both controller, our data can be available? If not, what solution can we use to recover data?

Thanks

SAN model: MSA1500CS

Firmware: 5.20 (A/P)

ACU Version :9.40.12.0

Latest Qlogix HBA driver.

I added four new 146GB HP drives (which are identical to the existing) to the Bay.

They showed up on the ACU without any hassle.

And new array was created using two drives smoothly .

AND NOW THE ISSUE!!!

When i try to create a new logical drive, it throws an error: "The operation has failed with the following code: NO_DRIVES"

It is mind boggling! 

I also tried creating the logical disk through ACUCLI but i also got an error.

Tried switching up disks, but it seems it doesn't want to create a new logical disk at all.

Also disabled caching but to no avail .

Now this is where I am stuck at now.

Any help or questions would be greatly appreciated.

Hi,

Can anyone tell me what might the best RPO be expected when using MSA replication between two MSA 2040 arrays.

Then documentation states that the replication can be scheduled at a minimum of 60 minutes, can this be reduced in any way to say 30 or 15Mins?

We are considering implementing MSAs in our environment but the  replication RPO may be a deciding factor.

Thanks in advance,

D

I have an old MSA 1000 that I used to manage on a Windows Server 2003.  The MSA is still solid, but I want to manage it from Windows Server 2008.  However, I am not able to find the management software that will install on a 2008 Windows Server.  Anyone know if the managment software is available for 2008 Server?

Hi everybody,

I´m no expert in Atalla products and I have a problem... I need load a test VISA key into my Test Atalla and I dont know which is the way to do that... could you please help me with this issue?.

Thanks in advance.

Rene

Hey,

We have 3 p2000 arrays in our environment. I have noticed all of them are in constant cycle of scrubbing the vdisks.

Is this normal, or indicative of an issue?

Hello,

as the title says, i want to upgrade my MSA 2012fc G1 Storage to something new. Sinze i don't have good use for something like a 3PAR, i want to stay with goold old MSA. The latest generation MSA2040/1040 seems to be a good choice for me.

But i like to have a few questions answerd before i throw my money at HP and i hope you can help me out :)

1) The MSA series semms to have a high compatibility between all the different generations of chassis. For instance an MSA P2000 can upgraded to an MSA 2040 just by changing the controller(s). The only downside is that SSD’s are not supportet in this case.
So is it possible to add an MSA2040 Controller to an MSA G1 chassis?

2) If i decide to replace the whole MSA G1, is it possible to move all the harddrives to the new chassis without loosing any volumes/data?

3) Can i attach an MSA 2040 to an MSA G1 or vice versa as expansion (with SAS connection) to use both?

My last question is kinda a noob one, but i didnt found any reliable source :) The MSA 2012fc G1 is attached to an 4Gb fc switch. Sinze MSA 2040 has an 16Gb / 8Gb fc connectors, do i need to upgrade my fc switch to at least 8Gb?

I have a P2000 LFF Storage Enclosure with a pair of iSCSI controllers installed. The controllers are p/n BK829A

I want to verify, firstly, that I can attach these three enclosures by SAS in a supported configuration:

1x P2000 LFF p/n AP844B

2x D2700 SFF p/n AJ941A

...such that the full "stack" of disk enclosures will look like this:

P2000 - BK829A - 12x LFF 300GB 6G SAS 15k

P2000 Enclosure - AP844B - 12x LFF 300GB 6G SAS 15k

D2700 Enclosure - AJ941A - 25x SFF 300GB 6G SAS 15k

D2700 Enclosure - AJ941A - 25x SFF 300GB 6G SAS 15k

Secondly, assuming that all drives are equal in capacity (300gb) and spindle speed (15k) but not of the same form factor (LFF/SFF) I want to know if it is possible to construct a single RAID10 logical drive from ALL of the drives across the four enclosures, including one or two hot spares in the array. In other words, is there are any restriction here that will prevent me from constructing a logical array using physical drives that differ only in form factor?

Thirdly, I am seeking to verify that this particular stack of hardware is "6G" bandwidth from top to bottom. 

Fourthly, I am seeking to verify that I can use with this stack, a SAS cabling configuration consistent with the dual-port "performance" cabling configuration specified by the HP D2700 cabling guide. I would like to know that the BK829A controllers at the top of the stack support this configuration.

I am intending to use this stack as a secondary storage tier for VMWARE Replication. (I use NIMBLE for primary storage). What I am hoping to do with this stack is to construct a 72-disk RAID 10 array with a couple of hot spares. Speed is important, reliability (relatively) less so. 

I appreciate any feedback or observations in addition to any specific answers to the above questions.

Many thanks.