IETF Logo Mail Archive

Re: [mpls-tp] Alarm Reporting (aka AIS)

Maarten Vissers <maarten.vissers@huawei.com> Wed, 08 December 2010 07:15 UTC

Return-Path: <maarten.vissers@huawei.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70FC13A67AB for <mpls-tp@core3.amsl.com>; Tue, 7 Dec 2010 23:15:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.084
X-Spam-Level:
X-Spam-Status: No, score=-6.084 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, 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 SC9myt0rWkXF for <mpls-tp@core3.amsl.com>; Tue, 7 Dec 2010 23:14:59 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 991583A66B4 for <mpls-tp@ietf.org>; Tue, 7 Dec 2010 23:14:59 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LD300LQSLJDN7@usaga02-in.huawei.com> for mpls-tp@ietf.org; Tue, 07 Dec 2010 23:16:26 -0800 (PST)
Received: from m00900002 ([10.202.112.102]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LD30011LLJBJD@usaga02-in.huawei.com> for mpls-tp@ietf.org; Tue, 07 Dec 2010 23:16:25 -0800 (PST)
Date: Wed, 08 Dec 2010 08:16:52 +0100
From: Maarten Vissers <maarten.vissers@huawei.com>
In-reply-to: <077E41CFFD002C4CAB7DFA4386A532640308F66E@DEMUEXC014.nsn-intra.net>
To: "'Sprecher, Nurit (NSN - IL/Hod HaSharon)'" <nurit.sprecher@nsn.com>, mpls-tp@ietf.org
Message-id: <002a01cb96a7$e4552040$acff60c0$%vissers@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_Eeee32XsD8TMo25nRMCYFw)"
Content-language: en-gb
Thread-index: AcuWfGt80MeNI9HgT3GIq0sKBOnFIgAK1C+A
References: <077E41CFFD002C4CAB7DFA4386A532640308F66E@DEMUEXC014.nsn-intra.net>
Cc: "'Zhao, Peng \(NSN - CN/Shanghai\)'" <peng.zhao@nsn.com>
Subject: Re: [mpls-tp] Alarm Reporting (aka AIS)
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2010 07:15:03 -0000

Nurit,

 

In MPLS-TP all transport paths are monitored and will have MEPs. 

 

Regards,

Maarten

 

From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
Of Sprecher, Nurit (NSN - IL/Hod HaSharon)
Sent: 8 December 2010 03:06
To: mpls-tp@ietf.org
Cc: Zhao, Peng (NSN - CN/Shanghai)
Subject: [mpls-tp] Alarm Reporting (aka AIS)

 

Hi,

I have a question about the functionality of Alarm Reporting..

Assuming that there is a failure at a server layer somewhere across the
network..and the MEP of the server layer identifies it and needs to ensure
that Alarm Reporting is sent to all of the MEPs of the client services that
transmit over the failed server.but it may be that some of the client
services do not have MEPs..how does the node detecting the server failure
knows which client services have MEPs and an Alarm Reporting message needs
to be sent to their MEPs and which do not have MEPs and an Alarm Reporting
message must not be sent for these client services..(as we would not like to
flood the network with unnecessary traffic)..

I hope someone can clarify it to me.

Best regards,

Nurit

v2.8.7 | Report a Bug | By Email