dethomas

Even with the ASA's with Firepower modules, you're only getting the ASA config, not the Firepower configuration, right? In our case, at least, we need to back up the FMC to get that and as far as I know we can't do that with NCM.

Thanks for the response. I do believe I've found my problem. My script was not populating the ChildURI field correctly. It didn't show anything amiss in the web gui when looking at the dependencies but when I looked at the fields in SWQL studio I could see the problem. I tweaked the script and recreated the dependencies.…

Thanks for the suggestions .... I'm seeing this on multiple switches but the one I am concentrating on at the moment is not POE. The hardware sensors are all 'up' except for 7 that are undefined. I'm not able to find the 'List Of Interface Charts' pictured above. Is that a specific widget that I can add? In any event I am…

I just ran the full script using the bulk delete instead of the individual deletes and I did have the same issue. I believe the bulkdelete did help but it seems like when I do something with the api the connection to the data base must be held open longer than expected so the pool is eventually depleted. 

I created a copy of the swisclient this morning and added the bulkdelete method you suggested. I tweaked the script to gather up all of the nodes to delete for a given node and then do a bulkdelete and so far it is working fine. Thank You!

Thanks! That sounds like it could very well be a practical solution. I'll give it a try as soon as possible and update you.

Thanks for the responses. I populated the property with a different value on a test node and 'Not Like' is working the way I need it to.

I think I just realized there is a fairly obvious solution, at least for this particular use case. I can create a custom property called 'Has_16.6.7_Image' and have the script make an API call to set the value of the custom property to either True or False.

I just ran into this issue the other day. I had the image file in the SFTP-Root folder. After removing it the upgrade took place as expected. The mechanism still seems a little strange though. Doesn't it imply that you cannot do multiple simultaneous upgrades? (Since it would start one upgrade and then the image would be…

Yes. The syntax is accepted but returns no nodes. But while typing this reply I think I may know why. In the case I'm working with the property is either populated with the given value or not populated at all yet. The Not Like is probably not matching when the property is not populated. I'll be populating the other values…

Thank you for the explanation. 

I don't think this is an issue any more. We have NPM 12.5 and it had no problem identifying our ISR routers.

I don't think I know exactly what you mean 'all sensor related events on interface / node'. I can say that I'm not seeing any alerts or events on either the interfaces or nodes. Screen shots below of an interface exhibiting this behavior (let me know if they don't show the relevant information). If the pattern holds, I'll…

If I'm following you correctly, that sounds like a very interesting idea. I could create an eem script to test for the existence of the file in question and then create an arbitrary oid that would return a value indicating whether the file existed or not. I'm eager to give that a try. Thanks.

Thanks for the suggestions. I'll be keeping them in mind for future use cases. For this one, I'm going with the 'custom property and have the script update that with the api' method.

We do have SAM, although I do not personally use it. I did look at the scripting capability there, but it didn't seem that it would work for what I want it for. I didn't see how the output of a script run by sam node could populate a value of multiple npm nodes. I could have a python script run on one of the linux sam…

Thanks. This certainly does sound like the same issue I'm running into. I'll look through the work arounds suggested there (and hope the bug fix is provided soon for a permanent fix).

Update on this: My problem has nothing to do with the 'When the parent goes down' setting. I was able to find the swql field that controls that, 'IncludeInStatusCalculation' and was able to verify that the dependencies I had created with the api had the field set correctly. So I'm back to having no idea what is causing the…

I'm pretty new to Solarwinds so may be making some basic mistakes but I don't seem to be getting accurate data here. I'm seeing the 'a' radios as up and transmitting data on AP's in which they've been intentionally shut down (and confirmed on the controller that they are shut down). And the client counts seem off. We have…

Update on this: Our server team restarted all of the Solarwinds servers this morning and the script it working again

I'm wondering if you ever found a solution for this. I have the same issue. I may have found the problem but don't have a scriptable solution. When you edit the dependency manually on the 'Review' screen there is a setting 'When the parent goes down:'. My dependencies are acting as if that is set the wrong way. I can't be…

I'm able to configure dependencies with an interface as the parent and node as the child. I'm on version 12.5 of the NPM if that makes a difference.