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

Continious Gaps in interface utilization Data

Hi Folks,

I have had a long standing problem with Continuous Gaps in interface utilization Data. I am now using 9.1 SP1 however I have seen this problem for at least the past three upgrades. I have opened several tickets, bought a new Terrabit SQL DB (RAID10) . I have 2 pollers each monitoring approx 300 nodes and no more then 6 to 7 thousand interfaces. I have tried everything I can think of but no matter what I do, the gaps continue. I have a very large group of application users who are now creating work around tools like MRTG and Cacti to get the data that should be available in Orion. Anyone care to take a stab at finally resolving this?

Find more posts tagged with

Accepted answers

All comments

jtimes

I haven't seen gaps since ver 7something, but without additional information about your polling completion rate polling frequency and charting rates etc, I would have to speculate that your gaps could be from having to many elements on an individual polling engine. I have eight active polling engines and the highest element count I have is around 5k on a single engine.

FormerMember

I am using 9.1 SP1 of Orion SLX. I have 2 polling engine and the SQL DB is external. I have 6 to 7 K interfaces on each polling engine, and atleast what I am hearing is that polling engines are supposed to be up to 8K.

Thanks I would love to compare notes on equipment to see if there is something in this environment that is different. The SQL DB is running SQL Server 9.0.1399 on a Win server 2003 SE (5.2 Build3790)

The Processor is an Intel- Xeon with 4 3.2GHz CPUs. 4 Gigs RAM.

C Drive "OS" is RAID 1
D Drive "SQL RAID 10 with about a terabit of disk space.

If I could compare the topology, perhaps there is something in this environment that does not work well. You mentioned 5 thousand node limits did you see a problem after 5K in the past?

I open support tickets, they age them out after 5 days then start a new ticket. so far iv'e been asked for the same information several times but no one from support has been able to step to the plate follow thorugh and resolve. The support for this anomaly has been terrible.

mhh351

I have over 21K of pollers on ONE polling engine. The application server is 2 dual core. The database is now on a 64bit SQL server that is also 2 dual core.

I have had gaps if I try to do all of the work in less than 10 minutes of statistics.

There are several things that I have been successful in tuning.

1. Make sure that your SQL database LOG file is being maintained at a rate of no more than 10 to 15 minutes increments. The log file can get too big and take a lot of time to maintain, thus causing delays in adding more info to the database. Your DBAs will probably cry about this but they will change it for you.

2. Make sure that you are NOT running on a SAN. While they are supposed to be fast, they actually cannot handle the rapid amount of smal bit data that Orion sends. If the Orion data gets behind several large packets, there will be degredation. We worked on that one for almost a year! Putting the DB on a physical drive on the DB server really helped.

3. Make sure that Orion is not re-discovering all of the network devices frequently. We use a one week algorythm that seems to help (10080 minutes).

4. Cut your SNMP and Ping timeouts way down. Most every device should reply in 1 second unless it is on a very slow link. Also, if there are devices that are known to be down for a length of time, consider unmanaging them. Orion will wait for an answer from each one. If the timeouts are set high, Orion just waits.

5. Make sure that the database has been maintained properly. If the database has not been re-orged or the files structure is fragmented, it will take a longer time for Orion to get confirmation that the data was processed.

There are just some of the things that we have run into. They are not meant to be the end all/be all answers. I just thought that some of them might help you. I hope that they do.

sedmo

The post at the link below indicates that each polling engine can handle about 1000 elements per minute. This means if you have a five minute polling interval then the polling engine will support around 5,000 elements.

mark_wiggans

You can reference this walkthrough as well.

http://www.solarwinds.com/support/orion/docs/gaps/gaps.htm

FormerMember

Thank you very much I will try each step and let you know

Mark

FormerMember

Hi Mark,

I tried every single step mentioned in "http://www.solarwinds.com/support/orion/docs/gaps/gaps.htm" however still have these stubborn gaps. I would happily take any advice to help get past this problem. Support pretty much has me repeating the same steps, then disappears for a few days then asks me to repeat the same steps and send diagnostics then goes back to step one. Its been a month. Any advanced help would really be appreciated.

BryanBecker

What's the LAN latency between your poller(s) and your DB server?