Comments
-
This is quite odd, i had not had a chance to get to this issue yet to try your suggestions, however i log on this morning and the error on this server is gone.
-
thanks for the suggestions guys, i will attempt them and post results as soon as i have them. thanks again
-
casey.carson take a look at this thwack post by mesverrum, it's a really nice resource and sounds like exactly what you need Node Downtime with Duration and Minimum Length Filtering
-
There should be an entry for it in the audit log, you can filter it by "Interface added"
-
If you turn on session tracing it will give you a little more insight as to what the problem may be. Here's a KB article for turning on sessions tracing Success Center- Generate Session Trace Logs
-
Do you have User Device Tracker (UDT)? NPM will only give you interfaces that you are currently monitoring so at the moment your two options would be to monitor every interface and then exclude certain ones from alerts then you'll be allowed to report on them. Alternatively if you have UDT then you can make them a UDT…
-
What is the object you are alerting on?
-
haroonh have you checked with the DBA to ensure that mixed-mode authentication is enabled for the SQL instance you are connecting to? I've seen this issue when mixed-mode authentication is turned off, or if you're typing the username incorrectly for the local SQL account
-
Thanks for the info and resources. appreciate you taking the time.
-
You could potentially create another Config Type in NCM, and then for the device template for Nexus add it as a config type and tell it to run this command. then you can create a job that does exactly what you want it to based off the new config type you created.
-
What is the device template that is assigned to it? Sounds like the "terminal prompt" value is not set appropriately for whatever device template it is trying to use, I've seen issues where it being left at Auto-Detect can cause issues with the commands being sent to it. Can you try to statically set the device template to…
-
can you post a screenshot of the alert logic and message? I have a feeling that the reason it looks like you're getting three separate emails is because of the way that your message or logic may be configured.
-
wahorn have you looked at the product upgrade advisor in your customer portal? this should tell you the upgrade path that you should use. Also, take a look at this article written by aLTeReGo How to Migrate Orion to a New Server With Zero Downtime This article may help you as well.
-
found this thread and it worked perfectly for me see below NCM & RegEx.... What am I doing wrong???? now im just trying to figure out how to ignore the ": Written" line for ASA's
-
i have the defaults and i am experiencing the same type of issue i have attached screenshots.
-
i am having the same issue. were you able to find a fix for this?
-
what devices is this happening on?
-
What is your backup solution?
-
quick question. If the node is "unmanaged" will solarwinds dump syslog messages it receives for that device?
-
i originally attempted to set this all up using the default UDP 514 port, and that was not working. so i started looking at other methods. i have configured my host to send syslog via the default port and am still not receiving the syslog messages. any thoughts?
-
Are you using Named-Pipes? I've seen this when using Named-Pipes, we re-configured to just use TCP/IP your connection string would look like this "IP_ADDRESS,PORT" when we did this I stopped having random connectivity issues like you're seeing.
