Troubleshooting

The following troubleshooting tips may help resolve a configuration problem without the need to contact Cisco's Technical Assistance Center (TAC).

If you contact Support regarding your LocalDirector configuration, have a diagram of your network with IP addresses and subnet masks available, and have a copy of the following output:

show real
show virtual
show name
show bind
show configuration
show version
show interface
show syslog

Blank Console

Make sure that you used the console cable provided with the LocalDirector, and that it is properly connected.
Make sure that the terminal emulation software is set at 9600 baud, 8 data bits, no parity, and 1 stop bit.

Problems Booting

If you have a non-system diskette in the diskette drive, the LocalDirector will not boot and will display messages similar to the following:


PIX Bios V2.7
Booting Floppy
 ..................................Execing flop
PIX Bios V2.7
Booting Floppy
 ..................................Execing flop
PIX Bios V2.7
Booting Floppy

Replace the diskette with one that contains the LocalDirector software or remove the diskette so the LocalDirector can boot from flash memory.

Note When copying files from CCO, do not copy the LocalDirector .exe to diskette and use it as a system diskette. See "LocalDirector Software Installation and Upgrade" in Chapter 2, "Installing LocalDirector," for more information on downloading files from CCO.

Cannot Access Real Servers

Use the show configuration command to verify that each network interface is properly configured.
Make sure that the devices on both network interface segments have the same network number.

Reals Can be Accessed but Virtual Is Not Working

You may run across a situation where you can access the real servers and can ping the virtual servers, but you cannot access the real servers through a virtual server. This is usually caused by either a bad cable (rare) or a bridge loop (most likely).

Sometimes both ends of the LocalDirector are connected to the same switch/hub, thereby creating a loop. SYSLOG messages are generated to indicate a bridge loop. Ensure that you have properly deployed the LocalDirector, with all the servers on one side and the incoming network on the other.

Check the routing table with the show route command.
Make sure you are not trying to access the virtual server from the server side of the switch.
Make sure that the virtual machine is in service (IS) by using the show virtual command.

Port Mapping

The map command syntax changed as follows:

LocalDirector version 1.2.x:

[no] map v_ip v_port r_ip r_port

LocalDirector version 1.5:

[no] map virtual_id virtual_port real_port

This creates a problem if you have a configuration similar to the following where port 80 traffic is going to two different ports on the real machines bound to it:


virtual 192.168.89.100
real 192.168.89.121
real 192.168.89.122
bind 192.168.89.100 192.168.89.121 192.168.89.122
map 192.168.89.100 80 192.168.89.121 8001
map 192.168.89.100 80 192.168.89.122 8002

Now port 80 is only mappable to the same port on the real server as follows:


virtual 192.168.89.100
real 192.168.89.121
real 192.168.89.122
bind 192.168.89.100 192.168.89.121 192.168.89.122
map 192.168.89.100 80 8001

Port 80 traffic will be sent to port 8001 on both 192.168.89.121 and 192.168.89.122.

Note The map command will be phased out in future releases.

Load Balancing

Make sure (via show real, show config, and show bind) that all the real servers are properly bound to the virtual address(es) and marked in service (IS).
Test with ping and traceroute to determine if you can reach the real servers through the LocalDirector (they should be available). Check for routing loops.
If you have assigned weight values to your real servers, be sure that the predictor option is set to weighted.

Note Depending on your environment, minor fluctuations may occur in load balancing. Refer to Appendix B, "Load Balancing Options," for more information.

Rebooting

If a LocalDirector is truly crashing (as opposed to just rebooting), it will dump core. Capture the core dump and provide it to Cisco's TAC so they can determine whether or not the issue is known.

Changing Routers or Servers Causes Access Problems

Changing routers or servers may cause access problems if the LocalDirector is using an old MAC address. Enter no arp or clear arp to clear the ARP cache.

Forgot Password

If you use the configure floppy command, the password that was in use when the diskette was saved will overwrite the current password. Try a previously used password, or contact Cisco's TAC.

SYSLOG and SNMP Messages

This section lists SYSLOG and SNMP messages generated by the LocalDirector. In the following messages, 'hostname' is the name of the LocalDirector unit, 'x' is the server identification, and 'interface' is the LocalDirector interface. All of the following messages (except the last two) are sent to the SYSLOG host. Messages marked with an asterisk (*) are also sent to the SNMP host.

For a list of SYSLOG failover and configuration replication messages, see Appendix A, "LocalDirector Hot-Standby Failover."

Critical messages


Level 2 "Real machine 'x' Remains Failed"*
Level 2 "Real machine 'x' Failed"*
Level 2 "Switching 'x' from 'slowstart' to 'predictor'*
Level 2 "Virtual machine 'x' brought into service"*
Level 2 "Virtual machine 'x' Failed"*
Level 2 "Virtual machine 'x' no longer under SYN attack, going to normal mode."*
Level 2 "Virtual machine 'x' under SYN attack, going to SynGuard mode!"*
Level 2 "Virtual machine 'x' At Capacity"
Level 2 "Switching 'x' from 'predictor' to 'slowstart'"
Level 2 "Real machine 'x' Failed Application"
Level 2 "Real machine 'x' Application Remains Failed"
Level 2 "Switching 'x' from 'predictor' to 'slowstart'"
Level 2 "Switching 'x' from 'predictor' to 'slowstart'"

Error messages


Level 3 "Bridge Loop, 'source'->'destination' 'interface' -> 'interface'."
Level 3 "rip_open() - open 'interface' failed"
Level 3 "rip_open() - create 'interface' failed"

Normal but significant messages


Level 5 "Trying Real machine 'x'
Level 5 "Begin Configuration: reading from floppy"
Level 5 "Begin Configuration: reading from memory"
Level 5 "Begin Configuration: reading from terminal"
Level 5 "Begin Configuration: writing to floppy"
Level 5 "Begin Configuration: writing to memory"
Level 5 "End Configuration: FAILED"
Level 5 "End Configuration: OK"
Level 5 "Erase Configuration."
Level 5 "Local Director Booted"*
Level 5 "Real machine 'x' edited from Failed to Out Of Service"
Level 5 "Real machine 'x' edited from In Service to Out Of Service"
Level 5 "Real machine 'x' edited from Out Of Service to In Service"
Level 5 "Real machine 'x' edited from Testing to Out Of Service"
Level 5 "Real machine 'x' In Service"*
Level 5 "Trying Real machine 'x'"*
Level 5 "Virtual machine 'x' edited from In Service to Out Of Service"
Level 5 "Virtual machine 'x' edited from Out Of Service to In Service"
Level 5 "Virtual machine 'x' edited from Failed to In Service"
Level 5 "Virtual machine 'x' edited from Failed to Out Of Service"

Messages sent via SNMP traps only:


"SNMPlinkUp, 'interface'"
"SNMPlinkDown, 'interface'"
"SNMP warmstart"

Table of Contents