Thanks for your reply Remi. Much appreciated. Static ingress replication looks easy and perfect for my requirements. I will have a vPC pair at each site so I assume I use a different loopback for the NVE on each vPC member and define both those as a static mapping at the other site. So each vPC member will have 2 x static ingress mappings. One for each vPC member at the other site. Apart from that the rest looks pretty straight forward and no multicast makes sense since I only have minimal VxLAN devices at 2 sites. I don't think I need the secondary loopbacks as shown in the diagram above. Is that correct? Thanks, Stuart. ... View more

Thank you for the reply.    However, I know that noise is external non-wifi energy and interference is wi-fi related energy.  Other AP's, smartphone hotspots etc.   What I'm trying to ascertain is specifically what the high bars on channels 1 and 7 are telling me and what are the percentage values related to.  On channel 7 the red bar is just short of 20%.  20% of what?  Are the values in the blue bars a point in time?  So is channel 7 seeing 45dBm of interference at the single point in time I looked at the stats?  Also, is it strange to see interference on channel 7 as opposed to channel 6 or is that an indication of something using channel 7 for wifi traffic? Channel 6 looks very clean in respect of interference.   Thanks in advance for any replies, Stuart. ... View more

Ok.  So I did some further testing today.   I simplified my access-lists to catch all IP traffic between the hosts I do the file transfer between.  This was in place before but I had only cut and pasted lines with ftp on them which gave the false impression the ACL's were applied incorrectly.   ip access-list extended WAAS  permit ip host 10.10.0.100 host 10.30.0.100  permit ip host 10.30.0.100 host 10.10.0.100   I use a route-map to reference the access-list   route-map WAAS permit 10  match ip address WAAS  set ip next-hop verify-availability 10.20.0.1 1 track 1  <- Track the WAAS being alive.   The track is up so we can discount that.   I then apply the route-map as a policy to the LAN and WAN interfaces on each router   Router-A interface GigabitEthernet0/0.10  description LAN  encapsulation dot1Q 10  ip address 10.10.0.254 255.255.255.0  ip policy route-map WAAS ! interface GigabitEthernet0/1  description WAN  ip address 10.0.0.1 255.255.255.252  ip policy route-map WAAS   On the WAAS subnet there is no policy   interface GigabitEthernet0/0.20  description WAAS subnet  encapsulation dot1Q 20  ip address 10.20.0.254 255.255.255.0   I do an identical access-list at the far end so it matches traffic in both directions.   ip access-list extended WAAS  permit ip host 10.10.0.100 host 10.30.0.100  permit ip host 10.30.0.100 host 10.10.0.100   And an identical route-map and policy.   route-map WAAS permit 10  match ip address WAAS  set ip next-hop verify-availability 10.40.0.1 1 track 1   Router-B interface GigabitEthernet0/0.30  description LAN interface  encapsulation dot1Q 30  ip address 10.30.0.254 255.255.255.0  ip policy route-map WAAS   interface GigabitEthernet0/1  description WAN interface  ip address 10.0.0.2 255.255.255.252  ip policy route-map WAAS   I don’t apply any policy on the WAAS subnet   interface GigabitEthernet0/0.40  description WAAS subnet  encapsulation dot1Q 40  ip address 10.40.0.254 255.255.255.0   On both WAAS I have interception method "none"   When I try to setup an ftp session it hangs.  On the client it sends 3 x syn packets but never sees a syn-ack.  On the server it never sees any of the 3 syn packets so I have to assume the syn is getting dropped somewhere.  I suspect at the 1 st WAAS   I looked in the WAAS syslog.txt file for the pattern loop and there is nothing.   To get the transfer working I do the following   Enable wccp on each WAAS as the interception method with the default gateway as the wccp router.   Then on both routers Ip wccp 61 Ip wccp 62   That’s all.  No redirection on any interface   As soon as I do that I see the following   Router A Dec 19 12:14:51.994: %WCCP-5-SERVICEFOUND: Service 61 acquired on WCCP client 10.20.0.1 Dec 19 12:14:51.994: %WCCP-5-SERVICEFOUND: Service 62 acquired on WCCP client 10.20.0.1 Router B Dec 19 13:00:19.372: %WCCP-5-SERVICEFOUND: Service 61 acquired on WCCP client 10.40.0.1 *Dec 19 13:00:19.372: %WCCP-5-SERVICEFOUND: Service 62 acquired on WCCP client 10.40.0.1   I then try the ftp transfer again and it works.  There is no WCCP redirection anywhere.  The PBR is only on the LAN and WAN interfaces to re-route traffic as it enters the interface and the interface to the WAAS has no PBR or wccp on it.   Similarly, when I try to map a network drive to pull a file across the drive mapping times-out until I put the wccp config on.  Then it maps immediately and I can pull my file across.  On the WAAS I see   ConnID        Source IP:Port          Dest IP:Port            PeerID Accel RR     67        10.30.0.100:20     10.10.0.100:56123 50:3d:e5:9d:5c:45 TDL   98.6%     68     10.10.0.100:56124       10.30.0.100:445 50:3d:e5:9d:5c:45 TGDL  98.8%   So I have a cifs and ftp session in progress and optimizing.   I then tried removing the wccp config from the routers but leaving the WAAS with interception method and it worked.  So the common factor here seems to be that the WAAS must have interception method wccp configured to use PBR.    Stuart.     ... View more

