To prevent alerts for devices behind your core router during a reboot, what should you configure?

To prevent alerts for devices behind your core router during a reboot, what should you configure?

• A. Configure dependencies between the core router and affected devices
• B. Pause alerting for the affected group
• C. Disable all alerts globally
• D. Remove the devices from monitoring temporarily

Answer: (A)

Using a parent–child dependency between the core router and the devices behind it lets the alerting system know that outages on the downstream devices are a consequence of the upstream device reboot. In SolarWinds NPM you set this up by designating the core router as the parent and the affected devices as dependents, and you enable alert suppression for dependent nodes when the parent is down. During the reboot, the core router’s down status will suppress alerts for all the devices behind it, preventing alert storms and keeping notifications accurate to real maintenance activity. Once the core router is back up, the dependency is released and normal alerting resumes if issues persist. Other options are less ideal: pausing alerts for the group requires manual action and doesn’t reflect the network topology, disabling all alerts globally is too broad, and removing devices from monitoring is heavy-handed and defeats ongoing monitoring.

Using a parent–child dependency between the core router and the devices behind it lets the alerting system know that outages on the downstream devices are a consequence of the upstream device reboot. In SolarWinds NPM you set this up by designating the core router as the parent and the affected devices as dependents, and you enable alert suppression for dependent nodes when the parent is down. During the reboot, the core router’s down status will suppress alerts for all the devices behind it, preventing alert storms and keeping notifications accurate to real maintenance activity. Once the core router is back up, the dependency is released and normal alerting resumes if issues persist.

Other options are less ideal: pausing alerts for the group requires manual action and doesn’t reflect the network topology, disabling all alerts globally is too broad, and removing devices from monitoring is heavy-handed and defeats ongoing monitoring.