After the initial setup of the switch via http://my.meraki.com where I configured IP address, mask, gateway and DNS, this switch then comes online within the dashboard via the configured gateway.
The point now is that we have to route Internet via another gateway, means I have to change the default gateway of this switch, which I can do within the dashboard. When now something happens with this new gateway, I lost the management of the switch.
Is there a way that I can get back to the initial setup page by accessing the switch directly? I still can ping the switch within the local network, but I cannot access this switch by using http://switch-ip. I am thinking to a similar case of the MX appliances, where I can access to this local status page and then login to the MX device and change the network parameters.
The only way we found now is to factory-reset the whole switch again and then start from scratch. But I am pretty sure there is another way to do so.
Solved! Go to Solution.
Did you disable the local status page at the dashboard settings?
This does not work?
MS - 220.127.116.11
In order to access this address, configure a device with the following IP settings, and then browse the address in a web browser.
IP Address: 18.104.22.168
Subnet Mask: 255.255.2555
Thank you for your reply here. You mean that from within the local network, I should be able to access my switch by using http://switch.meraki.com? But this then resolves in the Internet, I don't think I can access it in this way. But I can check that one once the switch is online again (unfortunately only next week, but I then will update the post again here).
The other one you are saying is that the ip address 22.214.171.124 is still active, even if my switch has for example 10.11.12.13? Saying I also then can configure a laptop with for example 126.96.36.199, then I can browse with HTTP to 188.8.131.52 to get the local device page?
Unfortunately I was not able to test this topic, connecting to the management port and get it from there. But I would say to close this threat as solved, getting back to the management port will be the correct answer.