07-01-2022 11:55 AM
Hello,
I have set up my new home WIFI a few months ago and I have some issues I am unable to get hold of... maybe somebody can help, I think there is something missing which I just don't get...
My hardware components:
My idea:
My configuration:
My issue:
Now I am pretty unsure what to do. I do not like my access points assigning IP addresses, because I have had the idea of managing them centrally, at some point maybe being able to have certain rules for my children's devices (assigning static IP's to their devices and blocking them from certain websites, ...). However, if I go back to the previous setting (bridge mode on the access points) I again face the issue that the network will not work for some reason after a power outage... Did anybody experience something similar and can provide help? Any hint is much appreciated!
07-01-2022 01:34 PM
Hello,
chances are that stopping and restarting the DHCP service on the switch when the switch comes back up resolves the issue.
Configure the EEM script below:
event manager applet DHCP_SERVICE
event timer cron cron-entry "@reboot"
action 1.0 cli command "enable"
action 2.0 cli command "conf t"
action 3.0 cli command "no service dhcp"
action 4.0 cli command "service dhcp"
acyion 5.0 cli command "end"
07-02-2022 11:35 AM
Hi Georg,
many thanks for your suggestion. I just wanted to try it out, but was wondering - you thought I should execute the script in the CLI of the switch? Because I have only used the GUI so far, but I guess there is no way to make the settings via GUI, right?
Thanks,
chrisse
07-02-2022 12:25 PM
Hello,
very good question actually. I don't think the GUI lets you do that. The CLI is fairly easy once you get used to it.
07-03-2022 01:38 PM
Hi Georg,
no problem, I am going to try the solution you have stated anyway. Maybe it is able to solve the issues we have.
One more thing which strikes me: I just did some setup of a new device and the network was not having a power outage today. I have previously operated the relevant WIFI network it in NAT mode, then I have switched to "bridge" mode just before connecting the device I have set up. After 3-4 tries the device was still not able to get an IP address (in bridge mode). After switching back to NAT mode, it worked within 30 seconds and I had an IP address.
This appears a bit odd to me, since I guess your approach would only fix an issue connected to restarts of the switch, right? Somehow it appears as if IP addresses are just not (always?) handed out to my devices...
07-03-2022 11:37 PM
Hello,
what AP do you have ? And what 'device' are we talking about ? Do you have a schematic drawing of your topology that shows how the AP, switch, and (I assume) ISP modem/router are connected ?
07-04-2022 12:49 PM - edited 07-04-2022 12:58 PM
Hi Georg,
of course - here is a schematic drawing:
[image: image.png]
The IP Address pool on my Cisco switch is configured to assign IP's from
192.168.1.1 to 192.168.1.49 (lease is infinite, but as I have said, I am
not running out of ip addresses and I have already tried to set a time
limit to that). Network mask is 255.255.255.0 and DNS and Standard Gateway
192.168.1.1.
All lines are standard LAN cables, just the ISP Modem is connected to the
internet via LTE. The device I was trying to connect to the internet was a
Lenovo Tablet. However, I have the same issue (hardly not getting an IP
address) on my wife's Samsung mobile phone as well plus sometimes on our
Amazon Echo devices.
The access point I have is 2x the same Cisco Meraki Go GR10.
Thanks!
PS: Maybe I should note that I have absolutely no problem in getting an IPv6 address, or whatever reason. I have not set it up explicitly on the DHCP server. However, I always get an IPv6, but as I have said the IPv4 address is missing.
07-04-2022 09:32 PM
I have just done some more tests after a power outage today. It appears as if it really is related to the DHCP server. When I just go to "Edit" mode of my address pool and hit "apply" (without changing anything) things seem to start working again normally.
Georg, does the script you have provided only restart DHCP in case of explicit (user-triggered) reboots? Or at any reboot?
Thanks!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide