EAP225 v4.0 is disconnected from Omada Controller v5.5.6

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

EAP225 v4.0 is disconnected from Omada Controller v5.5.6

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
EAP225 v4.0 is disconnected from Omada Controller v5.5.6
EAP225 v4.0 is disconnected from Omada Controller v5.5.6
2022-10-20 10:45:07
Model: EAP225  
Hardware Version: V4
Firmware Version: 5.0.8

Hello,

 

I have been working with EAP225 v3.0 and v4.0 for some time. But I have got a problem with EAP225 v4.0 firmware version 5.0.8 over Omada TPlink Cloud.

 

Actually, the EAP225 devices and the Omada Controller are in different networks. All of the EAP225 devices with version 3.0 work correctly and they are not problem. But EAP225 v4.0 are disconnected from Omada Controller.

 

What I know, first to configure the EAP225 device with the Omada Controller, they must be in a same network that can see each other. 

After the relevant configuration and settings, I transfer the EAP225 device to the desired building. After completing the installation process, I turn on the device.

After about 1 minute, EAP225 v3.0 devices to Omada Controller without problem are connected and I can see and control them. But EAP225 v4.0 devices no longer appear in the controller and are disconnected.

 

After checking, I found that EAP225 v3.0 devices gets the new network IP from DHCP. But EAP225 v4.0 devices still appear in Omada Controller with previous IP.

The most interesting thing is that EAP225 v4.0 works and anyone can connect to this device and get internet services. But on the Omada Controller, it still shows disconnected. (see as below)

What do you suggest to solve this problem?

 

Best regards,

Yashar

  0      
  0      
#1
Options
2 Reply
Re:EAP225 v4.0 is disconnected from Omada Controller v5.5.6
2022-10-21 07:43:19

  @Yashar 

 

The IP addresses of the EAP and the controller are not in the same network segment and cannot communicate with each other, you can try reboot the EAP.
Alternatively, you can forget the EAP and reconfigure it.

Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:EAP225 v4.0 is disconnected from Omada Controller v5.5.6
2022-10-21 17:12:54

  @Yashar 

 

If you have the possibility of working with VLANs, you can choose to adopt the nodes and then assign them a management VLAN, in this way it does not matter what IP they have and what range they are in, but they will always be seen by the console by a certain VLAN.

What you need next is to create different WLANs, with different VLAN IDs to determine where each VLAN ID is posted.

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 640

Replies: 2

Related Articles