headers
Adrian Farrel | 22 May 2013 18:10
Picon

draft-zhou-pim-vrrp-01

Hello VRRP list,

Please be aware of this work in the PIM working group and comment there if you
have an opinion.

Thanks,
Adrian

> -----Original Message-----
> From: pim-bounces <at> ietf.org [mailto:pim-bounces <at> ietf.org] On Behalf Of Mike
> McBride
> Sent: 22 May 2013 07:17
> To: Xuxiaohu; sganesan <at> extremenetworks.com; rajiva <at> cisco.com;
> pjhingra <at> cisco.com; weizho2 <at> cisco.com
> Cc: Mike McBride; pim <at> ietf.org
> Subject: Re: [pim] call for adoption: draft-zhou-pim-vrrp-01
> 
> Folks,
> 
> We have this new draft-zhou-pim-vrrp-01 which we are about to adopt
> into the pim wg. It has been brought to the WGs attention that there
> is a older draft (draft-xu-pim-drpriority-auto-adjustment-03) which
> may have some overlap with the new one. That older draft does contain
> information about VRRP aware PIM which is attributed to Stig in the
> acknowledgements. If the five of you authors feel that there is some
> validity that the older draft contains some information being used in
> the new draft, you may want to acknowledge that in the references or
> acknowledgements. It appears the drafts are dissimilar enough to not
> be merged but I may be wrong. Please share your opinions on this so we
> can establish consensus within the group and move the document along.
(Continue reading)

Permalink | Reply | 0 comments |
headers
hammondjohnson | 27 Apr 2013 19:54
Favicon

Biggest Fake Conference in Computer Science

We are researchers from different parts of the world and conducted a study on  
the world’s biggest bogus computer science conference WORLDCOMP 
( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia 
from University of Georgia, USA.

We submitted a fake paper to WORLDCOMP 2011 and again (the same paper 
with a modified title) to WORLDCOMP 2012. This paper had numerous 
fundamental mistakes. Sample statements from that paper include: 

(1). Binary logic is fuzzy logic and vice versa
(2). Pascal developed fuzzy logic
(3). Object oriented languages do not exhibit any polymorphism or inheritance
(4). TCP and IP are synonyms and are part of OSI model 
(5). Distributed systems deal with only one computer
(6). Laptop is an example for a super computer
(7). Operating system is an example for computer hardware

Also, our paper did not express any conceptual meaning.  However, it 
was accepted both the times without any modifications (and without 
any reviews) and we were invited to submit the final paper and a 
payment of $500+ fee to present the paper. We decided to use the 
fee for better purposes than making Prof. Hamid Arabnia (Chairman 
of WORLDCOMP) rich. After that, we received few reminders from 
WORLDCOMP to pay the fee but we never responded. 

We MUST say that you should look at the above website if you have any thoughts 
to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have stopped 
indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See 
http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the 
conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thirumavalavan Periyannan | 22 Feb 2013 14:56
Favicon

Re: vrrp Digest, Vol 81, Issue 3

Hi Anurag,

You meant to say that when we do graceful failover on VRRP Master then traffic needs switch to VRRP backup
router without waiting for Master_Down_Interval time.

Please correct me if I am wrong.

Sent from my iPhone

On 22-Feb-2013, at 5:11 PM, "vrrp-request <at> ietf.org" <vrrp-request <at> 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 <at> 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 <at> ietf.org
(Continue reading)

Permalink | Reply | 9 comments |
headers
sreenatha | 21 Feb 2013 17:03
Favicon

Re: Proposal for Maintenance Event for VRRP [RFC-5798]

Hi Anurag,
     Proposed idea is good. I have some queries on this proposal:

1. On receiving new maintenance_event, priority of the router is not 
changed, right? So if back-up router has less priority, even if Master 
receives the ADVERTISEMENT from the backup router, Master will discard. 
So how the Master router state is going to change?

2. How much time Master router should wait to receive ADVERTISEMENT 
message from any backup router?

3. Standard VRRP MIB(RFC-2787) does not allow user to configure '0' for 
VRRP Priority. So you are proposing to change this value also?

Thanks,
Sreenatha Setty

On 02/21/2013 01:30 AM, vrrp-request <at> 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.
>
>
>
(Continue reading)

Permalink | Reply | 12 comments |
headers
Anurag Kothari (ankothar | 19 Feb 2013 23:08
Picon
Favicon

Proposal for Maintenance Event for VRRP [RFC-5798]

Hi

 

I want to propose a new Maintenance Event (modification of Shutdown Event) for VRRP (RFC-5798] which would allow to gracefully failover the VRRP Master to Redundant (Backup Router).

 

Problem Statement:

VRRP preemption is not configured on the redundant / backup router. How to initiate VRRP Traffic to failover to the redundant / backup router gracefully without modifying the configuration on the redundant / backup router (i.e. adding preemption)

 

Proposed Solution:

Addition to Section 6.4.3 of RFC-5798:

 

- If a Maintenance event is received, then:

 

+ Cancel the Adver_Timer

 

+ Send an ADVERTISEMENT with Priority = 0

 

-endif // maintenance recv

 

Unlike Shutdown event the router will not “Transition to the {Initialize} state” and continue to be Master and forward traffic  till the backup router sends an ADVERTISEMENT (triggered by receiving an ADVERTISEMENT with Priority = 0) and becomes master.

 

Here are couple of examples of how a maintenance event may be triggered

 

1)      By some user command e.g. “maintenance-mode” in the vrrp configuration.

2)      By setting the priority = 0 for a particular VRID.

 

Thanks

-Anurag

 

_______________________________________________
vrrp mailing list
vrrp <at> ietf.org
https://www.ietf.org/mailman/listinfo/vrrp
Permalink | Reply | 0 comments |
headers
Gauri Senad | 19 Nov 2012 22:28
Picon

