fcmsutil : Target port is in invalid state

[Eric SAUBIGNAC]

Bonsoir,

Got a strange behavior on a BL860c and BL870c, hp-ux 11.31 March 2008 on each, latest patches from swainv installed.

When I issue a command like "fcmsutil /dev/fcd0 get remote all" I get a normal output (see attached file). When I do the same command on a specific N_Port_id, choosen from previous output, I get an erreor like "Target port is in invalid state".

I have searched for a similar issue in forums, for a patch in HP database, but I found nothing. My problem is that I have some administration scripts based on this and theu no more work :-(

Any idea ?

Eric

[OFC_EDM]

Not sure. This is just a guess but did you check the state of the port on the switch?

[Eric SAUBIGNAC]

Kevin,

Switchs are embedded in C7000. Just did a check, and don't know why, but the HP-UX ports were in a "persistent disabled" state.

Though all hp-ux ports were disabled, I don't understand why hp-ux box were still able to access the EVA ???

Anyway, modifying to "persistent enable" has changed nothing. I did a reboot of one box with same result : "get remote all" is OK but "get remote" on a specific N_Port_id is still bad

Eric

[OFC_EDM]

Which type of switches are you using?
Which model of EVA?

[Eric SAUBIGNAC]

EVA 4100, version 6.110, and embedded switch in C7000 : AE370A "San Brocade 4/12 BS C-Class", version 6.0.0.b

Eric

[Fabio Ettore]

Hi Eric,

I have a system with target port status DVS_READY that I think it should be the normal status, infact fcmsutil get remote does reply a good result. Instead in your case you have target port status DSM_READY.

Definitely I suppose that the message "Target port is in invalid state" is expected when having status port DSM_READY. Maybe you should investigate about why the target status port is DSM_READY and not DVS_READY. Take a look at the following document:

http://docs.hp.com/en/A6795-90007/ch01s09.html

It sounds like you have to see DVS_READY but unfortunately I don't know the exact meaning though :-( I can only suppose that.

Anyway I think that should be the way to continue about this problem.

Hope this helps you.

Best regards,
Fabio

[Torsten.]

I'm not sure about this, but I would check if any vdisk is NOT presented in hp-ux mode.

[Eric SAUBIGNAC]

Fabio : very clever remark with DVS_READY vs DSM_READY. But unfortunately I don't know how to deal with it :-( Also did not find explanation of that at the URL you gave.

Torsten : good idea, but corresponding hosts are correctly configured at EVA level with "Hewlett-Packard HP-UX" type :-(

Eric

[Fabio Ettore]

Hi Eric,

yes, that link was just to show the DVS_READY status on target port, not for the explaination.
Anyway I think that difference (between DVS_READY and DSM_READY) depends on FC driver and so depends on the kind of FC card adapter (DVS_READY for td driver and DSM_READY for fcd driver).

But unfortunately I don't know the exact meaning of them.
Could you post a complete

ioscan -fn

That should say what the system does see on the FC channels.

Best regards,
Fabio

[Torsten.]

According to a document found on the net I guess
dynamic voltage scaling (DVS)
dynamic link shutdown (DLS)

is port behaviour related. But DSM?

I assume the eva port status (CVeva) is Logged into fabric?

[Eric SAUBIGNAC]

Ok Fabio, you will find it in the attached file with some more informations.

I have just made a test on another SAN where port status are also DSM_READY (fcd drivers) and every thing is OK. But it is HP-UX 11.23 on a "normal" box (not those f.....g blades :-( Where is my hammer ? )

Eric

[Eric SAUBIGNAC]

Yes Torsten. Here is copy/paste from command view EVA

Port 1:
World Wide Name: 50001FE1 50111FBC
Address: 0B-12-00
Operational State: Good
Connection state: Logged into fabric
Speed: 4Gb/s
Topology: Fabric
Port 2:
World Wide Name: 50001FE1 50111FBD
Address: 15-12-00
Operational State: Good
C onnection state: Logged into fabric
Speed: 4Gb/s
Topology: Fabric

From FC switch point of view I see no trouble : EVA is correctly seen as F port. Speed is now configured at 4Gb, it was in auto mode before.

I would like to connect a "normal" box on this SAN to see if there are some differences with blades, but for the moment it is not possible :-(

Eric

[Fabio Ettore]

Hi Eric,

on /dev/fcd0 channel is recognised the boot disk /dev/rdisk/disk4 (I see it has 4 links, 1 primary and 3 alternate).
Anyway if on a 11.23 system all works well then it sounds like a issue (probably still unknown) about fcd driver and 11.31 when selecting a specific target port by fcmsutil.

Have you the latest version of FCD driver on 11.31?
If so then I suggest opening a call by HP and submit the issue. Otherwise download the latest FCD driver for that kind of adapter from software.hp.com.

Good luck...

Best regards,
Fabio

[Eric SAUBIGNAC]

Bonjour,

"Anyway if on a 11.23 system all works well", not really : the test was done on an other SAN.

Yes, I have latest patch for fcd driver (PHKL_36790) ... well I guess it is the latest one !

I have placed a call to HP yesterday and still waiting for valuable answer ...

If I have time enough, I will try to install an 11iv2 to see.

Eric

[Eric SAUBIGNAC]

Finally, it is a bug. Here is the answer of HP :

------------------------
The problem appears to be a regression in the latest version of the fcd driver. QXCR1000815634 has been raised for this and it will get investigated further
------------------------

I have now to modify my scripts. So I will scan whole output of "get remote all" instead of "get remote . That's life.

Thanks everybody

Eric

[Fabio Ettore]

Hi Eric,

thanks for letting us know.

Regards,
Fabio