Re: Log MIB Implementation Survey

>>>>> On Mon, 5 Apr 2004 12:29:02 -0700, "Randy Presuhn" <[email protected]> said:

Randy> Here is the Implementation Survey for RFC 3014, the Log MIB.

Here is an extremely late...  oh you get the point: sorry.

Module: NOTIFICATION-LOG-MIB
Implementation Source:                 Net-SNMP
Management Application / Agent:        subagent in the management station

notificationLogConfigGroup (y/n): n
notificationLogStatsGroup (y/n): y
notificationLogLogGroup (y/n): y
notificationLogDateGroup (y/n): y


OBJECTs:
nlmConfigGlobalEntryLimit (rw/ro): rw
lower bound: 0
upper bound: by memory

nlmConfigLogEntryLimit (rw/ro): no
lower bound: ________
upper bound: ________

nlmConfigLogEntryStatus: (rw/ro): no


Randy> Deployment / Operational Experience:

I actually implemented this on our receiver side a while ago (to test
a new automatic-storage API mechanism actually, but thats besides the
point).  Thus, the log reports only things that were actually received
by the demon and are reported to the agent running on the management
station through a agentx connection between the notification receiver
and the agent.  We don't support anything but the default log group
and no configuration.  I don't know if anyone is actually using the
results of the days work I did in throwing it together.

That being said, it is highly likely that we'll be implementing it in
the agent in the near future since a fairly large number of clients
are suddenly going to need support for it on the agent side.

-- 
"In the bathtub of history the truth is harder to hold than the soap,
 and much more difficult to find."  -- Terry Pratchett