Problem in addition of IP address to vrrp interface

Hello,

I am using 6WIND stack for addition vrrp-interface. When I add first vrrp in the system using 6wing CLI its is getting added successfully. Now when the second vrrp interface is added its IP address is not getting attached to the vrrp interface. Following is the "ifconfig" output. Any one has seen such issues earlier with 6wind stack?

 ifconfig   | grep -A 5 vrrp
vrrpv2g5  Link encap:Ethernet  HWaddr 00:00:5E:00:01:05
          inet addr:10.112.107.99  Bcast:10.112.107.103  Mask:255.255.255.248
          inet6 addr: fe80::200:5eff:fe00:105/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:964 errors:0 dropped:0 overruns:0 frame:0
          TX packets:224 errors:1 dropped:0 overruns:0 carrier:0
--
vrrpv2g6  Link encap:Ethernet  HWaddr 00:00:5E:00:01:06
          inet6 addr: fe80::200:5eff:fe00:106/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 -------------------> There is no IP address on this VRRP. Ideally there should be 10.112.107.107/29 on it.
          RX packets:40 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:2 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000


Regards,

Gauri 

_______________________________________________
vrrp mailing list
vrrp <at> ietf.org
https://www.ietf.org/mailman/listinfo/vrrp
Permalink | Reply | 0 comments |
headers
Thirumavalavan Periyannan | 24 Sep 2012 14:23
Favicon

FW: IPv6 G-ARP

Hi All,

I am seeing two different things in G-ARP VRRPv3 IPv4/IPv6

VRRPv3-IPV4 – It’s taking switch physical mac address as source mac address of layer 2 header but in
IPv6 Layer 2 header taking Virtual mac as source mac.

I am suspecting the VRRPv3-IPv4 behavior here. Could you please let me know your suggestions.

Thanks & Regards,
Thirumavalavan P
Associate SQA Engineer
________________________________
direct:      +91-44-30002217
mobile:    +91-9611736683

[cid:image002.png <at> 01CD95AD.71C35540]


________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2012.0.2221 / Virus Database: 2437/5273 - Release Date: 09/17/12
________________________________ No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2012.0.2221 / Virus Database: 2437/5273 - Release Date: 09/17/12

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.
_______________________________________________
vrrp mailing list
vrrp <at> ietf.org
https://www.ietf.org/mailman/listinfo/vrrp
Permalink | Reply | 0 comments |
headers
tony vanderpeet | 4 Sep 2012 03:24
Picon
Favicon

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 mailing list
vrrp <at> ietf.org
https://www.ietf.org/mailman/listinfo/vrrp
Permalink | Reply | 3 comments |
headers
Thirumavalavan Periyannan | 30 Aug 2012 21:51
Favicon

Doubt in VRRPv3 Master to backup state

Hi All,

 

How long it will take when the router transits from Master to backup when it hears the advertisement packet with different advertisement interval and higher priority.

 

In RFC 5798 haven’t specified timers here,

 

Please correct me If I am wrong.

 

(725) -* If the Priority in the ADVERTISEMENT is greater

            than the local Priority,

            (730) -* or

            (735) -* If the Priority in the ADVERTISEMENT is equal to

            the local Priority and the primary IPvX Address of the

            sender is greater than the local primary IPvX Address, then:

 

               (740) - <at> Cancel Adver_Timer

               (745) - <at> Set Master_Adver_Interval to Adver Interval

               contained in the ADVERTISEMENT

               (750) - <at> Recompute the Skew_Time

               (755) <at> Recompute the Master_Down_Interval

               (760) <at> Set Master_Down_Timer to Master_Down_Interval

               (765) <at> Transition to the {Backup} state

 

 

Thanks & Regards,

Thirumavalavan P

Associate SQA Engineer

direct:      +91-44-30002217

mobile:    +91-9611736683

 

 

 


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.
_______________________________________________
vrrp mailing list
vrrp <at> ietf.org
https://www.ietf.org/mailman/listinfo/vrrp
Permalink | Reply | 0 comments |
headers
Thirumavalavan Periyannan | 7 Aug 2012 08:58
Favicon

Doubt in Accept mode in VRRPv3

Hi All,

 

I have a doubt in VRRPv3 accept mode.

 

Why Accept mode introduced in VRRPv3 and use of accept mode?

 

Thanks & Regards,

Thirumavalavan P

Associate SQA Engineer

direct:      +91-44-30002217

mobile:    +91-9611736683

 

 

 


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.
_______________________________________________
vrrp mailing list
vrrp <at> ietf.org
https://www.ietf.org/mailman/listinfo/vrrp
Permalink | Reply | 0 comments |
headers
Alexey Razuvaev | 17 May 2012 16:10
Picon

RFC 5798 - ipv6 link-local configuration

Hi,

VRRPv3 for IPv6 specifies that the first address should be a link-local address. If that is configured by an operator and not generated by software, how do we make sure that there are no collisions with existing link local addresses? Since the protocol spec does not mention any link-local address range dedicated to VRRP, how do current implementations make sure that it doesn't collide with anyone else on the network? I understand that IPv4 has similar issues, but in IPv4 case the network would be statically configured, unlike in IPv6 case where link-local addresses are generated from MAC.

Additionally what is the reasoning behind not allowing to use Virtual MAC address to generate link-local address? It seems like it would simplify the set up, but I think I am missing some crucial detail.

Also, if I were to allow global IPv6 to be configured for virtual router, I would have to force the operator to also configure a link-local address, correct?

Thanks,
Alexey.
_______________________________________________
vrrp mailing list
vrrp <at> ietf.org
https://www.ietf.org/mailman/listinfo/vrrp
Permalink | Reply | 1 comment |

Gmane