topic Peering with WAAS not managed by my CM - BAD. in Application Networking

Peering with WAAS not managed by my CM - BAD.

Tammy Cox — Wed, 17 Apr 2013 21:22:14 GMT

How can I prevent a WAAS appliance from automatically peering with another WAAS in the path that is managed by a different central manager.

Client-->Router1 w/WAE -->WAN --> Router2 w/SRE WAAS --> Router 3 Data Center w/WAE -->File Share Server

WAAS Associated with Router 1 and Router 2 are managed by their own CM.

WAAS associated with Router 3 is managed by a different CM.

We only want the Router 1 and Router 2 WAAS devices to optimize our traffic.

The WAAS associated with Router 3 is not WAAS we want to peer with, eventhough closer to the File Share Sever.

Peering with WAAS not managed by my CM - BAD.

ajayku2 — Thu, 18 Apr 2013 07:22:21 GMT

Hi,

One solution would be to bypass the traffic coming from your location on the ROuter 3 WAAS.

In can be done at the WAAS @ router 3 or By configuring wccp access list on Router 3.

regards,

Ajay Kumar

Peering with WAAS not managed by my CM - BAD.

Tammy Cox — Thu, 18 Apr 2013 12:59:52 GMT

That's not an option nor an acceptable solution - that would mean for every router/WAAS in the path (that isnt managed by my CM), I'd have to find the owner and somehow convince them that they need to change their environment. What are the options to control this from MY side? Is there a WAAS domain capability so that I can decide and contol the WAAS's that can be peering?