Basic WCCP troubleshooting: an simple example

Blog

Feb 21, 2011 1:31 AM
Feb 21st, 2011

It is difficult to write a document that is more complete then the troubleshooting WCCP entry However that document doesn't give a guide on how to troubleshoot WCCP.

In this post we will solve a basic WCCP issue and we will explain all the steps along the way.

Before I can show you the problem I need to fix out lab. We have a WCCP cluster containing cdn-wave-574-1 and cdn-wave-574-2. When logging in I see:

cdn-wave-574-1#show wccp routers 


Router Information for Service: TCP Promiscuous 61

Routers Seeing this Wide Area Engine(0)

-NONE-

Routers not Seeing this Wide Area Engine

172.16.1.1

Routers Notified of from other WAE's

-NONE-

Multicast Addresses Configured

-NONE-

and
cdn-wave-574-2#show wccp routers

Router Information for Service: TCP Promiscuous 61
Routers Seeing this Wide Area Engine(1)
Router Id       Sent To         Recv ID     KeyIP        KeyCN  MCN
192.168.50.45 172.16.1.1 0007FF4C    10.48.68.201   12063     21711
Routers not Seeing this Wide Area Engine
-NONE-
Routers Notified of from other WAE's
-NONE-
Multicast Addresses Configured
-NONE-
So on cdn-wave-574-1 we have a problem: we don't talk to the router.  First thing to check is the configuration:
cdn-wave-574-1#show run | i wccp
wccp router-list 1 172.16.1.1
! default wccp mask is src-ip-mask 0xf00 dst-ip-mask 0x0
wccp tcp-promiscuous router-list-num 1 l2-redirect mask-assign assign-method-strict l2-return
wccp version 2
no wccp flow-redirect enable
cdn-wave-574-2#show run | i wccp
wccp router-list 1 172.16.1.1
! default wccp mask is src-ip-mask 0xf00 dst-ip-mask 0x0
wccp tcp-promiscuous router-list-num 1 l2-redirect mask-assign assign-method-strict l2-return
wccp version 2
no wccp flow-redirect enable
That looks identical and thus ok. Can we ping the router?
cdn-wave-574-1#ping 172.16.1.1
PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data.
From 172.16.1.2 icmp_seq=3 Destination Host Unreachable
From 172.16.1.2 icmp_seq=5 Destination Host Unreachable

--- 172.16.1.1 ping statistics ---
5 packets transmitted, 0 received, +2 errors, 100% packet loss, time 4000ms
cdn-wave-574-2#ping 172.16.1.1
PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data.
64 bytes from 172.16.1.1: icmp_seq=1 ttl=255 time=0.404 ms
64 bytes from 172.16.1.1: icmp_seq=2 ttl=255 time=0.396 ms
64 bytes from 172.16.1.1: icmp_seq=3 ttl=255 time=0.448 ms
64 bytes from 172.16.1.1: icmp_seq=4 ttl=255 time=0.400 ms
64 bytes from 172.16.1.1: icmp_seq=5 ttl=255 time=0.813 ms

--- 172.16.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 0.396/0.492/0.813/0.162 ms
Hmm. Do we have a MAC for that IP?
cdn-wave-574-1#show arp | i 172.16.1.1
Internet  172.16.1.1       INV        00:00:00:00:00:00 ARPA  GigabitEthernet1/0
No we don't. Why?
cdn-wave-574-1#show interface GigabitEthernet 1/0  | i Link
Link State: Interface is up,line protocol down
Aha. No cable. Please note that the magic command also gives this information:
cdn-wave-574-1#test self-diagnostic all             
running test `basic'
running test `connectivity'
running test `interfaces'
running test `tfo'
running test `wccp'
running test `inline'
running test `system'
running test `wafs'
running test `application-security'

------------------------------------------------------------
Diagnostic Report performed on 2/21/2011 9:55:9

Test PASS  [basic]

Test PASS  [connectivity]

Test WARN  [interfaces]
     WARN  IFACE_LINK_DOWN  Interface GigabitEthernet 1/0 line protocol is down.
     Action:
     Check the cable connectivity to switch/router.


Test PASS  [tfo]

Test FAIL  [wccp]
     WARN  UNREACHABLE      WCCP router 172.16.1.1 is not reachable
     Action:
     Check if configured address is correct and/or there're no network connectivity issues.

     FAIL  UNREACHABLE      No WCCP routers are reachable
     Action:
     Check if configured address is correct and/or there're no network connectivity issues.


Test NONE  [inline]
     NONE  -                Skipping test because inline card(s) is not present

Test WARN  [system]
     WARN  HAS_ALARM        3 Major Alarms are raised in the device.
Please find the list below.
1.     WCCP router 172.16.1.1 unreachable for service id: 61.
2.     WCCP router 172.16.1.1 unreachable for service id: 62.
3.     The Flow Monitor control connection to the tcpstat-v1 console could not be (re)established after multiple attempts.

     Action:
     Critical/major alarms are raised. Check device alarms using 'show alarms detail' cli command for details.


Test NONE  [wafs]
     NONE  -                Skipping test because Wafs is not enabled

Test PASS  [application-security]
Next week we will handle a case of mistaken identity. See you then.
Average Rating: 0 (0 ratings)

Actions

Login or Register to take actions

This Blog

Posted February 21, 2011 at 1:31 AM
Stats:
Comments:0 Avg. Rating:0
Views:3801   
Shares:0

Related Content