Document ID: 18005 | PDF Downloads
|
FeedbackCisco has announced the end-of-sale for the Cisco LocalDirector. For more information, refer to the LocalDirector 400 Series End-of-Life and End-of-Sale Notices and Product Bulletins.
Introduction
This document provides troubleshooting commands and information for when one (or more) of the virtual/real servers is not working on LocalDirector (LD).
Before You Begin
Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.
Prerequisites
There are no specific prerequisites for this document.
Components Used
The information in this document is based on the software and hardware versions below.
-
LD-416, software 4.2.2
The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.
Commands
Use these commands to troubleshoot your device:
-
show virtual—do you see all your virtual servers with the proper protocol, IP address/port, and are they in-service (state=is)?
-
show real—do you see all your real servers with the proper protocol, IP address/port and are they all in-service? Are any of the counters in the last three columns non-zero?
-
show bind—do you see your virtual bound to the proper reals? Make sure the ports, if specified, are correct. If the virtual and real ports are not the same, port translation will be performed, so make sure this is what was intended.
-
ping —repeat for each real.
-
show arp—on the LD. Do all your real's IP addresses show up on a different interface than the IP address of the default-router? If not, you need to re-evaluate your topology. Note: The machine accessing the virtual must not be on the same interface as any of the reals bound to that virtual.
-
show arp—on the LD's default router. Do all the virtuals show with the MAC address of the LD? If not, check the topology. Use the same troubleshooting steps for the show arp command.
-
show weight—do any of the real servers show a weight of 0? This is the same as out-of-service.
-
show syslog—do any of the real servers look like they are being failed and brought back into service? If so, for what reason? For TCP virtuals, Telnet from the default router or some device behind the router to the virtual address using the port number configured in the virtual or real statement. If the real is not responding, the LD will take it out-of-service immediately.
Related Information
| Updated: Jan 30, 2006 | Document ID: 18005 |