03-10-2010 10:13 AM - edited 03-11-2019 10:20 AM
We receive alerts from Solarwinds whenever the a threshold is reached, for example:
Node SRU-FW1.salve.edu has an average response time of 333 msms which falls above the 200ms threshold
Is 333 msms way to high? acceptable etc.. Any points to what to look for in troubleshooting would be much appreciated
We are running 8.2(1) on a ASA5520-K8, 512 MB RAM CPU pentium Celeron 2000 MZH
Thanks
03-10-2010 01:37 PM
If you are pinging the ASA check its cpu while you see the slow response.
If the ASA has high cpu it could explain the issue.
300ms is high, of course it all depends how many hops are in between.
You can also do a packet capture on the ASA to look at the icmp packet timestamps to see if the ASA delays to respond or if there is something in the middle that delays it.
PK
03-10-2010 07:52 PM
topo:
asa--router1--router2--router3--router4---and so on ---
ping from the asa to router1 and record the time.
ping from asa to router2 and record the time
ping from asa to route3 and record the time.
See where the time increases and get intouch with the folks who maintain that device and see what might be going on.
-KS
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide