Notifications
The Notifications menu provides five options:
- ARMT Only Alerts: Displays alerts generated for the ARMT Only delivery method.
- Email Alerts: Displays alerts generated for the Email delivery methods.
- Ticketing Alerts: Displays alerts generated for the AOTS delivery method.
- Profiles: A user interface for managing notification profiles.
- Subscriptions: A user interface for managing notification subscriptions.
ARMT Only, Email, and Ticketing Alerts
The ARMT Only Alerts, Email Alerts, and Ticketing Alerts pages are a convenient way to look back at alerts that were sent to you, in case you deleted the email or need to have an extra record of it. The information column summarizes the content of the alert for quick reference. You can filter for similar events and go back as far as 30 days if you need to look for a record of something older. If you want to get to the device quickly you can do so by selecting the MAC address. The ARMT Only Alerts, Email Alerts, and Ticketing Alerts pages are the same, except that for the Ticketing Alerts page, the alerts come from the AoTS Ticketing system.
- Resource: The Device, Data Plan, or Organization that generated the alert.
- Category: The Device Category (if applicable.)
- Model: The Device Model (if applicable.)
- Organization: The organization that the device or data plan belongs to.
- Site: The Site of a device (if applicable.)
- Profile: The Notification Profile that generated the alert.
- Type: The type of notification.
- Level: The level of urgency associated with the notification, as defined in RFC5424.
- Information: Additional information about the alert.
- Delivered At: When the notification was sent to the user.
- Created At: When the notification was created.
Profiles
The Profiles page display the existing profiles for your organization/account and allows you to Edit, Copy, and Delete existing profiles, and add new profiles.
To add a new profile, click Add.
Specify the Owner, Name, and Delivery Method, and click Next.
Specify the Frequency and Recipients and click Next.
Specify the Publisher Type and the Publisher and click Next.
Specify the types of Notifications and click Create Profile.
The following sections list each notification and what it is triggered by.
VPN Gateway notifications
- Device up: The VPN Gateway device is probed once every 15 minutes and has responded successfully to the probe.
- Device down: The VPN Gateway device is probed once every 15 minutes. If the ARMT tool misses two consecutive probes and also has not received any SNMP informs within the past 30 minutes, the device will be marked as down (red status) and this notification will be sent. The time specifying when a VPN Gateway device is considered down cannot be adjusted.
- Device firmware changed: The VPN Gateway device is running on a different firmware version from the last time the device was probed.
- Device rebooted: The VPN Gateway device sent an SNMP inform that it was rebooted.
- Device primary IP changed: The VPN Gateway device's current WAN IP address has changed.
- Device unreachable: ARMT cannot reach the device.
- Backup WAN autotest failed: The VPN Gateway device sent an SNMP inform that its scheduled autotest has failed on either the WAN2 or cellular interface.
- Tunnel disconnected: The VPN Gateway tunnel has disconnected.
- Tunnel established: The VPN Gateway tunnel has been established.
- Device WAN interface changed: The VPN Gateway device sent a syslog stating that it has switched to a new WAN interface.
- Backup WAN threshold reached: The VPN Gateway device sent an SNMP inform that it has been connected with either the WAN2 or Cellular interface longer than the threshold time. The VPN Gateway device will continue to use the backup connection if this inform is sent; the inform is meant to be a warning that the VPN Gateway device has been in backup mode for an extended period of time. To enable this SNMP inform, enable the Dial Backup Threshold option in the Service Manager profile for the VPN Gateway.
- Device cellular location changed: The cellular location details reported by the VPN Gateway device changed. For more details about determining the cellular location of a VPN Gateway device, refer to the Devices section.
- Device signal strength fell below nominal threshold: The cellular signal strength reported by the VPN Gateway device has dropped below a specified threshold percentage. This threshold is defined by an ARMT admin in the Admin panel of the site.
- Device cellular network type changed: The SNMP probe response from the VPN Gateway device indicated that the cellular network (4G LTE, 3G HSPA+, etc.) type that it is connected on has changed.
- Ping test succeeded: The VPN Gateway device sent an SNMP inform that it successfully pinged an IP address specified in its Service Manager profile. The VPN Gateway must be running version 6.2 or higher to have ping tests enabled.
- Ping test failed: The VPN Gateway device sent an SNMP inform that it failed to ping an IP address specified in its Service Manager profile. The VPN Gateway must be running version 6.2 or higher to have ping tests enabled.
- VRRP state changed: The VPN Gateway device sent an SNMP inform that its VRRP state changed. Note that VRRP must be enabled in the VPN Gateway's Service Manager profile to receive this inform.
- OOB Cable(s) Missing: The VPN Gateway notified ARMT that its Out-of-Band cable is missing.
- OOB Cable(s) All Present: The VPN Gateway notified ARMT that its Out-of-Band cable is present.
- Rogue mac detected: A device with a rouge MAC address was detected.
- Rouge mac no file: A device with no record of logging in detected.
- IP Connection Tracking Table Full: The device sent an SNMP inform that its connection tracking table is full.
Cellular notifications
- Device recovered: This notification is generated whenever the cellular device is considered down (red status) and the device checks back in to the ARMT monitor by sending a syslog or if the device is reachable through remote control commands. This notification will trigger the device to show as up (green status) in ARMT.
- Device down: The cellular device sends a heartbeat syslog once every 30 minutes. If ARMT has not received any syslogs within the past 139 minutes (2 hours 19 minutes), the device will be marked as down (red status) and a notification will be sent. The time specifying when a cellular device is considered down can be adjusted by changing the configuration of the device. See Adjusting when a Cellular Device is considered Down by ARMT.
- Device firmware changed: The cellular device is running on a different firmware version from the last firmware version the device logged.
- Device primary IP changed: The embedded cellular device sent a syslog stating that the IP address it received from the cellular network has changed.
- Device unreachable: The device could not be contacted.
- Device cellular network type changed: The cellular device sent a syslog stating that the cellular network (4G LTE, 3G HSPA+, etc.) type that it is connected on has changed.
- Device WAN interface changed: The cellular device sent a syslog stating that it has switched to a new WAN interface.
- Device signal strength fell below nominal threshold: The cellular signal strength reported by the cellular device has dropped below a specified threshold percentage. This threshold is defined by an ARMT admin in the Admin panel of the site.
- Device rebooted: The cellular device sent an SNMP inform that it was rebooted.
- Device cellular location changed: The cellular location details reported by the cellular device changed. See Devices for more details about determining the cellular location of a cellular device.
- Device ethernet port connected: The cellular device sent a syslog stating that a client device was connected to its Ethernet port and it has physical Ethernet connectivity to that device.
- Device Ethernet port disconnected: The cellular device sent a syslog stating that it lost physical connectivity to a client device that was previously connected via Ethernet to the Remote Manager.