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

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

Installing and Configuring the SteelHead | 41
Configuring out-of-path SteelHeads
Ensure that the server is located across the WAN.
4. Drag and drop the 1-MB file again.
Performance improves significantly.
Checking for speed and duplex errors
If you selected autonegotiation (auto) for your in-path and primary interfaces, you must ensure that the
SteelHead negotiated the speed and duplex at the rate your devices expect. For example, ensure settings
are
auto on the LAN and WAN and 100 FULL on the LAN and WAN. You can verify your speed and duplex
settings in the Networking > Networking: In-path Interfaces page and the Networking > Networking:
Base Interfaces page of the Management Console.
To check for speed and duplex errors
1. In the Management Console, choose the Reports > Diagnostics: System Logs page.
2. Check the system logs for duplex or speed errors, and cyclic redundancy check (CRC) or frame
errors.
3. Choose Administration > System Settings: Alarms.
4. Check the link duplex and link I/O alarms.
If a link alarm status is degraded, choose Networking > Networking: Base Interfaces or Networking >
Networking: In-path Interfaces and examine the SteelHead link configuration. 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. If the interfaces don’t
support automatic duplex, configure both ends for full duplex.
You can enable or disable the alarm for a specific interface. To disable an alarm, choose
Administration: System Settings > Alarms and select or clear the check box next to the link alarm.
Configuring out-of-path SteelHeads
In an out-of-path deployment, the SteelHead is not in the direct path between the client and the server.
Servers see the IP address of the server-side SteelHead rather than the client-side IP address.
An out-of-path configuration is suitable for data center locations where physical in-path or logical in-
path configurations aren’t possible. For a detailed figure, see
“Choosing a network deployment” on
page 25 .
For detailed information about out-of-path deployments, see the SteelHead Deployment Guide .
Connecting out-of-path SteelHeads to your network
You use a standard Ethernet straight-through cable to connect the primary port of the SteelHead to the
LAN switch in an out-of-path configuration.