These datagrams are then collected by software such as the Orion NetFlow Traffic Analyzer. Network monitoring relies on the routers collecting then exporting detailed NetFlow (or J-Flow) information in UDP packets. NetFlow has now become a mature technology, and though the use of templates, Version 9 has become future proof.
Possible Network Problems NetFlow Can Tackle. Incidentally, this is why you cannot test SolarWinds Traffic Analyzers without access to a router. It was but a small step from extracting routing information from the IP packets’ headers, to developing a reporting capability for NetFlow. NetFlow started life as a mechanism to control caching on Cisco routers, and thus speed-up network packets. Interfaces: any single points of network traffic, such as switch ports, physical interfaces, virtual interfaces, sub-interfaces, and VLANs.įor more information on checking your SolarWinds NTA licenses, see How to check licenses in the SolarWinds Platform Web Console.įor more information on licensing, see License SolarWinds Platform products in the SolarWinds Platform Web Console.Cisco developed the NetFlow protocol as part of their Internetwork Operating System (IOS) back in 1996. Nodes: any devices being monitored, such as routers, switches, virtual and physical servers, access points, and modems. To monitor over 12,000 elements, use additional polling engines (APEs). With the default polling interval, one polling engine can monitor a maximum of 12,000 elements. The following types of SolarWinds NTA licenses are available: License 
For example, when you upgrade an NPM SL250 license to SL500, you must upgrade your SolarWinds NTA license to SL500. When upgrading licenses, the license levels must match. For more information on NPM licenses, see NPM licensing model. For example, if you have an NPM license for SL250, your SolarWinds NTA license is also SL250. Licensing for SolarWinds NTA follows the license level of your SolarWinds NPM installation.
0 kommentar(er)
