WCCP - All Packets are "UNASSIGNED" - HELP!!!

Question

I just brought up a couple WAAS appliances up connected to my 6509 and it appears none of the traffic is getting redirected to my 2 WAAS devices. When I do a "sh ip wccp",all packets are unassigned. I am running 4.1.1b on the WAAS.
phx-core-sw-a#sh ip wccp
Global WCCP information:
Router information:
Router Identifier: 10.20.255.252
Protocol Version: 2.0
Service Identifier: 61
Number of Service Group Clients: 2
Number of Service Group Routers: 2
Total Packets s/w Redirected: 0
Process: 0
CEF: 0
Redirect access-list: -none-
Total Packets Denied Redirect: 0
Total Packets Unassigned: 427007868
Group access-list: -none-
Total Messages Denied to Group: 0
Total Authentication failures: 0
Total Bypassed Packets Received: 0
Service Identifier: 62
Number of Service Group Clients: 2
Number of Service Group Routers: 2
Total Packets s/w Redirected: 0
Process: 0
CEF: 0
Redirect access-list: -none-
Total Packets Denied Redirect: 0
Total Packets Unassigned: 12021424
Group access-list: -none-
Total Messages Denied to Group: 0
Total Authentication failures: 0
Total Bypassed Packets Received: 0
Config Snippets from 6509's - same on both
ip wccp 61
ip wccp 62
interface GigabitEthernet9/48
description Interface to WAN Router
ip address 10.20.255.2 255.255.255.252
ip wccp 62 redirect in
interface Vlan112
description File Servers 10.0.12.0/24
ip address 10.0.12.2 255.255.255.0
ip wccp 61 redirect in
************WAAS Config*********
device mode application-accelerator
hostname phx-waas-app-01
clock timezone MST -7 0
primary-interface PortChannel 1
interface PortChannel 1
description Port Channel to phx-core-sw-a
ip address 10.20.253.250 255.255.255.0
exit
interface GigabitEthernet 1/0
channel-group 1
exit
interface GigabitEthernet 2/0
channel-group 1
exit
ip default-gateway 10.20.253.254
no auto-register enable
! ip path-mtu-discovery is disabled in WAAS by default
ntp server 10.10.254.252
wccp router-list 1 10.20.255.252 10.20.255.253
wccp tcp-promiscuous router-list-num 1 l2-redirect
wccp version 2

Answer 1

Any improvment with the Mask-assign method? If it's still not working, I would do the following.
1. do "no wccp ver 2" on your WAEs. Let things set for a few minutes and then bring it back up. This will take down your acceleration, so be careful but will allow you to re-establish wccp if it's still attempting to use hash assign (default).
2. If it's not working yet, then clear the counters and let some traffic flow so we can see fresh info, and do the following on your routers.
sh ip wccp 61 detail
sh ip wccp 62 detail
and do the following on your WAEs
sh wccp gre
sh wccp router
And post it and we'll see what you get.
Thanks,
Dan