Re: [VRRP] vrrp Digest, Vol 88, Issue 2

Sandhya Puppala <psandhya81@yahoo.com> Tue, 22 October 2013 10:42 UTC

Return-Path: <psandhya81@yahoo.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 C89D711E8185 for <vrrp@ietfa.amsl.com>; Tue, 22 Oct 2013 03:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[AWL=-1.600, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LT9vxqZpPAkM for <vrrp@ietfa.amsl.com>; Tue, 22 Oct 2013 03:42:01 -0700 (PDT)
Received: from nm33-vm5.bullet.mail.bf1.yahoo.com (nm33-vm5.bullet.mail.bf1.yahoo.com [72.30.239.205]) by ietfa.amsl.com (Postfix) with ESMTP id D995111E8354 for <vrrp@ietf.org>; Tue, 22 Oct 2013 03:41:24 -0700 (PDT)
Received: from [98.139.212.153] by nm33.bullet.mail.bf1.yahoo.com with NNFMP; 22 Oct 2013 10:41:24 -0000
Received: from [98.139.212.228] by tm10.bullet.mail.bf1.yahoo.com with NNFMP; 22 Oct 2013 10:41:24 -0000
Received: from [127.0.0.1] by omp1037.mail.bf1.yahoo.com with NNFMP; 22 Oct 2013 10:41:24 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 437735.80581.bm@omp1037.mail.bf1.yahoo.com
Received: (qmail 49125 invoked by uid 60001); 22 Oct 2013 10:41:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1382438484; bh=QlmkMuskZq6bMZRjSPtaJbQPahd9SbfvEaOCqMR0doU=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=vy4JKdfyDpeFwEXQjaJ2jqTRswwhpOgRTUbHpensjKtNOlCp/hH91quXdRudb0IQg4wlIBIzg0aWqyq/yaQAIIguDqR2jo+GhQggn4AKQrlV8AW+iM1/Z2+Ic6MwkUH42ED8CidNL/Szj+1oD2eFyfNtq7x9OKDpVlsqcyrLpRw=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=BS8rm9UXcTtp15IOP1jz8mXwMWQsOoHVs+9U8iHPIGy2xY06oBow2usLkBTAKPWslOf++l2LMIM7GgcQeloPcajQeqphvDdoK6w5KnGVtWm+2IoQBwiaQyRKuQiVu4DAPMSYNjPBm1jj9G5P5lg0BgQ8WKMDeSYISsCtjf7Q480=;
X-YMail-OSG: iUpZHa4VM1mFuJ8j3NBE7yYpYADGWGV6Bu2CfcF5Pgjfs2w vJOWQzgSCO6daPTsdFbaaJYofmqrmHKYpPolXd5i_FmE4t9VMdwDJWkdknjo LmVgf08S5PUFxIw2UJHBWhYB6WJEd8uKDx4tibWUc0UJ9sPeYjLMms5FzIsi Mtwmjrjq6KD0_2p7D7YiCy.UETJnyyZzPIQeSfbISErxPum8Ek03WohXPeIP 1mogceyUkwva5f10.BF3qUOIvQf_KK4HTNwpQK0IJ0.Y48ALSC_WOQlk60bg 9_eaXdutOz1zdFVGckZfzuShk1IsBCkWlMKV9n_IL40yJmWoYwHTiVQPsEXN FHGS9ZGPaMKjHeYv_4IbNVeDlmXKhAZT77S9hi76e2W1CVozOBoQjBAI1_Wc ZSc5Wq1QeOGb5bFk_.taiSQlqXrBDSYyFPTJLDJWmF0eUoPCP4Dj29kRt5jA vSzruN2Rsh0S9f1Ed6UZokVeCPwZbmwrtaP.LIB..lVO6dpcsap0jz1z2rKu pC3VXZnPcXJVcKhPHSPUP9OjazcvW6HgjOGgDjNx14zhsnee0KNM1iRyDsYe bzCG72GS7IcgFNS.cfuJgi46c2FAN31xuo0nouQgxayhzPUU5SkI-
Received: from [203.91.201.57] by web160102.mail.bf1.yahoo.com via HTTP; Tue, 22 Oct 2013 03:41:24 PDT
X-Rocket-MIMEInfo: 002.001, CgpIaSBTcmVlbmF0aGEsCgpUaGFuayB5b3UgZm9yIHlvdXIgcmVzcG9uc2UuCkkgYWdyZWUgd2l0aCB5b3UuIEkgYWxzbyBmZWVsLCBib3RoIHNob3VsZCBiZSBNYXN0ZXIsIGJ1dCBpbiBSRkMgNTc5OC4KSW4gc2VjdGlvbiA3LjEKSWYgYW55IG9uZSBvZiB0aGUgYWJvdmUgY2hlY2tzIGZhaWxzLCB0aGUgcmVjZWl2ZXIgTVVTVCBkaXNjYXJkIHRoZSBwYWNrZXQsIFNIT1VMRCBsb2cgdGhlIGV2ZW50LCBhbmQgTUFZIGluZGljYXRlIHZpYSBuZXR3b3JrIG1hbmFnZW1lbnQgdGhhdCBhbiBlcnJvciBvY2N1cnIBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.160.587
References: <mailman.41.1382209253.349.vrrp@ietf.org>
Message-ID: <1382438484.49051.YahooMailNeo@web160102.mail.bf1.yahoo.com>
Date: Tue, 22 Oct 2013 03:41:24 -0700 (PDT)
From: Sandhya Puppala <psandhya81@yahoo.com>
To: "vrrp@ietf.org" <vrrp@ietf.org>
In-Reply-To: <mailman.41.1382209253.349.vrrp@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1775031368-1806675558-1382438484=:49051"
Subject: Re: [VRRP] vrrp Digest, Vol 88, Issue 2
X-BeenThere: vrrp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sandhya Puppala <psandhya81@yahoo.com>
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: Tue, 22 Oct 2013 10:42:07 -0000


Hi Sreenatha,

Thank you for your response.
I agree with you. I also feel, both should be Master, but in RFC 5798.
In section 7.1
If any one of the above checks fails, the receiver MUST discard the packet, SHOULD log the event, and MAY indicate via network management that an error occurred. 

- MAY verify that "Count IPvX Addrs" and the list of IPvX address(es) match the IPvX Address(es) configured for the VRID. If the above check fails, the receiver SHOULD log the event and MAY indicate via network management that a misconfiguration was detected. 


It is not mentioned to drop the packet. In the same section for other failed cases it clearly mentioned to drop the packet.
Please let me know your comments.


Thanks,Sandhya



On Sunday, October 20, 2013 12:31 AM, "vrrp-request@ietf.org"; <vrrp-request@ietf.org>; wrote:
 
If you have received this digest without all the individual message
attachments you will need to update your digest options in your list
subscription.  To do so, go to 

https://www.ietf.org/mailman/listinfo/vrrp

Click the 'Unsubscribe or edit options' button, log in, and set "Get
MIME or Plain Text Digests?" to MIME.  You can set this option
globally for all the list digests you receive at this point.



Send vrrp mailing list submissions to
    vrrp@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://www.ietf.org/mailman/listinfo/vrrp
or, via email, send a message with subject or body 'help' to
    vrrp-request@ietf.org

You can reach the person managing the list at
    vrrp-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of vrrp digest..."


Today's Topics:

   1. Re: vrrp Digest, Vol 88, Issue 1 (Thirumavalavan Periyannan)
   2. Re: :  VRRP IPV6 Session Configuration with different link
      (Sreenatha Setty)


----------------------------------------------------------------------

Message: 1
Date: Sat, 19 Oct 2013 01:02:02 +0530
From: Thirumavalavan Periyannan <tperiyannan@extremenetworks.com>;
To: "vrrp@ietf.org"; <vrrp@ietf.org>;
Subject: Re: [VRRP] vrrp Digest, Vol 88, Issue 1
Message-ID:
    <617438426768D648ABBC00E677AA0149028C9A0DF814@INEXCHANGE.corp.extremenetworks.com>;
    
Content-Type: text/plain; charset="us-ascii"

Hi,



Yes, If Virtual IP (including link local) is different for specific VRID then it will be DUAL Master State on DUT1 & DUT2 routers.


Thanks & Regards,
Thirumavalavan Periyannan
Associate SQA Engineer, Extreme Networks



-----Original Message-----
From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org] On Behalf Of vrrp-request@ietf.org
Sent: Saturday, October 19, 2013 12:31 AM
To: vrrp@ietf.org
Subject: vrrp Digest, Vol 88, Issue 1



