Meraki

jdsilva · ‎Apr 22 2020

Welcome! Always good to see more fellow Canadians here!

jdsilva · ‎Apr 17 2020

Hey @Roberto4. Welcome to the community!

jdsilva · ‎Apr 17 2020

I think you should space them a little further apart to get better coverage. Maybe mount them on the ceiling too? Otherwise, looking good! 😉

jdsilva · ‎Apr 8 2020

I'm wondering if there's some confusion around the fields here? Name is just a textual description of the static route. A comment or a remark, if you will. Subnet is the destination you are trying to match in CIDR notation. Gateway IP is the next hip IP address you want to forward traffic to. Are you by chance meaning something like this:

jdsilva · ‎Apr 8 2020

255.255.255.255/32 doesn't match 155.231.231.1.

jdsilva · ‎Apr 8 2020

Is that the actual static route you are using? That doesn't make any sense, and it certainly doesn't match what you are trying to ping. What exactly are you trying to do here?

jdsilva · ‎Apr 7 2020

@GIdenJoe wrote: For HA MX'es don't forget your WAN1 and WAN2 on both appliances need to connect to the same respective upstream ISP circuits. So you'll need to have one ISP come in building 1 and connect that one first on the switch there on an external VLAN and then have two ports connecting to both the WAN1's of the MX'es, so the third link will also be going over the fiberlink. And then the reverse of ISP2. That one will connect first to switch 2 and then back up to the MX'es WAN2. Only if you need to use a VIP. You don't need to do this if you just use the MX IP's.

jdsilva · ‎Apr 7 2020

Yes, you can do this. Just make sure the MX's have a L2 connection between them and this will work. And I'm sure you've got this covered, but if you're doing SX then make sure you have OM3/4 for your fibre run. SX on OM1/2 doesn't support that distance.

jdsilva · ‎Apr 6 2020

OMG, a non-all star cracked the top four! Damn fine work there @DarrenOC !

jdsilva · ‎Apr 3 2020

Woohoo! My example was meant as pseudocode since I didn't have any idea what a null character would be in whatever language that actually is 🙂

jdsilva · ‎Apr 3 2020

I've not used the code you're referring to before, and honestly I only really know a bit of python, but it seems to me that if you were to blank out the secret before you do anything else with the data tat should do the trick? @Mikanator wrote: // Check secret and store event const SECRET = "xxx123"; if(body.sharedSecret == SECRET){ body.sharedSecret = <NULL> <----- Blank secret from data PD.emitCEFEvents([cef_event]); }

jdsilva · ‎Apr 3 2020

SImply put, your only option is PoE. The MV72 does not have any other power input other than power supplied via the Ethernet port. That said, how you get PoE to the camera is up to you. You can use PoE supplied directly off a switch, or you can insert a PoE injector into the mix, and that injector can be powered by any number of methods depending on the model of injector you use.

jdsilva · ‎Apr 1 2020

Hey @SobyKuruvilla , Unfortunately, you can neither convert a RJ45 port to be used for the WAN, or set up a port-channel as the MX does not support LACP. Your only option to get 2Gbps is to use an SFP+ module 😞

jdsilva · ‎Mar 31 2020

Give this a go: https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair

jdsilva · ‎Mar 24 2020

Gotta get me some of those socks!

jdsilva · ‎Mar 24 2020

Hey @Herixon. I would guess that it is related to that link. What I would think is happening is that the STP BPDU's are getting lost in transit on that link, so SW2 is actually transitioning to root because it stops hearing BPDU's from SW1. When SW2's port is designated it thinks it is the root. When its port is root then it agrees that SW1 is the root. If there's no other devices between those two switches then I would certainly look at the components of that link. SFP's, patch cables, the fibre run itself... If you have a tester that's a good place to start, Swapping the modules (one at a time to isolate one as the problem if it is) is another good option.

jdsilva · ‎Mar 20 2020

Oh! I just realized, you can match the returned users' IPv4 address against your client VPN address range! That'll tell you for sure if they're local or remote.

jdsilva · ‎Mar 20 2020

@Paul_Jefferies , The closest thing I see is this: https://api.meraki.com/api_docs/v0#list-the-clients-that-have-used-this-network-in-the-timespan But when I just tried pulling the data from there it would seem that there's no specific field that identifies the client as a VPN client, even though this same data in the Dashboard does show a VPN icon beside the user... So that's lame. You might still be able to use this endpoint if you're not doing any other authentication on your network. If you're not, then the "user" field will always be blank for non-VPN users, and VPN users will have the user field populated. If you can use that to get all the VPN users then you can hit this endpoint: https://api.meraki.com/api_docs/v0#return-the-clients-daily-usage-history to get usage data.

jdsilva · ‎Mar 19 2020

@LasseBang is correct. There's no way to do what you're asking with a Non-Meraki VPN.

jdsilva · ‎Mar 19 2020

Hey there! Welcome to the community!

jdsilva · ‎Mar 2 2020

Congrats to @damienleick ! I'd say honourable mention to both @cmr and @CptnCrnch this month too. Both were super active this month with very helpful and informative posts! And of course good job to all you other usual suspect 🙂

jdsilva · ‎Feb 27 2020

Yes, you can use a 1Gbps SFP module in an SFP+ port. By definition SFP+ ports are 1/10Gbps and either will work.

jdsilva · ‎Feb 27 2020

Welcome!

jdsilva · ‎Feb 26 2020

Hey @Dennis_S, You can add clients before they are seen on the network, and apply a blocked policy at that time. Under Network wide > Clients just hit the "Add client" button:

jdsilva · ‎Feb 25 2020

Hello @seniorcit , welcome!

About jdsilva

jdsilva

Community Record

Badges