SolarWinds SCP-NPM Dumps

 Traps are unsolicited messages sent by network devices to report events or issues. The Orion Platform can receive and process traps from any device that supports SNMP. To alert on a select message, you can use the Traps in Orion Alerts feature, which allows you to configure the default trap alert to fire on the trap message you select to alert on. You can also customize the alert conditions, actions, and triggers to suit your needs. For example, you can alert on traps thatmatch a specific OID, source, or severity, and send an email, log a ticket, or run a script when the alert is triggered. References: Configure SNMP traps in NPM, Traps in Orion Alerts, Create alerts for SNMP traps

 By default, Orion NPM retains Syslog messages in the database for seven days before discarding them. This means that any Syslog messages older than seven days are deleted from the database and cannot be viewed or searched in the web console. To change the default Syslog retention period, you need to modify the Database Settings on the Orion Polling Settings page in the web console. You can also use the Database Manager tool to manually delete or archive Syslog messages from the database. References: SolarWinds SCP Study Aid - NPM, page 19; NPM Administrator Guide, page 111.

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