Hi Brett, RFC 3014 is for retrieving a log of SNMP notifications. I don't believe it is for retrieving syslog messages.
The purpose is to log traps/informs so that if they don't get delivered, a manager can still see what was sent. This is equivalent to what you want for syslog messages, but I don't think this mib should be used for that purpose, because if I just want to see what SNMP traps were sent, I don't want to have to wade through the whole log of syslog messages. dbh > -----Original Message----- > From: Glenn Mansfield Keeni [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 12, 2003 10:02 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Remote syslog message retrieval > > > Brett, > [EMAIL PROTECTED] wrote: > > I have a question for consideration. > > > > I was looking over the draft syslog mib and wondered why there is no > > mechanism to retrieve messages that have been stored > locally on the remote > > device? > The present SyslogMIB is essentially about monitoring (and potentially > controlling ) syslog processes. It provides statistics on messages > sent, received etc. by the syslog process. But it does not deal with > message retrieval. > > > > I realize that under normal operation the device would be > sending its syslog > > messages to a syslog server. However, there are situations > where the syslog > > server may have been unreachable for a period of time. It > would be nice if > > the locally-stored messages could be read via SNMP. > I fully agree with you. The Notification Log MIB (rfc3014) is defined > for retrieving logged messages. This can be adapted to retrieve syslog > messages. There a small amount of work that needs to be done. > If there is > sufficient interest perhaps this should be taken up as a WG-work item. > I guess that next in the queue would be addition of SNMP Notifications > as one of the actions of the syslog process. > > Glenn > > > > > Brett > > > > > > > > >
