Solved! Go to solution.
Hi MX-2020,
Sounds like you are moving in the right direction.
Here are couple more pointers.
You shouldn’t need to set any specific NAT, the MX will do PAT of the local IP addresses to the respective WAN IP address without any additional configuration.
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?
Not sure which each of your VLANs are enabled for but try creating a third for Meraki Device Management.
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
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
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
Hi @MX-2020 , just to clarify this isn’t the official Meraki support help desk. I’m a user of Meraki eqpt just like yourself but jump in and out of the forum to help others.
Lets focus on getting your switch online.
So VLAN 80 is being used for Management also. What happens if you set the Native vlan on both sides of the Trunk uplink between the MX and MS?
Does the MS get an IP address. What are you using for DNS? Can your DNS server see the internet?
To add further: it'd be very helpful (even for yourself) having the design drawn. It would help us all (including you) better understanding the issue.
@MX-2020 you have both WAN2 and LAN (labelled as management?) both going back to the MS. Why do you have that setup?
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.
It is a little bit complicated 😀, and I can’t see why it should be.
There are a couple of things to consider...
Hope these, along with everyone else’s suggestions may help.
Hi MX-2020,
Sounds like you are moving in the right direction.
Here are couple more pointers.
You shouldn’t need to set any specific NAT, the MX will do PAT of the local IP addresses to the respective WAN IP address without any additional configuration.
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.