Reboot schedules are not EAP215-Bridge friendly.

Reboot schedules are not EAP215-Bridge friendly.

Reboot schedules are not EAP215-Bridge friendly.
Reboot schedules are not EAP215-Bridge friendly.
2024-08-20 12:27:59 - last edited 3 weeks ago
Tags: #Mesh #bridge
Model: EAP215-Bridge KIT  
Hardware Version: V1
Firmware Version: 1.0.4 Build 20240312 Rel. 33492

This is my configuration:

ER7212PC---PoEinjector---EAP650-Outdoor

                  ---PoEinjector---EAP215-BridgeAP >>>WiFi<<< EAP215-BridgeClient---PoEinjector---PoEinjector---EAP610-Outdoor

*Traffic traveling from EAP650-Outdoor to EAP610-Outdoor through the bridge.

 

After a scheduled reboot:

ER7212PC---PoEinjector---EAP610-Outdoor >>>Mesh<<< EAP610-Outdoor

                  ---PoEinjector---EAP215-BridgeAP >>>WiFi<<< EAP215-BridgeClient---PoEinjector---PoEinjector---EAP610-Outdoor

*Traffic traveling from EAP650-Outdoor to EAP610-Outdoor via mesh.

 

The only sequence that fixes this is to forget both ends of the bridge (EAP215-BridgeAP and EAP215-BridgeClient), and the EAP610-Outdoor. Reprovision the bridge EAP215-BridgeAP first, reprovision the EAP215-BridgeClient second, and then reprovision the EAP610-Outdoor. The bridge kit does not like scheduled reboots. I hope TPL can do something about this.

  0      
  0      
#1
Options
1 Accepted Solution
Re:Reboot schedules are not EAP215-Bridge friendly. -Solution
2024-08-21 06:46:37 - last edited 3 weeks ago

Hi  @mccormiermt6 

 

This is mostly because the EAP610-Outdoor detected the EAP650-Outdoor signal before it detected the wired connection of the EAP215 bridge. In another word, the EAP610-outdoor was successfully meshed with the EAP650-outdoor before the EAP215 bridge KIT was successfully connected.

 

Suggestion:

1. Set the Tx power of EAP650-outdoor lower, so that the EAP610-outdoor won't mesh with it. But this will also reduce its wireless range.

2. Set different reboot times for these devices. For example: EAP650-outdoor reboot at 1AM every day, EAP215-bridge KIT reboot at 2AM every day, and EAP610-outdoor reboot at 3AM every day. I believe this will avoid this issue.

 

I would recommend suggestion 2 more.

Recommended Solution
  0  
  0  
#2
Options
2 Reply
Re:Reboot schedules are not EAP215-Bridge friendly. -Solution
2024-08-21 06:46:37 - last edited 3 weeks ago

Hi  @mccormiermt6 

 

This is mostly because the EAP610-Outdoor detected the EAP650-Outdoor signal before it detected the wired connection of the EAP215 bridge. In another word, the EAP610-outdoor was successfully meshed with the EAP650-outdoor before the EAP215 bridge KIT was successfully connected.

 

Suggestion:

1. Set the Tx power of EAP650-outdoor lower, so that the EAP610-outdoor won't mesh with it. But this will also reduce its wireless range.

2. Set different reboot times for these devices. For example: EAP650-outdoor reboot at 1AM every day, EAP215-bridge KIT reboot at 2AM every day, and EAP610-outdoor reboot at 3AM every day. I believe this will avoid this issue.

 

I would recommend suggestion 2 more.

Recommended Solution
  0  
  0  
#2
Options
Re:Reboot schedules are not EAP215-Bridge friendly.
2024-08-21 17:38:08

  @Vincent-TP this worked, thank you.

Vincent-TP wrote

Hi  @mccormiermt6 

 

This is mostly because the EAP610-Outdoor detected the EAP650-Outdoor signal before it detected the wired connection of the EAP215 bridge. In another word, the EAP610-outdoor was successfully meshed with the EAP650-outdoor before the EAP215 bridge KIT was successfully connected.

 

Suggestion:

1. Set the Tx power of EAP650-outdoor lower, so that the EAP610-outdoor won't mesh with it. But this will also reduce its wireless range.

2. Set different reboot times for these devices. For example: EAP650-outdoor reboot at 1AM every day, EAP215-bridge KIT reboot at 2AM every day, and EAP610-outdoor reboot at 3AM every day. I believe this will avoid this issue.

 

I would recommend suggestion 2 more.

 

  1  
  1  
#3
Options

Information

Helpful: 0

Views: 123

Replies: 2

Tags

Mesh
bridge
Related Articles