Universal Device Pollers (UDPs) in SolarWinds are tightly coupled with the polling engine on which they are configured. If the main polling engine fails, custom pollers do not automatically failover; as a result, statistics collection for those UDPs is interrupted. According to SolarWinds documentation:

" UDPs are assigned to a specific polling engine. If the polling engine fails, UDP statistics are not collected until the engine is restored. "

" Universal Device Pollers are not supported on failover engines; they do not collect data from hot standby or failover engines. "

Thus, options C and D directly reflect the official guidance.

If logs are not being sent from a Windows agent, you must confirm that the log forwarding feature is enabled. Even if the agent is installed, logs will not be transmitted unless this setting is turned on.

The documentation notes:

" Ensure the agent is configured to forward logs. Log forwarding must be enabled for the agent to transmit log data to the SolarWinds platform. "

If flows are confirmed as reaching the poller but no data appears in the web console, the most common cause is a missing or incorrect source address field in the flow configuration on the sending device. SolarWinds uses the source address to match incoming flows to the correct device record in its database; if this field is missing or misconfigured, the data will not be processed or displayed.

Exact Extract from Official Guide:

“If the source address field is missing or incorrectly configured in the flow-exporting device, the system cannot associate the flow with a monitored device, and no data will appear in the console.”

— (Network Performance Monitor Administrator Guide, “Troubleshooting NetFlow” section)

To request an update to the SolarWinds MIB database, you must provide a complete SNMP walk or MIB walk from the device in question. This allows SolarWinds to identify and incorporate new OIDs and their definitions into the database.

From the documentation:

" Submit a request with a full SNMP walk or MIB walk output from your device. This provides the necessary OID and device structure for the SolarWinds team to update the MIB database. "

The Universal Device Poller (UDP) in SolarWinds NPM allows users to monitor any SNMP-exposed value, including interface traffic, UPS battery status, and CPU temperature, provided the device ' s MIB exposes the relevant OIDs. Users configure the UDP to poll these custom OIDs, making it a flexible option for monitoring a wide range of metrics across diverse devices.

A " no data " message in NetFlow charts usually indicates that the flow collector service is not receiving or processing flow data. One of the primary troubleshooting steps recommended in the SolarWinds documentation is to restart the collector service. This resolves issues caused by service interruptions, memory leaks, or flow processing errors.

The documentation states:

" If NetFlow charts display ' no data, ' verify that the NetFlow collector service is running. Restart the collector service if necessary, as service interruptions can cause a lack of flow data display. "

Incorrect hardware health data often results from polling the wrong MIB tree. By changing to the correct or preferred MIB tree for the device model, SolarWinds can accurately interpret and display hardware health metrics.

To monitor a custom application using flow monitoring in SolarWinds Hybrid Cloud Observability, you must define the application by specifying its port or port range (and optionally protocol). After this, the application can be assigned to flows involving specific machines, but the primary step is to define application ports first.

To display the serial number in the node details widget using Device Studio, you must add a new data source field, name it " Serial Number, " and provide the correct OID that polls the serial number from the device. This field then appears in the node details widget for the custom poller. Editing an existing field ' s name is not best practice, and UDPs cannot be linked directly to Device Studio widgets.

Only SNMP version 3 supports advanced authentication methods such as MD5, SHA1, SHA256, and SHA512 in SolarWinds and other SNMP-compliant platforms.

The documentation specifies:

" SNMP v3 provides secure authentication and encryption options, including MD5, SHA1, SHA256, and SHA512. Versions 1 and 2c only support community string authentication. "