Comments
-
Dsla, were you ever able to resolve this by any chance? I'm having the same issue. I would actually prefer that a new incident gets generated as our queues are kind of setup that if it were reopened, it may get overlooked.
-
I performed a SNMP-Walk on our Talari SD-WAN appliance using SolarWinds SNMP Walk tool. This created a text file of all the OID's responding from the walk of the device along with the output that the OID provides. I then Logged onto the Talari appliance and located the information I needed, in this case it was the serial…
-
Did you ever find the root cause for this? I'm ironically experiencing the same thing.
-
For those who may come across this in the future... After working with support we turned debugging on for the specific application template, reviewed the logs on the specific application template (each app template has it's own ID and can be found in: "C:\Programdata\Solarwinds\Logs\APM"), along with rebuilding the job…
-
Yes! We are currently having this same exact issue! Updated to 8.0.0.4 on our EMC Isilon's and both are showing as unreachable in NPM. We have our arrays added in via SRM. SRM test's the connection and shows everything as fine, but then lists it as unreachable. Extremely odd. I did also notice we now have a "Fraunhofer…
-
Is this after you have fully added the node into the managed nodes? What is your polling interval set to?
-
I know this is from over a year ago, but I've been able to get around this by just deleting the unknown NIC, performing a rediscover on the node, and then listing the nodes resources. My issue with this though, is that sometimes when I attempt to relist the nodes resources after doing a rediscover, it tells me that the…
-
The information provided by LadaVarga about adding the proper close codes within the Solarwinds properties of the SeviceNow integration, along with making sure that you have the "Reopen State" set to "None" within the trigger condition of the Solarwinds incident creation alert, resolved my issue.
