msa1000 with an msa30 dual bus causes msa lockup

[BrendanB]

Hey all,
I have an msa1000 running:
MSA1000 Firmware Revision: 6.86b1 (8A1BJN71W050CB)
MSA1000 Hardware Revision: 7 [AutoRev: 0x010000]
Fibre Module AutoRev: 0x000001
Box 1a PROLIANT 4L7I DB Rev: 1.86 (8A1BJN71W050)
Box 1b PROLIANT 4L7I DT Rev: 1.86 (8A1BJN71W050)

and an msa30 with a dual bus scsi io module

When i plug in both channels to the msa it causes a lockup in the firmware
but if i plug 1 channel in on the msa30 it works fine.

I've tried the following configurations with both the msa1000 and msa30 off with all drives out:
msa1000 channel A -> msa30 channel A
msa1000 channel B -> msa30 channel B

msa1000 channel A -> msa30 channel B
msa1000 channel B -> msa30 channel A

If i try just one channel in all those configurations it works fine


Any ideas?

[IBaltay]

Hi,
the only visible strange thing in your configuration is that you have dual controller config with 2 different firmware versions:
in normal conditions the 2 different firmware versions are compared each time the system is powered off/restarted or if a 2nd controller is hot plugged. If the firmware versions are different, the controller LCD panel prompts to clone the firmware to have the same versions:
the rules are the following:
a) if the system was powered on with both controllers inserted, the most recent firmware version will be applied/cloned regardless of which controller it is on
b) if the 2nd controller is hot plugged, then the version of the original (1st) controller is used for clonning regardless of its version

then it starts the cloning and it is displayed on the controller LCD panel as follows:
rom clonning started
array controller restarting
startup complete

The question is, why it does not work in your dual MSA 1000 configuration and maybe the manual upgrade to the v7.0 should be applied

[BrendanB]

Hi Thanks for the quick response,

Sorry but i cant see where it mentions that the firmware is different on the two controllers?
i see a firmware and a hardware revision?

[IBaltay]

Ok, but can you check the firmware versions of both controllers pls to be sure?

[BrendanB]

CLI-1> show this_controller
Controller 1 (right controller):
MSA1000(c) Hewlett-Packard P56350GX3QK04M Version 6.86 Build 1 Hardware 7
Integrated Enclosure.
Controller Identifier:
NODE_ID = 500805F3-00003C50
SCSI_VERSION = SCSI-3
Supported Redundancy Mode: Active/Standby Asym-Active/Active
Current Redundancy Mode: Asym-Active/Active
Active/Standby Simulation DISABLED
Device Port SCSI address 6
Terminal speed for the CLI is set to 19200.
Host Port_1:
REPORTED PORT_ID 500805F3-00003C51
PORT_1_TOPOLOGY = F_Port
Cache:
64 megabyte read cache 64 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:
0 Days 22 Hours 59 Minutes 36 Seconds
Health:
Surface Scan: Complete.
Rebuild Status: Complete.
Expansion: Complete.


CLI-1> show other_controller
Controller 2 (left controller):
MSA1000(c) Hewlett-Packard P56350A9IMI01O Version 6.86 Build 1 Hardware 7
Integrated Enclosure.
Controller Identifier:
NODE_ID = 500805F3-00003C50
SCSI_VERSION = SCSI-3
Supported Redundancy Mode: Active/Standby Asym-Active/Active
Current Redundancy Mode: Asym-Active/Active
Active/Standby Simulation DISABLED
Device Port SCSI address 7
Terminal speed for the CLI is set to 19200.
Host Port_1:
REPORTED PORT_ID 500805F3-00003C59
PORT_1_TOPOLOGY = F_Port
Cache:
64 megabyte read cache 64 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:
0 Days 22 Hours 55 Minutes 51 Seconds
Health:
Surface Scan: Complete.
Rebuild Status: Complete.
Expansion: Complete.

[IBaltay]

can you also do the ADU pls? Array (diagnostic utility report)

[BrendanB]

how do i generate that from the msa?

[Uwe Zessin]

You need to execute ADU on an operating system.

It is also on the SmartStart CD-ROM, but my experience is that it almost always refuses to write the report to an attached USB stick.