SCP-NPM Exam Dumps : SolarWinds Network Performance Monitor (NPM) Exam

To detect duplex mismatches, you need to meet the following requirements1:

• The nodes must be monitored by NPM.
• The nodes must be in the up state during the discovery.
• The nodes must support topology and be interconnected.
• Duplex of both devices must be identified as full or half.
• The Possible Duplex Mismatches widget must be enabled on the node details view.

You do not need to ensure corresponding values for each interface are different, as this is the result of a duplex mismatch, not a requirement for detection. In fact, you should unify the duplex mode configuration on neighboring interfaces to avoid mismatches1.

References: Detect and predict duplex mismatches in NPM; Speed and Duplex Mismatch - Forum

NPM polls static properties, such as interface speed and duplex mode, from the firewall devices using SNMP. NPM also collects traffic statistics, such as bytes in and bytes out, from the firewall interfaces using SNMP or NetFlow. NPM then calculates bandwidth consumption based on the total amount of bytes coming through the firewall over a given time interval. Bandwidth consumption is expressed as a percentage of the interface speed. For example, if a firewall interface has a speed of 100 Mbps and NPM polls 10 MB of bytes in and 10 MB of bytes out in one minute, the bandwidth consumption is 20% [(10 MB + 10 MB) / 100 Mbps * 100%]1. References: Monitor firewalls with NPM, Calculate bandwidth utilization on an interface

To show the connection between two devices on an Orion map, you need to meet the following requirements1:

• The devices must be monitored by NPM.
• The devices must support topology and be interconnected.
• The devices must have the corresponding interfaces monitored and identified as full or half duplex.
• The Orion Maps feature must be enabled and configured.

If you do not see the connection between two devices on an Orion map, you should first verify that you are monitoring Layer 2 and 3 topologies for the devices. You can do this by checking the NPM Network Topology widget on the device details page. This widget will reflect what connections will be automatically drawn in Orion Maps2. If the widget does not show the expected connection, you may need to enable topology polling for the devices or check the SNMP credentials and configuration3.

If you are monitoring the correct topologies and still do not see the connection, you can build a custom connection between the devices using the Orion Maps feature. In the Map Editor, you can add the two devices to the canvas, select them, and click the Connect Objects button. Here you can specify the interface on either side and choose to add the manual connection to the database2.

Building a new Orion map and adding the related entities instead of the nodes will not resolve the issue, as the related entities are based on the same topology data as the nodes. Changing the monitoring method from SNMP to CLI will not resolve the issue, as CLI is not supported for topology polling3.

References: Orion Maps; Orion Map Devices not connect - Forum; Polling methods used by Orion.