cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Cisco Community Designated VIP Class of 2020

Basic things to check on a WAE

2842
Views
0
Helpful
0
Comments
Cisco Employee

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;

.

CDN-WAVE-474-1#show accelerator 

Accelerator         Licensed            Config State        Operational State            
-----------         --------            ------------        -----------------            
cifs                Yes                 Enabled             Running   
epm                 Yes                 Enabled             Running   
http                Yes                 Enabled             Running   
mapi                Yes                 Enabled             Running   
nfs                 Yes                 Enabled             Running   
ssl                 Yes                 Enabled             Running   
video               Yes                 Enabled             Running   
wafs-core           Yes                 Disabled            Shutdown                      
wafs-edge           Yes                 Disabled            Shutdown

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) 144.254.10.123 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 (72.163.4.161) 56(84) bytes of data.
64 bytes from 72.163.4.161: icmp_seq=1 ttl=109 time=137 ms
64 bytes from 72.163.4.161: icmp_seq=2 ttl=109 time=137 ms
64 bytes from 72.163.4.161: icmp_seq=3 ttl=109 time=137 ms
64 bytes from 72.163.4.161: icmp_seq=4 ttl=109 time=138 ms
64 bytes from 72.163.4.161: 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

ConnID        Source IP:Port          Dest IP:Port            PeerID Accel RR  
   829       172.16.5.2:4568        172.16.2.2:445 00:22:64:96:eb:5c TCDL  97.8%

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.

Is the system overloaded?

CDN-WAVE-474-1#show processes system 
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
admin        1  0.0  0.0   1492   536 ?        Ss   Jan21   0:06 init
admin        2  0.0  0.0      0     0 ?        S<   Jan21   0:00 [kthreadd]
admin        3  0.0  0.0      0     0 ?        S<   Jan21   0:02 [migration/0]
...
29870 admin     30  10  286m  50m  13m S  0.0  1.8   0:01.93 java                                                       
29879 admin     30  10  447m 134m  21m S  0.0  4.7   0:02.81 java                                                       

procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id wa
0  0      0 134664 330180 1625988    0    0     0    12   13    15  2  1 97  0
1  0      0 134308 330180 1625988    0    0     0     0 1032  3032 16  8 77  0
0  0      0 134460 330180 1625988    0    0     0     0 1011  2197  2  2 97  0
0  0      0 134540 330180 1625988    0    0     0     0 1007  2021  0  0 100  0
0  0      0 134508 330180 1625992    0    0     0     0 1011  1948  1  1 99  0

We are only interested in the last few lines of output which show the vmstat output for this system. This is showing a rather idle system...

Not surprisingly this system seems to have no real problems.

CreatePlease to create content
Content for Community-Ad
FusionCharts will render here
This widget could not be displayed.