mdriskell ✭✭✭✭✭

If ICMP wasn't working you wouldn't get any node down/up events (regardless if they are in the past) Try this pick a node and go to the node details page. Look specifically at the polling details resource. What is the next poll time and what is the last database update?

I don't expect either of you to respond to this thread...not really in your realm of responsibility...However I'm tagging you so hopefully this can make it's way up the chain. This may be frowned upon and if it is I apologize but the new site gave us the ability to tag users so that's what I'm doing.

You can absolutely do that. I misunderstood your question. Create a copy of an existing node details view or an application summary view. Edit it the way you want showing exactly what you want. You can then assign that as either a default view for that application or node depending on what you want to accomplish under the…

What I did was to create a discovery using a list of all of my ancillary IP addresses. I let it discover all of them...then I added them to the ignore list. Bad news is you have to have a listing of all IPs on your routers in order to do so but if you have it handy try that.

There are SQL experts within these forums perhaps someone can assist with this. I was upset to learn that the backup DB was removed from this tool as well. While we have scheduled backups I always used this tool to do an on demand backup prior to an upgrade. Now I've had to engage our DBAs to do this prior to an upgrade.

As I understand it the Netflow information is sent based off of Layer 3 interfaces only so I don't believe you can filter down to this level on a simple switch port (now you should be able to report off that one machine's IP address however) Here is a link to Cisco's page on some netflow considerations.…

Here is an example of what I see. The first image is the last 25 events on the node details page of a device. The second image is from going to the events page and choosing the exact same device. You see in the second image that I have a T1 constantly dropping. In the first image I have no events since 8/31 although the…

Where are you making these changes?

Opened case 98037 regarding this issue. I will follow up here when I have a fix so others can apply if they have the same issue.

That's weird...I uploaded a new image and it changed the previous image I had submitted in my original post.

Ciscoworks can do it so i thought solarwinds might have a similar feature. Oooh Snap :D I could definitely use something like this. We are in the process of converting several hundred nodes from telnet to SSH so while in the conversion process this would be very handy. 

Edit the report in report writer. On the general tab near the bottom look for a checkbox called Group Historical Data by days. Uncheck that box, save, and retry the report in the webui. It's documented in this thread among others...I've had this bite me a few times. Message was edited by: Mike Driskell

Ok that clarifies it for me but doesn't solve my problem. I was looking for a scenario where I could upgrade without causing an outage.

Doesn't help the dependencies part but in your interface alert couldn't you simply add that the node status must be up in order to trigger? Also on the multilinks...the individual T1s make up the multilink not the other way around so the multilink should be up unless all t1s are down. 

Stephen you are right there isn't a way to do that as well and I'm under the same problem with our NOC. I would love to be able to give out granular control of say poll node but it currently isn't possible. Your second idea a custom watch page is intriguing and I could definitely see this as benefit as well.

Now I don't think this will handle any audit requirements because this is only active alerts...I never really found how to pull alerts that have already cleared.

Not a solution but a workaround...couldn't you script logging into the device and FTP the config to a separate FTP server. Doesn't give you any of the other features but would at least let you back up the configs.

This leads to a secondary question.....Nodes, Interfaces, & Volumes are all treated the same by NPM as they are all elements. That being said why is it when you go to the manage node page can you only search by Nodes & Interfaces. Not all users are comfortable doing a mass delete via SQL but without that option the only…

Thanks I will look for another client as I am using the one from the Additional Components section.

Brandon, I get a 403 forbidden error when trying to pull up that link.

I'l do this in our test environment first. I was just curious if anyone had done it before and how many tables I'll have to tackle.

JobEngine V2 will not stop using the service manager for me either. I had to kill the process using task manager before doing my repairs.

I did it yesterday and don't remember the sizes. As of right now the polling controller is around 200MB, the job tracker 75MB and the Job Engine V2 61 MB

So it happened a handful of times and I had to restart the services on the polling engine. Now if it's just WMI I'd try something else against that node to be certain.

I would state that WMI is more secure...It requires username/password to access whereas only SNMPv3 requires credentials. SNMP is limited as well as stated only pulling in basic information. Now that being said I believe there is more work to do from an overhead perspective by SolarWinds if WMI is used for all nodes.

Is this a windows process? If so I have a custom script to do just that.

You would need to do one of two things. If you are simply looking for STORM anywhere in the trap then add *storm* to the trap details tab of the trap rules. If you need to match specifically on those trap OIDs netapp.18825.1.1.6.165=STORMT_CCL_Bugzilla netapp.18825.1.1.6.168=STORMT_CCL_smt Then you would need to add to the…

Ok thanks...looking at the documentation again for the template pack it does show that on page 3. I had a printout of page 4 which said the only prerequisite was WINRM so I missed that. Also confusing is the APM template itself which states Specifies the TCP port for which this listener is created. WinRM 1.1 and earlier:…

Thanks, but I don't want to delete the discovery info I am using the topology data but we have some very large switching infrastructure so I broke down my scans...once I install 10.2 I will look at combining them into larger scans again.

No problem.....I was hoping others might find this beneficial.