HP DL585 and MSA1000 Problems

[Stephen Harmon]

I have an HP StorageWorks MSA1000. On the back of it I have an 8 port fiber switch. I am plugged into the first port of the fiber switch, which is then cabled to the HBA on my server. I have tried two different servers. An HP DL385 and DL585. With the SmartStart software (which I boot from CD), I can see and configure the MSA1000 from both servers. However, when I boot the Linux Operating System (SLES 11), I can only get the DL385 to connect.

On the DL385 I will do an "lsscsi" and see the SAN and devices (/dev/sda) I created on the SAN. On the DL585 I can't see anything but the dvdrom when doing an "lsscsi". I have tried swapping HBA's to see if that helps, but it didn't. When I stick the HBA from the DL585 to the DL385, it works fine there too (which it should because they are the same type of card).

They are both loading the ql2xxx driver. I am not sure where to go from here and didn't know if you had any pointers.

I guess I should also ask the question one last question. Do I have to do any special configuration from the SAN to allow additional machines to connect or should the SAN automatically take care of this?

Please let me know if I can provide more information to make this question easier.

Thanks,

-sdh

[Steven E. Protter]

Shalom,

1) If you install PSP for SLES, new drivers will be installed and you may see the SAN.

2) Could be a bad switch, contact HP hardware support for some help.

SEP

[Stephen Harmon]

Thanks for the information. What is the PSP for SLES? Is there an updated one for SLES 11?

The only question I have is both the DL385 and DL585 have the same version of SLES 11 and the same HBA. The DL385 can connect to the SAN, while the DL585 cannot. (as a matter of fact, I have tried multiple DL585's).

If I use the ports with the DL385, it can see the SAN, so it doesn't seem to be a problem with the switch. I don't have to assign LUN's to Servers or anything like that do I? Will the MSA1000 just allow any server to connect (if I have the right driver and hba)?

Thanks,

-sdh

[Stephen Harmon]

It looks like the new Proliant Support Pack for SLES 11 and the DL585 G6 came out on June 6. I applied the support pack but these DL585's still can't access the SAN (MSA1000).

I have also tried multiple ports in the switch with the server (DL 385) that can access this SAN, so it doesn't seem to be a switch problem.

On the SAN I have SSP (Selective Storage Presentation) disabled. By disabling this option, doesn't this mean that any server can access the SAN and any LUN? At this point I could only think of it being a SAN misconfiguration or a driver problem.

Any help to proceed further would be appreciated.

Thanks,

-sdh

[Fayez]

to troubleshoot the problem, enable the SSP on the storage, and see if it can see all wwwn ports of your server.

[John McNulty_2]

If you don't have SSP enabled and there are other systems on the SAN that could see that disk, then possibly one of them has grabbed the disk and popped a SCSI Reservation on it which will effectively lock everyone else out.

Sounds to me like this is the mostly likely cause of your problem. Clearing the SCSI reservation maybe problematic. I would enable SSP, then delete that disk from the MSA, re-create it, present it to the host HBA(s) you want and then see if you can see it afterwards.

[Stephen Harmon]

I enabled SSP and all of the WWNN's are presented. I ended up downgrading the DL585-G2 machine from SLES 11 to SLES 10.2 and it could finally see the SAN. However, the DL385 with SLES 11 can see it just fine. The problem I am running into is that I need SLES 11 for the product I am using. I have the same HBA in the DL385 as I do in the DL585-G2. I'm not quite sure why it won't work. I tried the latest PSP (8.25) but that didn't help. Seems like the drivers are loading...

Thanks.

-SDH

[Steven E. Protter]

Shalom again,

PSP is commonly updated 3 months or so after a major SLES release.

If SLES 11 is over 3 months since release you should be able to find a PSP version that supports it.

SEP