Because NPM 10.5 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!
Please add ability monitor nodes by SNMP ONLY and have them report as up and green in NPM! It seems like it would be easy to implement. Give the option when you add node of snmp only instead of just icmp and icmp + snmp. We have many areas we monitor with snmp across firewalls where icmp will NEVER be allowed due to tools that allow using icmp as a covert channel.
So has anyone got the new discovered nodes interface import wizard working? It appears that the wizard only works on the first one or two nodes. Maybe I just haven't spent enough time making it work, but I avoid it by selecting the interfaces from the found node screen, and that seems to bypass the interface dialog. It works unreliably and unpredictably as far as I can tell.
Yes, selecting trunk ports is important, but so is selecting access ports with more than 1 MAC in the bridge table. (Possibly more than 2 MACs if you use phones with in-built switch.) It would also be good to select all ports that see LLDP or Spanning Tree packets. Now THAT would be a useful import tool for us.
Now selecting certain interfaces by name would be useful, but combined with the node machine type. So if its a Ubiquity Networks wireless radio, I want the ath0 interface so I can monitor for traffic and errors. I think this is a virtual interface, so won't see MACs I'm assuming.
important feedback for us. We have no opened customer issues that it would work only for one or two nodes. Would you mind to open a support case for this? Maybe it's something related to your environment only, but we would like to investigate and fix.
Regarding the ports that may see LLDP or Spanning Tree packets, you can utilize regex statement if there is a certain rule on your interfaces (name, description, etc.) that may identify this. If not, we would have to add special polling into this discovery process in order to provide you more visibility into interface "responsibility". The complete list would be very useful here.
What are you trying to alert on in the traps? I have created several stored procedures to alert on traps sent from vSphere alarms and even Loadbalancer failovers, etc...
All done through SQL. Hit me up if you want to discuss.
I need to be able to alert when
TrapType like '%ospf%' and Traps.NodeID = '3357' and OIDName = 'ospfNbrState' and OIDValue = Down(1)
I also need to be able to alert when this OIDValue is flapping between 1 and 8
Setting it so that when using Solarwinds on an iPad it's permanently the full site view. Having this as a user option "Always show full site on a mobile device" would be great. Constantly clicking on Show Full Site gettings annoying.
Any chance that the F5 monitoring will include monitoring servers in the pools because as it stands the UI can be all green showing all it well with world but when you go and check on the device itself you can have pool members down.
I'm not sure if I saw this in another thwack thread but I think the ability to selectively choose what hardware health elements are monitored would be helpful. Especially with what happened when the feature was first introduced and SW was reporting hardware failures where there weren't any (primarily Cisco IOS bugs though).
For example, I have seen a device with a supposedly faulty PSU but this is actually a Cisco IOS bug. Until the customer upgrades the IOS, the only way for SW to stop reporting a problem is to disable hardware health monitoring for that device - there is no granular option.
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.