Hybrid-Cloud-Observability-Network-Monitoring Practice Questions

With Network Insight features (including for Palo Alto and F5 BIG-IP devices) installed alongside Network Configuration Manager and Performance Monitoring, you can monitor:

High availability details: Provides information on device redundancy, failover status, and clustering.

Policy details: Enables insight into firewall, security, and NAT policies for managed devices.

Access lists and VPNs may be monitored in other modules, but the primary, advanced insight is for high availability and policy configurations.

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. "

SolarWinds capacity forecasting accuracy improves when:

More historical data is used: The more historical data points included in calculations, the better the forecasting model will perform.

Using average daily values for calculations: This smooths out anomalies and provides a more accurate trend, as recommended in the documentation:

“To improve the precision of capacity forecasting, use as much historical data as possible and set calculations to use average daily values.”

Monitoring with platform agents or adjusting thresholds affects alerting, not trend accuracy.

SolarWinds ' log processing policies for svslog (syslog) and traps (SNMP traps) are processed independently and concurrently. This is because syslog and SNMP trap processing are separate services with their own processing pipelines, unlike the global pre and post policies which affect overall log routing or rule order.