MSA1000's only accessable from 1 Itanium server

[M.Boeijen]

We have two MSA1000's and 2 Itanium server (running HP-UX). The first server can access the MSA's (ioscan: device files are available). But on the second server the devices files aren't there.

Any idea how to diagnose this problem and/or what the cause is. It's my first MSA experience....

[M.Boeijen]

The server's and MSA1000 form a 2 node ServiceGuard cluster.

[Steven E. Protter]

Shalom,

Last I checked a firmware upgrade fixed that problem.

SEP

[YAQUB_1]

Hi,

Any SAN switch is there?

U can access MSA? if U can then paste the command output:-

CLI-1> show tech_support

BR/
Yaqub

[M.Boeijen]

The MSA firmware was updated from 4.48 to 5.2. (I'll post the tech_support on Monday)

[M.Boeijen]

I don't have the 'show tech_support' running 5.2 yet. But I realized that I saved the 'show tech_support' for 4.48. The output from SAN1 en SAN2 is attached.

I'm fairly new in the MSA section. My colleague defined a connection, and from that point on an ioscan on the first server showed the device files.

Later on the second server what added to the network. An ioscan shows the MSA as claimed, but no device files are shown.

PS please let me know if I also have to paste the 'show tech_support' output

[Khairy]

hi,

from the logs, i can conclude each server is connect to its own MSA1000 unit.

1st msa1000:
Connection WWPN Units
SAN1 50014380-017AFDB8 0

2nd msa1000:
Connection WWPN Units
SAN2 50014380-017AFDBA 0

The above output show the storage can only see an adapter.

This is strange unless MSA1000 doesn't has a switch installed and that may answers why only 1 server could access the storage. Means, all this while, each server is direct connect to MSA1000.

to allow both server to access the MSA's, you must have a san switch installed.

there could be several possible config for MSA1000 to be shared by 2 servers especially for service guard config.

Normal option is, a san switch and one FC HBA in each server. The FC HBA and the san switch are single point of failure.

server1, server2
-> san switch
-> msa1000 (san1)
-> msa1000 (san2)


Or maybe you could have 2 x FC hba with 2 separate san switch with each san switch is connected to both MSA1000.

Let us know more what you have there.

And output from `ioscan funC disk` and `ioscan -funC fc` would be good for a start.


Rgds

[Torsten.]

Did you already check the SSp (selective storage presentation) on the MSA?

[M.Boeijen]

Khairy, each MSA1000 has 1 SAN-switch. Both servers are connected to both switches. The fact that the MSA1000's are in the ioscan output of server2 we can conclude that server2 at least has a connection with both MSA's, right?!

Torsten, SSp? Should info about this be in the 'show tech_support'? If yes, the 'show tech_support' is attached in of of my replies. If not, I'll be happy to give more info, if you let me know which command/where.... (sorry, I'm new to the MSA's/switches and corresponding terminology).

I've attached the layout of servers/switches/MSA's with the FC connections.

A connection is created and this is used for server1. Should this connection also be available for server2, or does a new connection has to be configured?

[Torsten. · Accepted solution]

Some things I noticed from your show_tech_support:

>> SAN 1
Connection Name: SAN1
Host WWNN = 50014380-017AFDB9
Host WWPN = 50014380-017AFDB8
Profile Name = HP
Unit Offset = 0
Controller 1 Port 1 Status = Online

Connection Name:
Host WWNN = 50014380-017AFF9D
Host WWPN = 50014380-017AFF9C
Profile Name = Default
Unit Offset = 0
Controller 1 Port 1 Status = Offline

If you present a LUN to hp-ux, use ALWAYS the "HP" profile - never "default".

...


ACL is enabled:
Connection WWPN Units
SAN1 50014380-017AFDB8 0
Inaccessible Units: None


ACL (access control list = SSP for ACU)

SAN1 allows only access to
server HBA 50014380-017AFDB8

The other server is not allowed to see the LUN.


This is your problem!

Adjust the ACL and it will work.


(Same for SAN2)

[M.Boeijen]

This connection "" is the actual connection with server2, but with the wrong profile name ("Default" -> "HP")? Or does this connection have to be created manually? If you can give the commands/actions to 'fix' this that would be nice. But only if you don't have to do more analysis.

I 'll access to the MSA's on Monday to correct the config.

[Torsten.]

The most easy way to configure the array is to use a Proliant server running the ACU - but it is alos possible to configure via a serial line and the CLI.
See the manual for the CLI.

[M.Boeijen]

Thanks all for your help

[M.Boeijen]

We do have this /opt/compaq/hp../bmd/hp.. tool (don't know the name by heart) on the HP-UX Itanium server. This tool is used to connect to the local FC card?! Or I'm confused about this tool....

[Torsten.]

I remember there is a tool called "HPACUCLI" - but never worked with this.

IIRC this will do the CLI over FC instead of serial line.

[M.Boeijen]

I think that's the one. But running that from servers a "ctrl all show" results in something like:

error: no controllers

But I can imagine that this tools will work after the connection for server2 has been added first using the serial interface.

Again: thanks for your help.

[M.Boeijen]

Sorry for the typo, but running the "HPACUCLI" on server2 results in:

error: no controllers

On server1 actual controller info is show. But than again for this server a connection is configured.

This "HPACUCLI" has less avaliable functions/functionality than the serial CLI interface, right?

[Torsten.]

As mentioned before - I never worked with this.

You should use the online help or the readme file.

IMHO the HPACUCLI has the same functionality as the CLI , more or less.

Try for example:

> ctrl chassisname="SAN1" show ssp

[M.Boeijen]

The chassisname was not SAN1, but indeed it looks like the commands are available.

The MSA couldn't be accessed by the second server, because the proper 'rights' weren't configured.