Re: [VRRP] FW: VRRPV3-MIB protocol error trap question

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 17 September 2012 21:32 UTC

Return-Path: <adrian@olddog.co.uk>
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 E894C21F841E for <vrrp@ietfa.amsl.com>; Mon, 17 Sep 2012 14:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.631
X-Spam-Level:
X-Spam-Status: No, score=-1.631 tagged_above=-999 required=5 tests=[AWL=-0.892, BAYES_20=-0.74, HTML_MESSAGE=0.001]
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 3LaIKDViCMUu for <vrrp@ietfa.amsl.com>; Mon, 17 Sep 2012 14:32:27 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA2E21F8616 for <vrrp@ietf.org>; Mon, 17 Sep 2012 14:32:26 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q8HLWGki019876; Mon, 17 Sep 2012 22:32:16 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q8HLWDRk019865 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 17 Sep 2012 22:32:14 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Kalyan \(Srinivas\)Tata'" <stata@checkpoint.com>, <vrrp@ietf.org>
References: <50460123020000E1000154AA@gwia.alliedtelesyn.co.nz> <BE5C948D3F924B40BAAF2F4D9210F5411E4C3F48B1@USEXCHANGE.ad.checkpoint.com>
In-Reply-To: <BE5C948D3F924B40BAAF2F4D9210F5411E4C3F48B1@USEXCHANGE.ad.checkpoint.com>
Date: Mon, 17 Sep 2012 22:32:13 +0100
Message-ID: <03b001cd951b$e7b3d370$b71b7a50$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03B1_01CD9524.499B53D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG2x6W6pjWvPTAHkQf9MKEmeZXpWAH/6dWZl6yn2WA=
Content-Language: en-gb
Subject: Re: [VRRP] FW: VRRPV3-MIB protocol error trap question
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 17 Sep 2012 21:32:28 -0000

Hi,
Is there an Erratum that should be raised for this?
Thanks,
Adrian
 
From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf Of Kalyan
(Srinivas)Tata
Sent: 06 September 2012 04:12
To: 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] On Behalf Of tony
vanderpeet
Sent: Monday, September 03, 2012 6:25 PM
To: 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