SolarWinds Hybrid-Cloud-Observability-Network-Monitoring - Hybrid Cloud Observability Network Monitoring Exam

Cisco ASA access-list monitoring requires more than basic SNMP polling. SolarWinds documentation for reviewing access lists on ASA firewalls states that NPM and NCM must be installed, and that NCM is required to access the ACL subview and compare ACL configurations. SolarWinds also documents CLI polling as required for ASA-specific details and accurate firewall data. WMI is not used for Cisco ASA firewall polling because ASA is a network/security appliance, not a Windows host. Therefore, the complete task is to enable SNMP and CLI polling and monitor the ASA with NCM. Option A is incomplete because it omits NCM, which is required for ACL review.

===============

Custom pollers are typically created when you need to monitor metrics or OIDs that are not supported by default in SolarWinds:

Monitor specific metric that is not out-of-the-box: If a device exposes a metric not natively monitored by SolarWinds, you must create a custom poller for that metric.

Monitor unsupported object ID: For any OID that is not included in default templates, a custom poller is necessary.

Monitoring special equipment or devices without WMI might also need custom pollers, but the requirement specifically applies when you need to access non-standard metrics or OIDs.

Hardware health monitoring can be enabled during node discovery or after a node is added via the " List Resources " option. Additionally, hardware health can be enabled or viewed in the Asset Inventory page for nodes that support it.

From the documentation:

“You can enable hardware health sensors by selecting the option during resource discovery (List Resources) or later via Asset Inventory for individual nodes.”

False positives in hardware health alerts often occur when the polled MIB on the device is not the preferred or correct MIB for that particular hardware platform. This can result in SolarWinds interpreting SNMP data incorrectly, causing inaccurate alerts. Ensuring that the device is using the recommended MIB for hardware health resolves these false alert issues.

Log Analyzer listens for syslog messages by default on:

TCP port 514 (the standard syslog port)

TCP port 6514 (the default port for syslog over TLS/SSL, i.e., secure syslog)

Port 162 is for SNMP traps, and 1463 is not standard for syslog in SolarWinds.

The correct process for creating a poller in Device Studio is:

Select the technology

Specify the data source

Assign the poller to a node

Save the poller

If a node remains in “unknown” status:

A. Ping device from assigned polling engine: Verifies direct network connectivity from the poller to the node.

C. Verify the appropriate polling method is set for this node: Ensures SolarWinds uses the correct protocol (ICMP, SNMP, WMI, etc.) for monitoring.

D. Verify a ping response for this node is received through the ICMP: Confirms basic reachability and that the node is not blocking ping requests.

Running an SNMP walk (B) can help diagnose SNMP-specific issues but is not always directly relevant to a node simply being in “unknown” status unless SNMP is the configured polling method.

When collecting Windows event logs without installing an agent, SolarWinds recommends converting those events to SNMP traps or syslog messages using the SolarWinds Event Log Forwarder for Windows. This allows the platform to ingest and recognize Windows events through standard logging protocols.

" The SolarWinds Event Log Forwarder for Windows enables you to forward Windows event logs as SNMP traps or syslog messages, allowing agentless collection and integration into your SolarWinds platform. "

Option C, converting events to traps, is the correct method supported for agentless environments.

List Resources: When you add or manage a node, the List Resources page allows you to enable or verify hardware health monitoring options.

Manage Sensors: This section allows you to directly manage the hardware sensors (such as fans, power supplies, and temperature sensors) that report health status.

Device view and node properties are not the primary locations for enabling or managing hardware health sensors.