No other action is necessary as the alarm clears automatically. The system is running low on memory and has begun swapping memory pages to disk. This event can be triggered during a software upgrade while the optimization service is still running but there can be other causes.
If this event triggers at any other time, generate a debug sysdump and send it to Riverbed Support. No other action is required as the alarm clears automatically. The appliance has encountered another appliance which is running an incompatible version of system software. 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. The appliance has entered bypass mode and is now passing through all traffic unoptimized. This error is generated if the optimization service locks up or crashes. It can also be generated when the system is first powered on or powered off. If this trap is generated on a system that was previously optimizing and is still running, contact Riverbed Support.
A drive has failed in a RAID array. The appliance continues to optimize during this event. After the error is corrected, the alarm clears automatically. Note: Applicable to models , , , , , , , and only.
Indicates that the RiOS data store is corrupt or has become incompatible with the current configuration. If the alarm was triggered by an unintended change to the configuration, change the configuration to match the previous RiOS data store settings.
Then restart the optimization service without clearing the data store to reset the alarm. Typical configuration changes that require an optimization restart with a clear RiOS data store are enabling enhanced peering or changing the data store encryption. The appliance has entered admission control due to memory consumption.
The appliance is optimizing traffic beyond its rated capability and is unable to handle the amount of traffic passing through the WAN link.
During this event, the appliance continues to optimize existing connections, but new connections are passed through without optimization. No other action is necessary as the alarm clears automatically when the traffic has decreased. The appliance has entered admission control due to the number of connections and is unable to handle the amount of connections going over the WAN link.
The optimization service has halted due to a serious software error. See if a core dump or a system dump was created. If so, retrieve and contact Riverbed Support immediately. The optimization service has encountered a condition which might degrade optimization performance. Consult the system log for more information. No other action is necessary. A scheduled job on the system for example, a software upgrade has failed. A log in to the Management Console by user admin sends this trap as well.
This is for notification purposes only; no other action is necessary. A log out of the Management Console by user admin sends this trap as well. The system has lost one of its Ethernet links, typically due to an unplugged cable or dead switch port. Check the physical connectivity between the SteelHead and its neighbor device. Investigate this alarm as soon as possible. Depending on what link is down, the system might no longer be optimizing and a network outage could occur.
This is often caused by surrounding devices, like routers or switches interface transitioning. This alarm also accompanies service or system restarts on the SteelHead. Check that the clients and servers are using NFSv3 and reconfigure if necessary. A power supply on the appliance has failed not supported on all models. A redundant power supply on the appliance has failed on the appliance and needs to be replaced. Asymmetric routes detected, certain connections might not be optimized because of this.
Asymmetric routing has been detected on the network. This is likely due to a failover event of an inner router or VPN. If so, no action needs to be taken. If not, contact Riverbed Support for further troubleshooting assistance. A fan has failed on this appliance not supported on all models. A fan is failing or has failed and needs to be replaced. A memory error has been detected on the appliance not supported on all models. A memory error has been detected. A system memory stick might be failing.
Try reseating the memory first. If the problem persists, contact Riverbed Support for an RMA replacement as soon as practically possible.
An IPMI event has been detected on the appliance. Please check the details in the alarm report on the Web UI not supported on all models. Check the Alarm Status page for more detail. A configuration change has been detected. Check the log files around the time of this trap to determine what changes were made and whether they were authorized. The RiOS data store on the SteelHead went through an entire cycle and is removing data to make space for new data.
This is normal behavior unless it wraps too quickly, which might indicate that the RiOS data store is undersized. If a message is received every seven days or less, investigate traffic patterns and RiOS data store sizing.
The appliance temperature is a configurable notification. By default, this notification is set to trigger when the appliance reached 70 degrees Celsius. Raise the alarm trigger temperature if it is normal for the SteelHead to get that hot, or reduce the temperature of the SteelHead.
This alarm occurs when the appliance temperature reaches 90 degrees Celsius. Reduce the appliance temperature. This alarm clears automatically the next time all neighbors connect successfully.
Connection lost since end of stream was received from the specified neighbor. The connection has been closed by the connection-forwarding neighbor. Connection lost due to an error communicating with the specified neighbor. The connection has been lost with the connection-forwarding neighbor due to an error.
Connection lost due to lack of keep-alives from the specified neighbor. The connection-forwarding neighbor has not responded to a keepalive message within the time-out period, indicating that the connection has been lost. This alarm clears automatically when all neighbors of the SteelHead are responding to keepalive messages within the time-out period. Connection lost due to lack of ACKs from the specified neighbor. The connection has been lost because requests have not been acknowledged by a connection-forwarding neighbor within the set time-out threshold.
This alarm clears automatically the next time all neighbors receive an ACK from this neighbor and the latency of that acknowledgment is less than the set time-out threshold. The SteelHead has timed out while waiting for an initialization message from the connection-forwarding neighbor. This alarm clears automatically when the SteelHead is able to read the initialization message from all of its neighbors. Connection forwarding latency with the specified neighbor has exceeded the threshold.
The amount of latency between connection-forwarding neighbors has exceeded the specified threshold. The alarm clears automatically when the latency falls below the specified threshold. There is an error in the automatic re-enrollment of the SSL peering certificate.
This alarm clears automatically when the CRL is updated. The secure vault is locked. Check the Alarm Status page for more details. The alarm clears when the secure vault is unlocked.
If you wish to use a nondefault password for the secure vault, the password must be rekeyed. The secure vault password needs to be verified or reset.
Initially, the secure vault has a default password known only to the RiOS software so the SteelHead can automatically unlock the vault during system startup. The alarm clears when you verify the default password or reset the password. An error was detected while initializing the secure vault. Please contact Riverbed Support. An error occurred while initializing the secure vault after a RiOS software version upgrade. Contact Riverbed Support.
This message is for security notification purposes only; no other action is necessary. A disk error has been detected. A disk might be failing. If the problem persists, contact Riverbed Support. An SSD has reached 95 percent of its write cycle limit. A user has logged in to the SteelHead using the command-line interface.
A user has logged in to the SteelHead using the Management Console. A user has logged out of the SteelHead using the Management Console. This message is informational and no action is necessary. The appliance has entered admission control due to high CPU use. No other action is necessary as the alarm clears automatically when the CPU usage has decreased. The appliance has entered admission control due to high TCP memory use. No other action is necessary as the alarm clears automatically when the TCP memory pressure has decreased.
The alarm clears when the system partitions fall below usage thresholds. The number one cause of failing to join a domain is a significant difference in the system time on the Windows domain controller and the SteelHead.
We recommend using NTP time synchronization to synchronize the client and server clocks. It is critical that the SteelHead time is the same as the time on the Active Directory controller. Sometimes an NTP server is down or inaccessible, in which case there can be a time difference.
You must also verify that the time zone is correct. When a DNS misconfiguration occurs during an attempt to join a domain, these error messages appear:. Additionally, the domain join alarm triggers and messages similar to the following appear in the logs:.
The service has detected some x. The alarm clears when the x. The main SteelHead license has expired, been removed, or become invalid. A license on the SteelHead has been removed, has expired, or is invalid. The alarm clears when a valid license is added or updated. Indicates that the system has detected a problem with the SteelHead hardware. These issues trigger the hardware error alarm:. The alarm clears when you add the necessary hardware, remove the unqualified hardware, or resolve other hardware issues.
A top-level module on the system detail report is in error. New MAPI connections will be passed through due to high connection count. The total number of MAPI optimized connections have exceeded the maximum admission control threshold. By default, the maximum admission control threshold is 85 percent of the total maximum optimized connection count for the client-side SteelHead.
The 85 percent threshold is applied only to MAPI connections. The alarm clears automatically when the MAPI traffic has decreased; however, it can take one minute for the alarm to clear. RiOS pre-emptively closes MAPI sessions to reduce the connection count in an attempt to bring the SteelHead out of admission control by bringing the connection count below the 85 percent threshold. Check your automatic peering configuration. Restart the optimization service to clear the alarm.
At times, the USB flash drive that holds the system images might become unresponsive; the SteelHead continues to function normally. On desktop SteelHead x 50 and x 55 models, you must physically power cycle the appliance push the power button or pull the power cord. System will not optimize new connections until this error is cleared. The optimization service has encountered an optimization service condition. The message indicates the reason for the condition:. This message appears after a configuration file error.
For more information, review the SteelHead logs. This message appears if an in-path setting is disabled for an in-path SteelHead. This message appears after a reboot. The alarm clears on its own; no other action is necessary.
This message appears after a system crash. This message appears after entering the CLI command no service enable or shutting down the optimization service from the Management Console. This message appears after the optimization service is restarted from either the CLI or Management Console.
You might want to review the SteelHead logs for more information. Check the banner message in the Management Console to view more information. The banner message displays which upgrade failed along with the RiOS version the SteelHead has reverted to and is currently running. This is often caused by surrounding devices, like routers or switches interface transitioning.
This alarm also accompanies service or system restarts on the SteelHead. Check that the clients and servers are using NFSv3 and reconfigure if necessary. A power supply on the appliance has failed not supported on all models. A redundant power supply on the appliance has failed on the appliance and needs to be replaced. Asymmetric routes detected, certain connections might not be optimized because of this. Asymmetric routing has been detected on the network.
This is likely due to a failover event of an inner router or VPN. If so, no action needs to be taken. If not, contact Riverbed Support for further troubleshooting assistance. A fan has failed on this appliance not supported on all models. A fan is failing or has failed and needs to be replaced. A memory error has been detected on the appliance not supported on all models. A memory error has been detected. A system memory stick might be failing.
Try reseating the memory first. If the problem persists, contact Riverbed Support for an RMA replacement as soon as practically possible. An IPMI event has been detected on the appliance. Please check the details in the alarm report on the Web UI not supported on all models. Check the Alarm Status page for more detail. A configuration change has been detected. Check the log files around the time of this trap to determine what changes were made and whether they were authorized.
The RiOS data store on the SteelHead went through an entire cycle and is removing data to make space for new data. This is normal behavior unless it wraps too quickly, which might indicate that the RiOS data store is undersized. If a message is received every seven days or less, investigate traffic patterns and RiOS data store sizing. The appliance temperature is a configurable notification.
By default, this notification is set to trigger when the appliance reached 70 degrees Celsius. Raise the alarm trigger temperature if it is normal for the SteelHead to get that hot, or reduce the temperature of the SteelHead. This alarm occurs when the appliance temperature reaches 90 degrees Celsius.
Reduce the appliance temperature. This alarm clears automatically the next time all neighbors connect successfully. Connection lost since end of stream was received from the specified neighbor. The connection has been closed by the connection-forwarding neighbor. Connection lost due to an error communicating with the specified neighbor.
The connection has been lost with the connection-forwarding neighbor due to an error. Connection lost due to lack of keep-alives from the specified neighbor.
The connection-forwarding neighbor has not responded to a keep-alive message within the time-out period, indicating that the connection has been lost. This alarm clears automatically when all neighbors of the SteelHead are responding to keep-alive messages within the time-out period. Connection lost due to lack of ACKs from the specified neighbor. The connection has been lost because requests have not been acknowledged by a connection-forwarding neighbor within the set time-out threshold.
This alarm clears automatically the next time all neighbors receive an ACK from this neighbor and the latency of that acknowledgment is less than the set time-out threshold. The SteelHead has timed out while waiting for an initialization message from the connection-forwarding neighbor. This alarm clears automatically when the SteelHead is able to read the initialization message from all of its neighbors.
Connection forwarding latency with the specified neighbor has exceeded the threshold. The amount of latency between connection-forwarding neighbors has exceeded the specified threshold. The alarm clears automatically when the latency falls below the specified threshold. There is an error in the automatic re-enrollment of the SSL peering certificate.
This alarm clears automatically when the CRL is updated. The secure vault is locked. Check the Alarm Status page for more details. The alarm clears when the secure vault is unlocked. If you wish to use a nondefault password for the secure vault, the password must be rekeyed. The secure vault password needs to be verified or reset. Initially, the secure vault has a default password known only to the RiOS software so the SteelHead can automatically unlock the vault during system startup.
The alarm clears when you verify the default password or reset the password. An error was detected while initializing the secure vault. Please contact Riverbed Support. An error occurred while initializing the secure vault after a RiOS software version upgrade. Contact Riverbed Support. This message is for security notification purposes only; no other action is necessary. A disk error has been detected. A disk might be failing. If the problem persists, contact Riverbed Support.
An SSD has reached 95 percent of its write cycle limit. A user has logged in to the SteelHead using the command-line interface. A user has logged in to the SteelHead using the Management Console. A user has logged out of the SteelHead using the Management Console.
This message is informational and no action is necessary. The appliance has entered admission control due to high CPU use. No other action is necessary as the alarm clears automatically when the CPU usage has decreased.
The appliance has entered admission control due to high TCP memory use. No other action is necessary as the alarm clears automatically when the TCP memory pressure has decreased. The alarm clears when the system partitions fall below usage thresholds. The number one cause of failing to join a domain is a significant difference in the system time on the Windows domain controller and the SteelHead.
We recommend using NTP time synchronization to synchronize the client and server clocks. It is critical that the SteelHead time is the same as the time on the Active Directory controller. Sometimes an NTP server is down or inaccessible, in which case there can be a time difference.
You must also verify that the time zone is correct. When a DNS misconfiguration occurs during an attempt to join a domain, these error messages appear:. Additionally, the domain join alarm triggers and messages similar to the following appear in the logs:.
The service has detected some x. The alarm clears when the x. The main SteelHead license has expired, been removed, or become invalid.
A license on the SteelHead has been removed, has expired, or is invalid. The alarm clears when a valid license is added or updated. Indicates that the system has detected a problem with the SteelHead hardware. These issues trigger the hardware error alarm:. The alarm clears when you add the necessary hardware, remove the unqualified hardware, or resolve other hardware issues.
A top-level module on the system detail report is in error. New MAPI connections will be passed through due to high connection count.
The total number of MAPI optimized connections have exceeded the maximum admission control threshold. By default, the maximum admission control threshold is 85 percent of the total maximum optimized connection count for the client-side SteelHead. The 85 percent threshold is applied only to MAPI connections. The alarm clears automatically when the MAPI traffic has decreased; however, it can take one minute for the alarm to clear.
RiOS pre-emptively closes MAPI sessions to reduce the connection count in an attempt to bring the SteelHead out of admission control by bringing the connection count below the 85 percent threshold. Check your automatic peering configuration. Restart the optimization service to clear the alarm. At times, the USB flash drive that holds the system images might become unresponsive; the SteelHead continues to function normally. System will not optimize new connections until this error is cleared.
The optimization service has encountered an optimization service condition. The message indicates the reason for the condition:. This message appears after a configuration file error. For more information, review the SteelHead logs. This message appears if an in-path setting is disabled for an in-path SteelHead. This message appears after a reboot. The alarm clears on its own; no other action is necessary. This message appears after a system crash.
This message appears after entering the CLI command no service enable or shutting down the optimization service from the Management Console. This message appears after the optimization service is restarted from either the CLI or Management Console.
You might want to review the SteelHead logs for more information. Check the banner message in the Management Console to view more information. The banner message displays which upgrade failed along with the RiOS version the SteelHead has reverted to and is currently running.
You can use the MD5 checksum tool provided on the Riverbed Support site for the verification. If the upgrade continues to fail, contact Riverbed Support. One or more licensed features will expire within the next two weeks. One or more feature licenses are scheduled to expire within two weeks. This alarm is triggered per feature. One or more feature licenses have expired. Verify that the neighbor is reachable from this SteelHead.
Next, check that the optimization service is running on both SteelHeads. The optimization service has detected a failure with domain controller communication or a delegate user. To view useful debugging information in RiOS 7.
Verify that a delegate user has been added to the SteelHead and is configured with the appropriate privileges. Indicates that an interface was not configured for half-duplex negotiation but has negotiated half-duplex mode.
Half-duplex significantly limits the optimization service results. Next, examine the peer switch user interface to check its link configuration.
If the configuration on one side is different from the other, traffic is sent at different rates on each side, causing many collisions. To troubleshoot, change both interfaces to automatic duplex negotiation. Indicates that the error rate on an interface has exceeded 0. 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 few errors. The alarm clears when the error rate drops below 0.
To troubleshoot, try a new cable and a different switch port. Another possible cause is electromagnetic noise nearby. 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. During clean up RiOS uninstalls all slots and deletes all backups and packages. When you encounter this error, switch the storage profile again. If the switch succeeds, the error clears. The optimization service has encountered a peer SteelHead IPv6 incompatibility.
An IPv4 address is necessary for routing between neighbors and an IPv6 address is necessary for v6 optimization. Indicates that a connection-forwarding neighbor is running a RiOS version that is incompatible with IPv6. Neighbors must be running RiOS 8.
The SteelHead neighbors pass through IPv6 connections when this alarm triggers. You could also delete any RiOS images that you no longer use. You need to clear the RiOS data store. Clearing the data store degrades performance until the system repopulates the data. Indicates that one of the predefined paths for a connection is unavailable because it has exceeded either the timeout value for path latency or the threshold for observed packet loss.
When a path fails, the SteelHead directs traffic through another available path. When the original path comes back up, the SteelHead redirects the traffic back to it. The optimization service has encountered a neighbor incompatibility. The message indicates one of these conditions:. Indicates that a peer SteelHead is no longer connected to the secure transport controller.
The controller is a SteelHead that typically resides in the data center and manages the control channel and operations required for secure transport between SteelHead peers. The control channel between the SteelHeads uses SSL to secure the connection between the peer SteelHead and the secure transport controller.
The peer SteelHead is no longer connected to the secure transport controller because:. Indicates that a path selection monitoring probe for a predefined path has received a probe response from an unexpected relay or interface. An iSCSI initiator is not accessible. A snapshot failed to be committed to the SAN, or a snapshot has failed to complete due to Windows timing out.
Check the SteelFusion Core logs for details. Retry the Windows snapshot. The block store is running out of space. This triggers when only 5 percent of space is available in the block store. The can also happen if clients write more data than can be sent over the WAN for a prolonged period of time.
This indicates a temporary condition caused by too much IO. Limit the number of active prepop sessions. Check if the IOPS exceeds the model recommendation. The block store could not read data that was already replicated to the DC. Check the system logs to determine the root cause.
Replace any disks that have failed. The alarm clears when you restart the optimization service. The block store could not read data that is not yet replicated to the DC. The block store failed to start due to disk errors or an incorrect configuration. The SteelFusion Edge software version is incompatible with the block store version on disk. The alarm indicates that the software has been upgraded or downgraded with an incompatible version.
Revert to the previous software version. The block store could not save data to disk due to a media error. Most likely the configuration present on the SteelFusion Core is missing an entry for the Edge.
The Edge does not have an active connection with the SteelFusion Core. Check the network between the Edge and the Core; recheck the Edge configuration on the Core. The connection between the SteelFusion Core and the Edge has stalled. This alarm checks for how much uncommitted data is in the Edge cache as a percentage of the total cache size.
This alarm triggers when the appliance writes a large amount of data very quickly, but the WAN pipe is not large enough to get the data back to the SteelFusion Core fast enough to keep the uncommitted data percentage below 5 percent.
As long as data is being committed, the cache will flush eventually. The threshold is 5 percent, which for a 4 TB system is G. To change the threshold, use the following CLI command:. Core3 config edge id Edge2 blockstore uncommitted trigger-pct 50 repeat-pct 25 repeat-interval 5. The virtualization service is not running. The email notification indicates whether the alarm was triggered because the VSP services was disabled, restarted, or crashed. Average virtualization CPU utilization of the individual cores has exceeded an acceptable threshold.
The default threshold is 90 percent. If virtual CPU utilization spikes are frequent, it might be because the system is undersized. Sustained virtual CPU load can be symptomatic of more serious issues.
0コメント