3G SAS switch to MDS600 unable to connect due to SSA70 path failure

[christopherrmilton]

We are having trouble connecting our MDS600 to the 3G SAS switch c7000 in a single domain setup. We are getting the following errors. We have viewed all of the documentation and are unable to find any references to this error. Does anyone have any ideas?


=> switch local show config detail
...
Storage Enclosure: 50014380027D1700, PortBox=31:1 (Degraded)
Storage Type: SSA 70
Bay Count: 0
Box: 1
Port: 31
Degraded Status Reason: Path Failure
Model: SSA 70
Zoning Capable: False
High Performance Connection: enabled
Storage Enclosure Environmental Status: Unavailable
Storage Enclosure: 50014380027D1D80, PortBox=33:1 (Degraded)
Storage Type: SSA 70
Bay Count: 0
Box: 1
Port: 33
Degraded Status Reason: Path Failure
Model: SSA 70
Zoning Capable: False
High Performance Connection: enabled
Storage Enclosure Environmental Status: Unavailable

[MattAddy]

I am also having the same problem also using a 3G SAS switch to MDS600. Did you find anything out yet? I am in contact with HP support and have updated all firwamre to the most current with no changes. rebooted everything, still no go.

Device Information
Model MDS600
Connected Expander expander 1
Bay Count 35
Box Number 1
Firmware Version 2.66
High Performance Connection disabled
Degraded Reason Path Failure
Switch Port 51
Vendor ID HP
Zoning Capable True
Status Degraded

[gregersenj]

Have you cabled correctly?
Have you zoned the MDS?

I have no knowledge on the SSA 70.

But I have setup a system with P700m.

If you got a FW ver.1.xx on the SAS switch, it can't be zoned.
If you got a FW ver. 2.xx It must be zoned.

Also you must have the minimum FW rev. on the MDS for the ver. 2.xx to communcate with the MDS.

Once the MDS and SAS switches is at the minimum FW levels.
You must Zone the MDS, and assign the zones to the appropriate server(s)

The Zoning is done on the SAS switch.

BR
/jag

[christopherrmilton]

yes, it is cabled according to the documenation and I'm using the P700m Controller. http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01956983/c01956983.pdf

Yes, we created the zone. But the problem occurs immediately during start up. In the Virtual SAS Manager, I get the following alert on HP 3G SAS Blade Switch 5: VSM Active: Code 452 Storage Enclosure at Port:51 Box:1 is degraded because of a path failure.

The firmware on the 3G SAS Blade is 2.2.4.0 and the firmware on the MDS600 is 1.42. I'm unable to upgrade the firmware on the MDS600 because it says the path is degraded. I tried downgrading the firmware on the SAS and I still was unable to connect to the MDS600 for firmware upgrade.

[gregersenj]

"The firmware on the 3G SAS Blade is 2.2.4.0 and the firmware on the MDS600 is 1.42."
Here's the Reason for your problem

I had to follow the instructions below:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=3239462&prodTypeId=329290&objectID=c01909417

You might have to do the same.

BR
/jag

[gregersenj]

To save you some sweat.

This is not an exact how to. You will need to read the abaove links.

Read it before you read this.

I did this in dec 09/jan 10.
Using FW CD 8.60.

Download FW CD 8.60
Create FW CD on an USB memory stick.

Download 2.54 FW for the MDS (See Link)
Copy fw fw1244.scexe into the \compaq\swpackages folder.

Download Switch FW 1.1.8.xx

Depending on you configuration
Chhose how to do it.

If you got a C7000 and a SAS switch in IC Bay 3 and 4.
Remove the switch in bay 3.
Connect all cables to the swictch in bay 4.
Downgrade the switch to 1.1.8.x

Boot a blade with a Smart Array ctrl (Not the onboard)on the USb mem.
Enter debug mode - At the first screen hold down the CTRL key, and enter D B X
waite a few seconds and you get a Linux command prompt.

Change to the swpacakes folder
\opt\bootdev\compaq\swpackages
Enter the following command
sh FWfile.scexe
Then follow screen
Once the MDS has been upgraded to 2.54.
You can upgrade the SAS switch again.
Remove the switch.
Put switch 3 back
put switch 4 back
connect all cables correctly.

