Hi Darren, After a brief overview regarding our use cases, we will deploy MX105 in Routed mode. In the very close future we will not have any Edge devices - just ISP router and C3850 as L3. All the subnets from C3850 should be migrated to MX105 (planned downtime) leaving C3850 only as a L2 switch terminating access switches. MX105 will act as a Hub, while remote branches as a Spokes. In this case we can achieve IoT and Guest networks setup and FW rules on MX105. In case of passthrough mode packets are not translated and we will have no other edge device than ISP not-managed router, if we connect MX105 to the LAN side behind C3850 it will just forward traffic from DC server --> C3850 --> ISP router. This is not the best design. C3850 should do its job switching packets, MX105 should do its job routing packets. Between C3850 and MX105 i see just routed port /30 with C3850 having 0.0.0.0 route towards MX105. Also we need to statically NAT two servers (cannot do this on C3850) plus our ISP is giving us public IP which we are unable to NAT without NAT-capable appliance.. I hope it does make sense to you. ... View more

A huge effort all around!   Congratulations to all the winners. And a big congratulations to @AnthonyCho  ... View more

Check the Meraki event logs to see if there is a reason logged for the port going down. Other than that, as said above, open a support case to assist you with the troubleshooting. ... View more

Ran into this last week and was a bit frustrated by the change. I have one org that's PDL and the subscription management process, with each device being on its own term, is preferable.    Have another customer that's basically "15 businesses in a trenchcoat" who would have benefited greatly from being PDL and had their renewal coming up, so I went to convert them, only to discover that the option no longer existed.    Some of their licenses are less than 6 months old (MR) and they balked at the price of renewing the entire org and the idea that they had to, given that some of the licenses were purchased quite recently. The argument was that they should only have to renew the devices with expiring licenses, which were for specific sub companies, and these could be billed as such (to each sub company), which I really couldn't argue with. I'd have converted them to PDR earlier if I had known it was going away, but apparently I missed this memo, which is my fault.  ... View more

Wow! That's fantastic. Thanks for letting me know. ... View more

@Gomugomuno the dashboard certainly thinks that you have 202 devices registered, if you go to the Systems Manager page, do you see your devices and are they showing recent activity?   In terms of affecting the access points, I think you would be fine as normally any issue would set the whole organisation status to warning with less than 30 days left and yours is still OK/Green.  I would however log a ticket with support to be 100% sure. ... View more

I guess you should also consider that VRRP is optional.  A minimum of 2 IP addresses is mandatory (one of each MX).  Also of note is that if you don't use VRRP that the IP addresses don't have to be from the same ISP circuit. You could use the primary circuit on the primary MX, and a cheap consumer grade Internet circuit for the secondary MX.     ps. I only enable VRRP on about 25% of the installs tat I do. ... View more

