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

Ievgen Zhukov <evgeniy.zhukov@NetCracker.com> Tue, 07 March 2017 13:39 UTC

Return-Path: <evgeniy.zhukov@NetCracker.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 DD213129459 for <teas@ietfa.amsl.com>; Tue, 7 Mar 2017 05:39:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 yOODM2GEv74R for <teas@ietfa.amsl.com>; Tue, 7 Mar 2017 05:39:27 -0800 (PST)
Received: from umail.netcracker.com (umail.netcracker.com [195.211.250.42]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E665129486 for <teas@ietf.org>; Tue, 7 Mar 2017 05:39:24 -0800 (PST)
From: Ievgen Zhukov <evgeniy.zhukov@NetCracker.com>
To: Xufeng Liu <xufeng.liu.ietf@gmail.com>, 'Igor Bryskin' <Igor.Bryskin@huawei.com>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] Suggested telemetry counters for the TE Topology model
Thread-Index: AQHSjGW62/90UesFSESM+ih6aKgSZKGJczDQ
Date: Tue, 07 Mar 2017 13:39:20 +0000
Message-ID: <44C7337F3C5F254CB68FB0D74E6B0C7292777011@umaildb2.netcracker.com>
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> <02b801d28c65$a49269d0$edb73d70$@gmail.com>
In-Reply-To: <02b801d28c65$a49269d0$edb73d70$@gmail.com>
Accept-Language: ru-RU, en-US
Content-Language: ru-RU
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-exclaimer-md-config: 91db5894-0ad9-4b50-852b-9165d6b27cf8
Content-Type: multipart/related; boundary="_005_44C7337F3C5F254CB68FB0D74E6B0C7292777011umaildb2netcrac_"; type="multipart/alternative"
MIME-Version: 1.0
X-KSE-ServerInfo: mailgwrus.netcracker.com, 9
X-KSE-AttachmentFiltering-Interceptor-Info: white sender email list
X-KSE-Antivirus-Interceptor-Info: scan successful
X-KSE-Antivirus-Info: Clean, bases: 07.03.2017 11:04:00
X-KSE-AntiSpam-Outbound-Interceptor-Info: scan successful
X-KSE-AntiSpam-Version: 5.7.0, Database issued on: 03/07/2017 13:26:06
X-KSE-AntiSpam-Status: KAS_STATUS_NOT_DETECTED
X-KSE-AntiSpam-Method: none
X-KSE-AntiSpam-Rate: 0
X-KSE-AntiSpam-Info: Lua profiles 110122 [Mar 07 2017]
X-KSE-AntiSpam-Info: LuaCore: 179 179 df69398cfb4a4b0720d3fee32c5a4b98e6b8a11c
X-KSE-AntiSpam-Info: Version: 5.7.0.22
X-KSE-AntiSpam-Info: Envelope from: evgeniy.zhukov@NetCracker.com
X-KSE-AntiSpam-Info: {Track_mailer_missed_ms}
X-KSE-AntiSpam-Info: {Track_mailer_missed_ms_exch}
X-KSE-AntiSpam-Info: 127.0.0.200:5.2.1; twitter.com:4.0.3,4.0.4,7.1.1; www.linkedin.com:4.0.4,7.1.1; www.netcracker.com:7.1.1; NetCracker.com:4.0.3,7.1.1; www.facebook.com:4.0.4,7.1.1; d41d8cd98f00b204e9800998ecf8427e.com:7.1.1; 127.0.0.199:7.1.2,5.2.1; umaildb2.netcracker.com:7.1.1
X-KSE-AntiSpam-Info: Auth:dkim=none
X-KSE-AntiSpam-Info: Rate: 0
X-KSE-AntiSpam-Info: Status: not_detected
X-KSE-AntiSpam-Info: Method: none
X-KSE-Antiphishing-Info: Clean
X-KSE-Antiphishing-Method: None
X-KSE-Antiphishing-Bases: 03/07/2017 13:27:00
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/7EJZkZHp9pqif9dd7hjHG5h1Ouo>
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, 07 Mar 2017 13:39:42 -0000

Hi, Xufeng

Thanks for the answer.
I don’t receive invitation to TE model discussion so far.
Please guide me for TE model discussion.

Thanks,
-------------------

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: Xufeng Liu [mailto:xufeng.liu.ietf@gmail.com]
Sent: Tuesday, February 21, 2017 7:12 PM
To: Ievgen Zhukov <evgeniy.zhukov@NetCracker.com>; '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 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<mailto:Igor.Bryskin@huawei.com>>; teas@ietf.org<mailto:teas@ietf.org>
Cc: Anh Tuan Le <AnhLe@NetCracker.com<mailto:AnhLe@NetCracker.com>>; Michael Kloberdans <michael.kloberdans@netcracker.com<mailto:michael.kloberdans@netcracker.com>>; Andrew Veitch <andrew.veitch@NetCracker.com<mailto:andrew.veitch@NetCracker.com>>; Dmytro Gassanov <dmytro.gassanov@NetCracker.com<mailto: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

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

  1.  TE node level:
·       nodeAdds
·       nodeRemoves
·       connectivityMatrixEntryAdds
·       connectivityMatrixEntryRemoves
·       connectivityMatrixEntryModifys

  1.  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.



________________________________
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.