Cannot see MSA1000 under HP-UX

[mclmicha_1]

Hello all,

have a MSA1000 which I want to connect to a HP-UX system.
But my HP-UX system cannot see the MSA1000.
Have a A6795A FC Interface in my rx2600 running HP-UX 11.23. This interface is direct connect to a MSA1000 which have the special HP-UX Firmware 4.38. The MSA1000 has two LUNs.

When doing a "ioscan -fn" I only see the A6795A FC interface but not the MSA1000.

Can anybody helps me ?


Thanks in advance

Michael Kurz
MCL GmbH

[melvyn burnard]

I am not sure of this, but I seem to recall that it may take one or two reboots AFTER creating the Lun's to force HP-UX to actually see the LUN's presented by an MSA1000.
Just a thought

[mclmicha_1]

Hope this answer will shown correct.


Thanks for your answer.

Have made several reboots also have added some HP patches, but still no success.

Michael

[Victor Fridyev]

Hi,

Sorry for the stupid question, but are you sure that your FC cablaes are good ?
Could you check them somehow ? Or to replace ?

[mclmicha_1]

Victor,

not really a stupid question. Have already think about this.
But when connectin the MSA1000 on a Windows Server everything works fine.
Also the connection LED's on the MSA and A6795A FC card tell me that the connection is OK.
Have changed in the meantime the A6795A, but with no success.


Michael

[Shaikh Imran]

hi,
What does
#fcmsutil /dev/td0 OR #fcmsutil /dev/td1
Displays ?

Also check for more details using fcmsutil
(see man fcmsutil)

[Naveej.K.A]

Hi michael,

Is there any way of defining the port behaviour (OS type) on the MSA 1000 as see in Virtual arrays.??

if yes, have you set that to HPUX

with best wishes
Naveej

[Shaikh Imran]

Hi,
Also Are the drivers of the FC card properly installed and also are the required patches for the FC card loaded.

Regards,

[mclmicha_1]

Hello Shaikh,
hello Naveej,

yes you can config a "HP profile" on the msa1000, which I have already done.

The "fcmsutil /dev/td0" shows everything normal, but when doing "fcmsutil /dev/td0 get remote all" I got a failure "No device found".
So it seems, that the A6795A cannot see the msa1000.
When going to the msa1000 to the serial CLI interface and typing "show connections" I see the A6795A and its address.
Have checked the ACL on the msa1000, but there is no difference when disable ACL (that means all have access to all LUN) or when just enabling the rx2600 to all LUN.

Have also tried to connect a C3000 with 11.11 to the msa1000, but it is the same behaviour as the rx2600

Michael

[Shaikh Imran]

Hi,
That's the reason i was asking you about the
Driver and the patches for the driver.
I think it's time to look into
1) O.S. Patch version
2) Card Driver version
3) Required patches for the card.
4) check for
fcT1_fcp
fcT1_cntl
fcT1
fcp
fcparray
All these drivers in kernel.
OR
Also try resinstalling the driver again.

Is the card driver release >= B.11.23.01 OR
B.11.23.02

+++++++++++++++++++++++++++++++++++++++++++++
SOME USEFUL TIP FOR
A6795A card on IPF systems.
The drvcfg utility is an EFI shell command that can be used to set the Device Scanning Policy in the Fibre Channel EFI driver.
The -s option for the drvconfig ulitity provides two enumeration policy options for Fibre Channel, 0 and 1. With this setting, the Fibre Channel driver only scans devices that are in the current boot order list in NVRAM. If option 1 is selected, the Fibre Channel driver scans all of the devices connected to the Fibre Channel cards installed on the system1.

For more information on using the drvcfg utility, please type help drvcfg at the EFI shell prompt.

To Get the EFI prompt
Place the system cd containing the diagnostic/utility software in the CD-ROM drive.

Boot the system to the EFI Shell.
You will get a prompt like
SHELL>
Use help drvcfg


Regards,

[Ted Buis]

Current support appears to be single path, single controller only for HP-UX 11.23, but it appears to me that you may need SecurePath 3.0c or 3.0d is still needed even though the multipathing is not supported. EFI firmware 1.10 is needed. The A6795A needs version 11.23.01. Use fcmsutil to get the WWN. There is some information on "finding" missing LUNs on page 45 and forward at:
http://h200005.www2.hp.com/bc/docs/support/SupportManual/c00059254/c00059254.pdf

[mclmicha_1]

Hi folks,

thanks very much for your tips.

My FC Channel driver version is B.11.23.01.
Also hat set the Option 1 in drvcfg in the EVI shell. Now I see at booting that the scan also scans FC devices, but neither in this scan nor in the ioscan he will see the MSA.

Have a direct attached single server config (server direct to the MSA), so think not need the secure path software.

Will now try to get the newest A6795A SW and try to reinstall it.


Regards

Michael

[mclmicha_1]

I am really frustraded.

Have added the fc scan with drvcfg in the EVI shell. Now I see in the EVI shell the WWN of the MSA. So looks like the EVI shell can see the MSA1000.
Wenn testing the connection in HP-UX with "fcmsutil /dev/td0 get remote all" I get a "No device found" error.

Already have installed the newest SW driver (B 11.23.02) and the newest EVI driver (1.10) for the A6795A.

Is there any config file for the A6795A ?


Regards

Michael

[Ted Buis]

I am trying to confirm if secure path is required, however, since you have a new server, did you get phone in support from HP with it? If you are not sure, then look on your order for part numbers starting with HA, let me know the parts and I can tell you what you purchased. The Response Center number for those with a support contract is 800-633-3600.

[mclmicha_1]

Hi All,

it works.

The secret is the hard address at the MSA.
After enabling and setting the "this_controller_hard_address" at the CLI> promt (I configuring the MSA via the serial interface) and reseting both systems the "ioscan" can see the MSA units.

Look have set this address following.

CLI> show this_controller_hard_address
Hard Addressing is enabled.
Loop ID = 1, AL-PA = 0xE8

CLI>

No idea for what this is, but it works.


One again thanks very much for the help of all of you.

Regards from Germany


Michael

[Ted Buis]

Very glad you were successful and shared the results. I have confirmed that SecurePath is not required, in fact it won't work. The web page the led me to thing that SecurePath would work with the current release is going to be corrected.

[mclmicha_1]

Ted,

it looks that with the MSA built in ACL's you can manage which server can see which UNIT/LUN.

May next week I find some time to try some thinks.

Have a nice weekend.


Michael

[Ted Buis]

Yes, the MSA1000 can mask LUNs. Hopefully, in 2005 there will be full dual controller support with SecurePath, but it is not there today.

[Uwe Zessin]

Michael,

you apparently have a Fibre Channel Arbitrated Loop (FC_AL) environment. The addresses in such a loop are usually dynamically negotiated during loop initialization = soft addressing. There is a special phase during re-initialization of the loop when each node tries to keep its original address, but it is not guaranteed and it can change after a power cycle. 'hard addressing' assigns a fixed address for the FC port. This also helps some operations systems which do persistent binding based on the AL_PA.