topic Re: Network card info required in Operating System - OpenVMS

Network card info required

Terry Yeomans — Wed, 06 Dec 2006 11:38:51 GMT

We have a Alpha Server 1000A 5/333 running VMS 7.3-1 WE have had some slow responses recently and found that the network card is running at half duplex. We've tried to set to full but it knocks the node over. Can we find the cards' details without taking one of the boxes down to the chevrons? LANCP does not seem to hold the key to this info.

Re: Network card info required

Karl Rohwedder — Wed, 06 Dec 2006 11:43:25 GMT

You may use
$ ANA/SYS
SDA> CLUE CONFIG
or
SDA> SHO LAN /FULL

to get the card id.

regards Kalle

Re: Network card info required

Volker Halle — Wed, 06 Dec 2006 11:44:08 GMT

Terry,

$ ANAL/SYS
SDA> CLUE CONFIG
SDA> SHOW LAN/FULL/DEV=Exx ! VMS device name
SDA> EXIT

$ MC LANCP SHOW DEV/INT Exx

should show more information about the network interface card.

Volker.

Re: Network card info required

Volker Halle — Wed, 06 Dec 2006 11:50:57 GMT

Terry,

what you would like most is possibly this:

$ ANAL/SYS
SDA> CLUE FRU
FRU Table written to CLUE$FRU.SYS file, use System Event Analyzer or Error Log V
iewer to analyze.
SDA> EXIT
$ DIAGNOSE CLUE$FRU.SYS

this will show you the 'System Init Log', which is more-or-less the system console output from the last INIT.

Volker.

PS: This needs DECevent to be installed. You can also try this with WEBES/SEA.

Re: Network card info required

Richard Brodie_1 — Wed, 06 Dec 2006 13:17:17 GMT

"We've tried to set to full but it knocks the node over."

What I would want to determine first is whether the node crashed because the driver threw a wobbly, or because setting it to full duplex was a really bad idea.

Do the LANCP counters look OK running at half-duplex? An awful lot of people cause themselves a world of pain by setting their systems to full duplex when the network equipment is set to autonegotiate.

Re: Network card info required

Wim Van den Wyngaert — Thu, 07 Dec 2006 02:45:30 GMT

I tried the clue fru on my 1000 4/200 and this one said "FRU table not available or not implemented". Idem on AS 500. But it works on a 4100 (all 7.3).

This is new to me. I would advise everyone to try it too.

The diag then gives you : some important env variables, firmware versions and a lot of device info. I can see the device types of the ethernet card but not the speed it can handle.

Wim

Re: Network card info required

Steven Schweda — Thu, 07 Dec 2006 03:24:36 GMT

On a COMPAQ Professional Workstation XP1000
running OpenVMS V7.3-2:

SDA> clue fru
FRU Table not available or not implemented.

That was fun.

Re: Network card info required

Terry Yeomans — Thu, 07 Dec 2006 03:32:46 GMT

Thanks to all for your rapid responses.
Have used the info and found the what I need.
We don't have DecEvent installed but it is in the pipeline.
Regards Terry.

Re: Network card info required

rick jones — Thu, 07 Dec 2006 12:20:39 GMT

Half-duplex suggests that it was either hard-coded that way, or was set to autoneg and the other side was hardcoded and/or not doing autoneg. The attached is some boilerplate on 100BT autoneg

Re: Network card info required

rick jones — Thu, 07 Dec 2006 12:20:56 GMT

Half-duplex suggests that it was either hard-coded that way, or was set to autoneg and the other side was hardcoded and/or not doing autoneg. The attached is some boilerplate on 100BT autoneg

Re: Network card info required

Terry Yeomans — Fri, 08 Dec 2006 05:16:19 GMT

Thanks Rick for setting us in the right direction for the next step. Regards Terry.