Virtual Router Redundancy Protocol (vrrp)

Kalyan.Tata | 17 Oct 2006 20:36

Picon

RE: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-05.txt

Hi Joan,

First off, sorry I was a bit busy and could not get to update the mib
with your comments immediatly.
 I completed most of the changes except a couple and would appreciate
your help with the following:

===
4) RFC4181 (MIB Author Guidelines)
suggests using the following for the start of
the OID tree:

  xxxMIB
         |
         +-- xxxNotifications(0)
         +-- xxxObjects(1)
         +-- xxxConformance(2)
             |
             +-- xxxCompliances(1)
             +-- xxxGroups(2)

Currently, the OID tree is:

      vrrpOperations      OBJECT IDENTIFIER ::= { vrrpMIB 1 }
      vrrpStatistics      OBJECT IDENTIFIER ::= { vrrpMIB 2 }

      vrrpConformance     OBJECT IDENTIFIER ::= { vrrpMIB 3 }
      vrrpNotifications   OBJECT IDENTIFIER ::= { vrrpMIB 0 }
       vrrpMIBCompliances  OBJECT IDENTIFIER ::= { vrrpConformance 1 }
       vrrpMIBGroups       OBJECT IDENTIFIER ::= { vrrpConformance 2 }

(Continue reading)

Joan Cucchiara | 23 Oct 2006 16:27

Picon

Re: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-05.txt


Hello Kalyan,

I will reply to your questions below by tomorrow.

Thanks,
  Joan

----- Original Message ----- 
From: <Kalyan.Tata <at> nokia.com>
To: <dromasca <at> avaya.com>
Cc: <vrrp <at> ietf.org>
Sent: Tuesday, October 17, 2006 2:36 PM
Subject: RE: [VRRP] Re: Re: MIB Dr. Review 
ofdraft-ietf-vrrp-unified-mib-05.txt

Hi Joan,

First off, sorry I was a bit busy and could not get to update the mib
with your comments immediatly.
 I completed most of the changes except a couple and would appreciate
your help with the following:

===
4) RFC4181 (MIB Author Guidelines)
suggests using the following for the start of
the OID tree:

  xxxMIB
         |

(Continue reading)

Joan Cucchiara | 24 Oct 2006 15:19

Picon

Re: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-05.txt


>
> ----- Original Message ----- 
> From: <Kalyan.Tata <at> nokia.com>
> To: <dromasca <at> avaya.com>
> Cc: <vrrp <at> ietf.org>
> Sent: Tuesday, October 17, 2006 2:36 PM
> Subject: RE: [VRRP] Re: Re: MIB Dr. Review 
> ofdraft-ietf-vrrp-unified-mib-05.txt
>
>
> Hi Joan,
>
> First off, sorry I was a bit busy and could not get to update the mib
> with your comments immediatly.
> I completed most of the changes except a couple and would appreciate
> your help with the following:
>
> ===
> 4) RFC4181 (MIB Author Guidelines)
> suggests using the following for the start of
> the OID tree:
>
>  xxxMIB
>         |
>         +-- xxxNotifications(0)
>         +-- xxxObjects(1)
>         +-- xxxConformance(2)
>             |
>             +-- xxxCompliances(1)

(Continue reading)

Wijnen, Bert (Bert | 24 Oct 2006 15:48

Picon

RE: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-0 5.txt

W.r.t.

> > 8) Could notifications be generated or not, using the
> >  the notification MIB and target MIB (RFC2583)?
> >  I don't see a need for this object, but please let me
> >  know the answer to the above question.
> >
> > ++ RFC2583 seems to be Guidelines for Next Hop Client (NHC) Developers.
> > I could find RFC 3878 - Alarm Reporting Control MIB but this did not 
> > look relevant. Could you please clarify?
> 
> Sorry, this was a typo, the RFC is RFC 2573.  The MIBs in 

I think it is better to use RFC3413 instead. It is basically the same
as 2573, but 3413 is the current document (part of STD62) and
it obsoletes the earlier 2573.

