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

Node change not reflected in Orion?

Orion 7.2.2 SLX monitoring 6,000 nodes. Two HP Proliant Servers with 2x3.2GHz Xeon CPU, 4GB Memory, 3x75GB HDD. One for Orion, one for SQL.

We made a change today to one of our nodes that we are monitoring with Orion. We changed the interface name on the router, yet after waiting an hour, this is still not reflected in Orion. I've opened the node in System Manager and told it to rediscover the node, yet it still shows the old interface name.

I've also seen this happen when we have upgraded a circuit and changed the circuit speed of the interface on the router. It never is reflected in Orion. I always end up having to manually change it in the System Manager.

How come this is happening?

Find more posts tagged with

Accepted answers

All comments

iunderwo

The delay is based on the rediscovery interval. Interface speeds and descriptions are only read on a periodic basis, and not with every polling cycle...mostly due to efficiency, and most of that stuff doesn't change much.

// Ian Underwood - Service Management
// Level 3 Communications

rwbuckn

quote:Originally posted by iunderwo

The delay is based on the rediscovery interval. Interface speeds and descriptions are only read on a periodic basis, and not with every polling cycle...mostly due to efficiency, and most of that stuff doesn't change much.

// Ian Underwood - Service Management
// Level 3 Communications

Wouldn't the rediscover selected from node details do the same thing as the scheduled re-discovery but just on the single node?
What about the status of nodes? Are you seeing a change there? What happens when if you stop and restart the NetPerfMon service?
I see the same thing as well as node status polling stops. It's the same old thing that's been around for awhile. Interface status polling keeps on going but everything about the nodes stops. I have to restart NetPerfMon to recover. I'm running the latest code and still no difference. I'm running about the same size servers as you only more memory. Solarwinds response - buy another server and pay another 6 grand for a second polling engine even though I'm within their sizing specs, albeit at the very top end.

iunderwo

One thing that's more important than the node count is the total element count. 6,000 nodes is one thing, but the sheer number of elements will bring a server to its knees.

Rediscovery for interfaces needs to be done from the interface itself, not from the nodes. That's how I've gotten it to work. The occassional restart is necessary, still, when response time stats stop being recorded.

I've got about 2,200 nodes...but close to 11,000 elements, also a dual 3GHz machine...however, the standard polling interval SW uses is 9 minutes, so with a 5-minute polling interval, I'm running about twice the recommended element load. Another server would be nice, but the local PD wouldn't take to kindly to the kneeecap busting that would be required to get that approved. <sigh>

// Ian Underwood - Service Management
// Level 3 Communications

Network_Guru

What do you have your MaxStatsPolling set to ?
Have a look in SysManager under: File > Polling Status

Here is what mine looks like;

Orion Network Performance Monitor Version 7.2.73
Network Node Elements 593
Interface Elements 2211
Volume Elements 84
Status Polling Index 1353 out of 2976
Statistic Polling Index 2879 out of 5439
Polls per second 24
Polling Completion 99.12 %
Outstanding Polling SNMP Queries 60
Outstanding Discovery SNMP Queries 0
Max Polls Per Second 24
Max Stat Polls Per Second 24

Of course this varies quite a bit, but I do see the polling completion hit 100%
as well as the polls per second drop of to 0.
(I have set both Polls Per Second higher than the recommended value for this number of elements).

-=Cheers=-
NG