![]() ![]() This is one very long command line: show flow monitor FLOW-MONITOR-V4 cache sort highest counter bytes top 50 format table Instead, group the flows so you can see your "top talkers" (traffic destinations and sources). Press 'q' to escape from the screen output if necessary. It's possible to see the individual flows that are active in the router: show flow monitor FLOW-MONITOR-V4 cacheīut on a busy router there will be thousands of individual flows, so that's not useful. Exit configuration mode, save the configuration, and then use these commands: show flow exporter EXPORTER-1 This ensures that the ifIndex values are retained during router reboots - also if you add or remove interface modules to your network devices. This enables ifIndex persistence globally. If you leave it at the default of 30 minutes your traffic reports will have spikes.Īlso make sure that the following command is still present on the border router: snmp-server ifindex persist The "cache timeout active 300" command breaks up long-lived flows into 5-minute fragments. Since you have not specified a protocol version for the exported flow records, you get the default which is Netflow v9. Why are we applying this to the 0/1 (inside) interface? So that our Netflow records show the internal addresses before they are NAT'd. ! Attaching the flow monitor to an interfaceįinally we will configure the FastEthernet 0/1 interface with the monitors we have created. These monitors let us monitor what is happening on the chosen interface of the border router. Next we will set up the flow monitors - we will set up one for IPv4 and another for IPv6. ! Configuration for your BORDER router only We will export the flows using UDP, and sending them to port 9996 on the destination collector. Login to the border router and enter configuration mode.įirst of all we will set up a flow exporter on the border router - this defines where we are going to export the flow information we have gathered from the router. In each of your groups 1 to 6 you must choose one person to type in the commands to set up your border router for Netflow and the management server where the Netflow exports will go. This is an example for doing this from the Campus X border router, bdr1.campusX, to the server named. We will use the existing campus network we have built. The purpose of this exercise is to learn how to configure netflow on the campus Border router. Netflow Lab Campus Network Design & Operations Workshop ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |