Obviously I lack context/scale and all that, so please ignore if
unwarranted.
What if you broke your buildings up into separate L3 domains: have an EX at
each building that does the "access" L3 features, and rely on the QFX5100
as your L3 core. Still doesn't solve your FBF-IPv6 though. Hmmm
On Sep 20, 2022, at 1:36 PM, Chuck Anderson via juniper-nsp
wrote:
> Why would you want DHCP snooping or dot1x on a campus core router? Those
> functions are typically implemented at the access layer switches connected
> directly to end users.
My understanding is that DHCP relay only works on
Why would you want DHCP snooping or dot1x on a campus core router? Those
functions are typically implemented at the access layer switches connected
directly to end users.
On Fri, Sep 16, 2022 at 03:11:22PM -0400, Jason Healy via juniper-nsp wrote:
> We're a small school campus that's been
On Sep 20, 2022, at 12:57 AM, Mike Gonnason wrote:
> Do you have any more details about what limitations you are encountering on
> the QFX? Is it hardware related or software?
The example that spurred my email was DDOS protection on the QFX. We're
getting lots of L3NHOP errors (still, I
Hi Jason,
Do you have any more details about what limitations you are encountering on
the QFX? Is it hardware related or software?
You can use the feature explorer to see what is supported:
On Fri, 16 Sept 2022 at 22:12, Jason Healy via juniper-nsp
wrote:
Hey Jason,
> My question is, what would be the logical "step up" from the qfx on a small
> network? I'm thinking the MX240 as it's the smallest router that has
> redundant REs. However, I have no experience with the router
Looking for a little wisdom from the list.
We're a small school campus that's been running a QFX 5100 as our core
switch/router for several years. It's been a good piece of equipment but we
continue to hit weird limitations and I'm wondering if we're pushing the
platform too hard.
My
7 matches
Mail list logo
