How to use Cisco Router WCCP debug commands for WCCP troubleshooting

Products

ProxySG Software - SGOS

Issue/Introduction

Warning

The following Cisco router debug commands should be used with CAUTION! The use of these debug commands can cause a router performance hit if the debugs are left running. Remember to disable all debug commands after using.

To disable all running debug commands:

undebug all

Example

Router# undebug all

All possible debugging has been turned off

To verify that if any debug commands are running on the router use the following command:

show debug

Example

Router# show debug

WCCP:
WCCP packet info debugging is on
WCCP events debugging is on

Telnet Usage Note

If you telnet to the router you will need to use the Terminal Monitor command to see the debug output messages on the telnet console. If you are using a serial console connection on the router, the debug messages will be shown without the need of the Terminal Monitor command.

Example

Router# terminal monitor

debug ip wccp events

To display information about significant Web Cache Control Protocol (WCCP) events, use the debug ip wccp events command in privileged EXEC mode. The no form of this command disables debugging output.

debug ip wccp events

no debug ip wccp events

Command Modes

Privileged EXEC

Example

The following is sample output from the debug ip wccp events command when a ProxySG is added to the list of available Web caches:

Router# debug ip wccp events

WCCP-EVNT: Built I_See_You msg body w/1 usable web caches, change # 0000000A

WCCP-EVNT: Web Cache X.X.X.3 added

WCCP-EVNT: Built I_See_You msg body w/2 usable web caches, change # 0000000B

WCCP-EVNT: Built I_See_You msg body w/2 usable web caches, change # 0000000C

debug ip wccp packets

To display information about every Web Cache Control Protocol (WCCP) packet received or sent by the router, use the debug ip wccp packets command in privileged EXEC mode. The no form of this command disables debugging output.

debug ip wccp packets

no debug ip wccp packets

Command Modes

Privileged EXEC

Example

The following is sample output from the debug ip wccp packets command. The router is sending keepalive packets to the ProxySG at X.X.X.4 and X.X.X.3. Each keepalive packet has an identification number associated with it. When the ProxySG receives a keepalive packet from the router, it sends a reply with the identification number back to the router.

Router# debug ip wccp packets

WCCP-PKT: Received valid Here_I_Am packet from X.X.X.4 w/rcvd_id 00003532

WCCP-PKT: Sending I_See_You packet to X.X.X.4 w/ rcvd_id 00003534

WCCP-PKT: Received valid Here_I_Am packet from X.X.X.3 w/rcvd_id 00003533

WCCP-PKT: Sending I_See_You packet to X.X.X.3 w/ rcvd_id 00003535

WCCP-PKT: Received valid Here_I_Am packet from X.X.X.4 w/rcvd_id 00003534

WCCP-PKT: Sending I_See_You packet to X.X.X.4 w/ rcvd_id 00003536

WCCP-PKT: Received valid Here_I_Am packet from X.X.X.3 w/rcvd_id 00003535

WCCP-PKT: Sending I_See_You packet to X.X.X.3 w/ rcvd_id 00003537

WCCP-PKT: Received valid Here_I_Am packet from X.X.X.4 w/rcvd_id 00003536

WCCP-PKT: Sending I_See_You packet to X.X.X.4 w/ rcvd_id 00003538

WCCP-PKT: Received valid Here_I_Am packet from X.X.X.3 w/rcvd_id 00003537

WCCP-PKT: Sending I_See_You packet to X.X.X.3 w/ rcvd_id 00003539