contactjt

Thanks for confirming. Just odd if you can stack a poller seems like we should be able to stack a web server.

my NPM is only 10.6, but my EOC which has the issue is 1.6

Yeah that's not good. This message usually indicates the poller isn't working. This needs to be fixed before we look at the the nodes themselves. General steps to resolve this: * Verify connectivity between the poller and the database * Verify the polling services are running see Orion Service Manager (Start Menu ->…

For NPM using SWQL the commands would be: SELECT CASE WHEN AStat.AcknowledgedTime = '12/30/1899 8:00:00 AM' THEN '' WHEN AStat.AcknowledgedTime != '12/30/1899 8:00:00 AM' THEN toString(AStat.AcknowledgedTime) END AS [Acked Time] FROM Orion.AlertStatus AS AStat

thanks

Right so could I just install a stacked copy to a separate install folder? I don't expect the single web application to handle SIWS to two NPM cores. My other option would be to dedicate one web server and the NPM web server for the first orion instance. Then the other web server and other NPM server for the second orion…

I think this may not be the correct NPM area, seems like this might be some old area.

No real progress. Basically the issue has become less relevant since it appears to just be a chart of nodes or elements you designate as VOIP. In my environment I have a custom property and I just made my own dashboards.

Well the idea is in a report I want to show null instead of the acknowledged time. FOR SQL this would be something like: SELECT Case [AcknowledgedTime] When '12/30/1899 8:00:00 AM' THEN null Else [AcknowledgedTime] End FROM [SolarWindsEOC].[dbo].[EOC_AlertStatus] Where Acknowledged = 0 Also FWIW I can get this to work on…

Go into the filters from Trap Viewer. Then look at the Trigger Threshold. It's pretty self explanatory.

I don't yet have one, I just saw this issue on Friday night. I can tell it's failing sometimes, but beyond that I can't tell why.

I'm on 10.6 because our 10.4.2 -> 10.6 was a nightmare. We need to get back on the upgrades here but 11.5 is just too big/troublesome for me to consider. I'm going to 11.0.1 this year but even that has 8+ hot fixes. I mean come on where is 11.0.2?

procedure stored.

To be honest I wouldn't worry too much if users are not complaining or you don't see a lot of web resources loading up slowly or timing out. The way the DB works is that the data is 'rolled up' from the detailed level with each poll (kept as detailed for 7 days I think by default). Nightly this rolls up this into hourly…

I want too but before I can I need to know if it's stable with 30k nodes, EOC, and FOE.

This is pretty close to what I need. At least it will cut off some questions. Ideally the whole tab can be removed. It was possible on 1.5, c'est la vie.

None is not an option though. In NPM I see none clearly. In EOC it's not in the list.

Thanks, I think this is close enough for what I was thinking.

I do see the page works better for me in Chrome. IE8 of course is our standard supported browser for our internal users. I still have my other issues of not being able to add any node because I hit a maximum request limit. It seems like this page pulls every node and interface. Then you check one and it takes that whole…

Yes essentially. Right now I have a load balancer site in front of them. If I have to I can change the design but the load balancer can redirect to any port I wish so I don't think it's unreasonable to have have the first NPM on port 80, and the second on port 8080 or maybe just on a different IP.

Any dimension info available? I'm guessing it's big enough for a pixel?

Very Useful, though I did add one poller to it. upsSecondsOnBattery 1.3.6.1.2.1.33.1.2.2

FYI I did open a support case 630538. They are researching how to increase this length. In the mean time I may have found my own fix. This page is poorly designed for large node or interface counts. This is what I believe is happening: Page loads each node and all available interfaces User selects an element to add in and…

There is a fast ping that starts on the first failure. On my system it's 180 seconds, I think it works out to and average time of half the polling interval + 180 seconds, then that is checked every 1 minute which could add some delay, then there is any email delay.

* Restart the pollers. * Verify if it's connectivity issue with snmpwalk. * Otherwise open a support ticket. I can help more if you explain what you mean by some of your nodes, and what no data means? Do these nodes show down? Is layer 3 working?

Moved to Orion SDK since I got no attention on the EOC forum. Support said yes this is supported but told me to come here for help. I am asking them for a working example but I am quickly losing hope that this is supported.

Dunno about the goal itself as the SWQL schema could change. As for which is faster I'd suggest SQL is better (possibly faster). Mainly because in SQL you can use with(NOLOCK) on joins an what not and this reduces blocking.

I can't even get the system to add my nodes. I wish there was a way to filter this list before the webpage pulls every node/interface

I'd like to know as well. I am considering 3.11 or 4.0 to deploy later this month or in June.

The polling seems to work OK for a while then start to fail. Still can't find specific issues. It seems like the Wireless Module (not used) starts to fail first, then the NPM module. Additional interesting messages in the logs are: 2015-02-22 07:34:42,502 [22] WARN SolarWinds.EOC.PollingService.JobsProcessor - Not…