sFlow and Application Telemetry send mirrored packets from a common source to a common destination. sFlow sends samples directly to the destination, while Application Telemetry sends mirrored packets through a GRE tunnel, to the same destination.
The tunnel source is the switch that you want to monitor:
sFlow sends sampled flows.
Application Telemetry sends packets that match its policy rules.
Both sFlow and Application Telemetry use an agent to package either the sFlow streams or the Application Telemetry packets. To configure the agent, they both use the sflow agent-ip command.
Note
The switch sends only one mirrored copy, even if the packet matches two or more policies. For information on which mirrored copies take precedence, see Configuration considerations.
The tunnel destination for the mirrored traffic is a server where software performs a deep packet inspection of the mirrored traffic.
sFlow sends flow and counter samples as datagrams to the sFlow Collector.
Application Telemetry sends packets that match the policy rules over a GRE tunnel to the Analytics Engine.
To configure the tunnel destination, they both use the sflow collector <1–2> command.
Important
You can configure two Collectors, but Application Telemetry uses Collector 1 only. You must configure Collector 1 before you enable Application Telemetry.