Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

TCP Port 25 Monitor - very high response time

Hi guys,

We seem to be having an issue with our CAS servers, as noted by the TCP Port 25 monitor template. We have it configured as follows:

The two servers we seem to be having an issue with is across the pond in The Netherlands. Our Orion server is in Canada.

At times, we are seeing very high response times (in the 3000ms range). It fluctuates, and then back down to normal. This will occur for awhile on one server, and then it will happen on the other CAS server. When reviewing the health of the server, CPU/Memory consumption is normal for a CAS server. The queues aren't getting flooded. I have PerfMon counters watching SMTP receive counters (however, I don't have SMTP send counters configured) and not seeing one CAS server receiving more than the other.

Can someone explain why I may be seeing this? Or, better yet, how this monitor actually works and what it's really measuring?

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

The monitor depicted in the image above is a simple TCP port check that could be mimicked by telneting to an open port "telnet some.server.com 25" for example would duplicate this monitor. It's a very basic check, unlike some of our more sophisticated user experience monitors. The high latency may be occurring due to a connection limit imposed by the server itself, or transparent proxy or firewall between the SAM server and the monitored host. This long wait.... is normally what you'd see when there are no more connections available. The server does not actively refuse it so the session stays open until a connection is made or the timeout value is reached.

vpbcarder

Thank you.

I find it hard to believe that we're experiencing this issue in our remote Venlo site since there is a lot more activity in our Windsor site (we have CAS servers in Windsor, and also this is where the Orion box sits). Something tells me this is network related.

My ask: Is there any way to adjust this monitor (or create another one) to notify us ONLY when the connection drops? High latency is a big deal but I'm thinking it's more important for us to know when the connection drops all together (perhaps, due to service stoppage or back pressure).

Thanks in advance!

aLTeReGo

If you're only concern is with application up/down status then simply remove the warning and critical thresholds defined in the monitor. E.G ensure the highlighted fields below are blank for this TCP Port component monitor.

Response Time Warning and Critical.png