Bert

_______________________________________________
vrrp mailing list
vrrp <at> ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp

Kalyan.Tata | 24 Oct 2006 22:28

Picon

RE: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-05.txt

Thanks Joan for the clarifications. 
I have one last issue when trying to fix  "indexing that may create
variables with more than 128 sub-ids"

I will send you the detailed problem tonight.

Thanks once again.
Kalyan

-----Original Message-----
From: ext Joan Cucchiara [mailto:jcucchiara <at> mindspring.com] 
Sent: Tuesday, October 24, 2006 6:20 AM
To: Joan Cucchiara; Tata Kalyan (Nokia-ES/MtView); Dan Romascanu
(E-mail)
Cc: vrrp <at> ietf.org; fenner <at> research.att.com
Subject: Re: [VRRP] Re: Re: MIB Dr. Review
ofdraft-ietf-vrrp-unified-mib-05.txt

>
> ----- Original Message -----
> From: <Kalyan.Tata <at> nokia.com>
> To: <dromasca <at> avaya.com>
> Cc: <vrrp <at> ietf.org>
> Sent: Tuesday, October 17, 2006 2:36 PM
> Subject: RE: [VRRP] Re: Re: MIB Dr. Review 
> ofdraft-ietf-vrrp-unified-mib-05.txt
>
>
> Hi Joan,
>

(Continue reading)

Kalyan.Tata | 25 Oct 2006 21:59

Picon

RE: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-05.txt

Hi Joan,
I was trying fix the following :
===========
21)            INDEX    { vrrpOperationsInetAddrType,
vrrpOperationsVrId,
                      ifIndex, vrrpAssociatedIpAddr }

   W: f(VRRP-MIB), (423,8) Row "vrrpAssociatedIpAddrEntry" has
   indexing that may create variables with more than 128 sub-ids

The issue here is that the Address (InetAddress) is 0..255 octets,
but really only need either 4 octets (IPv4 address) or
16 octets (IPv6 address).  Please limit the size of this
using SIZE(0|4|16) (as an example).

DIFFSERV-MIB (and others) give an
example of how to limit the size in the conformance (and also
limit the address type).  This needs to be added to the
conformance section.
===================

++ I get the following additional warning if I add vrrpAssociatedIpAddr
to conformance section.
++ vrrpAssociatedIpAddr is part of table index and I cannot add it to
groups. 

433    5    warning: index of row `vrrpAssociatedIpAddrEntry' can exceed
OID size limit by 142 subidentifier(s)
1591    3    refined object `vrrpAssociatedIpAddr' not listed in a
mandatory or optional group

(Continue reading)

Wijnen, Bert (Bert | 26 Oct 2006 10:40

Picon

RE: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-0 5.txt

RFC4181 is clear about what to do about warnings w.r.t. 
max number of subids in an OID because of INDEX
object that (in theory) can go beyond 128.

See sect 4.6.6 in RFC4181.

And PLEASE DO Keep the specifics in MODULE-COMPLIANCE.
That shows which exact addressTypes and related max lengths
MUST be supported for compliance.

Hope this helps,
Bert

> -----Original Message-----
> From: Kalyan.Tata <at> nokia.com [mailto:Kalyan.Tata <at> nokia.com]
> Sent: Wednesday, October 25, 2006 22:00
> To: vrrp-bounces <at> ietf.org; jcucchiara <at> mindspring.com; 
> dromasca <at> avaya.com
> Cc: fenner <at> research.att.com; vrrp <at> ietf.org
> Subject: RE: [VRRP] Re: Re: MIB Dr. Review
> ofdraft-ietf-vrrp-unified-mib-05.txt
> 
> 
> Hi Joan,
> I was trying fix the following :
> ===========
> 21)            INDEX    { vrrpOperationsInetAddrType,
> vrrpOperationsVrId,
>                       ifIndex, vrrpAssociatedIpAddr }
>

(Continue reading)

