gt;Sent: Monday, February 09, 2004 1:12 AM
>>To: Harrington, David
>>Cc: [EMAIL PROTECTED]
>>Subject: Re: SyslogMIB Issue-#4 // Issue-#2
>>
>>Dave,
>>Harrington, David wrote:
>>
>>>Hi,
>>>
>>>Rather than reinventing wheels, let&#x
12 AM
> To: Harrington, David
> Cc: [EMAIL PROTECTED]
> Subject: Re: SyslogMIB Issue-#4 // Issue-#2
>
> Dave,
> Harrington, David wrote:
> > Hi,
> >
> > Rather than reinventing wheels, let's try to review work that has
> > already been done in the IETF
This is a reply to a direct question - general comment following with
other reply.
> With Kiwi Syslog and WinSyslog, the config file is not
> created or edited
> by the user.
Just FYI: we (WinSyslog & similar products) are heading towards either
human-readable config file or skilled-human-readabl
> From: Harrington, David [mailto:[EMAIL PROTECTED]
> Rather than reinventing wheels, let's try to review work that has
> already been done in the IETF for these purposes, and discuss any
> experience that has already been had with these approaches.
> Please look
> at the RFC3165 Script MIB
> (ftp:
Dave,
Harrington, David wrote:
> Hi,
>
> Rather than reinventing wheels, let's try to review work that has
> already been done in the IETF for these purposes, and discuss any
> experience that has already been had with these approaches. Please look
> at the RFC3165 Script MIB
I fully agree.
> (ftp:
dbh
> -Original Message-
> From: Glenn Mansfield Keeni [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 08, 2004 1:21 AM
> To: [EMAIL PROTECTED]
> Subject: Re: SyslogMIB Issue-#4 // Issue-#2
>
> Andrew Ross wrote:
>
> > Having a minimum set of configuration options woul
config file would be a good choice here.
Rainer, does that that work for you?
Cheers
Andrew
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Glenn Mansfield
Keeni
Sent: Sunday, 8 February 2004 7:21 p.m.
To: [EMAIL PROTECTED]
Subject: Re: SyslogMIB
Andrew Ross wrote:
> Having a minimum set of configuration options would probably be a waste
> of time in my view as all implementations are so different.
>
> Since all implementations use (or can be made to use) a config file, my
> vote is for a free form string variable. The format of the text d
>Let me phrase my question rather bluntly: does it pay to provide a very
>minimal set of config settings given the fact that almost every vendor
>has very different ways to do this. Also, in my experience customers
>tend to use those vendor-specifc ways, simply because they need it. To
>be honest,
[EMAIL PROTECTED]
> Sent: Friday, February 06, 2004 4:30 AM
> To: Harrington, David; Glenn Mansfield Keeni; [EMAIL PROTECTED]
> Subject: RE: SyslogMIB Issue-#4 // Issue-#2
>
> David,
>
> > -Original Message-
> > From: Harrington, David [mailto:[EMAIL PROTECTED]
>
David,
> -Original Message-
> From: Harrington, David [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 05, 2004 9:53 PM
> To: Rainer Gerhards; Glenn Mansfield Keeni; [EMAIL PROTECTED]
> Subject: RE: SyslogMIB Issue-#4 // Issue-#2
>
> Hi,
>
> SNMP is good at
> -Original Message-
> From: Rainer Gerhards [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 30, 2004 12:57 PM
> To: Glenn Mansfield Keeni; [EMAIL PROTECTED]
> Subject: RE: SyslogMIB Issue-#4 // Issue-#2
>
> Let me make a comment here that applies to issue #2 (BSD Centric)
>
&
Let me make a comment here that applies to issue #2 (BSD Centric)
> -Original Message-
> From: Glenn Mansfield Keeni [mailto:[EMAIL PROTECTED]
> Sent: Sunday, January 25, 2004 3:05 PM
> To: Harrington, David
> Cc: [EMAIL PROTECTED]
> Subject: Re: SyslogMIB Is
>Getting the high resolution timestamp should not be a problem. And
> I think that we can agree to constrain the length of the message that
> will be carried in the trap.
In -protocol, the max length is sill FIXED at 1024 per message fragment.
If a message is large, it MUST be fragmented into
> Hi Rainer,
>This pretty much matches with the image I have in mind.
> Till there is no "original sender" in the syslog message
> itself I guess that we will have to do with the "last sender".
I assume we are talking about a syslog relay chain BEFORE the realy that
issues the trap here. Actua
PROTECTED]
>>Sent: Sunday, January 25, 2004 11:10 PM
>>To: 'Glenn Mansfield Keeni'; 'Harrington, David'
>>Cc: [EMAIL PROTECTED]
>>Subject: RE: SyslogMIB Issue-#4
>>
>>
>>Hi Glenn,
>>
>>That system looks good. Something to map syslo
ginal Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Glenn Mansfield
> Keeni
> Sent: Monday, 26 January 2004 3:05 a.m.
> To: Harrington, David
> Cc: [EMAIL PROTECTED]
> Subject: Re: SyslogMIB Issue-#4
>
>
> Hi Dave,
> Thanks for the
0 PM
> To: 'Glenn Mansfield Keeni'; 'Harrington, David'
> Cc: [EMAIL PROTECTED]
> Subject: RE: SyslogMIB Issue-#4
>
>
> Hi Glenn,
>
> That system looks good. Something to map syslog messages into
> SNMP traps
> and another one for notifications.
>
&g
al Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Glenn Mansfield
Keeni
Sent: Monday, 26 January 2004 3:05 a.m.
To: Harrington, David
Cc: [EMAIL PROTECTED]
Subject: Re: SyslogMIB Issue-#4
Hi Dave,
Thanks for the comments. I agree with you. Traps are useful.
They provide
Hi Dave,
Thanks for the comments. I agree with you. Traps are useful.
They provide a uniform mechanism/console for the network manager
to manage the network, related devices and processes.
There are two levels at which we may want SNMP traps in the
Syslog Messaging context.
a. To provid
Hi Glenn,
The benefit of having an SNMP trap is that there becomes some
coordination between the syslog messaging and SNMP trap manager
applications.
Operators often use trap management tools to alert them to problems, and
these applications often have the ability to filter out uninteresting
trap
21 matches
Mail list logo
