MSA1500 cs with and MSA30 and MSA20 connected.....

[Girardy]

Hi,
I have a blade center connected to a SAN through 2 SAN Switches.
My controller is an MSA 1500cs and I have 2 chassis connected to it.
I have just updated my firmwares with the latest version (6.86 for the MSA1500cs and 5.20 for the MSA20). This is supposed to give me an active/active configuration.
I have restarted my servers and it's asking me for a COMPAQ MSA CONTROLLER SCSI Array Device driver that I cannot find anywhere on the Support CD v 7.57 or on HP's site....
This doesn't bother the servers to use their respective SAN volumes but I cannot use ACU to manage the volumes as it doesn't see the MSA controller.
Of course, I have updated all the drivers and Bios and installed PSP 7.51....
My servers are using Windows Server 2003 SP1 US version and up-to-date to the latest patches.

I really don't know what to do.
Can anyone help me please ?

Thanks
See the atached file to illustrate what I say.

[Girardy]

I have to precise that I don't have any zoning on my switches and before the firmware upgrade, I didn't have any problem to see the controllers.... apart the crashes problems and constant I2C problems..... Which I really hope this firmware upgrade will definitely solve

[Girardy]

And I also updated MPIO with the one provided on the ISO CD v7.57

[John Kufrovich · Accepted solution]

Girardy,

Set your host profile. Since ACU can't see the system you will need to use the cli cable.

[John Kufrovich]

If you set SSP and used the "default" setting for the HOST profile then you will see this problem.

Using CLI, set you host profile to the appropriate OS. With A/A, default is no longer windows default.

The only other way around the problem is back rev your controller and reset your SSP host profile, then go back to windows

[Girardy]

OK, I see what you mean... what are the commands I have to pass to change the profile via the CLI interface ??



Thanks

[Uwe Zessin]

> ADD CONNECTION con_name WWPN=.... PROFILE=...

You can check with:

> SHOW CONNECTIONS

[Girardy]

Thanks all for your help.
It worked.
I'm really happy to see there are people that are still willing to help.

Thanks again

[SysAdminGuy]

Please can you confirm a few things for me from this post.

You mentioned a CLI cable. Does this mean using a laptop and connecting directly into the MSA1500 controller I/O port.

For the command below please can you explain what a profile is. When we run the command from the ACU CLI and show SSP it looks if the profile is set correctly and the on our setup we have the Connection Name and Host Mode set correctly for a single configured device.


In the ACU CLI install on the host server the following commands do not work. What is the proper syntax?

"ADD CONNECTION con_name WWPN=.... PROFILE=...

You can check with:

> SHOW CONNECTIONS "

[Uwe Zessin]

You can use a laptop or any server that has a teminal emulator installed. I try to make sure that 'HyperTerm' is installed on all servers.

About the connection profile:
many operating systems have their own idea what answer they expect from a storage array in certain, specific situations like failovers. The profile is a bitmask which tells the controller software what OS is behind a specific WWN and how to act properly. Do a:
CLI> show profile
and I am sure you will get an idea.

About the ACU CLI: I am sorry, but I have not worked with it yet. I hope somebody else can help.

[Girardy]

Hi,
As told before, I used the CLI cable and SecureCRT with a telnet connection to the MSA1500 controller.

The correct syntax that worked for me was :
1) show connections
2) modify connection ...

I'll tell you tomorrow exactly what I did because I cannot remember right now but I didn't add, I modified the already created connections to set the profile to the desired OS (in my case : Windows)

[Uwe Zessin]

That works if you have named connections, but new connections are called "". You can pretend to use "ADD CONNECTION" to 'give them' a name.

[Girardy]

I do agree with you but my problem was after the firmware update on an already running and configured MSA.
By not setting the profile type, I wasn't able to configure my MSA anymore and it was seen by the ACU at all.

[LashesBB]

I had the same problem and setting the profile name resolved he MPIO issue but it is still asking me for the device drivers for the MSA1500. Everything is working fine but I have 2 qustions marks in the other devices of device manager. How do I resolve this?

[Girardy]

Hi,
Once I have set up the profiles used for the connections, I didn't have any problem with the driver.
Can you tell me what OS you have please ?
It doesn't ask for any driver after being able to see the MSA1500 cs.
I'll check tomorrow but I don't remember of any driver I had to install.

[John Kufrovich]

Use the MSA CD 7.57 and install the "Event Notification driver"

[RayB_1]

What does host profile have to do with managing a MSA1500 with ACU.

Did something change in 6.86?

Never needed to present disks in 5.xx or set host profile to manage a MSA1500 with ACU.



/ray

[RayB_1]

Found what I was looking for in upgrade manual.

For existing MSA, do not perform a firmware update until you have confirmed that the â host modeâ or â profileâ for each connection is correctly set. The host mode identifies the operating system of each
HBA connection to the storage. Do not use the â defaultâ setting.