Re: [VRRP] FW: VRRPV3-MIB protocol error trap question
"Kalyan (Srinivas)Tata" <stata@checkpoint.com> Mon, 24 September 2012 23:28 UTC
Return-Path: <stata@checkpoint.com>
X-Original-To: vrrp@ietfa.amsl.com
Delivered-To: vrrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 192031F041D for <vrrp@ietfa.amsl.com>; Mon, 24 Sep 2012 16:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.391
X-Spam-Level:
X-Spam-Status: No, score=-9.391 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X22Mgs0r5W3X for <vrrp@ietfa.amsl.com>; Mon, 24 Sep 2012 16:28:52 -0700 (PDT)
Received: from us.checkpoint.com (usmail2.us.checkpoint.com [216.200.240.146]) by ietfa.amsl.com (Postfix) with ESMTP id 48D701F042B for <vrrp@ietf.org>; Mon, 24 Sep 2012 16:28:51 -0700 (PDT)
X-CheckPoint: {5060EE8D-2-8AF0C8D8-FFFF}
Received: from us-ex01.ad.checkpoint.com (us-ex01.ad.checkpoint.com [216.200.240.139]) by us.checkpoint.com (8.14.4/8.14.4) with ESMTP id q8ONSoUm025980; Mon, 24 Sep 2012 16:28:50 -0700
Received: from USEXCHANGE.ad.checkpoint.com ([216.200.240.132]) by US-EX01.ad.checkpoint.com ([216.200.240.139]) with mapi; Mon, 24 Sep 2012 16:28:50 -0700
From: "Kalyan (Srinivas)Tata" <stata@checkpoint.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "vrrp@ietf.org" <vrrp@ietf.org>
Date: Mon, 24 Sep 2012 16:28:48 -0700
Thread-Topic: [VRRP] FW: VRRPV3-MIB protocol error trap question
Thread-Index: AQG2x6W6pjWvPTAHkQf9MKEmeZXpWAH/6dWZl6yn2WCACxV1wA==
Message-ID: <BE5C948D3F924B40BAAF2F4D9210F5411E4C4479D8@USEXCHANGE.ad.checkpoint.com>
References: <50460123020000E1000154AA@gwia.alliedtelesyn.co.nz> <BE5C948D3F924B40BAAF2F4D9210F5411E4C3F48B1@USEXCHANGE.ad.checkpoint.com> <03b001cd951b$e7b3d370$b71b7a50$@olddog.co.uk>
In-Reply-To: <03b001cd951b$e7b3d370$b71b7a50$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: multipart/alternative; boundary="_000_BE5C948D3F924B40BAAF2F4D9210F5411E4C4479D8USEXCHANGEadc_"
MIME-Version: 1.0
Subject: Re: [VRRP] FW: VRRPV3-MIB protocol error trap question
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Virtual Router Redundancy Protocol <vrrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vrrp>, <mailto:vrrp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vrrp>
List-Post: <mailto:vrrp@ietf.org>
List-Help: <mailto:vrrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vrrp>, <mailto:vrrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Sep 2012 23:28:53 -0000
Hi Adrian,
I replied to that email too fast without reviewing the history. Please disregard my reply. Creating the OID with the invalid VRID received and setting the vrrpv3StatisticsProtoErrReason to vrIdError(4) would be the correct behavior.
Thanks
Kalyan
From: Adrian Farrel [mailto:adrian@olddog.co.uk]
Sent: Monday, September 17, 2012 2:32 PM
To: Kalyan (Srinivas)Tata; vrrp@ietf.org
Subject: RE: [VRRP] FW: VRRPV3-MIB protocol error trap question
Hi,
Is there an Erratum that should be raised for this?
Thanks,
Adrian
From: vrrp-bounces@ietf.org<mailto:vrrp-bounces@ietf.org> [mailto:vrrp-bounces@ietf.org]<mailto:[mailto:vrrp-bounces@ietf.org]> On Behalf Of Kalyan (Srinivas)Tata
Sent: 06 September 2012 04:12
To: vrrp@ietf.org<mailto:vrrp@ietf.org>
Subject: [VRRP] FW: VRRPV3-MIB protocol error trap question
From: Kalyan (Srinivas)Tata
Sent: Wednesday, September 05, 2012 8:11 PM
To: 'tony vanderpeet'
Subject: RE: [VRRP] VRRPV3-MIB protocol error trap question
Hi Tony,
This was an editing error in which the vrIdError was not removed from the vrrpV3StatisticsProtoErrReason when vrrpv3RouterVrIdErrors was added as a global counter.
(exactly for the reason you mentioned)
vrrpv3RouterVrIdErrors should be used for counting the number of vrid errors.
Thanks
Kalyan
From: vrrp-bounces@ietf.org<mailto:vrrp-bounces@ietf.org> [mailto:vrrp-bounces@ietf.org]<mailto:[mailto:vrrp-bounces@ietf.org]> On Behalf Of tony vanderpeet
Sent: Monday, September 03, 2012 6:25 PM
To: vrrp@ietf.org<mailto:vrrp@ietf.org>
Subject: [VRRP] VRRPV3-MIB protocol error trap question
I am implementing the protocol error trap in the VRRPV3 MIB and have spotted a possible hole in the MIB. I wonder if this was picked up in discussions and a work-around devised?
When an advertisement is received with an unrecognised VR ID, a protocol error trap is generated, with the object vrrpv3StatisticsProtoErrReason. This object has value vrIdError(4) in this case, but what should the index of the object be? In particular, what should the VR ID part of the index be?
I am inclined to create a variable binding with a fake OID using the unrecognised VR ID, since this will actually convey the information required (which VR ID is invalid, and the address type and ifIndex).
What, if any, discussion has taken place around this issue, and was there any conclusion reached?
Thanks
Tony
Tony van der Peet
Software Architect
Allied Telesis Labs Limited
27 Nazareth Ave
Christchurch, NZ
Tel: +64-3-3399532 (DDI)
Mob: +64-27-2091860
- [VRRP] VRRPV3-MIB protocol error trap question tony vanderpeet
- [VRRP] FW: VRRPV3-MIB protocol error trap question Kalyan (Srinivas)Tata
- Re: [VRRP] FW: VRRPV3-MIB protocol error trap que… Adrian Farrel
- Re: [VRRP] FW: VRRPV3-MIB protocol error trap que… Kalyan (Srinivas)Tata