Changing from Vlan to single LAN

[Kenneth2]

Hi,

I have a network defined as 10.10.10.0/24 and have previously had multiple Vlan's. But now I want to set the LAN settings to Single LAN as the former Vlans is not being used and is deleted.

But when i click on the Single LAN it changes the network to 192.168.1.0/24. 

If I then change the network back to 10.10.10.0/24 and click apply, it comes up with this error:

• The fixed IP address 192.168.1.53 is not in the subnet 10.10.10.1/24.
• The fixed IP address 192.168.1.200 is not in the subnet 10.10.10.1/24.
• The fixed IP address 192.168.1.236 is not in the subnet 10.10.10.1/24.
• The fixed IP address 192.168.1.235 is not in the subnet 10.10.10.1/24.
• The fixed IP address 192.168.1.234 is not in the subnet 10.10.10.1/24.
• The fixed IP address 192.168.1.17 is not in the subnet 10.10.10.1/24.
• The fixed IP address 192.168.1.199 is not in the subnet 10.10.10.1/24.
• The fixed IP address 192.168.1.70 is not in the subnet 10.10.10.1/24.
• The first IP address 192.168.1.174 is not in the subnet 10.10.10.1/24.
• The last IP address 192.168.1.254 is not in the subnet 10.10.10.1/24.

Why is it locked on that network and why can't I change it to Single LAN?

I have other sites that uses the Single LAN and is not on a 192.168.1.0 network.

I can't find any device or setting that shows the 192.168.1.0 network...

[ww]

Looks like its keeping the previous multi vlan settings in the dashboard/backend.

Could you try enable multiple vlan and remove those vlans/static routes first.

[Kenneth2]

I've tried to add a Vlan with a network 192.168.1.0 but I can't find any routes or anything else like DHCP reservations...

[Ryan_Miles]

Sounds like there are fixed IPs configured on the DHCP scope. Remove those first.

[Kenneth2]

There is no DHCP configured for the network on the Meraki.. 😞

[Ryan_Miles · Accepted solution]

Hmm, well perhaps open a Support ticket. They'll be able to see your config and offer better assistance. 

[Mloraditch]

Any single MX config that could have those ips would possibly cause that error, that includes DHCP, Traffic Shaping, Firewall Rules

[PhilipDAth]

The fixed IPs can be referenced in many places.  Off the top of my head:

• DHCP reservations
• NAT translations
• Firewall Rules
• VPN firewall rules
• Potentially client VPN configuration