[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::alphanotes

Title:Alpha Support Conference
Notice:This is a new Alphanotes, please read note 2.2
Moderator:VAXAXP::BERNARDO
Created:Thu Jan 02 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:128
Total number of notes:617

114.0. "Invalid Media Address - DE450-CA" by NIOSS1::BROWNT () Fri May 23 1997 13:07

     Hi,

    I have a DE450-CA in an AlphaServer 8400 running OpenVMS V6.2-1H3.
    When the network starts up I receive the following error:

    Invalid media address, unit it active;
    Unrecognized component circuit EWA-0

    This only occurs when the AUI cable is connected on boot up. When
    the cable is connected after boot up, I don't see this error and
    I able to do loops and connect to other nodes. 

    My configuration also has 3 CIPCA's and a DEFPA module.
    
    In the SOC under the 8400 it mentions that 2 patches are required
    to support the DE450 with OpenVMS V6.2. I thought that they were
    referring to the following patches:

    ALPBOOT06_062 and ALPLAN04_062

    I installed these but still have the same errors on boot up. Any
    ideas what is the problem here? Thanks.

                                                       Tim
                                         
T.RTitleUserPersonal
Name
DateLines
114.1MILORD::BISHOPThe punishment that brought us peace was upon HimFri May 23 1997 13:513
    You have another node with the same node number on the same ethernet.
    
    - Richard.
114.2HELP/MESSAGE IVADDR; DECnet-PlusXDELTA::HOFFMANSteve, OpenVMS EngineeringFri May 23 1997 14:0516
  The command $ HELP/MESSAGE IVADDR will point you at the typical causes
  of this error.  Richard is right, however -- chances are, there is an
  Ethernet address conflict being detected.

  If you have multiple Ethernet or FDDI controllers on this system, then
  you need to make sure there are only routers connecting the network
  segments -- the segments cannot be directly connected nor bridged,
  or you need to run DECnet-Plus (formerly known as DECnet OSI).

  With DECnet Phase IV, all Ethernet and FDDI controllers on the system
  effectively receive duplicate network addresses -- IVADDR can mean that
  the system is "seeing itself" on the LAN...  Either disconnect the
  various LAN segments, shut off DECnet Phase IV on all but one LAN
  controller, use DECnet-Plus, etc...