FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
417 views 2 comments
by anonymous
Hi,
How to configure Event Reporting for the specified events "Wired WAN connection nonoperational" and "Wired WAN connection operational"?
I need to monitor the WAN port in case if the specified port is down for more than a defined period.
At this moment the only way what I found is set a notification for LAN port state change but it sent notifications from all ports not only WAN/LAN ports.
RUT230 with FW ver.: RUT2XX_R_00.01.12.3

1 Answer

0 votes
by anonymous
Hi,

For that we have WAN Failover which can notify you once the main connection is down - so for this scenario let's say Wired WAN. You can set event reports once WAN Failover switches to secondary connection / or Main, this way you will know if your WAN is operational or not.

More information about this can be found here:

https://wiki.teltonika-networks.com/view/RUT240_WAN#Summary

https://wiki.teltonika-networks.com/view/RUT240_Events_Log#WAN_Failover

EB.
by anonymous
Unfortunately, WAN Failover is not what I need because it works only in case WAN + mobile but I am using only mobile to send SMS notifications (without APN) and single WAN.

I looked at Reporting Configuration for Networks events to FTP/Email but in my case, it can't send notification without connection with any email server.

Ping Reboot with SMS notification seems that not works when WAN is not connected. It is strange and in my opinion, it should send a notification in the same situation as the timeout at ping.

Update: It seems that Ping Reboot not works for remote addresses. Am I sure or something I set wrong?
by anonymous
I was able to replicate your issue with Wired WAN and ping reboot not working on unsuccessful ping. I've reported this issue to RnD and come back to you once I have any useful information.

EB.