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

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

Troubleshooting | 49
In-path SteelHeads connection
• Connect to the SteelHead CLI and enter the ping command to check the duplex mismatch:
ping –f –I <in-path-ip> –s 1400 <client-ip>
• Change the interface speed and duplex to match.
• Ensure there’s a speed and duplex match between each in-path interface and its peer network
interface. If they don’t match, you might have a large number of errors on the interface when it’s in
the bypass mode, because the switch and the router aren’t set with the same duplex settings. Also,
ensure connectivity when service is down.
If matching speed and duplex don’t reduce collisions or errors, try hard-setting one end and auto-
setting the other. Try the half-duplex mode.
• If all combinations fail, as a last resort, add an intermediary hub or switch that is more compatible
with both network interfaces.
In-path SteelHeads connection
When SteelHeads have in-path connection issues, the two sites are connected in-path and you can ping
them, but they can’t connect to each other to optimize data.
Possible cause
The firewall is running port filtering and drops your probe packets. The firewall is filtering the IP and port
address of the source and destination (bandwidth limitation) systems.
Solutions
To resolve the SteelHead connection issue:
• open port 7800 on both firewalls.
• use the port visibility mode.
• if there’s no encryption, place the SteelHead after the firewall.
Oplock issues
These symptoms occur due to opportunistic lock (oplock) issues:
• File access is not faster or tasks such as drag-and-drop are fast but applications might benefit from
acceleration.
• The Current Connections report page in the Management Console (select Reports > Networking:
Current Connections) displays slow connections as optimized.
Possible causes
• The client is running an old antivirus software, which competes with the application for an oplock
instead of opening as read-only. The antivirus causes multiple file opens.
• The server has oplocks disabled.