Specifications

Equalizer Doesn’t Respond to Pings to the Admin Address
Equalizer Installation and Administration Guide 189
Equalizer Doesn’t Respond to Pings to the Admin Address
Equalizer is not powered on
Check that power switch is on and the front panel LED is lit. Connect the keyboard and monitor,
cycle the power, and watch the startup diagnostic messages.
Equalizer isn't connected to your network
Check the network wiring.
Administration address not configured on the external interface
This applies to dual network configurations. Use the Equalizer Configuration Utility to set the IP
address and netmask for external interface. Be sure to commit your changes.
Browser Hangs When Trying to Connect Via FTP to an FTP
Cluster
FTP server returns its private IP address in response to a “PASV” command
Enable PASV mode FTP translation on the Advanced options page of the Equalizer Administration
utility. (For more information, see “Enabling Passive FTP Connections” on page 53.) This behavior
is likely to cause problems if you’re using reserved internal addresses for the server
Return Packets from the Server Aren’t Routing Correctly
IP spoofing is enabled
This problem normally occurs in a single network setup. When you enable IP spoofing, clustered
servers see the client’s IP address. If the server tries to reply directly to the client, the client will
reject the reply (it had sent its request to a different address).
Run a
traceroute to ensure that routes from a server to a client go through Equalizer and not
directly back to the client. If Equalizer does not appear, modify the route to include Equalizer.
Alternatively, you can disable IP spoofing.
Web Server Cannot Tell Whether Incoming Requests Originate
Externally or Internally
IP Spoofing is not enabled
Check the cluster’s configuration and enable IP spoofing. This causes Equalizer to pass the client’s
IP address. Make sure that responses from the server go through the Equalizer.