Capacity planning is available for the following metrics of monitored nodes, interfaces, and volumes: CPU utilization on nodes, memory usage on nodes, space usage on volumes, receive (in) utilization on interfaces, and transmit (out) utilization on interfaces1. Capacity planning allows you to monitor capacity usage trends on the network and forecast capacity issues based on historical data and customizable thresholds.You can view capacity forecasting graphs and tables on the details views of nodes, interfaces, and volumes, or use the Top XX Capacity Problems widget to see a list of objects whose usage trend is rising2.Reference:Monitor capacity usage trends on the network and forecast capacity issues in NPM,Forecast capacity for nodes, interfaces, or volumes in NPM

The Orion platform supports agent-based monitoring for Windows, Linux/Unix, and AIX systems. An Orion agent is software that provides a communication channel between the Orion server and the target system, as an alternative to WMI or SNMP. Agent-based monitoring can offer better performance, security, and reliability than agentless monitoring, especially for remote or cloud-based systems. The Orion platform does not support agent-based monitoring for Sun Solaris or IBM systems, as they are not compatible with the agent software.Reference:Monitor with SolarWinds Platform agents in SAM,SolarWinds Platform Agent requirements,Orion Platform | SolarWinds

Web Console maps are interactive and dynamic maps that you can create and customize using the Orion Maps feature in the SolarWinds Platform Web Console. You can display various items on the maps, such as monitored nodes, interfaces and volumes, SAM applications and components, and network links. You can also add custom labels, annotations, and images to the maps. Web Console maps can help you visualize the relationships and dependencies among your network devices and applications, as well as troubleshoot issues and identify root causes.Reference:Orion Maps,Create and customize maps in the Orion Platform,Orion Maps 2.0, New Alerting, and Palo Alto Networks Monitoring - SolarWinds Lab Episode #77.

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-adding-map-objects-sw3356

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.Reference:SolarWinds SCP Study Aid - NPM, page 19;NPM Administrator Guide, page 111.

An OID (Object Identifier) is a unique identifier for a specific variable in a MIB (Management Information Base) that can be polled or monitored by SNMP (Simple Network Management Protocol). However, not all OIDs are supported by all devices or SNMP agents, which are software components that collect and report the MIB data. If you select an OID that is not supported by the device or the SNMP agent, you will get an ''OID not supported'' error when you try to create a custom poller for that device in NPM (Network Performance Monitor).This means that the device or the SNMP agent does not have the information for that OID or does not respond to the SNMP request for that OID12.

To resolve this issue, you can try the following steps34:

Verify that the device supports the OID that you want to monitor. You can use the MIB Browser or the MIB Walk tool to browse the MIB tree of the device and find the OID. You can also check the device vendor's documentation or website for the supported OIDs and MIBs.

Verify that the SNMP agent on the device is configured properly and has the latest version. You may need to update the SNMP agent or enable some features or extensions to support the OID. You can also check the SNMP agent's logs or status for any errors or warnings.

Verify that the SNMP credentials and settings are correct and match the device's configuration. You may need to use a different SNMP version, community string, port, or timeout value to communicate with the device. You can also test the SNMP connectivity using the SNMP Test tool or the Test button in the UnDP (Universal Device Poller) application.

Verify that there are no network issues or firewalls that are blocking the SNMP traffic between the NPM server and the device. You may need to allow the SNMP protocol and port on the firewall or router, or use a different network path or interface to reach the device. You can also use the Ping or Traceroute tools to check the network connectivity and latency.