T.R | Title | User | Personal Name | Date | Lines |
---|
4657.1 | V1.3 added MIB Filtering | MOLAR::CHRISB::BRIENEN | Network Management Applications! | Wed Mar 10 1993 16:05 | 26 |
| RE: base note -
> 1. When I add a private MIB extension, it does not show on the map under
> the SNMP MIB clas for the respective entity. However, if I use the
> dictionary browser, the private MIB extension classes do show up.
>
> o o o
>
> Has anyone experienced this type of problem that may shed some light
> on what's wrong.
DECmcc V1.3 has a new feature: MIB filtering.
What this basically means is that MCC will not show MIBs for a selected
entity (as children of SNMP) that don't apply to that entity. Example:
if you've selected an SNMP entity that doesn't have the RMON MIB implemented,
RMON won't appear as an SNMP child, even if the mib is loaded in the
dictionary.
The dictionary browser will display all of the mibs (SNMP child entities)
in the dictionary. A new SNMP AM management attribute ("MIB Extensions
Available") will do likewise. Iconic Map will just display what the
target agent provides.
Chris
|
4657.2 | More Info on .0 | MAIL::CLAYTON | Merlin Clayton DTN 445-7217 | Wed Mar 10 1993 22:03 | 20 |
| I wasn't aware of the new MIB filtering feature, but...
I translated the Chipcom 10-BaseT MIB for a Chipcom 10-BaseT repeater,
and the Proteon P4100 MIB for a Proteon P4100 router and when I select
the respective Chipcom or Proteon entity, neither private MIB extension
shows up as a MIB child entity of the parent.
Is there something else that needs to be enabled that I'm overlooking?
If the target SNMP agent is not compatible with the private MIB class
extension (e.g., MIB definition and agent version mismatch) what would
the expected results be?
Is there a way to over ride the MIB filtering feature just to see if
the private MIB extensions are there?
Thanks for the info thus far.
Merlin
|
4657.3 | try dereg/re-register | TOOK::MCPHERSON | pre-retinal integration | Thu Mar 11 1993 08:03 | 9 |
| Merlin,
Did you register the 10BaseT repeater before or *after* you added the MIB
extension? I may be a little out of date on this, but for the filtering to
work, the object should be registered *after* the MIB extenstion has been
added...
Semper Foo!
/doug
|
4657.4 | Doug's Right Again | MAIL::CLAYTON | Merlin Clayton DTN 445-7217 | Thu Mar 11 1993 09:45 | 18 |
| As usual you're brilliant Doug.
I deregistered and re-registered my Proteon router in the demo center and
the Proteon MIB extension came up. However, my next question is, "Is this
behavior desirable?"
What if, in a real network operations scenario I have a large number of
entities registered that support SNMP standard MIB classes only. Then the
manufacturer enhances their SNMP agent by adding private MIB extensions, or
RMON, etc. After translating the manufacturer's new MIB enhancements and
integrating them into my DECmcc - oops! POLYcenter - do I have to deregister
all of the respective devices and re-register them again to pick up the
enhanced MIB capability?
Like I said, this behavior will not be desirable in a real world scenario.
Comments?
Jarhead
|
4657.5 | Sure don't want to deregister first... | TOOK::R_SPENCE | Nets don't fail me now... | Thu Mar 11 1993 14:39 | 6 |
| An Idea... Even if you have it registered can you just DO a REGISTER
to pick up the MIB info? Or, perhaps there is really an attribute
or child that can be registered?
s/rob
|
4657.6 | REGISTER no longer does a REREGISTER | TOOK::STRUTT | Management - the one word oxymoron | Mon Mar 22 1993 18:21 | 16 |
| re: .5
Sigh...
The original design permitted a REGISTER operation to perform as a
REREGISTER operation - for exactly the reasons cited: you don't want to
have to DEREGISTER and REGISTER something, cos you may lose valuable
data in the process.
Unfortunately, during the V1.2 implementation (I think) when partial
registration was added, this feature, which was never documented,
was inadvertently removed. When I mentioned this during v1.3
development I was told that it wouldn't get put back, either - however
in some future release (perhaps) there might be a new REREGISTER
operation which did what REGISTER did in the first couple of versions.
Colin
|