Re: [nv-l] update process for MIB´s
At 01:54 PM 17-05-05 +0200, you wrote:
we are using several of our Netview servers (version 7.1.3, fixpack 3) as a
trap receiver and therefore have to deal with updating the trap definitions.
I would like to know as a kind of best practices how you manage to keep
track on this?
are we right in thinking that new versions of MIB files (regardless of the
vendor who is providing those MIB files) do always cover the previous
version (same content), i.e. they are compatible to each other? Or could it
be in some cases that definitions are going to be removed in new versions of
A vendor can use a new MIB version to deprecate existing MIB objects
and/or add new ones. Existing OIDs cannot be reassigned. New objects,
whether entirely new or replacements for deprecated ones, need new OIDs. A
deprecation is basically advice to plan to stop using the deprecated object
because some new release of software is going to stop implementing it.
what is the best practice to get always informed about the most current
version of a MIB file / updates / changes?
1) to check the webpages of the vendors for new versions, filesize of the
MIB files etc.
2) to receive a vendor´s newsletter, which covers such nice information
about updates of specific MIB files?
3) check the trapd.log file for "unknown traps" to search for them in the
The vendor's product release notes or equivalent should tell you which
versions of which MIBs are implemented.
Thank you - it is greatly appreciated.
> Thorsten Mildeberger
> EMS Solutions - SMC Tools & Automation
> ITO - Central Region
> EDS Deutschland GmbH
> Eisenstr. 43
> 65428 Rüsselsheim
> Tel.: +49 (0) 6142 80-3706
> Fax.: +49 (0) 6142 80-3030
|<Prev in Thread]
||[Next in Thread>|
- Re: [nv-l] update process for MIB´s ,
Joe Fernandez <=
Archive operated by Skills 1st Ltd
See also: The NetView Web