[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
5716.0. "SNMP/Cabletron Problems" by BAHTAT::TAYLOR () Thu Nov 04 1993 07:27
Can anyone help me with this problem before it drives me completely nuts ?
I am implementing DECmcc with a customer who has a large variety of
Cabletron Hubs. At the outset I built all the Cabletron mibs (+ others) into
the dictionary.
After a long process of registering all manner of devices including the hubs
I found that when looking into a particular hub, the Cabletron mib definition
was not visible, whilst the private mib extensions for other snmp devices were
accessible (eg. NAT). Using the dictionary browser everything seems fine for the
Cabletron definitions. Fine I thought, this must be a mismatch between agent
s/w and mib version.
I asked the customer to contact Cabletron and find out what mibs supported
the various device types installed on their Lan. This is what he got back :-
Device Mib(s)
IRM2 RREV2-MI.TXT
MRXI RREV2-MI.TXT
COMMON.TXT
EMME RREV4-MI.TXT
CHASSIS.TXT
CTRON-OID.TXT
CTBRIDGE.TXT
TRAP-MIB.TXT
BRIDGES (NB25) CTRN-BDG.TXT
Having got this list he copied the mib files from the "Cabletron Bulletin
Board", and we checked them against the ones supplied with MCC. COMMON.TXT,
CHASSIS.TXT,CTBRIDGE.TXT,RREV4-MI.TXT all seem to match the ones in the kit,
however the revision levels of all but ctbridge.txt are different.
MCC CABLETRON
CABLETRON_COMMN_MIBDEF.TXT COMMON.TXT
V 1.01 14/8/92 V 1.02 18/1/93
CABLETRON_CHASS_MIBDEF.TXT CHASSIS.TXT
V 1.05 14/8/92 V 1.01 12/10/92
CABLETRON_RREV4_MIBDEF.TXT RREV4-MI.TXT
V 1.30 14/8/92 V 1.34 18/1/93
At this point I decided to start again and install all the "Cabletron" mibs.
The results (and problems) are shown below.
1. CTRN-BDG.TXT doesn't even pass Phase 1 of the compiler. This is the error
message and the contents of the .lis file.
********
Beginning Phase 1 for file DKA700:[MCC.CTRON]CTRN-BDG.TXT;
3-NOV-1993 15:02:42
Now starting to run the MIB Translator ...
This may take approximately 1-5 minutes.
Issuing following command:
$ MTU DKA700:[MCC.CTRON]CTRN-BDG.TXT;
Line 34 : Syntax error
An error occurred while running the MIB Translator.
Check file CTRN-BDG.LIS,
if it exists, for any further information.
Files CTRN-BDG.MS and CTRN-BDG_ENUM.MS
may also have been created; delete these files, as appropriate.
3-NOV-1993 15:02:43
Procedure terminated in error.
*********
DECmcc MIB Translation Utility T1.1.0-A Page 1
Input: dka700:[mcc.ctron]ctrn-bdg.txt; Output: ctrn-bdg.ms, ctrn-bdg_enum.ms
1
2 -- Cabletron Management Information Base
3 -- For the Ethernet Bridge (IRBM, NB25E, and NB20E)
4 -- By: Gayle Delaney
5 -- Revision 0.7
6 -- Date: February 21, 1991
7 --
8 --
9 -- REVISION HISTORY
10 --
11 -- Rev. 0.1 - Initial revision.
12 -- Compatible with versions 0.00.02 and 0.00.03 of the SNMP NB25E
13 -- bridge.
14 --
15 -- Rev. 0.2 - Revised and updated.
16 -- Added Bridgerev1 to object identifiers.
17 --
18 -- Rev. 0.3 - Revised and updated.
19 -- Added PortRuntPackets, PortOversizePackets, and PortFrFilt.
20 -- Changed syntax of all four AcqCreate objects and AcqDelete
21 -- object to INTEGER.
22 -- Changed syntax of all four PermCreate object and PermDelete
23 -- object to INTEGER.
24 --
25 -- Rev. 0.4 - Revised and updated.
26 -- Added trap object identifiers.
27 --
28 -- Rev. 0.5 - Changed certain device and port objects to counter types.
29 --
30 -- Rev. 0.6 - Added AcqSrcAddress and PermSrcAddress.
31 --
32 -- Rev. 0.7 - Updated DeviceRestoreSettings and Traps.
33
34 bridgeRev1 OBJECT
Syntax error at line 34.
*******************************************************************************
2. RREV4-MI.TXT completes Phase 1 ok, but during the MSL translation falls over
with :-
*******
Phase 1 -- Enter name(s) of file(s) to translate
(separate multiple files by commas): DKA700:[MCC.CTRON]RREV4-MI.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 DKA700:[MCC.CTRON]RREV4-MI.TXT;
3-NOV-1993 15:07:24
Now starting to run the MIB Translator ...
This may take approximately 1-5 minutes.
Issuing following command:
$ MTU DKA700:[MCC.CTRON]RREV4-MI.TXT;
Max levels = 11
MIB translation completed successfully.
3-NOV-1993 15:07:39
Phase 1 for file DKA700:[MCC.CTRON]RREV4-MI.TXT; completed.
Beginning Phase 2 for file DKA700:[MCC.CTRON]RREV4-MI.TXT;
Now checking DECmcc data dictionary for subclass cabletron ...
%DAP-S-USE_DICT, Using dictionary file: dka700:[mcc]mcc_fdictionary.dat;4
Found definition.
The definition for the cabletron 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]:
3-NOV-1993 15:07:56
Now starting to run the MSL Translator ...
This may take approximately 1-10 minutes.
Issuing following command:
$ MANAGE/TOOLKIT/SPECIFICATION RREV4-MI.MS
DECmcc Management Specification Language Translation Tool
Version V1.3.0
%MCCMSL-I-MSLLOCATION, Line: 1459, File: RREV4-MI.MS;,
%MCCMSL-E-PARSER, yacc stack overflow: The value "1" is not expected
%MCCMSL-E-ERROR, MSL did not complete successfully, please see previous error
An error occurred while running the MSL Translator.
Check file RREV4-MI.LOG, if it exists, for any further information.
3-NOV-1993 15:08:14
Procedure terminated in error.
%NONAME-E-NOMSG, Message number 04EFB05A
*****************************************************************************
3. RREV2_MI.TXT completes Phase 1 ok, but during the dictionary update falls
over with :-
$ man/tool/dict
%DAP-S-USE_DICT, Using dictionary file: dka700:[mcc]mcc_fdictionary.dat;4
POLYCENTER Dictionary Administrator Program Version V1.3.0
DAP> merge class snmp subclass cabletron from RREV2-MI.com
Percent of file processed = 5%
%DAP-I-LINENUMB, At or near line number 4675.
%DAP-I-CMD_LINE, Command: CREATE CLASS SNMP SUBCLASS CABLETRON SUBCLASS COMMSD
EVICE SUBCLASS COMMON SUBCLASS SYSOIDS SUBCLASS SYSIRMTYPE SUBCLASS SOIDIRMS
NMP CODE 1
%MCC-E-NOENTITY, no corresponding entity instance exists
DAP>
*****************************************************************************
Having loaded the mibs which did not barf in any way + RREV4 from the MCC kit
I deleted and re-registered an EMME. Magic!!! The Cabletron stuff is now there.
No difference with an MRXI or IRM2 device though. This leads me to think that
I really do need the RREV2 mib for these devices. So what can I/we do to get
that particular mib to load ?
What is wrong with the latest RREV4 mib file, which causes the MSL
translation to fail ?
If anyone could take a look at this I would be grateful, and if required I
can provide access to the relevant .com/.ms files.
regards,
Richard.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5716.1 | GiveItToMe,Quick | BIKINI::KRAUSE | European NewProductEngineer for MCC | Wed Nov 10 1993 08:34 | 5 |
| Ok, I'll take it. Copy the MIB files to NACWS2::
Incidentally I just got a Cabletron hub with an IRM2 for a few days.
Therefore I even might be able to try out the MIB.
*Robert
|