About alarms

You can set alarms in the Administration > System Settings: Alarms page. Enabling alarms is optional.

The system’s hierarchical alarms group certain alarms into top-level categories, such as the SSL Settings alarm. When an alarm triggers, its parent expands to provide more information. As an example, the Disk Full top-level parent alarm aggregates over multiple partitions. If a specific partition is full, the Disk Full parent alarm triggers and the Alarm Status report displays more information regarding which partition caused the alarm to trigger.

When an alarm reaches the rising threshold, it is activated; when it reaches the lowest or reset threshold, it is reset. After an alarm is triggered, it is not triggered again until it has fallen below the reset threshold. Notice that CPU Utilization settings are percentage thresholds, while endpoint-related alarm settings are number counts.

Disabling a parent alarm disables its children. You can enable a parent alarm and disable any of its child alarms. You can’t enable a child alarm without first enabling its parent.

The children alarms of a disabled parent appear on the Alarms Status report with a suppressed status. Disabled children alarms of an enabled parent appear on the Alarm Status report with a disabled status. For more details on alarm status, see Viewing Alarm Status reports.

This alarm indicates a configuration error.

Enables an alarm and sends an email notification if the average and peak threshold for the CPU utilization is exceeded. By default, this alarm is enabled with a rising threshold of 90 percent and a reset threshold of 70 percent.

• Rising Threshold—The alarm is triggered when CPU utilization reaches the rising threshold.

• Reset Threshold—The alarm is cleared and reset when CPU utilization reaches, or falls below, the reset threshold.

Enables an alarm if the system partitions (not the service data store) are full or almost full. For example, Client Accelerator Controller monitors the available space on /var, which is used to hold logs, statistics, system dumps, TCP dumps, and so on. By default, this alarm is enabled. This alarm monitors these system partitions:

Indicates whether the number of endpoint clients with data store errors has reached the rising threshold. By default, this alarm is enabled with a rising threshold of 50 and a reset threshold of 40.

Indicates whether the number of endpoint clients with File System Full errors has reached the rising threshold. By default, this alarm is enabled with a rising threshold of 50 and a reset threshold of 40.

Indicates whether the number of endpoint clients with Endpoint genID errors has reached the rising threshold. By default, this alarm is enabled with a rising threshold of 50 and a reset threshold of 40.

Indicates whether the number of endpoint clients with NFS errors has reached the rising threshold. By default, this alarm is enabled with a rising threshold of 50 and a reset threshold of 40.

Indicates whether the number of endpoint clients with service errors has reached the rising threshold. By default, this alarm is enabled with a rising threshold of 50 and a reset threshold of 40.

Indicates whether the number of endpoint clients with SSL errors has reached the rising threshold. By default, this alarm is enabled with a rising threshold of 50 and a reset count of 40.

Indicates whether the number of endpoint clients in your network with mismatches between software versions has reached the rising threshold. If a software mismatch is detected, resolve the mismatch by upgrading or reverting to a previous version of the software. By default, this alarm is enabled with a rising threshold of 50 and a reset threshold of 40.

Indicates whether to send an alarm when all the licenses have been used. Alarm triggers for only desktop licenses. The alarm triggers upon reaching the rising threshold. The default rising threshold value is 100%. The alarm resets upon reaching or dropping below the reset threshold. The default reset threshold value is 99%.

Enables an alarm and sends an email notification if a license is removed, is about to expire, has expired, or is invalid. This alarm also triggers if there is no license installed. By default, this alarm is enabled. When enabled, you can enable any of these children alarms:

• Autolicense Critical Event—This alarm triggers when the Riverbed Licensing Portal can’t respond to a license request with valid licenses.

• Autolicense Informational Event—This alarm triggers if the Riverbed Licensing Portal has information regarding the licenses. For example, this alarm displays when the portal provides a license that is associated with a token previously used on a different controller.

• Licenses Expired—This alarm triggers if one or more features have at least one license installed, but all of them are expired.

• Licenses Expiring—This alarm triggers if the license for one or more features is going to expire within two weeks.

• Licensing—This alarm triggers if there is no license installed. The licenses expiring and licenses expired alarms are triggered per feature. For example, if you install two license keys for a feature, LK1-FOO-xxx (expired) and LK1‑FOO-yyy (not expired), the alarms don’t trigger, because the feature has one valid license.

Enables an alarm and sends an email notification when an interface was not configured for half-duplex negotiation but has negotiated half-duplex mode. The alarm indicates which interface is triggering the duplex alarm. By default, this alarm is enabled. When enabled, you can enable any of these children alarms:

Enables an alarm and sends an email notification when the error rate on an interface exceeds 0.1 percent while either sending or receiving packets. This threshold is based on the observation that even a small link error rate reduces TCP throughput significantly. A properly configured LAN connection experiences very few errors. The alarm clears when the rate drops below 0.05 percent. By default, this alarm is disabled. When enabled, you can enable any of these children alarms:

• Interface aux Link Error—This alarm triggers if an Ethernet link is lost with the aux interface.

• Interface primary Link Error—This alarm triggers if an Ethernet link is lost with the primary interface.

This error condition is often caused by surrounding devices, like routers or switches that are transitioning between interfaces. System restarts also trigger this alarm.

Enables an alarm and sends an email notification if an Ethernet link is inoperable due to a network event. Depending on which link is inoperable, the system might no longer be optimizing and a network outage could occur. By default, this alarm is disabled. When enabled, you can enable any of these children alarms:

• Interface aux Down—This alarm triggers if an Ethernet link is inoperable on the aux interface.

• Interface primary Down—This alarm triggers if an Ethernet link is inoperable on the primary interface.

Enables an alarm and sends an email notification if memory paging is detected. If 100 pages are swapped every couple of hours, the system is functioning properly. If thousands of pages are swapped every few minutes, contact Support at https://support.riverbed.com. By default, this alarm is disabled.

Enables an alarm and sends an email notification if the system detects an error while trying to create a process dump. This alarm indicates an abnormal condition in which the Client Accelerator Controller can’t collect the core file after three retries. It can be caused when the /var directory is reaching capacity or other conditions. When the alarm is raised, the directory is blacklisted. By default, this alarm is enabled.

Enables an alarm and sends an email notification if the system encounters a problem with the secure vault. By default, this alarm is enabled. When enabled, you can enable this child alarm:

• Secure Vault Locked—Indicates that the secure vault is locked. To optimize SSL connections or to use Client Accelerator data store encryption, the secure vault must be unlocked. Choose Administration > Security: Secure Vault and unlock the secure vault.

Enables an alarm if an error is detected in your SSL configuration. By default, this alarm is enabled. When enabled, you can enable these children alarms:

• SSL Certificates—Indicates that an SSL peering certificate has failed to reenroll automatically within the Simple Certificate Enrollment Protocol (SCEP) polling interval.

• SSL Signing Certificate Validity—Indicates that an SSL peering certificate has failed to reenroll automatically within the Simple Certificate Enrollment Protocol (SCEP) polling interval.

Memory, data storage, or CPU resources are insufficient for the maximum number of endpoints.

Enables an alarm to be triggered if the hardware platform does not support Client Accelerator Controller-v. By default, this alarm is enabled.

Enables an alarm to be triggered if the virtual machine is unavailable. By default, this alarm is enabled.