RARE user and assistance email list

[Xavier Jeannin <>]

Do not consider my previous email, I found the bundle documentation

I will try it and then come back if have additional question

Regards
Xavier

> Thank you
> Regards
> Xavier
>
> Le 20/10/2022 à 10:03, mc36 a écrit :
> > hi,
> > lacp is there:
> > you have to configure it per member interface with both the lacp knob 
> > and the bundle-group knob...
> > the first one is just the protocol sender and you can omit if you do 
> > "mode on" on the remote side...
> > so that latter is the interesting part in the fastpath, and it's 
> > heavily tested with the dataplanes...
> > br,
> > cs
> >
> > On 10/20/22 09:58,  wrote:
> > > Hello
> > >
> > > I allow myself to post again this request about LACP supporting 
> > > trunk as if this would not be implemented, it will impact strongly 
> > > our use case deployment.
> > >
> > > Thank you
> > > Regards
> > > Xavier
> > >
> > > Le 17/10/2022    18:23, Xavier Jeannin a   crit  :
> > > > Hello
> > > >
> > > > I am still stuck with the creation of LACP handling a trunk.
> > > > In the meantime, I review my configuration and see that 
> > > > "bridge-group 2" was not declared in P4 server after correction 
> > > > same pb.
> > > > This really something that block this work.
> > > >
> > > > Any suggestion ?
> > > >
> > > > Regards
> > > > Xavier
> > > >
> > > > Le 27/09/2022    10:37, Xavier Jeannin a   crit  :
> > > > > Hello
> > > > >
> > > > > I create a testbed on which (see picture attached):
> > > > >
> > > > >   * the client is connected on a WEDGE (L2-PPN) at Layer 2 using 
> > > > > Ethernet   or VLAN
> > > > >   * The WEDGE (L2PPN) should be connected to our backbone thanks 
> > > > > to a bond of interfaces (LACP). The traffic on the LACP must be a 
> > > > > VLAN trunk.
> > > > >
> > > > > I see a strange behaviour and it is certainly due to how I 
> > > > > configure it.
> > > > >
> > > > > If I put the 2   vlans (11-12) on the all interfaces taking part 
> > > > > on the LACP, it does not work.
> > > > > If   I put the 1 vlan only on each interface of the taking part on 
> > > > > the LACP, it   works. But in this case the traffic should not be 
> > > > > well shared between the LACP links.
> > > > >
> > > > > I suspect I implement this use case not appropriately (see 
> > > > > configuration attached + picture). Any suggestion?
> > > > >
> > > > > Regards
> > > > > Xavier
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Xavier JEANNIN
> > > > > Network Dpt.
> > > > > GN4-3 Network technology evolution (WP6 T1) task leader
> > > > > T  l. : +33 1 5394 2042
> > > > > Mob. : +33 6 3017 0963
> > > > > www.renater.fr
> > > > --
> > > > Xavier JEANNIN
> > > > Network Dpt.
> > > > GN4-3 Network technology evolution (WP6 T1) task leader
> > > > T  l. : +33 1 5394 2042
> > > > Mob. : +33 6 3017 0963
> > > > www.renater.fr
> > >
> > > --
> > > Xavier JEANNIN
> > > Network Dpt.
> > > GN4-3 Network technology evolution (WP6 T1) task leader
> > > T  l. : +33 1 5394 2042
> > > Mob. : +33 6 3017 0963
> > > www.renater.fr
> > >
> > > _._,_._,_
> > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ 
> > >
> > > Groups.io Links:
> > >
> > > You receive all messages sent to this group.
> > >
> > > View/Reply Online (#768) <https://groups.io/g/freertr/message/768> | 
> > > Reply To Group 
> > > <> 
> > > | Reply To Sender 
> > > <> 
> > > | Mute This Topic <https://groups.io/mt/93945667/6006518> | New 
> > > Topic <https://groups.io/g/freertr/post>
> > > Your Subscription <https://groups.io/g/freertr/editsub/6006518> | 
> > > Contact Group Owner <> | Unsubscribe 
> > > <https://groups.io/g/freertr/unsub> []
> > >
> > > _._,_._,_
--
Xavier JEANNIN
Network Dpt.
GN4-3 Network technology evolution (WP6 T1) task leader
Tél. : +33 1 5394 2042
Mob. : +33 6 3017 0963
www.renater.fr