Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents
"Yuquan Tracy Jiang (jiangy)" <jiangy@cisco.com> Mon, 01 December 2008 21:45 UTC
Return-Path: <opsawg-bounces@ietf.org>
X-Original-To: opsawg-archive@optimus.ietf.org
Delivered-To: ietfarch-opsawg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 45A313A69EE; Mon, 1 Dec 2008 13:45:01 -0800 (PST)
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78D9F3A6BB2 for <opsawg@core3.amsl.com>; Mon, 1 Dec 2008 12:57:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ggEVZjKt8wS for <opsawg@core3.amsl.com>; Mon, 1 Dec 2008 12:57:41 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 8325E3A6BA6 for <opsawg@ietf.org>; Mon, 1 Dec 2008 12:57:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,698,1220227200"; d="scan'208";a="204540416"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 01 Dec 2008 20:57:38 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id mB1Kvc5S024038 for <opsawg@ietf.org>; Mon, 1 Dec 2008 12:57:38 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mB1KvcWP010932 for <opsawg@ietf.org>; Mon, 1 Dec 2008 20:57:38 GMT
Received: from xmb-sjc-226.amer.cisco.com ([128.107.191.58]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 1 Dec 2008 12:57:37 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 01 Dec 2008 12:57:37 -0800
Message-ID: <43F339CB2F4C8E4DA0AC53BFA69B0DD506F5A15C@xmb-sjc-226.amer.cisco.com>
In-Reply-To: <85B2F271FDF6B949B3672BA5A7BB62FB06C2B0D3@xmb-sjc-236.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents
Thread-Index: AclLS1jVjAP0L960Q8ajyU5PDMjoSgEt6tzQAPumQSAAACKPYAAA/BUQ
References: <85B2F271FDF6B949B3672BA5A7BB62FB06C2AC0C@xmb-sjc-236.amer.cisco.com> <43F339CB2F4C8E4DA0AC53BFA69B0DD506F5A0FD@xmb-sjc-226.amer.cisco.com> <85B2F271FDF6B949B3672BA5A7BB62FB06C2B0D3@xmb-sjc-236.amer.cisco.com>
From: "Yuquan Tracy Jiang (jiangy)" <jiangy@cisco.com>
To: opsawg@ietf.org
X-OriginalArrivalTime: 01 Dec 2008 20:57:37.0991 (UTC) FILETIME=[7150AD70:01C953F7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2494; t=1228165058; x=1229029058; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jiangy@cisco.com; z=From:=20=22Yuquan=20Tracy=20Jiang=20(jiangy)=22=20<jiangy@ cisco.com> |Subject:=20RE=3A=20[OPSAWG]=20WG=20adoption=20of=20SNMP=20 <->=20SYSLOG=20mapping=20documents |Sender:=20; bh=vX8v2s0GhO0gO2Y3Odp0Ub0Mj3o9nwqSXx0ColkHuAc=; b=IV56e+dVAm18iuuNhZkCTVSBNqAbxI9hzgxMFZH1FtEmQrm3ViwDUstWuP 1a/gov9wU47qYKxGmIEmpcxqTNqBHYPj/0mmENjZ1Ni73DzpnCbMt+dBw7o7 qMYSoxXwgc;
Authentication-Results: sj-dkim-4; header.From=jiangy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Mailman-Approved-At: Mon, 01 Dec 2008 13:45:00 -0800
Cc: "Steve Giles (stgiles)" <stgiles@cisco.com>, "Joe Zhao (jzhao)" <jzhao@cisco.com>
Subject: Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: opsawg-bounces@ietf.org
Errors-To: opsawg-bounces@ietf.org
It is helpful to converge the management interfaces so that the NMS vendors and end customers will have less of them to deal with. It will help simply NMS system design and eliminate some tasks needed to correlate information passed from different channels regarding the same underlying event. By providing a standard way to convert between syslog and SNMP, two of the most commonly used management interfaces, it will help reduce the engineer efforts currently put in to manually replicate the information regarding same underlying event to both syslog and SNMP, and the inconsistency introduced during the subsequent independent updates. Thanks. Tracy =========================== Yuquan (Tracy) Jiang Product Manager Embedded Management, NSSTG Cisco Systems, Inc. Phone: 408-527-3877 (w) Email: jiangy@cisco.com -----Original Message----- From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder Sent: Thursday, November 20, 2008 12:05 PM To: opsawg@ietf.org Subject: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents Hi, the chairs of this WG need to decide whether there is support for adopting (a) a document defining a new SD-ID to represent SNMP notifications in SYSLOG [1] and (b) a document defining a MIB module representing SYSLOG messages [2]. For an overview, see the presentation slides form the Dublin meeting [3]. I believe that the documents are already pretty mature and can likely go through the WG relatively quickly. There has been quite some support for this work in Dublin and Rainer Gerhards expressed his support on the list. I am aware that some people did contact the chairs directly expressing their support but it might make things easier to move this forward if people can actually express their support here. Thanks, /js [1] http://tools.ietf.org/html/draft-marinov-syslog-snmp-02 (15 pages) [2] http://tools.ietf.org/html/draft-schoenw-syslog-msg-mib-01 (18 pages) [3] http://www.ietf.org/proceedings/08jul/slides/opsawg-1.pdf -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
- [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping d… Juergen Schoenwaelder
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Aiko Pras
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… David Partain
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Martin Bjorklund
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Natale, Bob
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Alexander Clemm (alex)
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Juergen Quittek
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Rainer Gerhards
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Mehmet Ersue
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Benoit Claise
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Yuquan Tracy Jiang (jiangy)
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… tom.petch
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Juergen Schoenwaelder
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… tom.petch