About MRCUR

MRCUR · ‎10-16-2018

Is your MX meant to be your 3750's default gateway at 192.168.76.254 or is this another device?

MRCUR · ‎10-12-2018

Unfortunately @MacuserJim is correct. The timeout is a global org setting so the users will need to keep the session active. If you have video walls set up, you could use the new auto rotate walls option to have the page auto refresh and move between walls. This should keep the session alive although I have not tested it since the feature just launched (hopefully it's available for everyone!).

MRCUR · ‎10-12-2018

This isn't supported today for certs or credentials on the MV. You could use MAC based auth as a workaround.

MRCUR · ‎10-11-2018

Dashboard notifications are not immediate. I'd say roughly 1-2 minutes sounds about right.

MRCUR · ‎10-11-2018

If your core Cisco switch has a default route pointing at the ASA's "inside" (LAN) IP, then you can replicate that on the MX using the "use a single LAN" option. You would create a "Local LAN" that matches the ASA's inside IP and then create static routes for all of your internal subnets and put the Cisco switch IP as the next hop.

MRCUR · ‎10-11-2018

You will not see the custom DNS servers you set on the client. The client will always see the AP as its DNS server. See this note from the article you linked to: Note: Wireless clients will still use the AP as their DNS server, this configuration customizes the destination server of the AP's DNS proxy.

MRCUR · ‎10-04-2018

That certainly looks like a valid URL since it's going to aaplimg.com. I do suspect that blocking it would break other Apple services however.

MRCUR · ‎10-04-2018

This should work fine. I have my Z3 behind a Ubiquiti USG and previously had it behind an MX64.

MRCUR · ‎10-03-2018

In addition to what @PhilipDAth, you cannot have a dual master setup with the MX line. Warm Spare is just that - a method of having a warm spare device ready to failover very quickly if necessary. A dual master with the MX line is a split brain scenario which is unsupported and undesirable.

MRCUR · ‎10-02-2018

@jdsilva wrote: Try swapping the fibres around. To clarify what @jdsilva is saying - you have two fiber strands, flip them (on the fiber patch panel likely) so they're opposite what they are now. It's likely that you have TX going to TX and RX going to RX right now instead of TX to RX.

MRCUR · ‎10-02-2018

@PhilipDAth wrote: vMX is not free. You need to buy a licence from Cisco Meraki to use it (like all other Cisco Meraki kit). You also need to pay Microsoft Azure for the virtual machine charges and data traffic. Philip is right. The only thing "free" about the vMX is the VM image itself.

MRCUR · ‎09-26-2018

I would recommend removing the config and moving to a supported setup. I've created a VLAN for the L3 MS devices on the upstream switch they connect to which provides the switches with Internet access. I then make this a tagged VLAN on the MS uplink port and set the VLAN as the management VLAN for the device in Dashboard.

MRCUR · ‎09-26-2018

My understanding on this after speaking to multiple engineers is that the setup you are using is not supported. I originally wanted to setup my L3 MS switches this way and was advised not to because of this.

MRCUR · ‎09-24-2018

It sounds like you're looking for a specific answer here. I suggest you open a case with Support.

MRCUR · ‎09-22-2018

When looking at the timeline, do you see a green bar along the top (this indicates footage is available)? Make sure the timeline is zoomed out enough so that your motion event is within the timeframe that's shown on the timeline. Also try doing a search of the whole view (activate motion search and then click outside of the frame - this selects the entire area for searching).

MRCUR · ‎09-21-2018

Have you actually created a stack in Dashboard? Did you set the ports you're using to run as stacking ports?

MRCUR · ‎09-21-2018

Apple defines what the restriction payloads can do, not Meraki. You should submit this feedback to Apple directly.

MRCUR · ‎09-21-2018

I don't think so. The delay date is set based off of "release date" which is 9/17/18.

MRCUR · ‎09-19-2018

@cta102 The AP's don't tag their management traffic if the VLAN box is left blank on the AP LAN IP config (MS switches do from what I've seen).

MRCUR · ‎09-19-2018

You might be able to get away with setting the "All other AP's" to VLAN 1 or 0. Give it a try in a test network.

MRCUR · ‎09-17-2018

This is not possible with the MX as the redundancy (warm spare) is an active-passive design. All traffic is handled by the active MX unless there is a failover event and then all traffic is handled by the second MX until the primary MX comes back online.

MRCUR · ‎09-14-2018

I don't think @GeorgeB is a huge PTZ fan. They're expensive, there are lots of components that can fail and they don't give you constant coverage of a given area. We've found that it's been easier to simply add additional cameras to cover a whole area (the MV12W provides a very wide angle view) than what was previously being done with PTZ's. This isn't to say Meraki won't eventually release something to compete with a PTZ, but for now it's a non-issue for us.

MRCUR · ‎09-13-2018

@PhilipDAth It's just the URL of an individual camera page that you can see today.

MRCUR · ‎09-13-2018

@PhilipDAth I think that feature is enabled even for cloud proxy streams now. There is a high & low version of those streams on MV12's and works pretty nicely. @BlakeRichardson I don't have any issues reviewing footage off network. It's a bit slow at times to do the cloud streaming, but once it's going it's totally fine.

MRCUR · ‎09-12-2018

This is awesome! Thanks for the update @GeorgeB.

MRCUR

Community Record

Badges