Conference azur::mcc

2644.0. "Decserver 300 private MIB" by PRSSOS::BONNAFE (Guy BONNAFE - CSC France) Fri Mar 27 1992 14:13

	DECmcc V1.1 and SNMP AM V1.1

	In the kit DS3021, saveset B ( DECserver 300 V2.1 ), a private MIB 
	named CHAR-MIB.TXT is provided. I would try to extend my dictionary in
	order to include this part of the MIB ( experimental part ).
	By using the command procedure MCC_TCPIP_MTU.COM ( after cleaning
	the MIB of all extra characters ! ), I get an error during the phase 2. 

	Did anybody already try this operation ? Is there a way to trace
	the work of the MSL Translation Tool ?
	Regards,
	Guy.



===========================================================================
$ @MCC_TCPIP_MTU.COM

Welcome to the DECmcc TCPIP MIB Translator Utility driver procedure T1.1.0

  27-MAR-1992 16:53:44

This procedure operates in a 3 phased manner --
Phase 1 translates the MIB definition into a management specification.
Phase 2 (as an option) translates the management specification into a
  dictionary loadable file and loads the dictionary.
Phase 3 (as an option) builds the parse tables.
  (Phase 3 may only be performed if Phase 2 was selected to be performed)

Phase 1 -- Enter name(s) of file(s) to translate
  (separate multiple files by commas): CHAR-MIB.TXT
Phase 2 -- Do you want to update the DECmcc data dictionary? (Y/N) [N]: y
Phase 3 -- Do you want to build the DECmcc parse tables? (Y/N) [N]:

Issuing following command:
  $ MTU = "$ SYS$SYSTEM:MCC_TCPIP_MTU.EXE"

                                   * * *

Beginning Phase 1 for file SUPMCC$DKA200:[MCC]CHAR-MIB.TXT;
Now starting to run the MIB translator...
This may take approximately 1-5 minutes.
  27-MAR-1992 16:54:00
Issuing following command:
  $ MTU SUPMCC$DKA200:[MCC]CHAR-MIB.TXT;
Entity Model tree is being pruned.
The following non-leaf objects are being removed:
Child entity wellKnownProtocols
Child entity protocolOther
Child entity protocolTelnet
Child entity protocolRlogin
Child entity protocolLat
Child entity protocolX29
Child entity protocolVtp
MIB translation completed successfully.
  27-MAR-1992 16:54:07
Phase 1 for file SUPMCC$DKA200:[MCC]CHAR-MIB.TXT; completed.

Beginning Phase 2 for file SUPMCC$DKA200:[MCC]CHAR-MIB.TXT;
Now copying "INCLUDE" .MS files from MCC_COMMON to default directory.
Now starting to run MSL translator...
This may take approximately 1-10 minutes.
  27-MAR-1992 16:54:09
Issuing following command:
  $ MANAGE/TOOLKIT/SPECIFICATION SUPMCC$DKA200:[MCC]CHAR-MIB.MS
DECmcc Management Specification Language Translation Tool
               Version V1.1.1

%SCN-F-CASERANGE, No case clause was specified for current index

  27-MAR-1992 16:54:16

Procedure terminated in error.

	Guy,
		Can you send me the character mib you are using and the
	corresponding MS files generated by MTU? You can mail it to 
	MOLAR::BOSE

		BTW, we are including both the experimental and standard 
	character mibs on the V1.2 kit, and they both seem to work fine.

	Rahul.

	Guy,
		You've uncovered a restriction in the V1.1 MSL translator.
	The translator cannot handle cases where the level of indirection
	for an attribute's type definition is more than two. Thus the
	following example will cause the MSL translator to break
	with the error message : 
	%SCN-F-CASERANGE, No case clause was specified for current index

	Example :

	TYPE
	  ObjectIdentifier = 17 Latin1String;

	TYPE
	  AutonomousType = 18 ObjectIdentifier;

	TYPE
	  InstancePointer = 19 ObjectIdentifier;

        ATTRIBUTE charPortHardware   = 4 : AutonomousType <<<<<<<<<
            ACCESS     = NONSETTABLE,      
            DISPLAY    = TRUE,
            CATEGORIES = (CONFIGURATION),
            SYMBOL = EX19_2_1_4,
            SNMP_OID = {1 3 6 1 3 19 2 1 4}
        END ATTRIBUTE charPortHardware;

        ATTRIBUTE charSessConnectionId   = 9 :  InstancePointer  <<<<<<<<
            ACCESS     = NONSETTABLE,          
            DISPLAY    = TRUE,
            CATEGORIES = (CONFIGURATION),
            SYMBOL = EX19_3_1_9,
            SNMP_OID = {1 3 6 1 3 19 3 1 9}
        END ATTRIBUTE charSessConnectionId;


	The good news is that this all works in T1.2.xxx.
	The only work-around I can think of is that you edit 
	the .MS file and change the attribute definitions to 

	ATTRIBUTE charPortHardware   = 4 : ObjectIdentifier

	and then translate and load the .MS file.

	Rahul.

    Hi,
    
    I have a customer that is also seeing the error reported in .0.
    
    %SCN-F-CASERANGE, No case clause was specified for current index.
    
    They are trying to incorporate mibs from a package they obtained
    through Hughes LAN Systems.  Is there anything we can do for them or
    should we just tell them to wait for V1.2.
    
    Thanks'
    
    Walt

	Walt,
		As I mentioned in .2, there is a restriction in the V1.1
	MSL translator which does not allow more two levels of indirection
	for an attribute's type definition. This restriction is not present
	in the V1.2 MSL translator.

		You have two choices, either tell your customer to wait
	for V1.2, or hack up the mib to remove the extra indirections (as
	shown in .2). 

	Rahul.