Kalyan.Tata | 26 Oct 2006 21:50

Picon

RE: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-05.txt

 Thanks Bert,
	I did go through RFC RFC4181 for this but I was not sure if I
can ignore the new warning that is 
	produced by adding vrrpAssociatedIpAddr to MODULE-COMPLIANCE.

	From your mail, I take it that I can ignore the following.
>    (3) refined object `vrrpAssociatedIpAddr' not listed in a mandatory

> or optional group

	I will go ahead and keep the specifics in compliance section and
also add text to 
	DESCRIPTION indicating the size constraints.

Thanks,
Kalyan

-----Original Message-----
From: ext Wijnen, Bert (Bert) [mailto:bwijnen <at> lucent.com] 
Sent: Thursday, October 26, 2006 1:40 AM
To: Tata Kalyan (Nokia-ES/MtView); vrrp-bounces <at> ietf.org;
jcucchiara <at> mindspring.com; dromasca <at> avaya.com
Cc: fenner <at> research.att.com; vrrp <at> ietf.org
Subject: RE: [VRRP] Re: Re: MIB Dr. Review
ofdraft-ietf-vrrp-unified-mib-05.txt

RFC4181 is clear about what to do about warnings w.r.t. 
max number of subids in an OID because of INDEX object that (in theory)
can go beyond 128.

(Continue reading)

Joan Cucchiara | 27 Oct 2006 20:05

Picon

Re: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-05.txt


> ----- Original Message ----- 
> From: <Kalyan.Tata <at> nokia.com>
> To: <bwijnen <at> lucent.com>; <vrrp-bounces <at> ietf.org>; 
> <jcucchiara <at> mindspring.com>; <dromasca <at> avaya.com>
> Cc: <fenner <at> research.att.com>; <vrrp <at> ietf.org>
> Sent: Thursday, October 26, 2006 3:50 PM
> Subject: RE: [VRRP] Re: Re: MIB Dr. Review 
> ofdraft-ietf-vrrp-unified-mib-05.txt
> 
> 
> Thanks Bert,

Thanks from me also Bert!

> I did go through RFC RFC4181 for this but I was not sure if I
> can ignore the new warning that is
> produced by adding vrrpAssociatedIpAddr to MODULE-COMPLIANCE.
> 
> From your mail, I take it that I can ignore the following.
>>    (3) refined object `vrrpAssociatedIpAddr' not listed in a mandatory
> 
>> or optional group
> 
> I will go ahead and keep the specifics in compliance section and
> also add text to
> DESCRIPTION indicating the size constraints.
> 

Hi Kaylan,

(Continue reading)

Kalyan.Tata | 28 Oct 2006 20:24

Picon

RE: Re: Re: MIB Dr. Review ofdraft-ietf-vrrp-unified-mib-05.txt

Thanks Joan,
I will remove the not-accessible (index) objects from the conformance
section (this will remove the level 3 error)
and will add text to the description (This will take care of the level 5
warning below)

Thanks Again to you and Bert for all the help.

Thanks,
Kalyan

-----Original Message-----
From: ext Joan Cucchiara [mailto:jcucchiara <at> mindspring.com] 
Sent: Friday, October 27, 2006 11:05 AM
To: Tata Kalyan (Nokia-ES/MtView); Wijnen, Bert (Bert); Dan Romascanu
(E-mail)
Cc: fenner <at> research.att.com; vrrp <at> ietf.org; Joan Cucchiara
Subject: Re: [VRRP] Re: Re: MIB Dr. Review
ofdraft-ietf-vrrp-unified-mib-05.txt

 
> ----- Original Message -----
> From: <Kalyan.Tata <at> nokia.com>
> To: <bwijnen <at> lucent.com>; <vrrp-bounces <at> ietf.org>; 
> <jcucchiara <at> mindspring.com>; <dromasca <at> avaya.com>
> Cc: <fenner <at> research.att.com>; <vrrp <at> ietf.org>
> Sent: Thursday, October 26, 2006 3:50 PM
> Subject: RE: [VRRP] Re: Re: MIB Dr. Review 
> ofdraft-ietf-vrrp-unified-mib-05.txt
>

