In this post we will discuss how to check a WAE that you want to investigate.
If you have a suspission that a certain WAE might be causing problems I suggest that you log on to the device using the CLI.
Most of the following commands can be issued via the GUI on the CM but that will be a lot slower.
The output bellow comes from a WAE in our static lab, so the output is for a working, but quite idle WAE. I'm not giving examples for a failing system because these commands fail in an obvious manner.
The first thing I do on a WAE is to check for a number of basic things, like:
CDN-WAVE-474-1#show license License Name Status Activation Date Activated By -------------- ----------- --------------- -------------- Enterprise active 06/30/2010 admin Video active 07/01/2010 CMS Virtual-Blade active 07/01/2010 CMS
This is because without a license everything will work, but without acceleration.. Then there is;
This shows the normal situation for a non-legacy device and all AO's are operational. Next we have:
CDN-WAVE-474-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/1/2011 15:8:24
Test NOTE [basic] NOTE NO_NTP_CFG Device ntp time synchronization is not configured Action: Use 'ntp server' cli command to configure NTP server.
Test FAIL [connectivity] FAIL UNREACHABLE Domain-name server(s) 22.214.171.124 is not reachable Action: Check if configured address is correct and/or there're no network connectivity issues.
NOTE - Unable to check whether device hostname is resolvable because name servers are not configured/reachable
Test PASS [interfaces]
Test PASS [tfo]
Test NONE [wccp] NONE - Skipping test because WCCP is not enabled
Test PASS [inline]
Test PASS [system]
Test NONE [wafs] NONE - Skipping test because Wafs is not enabled
Test PASS [application-security]
This very useful command just runs a number of tests on your setup.
As you can see it gives warnings even on known working devices.
The NTP warning is very interesting. The WAAS system will work without it, but in a sane setup you really want NTP setup on all your devices.
The FAIL for the connectivity test is because the DNS server does not react to ping.
In our network this is normal, DNS name resolution does work:
CDN-WAVE-474-1#ping www.cisco.com PING origin-www.cisco.com (126.96.36.199) 56(84) bytes of data. 64 bytes from 188.8.131.52: icmp_seq=1 ttl=109 time=137 ms 64 bytes from 184.108.40.206: icmp_seq=2 ttl=109 time=137 ms 64 bytes from 220.127.116.11: icmp_seq=3 ttl=109 time=137 ms 64 bytes from 18.104.22.168: icmp_seq=4 ttl=109 time=138 ms 64 bytes from 22.214.171.124: icmp_seq=5 ttl=109 time=138 ms
--- origin-www.cisco.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3997ms rtt min/avg/max/mdev = 137.395/137.698/138.120/0.303 ms
Next we check if the device is doing something useful:
CDN-WAVE-474-1#show statistics connection
Current Active Optimized Flows: 1 Current Active Optimized TCP Plus Flows: 1 Current Active Optimized TCP Only Flows: 0 Current Active Optimized TCP Preposition Flows: 0 Current Active Auto-Discovery Flows: 0 Current Reserved Flows: 10 Current Active Pass-Through Flows: 0 Historical Flows: 103
D:DRE,L:LZ,T:TCP Optimization RR:Total Reduction Ratio A:AOIM,C:CIFS,E:EPM,G:GENERIC,H:HTTP,M:MAPI,N:NFS,S:SSL,V:VIDEO
So the device is seeing and accelerating traffic. Maybe there were some alarms?
CDN-WAVE-474-1#show alarms history detail
Op Sev Alarm ID Module/Submodule Instance -- --- -------------------- -------------------- -------------------- 1 C Mi servicestop nodemgr actastor_watchdog Jan 26 14:07:17.824 UTC, Processing Error Alarm, #000004, 2000:330006 nodemgr: The actastor_watchdog service stopped on request.
2 R Mi servicestop nodemgr actastor_watchdog Jan 26 14:07:07.520 UTC, Processing Error Alarm, #000004, 2000:330006 nodemgr: The actastor_watchdog service stopped on request.
3 C Mi servicestop nodemgr nscd Jan 26 14:05:08.453 UTC, Processing Error Alarm, #000001, 2000:330006 nodemgr: The nscd service stopped on request.
4 R Mi servicestop nodemgr nscd Jan 26 14:04:56.811 UTC, Processing Error Alarm, #000001, 2000:330006 nodemgr: The nscd service stopped on request.
Op - Operation: R-Raised, C-Cleared Sev - Severity: Cr-Critical, Ma-Major, Mi-Minor
We are not using show alarm because sometimes the alarms are temporary and you want to see recent alarms too.All of these look normal.
Hello,we have a UCS mini implementation with a pair of FI6324s and we would like to acquire a pair of Nexus switches which will be strictly used for the interconnection between the FIs and 3 Netapp AFF C190 Storage Arrays. The blades (four actually) are B...
Hi All, Is there any CLI command available on Cisco ACI Leaf to check the live traffic statistics on particular interface...as like we are checking with IOS / NX-OS with "sh interface eth1/2" This command is working on Leaf But not showing...
I'm trying to find some documentation for the MDS9148S Switch that proves the support of the following port types: F_Port (Fabric), M_Port (Mirror Port) and E_Port (Switch-to-Switch). I easily found F_Port and E_Port:Fiber Channel standard port types...
I am trying to find out where zoning changes are logged to. For example, an admin creates a new zone, adds it to the active zoneset and commits the changes (we usually do this via CLI). A little while later we get a report of an issue and...
Hi Cisco experts, I need your help to understand why the VRFs have to be configured with a set of "route-target both auto" and "route-target both auto evpn" in a Fabric with VXLAN BGP EVPN. Knowing that the Fabric can work normally with a set of ...