As requested:  Here are some beginner tips (especially aimed at CLI pro's) to succesfully get an MS switch or Catalyst Meraki managed switch online into dashboard.   Default switchport configuration: On a factory default MS switch every port has the following configuration: switchport mode trunk switchport trunk native vlan 1 switchport trunk allowed vlan all All VLANs are created by default so the ports can receive any traffic from any port. On a factory default Catalyst switch that has been placed into Meraki management mode the ports have the same configuration but since the TCAM space is configured differently all VLANs cannot be created.  So all ports get VLANs 1-995.  This part is important if you like to have your management VLAN above 995. When you connect your brand new or factory defaulted switch to an upstream device keep this default configuration in mind so you can manipulate the downstream port on your existing device to easily get the switch online.  You don't even have to worry about a temporary native VLAN mismatch.  The tip I usually give here is to set the desired switch management VLAN as native on the downstream port on the existing device. It is recommended to have your switch configuration already in place in dashboard before even connecting the new switch.  The configuration of the upstream switchport and the management IP are of importance here.  This way the moment the switch grabs it's configuration it will already be in the final state to keep being connected to dashboard. You can set the default switch management VLAN on the Switching -> Switch Settings page. If you like to use fixed IP addresses on your switches then it is also recommended to set this on the individual switch configuration page. And of course reflect the desired config on your uplink port   Even if you will eventually have a fixed IP address on your switch it is highly recommended to have a small DHCP pool in the switch management VLAN where your switch can automatically grab an IP address, connect to dashboard and then move over to it's fixed IP address configured in dashboard. In below screenshot you will see that the largest part of the VLAN is reserved for fixed IP addresses but the DHCP server will assign IP addresses from .201 to .254.   Final tip:  This has more to do with the day-1 and beyond configuration of the switch. On the Switching -> Switchports page you see every individual switchport for the entire network independent of the switch they are on.  This feature is imho the most powerful feature of the switching side in dashboard and has been my personal favorite since first working with dashboard in 2017. At the top you have the ability to adjust visible colums and slide those colums in the order you like. Click on the wrench and make sure you enable the tags column And then make sure you give meaningful tags to each switchport because the you can easily select ports based on their tag.  Tags can also be used for other functions like alerting but in this example the tags are important for selecting and having a consistent configuration over your entire network. In my personal preference I place an ACCESS tag on access ports and a TRUNK tag on trunk ports.  But I also add the VLAN descriptor in case of access ports or a function in case of a trunk port like AP, FW, SRV etc.  You can add multiple tags and each tag can be used for selection. In the search field at the top of the page you can type tag:yourtag and it will then only show the ports with that tag. Note: partial matches also work so avoid using the same letter sequence in another tag.  For example: if you had a tag INTUNE-PC and ADMIN-PC then you could erroneously select both if you type tag:PC. By clicking the checkbox left and above the entire list you select all the switchports visible on the screen at once and you can edit them all at once.  This does not work on multiple pages so you need to go to each page and click the top tickbox again to also select the ports on that page. You can track your selection at the top. I hope this was informative of you and like to that you for reading 🙂 ... View more

Accepted Solution. ... View more

congratulations  all Top shots .. we done @PaulF ... View more

@CloudStrife we decided to leave as-is (orange) since it seems that folks have gotten used to it. ... View more

Hi I totally understand, and I appreciate these SVG very much, they are great and I have been using them in Visio (just kind of convert them manually from images).     Keep up the good work 🙏   Kind regards, Frank ... View more

So sad. I really like the sweater though.  😞 ... View more

I suggest you talk with your preferred Cisco partner - they should be able to provide you quotes specific to your situation. ... View more

I've been replying to the case every so often looking checking for an update, surely the support teams are given the same training on both phone and email, so surely I'd get the same response on the phone, right?   I'd be shocked if a company the size of Cisco has such poor customer service that they "binned" tickets that were too difficult for their engineers. ... View more

I think the maximum power load is with a PoE device attached. Without that, I would calculate with no more than 20W power consumption.   (BTW: I wish these Teleworker devices had an option to be USB-C powered) ... View more

So...   chances are this is not a permitted 'conversion' from a Support perspective.  If you contact the Meraki account team, they may be able to reflect any residual value of the Z1 license in the pricing for the Z4 license. ... View more

Welcome to the Meraki community @JonColes  ... View more

Agree, but cost prohibitive when compared to other solutions on the market. I’ve tried this approach on a number of occasions and the other solutions win time after time. ... View more

Agree with @Mloraditch ‘s method here. Bring the switch on line, pre-stage and then swap out. ... View more

If your voice solution is using regular SIP with regular G711 codec you can even capture and analyse this with wireshark.  You can always perform a packet capture on the LAN side or the WAN side of the MX and then see in the telephony analysis if you are having packet loss or jitter.  You can even playback the audio which is cool. ... View more

I fear we were wrong on this one. ... View more

Yeah, without any issue. ... View more

See if anything gets announced at Cisco Live Melbourne this week! ... View more

Using Umbrella DNS should give you the built in security for the known bad or malicious sites - that constanly gets updated, but you would not be able to add your own without the Umbrella subscription, ... View more