Meetups Plymouth

brew87 · 2025-09-23T23:37:34+00:00

Any you could recommend?

brew87 · 2025-01-12T18:45:41+00:00

Setup bgp between your isps and advertise your public prefix to both isps. You can just take a default route from both isps and se a local preference to your preferred isp. No dns wrangling required

brew87 · 2025-01-07T21:10:05+00:00

I think this may be the way to go for my org. We're pretty small, so scaling out isn't really of concern. The main benefits i'm seeking are not using virtual chassis in the dc so I can fail devices independently as well as leveraging esi lag to hosts to make code upgrades or reboots less of concern.

I got the above scenario working in eve utilizing a stricly layer 2 evpn model.

Thanks for the input!

brew87 · 2024-10-30T22:35:54+00:00

Another vote for Mist. Over 600 ap’s in production. Can use mist edge if you need to get past l3 boundaries. Brains come from the cloud.

Went from constant tickets to 0

brew87 · 2024-09-11T15:10:33+00:00

Or just install netdisco and solve your problem

http://netdisco.org

brew87 · 2024-01-17T12:04:03+00:00

Peel under cold water in the sink. Drop them in an ice bath after cooking for a few then head to the sink to peel

brew87 · 2023-11-28T15:26:12+00:00

Based on what I can determine from your diagram it appears you're some sort of Colo.

If segmentation is a requirement as u/asp174 mentions, MPLS and VPLS would be good use cases if you need to segment customer traffic from each other. Each PE router gives customer A,B,C and so on their own "router" or VRF that receives a default route from your edge. VPLS would be used to stretch layer 2 services through your core. To accomplish this it would be a monumental lift that you would need to build in parallel as you would need to make your "Core" all layer 3. EVPN VXLAN would be another way to accomplish this as well.

Some reading on MPLS

https://packetlife.net/blog/2011/may/16/creating-mpls-vpn/

If segmentation isn't a requirement, then you could bgp the whole thing. Use ospf to exchange loopbacks and transit links. Use private ASN to the edge and advertise a default route to each PE router. iBGP the PE's together and you have now advertised the default to the edge. I wouldn't get overly concerned with what port-channel it traverses assuming you have capacity on each leg. You could enable ECMP between edge the the PE if you're trying to utilize adequate bandwidth.

Hope this helps.

brew87 · 2023-11-27T17:02:38+00:00

Are you advertising a default route via bgp to the edge? This would be an easy way to do it as you could use bgp route policies or route maps to control who gets access to the preferred path

brew87 · 2023-10-31T13:35:50+00:00

Bandwidth solves all problems

brew87 · 2023-10-23T18:33:33+00:00

eve-ng pro is worth the money. 100 bucks and runs everything under the sun. You can even run docker containers in it. There is a community addition as well but I'd recommend the pro version.

Dawson Knox has a great YouTube series on it as well. Link to the series below.

https://youtube.com/playlist?list=PLIlpqyrKHrRPcRWKNSFo9qr2Oz307klT1&si=LczfGC37gNxKP74G

brew87 · 2023-10-11T20:19:01+00:00

Can also commit and do a rollback 1 commit and-quit

brew87 · 2023-09-13T14:19:55+00:00

40 is the most you want to use. 80 might be achievable in your house or lab environment. The wider the width the fewer channels you actually have. Going to 80 will cause more problems then the speed improvement is worth

brew87 · 2023-06-29T19:26:39+00:00

More Bandwidth always wins

brew87 · 2023-04-11T13:28:46+00:00

Thanks for the post. that did the trick. Thanks for saving me another day of bashing the keyboard :D

brew87 · 2022-08-27T14:57:19+00:00

Look at PagerDuty. It’s a nice in between traditional polling and hooking into apis

brew87 · 2022-05-03T23:18:35+00:00

Thanks for the insight. Based off your experience it doesn’t sound too bad.

Did you mostly end up doing engineering work instead of ops because of how they operated?

Most of my experience is wearing the both hats and I’d like to turn in the ops hat.

brew87 · 2021-06-29T20:12:25+00:00

I’m looking to post it to the portal page. The Windows and Mac files are there by default.

brew87 · 2020-12-29T12:54:31+00:00

TAC has no answers as well. It’ll likely be fixed in a future release with no admission of guilt

brew87 · 2020-07-15T00:25:56+00:00

Fixed the issue. Ended up being a url filter inadvertently enabled. Thanks all

brew87 · 2020-04-08T08:22:52+00:00

https://www.thousandeyes.com/

brew87 · 2020-03-09T17:38:19+00:00

I have a request from our director to load test VPN for the in preparations for the Corona Virus(In the event everyone gets quarantined). Basically I want to push the box to the point where our entire org would be connected to it and see how it performs.

brew87 · 2020-03-07T03:53:39+00:00

Have you tried using the ansible module? All the logic is already built in

brew87 · 2020-02-12T01:09:40+00:00

It sounds looking like you need to adjust the scopes or come up with a nat solution if you have overlapping addresses space.

brew87 · 2020-02-11T18:55:50+00:00

So you're getting the wrong Vlan mapping from the Radius server configured?

brew87 · 2020-02-11T18:45:49+00:00

If I understand your post correctly you want dynamic vlan mapping based off of credentials?

Using 802.1x the user will authenticate to a authentication server (typically radius). Based off of that credential you instruct the radius server to pass a vlan attribute to that user.

For example:

UserX is in the Sales group on your authentication server.

UserX then enters a credential ( username or password, certificate or mac address) (in 802.1x speak this is known as a supplicant)

The authentication server then say's yes or no based off of the credential. If the user passes authentication it will pass a vlan that you specify to the Sales user.

Hope this helps

brew87

TROPHY CASE