Cisco WAAS Prepositioning 0.0 bytes Copied........ :-(

Question

Good Evening All,
I am having my first attempt of using the prepositioning function within Cisco WAAS running version 4.1.7a and its not going very well at all.........:-(
We are trying to test a preposition of Microsoft Updates to a selection of Branch WAE devices but the "Amount Copied" is constantly sat on 0.0 bytes and never changes.
Clearly i am doing something wrong and im hoping someone can advise, basically i create the Preposition task via the CM (also running 4.1.7a), i see the root folder i need (which has further subfolders benieth it) and select the folder, i submit this and it takes this with no problem, i assign the branch WAE's to this and its also submitted and accepted, i select schedule for "Now" and the preposition appears in the statuc tab however no matter how many hours its left it constantly sits at 0.0 Bytes - Clear something is wrong.
Doing a "Sh run" on the branch WAE it sees the preposition task at the end of the config but still nothing. I am assuming this is down to the fact that the Data Centre WAE is not loading the files in the "staging" area, the Data Centre WAE has flows for the chosen Server when you do a "sh stat con" and can ping the server by name and ip address.
Im at a lost of what to check next, we are not running the "legacy" WAFS as we first started running 4.1.3b and recently upgraded to 4.1.7a.
Can anyone help......??
Thanks in advance
Craig

Answer 1

Hi Mike,
Thanks for your quick reply on this, i have a feeling you may have hit the nail on the head already with your first comment...... Doh.
Ill give you an example of how the branch site is setup:-
e.g. (not actual addressing used but gives you the idea)
Branch Site
int vlan 10
ip address 10.10.10.1 255.255.255.192
ip wccp 61 redirect in
int vlan 11
ip address 10.10.10.65 255.255.255.192
ip wccp 61 redirect in
int fa0/1
description *** BRANCH WAE WAAS Device ***
ip address 1.1.1.5 255.255.255.248
Int se0/1/0
172.1.1.1 255.255.255.252
ip wccp 62 redirect in
ip wccp 61 redirect-list 161
ip wccp 62 redirect-list 162
access-list 161 permit tcp 10.10.10.0 0.0.0.127 192.168.1.0 0.0.0.255
access-list 162 permit tcp 192.168.1.0 0.0.0.255 10.10.10.0 0.0.0.127
Data centre end:-
This access-list is then replicated but in data centre but with the access-list 161 & 162 swapped - the 192.168.1.0 subnet is acting as the Data Centre server subnets.
In the data centre the WAE will have an address of say 172.21.1.5 255.255.255.248.
Is there any risk/implication of including the ip address ranges of the WAE devices themselves? currently we dont do this on any site where we have a WAE device and we are seeing great benefits still but i guess this will explain why the prepositioning is not working as the devices are not matching the ACL and therefore being denied redirection.
Cheers
Craig