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
Home
Products
Network Performance Monitor (NPM)
RFE: Rediscover on Reboot
iunderwo
One thing I've noticed in using SWNPM, is that the SNMP index of most devices rarely, if ever changes. However, I have noticed that some changes happen after a system reboot occurs and interfaces get reindexed.
The idea would be to run a rediscovery when a reboot has been detected, instead of a specific defined interval. It might lighten the load on some servers w/ lots of SNMP nodes.
// Ian Underwood - Service Management
// Level 3 Communications
Find more posts tagged with
Accepted answers
All comments
hez
Hi,
I've the opposite problem. we have ZyXel DSLAM's. and about every time they reboot, there seems to be a rediscovery going bad, so that the InterfaceIndex is changed in the NPM DB. which it should'nt as the InterfaceIndex on the DSLAM is Persistent. They are always built from slotid-portid. So that Port 12 in slot 2 is always InterfaceIndex 212. From the event log, it looks like this is related to the Dslam starting the card's in a "random" order, and that the discovery goes bad from polling the Interfaces to early. I would guess that if I could postbone the rediscovery of interfaces 1 minute after the DSLAM has reboot'd everything should be fine ?
Currently only monitoring about 150 interfaces, but considering going up to 1500 and the hazzle of stopping the DB, and correcting the Index's will be BAD..
Anybody has some suggestions to approaching this ?
/heZ
BryanBecker
If you have a Cisco device....they have global and interface commands to keep the indexes the same (persistance) even after a reboot :
Global : snmp-server ifindex persist
Per Interface : snmp ifindex persist
That should help.
BB
hez
Sadly enough Cisco has had a very limited productline regarding xDSL soluitons the last year's. So we've ended up with Zyxel IES series DSLAM's.
And Indexes are persistent just not while rebooting the DSLAM's.
This is what end's up in the Event Log :
dslam-slot-2, Port 20 - Physical Address changed from 00A0C5C19B54 to 00A0C5D69751
dslam-slot-2, Port 17 - Physical Address changed from 00A0C5C19B54 to 00A0C5D69751
dslam-slot-2, Port 21 - Physical Address changed from 00A0C5C19B54 to 00A0C5D69751
dslam-slot-2, port 6 - Physical Address changed from 00A0C5C19B54 to 00A0C5D69751
These are the mac-addresses of the line card's.
Quick Links
All Categories
Recent Posts
Activity
Unanswered
Groups
Help
Best Of