(Continue reading)

Group

gmane.ietf.vrrp.

Search Archive

Page

1 | 2

Articles in period: 10

October 2006

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane

Recent entries

draft-zhou-pim-vrrp-01 (22 May 2013)
Biggest Fake Conference in Computer Science (27 Apr 2013)
vrrp Digest, Vol 81, Issue 3 (22 Feb 2013)
Proposal for Maintenance Event for VRRP [RFC-5798] (21 Feb 2013)
Proposal for Maintenance Event for VRRP [RFC-5798] (19 Feb 2013)
Problem in addition of IP address to vrrp interface (19 Nov 2012)
FW: IPv6 G-ARP (24 Sep 2012)
VRRPV3-MIB protocol error trap question (4 Sep 2012)
Doubt in VRRPv3 Master to backup state (30 Aug 2012)
Doubt in Accept mode in VRRPv3 (7 Aug 2012)
RFC 5798 - ipv6 link-local configuration (17 May 2012)
Fwd: RFC5798 - clarification on checksum calculation (15 May 2012)
RFC5798 - clarification on checksum calculation (15 May 2012)
VRRPv3 IPv6 RFC-5798 checksum (7 May 2012)
RFC5798 - clarification on checksum calculation (2 Apr 2012)
RFC5798 - clarification on checksum calculation (29 Mar 2012)
Publication of RFC 6527 on VRRPv3 MIB (9 Mar 2012)
VRRP Algo (6 Mar 2012)
Backup->Master transition and ARP reply question (20 Feb 2012)
FW: Protocol Action: 'Definitions of Managed Objects for VRRPv3' to Pr (1 Dec 2011)
An update on draft-ietf-vrrp-unified-mib (29 Sep 2011)

Archives

2	May 2013
1	April 2013
4	March 2013
19	February 2013
1	November 2012
5	September 2012
2	August 2012
7	May 2012
2	April 2012
3	March 2012
3	February 2012
1	December 2011
1	September 2011
5	June 2011
9	April 2011
1	March 2011
4	February 2011
8	January 2011
1	December 2010
4	October 2010
4	September 2010
1	August 2010
7	July 2010
4	June 2010
1	April 2010
9	March 2010
2	February 2010
3	January 2010
5	December 2009
5	November 2009
20	October 2009
25	July 2009
5	April 2009
6	March 2009
2	February 2009
1	January 2009
3	December 2008
45	November 2008
18	October 2008
3	September 2008
10	August 2008
12	July 2008
6	June 2008
4	April 2008
7	March 2008
23	January 2008
4	December 2007
6	November 2007
14	October 2007
3	September 2007
15	August 2007
10	July 2007
5	June 2007
3	May 2007
30	April 2007
23	March 2007
11	February 2007
5	January 2007
1	December 2006
10	October 2006
10	September 2006
8	July 2006
6	June 2006
4	May 2006
2	April 2006
12	March 2006
5	February 2006
7	January 2006
11	December 2005
13	October 2005
4	September 2005
1	August 2005
10	July 2005
4	June 2005
10	May 2005
13	April 2005
10	March 2005
31	February 2005
12	January 2005
2	November 2004
6	October 2004
8	September 2004
1	August 2004
8	July 2004
12	June 2004
14	May 2004
11	April 2004
1	March 2004
13	February 2004
1	January 2004
5	December 2003
35	November 2003
20	October 2003
42	September 2003
38	August 2003
22	July 2003
9	June 2003
28	May 2003
4	April 2003
17	March 2003
15	February 2003
7	January 2003
35	December 2002
30	November 2002
19	October 2002
12	September 2002
10	August 2002
4	June 2002
5	May 2002
1	April 2002

Design

Zawodny | Right Menu | Left Menu

Your Own Design

Paste the URL of your CSS below. Download CSS template