aLTeReGo ✭✭✭✭✭

You will need to upgrade to SAM 6.2.2 before the agent is available to you. I'll assume based upon the screenshot you provided that you're currently running SAM 6.1 or earlier now.

Have you reviewed the following blog post? SAM 6.8 WHAT'S NEW PART 2 - Enhanced Support for Cisco UCS Monitoring

I'm still confused, is the inability to use Orion variables in a custom HTML/Text resource a bug or a feature...um, I mean by design? Denny, I appreciate you pointing me in a general direction but I'm even more out of my league in ASP.NET.

RaviK wrote: Yes aLTeReGo We do have cases opened for the issues faced 1. 00145840 - Solarwinds server down 2. 00156662 - Polling Server down 3. 00143315 - SWIS services not responding (hang state/down) 4. 00156141 - Upgrade fails with a DB Configuration error gangadhar.k c_sameer abdhijasharma RaviK , it appears all of…

This is located in your Customer Portal under "My Downloads" when you select "Server & Application Monitor" and click "Additional Components".

Under Centralized Advanced Settings, change'SolarWinds.Orion.InformationServiceClient' TransferMode from 'Streamed' to 'Buffered'. You can access Centralized Settings by going to http://your.Orionserver.ext/Orion/Admin/AdvancedConfiguration/Global.aspx

The queue is not time-based. It's based upon the volume of data (size). The queues can, however, be adjusted. Just ensure that you never increase the total size of all queues to more than the amount of free space available on the drive.

The SQL database acts as a quorum for HA. Heartbeat timeout is configurable under 'High Availability Settings'

I've logged this request internally under SAM-3715.

Yes. See my post above.

This is a fairly generic error that simply means it was unable to connect to the remote host. This could be caused by Windows Firewall settings, inline firewalls, router access control lists, etc. between the Orion server and the host being monitored. I would recommend trying something like WMIExplorer from the Orion…

Indeed I was. You have been given the distinct honor of having your case picked up by the great and powerful kasaff. Several other customers have reported similar issues after upgrading to CU6. QA has reproduced the issue internally and Development is hot on the trail of determining the root cause.

You will need to create a new application template and add an SMTP Component Monitor from the component monitor list as shown below.

These jobs are on the polling engine server, not the database. Yes, uninstalling/re-installing the Job Engine/Collector will reset the file where these jobs are stored on the poller.

Quick follow-up. Do you know what tables need to be dropped from the database for AM? Also, instructions on how to drop those tables would be great too. Thanks.

Updated link -> Troubleshooting WMI

Can you perform an SNMP MIB walk of that device over port 1161 using the same SNMP credentials as you are using for the node from the Orion server? * From the Orion server open the MIB walk tool - C:\Program Files (x86)\SolarWinds\Orion\SnmpWalk.exe * Enter the Glassfish server IP address in the "Agent Address of DNS name…

Can you post a screenshot of the charts you're trying to get on the summary page? This will make it easier for us to understand what you're trying to accomplish. Thanks.

Thanks PeterLyttle for keeping the community updated on your progress. Keep us posted if anything changes.

Thanks Jay. Kate should be picking your case up shortly.

The reason why the content match is failing is because there's a javascript validation on the page and the HTTP User Experience Monitor in SAM doesn't support Java Script. This is something you should be looking at our Synthetic End User Monitor to monitor as it fully supports Java Script.

You can modify the name of any volume by going to "Manage Nodes", selecting the volume, and clicking "Edit Properties" as pictured below.

You may need to clear your browser cache and cookies before the Worldwide Map resource is immediately fully functioning. It's likely that your browser cache expired on its own a day later.

My recommendation would be to run Microsoft's .NET Framework repair tool > Download Microsoft .NET Framework Repair Tool from Official Microsoft Download Center

Are you saying the node is managed as a WMI node and when using the inherit credentials from node option for the component monitor the service does not restart correctly, but when you assign specific credentials to the component monitor (even if they're the same as the WMI node credentials) the service restarts…

Very helpful advice ! Thanks for sharing. I'm sure this will be very helpful to others who might run into this issue in the future.

The poller itself does not have the capability. You can however install the Agent onto your main Orion server or Additional Polling Engine, then ensure the poller is managed via the Agent in Orion. This is now the default behavior for new installs.

SAM 6.0.1 is out. Time to upgrade * SolarWinds SAM 6.0.1 Release Notes * SolarWinds SAM 6.0 Release Notes

WMI is far more forgiving than SNMP. My recommendation would be to manage the node via WMI instead of SNMP and this should reduce or eliminate the phantom volume syndrome that you're seeing now when the SNMP volume index ID number changes on the host.

This thread was started when SeUM 1.0 was available. Since then we've added this feature natively to the product in SeUM 1.5 through the advanced alert macro ${ScreenshotUrl}. This should eliminate the need for you to do any custom SQL alerts.