[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

2779.0. "SNMP MIB's little flexibility " by WARDLE::REX (Life's not what I thought it was!) Thu Apr 16 1992 09:58

I came across this problem last week....

DECmcc T1.2.4
VMS V5.5

I was loading in 3 sets of CHIPCOM mibs, the original CHIPCOM MIB, another for
CHIPCOM hubs & one for CHIPCOM repeaters.

As I loaded the tree MIBs into DECmcc, they all wanted to use the CHIPCOM field
in the SNMP tree. So as the second and third MIB's were entered they removed all
previouis reference to CHIPCOM.

If a customer wishes to load multiple MIB's from a single vendor, is there any 
way of controlling the TITLE in SNMP terms for each individual MIB so they can 
co-exist ?

&*(

Rex

T.RTitleUserPersonal
Name
DateLines
2779.1suggestionCLAUDI::PETERSThu Apr 16 1992 15:477
How about editing the source MIB and changing the names to
CHIPCOM_HUB and CHIPCOM_REPEATER or CC_HUB and CC_REPEATER.
Then you should be able to add all three to the dictionary
without collisions.  ... Comments from engineering?  Also,
tell chipcom not to do that.  

/Claudia
2779.2New MTU allows you to add multiple mibs from the same vendorMUNDRA::MUNDRAThu Apr 16 1992 20:478
	The latest MTU utility (that went out today with external field
	test, T1.2.7) allows you to add multiple mibs from the same
	vendor.  When adding mibs to the dictionary, if a mib already
	exists for the vendor in the dictionary, it will ask you if you
	want it replaced or augmented.

Satinder Mundra
2779.3AUGMENT does not appear to workSCHOOL::LEKASFrom the Workstation of Tony LekasThu Sep 24 1992 20:12100
	I am working on an addition to the DEC vendor MIB for GIGAswitch.
It will, at least initially, be distributed as a seperate file from the
DEC vendor MIB.  When I try to augment the DEC vendor MIB using MTU I
recieve an error.  See below.  What am I doing wrong?

		Thanks,
		Tony



LEH_$ @mcc_common:MCC_TCPIP_MTU

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

  24-SEP-1992 14:35:38

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): sonoma.mib

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 TONY$ROOT:[W4]SONOMA.MIB;

  24-SEP-1992 14:35:54
Now starting to run the MIB Translator ...
This may take approximately 1-5 minutes.
Issuing following command:
  $ MTU TONY$ROOT:[W4]SONOMA.MIB;
Entity Model tree is being pruned.
The following non-leaf objects are being removed:
Child entity decMIBextension
Child entity elanext
Child entity giga
Child entity gigaFiltByRef
Child entity gigaFiltSw
MIB translation completed successfully.
  24-SEP-1992 14:36:05

Phase 1 for file TONY$ROOT:[W4]SONOMA.MIB; completed.

Beginning Phase 2 for file TONY$ROOT:[W4]SONOMA.MIB;

Now checking DECmcc data dictionary for subclass dec ...
Using dictionary file: sonoma_sw:[mcc]mcc_fdictionary.dat;3
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]: y

Now copying "INCLUDE" .MS files from MCC_COMMON to default directory ...
Copy completed.

  24-SEP-1992 14:36:28
Now starting to run the MSL Translator ...
This may take approximately 1-10 minutes.
Issuing following command:
  $ MANAGE/TOOLKIT/SPECIFICATION SONOMA.MS
DECmcc Management Specification Language Translation Tool
               Version V1.2

Scan of MS file has completed successfully
MSL translation completed successfully.
  24-SEP-1992 14:37:14

Editing SONOMA.COM ...
Editing of SONOMA.COM completed.

  24-SEP-1992 14:37:25
Now starting to update the DECmcc data dictionary ...
This may take approximately 1-15 minutes.
Issuing following command:
  $ MANAGE/TOOLKIT/DICTIONARY LOAD FROM SONOMA.COM
Using dictionary file: sonoma_sw:[mcc]mcc_fdictionary.dat;3
At or near line number 6.
Command: CREATE CLASS SNMP  SUBCLASS DEC  SUBCLASS EMA CODE 2
 specified entity definition exists already

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

  24-SEP-1992 14:37:30

Procedure terminated in error.
Message number 0326CEDA
2779.4Not possible to AUGMENT the DEC Vendor MIB!VCSESU::WADEBill Wade, VAXc Systems & Support EngFri Oct 02 1992 13:5725
    After speaking with Dan Carr about this I was made aware of the 
    following -
                             
    	- DECmcc does not support more than ~10 levels of child entities
    	
    	- The DEC Vendor MIB (DVM) has >10 levels so levels without leafs are
    	  "pruned" when the MIB is loaded
        
    	- Pruning causes a problem and it is NOT possible to AUGMENT the 
    	  DVM 
    
    	- If the DVM is loaded and you want to load a MIB that extends the
    	  DVM you have to edit the DVM, append your MIB and load the
    	  conglomeration
    
    	- If you buy another Digital product that extends the DVM you have
    	  to repeat the above and get real intimate with the MIBs
    
    	
    This should be QARed as it causes a real problem for products that 
    extend the DVM like the GIGAswitch and DECnis.   Can we get an estimate 
    on when it will be fixed?  
    
    Bill
    
2779.5Already doneRACER::daveAhh, but fortunately, I have the key to escape reality.Mon Oct 05 1992 11:273
This has been QAR'ed, more than once.
I have a QAR that was assigned to "ANDERSEN"
and am waiting on the result.
2779.6YAHEY::BOSEMon Oct 05 1992 20:0124
	RE .4

>>    	- DECmcc does not support more than ~10 levels of child entities

	The DECmcc dictionary routines can handle a maximum dictionary AES
	depth of 10. Now, if you have a directive declared with response 
	arguments, that takes up 4 levels :

   Class (1) : 
     Directive (6) : SHOW		---------------------> 1
      Response (8) : SHOWSUCCESS	---------------------> 2
	 Argument (4) : ATTRIBUTES	---------------------> 3
           Definition (3) : PRESENTATION_NAME  --------------> 4
           Definition (3) : VALUE_DATA_TYPE
           Definition (3) : VALUE_LENGTH
           Definition (3) : DISPLAY

	So the maximum depth of child entities supported is actually 6.
	Most DEC vendor mibs have a depth of 9 below the DEC enterprise
	object. Which means that pruning is forced, thereby rearranging the 
	original mib objects. This prevents subsequent merging of mibs 
	belonging to the same enterprise subtree.

	Rahul.
2779.7Where's the QAR?CHRISB::BRIENENDECmcc LAN and SNMP Stuff...Mon Oct 05 1992 23:0613
RE: 2779.5 (RACER::dave)

> This has been QAR'ed, more than once.
> I have a QAR that was assigned to "ANDERSEN"
> and am waiting on the result.

 I went looking for this QAR on MUSEUM (MCC012_INT/EXT and MCC013_INT/EXT)
and NACQAR (MCC_INTERNAL and MCC_EXT_V1_2) and couldn't find it.

 I'm wondering if our trusty QAR system (on MUSEUM) is losing individual
QARs (QAR # 00005, for one, appears to be missing...).

						Chris
2779.8SCHOOL::LEKASFrom the Workstation of Tony LekasTue Oct 06 1992 12:274
Tell me how to enter a QAR against DECmcc and I'll enter a new one if the
existing one can't be found.

		Tony
2779.9Filed as QAR#18 - MUSEUM MCC013_INTCHRISB::BRIENENDECmcc LAN and SNMP Stuff...Thu Oct 08 1992 15:3813
I've taken the liberty of filing a QAR in the MUSEUM MCC013_INT
database (QAR#018).

The QAR filed includes notes 2779.3, .4, and .6 ...

From what I hear, Dan Carr and Rahul Bose have come up with a
possible solution involving modifications to MTU for V1.3 whereby
the pruning of the DEC VENDOR MIB (would be done differently than
for other mibs).

Maybe Dan can provide some additional details about this...