If you have received this digest without all the individual message attachments you will need to update your digest options in your list subscription.  To do so, go to



https://www.ietf.org/mailman/listinfo/vrrp



Click the 'Unsubscribe or edit options' button, log in, and set "Get MIME or Plain Text Digests?" to MIME.  You can set this option globally for all the list digests you receive at this point.







Send vrrp mailing list submissions to

            vrrp@ietf.org<mailto:vrrp@ietf.org>



To subscribe or unsubscribe via the World Wide Web, visit

            https://www.ietf.org/mailman/listinfo/vrrp

or, via email, send a message with subject or body 'help' to

            vrrp-request@ietf.org<mailto:vrrp-request@ietf.org>



You can reach the person managing the list at

            vrrp-owner@ietf.org<mailto:vrrp-owner@ietf.org>



When replying, please edit your Subject line so it is more specific than "Re: Contents of vrrp digest..."





Today's Topics:



   1. VRRP IPV6 Session Configuration with different link local

      addresses (as VIP) (Sandhya Puppala)





----------------------------------------------------------------------



Message: 1

Date: Thu, 17 Oct 2013 22:27:21 -0700 (PDT)

From: Sandhya Puppala <psandhya81@yahoo.com>;

To: "vrrp@ietf.org"; <vrrp@ietf.org>;

