Skip to content
Back to Learning
CCNP · ENCORAdvanced

Flexible NetFlow: Flows Without Faces

R1's flow cache never names a sender and nothing reaches the collector's port. Fix Flexible NetFlow on four real routers, right below.

Live lab: real routersFlexible NetFlowNetwork assurance

Symptom

R1's flow cache fills but never names a sender, and nothing ever arrives on the collector's port. Fix the record and the exporter on four real routers.

Your mission

Prove the cause, then fix it

Format

Four real routers

Need a hint?

Reveal the root cause when you're ready.

Try the investigation first, then use this as your escape hatch, not a dead end.

Locked

Create a free account to open Flexible NetFlow: Flows Without Faces. You get the root cause and the full step-by-step fix.

Prefer no password? Use an email link instead

No spam. The fix lands in your inbox too. Your account includes 5 guided labs free. After that, the Learning Pass unlocks every remaining lab.

Lab debrief

Turn the session into a repeatable troubleshooting pattern.

Use this reference after your attempt: first explain the symptom, then verify the evidence, then confirm the repair.

The problem

Traffic between R2 and R3 crosses R1, which runs Flexible NetFlow on its link to R2 and exports toward a collector at 4.4.4.4 (R4 stands in for it). The operations team wants to see who talks to whom. The cache fills up, but it cannot name the sender of a single flow, and nothing has ever arrived on the collector's port even though R1's exporter reports packets sent.

What you'll practice

  • Read a flow cache and tell key fields from collected counters
  • Change the key fields of a record that a monitor is already using
  • Compare an exporter's settings with what the collector expects
  • Explain why an exporter's own counters do not prove delivery
  • Monitor traffic in both directions on one interface

1. Key fields and non-key fields

match fields decide what makes a flow unique; collect fields are counted per flow. A record with only a destination key merges every sender for that destination into one flow.

2. Records in use

IOS will not change a flow record while any monitor refers to it. Build a new record and point the monitor at it instead.

3. Exporters

An exporter sends records over UDP to a collector's address and port. It counts what it sends, not what arrives.

4. Timeouts

Flows are exported and removed from the cache after the inactive or active timeout, so the cache shows recent flows, not history.

The topology

Four real routers with static routing. R1 sits between R2 (loopback 2.2.2.2) and R3 (loopback 3.3.3.3) and monitors flows on its link to R2. R4 stands in for the collector at 4.4.4.4, reached through R2: an ACL entry counts every packet arriving on UDP port 2055, the port the collector expects.

Commands to run yourself

The real diagnostic commands for this lab, copy-paste ready. Run these in the same order to reproduce the investigation on your own session.

The flow cache as a table
show flow monitor MON cache format table
The record's key and collected fields
show flow record REC
Where the exporter sends
show flow exporter name EXP
Packets arriving on the collector's port
show ip access-lists COLLECTOR
Flexible NetFlow on R1Traffic between R2 and R3 crosses R1; R4 is the collector.10.0.12.0/30Et0/0 to Et0/010.0.13.0/30Et0/1 to Et0/010.0.24.0/30Et0/1 to Et0/010.0.34.0/30Et0/1 to Et0/1R1 · flow monitorLo0 1.1.1.1Et0/0 10.0.12.1Et0/1 10.0.13.1R2 · trafficLo0 2.2.2.2Et0/0 10.0.12.2Et0/1 10.0.24.1R3 · trafficLo0 3.3.3.3Et0/0 10.0.13.2Et0/1 10.0.34.1R4 · collector stand-inLo0 4.4.4.4UDP 2055Et0/0 10.0.24.2Et0/1 10.0.34.2The cache has no source addressesWho talks to whom is unknownNothing reaches the collector portExporter reports packets sent

Rate this lab

No ratings yet

Your rating

Frequently asked

Are these real routers or a simulation?

Real routers. Pressing Start boots four routers just for you, with full command sets: any valid command works, not only the ones the guide suggests. The first start can take a minute or two while the lab server wakes up.

Who can run this lab?

It is included with the Exam Pass and the Year Pass. Each session lasts up to three hours, and you can run one live lab at a time.

Does my exact fix have to match the answer?

No. The lab checks the routers' state: the flows in R1's cache and the exports counted on R4. Any record, monitor and exporter configuration that produces that state passes.

Which ENCOR topics does it cover?

Flexible NetFlow from the network assurance section (4.0) of the 350-401 blueprint.

Ready to run this lab yourself?

No setup, no image sourcing. Book a session or ask for a live demo.