Configuration Mode Commands : System Administration Commands : Alarm Commands : alarm enable
  
alarm enable
Enables the specified alarm.
Syntax
[no] alarm <type> enable
Parameters
<type>
•  admission_conn - This alarm should not be disabled. It indicates that the system connection limit has been reached. Additional connections are passed through unoptimized. The alarm clears when the SteelHead moves out of this condition.
•  admission_control - This alarm should not be disabled. It indicates that the system admission control pressure limit has been reached. Additional connections are passed through unoptimized. This alarm clears when the SteelHead moves out of this condition.
•  admission_cpu - This alarm should not be disabled. This alarm is triggered by high CPU usage. Additional connections are passed through unoptimized. The alarm clears when the SteelHead moves out of this condition.
 
•  admission_mapi - This alarm should not be disabled. It indicates that the total number of MAPI optimized connections has exceeded the maximum admission control threshold.
•  admission_mem - This alarm should not be disabled. It indicates that the system connection memory limit has been reached. Additional connections are passed through unoptimized. The alarm clears when the SteelHead moves out of this condition.
•  admission_tcp - This alarm should not be disabled. This alarm is triggered by high TCP memory usage. Additional connections are passed through unoptimized. The alarm clears when the SteelHead moves out of this condition.
•  appliance_unlicensed - This alarm triggers if the SteelHead 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.
•  arcount - This alarm should not be disabled. It indicates whether the system is experiencing asymmetric traffic. If the system experiences asymmetric traffic, the system detects this condition and reports the failure. The traffic is passed through, and the route appears in the Asymmetric Routing table.
•  autolicense_error - This alarm triggers on a SteelHead-v 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 SteelHead-v appliance.
•  bypass - This alarm should not be disabled. It indicates that the system is in bypass mode. If the SteelHead is in bypass mode, restart the SteelHead service.
•  certs_expiring - This alarm indicates that the system has expiring SSL certificates.
•  cf_ack_timeout_aggr - This alarm indicates that the connection has been lost because requests have not been acknowledged by a connection-forwarding neighbor within the set threshold.
•  cf_conn_failure_aggr - This alarm indicates that the connection cannot be established with a connection-forwarding neighbor.
•  cf_conn_lost_eos_aggr - This alarm indicates that the connection has been closed by the connection-forwarding neighbor.
•  cf_conn_lost_err_aggr - This alarm indicates that the connection has been lost with the connection-forwarding neighbor due to an error.
 
•  cf_keepalive_timeout_aggr - This alarm indicates that the connection forwarding neighbor has not sent a keep-alive message within the time-out period to the neighbor SteelHead(s) indicating that the connection has been lost.
•  cf_latency_exceeded_aggr - This alarm indicates that the amount of latency between connection-forwarding neighbors has exceeded the specified threshold.
•  cf_neighbor_incompatible_cluster - This alarm sends an email notification if a connection-forwarding neighbor is running a RiOS version that is incompatible with IPv6, or if the IP address configuration between neighbors does not match, or if path selection is enabled locally and the neighbor does not have path selection enabled. The SteelHead neighbors pass through IPv6 connections when this alarm triggers.
•  cf_read_info_timeout_aggr - This alarm indicates that the SteelHead has timed out while waiting for an initialization message from the connection-forwarding neighbor.
<type> (cont)
•  connection_forwarding - This alarm is the connection forwarding parent alarm.
•  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 SteelHead
•  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.
•  crl_error: SSL_CAs - Indicates that an SSL peering certificate has failed to reenroll automatically within the Simple Certificate Enrollment Protocol (SCEP) polling interval.
•  crl_error: SSL_Peering_CAs - Indicates that an SSL peering certificate has failed to reenroll automatically within the Simple Certificate Enrollment Protocol (SCEP) polling interval.
•  datastore - This alarm indicates the overall data store health.
•  datastore_clean_needed - This alarm indicates that you need to clear the RiOS data store.
•  datastore_error - This alarm indicates that the data store is corrupt or has become incompatible with the current configuration. Clear the data store to clear the alarm. If the alarm was caused by an unintended change to the configuration, you can change the configuration to match the previous RiOS data store settings. Then restart the optimization service without clearing the RiOS data store to reset the alarm. Typical configuration changes that require a restart with a clear RiOS data store are enabling the Extended Peer Table or changing the data store encryption.
•  datastore_sync_error - This alarm indicates that the system has detected a problem with the synchronized data.
•  disconnected_sh_alert - This alarm indicates that the connection to a SteelHead appliance in a connection forwarding cluster is lost.
•  disk:<x>:status - These alarms indicate that the system has detected a problem with the specified disk or a solid-state drive.
•  domain_join_error - This alarm indicates that the system has encountered an error when attempting to join a domain.
•  duplex - This alarm indicates that the system has encountered a large number of packet errors in your network. Make sure that the speed and duplex settings on your system match the settings on your switch and router. By default, this alarm is enabled.
 
