[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

3008.0. "DEC CMIP data types supported" by TOOK::MATTHEWS () Fri May 15 1992 21:07

    The DEC CMIP AM (aka DNA5 AM) in V1.2 targeted the data types
    that are used to support DNA5 entities which are a subset
    of the data types that are found in DECmcc's SRM. There are
    some DNA5 data types that were not finalized by the DNA5
    community until late last year. These we tested against
    our test object implementations but we are finding subtle
    differences between the test object and how various
    DNA5 entities are encoding them. Thus the V1.2 implementation
    of the DEC CMIP AM is not guaranteed to have every data
    type fully implemented. 
    
    A future reply to this note and the release notes will have
    a definitive list of the supported data types.
    
    It will be the goal of a future release of the DEC CMIP AM
    to support all data types defined within chapter 5 of the
    SRM.
    
    Also, the directives which can be dispatched to the SRM are
    a subset of those enrolled for the FCL. Another future
    reply to this note and the release notes will define which
    directives are available for use as action directives by
    node child entities or Management Objects subsidiary to the
    common agent.
    
    wally
T.RTitleUserPersonal
Name
DateLines
3008.1Datatype listTOOK::PURRETTATue May 19 1992 20:28147
						To CMIP			From CMIP
	MCC_K_DT_NULL 		0		Not supported		Not supported
						MCC_K_ID_NULL

	MCC_K_DT_BOOLEAN 	1		OK			OK
	MCC_K_DT_OCTET_STRING 	2		OK			OK
	MCC_K_DT_LATIN1STRING 	3		OK			OK
	MCC_K_DT_SIMPLE_NAME 	4		OK			OK
	MCC_K_DT_FULL_NAME 	5		OK			OK
	MCC_K_DT_FILE_SPEC 	6		OK			OK
	MCC_K_DT_UID 		8		OK			OK
	MCC_K_DT_VERSION 	9		OK			OK
	MCC_K_DT_ENUMERATION 	10		OK			OK		
	MCC_K_DT_BITSET 	11                  MCC supports BIT Set
	MCC_K_DT_RECORD 	13		OK			OK
	MCC_K_DT_VAR_RECORD 	14			Not tested
	MCC_K_DT_SEQUENCE 	15		OK			OK
	MCC_K_DT_SET 		16		OK			OK
	MCC_K_DT_ADDRESS_NSAP 	18		OK			OK
	MCC_K_DT_ADDRESS_NET 	19		OK			OK
	MCC_K_DT_ADDRESS_AREA 	20		OK			OK
	MCC_K_DT_ADDRESS_PREFIX 21		OK			OK
	MCC_K_DT_ADDRESS_TSEL 	22		OK			OK
	MCC_K_DT_ADDRESS_DTE 	23		OK			OK
	MCC_K_DT_PHASE4NAME 	24		OK			OK
	MCC_K_DT_PHASE4ADDRESS 	25		OK			OK
	MCC_K_DT_COMPONENT 	27      		No support
	MCC_K_DT_IMPLEMENTATION 28              XXXX                    OK
	MCC_K_DT_INTEGER8 	29              OK			OK
	MCC_K_DT_INTEGER16	30		OK			OK
	MCC_K_DT_INTEGER32	31		OK			OK
	MCC_K_DT_INTEGER64	32		OK			OK
	MCC_K_DT_UNSIGNED8	33		OK			OK
	MCC_K_DT_UNSIGNED16	34		OK			OK
	MCC_K_DT_UNSIGNED32	35		OK			OK
	MCC_K_DT_UNSIGNED64	36		OK			OK
	MCC_K_DT_COUNTER16	37		OK			OK
	MCC_K_DT_COUNTER32	38		OK			OK
	MCC_K_DT_COUNTER48	39		OK			OK
	MCC_K_DT_COUNTER64	40		OK			OK
	MCC_K_DT_OCTET		45		OK			OK
	MCC_K_DT_HEXSTRING	46		OK			OK
	MCC_K_DT_BIN_ABS_TIM	47		OK			OK
	MCC_K_DT_CHAR_ABS_TIM	48		OK			OK
	MCC_K_DT_BIN_REL_TIM	49		OK			OK
	MCC_K_DT_CHAR_REL_TIM	50		OK			OK
	MCC_K_DT_SET_OF		52		OK			OK
	MCC_K_DT_SEQUENCE_OF	53		OK			OK
	MCC_K_DT_RANGE		54	DNA5 supports it, problem is else where
	MCC_K_DT_FULL_ENTITY	55		OK??	 Need Testing	OK??
	MCC_K_DT_LOCAL_ENTITY	56		OK??	 Need Testing	OK??
	MCC_K_DT_TOWERSET	57		XXXX			OK
	MCC_K_DT_END_USER_SPEC	58		OK			OK
	MCC_K_DT_ENTITY_CLASS 	60		OK			OK
	MCC_K_DT_BITSTRING 	62	           MCC supports bit set
	MCC_K_DT_ID802_SNAP 	68		OK			OK
	MCC_K_DT_ID802_SAP 	69                 NO support....
	MCC_K_DT_IDENETV2_TYPE 	70		OK			OK
	MCC_K_DT_ID802 		71		OK			OK
	MCC_K_DT_IPADDRESS 	73		OK			OK
	MCC_K_DT_INTERNET_NAME 	74		   NO support....
	MCC_K_DT_STRINGSET 	94		   NO support....

--------------------------------------------------------
	These data types have no meaning in CMIP

	MCC_K_DT_SUBRANGE 	12
	MCC_K_DT_EXPRESSION 	26
	MCC_K_DT_LCOUNTER16	41
	MCC_K_DT_LCOUNTER32	42
	MCC_K_DT_VMS_ERROR	43
	MCC_K_DT_MCC_ERROR	44
	MCC_K_DT_NSCTS		51
	MCC_K_DT_MCC_REPLY	59
	MCC_K_DT_DIRECTORY_SPEC 61
	MCC_K_DT_FLOATF 	63
	MCC_K_DT_ATTRIB_LIST 	66
	MCC_K_DT_ATTRIBUTEIDLIST 67
	MCC_K_DT_REAL 		72
	MCC_K_DT_MCCMESSAGE 	75
	MCC_K_DT_RESERVED_DO_NOT_USE_1 76
	MCC_K_DT_RESERVED_DO_NOT_USE_2 77
	MCC_K_DT_RESERVED_DO_NOT_USE_3 78
	MCC_K_DT_RESERVED_DO_NOT_USE_4 79
	MCC_K_DT_EVENT_REPORT 	80
	MCC_K_DT_EVENTIDLIST 	81
	MCC_K_DT_ATTRIB 	82
	MCC_K_DT_ATTRIB_IDENTIFIER 83
	MCC_K_DT_TIME24 	84
	MCC_K_DT_USAGE_STATE 	85
	MCC_K_DT_ADMIN_STATE 	86
	MCC_K_DT_REPAIR_STATUS 	87
	MCC_K_DT_INSTAL_STATUS 	88
	MCC_K_DT_AVAIL_STATUS 	89
	MCC_K_DT_CONTROL_STATUS 90
	MCC_K_DT_OPER_STATE 	91
	MCC_K_DT_SNARESOURCENAME 92
	MCC_K_DT_QUALIFIEDSNANAME 93
	MCC_K_DT_OSERROR 	95
	MCC_K_DT_MESSAGE 	75

						To CMIP			From CMIP
         APPL_K_OCTET           4    
         APPL_K_CHAR_TIME       16  
         APPL_K_BIN_TIME        17   
         APPL_K_CHAR_REL_TIME   18  
         APPL_K_BIN_REL_TIME    19 
         APPL_K_LTN_STR         20 
         APPL_K_SIMPLE_NAME     26 
         APPL_K_FULL_NAME       27 
         APPL_K_UID             28 
         APPL_K_KNOWN           29 
         APPL_K_FULL_ENT        30            Not fully tested 
         APPL_K_LOCAL_ENT       31   	      Not fully tested
         APPL_K_DEFAULT         32  
         APPL_K_VERSION         33  
         APPL_K_ID              34  
         APPL_K_DTE             35 
         APPL_K_FILE_SPEC       36 
         APPL_K_NSAP            37 
         APPL_K_ENT_TITLE       38 
         APPL_K_AREA_ADDR       39 
         APPL_K_COUNTER16       40 
         APPL_K_COUNTER32       41 
         APPL_K_COUNTER64       42 
         APPL_K_COUNTER         42 
         APPL_K_ADDRE_PRE       43
         APPL_K_TOWERSET        44
         APPL_K_END_USER        45
         APPL_K_TSEL            46 
         APPL_K_IV_NAME         47 
         APPL_K_IV_ADDR         48 
         APPL_K_IMPLEMENT       49  	Not supported 		 Ok
         APPL_K_VERSION_EDIT    50 
         APPL_K_COMPONENT       51
         APPL_K_DNSUID          52 
         APPL_K_ENT_CLASS       53 
         APPL_K_HEX_STR         54 
         APPL_K_FLOOR           55 	Not supported as stand alone data type
         APPL_K_PROCOL_TOWER    56 	Not supported as stand alone data type
         APPL_K_RANGE           60 	Needs testing. Code is broken outside AM
         APPL_K_CLASSEVENT      61 	Gfilter... not supported
         APPL_K_INSTANCEEVENT   62 	Sfilter... not supported
         APPL_K_IDENETV2_TYPE   66 
         APPL_K_IEEE802_SNAP    67  
         APPL_K_IPADDRESS       81
3008.2Directive (Verb) listTOOK::PURRETTATue May 19 1992 20:4821
The following MCC Directives have entry points defined in the DNA5 AM.

ADD		REMOVE		SET		SHOW

Action directives:

BACKTRANSLATE	BLOCK		BOOT		CANCEL
CHANGE		CLEAR		CLOSE		COMMON
COMPARE		CONNECT		COPY		CREATE
DELETE		DIAGNOSE	DIALOUT		DIRECTORY
DISABLE		DISCONNECT	DUMP		ECHO
EDITACL		ENABLE		EVALUATE	GETNIF
GETSIF		IGNITE		IGNORE		INITIALIZE
LINK		LISTEN		LOAD		LOOP
OPEN		PASS		PERFORM		PING
POPULATE	PURGE		QUERY		RENAME
RESET		RESTRICT	RESUME		SHUT
SHUTDOWN	START		STARTLOOP	STOP
STOPLOOP	SUSPEND		SYNCHRONIZE	TEST
TESTACL		TESTEVENT	TRIGGER		UNLINK
UPDATE		WILDCARD
3008.3Can you turn these into QARs?MARVIN::COBBGraham R. Cobb (Wide Area Comms.), REO2-G/H9, 830-3917Tue Jun 02 1992 13:1925
A few major comments:

1) Local  entity  names  are  very, very important.  They are fundamental to
setting  up  any  Phase  V  entities.  Do you need some help to complete the
testing?

2) When  will the event filtering datatypes be supported? They are mandatory
to be able to manage event logging.

3) Why  does TowerSet have "XXXX" in the "To CMIP" column? Setting towersets
is  mandatory  for both event logging management and loopback testing on any
standalone router or gateway (they do not have DNS).

4) Ranges  are  required for management of X.25.  If they are broken outside
DNA5 they need to be fixed.

A couple of very small comments:

5) NSCTS  certainly  *does*  have  meaning  in  CMIP (NETMAN used to call it
"DNSUID").  I would have thought it was required for managing DNS.

6) Implementation  ought  to be supported for input as it could be specified
in a filter.

Graham
3008.4QAR 3097TOOK::MINTZErik Mintz, dtn 226-5033Tue Jun 02 1992 14:382
I have entered these as a group, QAR 3097.

3008.5QAR 3097 - answer (deferred)TOOK::MINTZErik Mintz, dtn 226-5033Wed Jun 10 1992 03:365
The answer to QAR 3097 indicates that this datatype work has be
scheduled for after the release of V1.2.  The lists in earlier replies
were intended as a preview of the information to be included in
the V1.2 release notes.