RUT230 Events Log: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
 
(32 intermediate revisions by 6 users not shown)
Line 1: Line 1:
==Summary==
{{Template: Networking_rut2xx_manual_events_log
 
| name   = RUT230
The '''Events Log''' windows display records of such event as logins, reboots, resets, connections, configuration changes and more.
| series = RUT2XX
 
}}
 
[[Image:Status events log.PNG]]
 
==Events Reporting==
 
The '''Events Reporting''' section gives you the ability to configure rules that will inform you via SMS or email when certain events occur on your router. These events can be almost anything – configuration changes, reboots, new connections, various status updates, etc.
 
 
[[Image:Status events log events reporting.PNG]]
 
 
===Events Reporting Configuration===
----
'''Events Reporting Configuration''' is used to create and customize Events Reporting Rules. Here you can specify any event type and subtype, chose whether you want to be informed by an SMS message or email, modify what kind of information you want receive should an event occur. To open this window, choose an Event type, Event subtype and Action and click the '''Add''' button. A new rule should appear in the Events Reporting Rules tab. Click the '''Edit''' button located next to that rule after which you will be redirected to that rule's configuration window.
 
====Send SMS====
----
 
[[Image:Status events log events reporting rule configuration.PNG]]
 
<table class="nd-mantable">
<tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Enable</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles the rule ON or OFF</td>
    </tr>
    <tr>
      <td>Event type</td>
      <td>Config change {{!}} New DHCP client {{!}} FW upgrade {{!}} Mobile data {{!}} SMS {{!}} SIM switch {{!}} Signal Strength {{!}} Reboot {{!}} SSH {{!}} WebUI {{!}} New WiFi client {{!}} LAN port state {{!}} Backup {{!}} Restore point {{!}} GPS;
 
