Re: [Teas] Suggested telemetry counters for the TE Topology model

"Xufeng Liu" <xufeng.liu.ietf@gmail.com> Tue, 21 February 2017 17:12 UTC

Return-Path: <xufeng.liu.ietf@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49BAC129518 for <teas@ietfa.amsl.com>; Tue, 21 Feb 2017 09:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level:
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 oSranSIw2PCV for <teas@ietfa.amsl.com>; Tue, 21 Feb 2017 09:12:16 -0800 (PST)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC3BB129517 for <teas@ietf.org>; Tue, 21 Feb 2017 09:12:15 -0800 (PST)
Received: by mail-lf0-x22b.google.com with SMTP id z127so67384767lfa.2 for <teas@ietf.org>; Tue, 21 Feb 2017 09:12:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=4N9Ole6LAWWDELG6JBc6Uq2mbrZM5ZyUlISkbI6nISQ=; b=PcIyyApby3eDnAhgU2ql/xtKB9IVhnmmoP4fnTTHRF7p2tocr1SfErOqNmLlu6XA6O EB3SOmu+1Tjxr4cHKMwLRaoJC+u2Q/ymAy46sQ0CpnaC0xgE4EfOwIQZLY4hdBVPCH4v J1fGtWqIpKpjPr+jxapZfIwWwgmSQcjoYvgsvUoxIM0J/AIf9Iy2xfCyBHN7OeFX/cHJ yJgmzXX2zfBrtEgtKUSDNsdD3mcO7FQfz8ibHp8Yeb4u13J3gJ4An8CGbPLNZAeBvtfr OjP5GgPx5SITQofVbRBoDR+9Zki27UxoqhQJZg3hHlCTsXp0En3F4q9jLc9kcpE/ZhA1 TZqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=4N9Ole6LAWWDELG6JBc6Uq2mbrZM5ZyUlISkbI6nISQ=; b=EgJLwC2p58LpSxlZ9veQGryJIkUlrE0KhMS4xv1w9+klW+7Q96w5bxJtxYFE7C5QaE 8kxkuRkAkjOGUIGXLr7+dAv7z7BP6A0RA7TKzJtxVHDC08B22hx8nDZdYB1q5yyVv27X u0ywsy3UlkvgaVoe8v2grH+aBD3hjaspafctu9Flr9JTxNcKMKzJC11GfYzN/2+ApiVu 3eQVvQjtTsDhUUm9Dt1sQILX9aYoVxSD315LcjpVo+1UNLWFbZ4VTi9s9KJZZnMsVo94 rvQJFX6xLZWot7x0aA0fClPa7G8niCAhBkjrfKf5YG0+3NRaNVn+Vl1pD0hfKi9mDVaa M2UQ==
X-Gm-Message-State: AMke39nGKKyQggVaayzzT33SGP7UQrPtqXSxpNsffXPsOvxAdHNPLo+IsyDbhlh0xrY/wA==
X-Received: by 10.46.32.19 with SMTP id g19mr6465519ljg.50.1487697133984; Tue, 21 Feb 2017 09:12:13 -0800 (PST)
Received: from xliuus (wsip-98-191-72-170.dc.dc.cox.net. [98.191.72.170]) by smtp.gmail.com with ESMTPSA id 75sm2929157lfy.27.2017.02.21.09.12.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Feb 2017 09:12:13 -0800 (PST)
From: Xufeng Liu <xufeng.liu.ietf@gmail.com>
To: 'Ievgen Zhukov' <evgeniy.zhukov@NetCracker.com>, 'Igor Bryskin' <Igor.Bryskin@huawei.com>, teas@ietf.org
References: <HE1PR0601MB265230B3D921A53D092ED62AB1EA0@HE1PR0601MB2652.eurprd06.prod.outlook.com> <C636AF2FA540124E9B9ACB5A6BECCE6B7DF15AFE@SZXEMA512-MBS.china.huawei.com> <AM5PR0601MB2641FBA1E70221822FB93BF5B1ED0@AM5PR0601MB2641.eurprd06.prod.outlook.com> <0C72C38E7EBC34499E8A9E7DD007863908EFC722@dfweml501-mbx> <0C72C38E7EBC34499E8A9E7DD007863908EFC751@dfweml501-mbx> <44C7337F3C5F254CB68FB0D74E6B0C72927237CC@umaildb2.netcracker.com>
In-Reply-To: <44C7337F3C5F254CB68FB0D74E6B0C72927237CC@umaildb2.netcracker.com>
Date: Tue, 21 Feb 2017 12:12:09 -0500
Message-ID: <02b801d28c65$a49269d0$edb73d70$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_02B9_01D28C3B.BBBEF9E0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQFqqgSyUeKX1SFIHw0ghAledcewmwGUvGOkAY8TvmIBrrVQagFRtNRCAijbddGiAQz64A==
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/ClrvlhaYdcHSS8RkFeHYsCr1gZ0>
Cc: 'Anh Tuan Le' <AnhLe@NetCracker.com>, 'Michael Kloberdans' <michael.kloberdans@netcracker.com>, 'Andrew Veitch' <andrew.veitch@NetCracker.com>, 'Dmytro Gassanov' <dmytro.gassanov@NetCracker.com>
Subject: Re: [Teas] Suggested telemetry counters for the TE Topology model
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 17:12:20 -0000

