There are a number of options available in the ReadyView dashboard for email alerts to be sent when certain network or device events occur. This article outlines which options are available for each product and provides additional considerations when using network alerts and organization-wide notifications throughout the dashboard.

Configuring Alerts

Network alerts can be configured in the dashboard under Admin > Settings > Notifications.

Network alerts can be configured by specifying the default recipients for all alerts or configuring recipients on a per-alert basis. There are two options to denote who will receive email alerts:

• Default recipient
  • These are the email addresses that will receive notifications for all alerts.
• Specific recipients
  • This allows a customer list of recipients, where email alerts are sent to all email addresses listed.

Alerts

Alerts can be triggered for the following ReadyLinks switch events:

• A device goes offline
  • This alert is triggered when a device is unreachable from the dashboard for 10 minutes. Note that the device may still be functioning, this only indicates that it is unable to contact the dashboard.
• A client is disconnected
  • This alert is triggered when a client device that was previously connected disconnects.
• A new client is connected
  • This alert is triggered when a new client device connects to the ReadyLinks switch. This event includes PHY rate information of the connection between the client and the ReadyLinks switch.
• A port state changes
  • This alert is triggered when the port state changes.
• CPU utilization is too high
  • This alert is triggered when the CPU utilization of a ReadyLinks switch exceeds the upper CPU threshold.
• Memory utilization is too high
  • This alert is triggered when the memory utilization of a ReadyLinks switch exceeds the upper memory threshold.
• Device is operating at a critical temperature
  • This alert is triggered when the junction temperature of a ReadyLinks switch falls outside of the operating temperature range.
• An SFP module is operating at a critical temperature
  • This alert is triggered when an SFP module is operating outside of its operating temperature range. Note that the SFP module must report its operating temperature range for this alert to trigger.
• ARP rate limit exceeded
  • This alert is triggered when ARP traffic exceeds the ARP rate limit set on the port.
• DHCP rate limit exceeded
  • This alert is triggered when DHCP traffic exceeds the DHCP rate limit set on the port.
• Loop detected
  • This alert is triggered when a network loop is detected on a port.

Syslog, API, and SNMP

Syslog, API, and SNMP each have their own benefits for network and device reporting. Below is a list comparing each option with their possible use-cases.

Spam Filters

All network alerts will be sourced from the same email address. To ensure that alerts are not being lost to a spam filter, please be sure to add [email protected] as a trusted email source.