A logistics Nexus switch already pushes interface counters to a collector once a minute. Operators still learn about a link failure on the following minute. Which subscription reports the interface state at the moment it changes?
Select an answer to reveal the explanation.
Short Explanation
A bus that only calls the depot once a minute will not tell you the tire blew out in between. On-change streaming telemetry pushes the interface state when it changes, so you are not waiting on the next sample. Shortening an SNMP poll is still the collector asking, and a SPAN copy of the management port is not a state subscription.
Full Explanation
Streaming telemetry is a push from the switch. A cadence subscription sends a sample on a timer even when nothing changed, which is why a one-minute counter feed reports a link failure only at the next tick. An on-change subscription sends the update when the interface state changes, so the collector learns about the failure at the event. SNMP polling, however short the interval, is still the collector pulling a table, and it is a different tool from a telemetry subscription. A checkpoint diff compares saved command text. It does not stream interface state, and an hourly job would be even later than the one-minute feed. A SPAN session copies frames to an analyzer. It does not subscribe the collector to interface oper-state. Caveat: on-change is for the state you named in the subscription. A counter you left on a cadence path still arrives on that timer. Operational check: flap a lab interface and confirm the collector receives the state update before the next cadence interval, while the counter subscription still arrives on its own timer.