FDDI Network Card

[Tracey]

I had a network card installed on one of my L2000 boxes. The card that was installed is (I beleive) an FDDI card with 3 ports, 2 fibre, one not. Right now both lights on the card are blinking green and of course I cannot ping to/from it.

When I go through sam to configure it, it apparently sees it, and I configured it. But I see no indications of which port I've just configured.

I've installed the FDDI Driver, and I think from reading other posts, that I also need to install the FDDI/9000 Server.

Any help is appreciated.

Tracey

[S.K. Chan]

Yes you definately need

Server FDDI/9000

for SAM to be able to see it.

[S.K. Chan]

Additional reference .. online..

http://www.docs.hp.com/hpux/netcom/index.html#FDDI/9000

[Tracey]

Thanks for the link, but I am still having the same problem. Any help is appreciated.

Tracey

[S.K. Chan]

Can you provide more details ? Especially the steps you took to configure it in SAM. Also while you're at it could you check if you got the latest PCI FDDI patches ..
11.00 PHNE_20874
10.20 PHNE_23509
11i no-FDDI-cumulative-patch-needed
Did you try configure it manually instead of using SAM ?

[Jeff Schussele]

Hi Tracey,

Also I would verify the fibre integrity & the port you're connecting to.
What's the link status on the port?
Have you tried a known good fibre & a known good port?
How about the port settings?

Rgds,
Jeff

[Tracey]

Sorry for the delay, I didn't get an email telling me I had responses.

The FDDI card was inserted into the machine by a HP tech, he started the machine up, saw that the card was showing up in IO scan and then left.

I've installed the FDDI server and FDDI drivers. Through SAM, I went into configure network cards, just like I would normally do for a single port network card, and assigned it an IP address. No indication of which port on the card I was configuring. I suppose I was expecting something to tell me A or B etc. Both lights on the back of the cards are still blinking green.

The fiber port on the hub and the cable were working just fine on my now defunct K460 so I beleive that are fine.

I don't have the patches mentioned installed, but I will go get them right now. And I have not yet tried to configure it manually. I may look into that after I try the patch.

One thing that confuses me is the major number on the lanscan vs the number on the device file. I've manually recreated the device file using 119 (doesn't work), but when I do it through sam it goes back to 50.

I also just noticed that the hardware state is down.. Hmm...

Please see my attached doucment for detail of drivers and scans.

Thank you in advance.
Tracey

[Duncan Edmonstone]

I don't think it matters which port you plug in through if you are going single attach into a concentrator... have a look at the following link:

http://docs.hp.com/hpux/onlinedocs/J3626-90032/J3626-90032.html

HTH

Duncan

[Steven Gillard_2 · Accepted solution]

From memory, the hardware state will remain DOWN until a valid signal is received on the FDDI port. It doesn't *really* matter whether you plug it into port A or B - FDDI is a dual ring topology so one port is 'upstream' and the other is 'downstream'. Both ports are part of the same network interface. If you don't have something plugged in to one of the ports the other port simply enters a 'wrap' state and the interface will continue to function normally (without the redundancy).

What you must be certain of is the following:

- that you have a valid, working FDDI device at the other end;

- that you've got the correct A->B or B->A connections. If you have a FDDI concentrator which it sounds like you do then it shouldn't matter.

- that the cable is ok - these fibre cables don't particularly like being bent so there's always a chance you have a bad one now even if it worked before. Its always a good idea to try another cable (if you can).

Regards,
Steve

[Tracey]

It appears that I need a cable adapter part number A4700-67073

I'll let the forum know if that solves my problem.

Thanks for all of the responses,
Tracey