Troubleshooting WCCP

Two types of debug commands are available for debugging or troubleshooting a WCCP connection between a FortiProxy unit operating as a WCCP router and its FortiProxy WCCP cache engines.

Real-time debugging

The following commands can capture live WCCP messages:

diagnose debug enable

diagnose debug application wccpd <debug level>

Application debugging

The following commands display information about WCCP operations:

get test wccpd <integer>

diagnose test application wccpd <integer>

Where <integer> is a value between 1 and 5:

1. Display WCCP statistics
2. Display WCCP configuration
3. Display WCCP cache servers
4. Display WCCP services
5. Display WCCP assignment

Enter the following command to view the debugging output:

diagnose test application wccpd 3

Sample output from a successful WCCP connection:

service-0 in root: num=1, usable=1

cache server ID:

len=44, addr=172.16.78.8, weight=4135, status=0

rcv_id=6547, usable=1, fm=1, nq=0, dev=3(k3),

to=192.168.11.55

ch_no=0, num_router=1:

192.168.11.55

Sample output from the same command from an unsuccessful WCCP connection (because of a service group password mismatch):

service-0 in root: num=0, usable=0

diag debug application wccpd -1

Sample output:

wccp_on_recv()-98: root recv: num=160, dev=3(3),

172.16.78.8->192.168.11.55

wccp2_receive_pkt()-1124: len=160, type=10, ver=0200,

length=152

wccp2_receive_pkt()-1150: found component:t=0, len=20

wccp2_receive_pkt()-1150: found component:t=1, len=24

wccp2_receive_pkt()-1150: found component:t=3, len=44

wccp2_receive_pkt()-1150: found component:t=5, len=20

wccp2_receive_pkt()-1150: found component:t=8, len=24

wccp2_check_security_info()-326: MD5 check failed