Table Of Contents
Troubleshooting for LocalDirector
Console Is Blank
Problems Booting
Cannot Access Real Servers
Real Servers Can Be Accessed but Virtual Server Is Not Working
Load Balancing
Rebooting
Changing Routers or Servers Causes Access Problems
Forgot Password
Syslog Messages
Troubleshooting for LocalDirector
This appendix contains troubleshooting tips that may help you resolve a configuration problem. Topics include:
•
Console Is Blank
•Problems Booting
•Cannot Access Real Servers
•Real Servers Can Be Accessed but Virtual Server Is Not Working
•Load Balancing
•Rebooting
•Changing Routers or Servers Causes Access Problems
•Forgot Password
•Syslog Messages
If you contact TAC regarding your LocalDirector configuration, we recommend that you have a diagram of your network with IP addresses and subnet masks available, and a copy of output from the following commands:
•show bind
•show bridge
•show configuration
•show interface
•show name
•show real
•show syslog
•show version
•show virtual
•write
•show fail
Console Is Blank
•Make sure that you used the console cable provided with 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 nonsystem diskette in the diskette drive, LocalDirector will not boot and will display messages similar to the following:
þ..................................Execing flop
þ..................................Execing flop
Replace the diskette with one that contains LocalDirector software, or remove the diskette so LocalDirector can boot from Flash memory.
We recommend that you remove the LocalDirector software floppy diskette after the initial boot of LocalDirector and store it in a safe place.
Note When copying files from Cisco.com, do not copy the LocalDirector .exe file to diskette and use it as a system diskette. See "Upgrading LocalDirector Software," for more information on downloading files from Cisco.com.
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.
•Make sure all interfaces in use are configured as No Secure.
Real Servers Can Be Accessed but Virtual Server Is Not Working
It is possible that you can access the real servers and can ping the virtual servers, but you cannot access the real servers through a virtual server. This situation is usually caused by either a bad cable (most unlikely) or a bridge loop (most likely).
Sometimes two interfaces of LocalDirector are connected to the same switch or hub, thereby creating a loop. Ensure that you have properly deployed LocalDirector, with all the servers on one side and the incoming network on the other.
•Check the bridge with the show bridge command.
•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.
•Use the show virtual command to make sure that the virtual server is in service (IS).
Load Balancing
•Make sure (through the show real, show config, and show bind commands) that all the real servers are properly bound to the virtual addresses and marked in service (IS).
•Test with the ping and traceroute commands to determine whether you can reach the real servers through LocalDirector (they should be available). Check for routing loops.
•If you have assigned weight values to your real servers with the weight command, be sure to use to the weighted keyword with the predictor command.
Note Depending on your environment, minor fluctuations may occur in load balancing.
Rebooting
If LocalDirector is truly crashing (not just rebooting), it will core dump. Copy the core dump, paste it into a file, and send it to the Cisco Technical Assistance Center (TAC) for analysis.
Changing Routers or Servers Causes Access Problems
Changing routers or servers may cause access problems if LocalDirector is using an old MAC address. Use the no arp or clear arp command 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 the TAC.
Syslog Messages
This section contains tables that alphabetically list the syslog messages generated by LocalDirector. Syslog messages are categorized into the following severities and are shown in the following tables: Syslog Notice Messages in Table A-1, Syslog Error Messages in Table A-2, Syslog Critical Messages in Table A-3, and Syslog Emergency Messages in Table A-4. The tables also include the functional component of LocalDirector where the message originates (such as the command interface, failover, and so forth).
Table A-1 Syslog Notice Messages
Message
|
Functional Component
|
Begin Configuration: reading from floppy
|
Command interface
|
Begin Configuration: reading from memory
|
Command interface
|
Begin Configuration: reading from net
|
Command interface
|
Begin Configuration: reading from terminal
|
Command interface
|
Begin Configuration: writing to floppy
|
Command interface
|
Begin Configuration: writing to memory
|
Command interface
|
Begin Configuration: writing to net
|
Command interface
|
Begin Configuration: writing to standby
|
Command interface
|
Begin Stateful Connection Replication: Sending to mate
|
Load balancer
|
dfp: can't ioctl tcp error call back
|
DFP Service
|
dfp: Connected to dfp host host:port
|
DFP Service
|
dfp: Connection to dfp host host closing because: message
|
DFP Service
|
dfp: Connection to host terminated
|
DFP Service
|
dfp error: io problem in security check
|
DFP Service
|
dfp error: not a pref_info_msg
|
DFP Service
|
dfp error: malformed packet
|
DFP Service
|
dfp error: reserved field expected to be 0
|
DFP Service
|
dfp error: security error
|
DFP Service
|
dfp error: unsupported proto type proto
|
DFP Service
|
dfp error: wrong proto ver, got ver expected ver
|
DFP Service
|
dfp error: wrong security type, received:type expected:type
|
DFP Service
|
dfp error: wrong vector type, received:type expected:type
|
DFP Service
|
dfp:trying to connect to dfp host host
|
DFP Service
|
Edited from At Capacity to Failed (External)
|
Real machine state change
|
Edited from At Capacity to Maintenance
|
Real machine state change
|
Edited from At Capacity to Out of Service
|
Real machine state change
|
Edited from At Capacity to Sticky
|
Real machine state change
|
Edited from Failed (External) to In Service
|
Real machine state change
|
Edited from Failed (External) to Maintenance
|
Real machine state change
|
Edited from Failed (External) to Out of Service
|
Real machine state change
|
Edited from Failed (External) to Sticky
|
Real machine state change
|
Edited from Failed to Failed (External)
|
Real machine state change
|
Edited from Failed to In Service
|
Real machine state change
|
Edited from Failed to Maintenance
|
Real machine state change
|
Edited from Failed to Out of Service
|
Real machine state change
|
Edited from Failed to Sticky
|
Real machine state change
|
Edited from In Service to Failed (External)
|
Real machine state change
|
Edited from In Service to Maintenance
|
Real machine state change
|
Edited from In Service to Out of Service
|
Real machine state change
|
Edited from In Service to Sticky
|
Real machine state change
|
Edited from Maintenance to Failed (External)
|
Real machine state change
|
Edited from Maintenance to In Service
|
Real machine state change
|
Edited from Maintenance to Out of Service
|
Real machine state change
|
Edited from Maintenance to Sticky
|
Real machine state change
|
Edited from Newly Created to In Service
|
Real machine state change
|
Edited from Newly Created to Out of Service
|
Real machine state change
|
Edited from Out of Service to Failed (External)
|
Real machine state change
|
Edited from Out of Service to In Service
|
Real machine state change
|
Edited from Out of Service to Maintenance
|
Real machine state change
|
Edited from Out of Service to Sticky
|
Real machine state change
|
Edited from Sticky to Failed (External)
|
Real machine state change
|
Edited from Sticky to In Service
|
Real machine state change
|
Edited from Sticky to Maintenance
|
Real machine state change
|
Edited from Sticky to Out of Service
|
Real machine state change
|
Edited from Testing to Failed (External)
|
Real machine state change
|
Edited from Testing to Maintenance
|
Real machine state change
|
Edited from Testing to Out of Service
|
Real machine state change
|
Edited from Testing to Sticky
|
Real machine state change
|
End Configuration: FAILED
|
Command interface
|
End Configuration: OK
|
Command interface
|
End Configuration: [OK]
|
Command interface
|
End Stateful Connection Replication
|
Load balancer
|
Erase Configuration.
|
Command interface
|
init_snmpd: out of memory
|
SNMP
|
In Service
|
Real machine state change
|
LocalDirector Booted
|
Load balancer
|
Newly created edited to In Service
|
Real machine state change
|
Newly created edited to Out of Service
|
Real machine state change
|
Passed security
|
Rotor
|
snmp: cannot open UDP channel on interface interface
|
SNMP
|
snmp: could not create snmp thread
|
SNMP
|
snmp: could not create snmp trap thread
|
SNMP
|
snmpd: out of memory
|
SNMP
|
snmp:init_snmp_trap: could not malloc
|
SNMP
|
SNMP not available.
|
SNMP
|
snmp: snmp_write: invalid or null data
|
SNMP
|
snmp: unknown gtrap gtrap
|
SNMP
|
snmp: unknown strap strap
|
SNMP
|
Testing
|
Real machine state change
|
The syslog Error Messages are listed in Table A-2.
Table A-2 Syslog Error Messages
Message
|
Functional Component
|
Bridge Loop, %E ifc %d->%d
|
Bridge
|
Route table full. %I %I %I not added.
|
IP
|
See Table A-3 for the syslog Critical Messages.
Table A-3 Syslog Critical Messages
Message
|
Functional Component
|
Application Remains Failed
|
Real machine state change
|
At Capacity
|
Real machine state change
|
Brought into service
|
Real machine state change
|
Configuration replication to Standby unit FAILED for command command
|
Command interface
|
Edited from Failed (External) to Failed
|
Real machine state change
|
Edited from In Service to Failed (External)
|
Real machine state change
|
Edited from In Service to Maintenance
|
Real machine state change
|
Edited from In Service to Sticky
|
Real machine state change
|
Edited from Maintenance to In Service
|
Real machine state change
|
Edited from Sticky to Failed
|
Real machine state change
|
Failed
|
Real machine state change
|
Failed Application
|
Real machine state change
|
Failed (No answer)
|
Real machine state change
|
Failed (TCP RST)
|
Real machine state change
|
LocalDirector LocalDirector out of connections!
|
Load balancer
|
No longer At Capacity
|
Real machine state change
|
Remains Failed
|
Real machine state change
|
Switching `%V' from `slowstart' to `%P'
|
Load balancer
|
Switching `%V' from `%s' to `slowstart'
|
Load balancer
|
Virtual machine `%V' no longer under SYN attack, going to normal mode.
|
Load balancer
|
Virtual machine `%s' under SYN attack, going to SynGuard mode!
|
Load balancer
|
Unit1 : Bad cable: myside - pin1 or pin4-11 external loopback
|
Failover
|
Unit: Bad cable: myside - pin4
|
Failover
|
Unit: Bad cable :myside - pin4-11 external loopback
|
Failover
|
Unit: Bad cable: otherside - pin6-14 internal loopback
|
Failover
|
Unit: Begin configuration replication: Receiving from mate
|
Failover
|
Unit: Begin Configuration Replication: Sending to mate
|
Failover
|
Unit: Cable not connected my side.
|
Failover
|
Unit: Cable not connected other side.
|
Failover
|
Unit: Cable OK.
|
Failover
|
Unit: Disabling Failover.
|
Failover
|
Unit: Enabling Failover.
|
Failover
|
Unit: End Configuration Replication
|
Failover
|
Unit: Error reading cable status.
|
Failover
|
Unit: Failover communications failure.
|
Failover
|
Unit: Link status `Down' on interface interface
|
Failover
|
Unit: Link status `Up' on interface interface
|
Failover
|
Unit: Lost Failover communications with mate
|
Failover
|
Unit: Mate interface interface failed.
|
Failover
|
Unit: Mate interface interface OK.
|
Failover
|
Unit: Mate reporting failure.
|
Failover
|
Unit: Mate says I'm failed.
|
Failover
|
Unit: Mate's interface interface failed
|
Failover
|
Unit: Monitoring on interface interface normal
|
Failover
|
Unit: Monitoring on interface interface waiting
|
Failover
|
Unit: No response from mate.
|
Failover
|
Unit: Power failure other side.
|
Failover
|
Unit: Switching to ACTIVE.
|
Failover
|
Unit: Switching to FAILED.
|
Failover
|
Unit: Switching to OK.
|
Failover
|
Unit: Switching to STNDBY.
|
Failover
|
Unit: Testing Interface interface
|
Failover
|
Unit: Testing on interface interface Failed
|
Failover
|
Unit: Testing on interface interface Passed
|
Failover
|
The syslog Emergency Messages are defined in Table A-4.
Table A-4 Syslog Emergency Messages
Message
|
Functional Component
|
Net Configuration: Access TFTP error
|
Command interface
|
Net Configuration: Badport TFTP error
|
Command interface
|
Net Configuration: Baduser TFTP error
|
Command interface
|
Net Configuration: Diskfull TFTP error
|
Command interface
|
Net Configuration: Exists TFTP error
|
Command interface
|
Net Configuration: failed
|
Command interface
|
Net Configuration: Illegalop TFTP error
|
Command interface
|
Net Configuration: NotFound TFTP error
|
Command interface
|
Net Configuration: Resource TFTP error
|
Command interface
|
Net Configuration: Server Errmesg TFTP error
|
Command interface
|
Net Configuration: Timedout TFTP error
|
Command interface
|
Net Configuration: unknown TFTP state
|
Command interface
|
