| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2420.1 | | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Wed Feb 26 1992 09:41 | 10 |
| The problem is that while the MCC dictionary design allows the visible
"presentation" name of an attribute to be different from its internal
name (for purposes of readability, internationalization, etc), the MIB
templates have no such capability so we are stuck using the attribute
names when we convert MIBS to MSL.
You can go into DAP and change the presentation names if you don't like
them, but the SNMP world is pretty used to those names by now.
|
| 2420.2 | IAB MIBs have standard definitions | MUNDRA::MUNDRA | | Wed Feb 26 1992 15:02 | 12 |
| If the object or attribute you are looking at is a MIB I or MIB II object, then
the definition of it is pretty much standard. This definition, however, still
may not be specific enough for your needs. Any privately defined MIB object
has whatever definition the creator decided for it.
To be more specific, anyone implementing MIBs coming from the IAB (Internet
Activities Board) should be following the standard definitions (as defined
by the IAB) for the objects in that MIB.
IAB MIBs would have RFC #s associated with them.
Satinder
|
| 2420.3 | MSU has Object ID Definitions | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Mon Mar 09 1992 18:36 | 10 |
| The Management Station for Ultrix (MSU) has a very nice description of
each MIB object, plus displays the Object ID along side. This
presented very nicely and is quite helpful. A number of other SNMP network
management applications provide the same capability.
Conversations with Dan Carr indicated that this capability would likely
be possible in a future version. Whether or not it gets a high enough
priority is the question.
-Dan
|