Hello, I'm having issues where my SEM agents on my nodes aren't connecting to the manager. Any troubleshooting tips? I see the service is stopped but when i run it it automatically stops again when I refresh the services.
I still get logs from devices they are just listed as UknownInternalAgent, but they dont show up as nodes
Hi, a stopped SEM Agent service that immediately stops again usually points to one of a few common causes: connectivity on ports 37890–37892, certificate/SAN mismatch, wrong manager hostname/IP in spop.conf, or a corrupted agent certificate/store.
I would start by checking the spoplog.txt log file for any clues (C:\Windows\SysWOW64\ContegoSPOP\spoplog.txt) and connectivity towards the SEM manager on port TCP 37890-37892.
PALO-ALG - Logging.xmlPalo Alto Networks ALG Security Technical Implementation Guide :: Version 2, Release: 3 Benchmark Date: 27 Oct 2022
Alert Cleared.htmlHello, I would like to share the HTML template details we have prepared so that Solarwinds alarms can become more meaningful. It can list alarm object details and connected device details separately in HTML template. Except for object and device details, you can easily add custom property information…
Cisco ASR Devices.pollerCisco ASR Devices
SWQL is built on the framework of SQL and as such supports most of the standard clauses as part of a query. A very simple example query is: SELECT Caption, IPAddress, Vendor, ResponseTime FROM Orion.Nodes Dissecting this query is relatively straightforward: show some fields (Caption, IP address, Vendor, and Response Time)…