•  fan_error - This alarm indicates that the system has detected a fan error.
•  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 SteelHead continues to function normally. When this error triggers you cannot perform a software upgrade, as the SteelHead is unable to write a new upgrade image to the flash drive without first power cycling the system. To reboot the appliance, enter the reload command to automatically power cycle the SteelHead and restore the flash drive to its proper function. On desktop SteelHead appliance x50 and x55 models, you must physically power cycle the appliance (push the power button or pull the power cord).
•  flash_protection_failed - This alarm indicates that the USB flash drive has not been backed up because there is not enough available space in the /var filesystem directory.
•  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.
 
•  halt_error - This alarm cannot be disabled. It indicates that the system has detected an unexpected halt to the optimization service.
•  hardware - This alarm indicates the overall health of the hardware.
•  inbound_qos_wan_bw_err - Enables an alarm and sends an email notification if the inbound QoS WAN bandwidth for one or more of the interfaces is set incorrectly. You must configure the WAN bandwidth to be less than or equal to the interface bandwidth link rate.
•  ipmi - This alarm indicates that the system has detected an Intelligent Platform Management (IPMI) event. This alarm is not supported on all appliance models.
<type> (cont)
•  licensing - This alarm is the parent licensing alarm and triggers if any of the license_expired, license_expiring, or appliance_unlicensed alarms are active.
•  license_expired - This alarm triggers if any feature has at least one license installed, but all of them are expired.
•  license_expiring - This alarm triggers if one or more features is going to expire within two weeks.
Note: The license expiring and license expired alarms are triggered per feature. For example, if you install two license keys for a feature, LK1-FOOxxx (expired) and LK1-FOO-yyy (not expired), the alarms do not trigger, because the feature has one valid license.
•  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.
•  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.
 
•  memory_error - This alarm indicates that the system has detected a memory error.
•  mismatch_peer_aggr - This alarm indicates that the appliance has encountered another appliance that is running an incompatible version of system software. Refer to the CLI, Management Console, or the SNMP peer table to determine which appliance is causing the conflict. Connections with that peer will not be optimized, connections with other peers running compatible RiOS versions are unaffected. To resolve the problem, upgrade your system software. No other action is required as the alarm clears automatically.
•  nfs_v2_v4 - This alarm indicates that the system has triggered a v2 or v4 NFS alarm.
•  non_443_ssl_servers_detected_on_upgrade - This alarm indicates that during a RiOS upgrade (for example, from 5.5 to 6.0), the system has detected a preexisting SSL server certificate configuration on a port other than the default SSL port 443. SSL traffic might not be optimized. To restore SSL optimization, you can either add a peering rule to the server-side SteelHead to intercept the connection and optimize the SSL traffic on the non-default SSL server port or you can add an in-path rule to the client-side SteelHead to intercept the connection and optimize the SSL traffic on the non-default SSL server port. After adding a peering or in-path rule, you must clear this alarm manually by issuing the following CLI command:
alarm non_443_ssl_servers_detected_on_upgrade clear
 
•  optimization_general - This alarm indicates that the optimization service is not operating normally. The service might not be running, it might be disabled, or it might have stopped optimizing.
•  optimization_service - This alarm indicates that the system has encountered an optimization service condition.
<type> (cont)
•  other_hardware_error - This alarm indicates that the system has detected a problem with the SteelHead hardware. The alarm clears when you add the necessary hardware, remove the nonqualified hardware, or resolve other hardware issues. The following issues trigger the hardware error alarm:
–  The SteelHead does not have enough disk, memory, CPU cores, or NIC cards to support the current configuration.
–  The SteelHead is using a dual in-line memory module (DIMM), a hard disk, or a NIC that is not qualified by Riverbed.
–  DIMMs are plugged into the SteelHead appliance but RiOS cannot recognize them because the DIMM modules are in the wrong slot. You must plug DIMM modules into the black slots first and then use the blue slots when all of the black slots are in use.
–  A DIMM module is broken and you must replace it.
–  Other hardware issues.
 
