Comprehensive and Detailed Explanation From Exact Extract:
If devices respond to SNMP queries individually but aren't discovered during network scans, the most likely cause is the discovery timeout value being set too low. This can result in slower devices timing out before responding to discovery requests, even though they are operational and SNMP-enabled.
The documentation explains:
"If devices are not discovered but respond to SNMP queries, increase the discovery timeout and retry. Short timeouts can cause missed responses from devices that take longer to reply during scanning." References:
Network Performance Monitor Administrator Guide, Section: "Discovery Troubleshooting" SolarWinds Success Center: "Device Not Found During Discovery"

Comprehensive and Detailed Explanation From Exact Extract:
When monitoring F5 BIG-IP load balancers, SolarWinds Network Insight requires both SNMP for device status and iControl (a proprietary F5 API) for advanced configuration and health monitoring. The SolarWinds guide states:
"After adding an F5 load balancer with SNMP, configure the iControl connection to access additional F5- specific health and configuration metrics." References:
F5 BIG-IP and iControl configuration - SolarWinds NPM Administrator Guide, Network Insight for F5 BIG- IP section

To collect and analyze Windows event logs in SolarWinds Hybrid Cloud Observability, you must:
Deploy and configure the platform agent on the Windows server: The agent is responsible for collecting logs locally, including event logs, and sending them to the SolarWinds platform for analysis.
Configure the Windows server to send logs to the SolarWinds platform: This can be achieved by forwarding event logs from the Windows server to the server running the SolarWinds platform (e.g., via Windows Event Forwarding or syslog if using third-party tools).
Simply configuring rules within the platform does not automatically grant access to Windows event logs; deployment of the agent or configuration of log forwarding is required for collection. This requirement is outlined in the Log Analyzer Administrator Guide and the Hybrid Cloud Observability documentation for Windows log collection.
Reference:
Log Analyzer Administrator Guide, "Collecting Windows Event Logs,"
Hybrid Cloud Observability Admin Guide, "Windows Log Collection Methods"

Comprehensive and Detailed Explanation From Exact Extract:
If the web console shows a router as "down" but it is actually operational:
ICMP is blocked: If the polling engine cannot ping the device, it will be reported as down.
SNMP is blocked: If SNMP polling fails (for devices polled via SNMP), detailed data and status cannot be retrieved, resulting in a down state.
Agent connection issues may apply for agent-based monitoring but are not typical for network routers. Node dependency configuration could affect child node status display but would not cause the parent node to show
"down".
Reference:
NPM Administrator Guide, "Troubleshooting Node Status - Down State Causes"