alarm enable (Core)

• appliance_unlicensed—This alarm triggers if the appliance has no BASE or MSPEC license installed for its currently configured model. This alarm also triggers for hardware earlier than xx60 with no BASE licensing installed.

• autolicense_error—This alarm triggers on an appliance when the Riverbed Licensing Portal cannot respond to a license request with valid licenses.

• autolicense_info—This alarm triggers if the Riverbed Licensing Portal has information regarding licenses for a Core.

• bkup_int—This alarm triggers if the backup integration module encounters an error.

• blkdisk—This alarm triggers and sends an email if the block-disk module encounters an error. By default, this alarm is enabled. This alarm applies only to Core implementations.

• config—This alarm sends an email notification if the Core configuration has been reverted to a previous version. By default, this alarm is enabled.

• coredr—This alarm is enabled by default and triggers if there are any disaster recovery errors or if there is a Degraded state in the disaster recovery configuration. There are several issues that can be reported:

– Journal LUN size—This alarm is triggered when the Journal LUN size is not large enough to allow creation of the required number of replicas. This alarm automatically clears when the new size of the Journal LUN is detected.

– WAN sync latency (replication performance)—This alarm is triggered if the backend on the secondary is having issues (slow IOPs or high latency), or if a large number of replicas (more than 10) are created at one time. This alarm also tracks the time it takes to commit writes to the secondary data center. This includes time to transmit the data, time to write the data on the secondary storage array, and time for a response.

– Replication state—This alarm is triggered if one or more replica LUNs are in Suspended state on the primary Core and are therefore not being replicated.

– Failover issue—This alarm is triggered when a disaster recovery failover has occurred, but not all Edges have failed over to the new primary data center.

– Split-brain—This message is triggered when a split-brain state is detected between the replication data centers. A split-brain is that both sites report they are primary and suspended.

– Data on FusionSync replica is corrupted—This alarm triggers when data mismatch is detected on any of the replica LUNs. This alarm is raised on the primary Core.

• cpu_util_indiv—This alarm indicates whether the system has reached the CPU threshold for any of the CPUs in the system. If the system has reached the CPU threshold, check your settings. If your alarm thresholds are correct, reboot the appliance.

• critical_temp—This alarm indicates that the CPU temperature has exceeded the critical threshold. The default value for the rising threshold temperature is 80°C; the default reset threshold temperature is 70°C.

• edge—This alarm indicates that Core has lost connection with one of its configured Edges.

• flash_error—This alarm indicates that the system has detected an error with the flash drive hardware. At times, the USB flash drive that holds the system images might become unresponsive; the appliance continues to function normally. When this error triggers you cannot perform a software upgrade, as the appliance is unable to write a new upgrade image to the flash drive without first power cycling the system. To reboot the appliance, enter the command to automatically power cycle the Core and restore the flash drive to its proper function.

• fs_mnt—This alarm indicates that one of the mounted partitions is full or almost full. The alarm is triggered when only 7% of free space is remaining.

• link_duplex—This alarm is triggered when an interface was not configured for half-duplex negotiation but has negotiated half-duplex mode. Half-duplex significantly limits the optimization service results. This alarm is enabled by default.

• link_io_errors—This alarm is triggered when the link error rate exceeds 0.1% 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 should experience very few errors. The alarm clears when the rate drops below 0.05%. This alarm is enabled by default. You can change the default alarm thresholds by entering the alarm error-threshold command at the system prompt. You can enable or disable the alarm for a specific interface. For example, you can disable the alarm for a link after deciding to tolerate the errors.

• linkstate: <x>—These alarms indicate that the system has detected a link that is down. The system notifies you through SNMP traps, email, and alarm status. By default, this alarm is not enabled. The no alarm linkstate enable command disables the link state alarm.

• lun—This alarm indicates that the connection to the LUN failed or there is an issue with LUN resizing.

• memory_error—This alarm indicates that the system has detected a memory error.

• model_unlicensed—This alarm indicates that the model license has been removed or is expired.

• other_hardware_error—This alarm indicates that the system has detected a problem with the hardware. The alarm clears when you add the necessary hardware, remove the nonqualified hardware, or resolve other hardware issues. This issues triggers the hardware error alarm: “The Core does not have enough disk, memory, CPU cores, or NIC cards to support the current configuration.”

• paging—This alarm indicates whether the system has reached the memory paging threshold. If 100 pages are swapped approximately every two hours the appliance is functioning properly. If thousands of pages are swapped every few minutes, then reboot the system. If rebooting does not solve the problem, contact Riverbed Support.

• secure_vault—This alarm indicates a general secure vault error.

• secure_vault_unlocked—This alarm indicates whether the secure vault is unlocked. When the vault is unlocked, SSL traffic is not optimized and you cannot encrypt a data store.

• snapshot—This alarm indicates that a snapshot has failed to commit to the SAN, or a snapshot has failed to complete.

• ssl—This alarm indicates whether the system has detected an SSL error.

• sticky_staging_dir—This alarm indicates that the system has detected an error while trying to create a process dump.

• storage_status—This alarm indicates the overall storage health status.

• temperature—This alarm is the parent temperature alarm and triggers if any of the warning_temp or critical_temp alarms are active.

• upgrade—This alarm indicates the status of an upgrade.

• warning_temp—This alarm indicates whether the CPU temperature has exceeded the warning threshold. The default value for the rising threshold temperature is 80°C; the default reset threshold temperature is 70°C.

• vmaware_backup—This alarm triggers and sends an email for the following conditions:

• proxy connection failure—connection to the proxy server fails. This alarm clears when the connection is restored between the Core and proxy server.