Conference 7.286::fddi

1527.0. "MFA-0 showing as type Ethernet" by CSC32::SCHMALSTIEG () Fri Dec 09 1994 20:50

 -- This note has been cross posted in the DECnet Extension note file --


Greetings,
    

The customer is running the FXDRIVER version "X-22A1" and when he views
the characteristics of the mfa-0 line via NCP it shows a device type on
one system as Ethernet and FDDI on another system. One system is a 9000
and I forgot what the other system types were. I am confused because the
below STARS database article indicates that it must be defined in the 
permanent database. The customer does not have a type defined in the permanent
database. The customer wants to know if this is cosmetic or is a problem 
that should be addressed. 

VMS 5.5-2 





DEMFA DECnet line startup on V5.5-2 Fails if Protocol `ETHERNET` specified.

     Any party granted access to the following copyrighted information
     (protected under Federal Copyright Laws), pursuant to a duly executed
     Digital Service Agreement may, under the terms of such agreement copy
     all or selected portions of this information for internal use and
     distribution only. No other copying or distribution for any other
     purpose is authorized.

Copyright (c) Digital Equipment Corporation 1993. All rights reserved.

PRODUCT:   VMS,  Version 5.5-2  DECnet. DEMFA

LAYERED PRODUCT:   DECnet

SOURCE: Digital Equipment Corporation


BRIEF PROBLEM OUTLINE:

DECnet  fails  to  start  on  a  DEMFA  (XMI - FDDI), circuit "MFA" when
protocol "Ethernet" is specified.  The NCP command SET KNOWN LINE ALL in
STARTNET.COM fails.


SYMPTOMS

Decnet does not startup on the FDDI. An error is reported when  the  SET
KNOWN LINE ALL command is issued  in STARTNET.COM. The text of the error
could be:-


NCP>set line mfa-0 all
%NCP-W-OPEFAI, Operation failure

%SYSTEM-F-DEVREQERR, device request error
                   , tributary malfunction
                   , DDCMP start message received
NCP>

or

NCP>set line mfa-0 all
%NCP-W-OPEFAI, Operation failure

%SYSTEM-F-DEVREQERR, device request error
                   , tributary malfunction
NCP>

If the line is then turned on manually the process will go RWAST.
System will need a reboot to clear problem with NCP.


ANALYSIS:

The  FXdriver  in  VMS 5.5-2 (ident X-20) and DECnet NCP now support the
line protocol keyword "FDDI". Before this version the keyword "ETHERNET"
was  used  even  on FDDI devices. When upgrading from 5.5-1 to 5.5-2 the
DECnet line database file (NETLINE.DAT) is preserved. When using a DEMFA
the  line  id is MFA. If the non-volatile database was defined with LINE
MFA-0 STATE ON PROTOCOL ETHERNET after the upgrade  you  will  get  this
problem.  The  correct  protocol  type  is now FDDI which is now the new
default.


SOLUTION:

Define the line characteristics to be protocol FDDI or ensure  that  the
protocol type is defaulted.

Change to Correct setting:-

NCP>lis line mfa-0 cha
Line Permanent Characteristics as of 23-AUG-1993 13:42:34

Line = MFA-0

Receive buffers          = 10
Protocol                 = FDDI

or

NCP>lis line mfa-0 cha
Line Permanent Characteristics as of 23-AUG-1993 13:42:34

Line = MFA-0

Receive buffers          = 10



From incorrect setting:-

NCP>lis line mfa-0 cha
Line Permanent Characteristics as of 23-AUG-1993 13:43:25

Line = MFA-0

Receive buffers          = 10
Protocol                 = Ethernet