Network Diagram            I think that I'm missing is a failover route at the backup site to redirect Internet traffic to the MX at the MX site or the configuration between Meraki MX or Meraki Switch.   I just add the 10.82.0.0**/16 route to** 10.10.80.1 on MX. Basically it is Wan 2 through Meraki switch Port 23 to ME router to Backup Link.     Backup side   Now on backup side Switch only default route 0.0.0.0 0.0.0.0 10.82.1.X (to Firewall), both ME router (Metro E) use BVI to connect each other. We use switch through Metro E Router connect to Meraki Side when I unplug the internet link from backup side firewall. Then we are not able to ping 8.8.8.8 / 8.8.4.4 and do not have internet access from Meraki side, but able to ping or go to Meraki side MX and MX management side, Switch IP and able to RDP to Meraki side server only. Will that help us to grant internet access (Wan 1), if I set on Flow preferences Internet traffic as Any 10.82.0.0/16 Any 210.x.x.0/29 any Wan 1 ?   I tried to set this setting before. It still not getting internet in backup site from Meraki site.  I think that I may miss the configuration between Meraki MX or Meraki Switch. What do you have any suggestion on that?   ... View more

Hi Bruce,     1. MS one default route     Default route 0.0.0.0/0 10.10.80.50    old firewall setting Management IP of 10.10.80.50     MX is the new replacement.    And I would like to set the MX to be 10.10.80.50. I have to figure it out how to set MX to have own IP address because MX is not normally like a other simple router have owned management IP. I think MS cannot define how to route to MS for this route 0.0.0.0/0 10.10.80.50      2. We disabled the load balancing mode.  Wan 1 : ISP 1 and WAN 2: ME route on port 21 (Access Vlan 99)     MX Port 3   Module Port Enabled Type VLAN Allowed VLANs  Built-in 3  Trunk Native: VLAN 80 (Server_Vlan)   Allow all Vlans     MS switch Port 19 Native VLAN 80 to connect MX port 3 both trunk native vlan 80 allowed all VLANs (80 and 88)    MX  ID                                                      80  Server_Vlan 10.10.80.0/24 10.10.80.1     MS routing as  ME_VLAN 10.10.99.X/29 10.10.99.X Vlan 99   It is through MS port 23 to go to ME router to second WAN 2 (backup link).      MX 10.10.80.50 (if I able to do on DHCP server set as fixed IP for MX relay on Window server on MS ) MS 10.10.80.10.       Wan   MX--> Wan1: ISP1 (Primary)              Wan2: ISP2 ME Link (backup link)       Network diagram   MX --> MS  --> MR       DHCP   MX --> MS( dhcp relay on window server) --> MR       Management   MX (dhcp server relay on window server through MS set as fix assignment Ip for MX)       3. MRs used bridge mode and assign a VLAN tag to all traffic from the SSID.       Now I think only issue which is between MX and MS.       Other than that, Local network MX and MS for internet access, do we need to set the NAT 1:1 or 1: many?        ... View more

Hi cmr,   MX   Wan 2 is not the management.    uplink Wan 2 --> MS --> ME Router                              Lan port (MX management) --> MS --> MR   Lan Port is the management.   Mainly MS switch is used for main routing and relay from other DHCP server and it's default route through MX to go internet. Other than that, it also set the route with Lan port to connect to ME router through backup Wan which bridge to our other site for remote server and network devices.   It is a little bit complicated.     ... View more

Hi UCcert,   Thanks for the advise.   Yes, Vlan 80 used for management too, I only able to set this setting on Meraki first and I will see what happen this weekend because I fall back to use the temporality setting on MS switch via other router connected to backup Wan 2 now. The MS switch is 10.10.80.10 static IP.   Router Management IP: 10.10.80.50 Opened NAT Routing: Vlan 80  10.10.80.0/24  10.10.80.1    I set it before. The MS switch got the different 10.10.80.16 via DHCP server and MR are all disconnected. it is using the ISP DNS. outbound the DNS are pingable. ... View more

 Hi CptnCrnch,   I have an Network design. Please have a look and discuss what you think?     MX-2020 ... View more

Hi,   1. Yes, MS Switch and MRs aren't go to internet from MX.      Hi @MX-2020 , so what you’re saying is that your MXs are registered but your Switches and MRs aren’t getting out to the cloud?   2. Vlan 88 Access point and User data     Vlan 80 Server, Printer UPS and Management     Vlan 99 Trunk Link, and ME router (Metro E connect to other Site and backup link)   Not sure which each of your VLANs are enabled for but try creating a third for Meraki Device Management.   Vlan 99 10.10.99.0/24  10.10.99.1   Before our Old firewall abled to set management IP as 10.10.80.50 and Lan port to connect to MS switch.     3. Before I set MS Port 19 as native 80 to connect to MX port 3                         MS Port 21 as Vlan 99 Trunk connect to MX Uplink Wan 2.     4. OK we have already set on it on port 21 from MS   99 10.10.99.0/24  10.10.99.1   The uplink from the MS to your MX set this as a Trunk with Native VLAN 99   5. The MS switch has relayed to other Window server (10.10.80.20) for DHCP.     Will it cause the duplicate IP if I enable DHCP on MX or MS on .99 range?   On your MS set the management IP to something in the .99 range or just enable DHCP on the MX and let that set the IP   MX-2020 ... View more