Today I am going to explain how to activate your Maipu router IPFIX. You may ask, “Why would I want to export IPFIX?” Thats a great question, because you want to be able to monitor all the traffic passing through your Maipu router so you can report on it.
To review, IPFIX stands for ‘IP Flow Information Export’. Some companies like to rename their implementation of NetFlow and IPFIX but Maipu keeps it simple and simply calls it IPFIX. IPFIX is just like NetFlow v9 but with added support. IPFIX allows vendors to export unique vendor IDs so they can stick proprietary information in the flows and export anything they want.
Below are the commands to activate IPFIX:
|router(config)# int fastethernet1||Enter the interface; the interface is connected to the internal management network.|
|router(config-if-fastethernet1)#ip address xx.xx.xx.xx||Configure the IP address.|
|router(config-if-fastethernet1)#exit||Exit the interface.|
|router(config)#ip flow enable||Enable the flow forwarding|
|router(config)#int fastethernet0||Enter the interface; the interface is the IPFIX traffic monitoring point.|
|router(config-if-fastethernet0)#ip address xx.xx.xx.xx||Configure the IP address.|
|router(config-if-fastethernet0)#ip route-cache flow||Enable the flow forwarding on the interface.|
|router(config-if-fastethernet0)#ipfix ingress||Enable IPFIX on the interface and monitor the ingress traffic.|
|router(config-if-fastethernet0)#exit||Exit the interface|
|router(config)#ipfix destination xx.xx.xx.xx||Configure the destination address of the IPfix packet and UDP destination port number|
You can enable egress as well per your requirements.
When the above commands are entered you can report on source and destination information, type of service, and in/out in data as long as you are collecting the flows from any NetFlow Collectors.
If you have any questions about IPFIX, please leave a comment below and I will answer them.