Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley)

2017-12-05 Thread adamv0025
ginal Message- > From: Chris Burton [mailto:chris.bur...@speakeasy.net] > Sent: Sunday, December 03, 2017 6:37 AM > To: adamv0...@netconsultings.com; juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley) > > For better or worse I d

Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley)

2017-12-04 Thread James Bensley
Amazon recently announced bare metal instances which provide access to the CPU virtual instruction set such as Intel VT-x, so although I haven't had a chance to look into it much just yet, I'm hoping one can spin up vMX/ASR9Kv etc. using these instances in Amazon and just offload the scaling issue

Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley)

2017-12-02 Thread Chris Burton
For better or worse I do remember those days, though I was referring to recent hardware switches/bridges (should have clarified that).  To my knowledge that only applies to things like the STP protocols, but I could be wrong, again would need to read through the specifications again to be sure

Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley)

2017-12-02 Thread adamv0025
Hey, > local link and not forwarded by the soft bridge by default (I do not know of > any hardware bridges that allow you to disabled this restriction, if you know > of any I would be interested. > My understanding is that Carrier-Ethernet grade switches/routers should allow you to

Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley)

2017-12-02 Thread Vincent Bernat
❦ 1 décembre 2017 21:43 -0800, Chris Burton  : > LACP and LLDP (and the like) are link local only protocols (would need > to dig through the specifications to find the exact rules), they > should not be forwarded by the bridge 802.1Q-2005, 8.6.3 and 8.13.4. However,

Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley)

2017-12-01 Thread Chris Burton
Glad the conversation helped.  The note about the scripts was a general FYI in case there are others looking to use the scripts as there have been many conversations about the use of LLDP and LACP with the vMX in the past, both on this thread as well as other chats, forums, etc... just

Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley)

2017-11-12 Thread adamv0025
> Chris Burton > Sent: Saturday, November 11, 2017 11:50 PM > > This has been discussed a few times on this list and other forums. That being > said, if you are looking to do this with Linux bridge you will need to modify > the net/br_private.h header library to remove the mask restriction placed

Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley)

2017-11-11 Thread Chris Burton
This has been discussed a few times on this list and other forums. That being said, if you are looking to do this with Linux bridge you will need to modify the net/br_private.h header library to remove the mask restriction placed on using group_fwd_mask setting in /sys/class/net and recompile

Re: [j-nsp] [c-nsp] LACP between router VMs (James Bensley)

2017-11-09 Thread Sergio D.
You can use the following on ovs: ovs-vsctl set bridge other-config:forward-bpdu=true according to the ovs-vsctl docs[0] this includes 01:80:c2:00:00:0x which is LACP. [0] http://openvswitch.org/support/dist-docs/ovs-vswitchd.conf.db.5.html > >1. Re: [c-nsp] LACP between router VMs