Meraki

MRCUR · ‎Dec 27 2017

@MRCUR wrote: For those who have deployed the vMX in Azure, is the "Historical data" working for you on the Uplink page? I have the default destination of 8.8.8.8 configured on the Traffic Shaping page along with an additional IP. I can see the traffic through a pcap, but am not seeing anything reflected in Dashboard. This is corrected in firmware 14.19.

MRCUR · ‎Dec 26 2017

@PhilipDAth wrote: And there is no need to run OSPF on the MS250, unless you also want to make that a part of your layer 3 design (which is probably not needed). Agreed on the OSPF. There is not really a need to run it here, although the original network diagram included it. It is very simple to run OSPF between Meraki devices, but it's not needed and the MS425's can certainly handle the routing.

MRCUR · ‎Dec 26 2017

Do you have VLAN's 101 & 102 allowed on your uplink from the 250's to the 425's? All of the inter-VLAN routing should be happing on the 425's right now.

MRCUR · ‎Dec 19 2017

As @VascoFCosta said, you should create a network per physical location. Since you don't want the same config in each location, you can then manually configure the SSID and settings for each network. If you do in the future want to unify the configuration, you can use a template and bind it to all the networks and then the config will be uniform across the sites. This is probably the most common deployment type since typically people are looking to unify management across sites.

MRCUR · ‎Dec 18 2017

I think to accomplish what you're looking for you'd need to have the MX do all your L3 routing, but even then I'm not sure any of the IDS rules are applied to traffic that isn't WAN to LAN.

MRCUR · ‎Dec 18 2017

The Adv Sec license is worth 1/2 of an Enterprise license. You can buy a new Adv Sec license and apply it to the org which will convert the org to Adv Sec.

MRCUR · ‎Dec 18 2017

The devices need to be removed from whatever network they are in within Dashboard and then unclaimed from the Organization -> Inventory page. Once that is done, you can claim them in your new org. I believe if your previous IT help contacts Meraki support, the licenses can be transferred but I'm not 100% on this. Maybe @MerakiDave knows for sure.

MRCUR · ‎Dec 18 2017

I'll second what @MerakiDave said re: WEP. You can't use WEP (there is zero reason to be using it anymore) with modern wireless data rates.

MRCUR · ‎Dec 18 2017

The MX line does not support IPv6 currently.

MRCUR · ‎Dec 15 2017

For those who have deployed the vMX in Azure, is the "Historical data" working for you on the Uplink page? I have the default destination of 8.8.8.8 configured on the Traffic Shaping page along with an additional IP. I can see the traffic through a pcap, but am not seeing anything reflected in Dashboard.

MRCUR · ‎Dec 14 2017

@BHC_RESORTS Color coded patch cables is the only way to keep things straight without always having to refer to documentation IMO. Also hugely helpful when you have a tech that isn't familiar with networking in a closet and need them to find the right thing for you.

MRCUR · ‎Dec 14 2017

I'll also add that I did an MS webinar over a week ago. Never heard from the assigned rep (not you, @MerakiDave!) and he hasn't responded to emails about the free switch.

MRCUR · ‎Dec 14 2017

Absolutely get onto 9.32 ASAP. It fixes a lot of weird stuff like you're seeing. Just note there is an ongoing issue with the 9.X firmware series. You need to reboot switches BEFORE starting the upgrade, otherwise they may not come back from the upgrade without manual intervention.

MRCUR · ‎Dec 14 2017

I've deployed a stack of MS350's running 1Gb iSCSI with EqualLogic devices without any problems. Has worked very well serving the EQL's and the ESXi hosts.

MRCUR · ‎Dec 14 2017

The post says they will continue to use Dashboard banners and email alerts as well. This is not the sole place alerts will be shown.

MRCUR · ‎Dec 14 2017

Make sure that the MX has a route to the network you're trying to access. And make sure that upstream devices have routes back to your VPN subnet. Not seeing a gateway is normal for client VPN.

MRCUR · ‎Dec 13 2017

@Speightz You definitely can't change the public IP to be static because of the lock. But as long as you don't de-provision the vMX, the IP won't ever change so it shouldn't be an issue to set up the S2S VPN's.

MRCUR · ‎Dec 12 2017

@jared_f wrote: VPP is mandatory to have silent app installs. If you are setting VPP up I recomend you do user based licenses because they are easier to track and manage (in my opinion). Jared I find the exact opposite. Device based licensing makes everything so much easier. Deploying devices without having to bother with getting an Apple ID onto them is great.

MRCUR · ‎Dec 11 2017

Yes, you can do this with device based app licensing. This will allow you to silently install the app. You should "purchase" licenses for the SM app in the VPP store and then deploy it to devices making sure to select the device assigned licenses.

MRCUR · ‎Dec 11 2017

NAT rules are bidirectional - otherwise there wouldn't be a valid return path. I haven't tried this specific setup with 1:Many NAT, but I don't see why it wouldn't work.

MRCUR · ‎Dec 11 2017

The MX250 and MX450 are the latest MX models. The MX400 (and MX600) are the previous generation models. Don't worry about the numbering - it'll all be aligned again in the future. Between the 250 and the 450, the 250 is the "lower end" model.

MRCUR · ‎Dec 11 2017

No, you need to supply a public IP that the MX has configured on its WAN interface subnet. Then in the LAN IP, you can put your internal network that you want to use the configured public IP for SMTP traffic.

MRCUR · ‎Dec 11 2017

@Paulofg wrote: To get a whole subnet to use a different outbound IP you will only be able to do that if the IP belongs to the WAN interface and as someone mentioned above you could achieve that with another L3 device connected to WAN2. You don't have to connect it to WAN2 in the setup I suggested to be clear.

MRCUR · ‎Dec 10 2017

@BHC_RESORTS wrote: @LindseyM wrote: Personally I don't think retention is a big issue. The camera's can average 90-120 days, how often do you need to go back farther than that? Even with standard quality, I'm a little dubious about that amount of footage in real world scenarios. Perhaps with standard quality and motion retention enabled, but I also agree. I'm only seeing that kind of retention on cameras in server rooms with little to no movement.

MRCUR · ‎Dec 10 2017

Do you have a /30 from the ISP AND another block of IP's that the ISP is routing to the /30 (Comcast does this for example)? In that case, what I've done in the past is terminate the /30 on a L3 switch that sits in front of the MX. Then on the switch, create a VLAN with the public IP block and connect the MX WAN port to this VLAN.

About MRCUR

MRCUR

Community Record

Badges