The clients are wireless and I want to filter the clients by their MAC. But I don't have installed a MX device, only have a switch and I only can configure a Deny Rule in Wireless -> Firewall&Traffic Shaping to apply a group policy but I'm not sure if it is going to work.   Thanks! ... View more

I agree.  Let's make sure to give this feedback to Meraki. ... View more

Hi. We are having an issue connecting a new Meraki MS390 to 2 production Nexus 7000 switches using vPC.  The Nexus 7K switches have been confirmed to be configured correctly by a Cisco employee & we have multiple working vPCs on them already.  The Meraki switch is not sending any LACP packets to the Nexus switches despite documentation saying it should.  How do you enable LACP on the MS390s? ... View more

I think there has been already a link to the meraki documentation site exited, in which it was recommended to use the LAN interfaces (for the time being) for native MPLS! Maybe someone does have this link and can provide it? I`d like to ask also a question regarding the use of the LAN Interface vs. the WAN NO NAT/NAT Exemption feature in BETA... Is my understanding correct that - when I use a LAN Interface for routing traffic to a MPLS Router no statistics e.g. shows up on the appliance dashboard? If so, is this possible when using the NO NAT on a WAN-Interface? Probably someone can also point out the differences/advantages when using NO NAT on a WAN-Interface... for example: content filtering, etc. may also work with it?     ... View more

so just to recap:   I create a new wireless network with PSK authentication. Map it to a VLAN/subnet on the network, and make sure it can communicate via layer3 to the existing corporate wireless.   then go into the policy on both wireless networks, enable bonjour forwarding, and specify that new printer VLAN?   ... View more

I haven't tried that, but I would imagine that if you have Meraki access-points and a MX, the reporting would still work. You just wouldn't get any info about the switches ... View more

If the comparison is "apples with apples", you you use SmartNet and DNA licencing with the same terms as the Meraki licences - the Meraki solution usually works out wayyyyyyyyy cheaper.   I haven't done a WLC for a while now.  I think DNA licencing is compulsory on them now, every if you don't have DNA Centre. ... View more

The concern I'd have here is that you'd end up with two totally different APs;   a 2.4 GHz AP, on one side of the wall and a 5 GHz AP on the other.  If your client mix is OK with this, that's fine. I'm thinking maybe you planned on splitting the pigtails from, say, an MA-ANT-25 across the two radios?   On the face of it, that would give you one antenna for each radio, both inside and outside..?   That really should be avoided;  the recommended dual antenna chains connected to the same radio is what provides multiple spatial streams (for newer clients) and/or antenna diversity [to mitigate multi-path fade] (for older clients).  These rely on both antennas having the same coverage area and the radio assumes that, in its operation.  This is mentioned in the antenna installation guide. ... View more

agreed --however, it was a requirement of the client. I couldn't change it ... View more

Ok, got it. Thanks for the reply MRCUR. ... View more

@Silas1066 wrote: I ultimately opened a case with Meraki   looks like the upstream Comcast router is causing the issue --not passing the traffic correctly to the security appliance I didn't even think to suggest that.  All of our sites have static ip's, so they have to have the isp equipment running in bridge mode.   We have seen from time to time carriers will route UDP traffic differently than tcp - even though they claim that they don't.  We use 7 or so ISP's nationwide, so we see a lot. ... View more

@Silas1066 wrote:     So I created VLAN 101 and assigned the uplink to 192.168.101.10 /24 I then created a SVI interface 101 on the switch with an address of 192.168.101.4 , with a default gateway of 192.168.101.2 (the MX)   A little counter-intuitive,   . . . It is counter intuitive, but not for the reason you gave. 101 is reserved in many networks for a good reason. Think about it, hint, Big Brother is watching . . . ... View more

that worked, thanks! ... View more

thanks for your help   that removing from spare status would have really thrown me   it is all good now 🙂 ... View more

That wasn't it remember that this switch had been added to the network weeks before as a stand-alone and was running the same firmware revision as the others. ... View more

Does the order email list an MX84-HW?  If it doesn't appear in your inventory then that suggests it was not added correctly. ... View more

The uplink port, if trunked, has to match the native Vlan of the trunk port on the other end. However, like I said previously, Meraki terminology is just plain wrong between what it calls Uplink and management or LAN IP. It is a little confusing the way they interchange the terms. One thing I can specifically tell you is that if you have an open port on the Meraki, duplicate your trunk information on it and put it in an inactive state. Then, anytime you need to make changes to the Uplink trunk you will have a backup in case things go awry. If the Meraki loses the ability to reach the cloud, there's really very limited things you can do to fix it via the local interface. ... View more