Finn   Accepted, the access lists were wrong.  However, I had just cut and pasted the ftp lines.  There were further lines below identifying the traffic by host address in both directions and this was catching the traffic.    The traffic was being optimized when I had the wccp part configured and wccp chosen as the intercept method.  I changed the interception method to "none" without changing the ACL's and that's what triggered the failure.  I also left wccp on the WAAS end and removed it from the routers to break the wccp connections and this caused the failure.  So my mistake for not including the full ACL entries but the issue still stands that the PBR works with wccp configured as the interception method but not with "none" as the interception method.  With "none" the ftp transfer hung. I didn't get prompted to log into the ftp server.  Similarly, I tried a cifs transfer and it hung.  Both failures resolved by setting up wccp even though I had no wccp redirection on the interfaces, just PBR.   I have some time scheduled in my lab tomorrow so will do some more testing and will confirm the ACL entries are sufficient to redirect the traffic.   Thanks again for your input.  It's much appreciated.   Stuart. ... View more

Finn   The setup has the WAAS on its own subnet at each site on a router sub-interface.  The LAN is on the same physical interface but a different sub-interface.  The WAN is on its own physical interface.  I only policy route on the LAN and WAN interfaces.   So at site A the traffic comes in the LAN on one sub-interface and is policy routed to the WAAS on a different sub-interface.  The WAAS returns the traffic to its default gateway's interface which has no policy routing applied.  The traffic is then routed to the other site.   At the other site the WAN interface policy routes the traffic to the WAAS on its own sub-interface.  It returns the traffic to it's gateway which has no policy routing and the traffic exits to the LAN.   If it makes any difference the WAAS CM is on this /24 but I don't see any issue with that.   Site A interface GigabitEthernet0/0.10  description LAN  encapsulation dot1Q 10 ip address 10.10.0.254 255.255.255.0 ip policy route-map WAAS   interface GigabitEthernet0/0.20  description WAAS interface  encapsulation dot1Q 20  ip address 10.20.0.254 255.255.255.0 ! interface GigabitEthernet0/1  description WAN  ip address 10.0.0.1 255.255.255.252 ip policy route-map WAAS ! ip access-list extended WAAS  permit tcp any any eq ftp  permit tcp any any eq ftp-data ! route-map WAAS permit 10  match ip address WAAS  set ip next-hop verify-availability 10.20.0.1 1 track 1   Site B interface GigabitEthernet0/0.30  description LAN interface  encapsulation dot1Q 30  ip address 10.30.0.254 255.255.255.0  ip policy route-map WAAS   ! interface GigabitEthernet0/0.40  Description WAAS and WAAS CM subnet  encapsulation dot1Q 40  ip address 10.40.0.254 255.255.255.0 ! interface GigabitEthernet0/1  description WAN interface  ip address 10.0.0.2 255.255.255.252  ip policy route-map WAAS   ip access-list extended WAAS  permit tcp any any eq ftp  permit tcp any any eq ftp-data   route-map WAAS permit 10  match ip address WAAS  set ip next-hop verify-availability 10.40.0.1 1 track 1   This fails to work.  All I do to get it to work is enable wccp config on the routers but no redirection on any interface.  I then enable wccp on the WAAS and tick the box to use the default gateway as the WCCP router. I could understand if I was doing wccp redirection in addition to PBR and that caused the problem.  But in this case it only works with wccp enabled with no redirection.    If I remove wccp config on the routers and choose interception method none on the WAAS the file transfer hangs.   I will need to go to my lab to see the logs you mentioned.   Thanks, Stuart. ... View more

Finn   Thank you for the reply.   However, I tried choosing none as the interception method with a PBR policy on my router and it doesn't work.  As a test I tried to start an ftp transfer but the connection hangs then times out when I try to connect to the remote ftp server.  Immediately I change the interception method to wccp it works so long as I have a matching wccp configuration on the router. I thought it might require an interception ACL so I created one with ip any any in it but still the same result.  It doesn't work unless I have wccp enabled.  I don't need to apply any wccp redirect commands.  All I have on the router is enough to enable service ID 61 and 61.  See below. ip wccp 61 ip wccp 62 On my router WAN and LAN interfaces I have no wccp configuration.  Only a PBR config   interface GigabitEthernet0/1  description WAN  ip address 10.0.0.1 255.255.255.252  ip policy route-map WAAS   interface GigabitEthernet0/0.10  description LAN  encapsulation dot1Q 10  ip address 10.10.0.254 255.255.255.0  ip policy route-map WAAS   So the redirection is happening with PBR but will not work unless wccp is there.  When I start the ftp transfer there are 0 packets listed as being redirected on wccp service 61 or 61 and the PBR route-map counters are incrementing.   Is this a possible bug ?  It seems strange I need wccp enabled but then don't use it for redirection.   Thanks, Stuart.   ... View more