•  outbound_qos_wan_bw_err - Enables an alarm and sends an email notification if the outbound QoS WAN bandwidth for one or more of the interfaces is set incorrectly. You must configure the WAN bandwidth to be less than or equal to the interface bandwidth link rate.
•  paging - This alarm indicates whether the system has reached the memory paging threshold. If 100 pages are swapped approximately every two hours the SteelHead 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.
•  path_selection_path_down - This alarm indicates that one of the predefined uplinks for a connection is unavailable because it has exceeded either the timeout value for uplink latency or the threshold for observed packet loss.
•  path_selection_path_probe_err - This alarm indicates that a path selection monitoring probe for a predefined uplink has received a probe response from an unexpected relay or interface.
 
•  power_supply - This alarm indicates that an inserted power supply cord does not have power, as opposed to a power supply slot with no power supply cord inserted.
•  profile_switch_failed - This alarm indicates that an error has occurred while repartitioning the disk drives during a storage profile switch. A profile switch changes the disk space allocation on the drives, clears the SteelFusion and VSP data stores, and repartitions the data stores to the appropriate sizes. You switch a storage profile by using the disk-config layout command on an EX or EX+ SteelFusion SteelHead. By default, this alarm is enabled.
•  raid_disk_indiv - This alarm indicates that the system has encountered RAID errors (for example, missing drives, pulled drives, drive failures, and drive rebuilds). For drive rebuilds, if a drive is removed and then reinserted, the alarm continues to be triggered until the rebuild is complete. Rebuilding a disk drive can take 4-6 hours.
 
•  secure_transport_controller_unreachable - This alarm indicates a network connectivity failure to the Controller for the secure transport feature. Issues that might trigger this alarm are Controller services down because of an upgrade or a network connectivity failure to the Controller.
•  secure_transport_registration_failed - This alarm indicates that the peer SteelHead is not registered with the Controller and the Controller does not recognize it as a member of the secure transport group.
•  secure_vault - This alarm indicates a general secure vault error.
•  secure_vault_rekey_needed - This alarm indicates whether the system has detected that the secure vault needs to be rekeyed.
•  secure_vault_uninitialized - This alarm indicates that the system has detected that the secure vault is uninitialized.
•  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.
<type> (cont)
•  serial_cascade_misconfig - This alarm indicates that the system has encountered an error in reaching a neighbor appliance configured for connection forwarding.
•  service_error - This alarm cannot be disabled. It indicates that the system has detected a software error in the SteelHead service. The SteelHead service continues to function, but an error message that you should investigate appears in the logs.
•  single_cf - This alarm indicates that the connection to a SteelHead connection forwarding neighbor is lost.
•  smb_alert - This alarm indicates that the system has detected an SMB signing error.
•  ssd_wear - This alarm is the parent alarm for ssd_wear_warning. This alarm triggers if one of the ssd_wear_warning:<x> alarms becomes active.
•  ssd_wear_warning - This alarm indicates that the specified disk is approaching its write cycle limit. (Appears only on SteelHead models 7050L or 7050M.)
RiOS tracks the number of writes to each block. To view the overall status, enter the following command:
show alarm ssd_wear
 
To view the status of an individual alarm, enter the following command:
show alarm ssd_wear:<x>
 
where <x> is the SSD disk port number.
•  ssl - This alarm indicates whether the system has detected an SSL error.
•  ssl_peer_scep_auto_reenroll - This alarm indicates that the system has detected an SCEP error. The SteelHead uses SCEP to dynamically reenroll a peering certificate to be signed by a certificate authority. The alarm clears automatically when the next automatic reenrollment succeeds. To clear the alarm, execute the protocol ssl peering auto- reenroll last-result clear-alarm command.
•  sticky_staging_dir - This alarm indicates that the system has detected an error while trying to create a process dump.
•  store_corruption - This alarm cannot be disabled. It indicates whether the data store is corrupt. To clear the data store of data, restart the SteelHead service and clear the data store on the next restart.
•  sw_version_aggr - This alarm indicates that there is a software version mismatch between peer appliances. The client-side and server-side SteelHeads are running incompatible versions of software.
•  system_detail_report - This alarm indicates that a system component has encountered a problem. This alarm is enabled by default.
•  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.
•  web_proxy_config_alarm - This alarm indicates that an error has occurred with the web proxy configuration. By default, this alarm is enabled.
•  web_proxy_service_alarm - This alarm indicates that an error has occurred with the web proxy service. By default, this alarm is enabled.
Usage
Enabling alarms is optional.
Critical temperature settings cannot be changed. Warning temperature settings can be changed.
The no command option disables all statistical alarms. The no alarm <type> enable command disables specific statistical alarms.
Example
amnesiac # alarm connection_forwarding enable
Product
SCC, Interceptor, Mobile Controller, SteelHead CX, SteelHead EX, SteelHead-v, SteelHead-c
Related Commands
alarm clear, alarm clear-threshold, alarm error-threshold, show alarm, show alarms