karltbraun

Also: don't have time to figure out how to find the ticket (Portal is broken, won't display existing tickets, I've been told it's my problem even though it happens with all browsers including IE 7) and attach the results. Clues would be appreciated.

Nope. But you made me look. -ktb

At present, we are presuming this is a bug in the Colubris firmware, and are taking it up with HP. I will update when we have more information on this. Thanks for your help so far.

Mav, We don't have NCM (but I'm considering looking into that). But #3 seems to be what I was looking for. Don't know why I didn't think of that. Thanks for getting back to me. -ktb

I will be opening a ticket on this this afternoon (WED-11-JAN) or tomorrow.

Thanks for this. I hadn't stumbled upon that. And I appreciate your pointing it out to me. But to Solarwinds I have to say: This is one of the most bogus features of an NMS I have seen - a real hack job. I have to go to two places to schedule this. Length of time in the utility, time to start in Task manager, and yet…

You know, I forgot I had that passed on to me already. A cursory glance indicates it's going to do the trick. I'll reply further if I need additional clarification. Thanks,

I'm sorry, but I don't know what "Look up for the URL" means.

Case #Case #259728

Correct except the last line: it's not "node down", it's "child" (interface) down (if the interface de-selected is in fact down). In other words: Why is the node showing interface down when the interface that is down is not being monitored?

Right, so if I don't want to actively monitor them, I ignore them. Then what. They seem to hang around in the discovery results forever.

Has there been any updates to this? (Really: how can you build query options and not have a "is not/does not" version of each of these options? It's basic logic.)

Any updates on adding HP MSM's? We've deployed NPM at an all HP shop, and we have many sites with many dozens of APs controlled by WSM's and MSM's.

Thanks, Just what I was looking for. -ktb

I hadn't thought about that, but that makes sense. Of course the DB is going to be filling up with obsolete interfaces. But I'm afraid your solution is not practical. If I understand you, you're telling me I need to memorize those node/interfaces that are repeating and just don't process them in the Scheduled Discover…

I'm sure that's mostly true, but after you try to import these newly discovered interfaces, and it checks the database and says "nope, already in there', it still keeps the newly discovered interfaces as waiting to be processed. As far as I know, at this point, you have two options: (1) keep them in the…

Yes, and not to be snippy, but when I said "I updated my credentials", that's what I meant. I even created a new credential with the correct password and that didn't work either.

Anyone? Bueller? Anyone? *crickets*

I just want to add myself to the list of those who want something like this. I would like to know what nodes are added to discovery for the last <period of time>. I think this is an import review point. Is there nothing that provides that kind of information?

By the way, before I added the node manually, IPAM knew of the device and had a last response time of within the last few hours. Device was originally discovered, but for reasons I won't go in to, I deleted the nodes so that they would be rediscovered, and found that they wouldn't discover. This was several weeks ago. I've…

I wonder if it would be possible to get a reply from Solarwinds on this?

*bump*

This is what I was looking for - thanks very much. I would have thought that the way to make this assignment was more granular, but this really helps.

Any updates on this?

*bump*