Riverbed SteelHead 5080, Руководство по установке и настройке

Страница: 48 / 94

48 | Troubleshooting
Duplex mismatch
• SteelHead to router: crossover cable
• SteelHead to switch: straight-through cable
• SteelHead to SteelHead: crossover cable
• SteelHead to a host: crossover cable
For details, go to Knowledge Base article S15298 .
Duplex mismatch
These symptoms occur due to a duplex mismatch:
• Access is not faster after configuring the SteelHead.
• The Link Duplex alarm triggers.
• The interface counters display error messages. An alarm or log message about error counts
appears.
• The pass-through rule is ineffective. (This is a definite indication of duplex mismatch.)
• Many retransmissions are present in packet traces.
• You can’t connect to an attached device.
• You can connect with a device when you choose autonegotiation, but you can’t connect with the
same device when you manually set the speed or duplex.
• Good performance occurs for one direction of data flow, but poor performance occurs in the
opposite direction.
Possible cause
• You have probably set the duplex value for your router to 100 Full (fixed) and set the duplex value
for the SteelHead to Auto.
Example
This example shows applications that appear slower with SteelHeads configured in an in-path
deployment. The timed performance numbers to transfer a 20-MB file over FTP are:
• no SteelHead – 3:16
• cold SteelHead – 5:08
• warm SteelHead – 3:46
Adding a pass-through rule for an application doesn’t help. Slow connections appear as optimized in the
Management Console on the Current Connections report page. However, stopping the SteelHead
service while leaving the system powered on and an in-path configuration returns performance to
original levels.
Solutions
To resolve the duplex mismatch error: