No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

How to Troubleshoot the Underlying Link Instability of the S5100?

Publication Date:  2012-07-20 Views:  74 Downloads:  0
Issue Description
The underlying link stability of the S5100 may degrade due to device insertion or removal, power cycle, I/O timeout, or error codes. If the instability persists for a long time, the device performance dramatically deteriorates and no I/O requests can be delivered. This case describes how to troubleshoot the underlying link instability. Alarm information: No visible alarms are displayed, but the overall performance deterioration can be sensed in token of the high I/O latency, persistent high water level of the cache, and abnormal utilization rates of the CPU and memory.
Alarm Information
None
Handling Process
Refer to accessory
Root Cause
Short-term link instability can occur due to device insertion or removal, or power cycle, which is normal and does not cause long-term or frequent system instability. If no device is physically inserted or removed from the S5100 and no power cycle is implemented but error messages about those cases are generated, the link instability occurs, which is probably caused by I/O timeout or error codes.
Suggestions
Error codes may but not necessarily incur unstable links. The S5100 initiates complete device scanning when component insertion or removal is detected. During the scanning, links may experience transient instability, which however is normal. When error codes are detected on disk slots or expansion ports, it is not necessarily the case that the disk slots or expansion ports incur unstable links. Instead, you are advised to repeatedly execute the showphyerrcode command at an interval to monitor the error code variation. If error codes continuously occur on a disk slot or expansion port, the link instability is probably caused by the slot or port.

END