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

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

5047.0. "DECnet IV AM - PA doesn't give line util." by ABACUS::BUKOWSKI () Wed May 12 1993 16:36

	The utilization statics for node4 entities with FDDI controllers
	do not work.  It looks like the node4 AM doesn't understand a 
	protocol type of FDDI.  Does anybody care?  Can somebody look at
	this to see if it is a bug that should be properly submitted?
    
    	Thanks,
	Mike

MCC> show node4 hyster line mfa-0 all statisti

Node4 hyster Line mfa-0
AT 12-MAY-1993 15:20:01 Statistics

Cannot locate services required information for computing statistics.


MCC> show node4 hyster line mfa-0 all char

Node4 DEC:.mko.hyster Line mfa-0
AT 12-MAY-1993 15:06:41 Characteristics

Examination of Attributes shows:
                        Receive Buffers = 10
                             Controller = Normal
                               Protocol =
%MCC-E-NOENTITY,  no corresponding entity instance exists

                          Service Timer = 4000 Milliseconds
                       Hardware Address = 08-00-2B-2F-73-CB
                            Buffer Size = 1498 Bytes
MCC>

$ MCR NCP TELL HYSTER SHOW LINE MFA-0 CHAR


Line Volatile Characteristics as of 12-MAY-1993 15:28:54

Line = MFA-0

Receive buffers          = 10
Controller               = normal
Protocol                 = FDDI
Service timer            = 4000
Hardware address         = 08-00-2B-2F-73-CB
Device buffer size       = 1498
Requested TRT            = 8000
Valid transmission time  = 2600
Restricted token timeout = 1000
Ring purger enable       = on
NIF target               = 00-00-00-00-00-00
SIF configuration target = 00-00-00-00-00-00
SIF operation target     = 00-00-00-00-00-00
Echo target              = 00-00-00-00-00-00
Echo data                = 55
Echo length              = 1
T.RTitleUserPersonal
Name
DateLines
5047.1no DEMFA support ?MFRNW1::SCHUSTERKarl Schuster @MFR Network ServicesThu May 13 1993 10:486
    I have exactly the same problem.
    I asume, MCC V1.3 does not support fully the DEMFA.
    For the customers this is not easy to understand, because DEMFAs are in
    the field now since summer 1992.
    
    Karl
5047.2missing enumerationBRAT::BUKOWSKIThu May 13 1993 13:4910
    
    I have found out more information.  Chris B. had me look into the
    Dictionary Browser under node4 line attribute protocol.  It turns
    out that Constructor Data Type is missing the enumeration for FDDI.
    Now we just need to get the correct people to add the proper value
    and produce a simple patch.  I would like a patch even though they
    supposing do not provide patches anymore and we are supposed to wait
    for the MUP.   Can somebody help us out here?
    
    Thanks,  Mike
5047.3node4 support for fddi2582::ROBERTSKeith Roberts - Network Management ApplicationsThu May 13 1993 14:5114
  Mike,

  Step #1 is for the Phase-4 AM to support the FDDI line .. as you indicated
  the MSL must be updated to support the FDDI enumeration for the Protocol
  Attribute .. and there may be other things to support in the MSL.

  Step #2 is getting FDDI Line Statistics.  Currently the Performance
  Analyzer does not support the FDDI variant.  I do not know if the statistics
  for FDDI are the same as other the other Node4 Line Protocols.  If they are,
  it will be pretty straight forward to add them.  If the stats are different,
  then SOMEONE will have to tell me what they are (the equations with
  attribute names).

  /keith
5047.4Missing FDDI enumeration entered as QAR#562MOLAR::MOLAR::BRIENENNetwork Management Applications!Thu May 13 1993 17:500
5047.5Not a simple patchTOOK::LYONSAhh, but fortunately, I have the key to escape reality.Thu May 13 1993 20:189
When this gets fixed, it will not be "a simple patch".

The PROTOCOL attribute appears in almost a hundred places in DEPENDS ON clauses
in the MSL, and each one has to be checked and fixed.  Many, many other 
attributes depend on the protocol type.

Also, it looks like there are a few places in the AM itself where the line 
protocol is an issue, and a new AM would be needed to go along with the MSL.
(line types are built into a table in the XLATE_TABLES module)
5047.6never assumeBRAT::BUKOWSKIFri May 14 1993 10:007
    
    Gee. Sorry for assuming the patch would be simple, but thanks for 
    looking into it.  Not knowing that Chris had entered a QAR, I entered
    QAR # 241 yesterday.
    
    Thanks again,
    Mike
5047.7See also note 4669TOOK::MINTZErik Pavlik MintzWed May 19 1993 11:101
The underlying problem here is the same as in note 4669.