Hi guys
This is my database server:
Web Server | VITALSTATISTIX |
Operating System | Windows 2003 Standard Edition |
OS Version | 5.2.3790 |
Service Pack | 2.0 |
| |
Database Server | 192.168.10.67 |
Catalog | SolarwindsData |
Database Engine | Microsoft SQL Server |
SQL Version | Microsoft SQL Server 2005 - 9.00.4035.00 (X64) Nov 24 2008 16:17:31 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.0 (Build 6002: Service Pack 2) |
Web Server VITALSTATISTIX Operating System Windows 2003 Standard Edition
OS Version 5.2.3790
Service Pack 2.0
Database Server 10.1.1.2 (fake)
Catalog SolarwindsData
Database Engine Microsoft SQL Server
SQL Version Microsoft SQL Server 2005 - 9.00.4035.00 (X64)
Nov 24 2008 16:17:31
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.0 (Build 6002: Service Pack 2)
and here is my polling engine details:
Polling Engine on VITALSTATISTIX
Engine Status Polling Engine Down
Type of Polling Engine Primary
Polling Engine Version Engine Version 9.1.0 - SolarWinds Orion Network Performance Monitor 9.1 SP5
IP Address 10.1.1.1 (fake)
Last Restart 23-May-10 05:04 PM
Last Database Sync 33 seconds ago
Last Fail-Over Never
Elements 8979 Elements
So, the problem here is that when you check under the admin settings on the webgui interface the polling engine status goes down/up/down within a matter of seconds, this causes false positives on our side and totally messes up the SLA agreements we have with our hotspots.
Everything was working fine (amount of elements are rougly the same as before the split) when the NPM and the SQL was running on the same box, but after the split this started happening.
Do you have any ideas where to start looking?