Subject: [VRRP] VRRP IPV6 Session Configuration with different link

            local     addresses (as VIP)

Message-ID:

            <1382074041.37205.YahooMailNeo@web160103.mail.bf1.yahoo.com>;

Content-Type: text/plain; charset="iso-8859-1"







Hi,





Consider the below topology,

DUT1 ----- DUT2



Configured DUT1 as owner with vip as fe80::ca35:b8ff:fea8:82fd.

And configured DUT2 as not-owner with vip as fe80::ca35:b8ff:fea8:8212



VIP on DUT1 and DUT2 are different.



What should be the states of DUT1 & DUT2?



According to draft http://tools.ietf.org/html/draft-ietf-vrrp-ipv6-spec-07

section 7.1,



If the packet was not generated by the address owner (Priority does not equal 255 (decimal)), the receiver MUST drop the packet, otherwise continue processing.



1. Does it need to compare the vip address of received packet and its vip address?

??? If there are different what need to be done?



As per RFC "DUT2 should accept the packet from DUT1".

Does this mean DUT2 state should become backup?







Thanks,

Sandhya

-------------- next part --------------

An HTML attachment was scrubbed...

URL: <http://www.ietf.org/mail-archive/web/vrrp/attachments/20131017/5babdb8d/attachment.htm>



------------------------------



_______________________________________________

vrrp mailing list

vrrp@ietf.org<mailto:vrrp@ietf.org>

https://www.ietf.org/mailman/listinfo/vrrp





End of vrrp Digest, Vol 88, Issue 1

***********************************

________________________________
DISCLAIMER:
This e-mail and any attachments to it may contain confidential and proprietary material and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ietf.org/mail-archive/web/vrrp/attachments/20131019/e1ee034d/attachment.htm>

------------------------------

Message: 2
Date: Sat, 19 Oct 2013 12:36:50 +0530
From: Sreenatha Setty <sreenatha.setty@ibtechnology.com>;
To: <vrrp@ietf.org>;
Cc: psandhya81@yahoo.com
Subject: Re: [VRRP] :  VRRP IPV6 Session Configuration with different
    link
Message-ID:
    <DB36B077CF387C4989BCC57D685FA30102F2BF4D@GRGHEXCHANGE.grgh.indiabulls.com>;
    
Content-Type: text/plain; charset="us-ascii"

Hi Sandhya,
     Normally Vendors will implement based on the standard RFC not on
the draft version, since drafts can undergo changes very frequently. I
am not sure for what reason you are referring that particular draft. 
I suggest you to refer latest VRRP v3 RFC: 5798 for better
understanding.

