As always, since NPM 10.3 has been released recently we are already working on the next release of NPM. Here is a preview:
PLEASE NOTE: We are working on these items based on this priority order, but this is NOT a commitment that all of these enhancements will make the next release. We are working on a number of other smaller features in parallel. If you have comments or questions on any of these items (e.g. how would it work?) or would like to be included in a preview demo, please let us know!
Hi, we are monitoring such request. It would be great if you could create an feature request here on thwack so other users may support that.
BTW: UDT is terrific.... We implemented and before I could train anyone, it was getting huge praise from all departments nationwide.
Easy to use, and very informative.
I'm glad to hear about the better F5 support. Particularly helpful would be the ability for NCM to login to the LTM, save the config to a .ucs file and then back up the .ucs file. Since the .ucs file has all the elements required for a successful restore, that would be nice.
I would think the #1 priority would be increasing the SLX unlimited to truely unlimited, as in more than 12,000 Elements.
We have Juniper MX960 sw/routers with 4,000 interfaces, 22 CPUs and 14 vendor MIBS. there are 2 in each site node we activate.
Guess how many I can fit on a single SLX license?
This has made our system of 12 NPM polling engines completely unscalable.
Everytime I add a node, I have to delete 6,000 interfaces manually or log into the Database and running a SQL to find all the MX960 intefaces, delete any that are listed as secondary.
struggling to make more than 4 fit on one server.
Our network has over 1,000 devices to be monitored, With 6 more nodes with 2 MX960s in them before the end of the year. bringing the total to 1,160 devices.
I heard there were vast increases i the 10.4 release... The tern used was Super Poller - True or untrue?
Example of my server counts for just interface elements, this is after I went through all of them and deleted any interfaces that I could.
Unfortunately, I can't add all 12 IPs to each device ACLs so the # 4 servers are the router/switch servers the MX has to go on and #5 is a backup, If it ends in V the poller is on a virtual server.if not it's a standale.
Verizon VoIP and CSS7
How many Elements total ???
I hate to say that again Solarwinds need "engineering guide" that will have best practice and max.
Solarwinds couldn't have the scalability of HP openview or other "big shop" software that can run 25,000 elements and 1,000,000 interface per server.
I'm happy that I don't have 20,000+ node in my network and keep I NPM.
12 Servers X 12,000 elements = 144,000
Currently, we have 35,487 elements on the entire system, 2 servers are at zero and just installed and not in any ACLs or the IDN firewalls.
Currently Total Server Utilization would be 25% Elements (one is a hot standby, one is for another organization and thier Cisco 3020 switches)
So the total number of servers dedicated to VoIP networks is 10.
10 X 12,000 = 120,000
35,487 total elements currently w/additional 18,000 by year end for 2012 total of 53,487 (give or take a few)
Of the 18,000 elements approx 12,000 of which will be the new MX960s.
So by Year End my total server utilization will be 45%
Servers of necessity had to have only 3 server IPs per device type (1 of which is the hot standby) due to the limits of some device ACLs. So essentially, we have 2 servers for firewalls, 2 for Routers, 2 for Switches, 2 for Border Controllers or 24,000 elements per device type.and the hot standby.
Some servers can contain many more devices, than others.due to the number of interfaces on those devices, Universal MIBS (i.e., Vendor MIBs) account for very few of the total elements monitored.
The new Juniper MX960 switch/router upon discovery has 4,000 interfaces of which roughly only 960 or so are useful physical interfaces, the remainder are signaling and media VLANS assigned to customers. This forces me to go into the interfaces and delete the specific (3,000 or so) one's not needed so that I can recover element space on the server I add the device to.
So essentially most of my servers are being used at <20% I have 3 that are above 75% and if I had to stick with the 3 IPs for the new MX960 switch/routers I'd be screwed.
I've managed to talk both engineering and operations into adding 2 more server IPs for these new devices giving me 4 pollers and 1 standby server dedicated to just 1 device type of 6. This is not Solarwinds fault. But, I'm extremely hopeful that the new release will greatly increase the element count on my SLX (unlimited) licenses. If not, some form of IP load balancing device will have to be placed between Solarwinds servers and the networks.
This is my tale of woe.
Thanks for listening
That sound bad.....
We have more den 10 MX960 but they don't have so many subinterface.
What is running in does subinterfaces that is so importent ?
When we had some Juniper E router that is a BRAS that has alot of pppoe custemeres we had problem to discover the physic GE/XE/AE because there where so many pppoe subinterface.
By the way how your SQL cope with 33K ?
I have 30 MXs now with another 6 before the end of the year.
GE/FE/XE/AE/LC/IP/and a few more..
On my hottest server I have a mix of Juniper M10i and MX960s. Total Element count right now is 8,146 after deleting out unnecessary interfaces.
Viewed via the Node Manager thats 33 pages of 250 interfaces on one server.
Based on that this server can add 2 more, maybe 4 MX960s, add 1 Delete interfaces, add the second delete the interfaces to keep it below 12,000 elements.
But the last one will discover 4000 and push the elements to 14-15K before I delete the unneeded interfaces. Just for my own morbid curiosity, after List Resources ran, I manually deleted 3,200 interfaces, takes about and 30 mins and would give me Carpal Tunnel pretty quick.
Could you comment on the status of:
9. Better handling of duplicate nodes - same devices with multiple IPs
I have been looking forward to this feature for many releases.
this is something already available in NPM 10.4 beta 1 - http://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2012/07/20/npm-104-bet...
you may install that on your non production server and give us your feedback.
#8 Support for audit trail.
I am hoping that this is relevant to a ticket that I submitted: Case # 355722 - Feature Request - Events do not show what user made changes in Orion.
I have noticed that under Alerts, Orion does correctly log what username (and to my surprise was granular enough to determine within a Windows Domain) has acknowledged an Alert. My request regarding this ticket was to add support of this type of logging to the Event Log page as to determine what user has made a change in Orion. (add/remove node/interface, change status etc). This would add accountability to individuals who have access to make changes in Orion and are not documenting information correctly/completely.
We have Orion NPM SLX with 3 additional pollers and approximately 20,000 nodes on our network. We have about 25 individuals with access to modify data in Orion and it is incredibly frustrating to track down who is consistently mucking up our database when there is no record of who made what changes.
yes this what is this feature about. You can try it in our NPM Beta 2 where it is already partially implemented (take a look on the message center). We are looking forward for your feedback.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.