Default: '''Config change'''</td>
      <td>The type of event that you wish to receive information about</td>
    </tr>
    <tr>
    <td>Event subtype</td>
        <td>'''Sample:''' After unexpected shut down</td>
        <td>Specified event's sub-type. This field changes in accordance with '''Event type'''</td>
    </tr>
    <tr>
    <td>Action</td>
        <td>Send SMS {{!}} Send email; Default: '''Send SMS'''</td>
        <td>Action that is to be taken after the specified event occurs</td>
    </tr>
  <tr>
      <td>Enable delivery retry</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles delivery retry On or OFF. If for some reason the message delivery is unsuccessful, the router initiates a retry if this field is enabled</td>
    </tr>
    <tr>
      <td>Retry interval</td>
      <td>1 min. {{!}} 5 min. {{!}} 10 min. {{!}} 15 min. {{!}} 30 min. {{!}} 60 min.; Default '''5 min.'''</td>
      <td>Specifies when the router should try re-sending the message in case the first attempt was a failure</td>
    </tr>
    <tr>
    <td>Retry count</td>
        <td>2 {{!}} 3 {{!}} 4 {{!}} 5 {{!}} 6 {{!}} 7 {{!}} 8 {{!}} 9 {{!}} 10; Default: '''2'''</td>
        <td>Specifies the maximum number of failed attempts after which the router does not try to send the message anymore</td>
    </tr>
    <tr>
    <td>Message text on Event</td>
        <td>string; Default: '''Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts;'''</td>
        <td>Specifies the text that the message will contain</td>
    </tr>
  <tr>
      <td>Get status after reboot </td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Specifies whether the router should send an SMS message indicating the router's status after the reboot in addition to the original message</td>
    </tr>
    <tr>
      <td>Status message after reboot</td>
      <td>string; Default: '''Router name - %rn; WAN IP - %wi; Data Connection state - %cs; Connection type - %ct; Signal strength - %ss; New FW available - %fs;'''</td>
      <td>Specifies the text that the status message will contain. This field becomes visible only if '''Get status after reboot''' is checked</td>
    </tr>
    <tr>
    <td>Recipients</td>
        <td>Single number {{!}} User group; Default: '''Single number'''</td>
        <td>Specifies the intended recipients. A guide on how to create a User group can be found in the SMS Utilities chapter, [[SMS_Utilities#User_Groups| User Groups]] section</td>
    </tr>
    <tr>
    <td>Recipient's phone number</td>
        <td>phone number; Default: " "</td>
        <td>The intended recipient's phone number. To add more than one number, click the green [[Image:Services sms gateway auto reply plus symbol.PNG]] plus symbol located to the right of this field. The phone number must be entered in the international format, but without dash symbols or spaces, e.g., '''+37061234567'''</td>
    </tr>
</table>
 
====Send Email====
----
 
[[Image:Status events log events reporting rule configuration email.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Enable</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles the rule ON or OFF</td>
    </tr>
    <tr>
      <td>Event type</td>
      <td>Config change {{!}} New DHCP client {{!}} FW upgrade {{!}} Mobile data {{!}} SMS {{!}} SIM switch {{!}} Signal Strength {{!}} Reboot {{!}} SSH {{!}} WebUI {{!}} New WiFi client {{!}} LAN port state {{!}} Backup {{!}} Restore point {{!}} GPS;
 
Default: '''Config change'''</td>
      <td>The type of event that you wish to receive information about</td>
    </tr>
    <tr>
    <td>Event subtype</td>
        <td>'''Sample:''' After unexpected shut down</td>
        <td>Specified event's sub-type. This field changes in accordance with '''Event type'''</td>
    </tr>
    <tr>
    <td>Action</td>
        <td>Send SMS {{!}} Send email; Default: '''Send SMS'''</td>
        <td>Action that is to be taken after the specified event occurs</td>
    </tr>
    <tr>
      <td>Enable delivery retry</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles delivery retry On or OFF. If for some reason the message delivery is unsuccessful, the router initiates a retry if this field is enabled</td>
    </tr>
    <tr>
      <td>Retry interval</td>
      <td>1 min. {{!}} 5 min. {{!}} 10 min. {{!}} 15 min. {{!}} 30 min. {{!}} 60 min.; Default '''5 min.'''</td>
      <td>Specifies when the router should try re-sending the message in case the first attempt was a failure</td>
    </tr>
    <tr>
    <td>Retry count</td>
        <td>2 {{!}} 3 {{!}} 4 {{!}} 5 {{!}} 6 {{!}} 7 {{!}} 8 {{!}} 9 {{!}} 10; Default: '''2'''</td>
        <td>Specifies the maximum number of failed attempts after which the router does not try to send the message anymore</td>
    </tr>
    <tr>
    <td>Subject</td>
        <td>string; Default: " "</td>
        <td>Specifies the subject of the email message</td>
    </tr>
    <tr>
      <td>Message text on Event</td>
      <td>string; Default: '''Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts;'''</td>
      <td>Specifies the text that the message will contain</td>
    </tr>
    <tr>
      <td>Get status after reboot </td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Specifies whether the router should send an SMS message indicating the router's status after the reboot in addition to the original message. If this is checked you will be prompted to enter the text that the status message should contain</td>
    </tr>
    <tr>
    <td>SMTP server</td>
        <td>ip {{!}} host; Default: " "</td>
        <td>Sender's email service provider's SMTP server. If you don't know the SMTP server's address, you can easily look it up online since it is public information</td>
    </tr>
    <tr>
    <td>SMTP port</td>
        <td>integer [0..65535]; Default: " "</td>
        <td>Sender's email service provider's SMTP port. If you don't know the SMTP server's port, you can easily look it up online since it is public information</td>
    </tr>
    <tr>
      <td>Secure  connection </td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles secure connection feature ON or OFF (use only if the email service provider's server supports SSL or TLS)</td>
    </tr>
    <tr>
      <td>Username</td>
      <td>string; Default: " "</td>
      <td>Sender's email account's login user name</td>
    </tr>
    <tr>
    <td>Password</td>
        <td>string; Default: " "</td>
        <td>Sender's email account's login password</td>
    </tr>
    <tr>
    <td>Sender's email address</td>
        <td>email; Default: " "</td>
        <td>The email address of the sender, i.e., the report message will be sent from this email. Make sure this is the same email that you provided login information to </td>
    </tr>
    <tr>
    <td>Recipient's email address</td>
        <td>email; Default: " "</td>
        <td>The intended recipient's email address. To add more than one email address, click the green [[Image:Services sms gateway auto reply plus symbol.PNG]] plus symbol located to the right of this field</td>
    </tr>
    <tr>
    <td>Send test mail</td>
        <td>-</td>
        <td>Sends a test mail using the information that you provided. Once you click this button, the router will login to the provided email account and send the specified message to the specified address(-es). You should always send a test mail before finishing the configuration to make sure that everything is in order</td>
    </tr>
</table>
 
====Event Types and Sub-types====
----
The examples provided above are both concerning the '''Reboot''' Event type and '''After unexpected shut down''' sub-type. This section is an overview of all other Event type and sub-types.
 
=====Config change=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when any type of configuration changes are applied</td>
    </tr>
    <tr>
      <td>OpenVPN</td>
      <td>Sends a report message when any '''[[VPN#OpenVPN|OpenVPN]]''' configuration changes are applied. For example, whenever a new OpenVPN instance is created, an OpenVPN instance gets disabled/enabled, an OpenVPN instance's protocol is changed from UDP to TCP or vice versa, etc.</td>
    </tr>
    <tr>
    <td>SMS</td>
        <td>Sends a report message when any SMS related configuration changes are applied. For example, whenever a new '''[[SMS Utilities]]''' rule is created or changed, changes are made to '''[[SMS_Gateway#Auto_Reply|Auto Reply]]''' or '''[[SMS_Utilities#Remote_Configuration|Remote configurations]]''', etc.</td>
    </tr>
    <tr>
    <td>Mobile traffic</td>
        <td>Sends a report message when '''[[RUT230 Mobile Traffic|Mobile Traffic]]''' Logging is enabled/disabled or logging interval is changed.</td>
    </tr>
    <tr>
      <td>Multiwan</td>
      <td>Sends a report message when changes to WAN '''[[WAN#Backup_Configuration|Backup]]''' configuration are applied. For example, whenever a switch from using Wired as main WAN to backup WAN occurs, Wireless is added as a Backup WAN, Health monitor configurations are changed, etc.</td>
    </tr>
    <tr>
      <td>Mobile</td>
      <td>Sends a report message when any '''[[Mobile]]''' configuration changes are applied. For example, whenever Service mode, APN, Connection type is changed, etc.</td>
    </tr>
    <tr>
    <td>Data limit</td>
        <td>Sends a report message when any '''[[Mobile#Mobile_Data_Limit|Mobile Data Limit]]''' configuration changes are applied. For example, whenever new data limit is configured, data limit gets disabled/enabled on SIM1/SIM2, data limit period is changed, etc.</td>
    </tr>
    <tr>
    <td>Events reporting</td>
        <td>Sends a report message when any configuration changes to Events Reporting are applied. For example, whenever a new Events Reporting Rule is created, changed, deleted, etc.</td>
    </tr>
    <tr>
      <td>Periodic reboot</td>
      <td>Sends a report message when any configuration changes to '''[[Auto_Reboot#Periodic_Reboot|Periodic Reboot]]''' are applied. For example, whenever Periodic Reboot gets enabled/disabled, Periodic Reboot interval is changed, etc.</td>
    </tr>
    <tr>
      <td>GRE Tunnel</td>
      <td>Sends a report message when any configuration changes to '''[[VPN#GRE_Tunnel|GRE Tunnel]]''' are applied. For example, whenever a new GRE Tunnel instance is created, deleted, enabled/disabled, Local tunnel IP is changed, etc.</td>
    </tr>
    <tr>
    <td>Ping reboot</td>
        <td>Sends a report message when any configuration changes to '''[[Auto_Reboot#Ping_Reboot|Ping Reboot]]''' are applied. For example, whenever Ping Reboot gets enabled/disabled, host to ping has changed, etc.</td>
    </tr>
    <tr>
    <td>Auto update</td>
        <td>Sends a report message when any configuration changes to Auto update are applied</td>
    </tr>
    <tr>
      <td>Site blocking</td>
      <td>Sends a report message when any configuration changes to '''[[Web_Filter#Site_Blocking|Site Blocking]]''' are applied. For example, whenever Whitelist is changed to Blacklist or vice versa, a new entry is added to Blacklist/Whitelist, etc.</td>
    </tr>
    <tr>
      <td>PPTP</td>
      <td>Sends a report message when any configuration changes to '''[[VPN#PPTP|PPTP]]''' are applied. For example, whenever a new PPTP instance was created, deleted, enabled/disabled, PPTP server address was changed, etc.</td>
    </tr>
    <tr>
    <td>Hotspot</td>
        <td>Sends a report message when any configuration changes to '''[[Hotspot]]''' are applied. For example, whenever Hotspot SSID was changed, Radius server was changed, Hotspot was enabled/disabled, etc.</td>
    </tr>
    <tr>
    <td>Input/Output</td>
        <td>Sends a report message when any configuration changes to '''[[RUT2xx Input/Output|Input/Output]]''' are applied. For example, whenever a new '''[[RUT2xx Input/Output#Periodic_Control|Periodic Output Control]]''' Rule was created, changed, deleted, an output was turn ON/OFF, etc.</td>
    </tr>
    <tr>
      <td>Content blocker</td>
      <td>Sends a report message when any configuration changes to '''[[Web_Filter#Proxy_Based_Content_Blocker|Proxy Based Content Blocker]]''' are applied. For example, whenever Whitelist is changed to Blacklist or vice versa, a new entry is added to Blacklist/Whitelist, etc.</td>
    </tr>
    <tr>
      <td>Login page</td>
      <td>Sends a report message when the router's '''[[RUT955 Administration#General|login password]]''' is changed</td>
    </tr>
    <tr>
    <td>Language</td>
        <td>Sends a report message when any '''[[RUT955 Administration#General|Language Settings]]''' are changed</td>
    </tr>
    <tr>
    <td>Profile</td>
        <td>Sends a report message when the router's '''[[RUT955 Administration#General|login password]]''' is changed</td>
    </tr>
    <tr>
      <td>DDNS</td>
      <td>Sends a report message when any configuration changes to '''[[RUT230 Dynamic DNS|Dynamic DNS]]''' are applied. For example, whenever a new DDNS instance is created, changed, deleted or edited</td>
    </tr>
    <tr>
      <td>IPsec</td>
      <td><Sends a report message when any configuration changes to '''[[VPN#IPsec|IPsec]]''' are applied. For example, a new IPsec instance is created, changed, deleted, etc./td>
    </tr>
    <tr>
    <td>Access control</td>
        <td>ends a report message when any configuration changes to Access Control are applied. For example, SSH/HTTP/HTTPS remote or local access is enabled/disabled, changes are made to SSH or WebUI Access Secure, etc.</td>
    </tr>
    <tr>
    <td>DHCP</td>
        <td>Sends a report message when any configuration changes to '''[[LAN|DHCP]]''' are applied. For example, whenever DHCP Server is enabled/disabled, DHCP address range is changed</td>
    </tr>
    <tr>
      <td>VRRP</td>
      <td>Sends a report message when any configuration changes to '''[[VRRP]]''' are applied. For example, whenever VRRP is enabled/disabled, VRRP IP address is changed, etc.</td>
    </tr>
    <tr>
      <td>SSH</td>
      <td>Sends a report message when any configuration changes to SSH are applied</td>
    </tr>
    <tr>
    <td>Network</td>
        <td>Sends a report message when any Network related configuration changes are applied. For example, whenever Main WAN is changed, LAN IP address is changed, a Wi-Fi Access Point is enabled/disabled, etc.</td>
    </tr>
    <tr>
    <td>Wireless</td>
        <td>Sends a report message when any configuration changes to '''[[Wireless]]''' are applied. For example, a new Wi-Fi Access point is created, deleted, enabled/disabled, SSID is changed, etc.</td>
    </tr>
    <tr>
      <td>Firewall</td>
      <td>Sends a report message when any configuration changes to '''[[Firewall]]''' are applied. For example, a new Traffic rule is added, a new SNAT rule is added, a rule is disabled/enabled, etc.</td>
    </tr>
    <tr>
      <td>NTP</td>
      <td>Sends a report message when any configuration changes to '''[[NTP]]''' are applied. For example, whenever NTP is enabled/disabled, Time zone is changed, etc.</td>
    </tr>
    <tr>
    <td>L2TP</td>
        <td>Sends a report message when any configuration changes to '''[[VPN#L2TP|L2TP]]''' are applied. For example, whenever a new L2TP instance was created, changed, deleted, etc.</td>
    </tr>
    <tr>
    <td>Other</td>
        <td>Sends a report message when any configuration changes other than the ones provided above are applied</td>
    </tr>
</table>
 
=====New DHCP client=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px"></th>
      <th style="width: 1000px"></th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when a new devices is connected to the router either via LAN or Wi-Fi</td>
    </tr>
    <tr>
      <td>Connected from WiFi</td>
      <td>Sends a report message when a new device is connected to the router via Wi-Fi</td>
    </tr>
    <tr>
    <td>Connected from LAN</td>
        <td>Sends a report message when a new device is connected to the router via LAN port</td>
    </tr>
</table>
 
=====FW Upgrade=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when the router initiates a Firmware upgrade (either from an uploaded FW file or from server)</td>
    </tr>
    <tr>
      <td>From file</td>
      <td>Sends a report message when the router initiates a Firmware upgrade from an uploaded FW file</td>
    </tr>
    <tr>
    <td>From server</td>
        <td>Sends a report message when the router initiates a Firmware upgrade from server</td>
    </tr>
</table>
 
=====Mobile Data=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when the router initiates a Firmware upgrade (either from an uploaded FW file or from server)</td>
    </tr>
    <tr>
      <td>From file</td>
      <td>Sends a report message when the router initiates a Firmware upgrade from an uploaded FW file</td>
    </tr>
    <tr>
    <td>From server</td>
        <td>Sends a report message when the router initiates a Firmware upgrade from server</td>
    </tr>
</table>
 
=====SMS=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
    <td>SMS received </td>
        <td>Sends a report message when the router receives a new SMS message</td>
    </tr>
</table>
 
=====Signal Strength=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when the router's '''[[RSSI]]''' value leaves any one of the below specified ranges</td>
    </tr>
    <tr>
      <td>-121 dBm -113 dBm</td>
      <td>Sends a report message when the router's RSSI value leaves the -121 dBm to -113 dBm range</td>
    </tr>
    <tr>
    <td>-113 dBm -98 dBm</td>
        <td>Sends a report message when the router's RSSI value leaves the -113 dBm to -98 dBm range</td>
    </tr>
    <tr>
    <td>-98 dBm -93 dBm</td>
        <td>Sends a report message when the router's RSSI value leaves the -98 dBm to -93 dBm range</td>
    </tr>
    <tr>
      <td>-93 dBm -75 dBm</td>
      <td>Sends a report message when the router's RSSI value leaves the -93 dBm to -75 dBm range</td>
    </tr>
    <tr>
    <td>-75 dBm -60 dBm</td>
        <td>Sends a report message when the router's RSSI value leaves the -75 dBm to -60 dBm range</td>
    </tr>
    <tr>
    <td>-60 dBm -50 dBm</td>
        <td>Sends a report message when the router's RSSI value leaves the -60 dBm to -50 dBm range</td>
    </tr>
</table>
 
=====Reboot=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when the router starts up after any type of reboot (except factory reset)</td>
    </tr>
    <tr>
      <td>After unexpected shutdown</td>
      <td>Sends a report message when the router shuts down unexpectedly and starts back up again</td>
    </tr>
    <tr>
    <td>From WebUI</td>
        <td>Sends a report message when the router starts up after a reboot command is initiated from the router's WebUI Administration->Reboot section</td>
    </tr>
    <tr>
    <td>From SMS</td>
        <td>Sends a report message when the router starts up after a reboot command is initiated via SMS</td>
    </tr>
    <tr>
      <td>From Input/Output</td>
      <td>Sends a report message when the router starts up after a reboot command is initiated via Input/Output</td>
    </tr>
    <tr>
      <td>From ping reboot</td>
      <td>Sends a report message when the router starts up after a reboot command is initiated by the Ping Reboot function</td>
    </tr>
    <tr>
    <td>From periodic reboot</td>
        <td>Sends a report message when the router starts up after a reboot command is initiated by the Periodic Reboot function</td>
    </tr>
    <tr>
    <td>From button</td>
        <td>Sends a report message when the router starts up after being restarted by the press of the physical button located on the router</td>
    </tr>
</table>
 
=====SSH=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when someone connects to the router via SSH (either successfully or unsuccessfully)</td>
    </tr>
    <tr>
      <td>Successful authentication</td>
      <td>Sends a report message when someone successfully connects to the router via SSH</td>
    </tr>
    <tr>
    <td>Unsuccessful authentication</td>
        <td>Sends a report message when someone unsuccessfully tries to connect to the router via SSH</td>
    </tr>
</table>
 
=====WebUI=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when someone connects to the router via HTTP or HTTPS (either successfully or unsuccessfully)</td>
    </tr>
    <tr>
      <td>Successful authentication</td>
      <td>Sends a report message when someone successfully connects to the router via HTTP or HTTPS</td>
    </tr>
    <tr>
    <td>Unsuccessful authentication</td>
        <td>Sends a report message when someone unsuccessfully tries to connect to the router via HTTP or HTTPS</td>
    </tr>
    <tr>
</table>
 
=====New WiFi client=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when a device connects to or disconnects from the router's WLAN (Wireless Network or Wireless LAN)</td>
    </tr>
    <tr>
      <td>Connected</td>
      <td>Sends a report message when a device connects to the router's WLAN</td>
    </tr>
    <tr>
    <td>Disconnected</td>
        <td>Sends a report message when a device disconnects from the router's WLAN</td>
    </tr>
</table>
 
=====LAN Port State=====
----
<table class="nd-othertables">
    <tr>
        <th style="width: 250px">EVENT SUB-TYPE</th>
      <th style="width: 1000px">DESCRIPTION</th>
    </tr>
    <tr>
      <td>All</td>
      <td>Sends a report message when a device is either plugged in or unplugged from one of the router's LAN ports</td>
    </tr>
    <tr>
      <td>Unplugged</td>
      <td>Sends a report message when a device is unplugged from one of the router's LAN ports</td>
    </tr>
    <tr>
    <td>Plugged in </td>
        <td>Sends a report message when a device is plugged into one of the router's LAN ports</td>
    </tr>
</table>
 
=====Backup=====
----
{| class="wikitable"
|+
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | EVENT SUB-TYPE
! style="width: 1000px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | All
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sends a report message when the router switches from using the Main WAN to using the Backup WAN and vice versa
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Switched to main
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sends a report message when the router switches from using the Main WAN to using the Backup WAN
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Switched to backup
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sends a report message when the router stops using the Backup WAN and start using the Main WAN
|-
|}
 
=====Restore Point=====
----
{| class="wikitable"
|+
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | EVENT SUB-TYPE
! style="width: 1000px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | All
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sends a report message when either when a new Restore point is created or a Restore Point is loaded in to the router
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Save
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sends a report message when a new Restore Point is created
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Load
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sends a report message when a Restore Point is loaded on to the router
|-
|}
 
==Reporting Configuration==
 
The '''Reporting Configuration''' section lets you create rules that transfer logs to email or FTP.
 
 
[[Image:Status events log reporting configuration.PNG]]
 
===Events Log Report Configuration===
----
'''Events Log Report Configuration''' provides you with the ability to change the configuration of periodic events reporting to email or FTP. You can access it by creating a rule and clicking the '''Edit''' button next to it, just like Event Reporting Configuration.
 
====FTP====
----
 
[[Image:Status events log events log reporting configuration.PNG]]
 
{| class="wikitable"
|+
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Enable
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Toggles the log file report rule ON or OFF
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Events log
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | System {{!}} Network {{!}} All; Default: '''System'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies which log to transfer
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Transfer type
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Email {{!}} FTP; Default: '''Email'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies whether to transfer the log(s) to FTP or Email
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Compress file
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Compress events log file using gzip
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Enable delivery retry
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Toggles delivery retry On or OFF. If for some reason the message delivery is unsuccessful, the router initiates a retry if this field is enabled
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Host
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | host {{!}} ip; Default " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | FTP server's IP address or hostname
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Retry count
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | 2 {{!}} 3 {{!}} 4 {{!}} 5 {{!}} 6 {{!}} 7 {{!}} 8 {{!}} 9 {{!}} 10; Default: '''2'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies the maximum number of failed attempts after which the router does not try to send the message anymore
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | User name
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | string; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Login user name used for authentication to the FTP server
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Password
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | string; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Login password used for authentication to the FTP
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Interval between reports
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Week {{!}} Month {{!}} Year; Default: '''Week'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies how often the reports should be sent
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Weekday {{!}} Month day
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | weekday {{!}} month day; Default: '''Sunday'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies the day of the month/week when the logging should take place. This field changes in accordance with '''Interval between reports'''
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Hour
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | integer [1..24]; Default: '''1'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies on the hour of the day when the logging should take place
|-
|}
 
====Email====
----
 
[[Image:Status events log events log reporting configuration email.PNG]]
 
{| class="wikitable"
|+
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Enable
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Toggles the log file report rule ON or OFF
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Events log
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | System {{!}} Network {{!}} All; Default: '''System'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies which log to transfer
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Transfer type
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Email {{!}} FTP; Default: '''Email'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies whether to transfer the log(s) to FTP or Email
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Compress file
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Compress events log file using gzip
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Subject
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | string; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies the subject of the email log message
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Message
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | string; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The text contained in the log email. This has nothing to do with the log itself, which will be sent as an attached file
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | SMTP server
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip {{!}} host; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sender's email service provider's SMTP server. If you don't know the SMTP server's address, you can easily look it up online since it is public information
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | SMTP server port
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | integer [0..65535]; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sender's email service provider's SMTP server. If you don't know the SMTP server's address, you can easily look it up online since it is public information
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Secure  connection
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Toggles secure connection feature ON or OFF (use only if the email service provider's server supports SSL or TLS)
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Username
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | string; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sender's email account's login user name
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Password
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | string; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sender's email account's login password
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Sender's email address
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | email; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The email address of the sender, i.e., the report message will be sent from this email. Make sure this is the same email that you provided login information to
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Recipient's email address
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | email; Default: " "
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The intended recipient's email address. To add more than one email address, click the green [[Image:Services sms gateway auto reply plus symbol.PNG]] plus symbol located to the right of this field
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Interval between reports
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Week {{!}} Month {{!}} Year; Default: '''Week'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies how often the reports should be sent
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Weekday {{!}} Month day
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | weekday {{!}} month day; Default: '''Sunday'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies the day of the month/week when the logging should take place. This field changes in accordance with '''Interval between reports'''
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Hour
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | integer [1..24]; Default: '''1'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies on the hour of the day when the logging should take place
|-
|}

Latest revision as of 09:38, 10 December 2020

Main Page > EOL Products > RUT230 > RUT230 Manual > RUT230 WebUI > RUT230 Status section > RUT230 Events Log

The information in this page is updated in accordance with the RUT2XX_R_00.01.14.1 firmware version.

Summary

In the Events Log window you can view records of events such as logins, reboots, resets, connections, configuration changes and more.

All Events

In this section you can view all occurred events.

System Events

In this section you can view all system events at once or filter it by choosing a type of events you want to see.

Network Events

In this section you can view all network events at once or filter it by choosing a type of events you want to see.

Events Reporting

The Events Reporting section gives you the ability to configure rules that will inform you via SMS or email when certain events occur on your router. These events can be almost anything – configuration changes, reboots, new connections, various status updates, etc.



Events Reporting Configuration

Events Reporting Configuration is used to create and customize Events Reporting Rules. Here you can specify any event type and subtype, chose whether you want to be informed by an SMS message or email, modify what kind of information you want receive should an event occur. To open this window, choose an Event type, Event subtype and Action and click the Add button. A new rule should appear in the Events Reporting Rules tab. Click the Edit button located next to that rule after which you will be redirected to that rule's configuration window.

Send SMS

FIELD NAME VALUE DESCRIPTION
Enable yes | no; Default: no Toggles the rule ON or OFF
Event type Config change | New DHCP client | Reboot | SSH | WebUI | New WiFi client | LAN port state | WAN Failover | Mobile data | SMS | Signal Strength;

Default: Config change

The type of event that you wish to receive information about
Event subtype Sample: After unexpected shut down Specified event's sub-type. This field changes in accordance with Event type
Action Send SMS | Send email; Default: Send SMS Action that is to be taken after the specified event occurs
Enable delivery retry yes | no; Default: yes Toggles delivery retry On or OFF. If for some reason the message delivery is unsuccessful, the router initiates a retry if this field is enabled
Retry interval 1 min. | 5 min. | 10 min. | 15 min. | 30 min. | 60 min.; Default 5 min. Specifies when the router should try re-sending the message in case the first attempt was a failure
Retry count 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10; Default: 2 Specifies the maximum number of failed attempts after which the router does not try to send the message anymore
Message text on Event string; Default: Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts; Specifies the text that the message will contain
Get status after reboot yes | no; Default: no Specifies whether the router should send an SMS message indicating the router's status after the reboot in addition to the original message
Status message after reboot string; Default: Router name - %rn; WAN IP - %wi; Data Connection state - %cs; Connection type - %ct; Signal strength - %ss; New FW available - %fs; Specifies the text that the status message will contain. This field becomes visible only if Get status after reboot is checked
Recipients Single number | User group; Default: Single number Specifies the intended recipients. A guide on how to create a User group can be found in the SMS Utilities chapter, User Groups section
Recipient's phone number phone number; Default: none The intended recipient's phone number. To add more than one number, click the green plus symbol located to the right of this field. The phone number must be entered in the international format, but without dash symbols or spaces, e.g., +37061234567

Send Email

FIELD NAME VALUE DESCRIPTION
Enable yes | no; Default: no Toggles the rule ON or OFF
Event type Config change | New DHCP client | Reboot | SSH | WebUI | New WiFi client | LAN port state | WAN Failover | Mobile data | SMS | Signal Strength;

Default: Config change

The type of event that you wish to receive information about
Event subtype Sample: After unexpected shut down Specified event's sub-type. This field changes in accordance with Event type
Action Send SMS | Send email; Default: Send SMS Action that is to be taken after the specified event occurs
Enable delivery retry yes | no; Default: yes Toggles delivery retry On or OFF. If for some reason the message delivery is unsuccessful, the router initiates a retry if this field is enabled
Retry interval 1 min. | 5 min. | 10 min. | 15 min. | 30 min. | 60 min.; Default 5 min. Specifies when the router should try re-sending the message in case the first attempt was a failure
Retry count 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10; Default: 2 Specifies the maximum number of failed attempts after which the router does not try to send the message anymore
Subject string; Default: none;

Character limit: 26

Specifies the subject of the email message
Message text on Event string; Default: Router name - %rn; Event type - %et; Event text - %ex; Time stamp - %ts; Specifies the text that the message will contain
Get status after reboot yes | no; Default: no Specifies whether the router should send an SMS message indicating the router's status after the reboot in addition to the original message. If this is checked you will be prompted to enter the text that the status message should contain
SMTP server ip | host; Default: none Sender's email service provider's SMTP server. If you don't know the SMTP server's address, you can easily look it up online since it is public information
SMTP port integer [0..65535]; Default: none Sender's email service provider's SMTP port. If you don't know the SMTP server's port, you can easily look it up online since it is public information
Secure connection yes | no; Default: no Toggles secure connection feature ON or OFF (use only if the email service provider's server supports SSL or TLS)
Username string; Default: none Sender's email account's login user name
Password string; Default: none Sender's email account's login password
Sender's email address email; Default: none The email address of the sender, i.e., the report message will be sent from this email. Make sure this is the same email that you provided login information to
Recipient's email address email; Default: none The intended recipient's email address. To add more than one email address, click the green plus symbol located to the right of this field
Send test mail - Sends a test mail using the information that you provided. Once you click this button, the router will login to the provided email account and send the specified message to the specified address(-es). You should always send a test mail before finishing the configuration to make sure that everything is in order

Event Types and Sub-types

The examples provided above are both concerning the Reboot Event type and After unexpected shut down sub-type. This section is an overview of all other Event type and sub-types.

Config change
ENEBT SUB-TYPE DESCRIPTION
All Sends a report message when any type of configuration changes are applied
OpenVPN Sends a report message when any OpenVPN configuration changes are applied. For example, whenever a new OpenVPN instance is created, an OpenVPN instance gets disabled/enabled, an OpenVPN instance's protocol is changed from UDP to TCP or vice versa, etc.
SMS Sends a report message when any SMS related configuration changes are applied. For example, whenever a new SMS Utilities rule is created or changed, changes are made to Auto Reply or Remote configurations, etc.
Mobile traffic Sends a report message when Mobile Traffic Logging is enabled/disabled or logging interval is changed.
Multiwan Sends a report message when changes to WAN Backup configuration are applied. For example, whenever a switch from using Wired as main WAN to backup WAN occurs, Wireless is added as a Backup WAN, Health monitor configurations are changed, etc.
Mobile Sends a report message when any RUT230_Mobile configuration changes are applied. For example, whenever Service mode, APN, Connection type is changed, etc.
Data limit Sends a report message when any Mobile Data Limit configuration changes are applied. For example, whenever new data limit is configured, data limit gets disabled/enabled on SIM1/SIM2, data limit period is changed, etc.
Events reporting Sends a report message when any configuration changes to Events Reporting are applied. For example, whenever a new Events Reporting Rule is created, changed, deleted, etc.
Periodic reboot Sends a report message when any configuration changes to Periodic Reboot are applied. For example, whenever Periodic Reboot gets enabled/disabled, Periodic Reboot interval is changed, etc.
GRE Tunnel Sends a report message when any configuration changes to GRE Tunnel are applied. For example, whenever a new GRE Tunnel instance is created, deleted, enabled/disabled, Local tunnel IP is changed, etc.
Ping reboot Sends a report message when any configuration changes to Ping Reboot are applied. For example, whenever Ping Reboot gets enabled/disabled, host to ping has changed, etc.
Auto update Sends a report message when any configuration changes to Auto update are applied
Site blocking Sends a report message when any configuration changes to Site Blocking are applied. For example, whenever Whitelist is changed to Blacklist or vice versa, a new entry is added to Blacklist/Whitelist, etc.
PPTP Sends a report message when any configuration changes to PPTP are applied. For example, whenever a new PPTP instance was created, deleted, enabled/disabled, PPTP server address was changed, etc.
Hotspot Sends a report message when any configuration changes to Hotspot are applied. For example, whenever Hotspot SSID was changed, Radius server was changed, Hotspot was enabled/disabled, etc.
Input/Output Sends a report message when any configuration changes to Input/Output are applied. For example, whenever a new Periodic Output Control Rule was created, changed, deleted, an output was turn ON/OFF, etc.
Content blocker Sends a report message when any configuration changes to Proxy Based Content Blocker are applied. For example, whenever Whitelist is changed to Blacklist or vice versa, a new entry is added to Blacklist/Whitelist, etc.
Login page Sends a report message when any Language Settings are changed
Language Sends a report message when any Language Settings are changed
Profile Sends a report message when a new Profile is added or deleted
DDNS Sends a report message when any configuration changes to Dynamic DNS are applied. For example, whenever a new DDNS instance is created, changed, deleted or edited
IPsec Sends a report message when any configuration changes to IPsec are applied. For example, a new IPsec instance is created, changed, deleted, etc.
Access control Sends a report message when any configuration changes to Access Control are applied. For example, SSH/HTTP/HTTPS remote or local access is enabled/disabled, changes are made to SSH or WebUI Access Secure, etc.
DHCP Sends a report message when any configuration changes to DHCP are applied. For example, whenever DHCP Server is enabled/disabled, DHCP address range is changed
VRRP Sends a report message when any configuration changes to VRRP are applied. For example, whenever VRRP is enabled/disabled, VRRP IP address is changed, etc.
SSH Sends a report message when any configuration changes to SSH are applied
Network Sends a report message when any Network related configuration changes are applied. For example, whenever Main WAN is changed, LAN IP address is changed, a WiFi Access Point is enabled/disabled, etc.
Wireless Sends a report message when any configuration changes to Wireless are applied. For example, a new Wi-Fi Access point is created, deleted, enabled/disabled, SSID is changed, etc.
Firewall Sends a report message when any configuration changes to Firewall are applied. For example, a new Traffic rule is added, a new SNAT rule is added, a rule is disabled/enabled, etc.
NTP Sends a report message when any configuration changes to NTP are applied. For example, whenever NTP is enabled/disabled, Time zone is changed, etc.
L2TP Sends a report message when any configuration changes to L2TP are applied. For example, whenever a new L2TP instance was created, changed, deleted, etc.
Other Sends a report message when any configuration changes other than the ones provided above are applied
New DHCP client
EVENT SUB-TYPE DESCRIPTION
All Sends a report message when a new devices is connected to the router either via LAN or Wi-Fi
Connected from WiFi Sends a report message when a new device is connected to the router via Wi-Fi
Connected from LAN Sends a report message when a new device is connected to the router via LAN port
Mobile Data
EVENT SUB-TYPE DESCRIPTION
All Sends a report message when mobile data connection status changes (from Connected to Disconnected or vice versa)
Connected Sends a report message when mobile data connection is achieved
Disconnected Sends a report message when mobile data connection is lost
SMS
EVENT SUB-TYPE DESCRIPTION
SMS received Sends a report message when the router receives a new SMS message
Signal Strength
EVENT SUB-TYPE DESCRIPTION
All Sends a report message when the router's RSSI value leaves any one of the below specified ranges
-121 dBm -113 dBm Sends a report message when the router's RSSI value leaves the -121 dBm to -113 dBm range
-113 dBm -98 dBm Sends a report message when the router's RSSI value leaves the -113 dBm to -98 dBm range
-98 dBm -93 dBm Sends a report message when the router's RSSI value leaves the -98 dBm to -93 dBm range
-93 dBm -75 dBm Sends a report message when the router's RSSI value leaves the -93 dBm to -75 dBm range
-75 dBm -60 dBm Sends a report message when the router's RSSI value leaves the -75 dBm to -60 dBm range
-60 dBm -50 dBm Sends a report message when the router's RSSI value leaves the -60 dBm to -50 dBm range
Reboot
EVENT SUB-TYPE DESCRIPTION
All Sends a report message when the router starts up after any type of reboot (except factory reset)
After unexpected shutdown Sends a report message when the router shuts down unexpectedly and starts back up again
After FW upgrade Sends a report message when the router initiates a Firmware upgrade (either from an uploaded FW file or from server)
From WebUI Sends a report message when the router starts up after a reboot command is initiated from the router's WebUI Administration->Reboot section
From SMS Sends a report message when the router starts up after a reboot command is initiated via SMS
From Input/Output Sends a report message when the router starts up after a reboot command is initiated via Input/Output
From ping reboot Sends a report message when the router starts up after a reboot command is initiated by the Ping Reboot function
From periodic reboot Sends a report message when the router starts up after a reboot command is initiated by the Periodic Reboot function
From button Sends a report message when the router starts up after being restarted by the press of the physical button located on the router
SSH
EVENT SUB-TYPE DESCRIPTION
All Sends a report message when someone connects to the router via SSH (either successfully or unsuccessfully)
Successful authentication Sends a report message when someone successfully connects to the router via SSH
Unsuccessful authentication Sends a report message when someone unsuccessfully tries to connect to the router via SSH
WebUI
EVENT SUB-TYPE DESCRIPTION
All Sends a report message when someone connects to the router via HTTP or HTTPS (either successfully or unsuccessfully)
Successful authentication Sends a report message when someone successfully connects to the router via HTTP or HTTPS
Unsuccessful authentication Sends a report message when someone unsuccessfully tries to connect to the router via HTTP or HTTPS
New WiFi client
EVENT SUB-TYPE DESCRIPTION
All Sends a report message when a device connects to or disconnects from the router's WLAN (Wireless Network or Wireless LAN)
Connected Sends a report message when a device connects to the router's WLAN
Disconnected Sends a report message when a device disconnects from the router's WLAN
LAN Port State
EVENT SUB-TYPE DESCRIPTION
All Sends a report message when a device is either plugged in or unplugged from one of the router's LAN ports
Unplugged Sends a report message when a device is unplugged from one of the router's LAN ports
Plugged in Sends a report message when a device is plugged into one of the router's LAN ports
WAN Failover
EVENT SUB-TYPE DESCRIPTION
All Sends a report message when the router switches from using the Main WAN to using the Failover WAN and vice versa
Switched to main Sends a report message when the router switches from using the Main WAN to using the Failover WAN
Switched to failover Sends a report message when the router stops using the Failover WAN and start using the Main WAN

Reporting Configuration

The Reporting Configuration section lets you create rules that transfer logs to email or FTP.


Events Log Report Configuration

Events Log Report Configuration provides you with the ability to change the configuration of periodic events reporting to email or FTP. You can access it by creating a rule and clicking the Edit button next to it, just like Event Reporting Configuration.

FTP

FIELD NAME VALUE DESCRIPTION
Enable yes | no; Default: no Toggles the log file report rule ON or OFF
Events log System | Network | All; Default: System Specifies which log to transfer
Transfer type Email | FTP; Default: Email Specifies whether to transfer the log(s) to FTP or Email
Compress file yes | no; Default: no Compress events log file using gzip
Host host | ip; Default none FTP server's IP address or hostname
User name string; Default: none Login user name used for authentication to the FTP server
Password string; Default: none Login password used for authentication to the FTP
Interval between reports Week | Month | Year; Default: Week Specifies how often the reports should be sent
Weekday | Month day weekday | month day; Default: Sunday Specifies the day of the month/week when the logging should take place. This field changes in accordance with Interval between reports
Hour integer [1..24]; Default: 1 Specifies on the hour of the day when the logging should take place

Email

FIELD NAME VALUE DESCRIPTION
Enable yes | no; Default: no Toggles the log file report rule ON or OFF
Events log System | Network | All; Default: System Specifies which log to transfer
Transfer type Email | FTP; Default: Email Specifies whether to transfer the log(s) to FTP or Email
Compress file yes | no; Default: no Compress events log file using gzip
Subject string; Default: none Specifies the subject of the email log message
Message string; Default: none The text contained in the log email. This has nothing to do with the log itself, which will be sent as an attached file
SMTP server ip | host; Default: none Sender's email service provider's SMTP server. If you don't know the SMTP server's address, you can easily look it up online since it is public information
SMTP server port integer [0..65535]; Default: none Sender's email service provider's SMTP server. If you don't know the SMTP server's address, you can easily look it up online since it is public information
Secure connection yes | no; Default: no Toggles secure connection feature ON or OFF (use only if the email service provider's server supports SSL or TLS)
Username string; Default: none Sender's email account's login user name
Password string; Default: none Sender's email account's login password
Sender's email address email; Default: none The email address of the sender, i.e., the report message will be sent from this email. Make sure this is the same email that you provided login information to
Recipient's email address email; Default: none The intended recipient's email address. To add more than one email address, click the green plus symbol located to the right of this field
Interval between reports Week | Month | Year; Default: Week Specifies how often the reports should be sent
Weekday | Month day weekday | month day; Default: Sunday Specifies the day of the month/week when the logging should take place. This field changes in accordance with Interval between reports
Hour integer [1..24]; Default: 1 Specifies on the hour of the day when the logging should take place
Retrieved from "https://wiki.teltonika-networks.com/index.php?title=RUT230_Events_Log&oldid=76202"