aLTeReGo ✭✭✭✭✭

Much of the data SAM collects is retrieved via other protocols other than SNMP. SNMP is extremely limited, as most applications don't expose any information via SNMP.

Could the issue be disk I/O on the SQL server? That's what killed us when we brought NTA online. We had to move the Orion database onto a 4GB Fibre Channel EMC SAN RAID 10 volume built on 15k drives to relieve the I/O bottleneck that was created by adding NTA.

That is correct. It's assumed that most customers will utilize the same database server for NTA as the rest of their Orion modules.

PerfStack does not support sum/aggregation at this time. This is a feature request we are tracking internally under PS-1134.

The OID we are looking for when testing the SNMP community string through the "Add Node" wizard is the sysObjectID 1.3.6.1.2.1.1.2.0. If this OID does not respond with a properly formatted value the test/validation will not pass and you will be unable to proceed with adding the node to Orion.

Try enabling/configuring a port. Initial EnergyWise is about power consumption at the PoE port level and less the chassis level That makes sense, but even Cisco's non-PoE devices support energywise so how's that suppose to work?

I'm glad you were able to resolve the issue. I'll let the folks in infodev know. Thanks for bring this to our attention.

Alternatively you could simply install the Linux Agent and you would not need to do all these additional steps.

SAM has been available as standalone product since the APM 4.0.2 release several years back. Just like NPM you can mix and match modules. For instance you can install SAM and WPM together without needing NPM. Each Orion based product is now offered fully standalone. The only notable exception to that rule is NTA.

Can you both tell me what versions and SP you are currently on? I'm running NPM SLX v9.5.1

I agree with rharland2012. Since the Management Resource appears on the view, this looks to be a permissions issue with your user account not being granted rights to use the Real-Time Process Explorer. This can be remedied by editing your user account [Settings - Manage Accounts - Select your user account - click edit -…

The agent uses TCP Port 17778 for Active Mode, and 17790 for Passive mode. TCP Port 17777 and 1433 are used by the Additional Poller to communicate with the main Orion server (Information Service TCP Port 17777) and the backend SQL database server (MSSQL TCP Port 1433).

How are you sending this information to PagerDuty? Most customers send email notifications as their primary method of forwarding alerts from Orion to PagerDuty.

Is this node managed via SNMP? If so, you can change the method that is used to monitor status, availability, and response time via 'List Resources' from ICMP to SNMP. This may resolve the issue. If it's a server, a better option would be to install the Agent on that machine.

SAM/APM do not have to be in the same domain as the servers it's monitoring. The only requirement is that the Orion server be in the domain (or have a trust relationship with that domain) you want your users to authenticate against using their Active Directory credentials. This does not impact of effect APM/SAM's ability…

SAM uses WMI to collect information from hosts. Essentially the request for information is passed to the operating system. The underlying Windows Operating System makes the call for information to the remote host via WMI no differently than any other Windows application which utilizes WMI would. WMI is built on another…

That information is coming from the ESX host, vCenter or Hyper-V machine that is managed by Orion via SNMP, WMI or the Agent.

What you appear to be referring to is QoE (Quality of Experience) which for a short period of time was a licensable feature of NPM. QoE used the same agent framework but what customers were paying for was QoE, not the agent itself. The agent has always been a zero cost option, but features you use with the agent may have…

Sorry it took me so long to respond. I've been on vacation. I tried what you suggested and I'm still receiving the same error. Any other suggestions?

11.5.x is a release branch. SolarWinds has never released hotfixes for all variations of a particular release branch. It's simply not feasible, nor practical to do so. In many cases the prerequisites and interdependencies for the fix include changes that were made to the service release. Thus making a separate and…

When the WPM player is installed it creates several new local user accounts on the machine for the worker processes to execute under. These user accounts are SEUM-USER-1, SEUM-USER-2, etc. These local user accounts must have permissions to login locally to the Orion server. It's my belief that either these local Windows…

Without looking at the logs it's difficult to say for certain, but it looks like the application you're sending this alert to is rejecting the POST, rather than this being a limitation of Orion.

avrilspirit​ what Orion product modules and versions do you have installed?

Orion runs under the local system account. It does not use auto-detected proxy settings. You must manually define your proxy server IP, port, etc..

If you're using the Advanced Alert Manager then alert emails should not be re-sent unless the condition of the monitored object has changed.

Operating System is also a default field you can add to virtually any node report by default. No SQL or SWQL required.

If you or Kate were able to find a solution please post it here so the entire community can benefit. Thanks!

To register the Agent with Orion some form of authentication is required. Whether that's a user keying this into a terminal, or you use an automated mechanism like the one described above, some type of credential must be provided. You could certainly encrypt your answer file and then decrypt it as part of the output, such…

pratikmehta003 wrote:So it will report based on what the 'free' command has it on the Linux device end. Yes

Using repository from Orion accessible only via https with not trusted certificate When the Orion web interface is configured to use HTTPS, it uses some certificate. This certificate can be quite often be self-signed, and therefore not trusted. The recommended method to fix this is by adding Orion's web certificate to the…