Comprehensive and Detailed Explanation From Exact Extract:
When a device returns multi-core CPU statistics as a table, SolarWinds Device Studio allows you to use the
"Add Calculated Value" option and select the average function. This enables the web console widget to display the computed average CPU utilization automatically.
The documentation explains:
"For devices with multi-core CPUs, you can use the Add Calculated Value feature in the Device Studio to compute the average (or other statistical functions) of returned table values, which can then be visualized directly in widgets." References:
Network Performance Monitor Administrator Guide, "Device Studio Calculated Values" SolarWinds Success Center: "Averaging Table Poller Results"

Unreadable fields in SNMP traps from a device typically indicate either the device is not monitored as a node (so SolarWinds cannot fully parse its SNMP data) or the MIB file for that device is not included in the SolarWinds MIB database, making it impossible to decode certain OIDs.
Reference:
" Unreadable trap fields often result from the device not being monitored as a node or missing the relevant MIB definitions in the SolarWinds MIB database. "
- (Network Performance Monitor Administrator Guide, SNMP Trap Troubleshooting section)

Comprehensive and Detailed Explanation From Exact Extract:
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.
References:
NPM Administrator Guide: Network Insight Features and Monitored Services Network Insight for Palo Alto and F5 - Service and Policy Monitoring

To detect duplex mismatches:
The node must be monitored (i.e., managed in SolarWinds).
The node must be in " up " status, so SNMP data about interface status, speed, and errors can be polled and compared.
Description in MIB (A) is not necessary if the device is already SNMP-capable, and " warning " status (C) is a result, not a requirement.
Reference:
NPM Administrator Guide, "Requirements for Detecting Duplex Mismatches,"
"Only monitored and up-status nodes are eligible for duplex mismatch detection."