Troubleshooting
Connectivity and Configuration Issues
Many connectivity and configuration issues can be diagnosed using standard network
troubleshooting techniques. This section identifies some common problems, the most likely
causes, and the best solutions. It also describes the diagnostic commands available in the CLI
(See
No Output (or Garbled Output) Over Serial
Terminal or terminal emulator may not be properly configured
Check the serial cable connection and the communication settings of the terminal or terminal
emulator. Refer to
"Setting Up a Terminal or Terminal Emulator"
on page 48 for the appropriate settings
for your appliance. If you are using terminal emulation software on a Windows or Unix system,
make sure the terminal emulation software is connecting to the port to which the serial cable is
connected.
Clients Time Out Trying to Contact a Virtual Cluster
Packets from the server are not being routed back through ADC
Log on to the server(s) and check the routing tables. Perform a
traceroute
(or
tracert
on
Windows) from the server to the client. Adjust route until the ADCs address shows up in the
traceroute output.
All packets sent from the server back to clients must pass through the ADC on the way back
to the client unless the spoof cluster option is disabled, or Direct Server Return (DSR) is
configured.
Test client is on the same network as the servers
If the test client is on the same network as the servers, the servers will probably try to send data
packets directly to the client, bypassing the ADC. You can correct this by adding host routes on the
servers so that the servers send their reply packets back to the client through the ADC.
No active servers in the virtual cluster
Possible solutions:
l
Check the cluster configuration: Is a server pool assigned to the cluster? Are there server
instances in the server pool and are they all marked UP?
l
Log onto one of the servers and run the netstat command. If the netstat output shows con-
nections in the SYN-RCVD state, the server is not forwarding its reply packets.
The ADC is not active
Try to ping one of the configured subnet IP addresses. If you do not get a response, “Equalizer
Doesn’t Respond to Pings to the Admin Address” provides additional troubleshooting information.
756
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
Summary of Contents for Equalizer GX Series
Page 18: ......
Page 32: ...Overview 32 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 42: ......
Page 52: ......
Page 64: ......
Page 72: ......
Page 76: ......
Page 228: ......
Page 238: ......
Page 476: ......
Page 492: ......
Page 530: ......
Page 614: ......
Page 626: ......
Page 638: ......
Page 678: ......
Page 732: ...Using SNMP Traps 732 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 754: ......
Page 790: ......
Page 804: ......
Page 842: ......
Page 866: ......