aLTeReGo ✭✭✭✭✭

The following KB article should get you pointed in the right direction. https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/Migrating_an_Orion_Platform_Product_Installation_-_Video

Have you tried uninstalling the Agent from the Orion server itself?

400 errors in almost all cases are indicative of an issue or problem that should be addressed. I say almost because your use case is obviously an exception. I recommend using the TCP Port Monitor for port 80 instead of the HTTP User Experience Monitor since this component monitor type doesn't honor HTTP error status codes.

The resulting output of the query used in the Oracle User Experience Monitor must return a single numeric value, with an optional message field.

Try changing "Numeric Status" to "Rate" or "Status"

I would recommend using the following templates instead. Linux/Unix File Size Monitoring Linux/Unix Directory Size Monitoring

The error code 0xc0000064 means that the specified user does not exist. To fix it, modify the "Xen" credential in SAM and add in your domain prefix. E.G. doman\xen.

Did you configure WinRM on both the Orion server and the host running NetBackup? CONFIGURING WINDOWS REMOTE MANAGEMENT (WINRM) * If not already done so, install PowerShell 2.0 and WinRM on the SAM and target servers. Powershell 2.0 can be found here: http://support.microsoft.com/kb/968930. * On the SAM server, open a…

QoE helps identify whether the performance issue is related to network latency, bandwidth congestion, etc. vs. slow application/server performance. In your case the web application performance is not due to network latency since that accounts for only 1ms. The majority of the time spent waiting was on the application…

It's likely that you'll need to either add or remove a ".1" or ".0" to the end of the OID to specify exactly what you're after. From what your describe it sounds like your polling a valid branch but not the value. The simplest way to test/verify is to use the MIB Viewer from the Engineers Toolset to validate the OID your…

By application do you mean Windows Service?

From what you describe it sounds like the Orion server is unable to SSH to that machine. You can confirm this by installing Solar-Putty onto the Orion server and attempting to connect to that server.

The following thread includes automating the configuration of the Linux Agent Deploy agents with Chef or Puppet

The credentials used to push the agent to the machine are never used by the Agent thereafter. You can change the password for that account after the Agent has been deployed and it will have zero effect on the agent.

Is the remote registry service running on the monitored server? I've seen cases where the Remote Registry service is stopped for some reason and this causes the polling issues you describe.

SAM 6.2 beta can be installed standalone for beta testing, or in conjunction with the NPM v12 beta. SAM 6.2 is still beta, and as such should not be installed on top of your production Orion installation. I believe this is the reason why you are receiving the error that you are.

Offhand looking solely at the charts themselves it's impossible to say for certain, but it's my guess that one is showing the average based upon the sample interval and amount of historical data loaded. The biggest difference in the charts are the timeframes. On appears to be loading data from "today" while the other looks…

Have you tried using the Custom Object resource to add the resources you want to display to the summary view you are creating? Another option is to use the Custom Table resource to add information to the view similar to how you would a report. You can even create your very own custom resources in Orion using the Custom…

You would need to contact VMware, or disable monitoring of this sensor under [Settings -> Manage Hardware Sensors].

In cases such as these, changing how the ESX host is polled from vCenter to Direct usually resolves this issue. This is because of a VMware issue with the VMware API that does not affect the CIM protocol that is used for monitoring hardware health from ESX hosts polled directly.

Orion Platform 2019.2 includes the ability to automatically delete these 'unknown' volumes. For more information, check the link below. https://thwack.solarwinds.com/docs/DOC-204353#jive_content_id_Automatic_Removal_of_Unknown_Volumes

If you post a MIB Walk from the device I would be happy to take a look and see if the information is exposed such that a template or Universal Device Poller could be created.

I'm not aware of this being a change in behavior. While that's certainly possible, it's certainly not something that's changed in the last few releases. I can though, see how this would be annoying and not necessarily the most desirable behavior. As such I've logged this internally under SAM-7119.

The error here is that the Oracle client itself has thrown an exception for some unknown reason. A quick Google search indicates that this isn't that uncommon of an issue. I'm not an Oracle Expert, but I play one here on Thwack. My suggestion is to use the Oracle client available under the Additional Components section of…

There's really no method of determining the SQL server edition without some form/type of credential being stored in the Orion database; be those SQL credentials, Windows Credentials, or the SNMP community string.

- Is there any way to increase the 10 output limit? There is no way to exceed the 10 output pair limit in SAM. The recommended solution would be to break this up across multiple scripts. It's far from ideal, which is why I'd personally recommend using Windows Performance Counters or WMI Monitors. It's certainly laborious,…

Have you considered using this Exchange 2010 Database Availability Group template instead?

We did see this occur once during the Beta, but it was fixed in the final release. Please open a case with support so we can look through the debug logs of your diagnostics and determine the root cause of the issue.

That error message is being returned by the Java application server to SAM based on the community string provided. It appears you may not have configured SNMP permissions for that community string. You may want to consider using JMX instead. * Java Application Server (JMX) * Oracle WebLogic (JMX) * GlassFish (JMX) * JBoss…

Not using an ACL file is typically not recommended, but depending upon the environment and other security policies in place (VLANs, firewalls, router access control lists, etc. coupled with the shared secret that is the community string) it can be secure enough for most environments. Security IMHO should be directly…