fcmsutil

[Marvin Diaz_1]

Hi,

Could anybody help me on the error below.

[/]#fcmsutil /dev/td8

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Previous Topology = UNINITIALIZED
Link Speed = UNINITIALIZED
Local N_Port_id is = 0x000000
Local Loop_id is = 126
N_Port Node World Wide Name = 0x50060b0000257287
N_Port Port World Wide Name = 0x50060b0000257286
Driver state = AWAITING_LINK_UP
Hardware Path is = 2/0/8/1/0
Number of Assisted IOs = 0
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 896
Driver Version = @(#) PATCH_11.11: libtd.a : Jun 28 2002, 11:08:35, PHSS_26799

need it very badly

Thanks for usual support,
Marvs

[RAC_1]

Driver state = AWAITING_LINK_UP

This makes me think is everything OK with cables/connections??

Wat does, ioscan -fnC fc says?? Is the card in claimed state?? Did you load the correct driver??

If all above is OK, how about reset??

fsmsutil /dev/td8 reset

Anil

[Tom Danzig]

Sounds like a bad cable or switch port (if used). The card cannot link up to the FC fabric or direct connect port it is attached to.

[Prashant Zanwar_4]

Probably you have connected on this FC card of your server. Because when i compare my two servers I am also getting these results.
Where nothing is connected I am getting AWAITING_LINK_UP

and where a array is connected, it's showing online.

Hope this helps
Thanks
Prashant

[Prashant Zanwar_4]

Try seeing ioscan -u output, it will show the path expansion for your FC by attached devices..

Thanks
Prashant

[Marvin Diaz_1]

Hi Guys,

All your suggestions are already done and still problem persist. In the ioscan all the 3 x FC cards are found and had a device drivers.

I have already isolated cables and switch ports but still problem persist. Try to look also the error:
Previous Topology = UNINITIALIZED
Link Speed = UNINITIALIZED

What does this mean?

Thanks and Need Badly your help

"Marvs

[Sridhar Bhaskarla]

Hi Marvs,

As the error says "AWAITING_LINK_UP", there is no link between the interface and the storage component. If the cable is having loose ends, make sure transmit end goes into the receive end of the adapter and vice versa. If the status LED on the adapter is blinking steadily, then the there is no link. Obvioulsly the card is being recognized on the system so I wouldn't worry much about the configuration on the system side.

-Sri

[Hein van den Heuvel]

Sri wrote: If the status LED on the adapter is blinking steadily, then the there is no link.

I agree with Sri. Time to actually go into the lab and look at stuff, like the HBA led's. The swithc probably has a management tool that lets you look at virtualized leds, but it is more fun to go and touch the stuff. I'd even go as far as looking into the cable, from a somewhat safe distance. Look once at the switch side for one lighted side (red) on the cable, and the other side on the swithc should be lit. Then plug back in and move over to the server. Pull the connector and look. Again, one side on the cable shoul dbe lit red, the other side of the connector should be lit.

Cheers,
Hein.

[Michael Tully]

The awaiting link-up means there is no connection at the other end.

1) check or change the cable
2) login to the switch and do a "switchshow"
This will tell you the mac address of the HBA card. If it reports "No Light" this will tell you a problem with either the switch port/cable or HBA card.
3) Try using the same cable on another HBA card if you have one.

[Hari Hara Kumar M_1 · Accepted solution]

Hello

The fcmsutil output shows that the card is currently not initialized (which means the link is not up and running). The previous topology also seems to indicate that this card has not been online since the last reboot. This could occur due to any of the below:

1. Cable between HBA and port at other end is not functioning at its best.
2. Problem with the GBICs at either the HBA or the other port end.
3. Problems in negotitating the speed to either 1 or 2 Gbps between the HBA and the port at the other end.
4. Some other problem that may require additional debug information.

It would help if the physical connections are verified manually. Changing the cables and/or GBICs may also help to rule out any basic hardware problems outlined in reasons 1 and 2.

If the problem persists, setup information along with output from running "ioscan -kfn" and "/opt/fcms/bin/tddiag > /tmp/tddiag.out" would help serve as a starting point into looking at the possibility of reasons 3 or 4 having been hit.

Thanks
-Hari