aLTeReGo ✭✭✭✭✭

ift_mcg wrote: That's what I am wondering if all Orion machines are on Server 2016 and DB OS is running at 2012 R2, what could be impacted if we just upgrade our Orion products only. The database server operating system is irrelevant. If you are running SQL 2016 on Windows Server 2012 R2, that is perfectly fine. Orion only…

Correct. Polling timeout for the application as a whole will terminate the connection attempt and mark the components inside the template as down if there was no response from the host. We're currently working on updating the chart resources in SAM, and the availability resource in particular will get quite an overhaul.…

dunky2k It looks like you need to simply confirm that you've backed up your database, and temporarily disable High Availability to proceed. The other two are warnings that can be ignored. As for the other Polling Engine, you may need to install the offline hotfix bundle to that machine without internet access. That can be…

Version information is located at the bottom of any page within the web interface.

Anything polled via Windows Performance Counters can be similarly polled via WMI. Again, if your primary concern is security then the Orion Agent is hands down your best bet as it requires zero listening ports on the monitored host.

Do you also have NPM installed on this same server? If so, what version? E.G. Do you have a "Network" tab at the top of your Orion web interface next to "Home" and "Applications"?

Is there NAT going on? WMI will not traverse a NAT except under special circumstances where your firewall vendor provides WMI helpers.

If possible, I would suggest clicking the "Configure Server" button again to see if that resolves the issue. In the off chance it does not and you're not agent adverse, I would try using the Agent to see if that works better for you.

SAM 5.0 supports native polling of 64bit WMI counters. RC3 has already been provisioned in your customer portal so you can upgrade APM to SAM 5.0 immediately to resolve this issue.

In order for the both SQL and WMI information to be collected the node must be managed in Orion using WMI. You cannot collect WMI information using AppInsight for SQL if the node is managed via SNMP.

The default action is RESTART, but as you can see below it's not possible to restart a stopped service. You can only start it.

The change would need to have occurred through (using) IPAM for an event to have been created, but this is likely a topic better suited for the IPAM forum.

The .674 OID is reserved for Dell so it can't be available anywhere else. It's likely the MIB has not been loaded properly by the SNMP daemon on the server. I would recommend restarting the SNMP daemon on the server to see if this resolves the issue. If that doesn't work I'd recommend contacting Dell for further assistance…

That is correct. These Linux nodes do not have the 'City' Custom Property assigned to them, which is why they are under the 'Unknown' grouping. This can be added by editing the node or going to the Custom Property Editor and populating this value.

Double check to ensure that these accounts are all using the same Reports folder. Beyond that, and possibly account restrictions I'm at a loss for ideas. I'd recommend opening a case with support if neither of these pan out.

What module(s) do you have installed?

Proxy To make wget use a proxy, you must set up an environment variable before using wget. Type this at the command prompt: set http_proxy=http://<i>proxy.myprovider.net:8080</i> ...where you use the correct proxy hostname and port for your ISP or network. You can use ftp_proxy to proxy ftp requests. --proxy=on --proxy=off…

There is already an out of the box alert titled "Alert me when a node goes down". I would recommend using this alert as-is or copying this alert and adding an additional condition to the trigger. Out of the box alert - Alert me when a node goes down Out of the box alert with additional vendor condition. I've also posted…

Give NET-SNMP a try. You can download and install NET-SNMP from http://net-snmp.sourceforge.net/ • Win32 binaries are available here: http://sourceforge.net/projects/net-snmp/files/net-snmp%20binaries/5.5-binaries/net-snmp-5.5.0-1.x86.exe/download • Example command from “installation directory /bin/”: snmpwalk -v 2c -c…

I'm glad you were able to figure it out! Thanks for following up and letting us know what you found.

It just occurred to me that we recently updated this template. Attached is the latest version of that template. Please delete the template from your server and import this one in its place and give it another go. Let me know if that resolves the issue.

Correct, and in the instance of a "Counter" the "Count Statistic as Difference" option should be used. The difference is that there is no math being performed on the number beyond polling for the value twice and subtracting the first value from the second. It's not possible to get the "per-second" value without first…

You can create a report and place it on an application details page as a report resource specific to that application using Application views so the report doesn't show up on other application details pages. You can even add a report resource to the component details page, but keep in mind that the component details page…

Once the nodes have already been added to Orion the simplest option is to change the polling method as described above. The Network Sonar Discovery Wizard can be used for importing newly discovered VMware ESX/ESXi hosts en masse into Orion.

Do you happen to be running Orion on 64Bit Windows? I've seen this same problem when trying to run Orion on Windows Server 2003 Enterprise SP2 64Bit edition. Orion 8.0x does not run under 64Bit windows. Orion 8.1 should run under 64Bit windows, but that is currently in beta.

What version of NPM are you running? Can I assume when you click 'List Resources' on either of those nodes, Hardware Health is not listed as an option?

Try this one: Trigger Alert when all of the following apply MIB is equal to ..... field Status is not equal to value ok Last line is a complex condition, Status is from Custom Node Pollers. Thanks for your help. You're honestly full of some great ideas but I'm afraid this one didn't work either. Sorry. got any other tricks…

There is really no harm in rebuilding indexes. Depending upon the size of the table this process could take as little as one second for a table that's a few kilobytes in size, or several hours for a table that's several hundred gigabytes in size. Obviously the speed of the processor, amount of RAM, and speed of the disk…

Reading through the case notes joedissmeyer​ somehow fixed his issue on his own with exportable certificate key, but unfortunately he did not share with us how this was done.

What you are referencing above is for node baselines, which function differently than application baselines.