aLTeReGo ✭✭✭✭✭

If you are running SAM 6.2 and VMAN 6.2 DataStores should be an available property type to alert upon when using the Web Based Alert Manager.

You can set it either at the application level (one IIS server) or at the template level (all IIS servers).

Same issue here, unresolved. Do you have any additional pollers in your environment? Have you upgraded to APM 4.2? Have you opened a case with support, and if so, what's the case number?

Sounds like something may have been missed when you cleared out the HA tables. I would recommend opening a case with support so we can determine the cause.

I've taken the liberty of putting Petr.Vilem's hard work above into an Orion Report Writer report which can be downloaded at the link below.

Not even close. Though SNMP "Get Table" is a great feature that is lacking in the current custom MIB poller, this feature could not by any means serve as a suitable replacement or substitute for the Wireless Network Monitor.

Have you tried adding copying those jar files to the "C:\Program Files(x86)\Orion\APM\jmxbridge\lib" directory on the Orion server? Keep in mind that this may also require modifications to the "SolarWinds\Orion\APM\jmxbridge\jsl\jsl.ini" file. Also note that any changes made should be done while the JMX Bridge Service is…

I would need to see the script itself as well as the script output (result) before I could determine the cause of the error. From the sounds of it though, it seems like the value returned is a string where an integer is expected.

The following MSDN article outlines the Default Windows PowerShell limits, as well as how to change them via GPO. To define these quota limits manually, type winrm set winrm/config @{<Quota>="<Value>"}. For example, to increase the maximum number of shells per user from 5 to 7, type winrm set winrm/config…

You can use ODP.NET or download the Oracle Database Client for SAM from your customer portal. Either one can be used with the Oracle User Experience Monitor. I do prefer and recommend the one available through the Customer Portal over ODP.NET though, as it's easier to install and configure properly and ODP.NET.

I will defer to jreves on this, as he is the Product Manager for NTA. To my knowledge, there are no 'combined' database server system requirements for NPM+NTA that I'm aware of. Hopefully, Joe can confirm when he returns from Cisco Live next week.

SAM uses nearly 50 different protocols to gather information, including WMI, RPC, VMware API, SOAP, SSH, ODBC, and many more. If you haven't yet tried SAM out, I would recommend doing so. You'd be amazed at what you are missing.

What exactly happens when we fill in those fields for the proxy? Is there some extra configuration applied to the agent during install? Filling in the fields shown below allows you to generate a transform file (MST) that can be used in conjunction with the installer (MSI) to pass configuration settings to the installation…

Thank you for clarifying . I didn't mean to call you out. I just wanted to ensure there was absolutely zero confusion for or anyone reading this thread.

Not off hand, but this is very high on our "to-do" list, as it will need to be done before legacy charts are deprecated.

The telecom guy has limited knowledge of what to configure on the S8700 in terms of SNMP settings. We've tried a few different things, but so far we've been unsuccessful adding the S8700 as an SNMPv2 node in Orion. Attached is a screenshot. First of all you can see the "Master Agent Status" is "up". No idea what that means…

Indeed, this works precisely as you describe above njoylif‌.

It's possible. This would need to be a custom SQL report though that filters the APM_HardwareInfo table from the Nodes table using the NodeID in the table join.

That is now how it functions today. That would be a feature request.

The most likely cause would be Network Sonar Discovery. Either you have a scheduled recurring Network Sonar Discovery running that is creating the events, or someone is manually kicking off an Network Sonar Discovery. 

Based on your screenshot above it looks like the volumes are coming from VMAN. E.G. the Component Volumes resource is a VMAN specific resource. Is this VM managed as a node in Orion? What does the Volume Details look like on on that node? Secondly, the report query you are using should be on "Volume" not on "Node".

Manual installation works essentially the same way. The only difference is how the Agent itself gets on to the machine.

Thanks xpowels​. I have retrieved the logs and have created case OA-972 internally for investigation.

You can filter the event log so those events don't clutter your view, allowing you to see the "wood". A possible workaround to the issue would be to manage the node in Orion via SNMP instead of WMI, and using RPC fetching methods for application component monitors where available. Optionally, you can also open a case with…

You can invoke virtually any command you wish using the Alert Manager's external command option. There's no requirement to use the OOTB actions.

Without seeing the actual events themselves it's hard to speculate with any degree of accuracy as to what it is you're seeing. Node status and Node status alone is determine by ICMP (Ping) One ping is sent every 2 minutes by default. If a node misses a single ping it is placed in a warning state and fast polling begins. If…

If the glassfish Node in Orion is managed using SNMPv3, then that is indeed your problem. The SNMP settings for the Glassfish application must match those of the node identically.

Before writing a script I would actually try adding a new Windows Service Monitor manually, configuring the service name appropriately manually using other Windows Service monitors as a guide, and then changing the fetching method to use RPC instead of WMI. There may be an issue using WMI with this host for some reason.…

Monitoring of the Array Controller was not implemented in SAM 5.0. It's currently a feature request we're tracking under FB103915. As for the disk information reporting logical volumes and not physical disks, this was likely an oversight that I'll get logged.

Can I suggest instead of pursuing this template that you upgrade to the SAM 6.1 Release Candidate? It includes AppInsight for Exchange which replaces this application template entirely, and is extremely simple and straightforward to setup and configure.