Re: [IPFIX] NetFlow v9 to IPFIX conversion

Andrew Feren <andrewf@plixer.com> Tue, 06 January 2015 20:07 UTC

Return-Path: <andrewf@plixer.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 606621A1B91 for <ipfix@ietfa.amsl.com>; Tue, 6 Jan 2015 12:07:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSlXMpqtll4j for <ipfix@ietfa.amsl.com>; Tue, 6 Jan 2015 12:07:53 -0800 (PST)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAEAD1A1B89 for <ipfix@ietf.org>; Tue, 6 Jan 2015 12:07:52 -0800 (PST)
Received: from [10.1.14.173] (64.140.243.154) by mx1.plixer.com (10.1.5.1) with Microsoft SMTP Server (TLS) id 14.3.210.2; Tue, 6 Jan 2015 15:07:25 -0500
Message-ID: <54AC4097.1050602@plixer.com>
Date: Tue, 6 Jan 2015 15:07:51 -0500
From: Andrew Feren <andrewf@plixer.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Petr Velan <petr.velan@cesnet.cz>, <ipfix@ietf.org>
References: <CALbOe5O0e3tw--vCrj9FkFWVvoMAb9iZaXyRYqfNFSSqQUT94w@mail.gmail.com>
In-Reply-To: <CALbOe5O0e3tw--vCrj9FkFWVvoMAb9iZaXyRYqfNFSSqQUT94w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030103040800000006050007"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipfix/rlvx0B0pSMfOw4GqeF_6Zd6x1lU
Subject: Re: [IPFIX] NetFlow v9 to IPFIX conversion
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 20:07:59 -0000

Hi Petr,

On 01/06/2015 07:03 AM, Petr Velan wrote:
> Hello all,
>
> I'm not sure whether this is the right place to ask, but we
> encountered following problem when converting NetFlow v9 messages to
> IPFIX.
>
> Some vendors (I've heard of ntop) are using elements IDs large than
> 32767 in NetFlow v9. When converting messages with these elements to
> IPFIX, they are considered to be Enterprise Numbers. To generate
> proper IPFIX message, we need to do one of the following:
> a) Generate a list of the elements and map them to PEN of the correct
> vendor. However, this would result in an attempt to cover all possible
> elements that anybody used in NetFlow v9. Moreover, we would still
> have to somehow handle the cases where the element is unknown
This should help with ntop/nprobe

Recent versions of nprobe (since version 5.5.5 I think) all use the
following mapping.

PEN = 35632 and IPFIXID = (v9ID - 57472)

For example, one v9 IE that nprobe exports is MYSQL_SERVER_VERSION
57667.  The IPFIX equivalent would be
MYSQL_SERVER_VERSION(35632/195).

The nprobe docs have a complete list.

Older versions of nprobe (pre ~2010) use IEs not in RFC 3954, but later
allocated in IANA.  There is no good way to convert those v9 exports to
IPFIX.

-Andrew


> b) Request a PEN for NetFlow compatibility and just add this PEN for
> every element that has ID larger than 32767.
>
> Personally, I believe that the b) is more general and error-prone. Do
> you think, that it would be possible to dedicate whole PEN to this cause?
>
> Thank you for any opinions,
>
> Petr Velan
>
>
>
> _______________________________________________
> IPFIX mailing list
> IPFIX@ietf.org
> https://www.ietf.org/mailman/listinfo/ipfix