A retail bank's management station polls Nexus switches with SNMP, and the poll interval is too coarse for interface counters. The team wants the switches to push those counters on a short cadence. Which method matches?
Select an answer to reveal the explanation.
Short Explanation
SNMP is you calling the switch to ask for news, over and over. You want the switch to push interface counters on a cadence, and a streaming telemetry subscription is that push. A faster poll is still a phone call, and a packet mirror is not a counter feed.
Full Explanation
Streaming telemetry on NX-OS lets a collector subscribe to operational data and lets the switch push updates. A cadence subscription sends the selected counters on that interval without the management station polling for them, which is the bank's requirement. SNMP polling can be made more frequent, and it remains a pull: the station asks, the switch answers. Shortening the poll does not turn SNMP into a push subscription, and it also adds more polling load. SPAN copies frames to a destination. Those frames are not a structured counter update, and mirroring production traffic at the management station is not how interface statistics are collected. An EEM applet can react when something happens, but emailing the entire running configuration on every counter change is not a telemetry feed. The configuration does not contain the counter values, and the applet would fire constantly as counters move. Caveat: a cadence subscription still needs a reachable collector and a sensor path that includes the interface counters, or the push has nowhere to go. Operational check: confirm the subscription is established and that counter updates arrive on the cadence when the management station is not polling SNMP.