Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LP11000 (1910 / 5759 IBM PN: 03N5020) 4Gb FC Dual-Port Adapter Problem

Status
Not open for further replies.

hammah

Technical User
Aug 27, 2007
8
DE
Hi folks!

I am relatively new to the AIX system, but not a total noob, and one of my first tasks at my new job is to get on two System p machines (both of them 9111-520) the above mentioned FC Adapters up and running. Unfortunately I've encountered some problems.

I hope I'll be able to provide you guys with sufficient information to that problem, so I'll just start.

The FC adapters were already placed in those machines by some other guy who works here, so I don't know whether this comprises already the existing problem.

Anyway on one machine, the adapter is in Slot C-3 (which is wrong based on this information and on the other machine it is placed in slot C-5, which seems to be correct based on the mentioned information, so I'll limit my information to this machine, so that if it works here, I can perform the appropriate measures on the other machine as well.

First of all, the output of oslevel -r

Code:
oslevel -r

5300-06

So the machine(s) is(are) up to date. Also the System Board microcode is up to date, and the machine(s) is(are) booted in to the temporary firmware image:

Output of lsmcode -cd sys0:

Code:
lsmcode -cd sys0

The current permanent system firmware image is SF240_320
The current temporary system firmware image is SF240_320
The system is currently booted from the temporary firmware image.

I don't know if this is the whole problem, and the machine should have been booted in to permanent image, but I don't think so. By the way, how do I change this? I've already tried :

Code:
/usr/lpp/diagnostics/bin/update_flash -c

and committing the temporary image via the
Code:
diag
command, but
Code:
lsmcode -cd sys0
keeps telling, me that the system is booted off the temporary image? I've rebooted twice with no effect.

Anyway, here is the output of lsslot -c pci:

Code:
lsslot -c pci

# Slot                   Description                         Device(s)
U787A.001.DPM03KO-P1-C1  PCI-X capable, 64 bit, 133MHz slot  pci5 lai0
U787A.001.DPM03KO-P1-C2  PCI-X capable, 32 bit, 66MHz slot   Empty
U787A.001.DPM03KO-P1-C3  PCI-X capable, 32 bit, 66MHz slot   Empty
U787A.001.DPM03KO-P1-C4  PCI-X capable, 64 bit, 133MHz slot  sisscsia0
[COLOR=red]U787A.001.DPM03KO-P1-C5  PCI-X capable, 64 bit, 133MHz slot  fcs0 fcs1[/color]
U787A.001.DPM03KO-P1-C6  PCI-X capable, 64 bit, 133MHz slot  Empty

My problem is, that I can't get the device to show up as Available:

Output of lsdev | grep fcs:

Code:
lsdev | grep fcs

fcs0       Defined   0B-08         FC Adapter
fcs1       Defined   0B-09         FC Adapter

And here the output of lscfg -vpl fcs*:

Code:
lscfg -vpl fcs*

  fcs0             U787A.001.DPM03KO-P1-C5-T1  FC Adapter

        Part Number.................03N5020
        EC Level....................A
        Serial Number...............1F6160C095
        Manufacturer................001F
        Feature Code/Marketing ID...1910
        FRU Number.................. 03N5020
        Brand.......................H0
        Device Specific.(ZM)........3
        Network Address.............10000000C9554488
        ROS Level and ID............02C82138
        Device Specific.(Z0)........1036406D
        Device Specific.(Z1)........00000000
        Device Specific.(Z2)........00000000
        Device Specific.(Z3)........03000909
        Device Specific.(Z4)........FFC01159
        Device Specific.(Z5)........02C82138
        Device Specific.(Z6)........06C12138
        Device Specific.(Z7)........07C12138
        Device Specific.(Z8)........20000000C9554488
[COLOR=red]        Device Specific.(Z9)........BS2.10X8[/color]
        Device Specific.(ZA)........B1F2.10X8
        Device Specific.(ZB)........B2F2.10X8
        Device Specific.(YL)........U787A.001.DPM03KO-P1-C5-T1

  fcs1             U787A.001.DPM03KO-P1-C5-T2  FC Adapter

        Part Number.................03N5020
        EC Level....................A
        Serial Number...............1F6160C095
        Manufacturer................001F
        Feature Code/Marketing ID...1910
        FRU Number.................. 03N5020
        Brand.......................H0
        Device Specific.(ZM)........3
        Network Address.............10000000C9554487
        ROS Level and ID............02C82138
        Device Specific.(Z0)........1036406D
        Device Specific.(Z1)........00000000
        Device Specific.(Z2)........00000000
        Device Specific.(Z3)........03000909
        Device Specific.(Z4)........FFC01159
        Device Specific.(Z5)........02C82138
        Device Specific.(Z6)........06C12138
        Device Specific.(Z7)........07C12138
        Device Specific.(Z8)........20000000C9554487
[COLOR=red]        Device Specific.(Z9)........BS2.10X8[/color]
        Device Specific.(ZA)........B1F2.10X8
        Device Specific.(ZB)........B2F2.10X8
        Device Specific.(YL)........U787A.001.DPM03KO-P1-C5-T2


  PLATFORM SPECIFIC

  Name:  fibre-channel
    Model:  LP11000
    Node:  fibre-channel@1
    Device Type:  fcp
    Physical Location: U787A.001.DPM03KO-P1-C5-T1

  Name:  fibre-channel
    Model:  LP11000
    Node:  fibre-channel@1,1
    Device Type:  fcp
    Physical Location: U787A.001.DPM03KO-P1-C5-T2

My first guess was that I have to update the microcode on that card, even if I can see based on the Z9 field, that it already has the newest microcode applied, as the *.rpm from IBMs Website installed perfectly. However, when I try to update the microcode, with the command:

Code:
diag -d fcsX -T download (where X = 0 or 1)

I get a message that the device hasn't got diagnostics support. According to IBM's Website if I query the current microcode I should get something which tells me what microcode the adapter has, but it fails, telling me the same thing. Furthermore, when I use cfgmgr to install the device, it tells me the following:

Code:
cfgmgr

Method error (/usr/lib/methods/cfgefc -l fcs0 ):
        0514-086 Cannot perform the requested function because the specified
                 device is not supported on this platform.
Method error (/usr/lib/methods/cfgefc -l fcs1 ):
        0514-086 Cannot perform the requested function because the specified
                 device is not supported on this platform.

Furthermore I've got the following messages in the errorlog:

Code:
errpt | more

...
8924BF96   0827134407 I H fcs0           Device Not Supported
8924BF96   0827134307 I H fcs1           Device Not Supported
...

and:

Code:
errpt -a | more

LABEL:          LP_NOT_SUPPORTED
IDENTIFIER:     8924BF96

Date/Time:       Mon Aug 27 13:44:22 MEDT 2007
Sequence Number: 11646
Machine Id:      00C5A21E4C00
Node Id:         XXXXXXX
Class:           H
Type:            INFO
Resource Name:   fcs1
Resource Class:  adapter
Resource Type:   df1000fd
Location:        U787A.001.DPM03KO-P1-C5-T2
VPD:
        Part Number.................03N5020
        EC Level....................A
        Serial Number...............1F6160C095
        Manufacturer................001F
        Feature Code/Marketing ID...1910
        FRU Number.................. 03N5020
        Device Specific.(BR)........H0
        Device Specific.(ZM)........3
        Network Address.............10000000C9554487
        ROS Level and ID............02C82138
        Device Specific.(Z0)........1036406D
        Device Specific.(Z1)........00000000
        Device Specific.(Z2)........00000000
        Device Specific.(Z3)........03000909
        Device Specific.(Z4)........FFC01159
        Device Specific.(Z5)........02C82138
        Device Specific.(Z6)........06C12138
        Device Specific.(Z7)........07C12138
        Device Specific.(Z8)........20000000C9554487
        Device Specific.(Z9)........BS2.10X8
        Device Specific.(ZA)........B1F2.10X8
        Device Specific.(ZB)........B2F2.10X8

Description
Device Not Supported

---------------------------------------------------------
LABEL:          LP_NOT_SUPPORTED
IDENTIFIER:     8924BF96

Date/Time:       Mon Aug 27 13:44:12 MEDT 2007
Sequence Number: 11644
Machine Id:      00C5A21E4C00
Node Id:         XXXXXXX
Class:           H
Type:            INFO
Resource Name:   fcs0
Resource Class:  adapter
Resource Type:   df1000fd
Location:        U787A.001.DPM03KO-P1-C5-T1
VPD:
        Part Number.................03N5020
        EC Level....................A
        Serial Number...............1F6160C095
        Manufacturer................001F
        Feature Code/Marketing ID...1910
        FRU Number.................. 03N5020
        Device Specific.(BR)........H0
        Device Specific.(ZM)........3
        Network Address.............10000000C9554488
        ROS Level and ID............02C82138
        Device Specific.(Z0)........1036406D
        Device Specific.(Z1)........00000000
        Device Specific.(Z2)........00000000
        Device Specific.(Z3)........03000909
        Device Specific.(Z4)........FFC01159
        Device Specific.(Z5)........02C82138
        Device Specific.(Z6)........06C12138
        Device Specific.(Z7)........07C12138
        Device Specific.(Z8)........20000000C9554488
        Device Specific.(Z9)........BS2.10X8
        Device Specific.(ZA)........B1F2.10X8
        Device Specific.(ZB)........B2F2.10X8

Description
Device Not Supported

And so I'm stuck. I really don't know what to do now. I've already tried to remove the device completely with rmdev -dl fcs0 resp. 1 and this works. cfgmgr then installs the device again, but it tells me the same thing as above, and leaves the device in the "Defined" state which is of course useless for me.

Do I have to unplug the card, use rmdev, plug in again the card to accomplisch what I want? Do I have to disconnect the Fibre-Cables from the card, or is this irrelevant? I have really tried a lot, but as I said I'm stuck, and I absolutely don't know what to do now?

So, any help would be appreciated, and if more info is needed, I'll be happy to post it.

Thanks in Advance!

Regards,
Hammah
 
I'm guessing you don't have all drivers installed for this adapter.

What does cfgmgr -v say or do?

Try also:

cfgmgr -v -i /dev/cd0 -l fcs0
(repeat for fcs1)

or

cfgmgr -v -i /path/to/lppsource/dir -l fcs0
(same here)

This isntructs the system to install any fileset needed to support the installed hardware. Did you (or your colleague) find any CDrom with device drivers needed to support the adapter?)


