| 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 |
I've got some mibs compiled into MCC for an Artel galactica bridge.
This gives me access to the Artel extensions, but my customer wants
to see some 802.1d information, which is accessible via the agent on
the bridge.
Is the 802.1d mib built into MCC, and if not, do I also need to
compile the bridge extensions to MIB-II along with the 802dot1d
extensions, into mcc?
-Craig
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 6000.1 | Load bridge MIB | BIKINI::KRAUSE | CSC Network Management/Hubs | Fri May 20 1994 08:41 | 4 |
You need to load BRIDGE_STD_MIBDEF.TXT. This should give you all the variables you need. 802.1d is Spanning Tree. *Robert | |||||
| 6000.2 | What would be the difference between Bridge and 802.1d | NYOS02::PLUNKETT | Fri May 20 1994 13:30 | 16 | |
After doing a little reading of "The Simple Times", and browsing the
notes in the SNMP conference, I am under the impression that 802.1d
and the Bridge MIB are one and the same, according to RFC1493.
RFC1493 obsoletes RFC1286, which is described as the Bridge MIB, and
I compiled a MIB provided by Chipcom referencing RFC1286, that gave
me my Spanning Tree information, which is really what the customer
was looking for. So for my purposes, I got what I needed, but would
still like to know what the difference would be between the two
items mentioned in the previous note.
I made the *mistake* of describing RMON to my customer, and now he's
thinking about adding that MIB. I'd better stay on my toes with
this MIB stuff.
-Craig
| |||||