Business Community > Controllers > OC300 doesn't reply to ping anymore
< Controllers

OC300 doesn't reply to ping anymore

OC300 doesn't reply to ping anymore

OC300 doesn't reply to ping anymore
OC300 doesn't reply to ping anymore
2025-01-14 12:14:06 - last edited 2025-01-16 07:57:23
Model: OC300  
Hardware Version:
Firmware Version:

Hello,

 

I've got a 14 months-old OC300 controller on a remote site which lately stopped to reply to ping.

A reboot didn't change anything.

The device lights are on.

 

I'm about to go on site to replace it but I would be very pleased to to connect once more to the current device before installing the new one.

 

The device is connected to LAN using front port 1.

If I'm not mistaken, this port is configured with a fixed address.

 

To get a backup of current confi, is it possible to use:

- the other Ethernet port (does it use a distinct IP address ?),

- an inner console port (does it exist ?)

- or the USB port to get CLI access the controller and ?

 

Best regards

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:OC300 doesn't reply to ping anymore-Solution
2025-01-14 22:20:52 - last edited 2025-01-16 07:57:23

Hi @Oliv2831,

 

I beleive the two ports are just bridged and there's just the one IP address for the device itself.  I've never heard of a console port on the controllers and I've not see an ssh option on the controller either (although that wouldn't help you).  Be sure to configure the backup job once you have this (or a new) controller online again.

Recommended Solution
  1  
  1  
#2
Options
3 Reply
Re:OC300 doesn't reply to ping anymore-Solution
2025-01-14 22:20:52 - last edited 2025-01-16 07:57:23

Hi @Oliv2831,

 

I beleive the two ports are just bridged and there's just the one IP address for the device itself.  I've never heard of a console port on the controllers and I've not see an ssh option on the controller either (although that wouldn't help you).  Be sure to configure the backup job once you have this (or a new) controller online again.

Recommended Solution
  1  
  1  
#2
Options
Re:OC300 doesn't reply to ping anymore
2025-01-16 08:09:45

For a reason, on this remote LAN, DHCP service didn't work properly anymore and both OC300 and APs adopted their default fallback IP.

This is the reason I couldn't reach the OC300 anymore.

Using fallback IP, I could communicate again with OC300 and understand what was going on.

 

To be honest, I didn't take much time to think about the strengths and weaknesses of this fallback IP feature.

 

Having tens of AP falling back to the same default IP is surprising.

On a side note, you can define a fallback IP but cannot define a gateway or DNS servers.

 

Anyway, from this incident, I identified several questions I'll ask in dedicated threads in this forum.

 

 

  0  
  0  
#3
Options
Re:OC300 doesn't reply to ping anymore
2025-01-16 16:45:02

  @Oliv2831,

 

"Having tens of AP falling back to the same default IP is surprising" surprise

 

Yeah, a post to see what others do would be interesting.  I just set the fallback IP to match the DHCP assigned value because if everything is powered on at the same time my APs/switches try to request an IP address before my DHCP service is running.

  0  
  0  
#4
Options

Information

Helpful: 0

Views: 196

Replies: 3

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.