[j-nsp] vrrp groups

Niels Ardts N.Ardts at intermax.nl
Fri Oct 30 14:26:32 EDT 2009

Ah, yes that makes sense! Thanks for your explanation.


Op 30 okt 2009 om 17:44 heeft "Terry Baranski" <tbaranski at mail.com>  
het volgende geschreven:\

> On Fri, Oct 30, 2009 at 11:02AM, Niels Ardts wrote:
>> However, an error is returned:
>> edit interfaces ae1 unit 241 family inet address yy]
>> 'vrrp-group 241'
>>  Duplicate interface: ae1 unit: 241 vrrp-group: 241 for address:  
>> bbbb and
> address: aaaa
>> error: configuration check-out failed
>> [edit interfaces ae1 unit 241]
>> We're running JunOS 8.0R2.8 on a M7i.
>> Any ideas?
> You're trying to use a given VRRP group ID twice on the same
> VLAN/subinterface.  I'm not surprised that this doesn't commit --  
> the VRRP
> protocol itself probably doesn't support such a configuration.  What  
> will
> work is using the same group ID multiple times on different
> VLAN/subinterfaces within the same physical interface.
> -Terry
> -----Oorspronkelijk bericht-----
> Van: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] Namens Terry Baranski
> Verzonden: dinsdag 29 september 2009 1:52
> Aan: juniper-nsp at puck.nether.net
> Onderwerp: Re: [j-nsp] vrrp groups
> On Mon, Sep 28, 2009 at 19:10:59, Harry Reynolds wrote:
>> Note that while you can assign the same group number to multiple ifls
>> on the same IFD best practice is not to as this can cause some issues
>> with learning bridges as noted below, each group shares the same v- 
>> mac.
> I have to say -- this is a recommendation from Juniper that I've never
> understood.  We've used group 1 exclusively for years (with hundreds  
> of
> VLANs per interface in some cases) without issue.  Using separate  
> group IDs
> seems overly complex and unnecessary.  As long as your switches aren't
> bleeding VLANs together there's no conceivable harm. (And if they  
> do, having
> the same group ID ensures you'll discover the problem quickly. :-)
> To clarify for the original poster: there's no *hard limit* which will
> prevent you from configuring 300 VRRP groups (with non-unique group  
> IDs) on
> one physical interface. (Even though the documentation said  
> otherwise up
> until 9.6.)  I would expect things to generally be okay with default  
> timers
> but I've never tried group counts in the hundreds with anything  
> smaller than
> an m40e.
> -Terry
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> Tenzij schriftelijk anders is overeengekomen, zijn op al onze
> rechtsbetrekkingen de Algemene Voorwaarden van Intermax van  
> toepassing. Deze
> zijn middels deze directe link
> http://www.intermax.nl/algemenevoorwaardenintermax.pdf in te zien en/ 
> of
> kunnen op verzoek worden toegezonden. Toepasselijkheid van eventuele  
> inkoop-
> of andere voorwaarden van opdrachtgever dan wel van derden wordt dan  
> ook
> uitdrukkelijk van de hand gewezen. Nederlands recht is exclusief van
> toepassing.
> De informatie verzonden met dit E-mail bericht is uitsluitend  
> bestemd voor
> de geadresseerde. Gebruik van deze informatie door anderen dan de
> geadresseerde is verboden. Openbaarmaking, vermenigvuldiging,  
> verspreiding
> en/of verstrekking van deze informatie aan derden is niet toegestaan.
> Intermax staat niet in voor de juiste en volledige overbrenging van de
> inhoud van een verzonden E-mail, noch voor tijdige ontvangst daarvan.
> Please consider the environment before printing this e-mail.

More information about the juniper-nsp mailing list