Coming to your query,  according to latest RFC 5798( section 7.1), " If
the packet was not generated by the address owner (Priority does not
equal 255 (decimal)), the receiver MUST drop the packet, otherwise
continue processing" condition is removed.  So router can accept vrrp
packets even if it is generated by other than the address owner if all
other conditions are met. (Mentioned in the above sections 7.1 of RFC
5798)

In your case, you mentioned different VIPs are configured. In the same
section only,  RFC tells, 
      - MAY verify that "Count IPvX Addrs" and the list of IPvX
      address(es) match the IPvX Address(es) configured for the VRID.

So according to this logic, both DUTs will discard the vrrp packets
since VIP address are different and both DUTs will become VRRP Masters.

And standard VRRP MIB(RFC 6527) specifies one statistics object to
represent these kind of address list errors:

vrrpv3StatisticsAddressListErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of packets received for which the
               address list does not match the locally configured
               list for the virtual router.

               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
           ::= { vrrpv3StatisticsEntry 10 }

Summary to your query:
    1. Both DUTs will detects VIP address error, discards the packets
and becomes the Masters.
    2. DUTs  increment the statistics variable
vrrpv3StatisticsAddressListErrors.


Additionally, if you configure different VRIDs, packets will be
discarded before checking the VIPs only. Both DUTs will become masters
and will increment vrrpv3RouterVrIdErrors statistics variable (RFC
6527).

vrrpv3RouterVrIdErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
          STATUS       current
           DESCRIPTION
               "The total number of VRRP packets received with a
                VRID that is not valid for any virtual router on this
                router.

               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3GlobalStatisticsDiscontinuityTime."

           REFERENCE "RFC 5798, Section 5.2.3"
           ::= { vrrpv3Statistics 3 }

Thanks & Regards,
B Sreenatha Setty
Senior Software Engineer
IB Technology

------------------------------------------------------------------------
--------------------------------------
Message: 1
Date: Thu, 17 Oct 2013 22:27:21 -0700 (PDT)
From: Sandhya Puppala <psandhya81@yahoo.com>;
To: "vrrp@ietf.org"; <vrrp@ietf.org>;
Subject: [VRRP] VRRP IPV6 Session Configuration with different link
    local    addresses (as VIP)
Message-ID:
    <1382074041.37205.YahooMailNeo@web160103.mail.bf1.yahoo.com>;
Content-Type: text/plain; charset="iso-8859-1"



Hi,


Consider the below topology,
DUT1 ----- DUT2

Configured DUT1 as owner with vip as fe80::ca35:b8ff:fea8:82fd.
And configured DUT2 as not-owner with vip as fe80::ca35:b8ff:fea8:8212

VIP on DUT1 and DUT2 are different.

What should be the states of DUT1 & DUT2?

According to draft
http://tools.ietf.org/html/draft-ietf-vrrp-ipv6-spec-07
section 7.1, 

If the packet was not generated by the address owner (Priority does not
equal 255 (decimal)), the receiver MUST drop the packet, otherwise
continue processing.

1. Does it need to compare the vip address of received packet and its
vip address?
??? If there are different what need to be done?

As per RFC "DUT2 should accept the packet from DUT1".
Does this mean DUT2 state should become backup?



Thanks,
Sandhya
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.ietf.org/mail-archive/web/vrrp/attachments/20131017/5babdb8d
/attachment.htm>

------------------------------

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www.ietf.org/mailman/listinfo/vrrp


End of vrrp Digest, Vol 88, Issue 1
***********************************
Disclaimer : 
This email communication may contain privileged and confidential information and is intended for the use of the addressee only.If you are not an intended recipient you are requested not to reproduce, copy disseminate or in any manner distribute this email communication as the same is strictly prohibited. If you have received this email in error, please notify the sender immediately by return e-mail and delete the communication sent in error. Email communications cannot be guaranteed to be secure & error free and IB Technology is not liable for any errors in the email communication or for the proper, timely and complete transmission thereof.



------------------------------

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www.ietf.org/mailman/listinfo/vrrp


End of vrrp Digest, Vol 88, Issue 2
***********************************