| 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 |
Help.! MCC still fails when trying to install the DEC_SERV.txt
accounting MIB. This person suggests that I delete the enterprise
and reload everything. One question: How?
many thanks if you can help even a little,,,,,
mike (the lost sole in MCC land)
<<< NOTED::DISK$NOTES6:[NOTES$LIBRARY_6OF4]MCC.NOTE;2 >>>
-< DECmcc - Internal Use Only >-
================================================================================
Note 6179.1 MIB install failure 1 of 1
DV780::SMITHG 10 lines 28-NOV-1994 12:04
-< Previous MIB load w/ prune >-
--------------------------------------------------------------------------------
I've run into similar errors then the first MIB for the enterprise, in
this case DEC, or a previous MIB load was done with the prune option =
yes. I think what's happening is that the accounting MIB load is
looking for a child that doesn't exist. What I had to do is delete the
enterprise and begin the DEC MIB loads again.
You are not getting any messages about the MIB being too deep and
forced pruning occuring are you?
Gary
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 6197.1 | How to delete a private MIB in MCC | TAEC::IRIBE | Thu Dec 22 1994 05:44 | 6 | |
I well know how to delete a private mib in the dictionary, but this is for TeMIP Framework OSF/1. You can try it. Be root and enter the following command : mcc_msl -r"1.3.12.2.1011.2.22.1.18.xxx" where xxx = 5000 + enterprise id. Good luck JMI | |||||
| 6197.2 | ABACUS::BUKOWSKI | Thu Dec 22 1994 10:09 | 5 | ||
What is the VMS equivalent?
thanks,
Mike
| |||||
| 6197.3 | PRSSOS::BONNAFE | Guy BONNAFE - CSC France | Thu Dec 22 1994 13:11 | 46 | |
Mike,
My advice is still the same : contact NAS engineering and try to
obtain a correct mib ...
The correct hierarchy to compile private mibs is as follows :
iso(1).org(3).dod(6).internet(1)
|
private(4)
|
enterprises(1)
|
dec(36)
|
ema(2)
|
decMIBextension(18)
So you can see in the accounting mib that :
1/ private and enterprises are in reverse order.
2/ mib-extensions-1 is defined as { ema 18 } : the correct name
should be decMIBextension instead of mib-extensions-1 !!!
The first error is handled by MCC compiler because the top hierarchy
is already defined into MCC dictionary.
The second error is detected only if a DEC private mib, using
decMIBextension, is already added in the dictionary ( all hub900
stuff for example ). Otherwise, the mib should be compiled without
any errors. Of course, you'll face the same problem if you try to
add a new DEC private mib later.
And don't forget to comment out sysuptime in the last trap definition.
To remove a mib from MCC dictionary :
$ manage/toolkit/dictionary
DAP> delete class snmp subclass <to_be_removed>
DAP> exit
Good luck,
Guy.
| |||||
| 6197.4 | thank you | BRAT::BUKOWSKI | Tue Dec 27 1994 17:07 | 6 | |
RE:-1
Thank you very much. The breif explanation of the MIB tree / object
Identifiers put me on track. It installed fine.
Mike
| |||||