HP StorageWorks Enterprise File Services WAN Accelerator 3.0.4 installation and configuration guide (AG424-96004, March 2007)

HP STORAGEWORKS EFS WAN ACCELERATOR INSTALLATION AND CONFIGURATION GUIDE 53
3 - TROUBLESHOOTING
I
NSTALLATION PROBLEMS
Problem: Number of Errors on an Interface is
4294967295
Description of
Problem
The show interfaces CLI command displays 4294967295 as the number of errors on
an interface.
Solution The bypass card is not properly installed; reinstall it. For information, see the HP
StorageWorks Enterprise File Services N4c WAN Accelerator 4-port NIC Installation
Guide.
Network (LAN/WAN) topology Packet traversion. Physically draw out both sides of the entire network and make sure that
packets traverse the same client and server HP EFS WAN Accelerators in both directions
(from the client to the server and from the server to the client). Verify packet traversion by
running a traceroute from the client to the server and the server to the client.
Bi-directional continuity. Make sure there is bi-directional continuity between the client
and the client-side HP EFS WAN Accelerator, and the server HP EFS WAN Accelerator and
the network server.
Auto-discovery. If the auto-discovery mechanism, as described in “Definition of Terms” on
page 15, is failing, try implementing a fixed-target rule. You can define fixed-target rules
using the Management Console or the CLI.
For information about configuring fixed-target rules the Management Console, see the HP
Enterprise File Services WAN Accelerator Management Console User Guide.
For information about configuring fixed-target rules the CLI, see the HP Enterprise File
Services WAN Accelerator Command-Line Interface reference manual.
Auto-discovery can fail due to devices dropping TCP options. which sometimes occurs with
certain satellite links and firewalls. To fix this problem, create fixed-target rules that point to
the remote HP EFS WAN Accelerator’s port 7800.
LAN/WAN bandwidth and reliability. Check client and server duplex issues or voice over
IP (VoIP) traffic clogging T1 lines.
Protocol optimization. Are all protocols that you expect to optimize actually optimized in
both directions? If no protocols are optimized, only some of the expected protocols are
optimized, or expected protocols are not optimized in both directions, check:
• That connections have been successfully established.
• That HP EFS WAN Accelerators on the other side of a connection are turned on.
• For secure or interactive ports that are preventing protocol optimization.
• For any pass-through rules that could be causing some protocols to pass-through HP EFS
WAN Accelerators unoptimized.
• That the LAN and WAN cables are not inadvertently swapped.
Broken or slow connections. For help in troubleshooting broken or slow connections, see
the HP EFS WAN Accelerator deployment guide.
Checkpoint Checklist
(2 of 2)