Conference azur::mcc

4318.0. "T1.3 tcpip mtu problem/bug?" by ZPOVC::RAMARAJ () Mon Dec 28 1992 19:51

I've got the DECHUB90 mib file and compiled it using the T1.3 MTU utility on
VMS.

The compiling is done successfully.

The Browser does show the dec subclass tree.  The FCL also recognises the 
dec subclass tree.

In the iconic map the subclass dec does NOT appear at all when viewing a 
DECagent.  Is it interpreting wrongly?  Is the problem in the SNMP AM, the 
DECHUB90 mib file or the MTU utility?


In V1.2 it was ok?

Another  problem:

I compiled the DEC_elan mib provided in the kit.  Later I compiled the DECHUB90
mib, with update dictionary and AUGMENT option.  There is no syntax error 
but after some time, it terminates with an error updating the dictionary.

The same happens if DECHUB90 is compiled and then the DEC_ELAN20 mib.

Log file is attached for the second case.


Raj
DEC Singapore
------------------------------

Welcome to the DECmcc TCP/IP MIB Translator Utility driver procedure T1.3.0

  28-DEC-1992 22:56:50

This procedure operates in a 2 phased manner --
Phase 1 translates a MIB definition into a management specification.
Phase 2 (as an option) translates the management specification into a
  dictionary loadable file and updates the DECmcc data dictionary.

Phase 1 -- Enter name(s) of file(s) to translate
  (separate multiple files by commas): dec_elan20_mibdef.txt

Phase 1 -- (prune option):
  You have the option to PRUNE the entity model tree created by the
    MIB Translator.
  Pruning will cause child entities without attributes to be discarded.
Do you want to PRUNE the entity model tree? (Y/N) [N]: 

Phase 1 -- (help generation option):
Do you want to build HELP text from the mib ? (Y/N) [N]: 

Phase 2 -- Do you want to update the DECmcc data dictionary? (Y/N) [N]: y

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

                                   * * *

