OC300 unavailable after changing IP address
I'm adding a subnet to my system to hold all the network hardware (router, switches, APs, Omada Controller).
When I changed the controller's IP address, I forgot that I have a DHCP reservation for it, and instead, I changed it on the device.
After rebooting, the controller is offline. I get a timeout error when browsing to any of the IP addresses (the old IP address, the new IP address, or the fallback IP address).
I have used the recovery mode to install the same firmware.
Is a factory reset my only option? I don't want to do this as I don't have a recent configuration backup.
Thanks for your assistance!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Vincent-TP after running a scanner on each of the subnets involved, I found that the controller did change its IP address to what I was trying to set it up with.
as far as the OC300 is concerned, everything is working fine.
- Copy Link
- Report Inappropriate Content
Hi @Wayne110,
If you have physical access, you should be able to directly attach a host to the controller to access it. Just manually set the hosts interface to a unique address in the same subnet that the controller is using.
- Copy Link
- Report Inappropriate Content
I should be able to, but I can't. When connecting directly to Port 2 on the OC300, I cannot reach it at the old address, the new address, or the fallback address.
I've tried using NMAP to see if I can find it, but it doesn't show up.
Since the router is being controlled by the OC300, I can't log into that either.
- Copy Link
- Report Inappropriate Content
@Wayne110, you may need to unplug the cable from port 1 and power cycle it to force it to start up with the fallback IP.
- Copy Link
- Report Inappropriate Content
I have never tried this but I read on the internet (the link appears below) that you might be able to determine the controller's IP address by connecting a PC directly to the controller and running Wireshark. Filter the arp packets and they may give you a clue. It's odd that neither the old nor the new IP addresses respond. It almost sounds like a typo error when you entered the new address.
Link: support dot.wheatstone dot com/portal/en/kb/articles/using-wireshark-to-find-an-unknown-ip-address
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Vincent-TP after running a scanner on each of the subnets involved, I found that the controller did change its IP address to what I was trying to set it up with.
as far as the OC300 is concerned, everything is working fine.
- Copy Link
- Report Inappropriate Content
Thanks for sharing the solution, and it's great to hear that the issue has been resolved! If you encounter any further problems or have additional questions, feel free to reach out. We're here to help! 😊
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 261
Replies: 7
Voters 0
No one has voted for it yet.