[c-nsp] WAE/WAAS in VRF environment

[Ramcharan, Vijay A]

My LAN and WAE interfaces are in the same VRF. They are aware of the
routes within my WAN vrf. The reverse is also true. My WAN vrf is aware
of the routes reachable via the LAN and WAE interfaces.  

I can ping from the WAE in one site over to the WAE in the other site
across the WAN without any problems. 
 
To recap, wae01 and router04 are in one site (with VRFs), while wae02
(ping source below) and the CM is in another site (no VRFs) across the
WAN. 

wae02#ping 209.1.1.2
PING 209.1.1.2 (209.1.1.2) 56(84) bytes of data.
64 bytes from 209.1.1.2: icmp_seq=0 ttl=62 time=52.3 ms
64 bytes from 209.1.1.2: icmp_seq=1 ttl=62 time=52.3 ms
64 bytes from 209.1.1.2: icmp_seq=2 ttl=62 time=52.4 ms

Vijay Ramcharan 
  
-----Original Message-----
From: Mike Louis [mailto:MLouis at nwnit.com] 
Sent: February 04, 2009 14:24
To: Ramcharan, Vijay A; cisco-nsp at puck.nether.net
Subject: RE: WAE/WAAS in VRF environment

How are you routing between your WAN and LAN interfaces today? Are you
leaking routes between the VRFs on the same router?

________________________________________
From: cisco-nsp-bounces at puck.nether.net
[cisco-nsp-bounces at puck.nether.net] On Behalf Of Ramcharan, Vijay A
[vijay.ramcharan at verizonbusiness.com]
Sent: Wednesday, February 04, 2009 2:19 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] WAE/WAAS in VRF environment

Is it possible to configure application acceleration using WAAS in a vrf
environment?

In other words, my WAN interface on the router is in a VRF, the LAN
interface is in another VRF and the WAE is on another VRF.

--------------------------
I have gotten as far as the WAE registering the router:
"WCCP configuration for TCP Promiscuous service 61 and 62 succeeded.
WCCP configuration for TCP Promiscuous succeeded.Please remember to
configure WCCP service 61 and 62 on the corresponding router."

wae01#sh wccp router
Router Information for Service: TCP Promiscuous 61
        Routers Configured and Seeing this Wide Area Engine(1)
                Router Id        Sent To        Recv ID
                0.0.0.0         209.1.1.1          0000022F
--------------------------

--------------------------
The router registers the WAE as a WCCP client:
router04#
"*Feb  4 18:56:09.892: %WCCP-5-SERVICEFOUND: Service 61 acquired on WCCP
client 209.1.1.2"
"*Feb  4 18:56:09.892: %WCCP-5-SERVICEFOUND: Service 62 acquired on WCCP
client 209.1.1.2"

The router however cannot figure out what its ID is and does not see
itself as a WCCP group router.
router04#sh ip wccp
Global WCCP information:
    Router information:
        Router Identifier:                   -not yet determined-
        Protocol Version:                    2.0

    Service Identifier: 61
        Number of Service Group Clients:     1
        Number of Service Group Routers:     0
        Total Packets s/w Redirected:        0
          Process:                           0
          Fast:                              0
          CEF:                               0
        Redirect access-list:                ACCELERATED-TRAFFIC
        Total Packets Denied Redirect:       0
        Total Packets Unassigned:            25957
        Group access-list:                   -none-
        Total Messages Denied to Group:      0
        Total Authentication failures:       0
        Total Bypassed Packets Received:     0
--------------------------

I will contact TAC shortly after this message (if our WAEs are still
supported).


Vijay Ramcharan
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Note: This message and any attachments is intended solely for the use of
the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, legally privileged,
confidential, and/or exempt from disclosure.  If you are not the
intended recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited.
If you have received this communication in error, please notify the
original sender immediately by telephone or return email and destroy or
delete this message along with any attachments immediately.