So let's start by collecting data on gig 2.0 for R1 right here, and then see if we can collect
any data that traverses it. So let me go ahead, I'm not going to save that, and we'll jump to R1
and kind of go a little bit bigger screen right here. There we go, now we can go.
We'll go into configuration mode and then straight into interface gig, and I've already forgotten
what interface that was. I'm pretty sure it was 2.0, but this is what I get for not paying
attention. Hang on, hang on, hang on. Let's get the lab topology. Yes, 2.0. Okay, great. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
attention. Hang on, hang on, hang on. Let's get the lab topology. Yes, 2.0. Okay, great.
Back to gig 2.0 and back to my terminal. There we go. So interface gig 2, nope, 2.0, not minus sign.
There we go. So what do I want to do? I want to collect flows that come in or out of this
interface. Watch how hard that is. IP flow ingress and IP flow egress. That's how we start collecting WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
interface. Watch how hard that is. IP flow ingress and IP flow egress. That's how we start collecting
flows for that particular interface. Now for it to work, we need to have a place to export the
flows to. So let's exit out of this, and we'll start to set up our IP flow. Nope, not pi, IP
flow export. And we'll say, what is our destination? You'll have to say what your
collector's IP address and their listening port is. So if I just put 1, 2, 3, 4, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
just to make up an IP address, I can also say they listen on the net flow port of 6783,
and we've just set the destination just like that. It's usually a good idea to set a source IP
address and not just let it pick a source IP address. So we'll say IP flow export. We'll say
our source can be something like loopback 0, as simple as that. We'll say IP flow export,
and then we'll specify what version do we want. Hit question mark here, and notice it gives you 1, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
and then we'll specify what version do we want. Hit question mark here, and notice it gives you 1,
5, or 9. I'll press 9 right there since we want to use version 9, the latest and greatest. And then
one last thing for good measure, let's do IP flow export, give it a question mark,
and we can see what we've got. Actually, that's not what I want to work with. When we do IP flow
export, this manages just the export functionality for what we want to send. But if you actually do WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
export, this manages just the export functionality for what we want to send. But if you actually do
IP flow hyphen question mark, you can actually see we've got a lot of things. IP flow export,
IP flow aggregation, IP flow capture, IP flow cache. Cache is probably the big one
because this is where we gather flow data and it doesn't immediately punt that flow as it learns
a flow. It doesn't immediately send that to the collector. It holds it in RAM. It holds it in
cache. So when we put question mark right here, how long do we want to hold it before we time out WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
cache. So when we put question mark right here, how long do we want to hold it before we time out
the cache? That's the big thing. We could also specify the number of entries in the cache before
we send. And we can also even specify MPLS settings. In fact, this is one of the big
benefits to version 9 and IP fix over version 5. When we moved to version 9 and IP fix,
we added support for MPLS and IPV6 and even application layer data. Whereas version 5 WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
we added support for MPLS and IPV6 and even application layer data. Whereas version 5
was really stuck in IPV4 only, no MPLS things, no IPV6, no application layer data. Version 9 and
IP fix add that support and that's why it's such a nice deal. If we do something like timeout,
we can set an active timeout and let's leave it at 60 minutes just to make sure it's able to hold
that cache for a while. When I press end here, that's it. It's now actually holding and configured
to start sending flows to a collector now using version 9.