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

Conference help::decnet-osi_for_vms

Title:DECnet/OSI for OpenVMS
Moderator:TUXEDO::FONSECA
Created:Fri Feb 22 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3990
Total number of notes:19027

3902.0. "NCL return data corrupt" by HGOSPS::KENNETH () Wed Mar 19 1997 07:08

Hi,

I would like to ask two questions here regarding to DECnet/OSI V6.3 
(customer does not install the ECO6 yet).

1) On the console, there is some message displays 
  
Event: Unrecognized Individual PDU Destination from: Node ...
FDDI station FDDI-0 Link FDDI-0,

	Data Link Header='54AA0004000B04AA0004000104AAAA030000006003'H.

I only know that the header is a PhaseIV header and the DECnet address
is 1.1 and 1.11.  

Does anyone know the other code's meaning?  What is 54 stand for?
'AAAA03000000" means what?

2) The customer has several nodes all running DECnet/OSI V6.3.  On one
of the nodes, if you use NCL> show node <remote node> fddi station mfa-0 all
you will get:

"command failed due to:
 return data corrupt or incorrectly encoded on remote system"

There is no problem when typing this command on the local node.

Is it normal?  

Thanks for your help in advance.

Kenneth Leung
T.RTitleUserPersonal
Name		DateLines
3902.1its just a phaseIV packetMARVIN::RIGBYNo such thing as an alpha betaWed Mar 19 1997 07:4022
>	Data Link Header='54AA0004000B04AA0004000104AAAA030000006003'H.
>
>I only know that the header is a PhaseIV header and the DECnet address
>is 1.1 and 1.11.  
>
>Does anyone know the other code's meaning?  What is 54 stand for?
>'AAAA03000000" means what?

The 54 is the frame control field used on FDDI. 54 indicates that this packet
originated on an FDDI ring and has not been bridged onto this ring by a
FDDI/Ethernet bridge.

As 'ethernet' formats are not supported on FDDI, they are carried as 802.2 SNAP
packets with a PID with the OUI field all zero and the last two byte being the
ethernet protocol type.

so the AA AA is the sourace and destination SAP == SNAP
   the 03    is the UI
   the 00-00-00-60-03 is ethernet protocol type 60-03 == DECnet phase IV

Was this reported on node 1.11, if so then it would appear that DECnet phase IV
is not enabled on the FDDI interface.
3902.2NET$FDDI fixes are available for this.BULEAN::ABERDALEWed Mar 19 1997 12:5518
    >2) The customer has several nodes all running DECnet/OSI V6.3.  On one
    >of the nodes, if you use NCL> show node <remote node> fddi station
    >mfa-0 all
    >you will get:
    >
    >"command failed due to:
    > return data corrupt or incorrectly encoded on remote system"
    >
    >There is no problem when typing this command on the local node.
    >
    >Is it normal?
    
    No.  It's not normal.  This is fixed in OpenVMS V7.0.  Contact 
    VMS Engineering to get NET$FDDI fixes for earlier OpenVMS versions.
    Note that you need to apply the fix to the <remote node> in order
    to get this to work properly.
    
                               - LL
3902.3May I know what is the name of the patch?HGOSPS::KENNETHFri Mar 21 1997 07:458
    Hi,
    
    May I know the patch ID?  I've asked the VMSnotes conference and I
    think they are not quite certain about it.
    
    Thanks again for your help.
    
    Kenneth Leung
3902.4Please IPMT to VMS Device Drivers for detailsBULEAN::ABERDALEFri Mar 21 1997 14:3511
    Someone recently posted a list of VMS patches in one of the notes
    conferences, and I recall thinking, "Oh that's great!"  I saved the
    list somewhere, but now I can't find it.  
    
    I'm hoping that someone who also kept a copy of that list will 
    chime in here.  Barring that possibility, the best way to ensure that
    you get the correct answer is to log an IPMT against the VMS Device
    Drivers group.  They're the keepers of the NET$FDDI and NET$CSMACD 
    fixes.
    
                               - LL
3902.5RMULAC.DVO.DEC.COM::S_WATTUMScott Wattum - FTAM/VT/OSAK EngineeringFri Mar 21 1997 16:241
note 3896.0