WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000

5
<Tags> WCCP, WAAS, WAAS Configuration, Configure Catalyst 6500 with WAAS, Cisco WAAS on 800 Series Router WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000 The WAAS system consists of a set of devices called wide area application engines (WAEs) that work together to optimize TCP traffic over your network. When client and server applications attempt to communicate with each other, the network intercepts and redirects this traffic to the WAEs so that they can act on behalf of the client application and the destination server. You use the WAAS Central Manager GUI to centrally configure and monitor the WAEs and optimization policies in your network. You can also use the WAAS Central Manager GUI to create new optimization policy rules so that the WAAS system can optimize custom applications and less common applications. In this guide it shows example of how to configure Catalyst 6500 and Nexus 7000 with Cisco WAAS. Configure Catalyst 6500 with WAAS

description

WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000...More details...

Transcript of WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000

Page 1: WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000

<Tags> WCCP, WAAS, WAAS Configuration, Configure Catalyst 6500 with WAAS, Cisco WAAS on 800 Series Router

WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000

The WAAS system consists of a set of devices called wide area application engines (WAEs) that work together to optimize TCP traffic over your network. When client and server applications attempt to communicate with each other, the network intercepts and redirects this traffic to the WAEs so that they can act on behalf of the client application and the destination server.

You use the WAAS Central Manager GUI to centrally configure and monitor the WAEs and optimization policies in your network.

You can also use the WAAS Central Manager GUI to create new optimization policy rules so that the WAAS system can optimize custom applications and less common applications.

In this guide it shows example of how to configure Catalyst 6500 and Nexus 7000 with Cisco WAAS.

Configure Catalyst 6500 with WAAS

6500: 

access-list 1 permit host <wae1_ip>

access-list 1 permit host <wae2_ip>

!

Page 2: WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000

ip access-list extended WAASRedirList

remark

permit tcp host 10.189.240.44 eq www any

permit tcp any host 10.189.240.44 eq www

remark

!

Interface tunnel1

Ip address 10.255.255.253 255.255.255.255

Tunnel source loopback2

Tunnel mode gre multipoint

!

ip wccp 61 redirect-list WAASRedirList group-list 1

ip wccp 62 redirect-list WAASRedirList group-list 1

!

int <WAN_interfaces>

ip wccp 61 redirect in

!

int <LAN_interfaces>

ip wccp 62 redirect in

WAAS:

wccp router-list 1 <6500_1_loopback> <6500_2_loopback>

wccp tcp-promiscuous service-pair 61 62 mask src-ip-mask 0xf00 dst-ip-mask 0x0

wccp tcp-promiscuous service-pair 61 62 failure-detection 30

wccp tcp-promiscuous service-pair 61 62 router-list-num 1 mask-assign

Page 3: WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000

egress-method generic-gre intercept-method wccp

wccp version 2

 

Configure Nexus 7000 with WAAS

N7000:

ip access list WCCP-redirect

permit ip 10.0.0.0/24 any

permit ip any 10.0.0.0/24

deny ip any any

!

ip access list wae

permit ip 10.87.100.164/32 any

!

feature wccp

!

ip wccp 61 redirect-list WCCP-redirect service-list wae mode closed

ip wccp 62 redirect-list WCCP-redirect service-list wae mode closed

 

WAAS:

wccp router-list 1 <Nexus_1_IP> <Nexus_2_IP>

wccp tcp-promiscuous router-list-num 1 l2-redirect mask-assign l2-return

wccp version 2

Verify 

Page 4: WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000

Use command "show ip wccp " to check if the configuration is working or not. You can also use command "more system:running-config" in the IOS.

More questions from Cisco Support Community: What is the difference between mode open and close on the nexus?  I understand the default is open so why it is close for WCCP services 61 and 62?

Answer: Close mode on Nexus uses a service list to identify an access list (wae in our example) that defines packets that match the service. Open mode will match all traffic. This can be configured as per requirement.

Hmm.The Nexus configuration is actually wrong.

The "service-list wae mode closed" piece means:

If there is no WCCP client to which we redirect traffic, then all traffic matching the wae ACL will be dropped.

This not a replacement for the group-list argumnt on the cat6k.

From https://supportforums.cisco.com/document/128001/wccp-and-waas-configuration-catalyst-6500-and-nexus-7000#Configure_Catalyst_6500_with_WAAS

Question here: Cisco WAAS on 800 Series Router

I have got two routers, one is Cisco 892 and another is Cisco 881. Both of the router have got the required memory for cisco waas. I want to enable cisco waas express on both router and test waas function. I will keep 892 router at head office and 881 router at branch. 

1. Will it work with waas express on both ends? 

2. The current wan connection is done through Vsat and the minimum latency is 600 ms. How much optimization can I get on this type of link? 

3. When I apply waas on the wan interface at head office will other normal traffic (non waas traffic) come through the same interface? How will it differentiate between normal and waas traffic? 

Page 5: WCCP and WAAS Configuration for Catalyst 6500 and Nexus 7000

4. If I don't make any class map will the waas work by just enabling waas on wan interface ? How ?

WAAS Express to WAAS Express is not possible

You need at least one WAAS Appliance in one end-point, if you have multiple sites, you can have express in all of them. Anyway, the requirement is one WAAS Appliance, the rest of the end-points can have WAAS express or ISR-WAAS

From https://supportforums.cisco.com/discussion/12349741/cisco-waas-800-series-router

More Topics about the Cisco and Networking you can read at

http://blog.router-switch.com/category/networking-2/