Keep in mind the QFX5100 doesn't support evpn or vpls. To do vpls right now, we're having to l2vpn back to an MX tunnel interface and stitch into a bridge domain. It's not pretty but so far it has worked. We've got our fingers crossed that evpn is coming soon.
Also, the 5100's apparently aren't using ASICs, or at least aren't using an ASIC on the interfaces that will support flexible-ethernet-services. What this means is that I can't L2 switch a customer on the same QFX interface that I'm either A) Terminating another customer at L3 (l3 vpn for example), or B) Doing a vlan-ccc/l2circuit/l2vpn connection on. This means there are some use cases (p2p ethernet circuits between olt's in the same CO for instance) that may require more than 1 port between the QFX and the olt. Joe On Thu, Jun 4, 2015 at 8:26 AM, Tim Jackson <[email protected]> wrote: > I'd recommend QFX5100 or EX4600. Same hardware inside for both. > > Beware that there are a few issues with DHCP and DHCPv6 pass through on > them, but that seems to be resolved now. > On Jun 4, 2015 6:22 AM, "Colton Conor" <[email protected]> wrote: > > > We need a Juniper switch with at least 24 built in SFP+ ports. Looks like > > Juniper has a ton of options including the EX4500, EX4550, EX4600, and > the > > QFX line which I don't know much about. This switch will be for > aggregation > > purposes for an access network that has GPON OLT's with 10G uplinks on > > them. What do you recommend? Which has the latest hardware? Which is the > > most cost effective? Any limitations to be aware of? > > _______________________________________________ > > juniper-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
