Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud

Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud

Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud
Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud
3 weeks ago - last edited 3 weeks ago
Model: EAP773  
Hardware Version: V1
Firmware Version: 1.0.13

Hello,

I have a strange problem with a network.

 

1x AVM Fritz!Box as Router 192.168.2.1 (with 1 GBit fiber optic) (DHCP, DNS, Gateway)

2x SG2428P Switch 192.168.2.30 + 31 (static LAN IP)

2x SG2210P Switch 192.168.2.32 + 33 (static LAN IP)

9x EAP773 192.168.2.40-48 (static LAN IP)

DHCP from Fritz!Box from 192.168.2.50-199

No VLAN

No onsite controller

 

The WLAN APs are connected through cable RJ45 with PoE from the switches.

MESH is disable in the site settings.

 

All 9 wlan APs show Recurring HEARTBEAT MISSED in the web Omada status.

There is no such problem with the 4 switche.

 

WLAN works fine and i can ping all wlan APs from a pc without any package loss or slow connection.

So the cabeling to the APs don't seems the problem.

 

I tried DHCP for the devices but this does not change anything.

There are no other devices with the same IPs.

 

The devices have the most current updates.

 

The omada log show nothing:

No entry in the table.

 

Somebody any ideas?

It feels like a omada bug beause the LAN pings are stable and the switches don't show this problem.

 

Thanks

Stefan

 

One AP is currently unplugged.

  0      
  0      
#1
Options
6 Reply
Re:Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud
3 weeks ago

Hi  @StefanKittel 

 

When the EAP shows heartbeat missed, is the wireless network affected?

Will they turn to Connected status automatically? Or need a manually reboot? or anything else?

 

How did you power on the EAPs?

Wish you a happy life and smooth network usage! 
  0  
  0  
#2
Options
Re:Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud
3 weeks ago

  @Vincent-TP 

 

Hello,

 

>When the EAP shows heartbeat missed, is the wireless network affected?

No

And i can ping the WLAN APs all the time without a ping missing.

 

>Will they turn to Connected status automatically? Or need a manually reboot? or anything else?

Nothing need to be done. They work all the time.

I even can change their LAN ip when the heartbeat is missing and it works.

 

>How did you power on the EAPs?

PoE through the tp-link switche.

 

Stefan

  0  
  0  
#3
Options
Re:Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud
3 weeks ago

Update: I added an ER8411

ER8411 192.168.2.1 (DNS+DHCP+GW)

Fritz!Box 192.168.6.1 (WAN)

 

Same Problem

  0  
  0  
#4
Options
Re:Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud
3 weeks ago

Can I download any debug-information and send them to the support?

  0  
  0  
#5
Options
Re:Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud
3 weeks ago

I found the network tools

I took an EAP which is showing missing heardbeat and pinged 8.8.8.8 from it.

Works fine. No Problem.

 

Can you tell me a hostname or ip to which the EAP would connect?

 

If I want to use a local controller.

Which model would fit?

 

Stefan

  0  
  0  
#6
Options
Re:Recurring HEARTBEAT MISSED with EAP773(EU) v1.0 1.0.13 Build 20240417 Rel. 57733 and omada cloud
3 weeks ago

Hi  @StefanKittel 

 

May we know what kind of controller you are using?

 

We recommend submitting a support ticket via email for efficient assistance.
Please include the following information in the email:
1. this Forum ID 734182;
2. your community nickname;

3. The type of controller you are using and its config file;

 

Wish you a happy life and smooth network usage! 
  0  
  0  
#7
Options