A logistics company wants a Nexus switch to create a configuration checkpoint every night at 02:00, whether or not any syslog event occurred. Which on-box tool should run that job?
Select an answer to reveal the explanation.
Short Explanation
This job is an alarm clock, not a fire alarm. You put the checkpoint command on the onboard scheduler at 02:00 so it runs because the clock says so. An EEM applet would sit quiet all night unless a syslog line happened to match.
Full Explanation
The NX-OS scheduler defines a job, typically a CLI command such as a checkpoint, and a timetable that runs that job at a set time. A nightly 02:00 checkpoint does not depend on an interface event, a neighbor flap, or any other syslog line, so the scheduler is the matching tool. An EEM applet whose trigger is a syslog pattern runs only when that pattern is logged. Quiet nights would produce no checkpoint, which misses the requirement. POAP runs when a switch boots without a startup configuration and is looking for an initial image and config. It is not a recurring production timer, and a checkpoint is not limited to first boot. A SPAN session copies traffic. It does not snapshot the running configuration or store a checkpoint. Caveat: the scheduler needs its feature enabled and a clock source the operator trusts, or 02:00 is whatever time the switch happens to have. Operational check: show the scheduler timetable, wait through one test window, and confirm a new checkpoint file exists even when the logging buffer stayed quiet.