HYBRID-CLOUD-OBSERVABILITY-NETWORK-MONITORING practice question 22 of 25

After creating a new device studio poller that appears to be returning values on a test device, it is then applied to additional nodes. One of these new devices is not returning the statistics of the test node. Which two of the following reasons might be the cause of the issue? (Choose two.)

Full set: 151 questions
Answer options
A: communication issue exists in new device
B: devices have different firmware versions Correct answer
C: new device needs to be rebooted
D: object IDs (QIDs) are not supported Correct answer
Correct Answer:
B. devices have different firmware versions; D. object IDs (QIDs) are not supported
Explanation

A custom Device Studio poller relies on specific Object Identifiers (OIDs) being available and responsive on the target device's SNMP agent. If a poller works on one device but not another seemingly identical one, the most common reasons are differences in the device's software or configuration. A different firmware version can significantly alter the Management Information Base (MIB), meaning the specific OIDs used by the poller may not be implemented or may have been changed. This directly leads to the OIDs being unsupported on the new device, causing the poller to fail and return no data.

Why Incorrect

A: A general communication issue would likely affect all polling for the device (e.g., status, CPU, memory), not just a single custom poller. C: Rebooting a device is a generic troubleshooting step for transient errors, not a standard solution for a specific, reproducible poller failure.

References

1. SolarWinds. (2023). Orion Platform Administrator Guide. In the chapter "Monitor custom statistics with Universal Device Pollers," the troubleshooting section emphasizes verifying OIDs. It states a common problem is "The OID is not available on the device, or the device does not support the MIB."

2. SolarWinds Success Center. (2023). Create a custom poller in the Orion Platform. This guide details the process of using an SNMP walk to discover and test OIDs on the target device, highlighting that OID availability is device-specific and can vary. This variation is often due to firmware (B) or licensing, which results in unsupported OIDs (D).

Scroll to Top