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.

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

The “Device View” feature allows users to view the physical layout of device interfaces on graphical stencils, providing an intuitive graphical representation of port locations and status.

Exact Extract from Official Guide:

“Device View displays the physical layout of device interfaces using graphical stencils for supported devices.”

— (Network Performance Monitor Administrator Guide, “Device View” section)

Unknown flow traffic often occurs when SolarWinds receives flow data from sources not defined in its database, or when flow-enabled devices are not sending data to the expected port.

Add the devices and interfaces to SolarWinds ' database: Ensures flow data is properly associated with monitored objects, resolving the " unknown " status.

Ensure flow-enabled devices send data to the appropriate port: If data is sent to the wrong port, SolarWinds cannot process it correctly, leading to unknown events.

SolarWinds documentation notes:

" Unknown flow traffic typically indicates a mismatch between flow sources and known device/interface configurations, or incorrect UDP port configuration. Registering devices/interfaces and verifying port assignments resolves most unknown flow issues. "

Universal Device Pollers (UDPs) must be explicitly assigned to each node for which custom polling is required. Adding a new node does not automatically assign existing UDPs to that node, even if it’s the same device type as others already using the poller. Assigning the existing UDP to the new node will resolve the issue and enable polling of the desired data.

SolarWinds platform allows for customizing threshold behavior to reduce false positives and tune alerting sensitivity. The three primary customizable threshold settings are:

Single poll: A threshold is triggered immediately if the value breaches the limit in a single polling cycle.

X consecutive polls: The threshold must be exceeded in X consecutive polling intervals before being considered breached.

X of Y polls: The threshold is triggered if the value exceeds the limit in X out of Y most recent polls.

" X concurrent polls " is not an available threshold customization in the SolarWinds platform.

For critical devices and connections, peak calculation is the recommended capacity planning method. This approach uses the highest observed utilization values within a time period, ensuring that planning accounts for maximum network demand and helps avoid bottlenecks during traffic spikes. SolarWinds documentation advises using peak calculations for important links to ensure network reliability and performance.

When you create a flow alert in SolarWinds, the object of the alert (such as a specific interface, node, or application) is chosen from the “Create a Flow Alert” panel. Flow alerts are not based on custom SQL queries, require the NetFlow service to be running, and always have associated trigger actions.

SolarWinds allows you to confirm which metrics (contributors) are used to determine node status. In the node status contributors configuration, you can check if CPU load is included for status calculation. This ensures that CPU thresholds are considered when evaluating overall node health.

SolarWinds determines node status by polling using ICMP (ping) and SNMP. If ICMP is blocked by a firewall or network device between the polling engine and the monitored node, the node will appear “down” in the web console even though it is actually up. Likewise, if the SNMP credentials configured in SolarWinds are incorrect, the polling engine cannot successfully query the device, leading to a false “down” status.

From the documentation:

“If ICMP packets are blocked or dropped, SolarWinds cannot determine node status, resulting in false down events.”

“Incorrect SNMP community strings or credentials will prevent node polling, and these nodes may appear down in the console.”

Changing the polling interval or node management settings does not directly cause this issue.