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

Conference 7.286::fddi

Title:	FDDI - The Next Generation

Moderator:	NETCAD::STEFANI

Created:	Thu Apr 27 1989
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2259
Total number of notes:	8590

850.0. ""Invalid media address" starting DECnet on DEFZA" by STU03::RUEGGEN () Fri Feb 05 1993 02:42

    
                    Hello,
    
                                                          
            customer has a MI-cluster consisting of a 7610 a 6430 and a
            4000-90. The 4000-90 has an ethernet interface and a FDDI
            (DEFZA) interface.
    
            This 4000-90 boots via ethernet and then tries to start
            DECnet on both adapters. Ethernet works o.k. but with
            the FDDI he gets "invalid media address".
            Doing a sho LAN under SDA shows that SCA (60-07) is
            started on both adapters. The only way I found to start
            DECnet on the FDDI was to "Run LAVC$STOP_BUS" for the
            FCA, then starting the line and circuit for FZA-0 and
            running "LAVC$START_BUS". I then see DECnet and SCA on
            this adapter.
            Is this an expected behaviour?
    
    
                                            Thanks in advance
    
                                                    Ulrich

T.R Title User Personal
Name Date Lines

850.1 KONING::KONING Paul Koning, A-13683 Fri Feb 05 1993 10:34 9

T.R	Title	User	Personal Name	Date	Lines
850.1		KONING::KONING	Paul Koning, A-13683	`Fri Feb 05 1993 10:34`	9
	Is there a bridge between the FDDI and the Ethernet? It sounds that way. The problem is that DECnet uses a LAN station address derived from the node address -- the same for all ports on which it's turned on. The rules require a unique LAN address for every station connected to the same extended LAN (i.e., LANs connected by bridges). The software checks this when you turn on the circuit. If the check finds a duplicate, you get the error message you mentioned. paul

Is there a bridge between the FDDI and the Ethernet?  It sounds that way.
The problem is that DECnet uses a LAN station address derived from the node
address -- the same for all ports on which it's turned on.  The rules require
a unique LAN address for every station connected to the same extended LAN
(i.e., LANs connected by bridges).  The software checks this when you turn
on the circuit.  If the check finds a duplicate, you get the error message
you mentioned.

	paul