Hi Ievgen,

 

During our last TE Topology model design meeting, we discussed these counters, and found that they seem to related to the TE model, rather than the TE Topology model. We will pass your comments to the TE model discussion meeting to cover them in the proper model.

 

Thanks,

- Xufeng

 

From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Ievgen Zhukov
Sent: Thursday, February 9, 2017 7:41 PM
To: Igor Bryskin <Igor.Bryskin@huawei.com>; teas@ietf.org
Cc: Anh Tuan Le <AnhLe@NetCracker.com>; Michael Kloberdans <michael.kloberdans@netcracker.com>; Andrew Veitch <andrew.veitch@NetCracker.com>; Dmytro Gassanov <dmytro.gassanov@NetCracker.com>
Subject: Re: [Teas] Suggested telemetry counters for the TE Topology model

 

Hi, Igor

 

On IETF97 was outlined next steps for ACTN, where "Telemetry" one of them.

 

Let me augment your suggestions with Session Level counters:

 

4. Session Level:

*	session-up-count
*	session-down-count
*	session-admin-down-count

 

 

BR,

-------------------

 

Evgeniy Zhukov, Business Analysis

Netcracker Technology

 

+38 (044) 238-8727 | ext. 26927| office

+38 (093) 210-4266 | mobile

 

We are Netcracker, and we are focused forward

 

ƕ 

From: Igor Bryskin [mailto:Igor.Bryskin@huawei.com] 
Sent: Tuesday, August 30, 2016 6:45 PM
To: Igor Bryskin <Igor.Bryskin@huawei.com>; Xufeng Liu <xliu@kuatrotech.com>; Zhangxian (Xian) <zhang.xian@huawei.com>; Vishnu Pavan Beeram <vbeeram@juniper.net>; Oscar Gonzalez De Dios <oscar.gonzalezdedios@telefonica.com>; Tarek Saad <tsaad@cisco.com>; Himanshu Shah <hshah@ciena.com>; Lou Berger <lberger@labn.net>; BRUNGARD, DEBORAH A (ATTLABS) <db3546@att.com>; Susan Hares <shares@ndzh.com>; Zafar Ali (zali) <zali@cisco.com>; Khaddam, Mazen (CCI-Atlanta) <Mazen.Khaddam@cox.com>; Tony Le <tonyle@juniper.net>; BELOTTI, SERGIO (SERGIO) <sergio.belotti@alcatel-lucent.com>; Beller, Dieter (Dieter) <dieter.beller@alcatel-lucent.com>; Rajan Rao <rrao@infinera.com>; xufeng.liu.ietf@gmail.com; Belotti, Sergio (Nokia - IT) <sergio.belotti@nokia.com>; Anurag Sharma <AnSharma@infinera.com>
Cc: teas@ietf.org
Subject: [Teas] Suggested telemetry counters for the TE Topology model

 

Hi, 

I suggest the following telemetry counters for the TE Topology model:

1.	TE Link level:

*	linkAdds
*	linkRemoves
*	linkModifys
*	linkUps
*	linkDowns
*	linkInMaintenanceSets
*	linkInMaintenanceClears
*	protectionSwitchs
*	protectionReverts
*	restorationSwitchs
*	restorationReverts
*	faultDetects
*	faultClears

2.	TE node level:

*	nodeAdds
*	nodeRemoves
*	connectivityMatrixEntryAdds
*	connectivityMatrixEntryRemoves
*	connectivityMatrixEntryModifys

3.	TE TTP level:

*	ttpAdds
*	ttpRemoves
*	ttpModifys
*	ttpUps
*	ttpDowns
*	ttpInServiceSets
*	ttpInServiceClears
*	ttpInMaintenanceSets
*	ttpInMaintenanceClears
*	llclEntryAdds
*	llclEntryRemoves
*	llclEntryModifys

 

 

Cheers,

Igor

 

 

  _____  

The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.