RE: VRRP - Multiple Masters Question
"venkateshs" <[email protected]>
| Newsgroups | gmane.ietf.vrrp |
|---|---|
| Message-ID | <[email protected]> |
Hi, Don's interpretation and Mukesh's comments over that are fine. I feel that the Administrators should ensure that there is no mismatch in these critical parameters like advertisement Interval. If the problem is the the `Mater State`, Why can't the State can be retained in INIT/BACKUP when there is a mismatch in Such Parameter Values? We have similar hello Interaval Parameter in OSPF .There also,the adjacency won't form if any mismatch in Hello Interval. I think there should be some valid reasons behind the Advertisement Interval.Can Authuors of RFC please give their comments on the same? Thanks & Regards Venkatesan S. -----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Mukesh Gupta Sent: Saturday, 3 December 2005 3:34 AM To: Radia Perlman Cc: Chappell, Brett L CIV B35-Branch; Hott,Robert W CIV B35-Branch; [email protected]; Plunkett, Timothy R CIV B35-Branch; Odonoghue, Karen F CIV B35-Branch Subject: Re: [VRRP] VRRP - Multiple Masters Question > a) discard (and log an error) if the value advertised > in the VRRP message disagrees with your configured > value for hello timer.... this is what is currently > specified > > b) use the interval advertised by the master, for as long > as it is master I would vote for option b. > If we switch to b), then another decision is whether that > is configured misconfiguration or not, i.e., if an error > should be logged. Yes ! Is there any case where having different advertisement intervals on different nodes will be useful? If not, it should be considered a misconfiguration but handled gracefully ! We are waiting for another update of the VRRP for IPv6 draft to address IESG's comments. We still have some time to pitch in this change if the WG agrees to do this ! - Mukesh _______________________________________________ vrrp mailing list [email protected] https://www1.ietf.org/mailman/listinfo/vrrp *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. *************************************************************************** _______________________________________________ vrrp mailing list [email protected] https://www1.ietf.org/mailman/listinfo/vrrp