Comments
-
Noted, we will look at this for a future release
-
Let us know if you see this behavior continue
-
OK, I am running 9.5 and tested this and you can do this in 9.5. I have a node in ICMP only right now, if I go to web node management and edit that node and deselect (ICMP (ping only) checkbox, I am now given option to enter SNMP values
-
There is also a permission checker utility in the program files Orion directory you can run
-
Do you mean version 10.1.2?
-
Stacy what do you want to show in there?
-
Yes it is completely supported. With the intro of UAC and the extra security settings in 2008 and 2008 R2, permission are a lot tighter than say 2003, but we have supported 2008 for over a year now.
-
Can you share this report you wrote with the community please.
-
Agree on the integrating into webpage, however, we wanted to get something to ya'll in this release to help with these items. Based on time and effort, this was a good first step.
-
Take a look at the scheduler tool, in essence that is what we are doing. When you create a job take a look at the output from the editor, it looks something like this <?xml version="1.0"?> <Job xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:xsd="">www.w3.org/.../XMLSchema"> <SwisConnectInfo Server="CBL-002-WIN2003"…
-
Can you tell me exactly what you are doing to create this behavior? If possible attach a screenshot
-
Yes Windows 2008 and 2008 R2 are fully supported. (2008 R2 supported was added in NPM 10.0). Orion just requires 32 bit support since it cannot yet fully leverage all the resources of a 64 bit box
-
I can log it as an enhancement request into the system
-
Have you seen these advanced alerts we wrote? See here, here and here. These should help if you assign to a couple devices on each of your polling engines
-
This is for sure something we are looking at for a future release
-
What type of information are ya'll interested in seeing and showing?
-
You may be able to create this with custom SQL, you can look at this thread for another wireless custom report to start from, see here
-
I have not heard this, can you send me your support case number so we can look into
-
We have a buddy drop which we believe addresses this issue. If you log a case with support, they should be able to give you a download to it.
-
I have not heard his report from other users or coming into support, but we will dig into it regardless. If you haven't already, please open a support ticket.
-
Correct, we support the entire Nexus line as well as Cisco UCS, see here for more info
-
Are you trying to use Windows pass-thru? What version of Orion are you on?
-
This tutorial might help, see here
-
Understood. We put message center there as a step in the right direction, but not the end all solution. The broader solution will take longer and is more complex.
-
Also, as a temporary workaround until we release the fix, you should be able to use the old discovery engine, which can be launched by navigating to <drive>/Program Files/Solarwinds/Orion/NetPerfMonDiscovery.exe
-
Not sure what is going on then, I would recommend a support ticket to investigate further.
-
When you upgraded to 10.1, did you use the one you installed from 10.0 or the one in the Program Files -> SolarWinds Orion menu?
-
We are currently in beta on this, see here for more info on that release
-
I chatted with Dev and added this as an item to add/address in the Orion Syslog server. One item you can do it send it to Kiwi Syslog and then forward up to Orion
-
Hard to tell looking at the error message. Are you getting other items in the windows event log or just the alert engine? Have you tried going through and disabling alerts to see if that is causing the issue till you can get a support ticket and rep to look at it.