Its very easy to identify your WAE is overloaded or not. Just have to run few commands and observe the outputs which are highlighted as below.
#sh
statistics con(On Cisco WAE)
•
•Current
Active Optimized Flows:
5960-->nearly equal to connection limit
• Current Active Optimized TCP Plus
Flows: 5609
• Current Active Optimized TCP Only
Flows: 349
• Current Active Optimized TCP Preposition
Flows: 0
•Current
Active Auto-Discovery Flows:
23
•Current
Reserved Flows:
40
•Current
Active Pass-Through Flows:
1260
•Historical
Flows:
585
•
#sh
tfo
detail(On Cisco WAE)
•
• Policy Engine Config
Item Value
• ------------------------- -----
• State Registered
• Default Action Use Policy
• Connection Limit 6000
•Policy Engine Statistics
•
-------------------------
•
Session timeouts: 0, Total
timeouts: 0
•
Last keepalive
received 00.4 Secs ago
•
Last registration occurred 417:10:10:06.7 Days:Hours:Mins:Secs
ago
•
Hits: 1693419791,
Update Released: 886466302
•
Active Connections: 5960,
Completed Connections: 476081344
•
Drops: 0,
Pre-Resource Counter: 21
•
Rejected Connection Counts Due To: (Total: 342344669)
•
Not Registered : 0,
Keepalive
Timeout : 0
•
No License : 0,
Load Level : 0
•
Connection Limit : 342344669,
Rate Limit : 0
•
Minimum TFO : 0,
Resource Manager : 0
•
Global Config : 0,
TFO Overload : 0
•
Server-Side : 0,
DM Deny : 0
•
No DM Accept : 0
No comments:
Post a Comment