Usinge the SAS switch manager.
Upgrade MDS to 2.66
Upgrade SAS switches to latest.

Don't try to be a wiseguy, it might punish you.

BR
/jag
A

[Elox]

christopherrmilton,

Did you solve this problem? I'm currently having the same problem myself.

[gregersenj]

have you read the link I postet
Aug 17, 2010 08:22:13 GMT ?

That did the trick for me.

BR
/jag

[Elox]

Yes, when i run the update in debug it says no devices were updated. It pretty much ignores the storage enclosure.

[christopherrmilton]

Actually, we ended up configuring for dual domain setup and the I/O modules we had didn't support dual domain. Also, the HP engineer tried to upgrade the firmware by connecting to a SAS port on a Proliant server. This also wasn't successful for us but worth trying if you have an available Proliant with SAS port.

[Elox]

Yeah, I already did that, went and bought a P411 to try with a ML350G5. Same result as you, unsuccessful.

The enclosure doesn't seem to care if it's dual or single domain. The system still identifies itself as "ssa70" and not a mds600. Also shows firmware version 2.58 which is not listed on the website anywere. I belive I might have a inhouse or pulled firmware.

I have a case with 2nd line at the moment, but I have little faith that they will be able to solve it for me. Hopefully the warranty might hold for a new pair of controllers.

[gregersenj]

Elox

The SAS switch's must be down graded to a ver. 1.xxxx FW, for the MDS to be upgraded to 2.5x fw.

BR
/jag

[Michael Bunker]

Elox and Christopher,
The SSA70 is an IO module for a different product that is not supported by the 3G SAS Switch. This IO has an older chip that doesn't support SAS zoning. You will need to replace the IO modules with MDS600 IO modules. Where did the old SSA70 IO's come from?

[Are Romøren]

> Boot a blade with a Smart Array ctrl (Not the onboard)on the USb mem.
Enter debug mode - At the first screen hold down the CTRL key, and enter D B X
waite a few seconds and you get a Linux command prompt.

Just out of curiousity - how was the connection between blade and MDS600 achieved? I'm struggling with the same issues as OP.

[drolfe]

---

@Michael Bunker wrote:
Elox and Christopher,
The SSA70 is an IO module for a different product that is not supported by the 3G SAS Switch. This IO has an older chip that doesn't support SAS zoning. You will need to replace the IO modules with MDS600 IO modules. Where did the old SSA70 IO's come from?

---

HI,

Hi,

Can you confim this, as I"m having the exact same issue and HP isn't sure if the SSA70 is the same as the MDS600 or not ?

Regards, Daniel

[tomas lovato]

I too am having the exact same issue. Purchased a MDS600/SSA70 and trying to plug it into a c7000 chassis with 3G sas switches in slots 5/6. Nothing I can do will clear up the "Path Falure" issue. I dont see any way to upgrade the firmware on the controllers themselves, just the switches. I tried downgrading and no further options became available.

Why is it that if I search HP's website for SS70, nothing comes up? whats the real model number? Is there a part number for the MDS600 controllers somewhere lurking around? One of the documents I saw mention ordering part#AP763A to get dual domain ability. I assume thats the controler for the 600 vs the 70?

The one photo i found of that part number shows red handles instead of bare metal ones. Is that a clue as to what the different is? Maybe the MSA70 only supports direct connect systems or something? or the controllers are limited.

If on my switch webpage I look at "Maintain->VSM Active->System log" there is a line refering to  -Expander (Addr: 50014380027AF080, Enclosure Logical identifier: 50014380027AF080, VendorID: HP      , ProductID: SSA 70          , #Phys: 36, Zoning enabled: false, bZoneLocked: false, bPhysicalPresenceAsserted: false, hasChanged: false)

If on my switch webpage I look at "Maintain->VSM Active->More Infomation" there is a line refering to  the enclosure "SSA 70" with a firm ware of 2.66.

Ive seen some info that  gregersenj posted in another thread, but it doesnt seem to be working for the folks that tried it....

[drolfe]

HI, Tomas,

I have anopther forum thread opened for this same issue, in my thread I have many screen shots, I have pictures of my SSA70 front and back and also a picture of the io module PN.

Hp-6g-BL-Sas-switch-can-t-see-MDS600

Let me know if your hardware is the same is mine

Regards, Daniel