4
Votes

Not getting alerts for WAN failover activation

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

Not getting alerts for WAN failover activation

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Not getting alerts for WAN failover activation
Not getting alerts for WAN failover activation
2022-06-08 15:25:25 - last edited 2022-06-09 08:55:53
Tags: #failover
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: 1.2.0

I have my ER605 connected to my cable modem (Netgear CM1000) as the primary WAN and my LTE modem (Netgear LM1200) as the backup WAN. Failover has worked successfully twice since I've had the backup modem set up, but even though I have alerts set up, I haven't received any. To cover all my bases, I've enabled events and alerts for 'WAN is down', 'WAN is up', 'Backup WAN Takes Effect', and 'Primary WAN Recovered'. I get other alerts (controller down/up, etc). I have noticed that during the cable modem outages, WAN still shows as 'up' because the cable modem is still turned on and communicating with the router, just not the upstream ISP. Omada is obviously detecting a problem with the cable modem connection and switching to the LTE modem, and switching back. It's just not letting me know; my wife usually lets me know because the changeover disrupts whatever my daughter is watching on Disney+. What am I missing?

 

Software controller is on version 5.3.1

#1
Options
11 Reply
Re:Not getting alerts for WAN failover activation
2022-06-09 06:03:27 - last edited 2022-06-09 08:55:53

  @iampegram 

settings > admin > check your profile. do you enable email notification?

not every log is pushing notification to you unless you select that and send to u by email. 

ScReW yOu gUyS. I aM GOinG hoMe. —————————————————————— For heaven's sake, can you write and describe your issue based on plain fact, common logic and a methodologic approach? Appreciate it.
#2
Options
Re:Not getting alerts for WAN failover activation
2022-06-09 08:02:01 - last edited 2022-06-09 08:55:53

iampegram wrote

I have my ER605 connected to my cable modem (Netgear CM1000) as the primary WAN and my LTE modem (Netgear LM1200) as the backup WAN. Failover has worked successfully twice since I've had the backup modem set up, but even though I have alerts set up, I haven't received any. To cover all my bases, I've enabled events and alerts for 'WAN is down', 'WAN is up', 'Backup WAN Takes Effect', and 'Primary WAN Recovered'. I get other alerts (controller down/up, etc). I have noticed that during the cable modem outages, WAN still shows as 'up' because the cable modem is still turned on and communicating with the router, just not the upstream ISP. Omada is obviously detecting a problem with the cable modem connection and switching to the LTE modem, and switching back. It's just not letting me know; my wife usually lets me know because the changeover disrupts whatever my daughter is watching on Disney+. What am I missing?

 

Software controller is on version 5.3.1

  @iampegram Have had the same problem with a TP-Link router, where the primary WAN is delivered by PPPoE via an ISP modem. The solution is to activate a 'keep alive' ping (not DNS lookup) to say 8.8.8.8, running at intervals.  This will detect if the up stream network is offline, even if the modem indicates that the WAN is up.  

#3
Options
Re:Not getting alerts for WAN failover activation
2022-06-10 02:46:54

  @Tedd404 the switchover events don't even show in the event log. I'll try enabling email alerts, but I don't think that'll help...

 

@GaelForce where do I find that option in Omada Controller? I only have a drop down box to select the detection interval.

#4
Options
Re:Not getting alerts for WAN failover activation
2022-06-10 08:57:41

  @iampegram 

wan disconnect would show up in the log. switch over should do that as well. do you find the switchover in the event/alert list?

ScReW yOu gUyS. I aM GOinG hoMe. —————————————————————— For heaven's sake, can you write and describe your issue based on plain fact, common logic and a methodologic approach? Appreciate it.
#5
Options
Re:Not getting alerts for WAN failover activation
2022-06-10 15:57:33

  @Tedd404 there are no entries in the log at the time of the switchover. WAN still shows active during this time because the connection between the modem and the router is still up. When the upstream cable connection is interrupted, the router does switch to the LTE modem, and it switches back when the upstream cable is restored. It just does so silently, which I don't want. I want to make sure I don't go over budget on LTE without having to constantly monitor it.

#6
Options
Re:Not getting alerts for WAN failover activation
2022-11-22 17:09:45

This is still happening as of controller version 5.6.3. Anyone have any advice? I can post logs...

#7
Options
Re:Not getting alerts for WAN failover activation
2023-02-25 16:02:50

  @iampegram 

I'm having the same issue and same gear/setup and I need to know when it fails over to monitor usage.

Does your sim have texting? The LM1200 can do failover itself when installed between the modem and router. It pings 8.8.8.8 for connectivity and can text in switch over events and data usage. Unfortunately my sim doesn't have texting.  

#8
Options
Re:Not getting alerts for WAN failover activation
2023-04-25 21:15:24

  @tc944 
Sorry for asking on an old post but need help on activating alerts. Configuring Omada controller is mandatory? Is there a simpler way? I've just would like to know when a WAN link is down. Thanks

#9
Options
Re:Not getting alerts for WAN failover activation
2023-05-04 17:29:15
I believe my SIM allows texting, but the whole point of the dual WAN ports on the ER605 is to allow for failover (or load balancing). BTW, still a problem in 5.9.31
#10
Options
Re:Not getting alerts for WAN failover activation
2023-05-12 12:45:06

  @iampegram  check the timing for log --> alert --> notification.  See if there is a hidden nuisance timer that requires the issue to persist for 5 minutes (or whatever time) before it is logged... longer for alert or notification.  I didn't see any duration of outage or WAN failover in this thread.  

#11
Options