Conference azur::mcc

This is one of my vavourites :-}

In short, you have to mangle the MIB a bit for it to be compilable. This 
is the case for almost every MIB I've ever seen...

>Variable ifAdminStatus in trap defn. backupLinkTrap12 not previously defined

ifAdminStatus is in the mib-2 subtree. MTU cannot import variables from
other MIBs, so the only way to get this compiled is to remove the
offending variables from the trap definition. 

>Ok no problem, because first of all, he should compile two files 
>(RFC1213.TXT and RFC1516.TXT) which will give the definition of the missing 
>variables.

RFC1213 is mib-2 and is already loaded in MCC. You cannot re-load it.
RFC1516 is the standard repeater MIB and should be compilable. The file 
RFC1516.TXT, however, usually is the RFC text with explanations and 
"nice" page formatting. So have a close look at it to make sure it 
contains *only* the MIB definition.

If you can't figure it out, send it to the MIB doctor (me, if all else 
fails :-).

*Robert

Hi,

Many thanks to Robert for the details about rfc1213.

I did sucessfully compile rfc1516.txt but after that operation I experienced 
the same symptom with HP-ICF.txt.

There are many missing variables like: rptrPortAdminStatus and so on.
Then I found that many of these were described in rfc1368.txt:
			
				SNMP-REPEATER-MIB DEFINITIONS

and in HP-MIBDEF.txt so I did compile this two files.

Well at this point the only variables that are not present in the dictionnary 
are : IfAdminStatus and rptrPortAdminStatus. I commented this specific part of 
HP-ICF.txt to avoid the error message and tried again and now I have got another
error:

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

  10-MAY-1994 09:46:42

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): $DISK1:[MOINET]HP-ICF.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 $DISK1:[MOINET]HP-ICF.TXT;

  10-MAY-1994 09:46:53
Now starting to run the MIB Translator ...
This may take approximately 1-5 minutes.
Issuing following command:
  $ MTU $DISK1:[MOINET]HP-ICF.TXT;
Table event does not have any associated index.
Table event does not have any associated index.
Table icfCommon does not have any associated index.
Table stp does not have any associated index.
Table icfBridge does not have any associated index.
Table icfBridge does not have any associated index.
Table icfBridge does not have any associated index.
Table icfBridge does not have any associated index.
Table icfBridge does not have any associated index.
Table icfBridge does not have any associated index.
Table icfBridge does not have any associated index.
Table icfHub does not have any associated index.
Table icfHub does not have any associated index.
Table icfHub does not have any associated index.
Max levels = 7
MIB translation completed successfully.
  10-MAY-1994 09:47:28

Phase 1 for file $DISK1:[MOINET]HP-ICF.TXT; completed.

Beginning Phase 2 for file $DISK1:[MOINET]HP-ICF.TXT;

Now checking DECmcc data dictionary for subclass hp ...
%DAP-S-USE_DICT, Using dictionary file: $disk1:[mcc_common]mcc_fdictionary.dat;1
Found definition.

The definition for the hp 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]:y

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

  10-MAY-1994 09:47:51
Now starting to run the MSL Translator ...
This may take approximately 1-10 minutes.
Issuing following command:
  $ MANAGE/TOOLKIT/SPECIFICATION HP-ICF.MS
DECmcc Management Specification Language Translation Tool
               Version V1.3M-01

%MCCMSL-I-MSLLOCATION, Line: 70, File: HP-ICF.MS;,
%MCCMSL-E-ID_CONFLICT, Object name or code conflicts with another object
        at the same location in the dictionary
%MCCMSL-E-ERROR, MSL did not complete successfully, please see previous error
An error occurred while running the MSL Translator.
Check file HP-ICF.LOG, if it exists, for any further information.

  10-MAY-1994 09:47:56

Procedure terminated in error.
%NONAME-E-NOMSG, Message number 04EFB05A

I do not understand why MTU is not able to replace an entry in the dictionnary.
I probably did something in the wrong way ??

Could somebody help me ? 
 Thanks in advance 

Paul

PS: I can send you the MIB file via mail if you wish.
 
    

Hi,

I think you must either AUGMENT or REPLACE not both.

In your case if you want to replace you may answer NO to AUGMENT question.

Beno�t DURIF @ VBO

    I apologize for this typing mistake, Robert.
    
    Of course I did not do the both at the same time because it is not
    possible. First I tried to "AUGMENT" and when I saw this error message
    I tried  with the "REPLACE" option and then I get the same error
    message.
    
    Excuse me once again for this confusing description.
    
    Paul
    

>Table event does not have any associated index.

This means that the MIB does not comply to RFC1212 (Concise MIB Format)
and therefore cannot be translated. Every table has to have an INDEX
clause, which is obviously missing from this MIB. 

Get to HP and request a MIB that is RFC1212 compliant!

*Robert

BTW: I just got your outage call in ECSO. We should continue offline (if
at all necessary). The MCC conference is already loaded with this kind
of MIB problems... 

    augmentation versus replacement...
    
    Once you started the agument, which means add the definition in the
    .com file to an existing entity class definition already in the
    dictionary, you probably got some of the definitions loaded in
    before it failed, so when you then tried to replace an existing
    definition, things weren't quite kosher.  You might want to check
    to see if there is any garbage hanging around in your dictionary
    and clean it up using the DELETE command.  Then choose augement
    to load.
    
    	augment -- add definitions (commands/attrs) to an existing entity class
    	load -- add in a new entity hierarchy (or child hierarchy)
    	replace -- remove an existing set of definitions and replace them