HTH,

p5wizard
 
Hi p5wizard!

cfgmgr -v tells me unfortunately the same thing:

Code:
Method error (/usr/lib/methods/cfgefc -l fcs0 ):
        0514-086 Cannot perform the requested function because the specified
                 device is not supported on this platform.
Method error (/usr/lib/methods/cfgefc -l fcs1 ):
        0514-086 Cannot perform the requested function because the specified
                 device is not supported on this platform.

Also if I try it with the path to lppsource supplied, there's no difference, and I get the same message. Unfortunately I don't think there was any CD supplied. Also I had read somewhere on the IBM pages (I don't remember where exactly), that this device should be supplied by drivers shipped with AIX5.3.

Regards,
Hammah
 
Time to call in a service request to IBM I guess.


HTH,

p5wizard
 
Is there a way to determine which driver / module a device uses, like e.g. in Linux with lsmod? I'm asking that, because there are some other machines in this network which have the same card in them working flawlessly.

And is there a way to determine to which fileset a specific file belongs? I could then determine which driver / module is needed from another machine, and try to install the specific fileset, or am I thinking something totally wrong here?

Regards,
Hammah
 
Hi everyone!

I've got another question. I've found on this page the following remark:

"Slot C5 can only accommodate short cards if feature 6594 is present in the system unit"

Well, the mentioned card is a short card, but how do I find out, whether feature 6594 is present or not? Would that be

Code:
lscfg -vpl sysplanar0 | grep 6594

or can I determine that somehow else?
 
#6594 - 4-Disk Slot Exp-PCI-X Ctlr

This is a disk expansion that occupies the space at the end of the slot 5 card position.

Slot 5 is a long slot and so can take long cards if the disk expansion is not fitted.

If the disk expansion is fitted it will prevent a long card from fitting in slot 5.

As you have a short card it does not matter if the disk expansion is fitted.

I think there is a problem with the devices.pci.df1000fd or the other devices.pci.df1000f* filesets.
 
If you have this type of card working in other servers and one of those servers is a test server, why not try and swap the cards and check if the card itself is OK or if the "good" card stops working in the "bad" server. If you don't want to try that for fear of messing up the "good" server, call the problem in to IBM and let them deal with it.


HTH,

p5wizard
 
@DukeSSD

Thanks for the answer. Concerning the filesets, well I made an lslpp -l devices.pci.df1000f* on one of the servers containing the "good" card, and on one of the servers containing the "bad" card and ran a diff. But the filesets are the same, also the filesets on the servers with the "bad" cards are newer, since I updated them, hoping that would solve the problem, which it unfortunately didn't...

Do you think it would make any sense, to force reinstallation of the filesets in question?

@p5wizard

Thanks for your answer as well. The problem is, that I've got two test servers with "bad" cards, which makes me somehow mad, since I´ve got the same problems on both of them.

The servers containing the "good" cards are used for production, and my boss will cut my balls off, if I shut them down...:) Also the servers with the "good" cards are another model, namely 9110-51A, in contrast to my problem children being 9111-520.

As I said, IBM documentation states that the cards are compatible with the latter model. But I think you are right, and I will let IBM deal with it, since I am really running out of ideas here.
 
Good decision. In this case I wouldn't touch any production server either. Not to isolate problems on non-prod servers that is.

HTH,

p5wizard
 
Rather than lslpp you should be using lppchk to check out your installed filesets.

Try:
lppchk -c
and
lppchk -vm3
on the problem system
 
I agree.

I had a look at the above link and associated tabs and at various other resources and I think the 9111-520 only supports the "full price" 5759.

Take them back to the supplier and demand 5759's in exchange because the 1910 is not supported in the 520.
 
@chgwhat & @DukeSSD

Oh man... Thanks a lot you guys! I could've tried everything and never gotten it to work, obviously. But I didn't find the link you mentioned, if so, I would've had a lot less trouble. That very useful link will become now a part of my neverending-IBM-Bookmarklist...

I'll kill IBM! It's unbelievable they're selling stuff, and don't even know what for. I'll let them change it.

Thanks again for everything!


Regards,
Hammah
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top