Installing New Fibre cards on rp4440

[Juan M Leon]

Hello, I hope somebody can help me with this problem.
I have 2 rp4440 servers that were build using a golden image.
The golden image was created from a server with all the drivers for multiple SAN Fibre cards installed

Yesterday I installed 2 cards model A6795-62002
(Tachyon XL2 PCI Fiber Channel adapter ) on each server.
Before the hardware was installed I verified that the drivers were on the server.

#-> swlist | grep -i fibre
FibrChanl-00 B.11.11.12 PCI/HSC FibreChannel;Supptd HW=A6684A,A6685A,A5158A,A6795A
FibrChanl-01 B.11.11.04 PCI-X FibreChannel;Supptd HW=A6826A,A9782A,A9784A,AB465A

#-> swlist -l product | grep -i fibre
FC-FCD B.11.11.04 PCI-X FibreChannel;Supptd HW=A6826A,A9782A,A9784A,AB465A
FC-TACHYON-TL B.11.11.12 PCI/HSC FibreChannel;Supptd HW=A6684A,A6685A,A5158A,A6795A
FCMassStorage B.11.11 Fibre Channel Mass Storage
PHKL_34161 1.0 Fibre Channel Mass Storage Patch
PHSS_31326 1.0 Tachyon TL Fibre Channel Driver Patch


However after the cards were installed and the system was available the ioscan shows the devices as unclaimed
the hardware paths are 0/4/2/0 and 0/5/2/0

lan 0 0/1/2/0 iether CLAIMED INTERFACE HP AB352-60001 PCI/PCI-X 1000Base-T Dual-port Core
lan 1 0/1/2/1 iether CLAIMED INTERFACE HP AB352-60001 PCI/PCI-X 1000Base-T Dual-port Core
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
lan 2 0/2/1/0 igelan CLAIMED INTERFACE HP A6825-60101 PCI 1000Base-T Adapter
ba 3 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
unknown -1 0/4/2/0 UNCLAIMED UNKNOWN PCI SerialBus (103c1029)
ba 4 0/5 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
unknown -1 0/5/2/0 UNCLAIMED UNKNOWN PCI SerialBus (103c1029)
ba 5 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
lan 3 0/6/1/0 igelan CLAIMED INTERFACE HP A6825-60101 PCI 1000Base-T Adapter




The lsdev out is the following.

#-> lsdev | grep -e 'td' -e 'Class' -e 'fc'
Character Block Driver Class
45 -1 fcT1_cntl lan
46 -1 netdiag1 unknown
48 -1 fcp fcp
49 -1 td unknown
50 -1 fcd unknown

The kmsystem output is the following

#-> kmsystem | grep -e 'td' -e 'fc' -e 'Module'
Module Configured Loadable
fcT1 Y -
fcT1_cntl Y -
fcT1_fcp Y -
fcd N -
fcms Y -
fcp Y -
fcp_cdio Y -
fcparray Y -
fcpdev Y -
fcpmux Y -
netdiag1 Y -
ssrfc N -
td N -


Seems that Driver td is unknow under the lsdev output and fcd was not loaded/configured in the kernel.
I am guessing that what I need to do is enable (In) the td and fcd Modules in the kernel and reboot for it to take effect.

My questions are:

Should the Modules get enabled (In) to be in the kernel once the crad is detected?
Enabling the modules is the only steps I need to do for the cards to work properly?
Any other suggestions or point of view?

All your help will be very appreciated.

Thank you

Juan

[Patrick Wallek]

>>Should the Modules get enabled (In) to be in the kernel once the crad is detected?

No the drivers will NOT get enabled automatically.

>>Enabling the modules is the only steps I need to do for the cards to work properly?

Yes, I believe that should suffice.

[Court Campbell]

Should the Modules get enabled (In) to be in the kernel once the crad is detected?

No, it's not automagic.

Enabling the modules is the only steps I need to do for the cards to work properly?

Yes, add the kernel drivers, recompile, and reboot.

Any other suggestions or point of view?

None that I can think of.

[Juan M Leon]

Patrick /Court
thanks for your answers, I feel more confortable with what I need to do.

Court, I think your comment is funny in a good way : "No, it's not automagic"

Again thanks both of you for your reply.

[Charles H Emery · Accepted solution]

I concur with Patrick and Court.
Recently assisted a coworker to resolve the exact same problem.

[Court Campbell]

I am not sure who coined the word automagic, but I have used it ever since I heard it.