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

[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.