(Now processing file # 1 out of a list of 1 file(s) ...)

Beginning Phase 1 for file SYS$COMMON:[MCC]DEC_ELAN20_MIBDEF.TXT;

  28-DEC-1992 22:57:08
Now starting to run the MIB Translator ...
This may take approximately 1-5 minutes.
Issuing following command:
  $ MTU SYS$COMMON:[MCC]DEC_ELAN20_MIBDEF.TXT;  

Max levels = 8

Too many levels. Forced pruning of Entity Model will occur.

Entity Model tree is being pruned.

The following attributeless entities will be removed:

Child entity decMIBextension

Child entity elanext

Child entity efddi

Child entity efddiSMT

Child entity efddiMAC

Child entity efddiPORT

Child entity esystem

Child entity einterfaces

Child entity ebridge

Child entity ebrInterfaces

Child entity ebrTwoPortStatic

Child entity ebrMultiPortStatic

Child entity ebrMultiProtoFilt

Child entity ebrMultiFiltSw

Child entity ebrNTP

Child entity eauth
MIB translation completed successfully.
  28-DEC-1992 22:57:35

Phase 1 for file SYS$COMMON:[MCC]DEC_ELAN20_MIBDEF.TXT; completed.

Beginning Phase 2 for file SYS$COMMON:[MCC]DEC_ELAN20_MIBDEF.TXT;

Now checking DECmcc data dictionary for subclass dec ...
%DAP-S-USE_DICT, Using dictionary file: sys$common:[mcc]mcc_fdictionary.dat;5
Found definition.

The definition for the dec MIB
  already exists in the DECmcc data dictionary.
You have the option of REPLACING or AUGMENTING this definition.

Do you want to REPLACE the existing definition? (Y/N) [Y]: n

Do you want to AUGMENT the existing definition? (Y/N) [Y]: 

  28-DEC-1992 22:57:48
Now starting to run the MSL Translator ...
This may take approximately 1-10 minutes.
Issuing following command:
  $ MANAGE/TOOLKIT/SPECIFICATION DEC_ELAN20_MIBDEF.MS

DECmcc Management Specification Language Translation Tool

               Version T1.3.0


%MCCMSL-S-NORMAL, Scan of MS file has completed successfully
MSL translation completed successfully.
  28-DEC-1992 22:59:45

  28-DEC-1992 22:59:45
Now starting to update the DECmcc data dictionary ...
This may take approximately 1-15 minutes.
Issuing following command:
  $ MANAGE/TOOLKIT/DICTIONARY MERGE CLASS SNMP SUBCLASS dec FROM DEC_ELAN20_MIBDEF.COM
%DAP-S-USE_DICT, Using dictionary file: sys$common:[mcc]mcc_fdictionary.dat;5

Percent of file processed =   5%
Percent of file processed =  10%
Percent of file processed =  15%
%DAP-I-LINENUMB, At or near line number 5740.
%DAP-I-CMD_LINE, Command: CREATE CLASS SNMP  SUBCLASS DEC  SUBCLASS EMA  SUBCLASS ESYSCHAR  SUBCLASS ESYSTRAPADDRESSTABLE CODE 1
Using parse table log file: sys$common:[mcc]mcc_fdictionary.log;17

Building containment tree file


Containment tree file built, objects=48712, size = 451556

Reading parse table file: sys$common:[mcc]mcc_fdictionary.bpt;20

Please wait while parse tables are updated

  Processing entity 
18 
5036 


%MCCPTB-I-NOENTRY, No dictionary entries found. 

   No attributes defined for entity class. 

  Processing entity 
18 
5036 
2 


%MCCPTB-I-NOENTRY, No dictionary entries found. 

   No attributes defined for entity class. 

  Processing entity 
18 
5036 
2 
1 


  Processing entity 
18 
5036 
2 
1 
1 


  Processing entity 
18 
5036 
2 
1 
2 


  Processing entity 
18 
5036 
2 
2 


  Processing entity 
18 
5036 
2 
2 
1 


  Processing entity 
18 
5036 
2 
3 


  Processing entity 
18 
5036 
2 
3 
1 


  Processing entity 
18 
5036 
2 
3 
2 


  Processing entity 
18 
5036 
2 
3 
3 


  Processing entity 
18 
5036 
2 
4 


  Processing entity 
18 
5036 
2 
5 


  Processing entity 
18 
5036 
2 
6 


  Processing entity 
18 
5036 
2 
7 


  Processing entity 
18 
5036 
2 
8 


  Processing entity 
18 
5036 
2 
9 


  Processing entity 
18 
5036 
2 
10 


  Processing entity 
18 
5036 
2 
11 


  Processing entity 
18 
5036 
2 
12 


  Processing entity 
18 
5036 
2 
13 


  Processing entity 
18 
5036 
2 
14 


  Processing entity 
18 
5036 
2 
15 


  Processing entity 
18 
5036 
2 
16 


  Processing entity 
18 
5036 
2 
16 
1 


Writing parse table file.  Please wait...

Created parse table file: sys$common:[mcc]mcc_fdictionary.bpt;21

Parse table build complete. 
%MCC-E-NOENTITY,  no corresponding entity instance exists 

An error occurred while trying to update the DECmcc data dictionary.

  29-DEC-1992 00:52:12

Procedure terminated in error.
%NONAME-E-NOMSG, Message number 0326CF0A

	Raj,

>>In the iconic map the subclass dec does NOT appear at all when viewing a 
>>DECagent.  Is it interpreting wrongly?  Is the problem in the SNMP AM, the 
>>DECHUB90 mib file or the MTU utility?

		In V1.3 the iconic map will only display the SNMP child
	entities which are supported by the agent. For some reason DECmcc
	thinks that the DEC mib is not supported by the DECagent.

		Keep in mind that the following must be true for the above 
	to work correctly.

		1) The SNMP entity must be re-registered after installing
		   T1.3.0.

		2) The registration must not be partial. For partially
		   registered entities none of the mib extensions will show
		   up as child entities of SNMP.

		3) At the time of registration, the dec extension of the
		   SNMP agent on the DECagent was accessible from the MCC
		   station.

	If you are absolutely sure that all the three conditions are met, 
	then file a QAR against the SNMP AM.


>>Another  problem:

>>I compiled the DEC_elan mib provided in the kit.  Later I compiled the DECHUB90
>>mib, with update dictionary and AUGMENT option.  There is no syntax error 
>>but after some time, it terminates with an error updating the dictionary.

	When you are augmenting an existing mib in the dictionary with 
	a branch of the mib, you have to make sure that both the mibs
	have not been pruned. You should should say NO to the question about 
	pruning. This will allow the different levels in the mib tree to
	remain intact and match up during augmentation.

	However, you need to keep in mind that you may exceed the maximum
	allowable levels in the dictionary when you choose not to prune.
	The field test update kit will be able to handle a lot more levels
	in the dictionary, and you might want to wait for it.

	Rahul.		

    
    Looks like you need to append the two MIB files then run mtu.  
    
    Hopefully the new 1.3 field test will support the number of levels in
    the Digital Vendor MIB.