Missing information from Netflow v9 packets (ISR4321)
I have this ISR 4321 in my lab and trying to configure it for Netflowv9 with application data. I have two Gig interfaces on this router and I am trying to collect the ingress traffic on both interfaces. I applied the following configuration on it. I am receiving some netflow data but it is having the following issues:
Data such as "source port", "direction", "output_snmp" are missing from the netflow packets.
I confirmed that my router has NBAR but my netflow v9 packets do not have the information. I receive some application data on my netflow analyzer but they are not delivered as part of a flow. They are delivered as separate netflow packets with the association back to an IP address or flow. It is the application name and some byte count. How can I receive the application information attached to a particular flow?
My question is that if I have the correct configuration on my router to resolve the issues listed above?
Please note that my "show version" output is at the bottom of this post.
To optimize the database description (DBD) packet exchange between two OSPF neighbors, use the compatible rfc5243 in router configuration mode or address family configuration mode for OSPFv3 AF. To disable RFC5243 optimization, use the no form of this com...
We said always that OSPF is a link-state routing protocol.For most engineer stuying CCNA or CCNP, OSPF is misunsdertanding.In reality, OSPF is a link-state routing protocol only within an area (intra-area); but almost a distance-vector routing protocol be...
A brief difference between ISIS and OSPF link state protocolsISIS and OSPF belongs to the same routing protocol family Link State, but if you study the two routing protocols, you will find several differences, in this article you will get the answer about...
The OSPF Type-2 LSA is one of the misunderstanding LSA among all the popular LSAs in OSPF , most people learns that this kind of LSA (Type-2) is generated by DR the Designated Router in a broadcast segment, for example when two or more than two routers ar...
Table of Contents
RADIUS has been the de-facto protocol for Remote Access Authentication for decades. RADIUS/UDP as defined by RFC 2865 has traditionally used MD5 for authentication and integrity. Unfortunately, successful attacks ...