A regional planning commission needs a local, sub-second reaction on one router when a tracked object fails, while still using off-box controllers for fleet-wide template changes. How should those tools be split?
Select an answer to reveal the explanation.
Short Explanation
EEM is the firefighter in the station—fast when the local alarm trips. Controllers are the regional dispatch that rolls out policy to every site. Use both for what they are good at instead of photocopying applets across the fleet or waiting for tonight’s batch to save a link.
Full Explanation
Embedded Event Manager provides on-box, event-driven actions with low latency for local conditions such as tracked-object failure. Central controllers and orchestration remain better for consistent, auditable fleet-wide configuration. Duplicating EEM everywhere poorly scales policy. Nightly batches cannot match sub-second local reaction, and EEM does not inherently forbid NETCONF-based management.