Comments
-
The main reason is to distribute the load of polling data from a large number of nodes. The Main Poller has resource limitations (CPU, memory, network). Additional Pollers help avoid performance degradation when the monitored environment grows.
-
The user account you’re using to make edits might not have sufficient privileges to modify subnets or IP addresses. SolarWinds allows fine-grained control over user permissions, so it’s important to ensure that the correct permissions are in place.
-
you can use the "Excluded IP Ranges" feature, which allows you to specify subnets or IP ranges that SolarWinds should ignore when performing network scans. This is useful if you have sensitive or non-relevant devices or subnets that you don’t want SolarWinds to monitor.
-
Ensure your account has admin or NCM admin permissions. Check if other users can see the jobs list. If they can, it’s likely a permissions issue.
-
by default, the system saves a backup of up to 10 previous configuration versions for each device node. These saved versions include running, startup, and downloaded configs, depending on your settings.
-
Yes, SolarWinds does support multiple maintenance schedules for devices. This is especially useful for organizations that need to apply different maintenance windows to various nodes, groups, or device types based on business hours
