Let's take a look at what we got
when it comes to our challenge section.
A network engineer says we're using NetFlow version nine,
so we already have flexible NetFlow.
Hang on.
Flexible NetFlow is a framework
for how we can piece things together.
NetFlow version nine is a version of exporting,
of export format.
You review the configuration and see only
interface gig one zero, IP flow ingress,
IP flow egress, IP flow expert version nine. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
IP flow egress, IP flow expert version nine.
Which statement is correct?
Flexible NetFlow requires IP fix,
not version nine, that's not right.
Flexible NetFlow and NetFlow version nine
are the same thing, nope.
This is classic NetFlow using a version nine export,
not flexible NetFlow.
That's the correct answer.
A router exports flow data to a non-Cisco collector,
but the collector reports it cannot decode
some of the flow fields.
Which change best resolves the issue? WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Which change best resolves the issue?
Add IP flow egress to the interface,
now that means it's just gonna export even more data.
Switch from NetFlow version nine to IP fix,
that's where my head goes first,
because it says non-Cisco.
IP fix is the IETF standard version 10 of NetFlow.
Increase the cache timeout, it's not gonna help you,
and enable telemetry instead of NetFlow
isn't gonna help you in this case either.
It's probably capturing the right data,
but the collector was receiving it
in a format it didn't understand. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
in a format it didn't understand.
Users report two to three second packet drops
several times per hour.
SNMP graphs and NetFlow data show no anomalies.
So SNMP and NetFlow isn't able to capture
any packet drops that are going on.
Which troubleshooting methodology is most appropriate?
Switch down from NetFlow nine to five,
that's definitely not it.
Use telemetry streaming.
Telemetry streaming can be your real live, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Telemetry streaming can be your real live,
real time data collection and visualization idea.
Continuous protocol debugs, while you could do this,
that could actually make things worse
because of all the compute overhead
that could be involved with it.
And increase SNMP polling frequency.
SNMP might not be configured to have the right traps
in the first place.
So this reinforces what we've learned
about troubleshooting with logs, debugs, and NetFlow.