[Info-vax] DE500 to DE500 woes

VAXman- at SendSpamHere.ORG VAXman- at SendSpamHere.ORG
Sat Nov 26 20:08:19 EST 2011


In article <19356348.23.1322351495548.JavaMail.geo-discussion-forums at yqlh18>, urbancamo <mark at wickensonline.co.uk> writes:
>Hi Guys,
>
>I've got a problem with an AS1000A serving an AlphaServer 300 4/266 as a di=
>skless satellite. Both have a DE500 100MB network card. I've tried all comb=
>inations of line speed, negotiation type and duplex on each end, but I stil=
>l get the following continuous on the server:
>
>%%%%%%%%%%%  OPCOM  26-NOV-2011 23:43:49.20  %%%%%%%%%%%    (from node TIGE=
>R  at 26-NOV-2011 23:43:48.57)
>Message from user DECNET on TIGER
>DECnet event 4.7, circuit down, circuit fault
>From node 4.258 (TIGER), 26-NOV-2011 23:43:48.57
>Circuit EWA-0, Line synchronization lost
>
>
>%%%%%%%%%%%  OPCOM  26-NOV-2011 23:43:59.20  %%%%%%%%%%%    (from node TIGE=
>R  at 26-NOV-2011 23:43:58.58)
>Message from user DECNET on TIGER
>DECnet event 4.10, circuit up
>From node 4.258 (TIGER), 26-NOV-2011 23:43:58.57
>Circuit EWA-0
>
>
>OpenVMS 8.3 has been fully patched (as far as I'm aware).
>
>On the satellite node specific details of the card are:
>
>LAN Data Structures
>-------------------
>               -- EWB Device Information 26-NOV-2011 23:28:24 --
>
>LSB address                 83CAE000    Driver code address         81DACB5=
>8
>Driver version     00000001.08310124    Device1 code address        0000000=
>0
>Device1 version    00000000.00000000    Device2 code address        0000000=
>0
>Device2 version    00000000.00000000    LAN code address            81DAE20=
>0
>LAN version        00000001.08310190    DLL type                      CSMAC=
>D
>Device name                 EW_DE500    MOP name                         EW=
>A
>MOP ID                           203    HW serial               Not supplie=
>d
>HW version                  02000020    Promiscuous mode                 OF=
>F
>Controller mode               NORMAL    Promiscuous UCB             0000000=
>0
>Internal loopback                OFF    All multicast state              OF=
>F
>Hardware address   00-00-F8-06-94-D1    CRC generation mode               O=
>N
>Physical address   AA-00-04-00-02-11    Full Duplex Enable                O=
>N
>Active unit count                  6    Full Duplex State                 O=
>N
>Line speed                       100                                       =
>=20
>
>On the AlphaServer 1000A we have:
>
>LAN Data Structures
>-------------------
>               -- EWA Device Information 26-NOV-2011 23:47:01 --
>
>LSB address                 84A56000    Driver code address         81E1875=
>8
>Driver version     00000001.08310124    Device1 code address        0000000=
>0
>Device1 version    00000000.00000000    Device2 code address        0000000=
>0
>Device2 version    00000000.00000000    LAN code address            81E19E0=
>0
>LAN version        00000001.08310190    DLL type                      CSMAC=
>D
>Device name                 EW_DE500    MOP name                         EW=
>A
>MOP ID                           203    HW serial               Not supplie=
>d
>HW version                  02000012    Promiscuous mode                 OF=
>F
>Controller mode               NORMAL    Promiscuous UCB             0000000=
>0
>Internal loopback                OFF    All multicast state              OF=
>F
>Hardware address   00-00-F8-31-4B-21    CRC generation mode               O=
>N
>Physical address   AA-00-04-00-F9-10    Full Duplex Enable                O=
>N
>Active unit count                 10    Full Duplex State                 O=
>N
>Line speed                       100                                       =
>=20
>
>If I use the built in DE435 on the AlphaServer 300 I don't get continuous m=
>essages, but obviously it works less quickly.
>
>In between the boxes there is two gigabit ethernet switches.
>
>Any help gratefully received...

If you can, see what happens is you connect a crossover cable (T568A to 
T568B) directly from DE500 to DE500.  However, I have found issues with
the DE500 when connected to GbE, probably due to the DE500 predating GbE.


-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.



More information about the Info-vax mailing list