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

Thirumavalavan Periyannan <tperiyannan@extremenetworks.com> Fri, 18 October 2013 19:36 UTC

Return-Path: <tperiyannan@extremenetworks.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 58A3D11E81B8 for <vrrp@ietfa.amsl.com>; Fri, 18 Oct 2013 12:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 S9KVHZwX5Z2i for <vrrp@ietfa.amsl.com>; Fri, 18 Oct 2013 12:35:59 -0700 (PDT)
Received: from usnc-casht-p1.extremenetworks.com (usnc-casht-p2.extremenetworks.com [12.38.15.167]) by ietfa.amsl.com (Postfix) with ESMTP id 74E5A11E82B9 for <vrrp@ietf.org>; Fri, 18 Oct 2013 12:35:58 -0700 (PDT)
Received: from inch-casht-p2.corp.extremenetworks.com (10.120.89.29) by USNC-CASHT-P1.corp.extremenetworks.com (10.6.17.63) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 18 Oct 2013 12:35:57 -0700
Received: from INEXCHANGE.corp.extremenetworks.com ([192.168.131.111]) by inch-casht-p2.corp.extremenetworks.com ([10.120.89.29]) with mapi; Sat, 19 Oct 2013 00:57:04 +0530
From: Thirumavalavan Periyannan <tperiyannan@extremenetworks.com>
To: "vrrp@ietf.org" <vrrp@ietf.org>
Date: Sat, 19 Oct 2013 01:02:02 +0530
Thread-Topic: vrrp Digest, Vol 88, Issue 1
Thread-Index: Ac7MNLlZ59a+hVLcSZ6Rd9/w3STvSwAAwY4Q
Message-ID: <617438426768D648ABBC00E677AA0149028C9A0DF814@INEXCHANGE.corp.extremenetworks.com>
References: <mailman.64.1382122881.5048.vrrp@ietf.org>
In-Reply-To: <mailman.64.1382122881.5048.vrrp@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_617438426768D648ABBC00E677AA0149028C9A0DF814INEXCHANGEc_"
MIME-Version: 1.0
Subject: Re: [VRRP] vrrp Digest, Vol 88, Issue 1
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: Fri, 18 Oct 2013 19:36:03 -0000

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.