10/17/2021 0 Comments Solarwinds Netflow Configuration
You shouldn’t need to edit anything. The default values here are good for TrafficInsights. Netflowparameters configuration. Set the variable count to 1, leaving only the row ALL. Click the edit pencil for netfloweventtypes. Netfloweventtypes configuration.More accurately, capturing sFlow from Juniper EX/QFX switches. One that I just recently crossed off is capturing Netflow. Like most of you, I have a long list of "To-do's" in our LogicMonitor deployment. Configure the interfaces to send.
The profile defines which NetFlow collectors will receive the exported records and specifies export parameters.#Global sflow enable, globally define polling interval and sampling rate,To configure typical Netflow version 9 flow reporting, follow the steps listed below. Create a NetFlow server profile. Add the device exporting NetFlow to SolarWinds NPM for monitoring.To use a NetFlow collector for analyzing the network traffic ingressing firewall interfaces, perform the following steps to configure NetFlow record exports. Remember: more data at your disposal does you no good if you can't place it in proper context.Set up a device to export NetFlow data to SolarWinds NTA Log in to the network device. I can't stress enough though that you pay close attention to LM's suggested best-practices, carefully consider Juniper's caveats, and put a lot of effort into planning the details of your deployment (which switches, which physical interfaces, etc) so that you understand what data you are actually getting from sFlow and how it is being delivered. I've included the needed Juniper commands for those of you who are also in non-Cisco environments. Also, there are very likely some limitations with regards to the number of sampling instances per fpc that you can create, the total number of instances that can be configured per chassis, and whether any single instance can span multiple fpc.#The below statement is valid for MX-80 HW. Good luck with thatSet chassis fpc 1 sampling-instance NETFLOW-INSTANCE#The above statement is valid for MX-240, MX-480, and MX-960 HW, though you will need to specify the fpc you want to use. One other relevant addendum to my original "you need to know your MX HW & SW in detail" caveat: I have 20 x1 GE and 2 x 10GE MIC-3D powering my physical interfaces if you have anything else consult Juniper documentation for sampling support information. I'll put that into a separate post check back later if you are interested.OK, I've finally had a chance to validate this configuration and I can tell you that it works, with a few minor alterations.see below.I have deployed this on an MX-80 running Junos 13.3R9.13. Unfortunately the degree of difficulty is substantially higher in terms of Juniper configuration.
0 Comments
Leave a Reply. |
AuthorAshenafi ArchivesCategories |