{"id":28188,"date":"2024-02-16T01:10:56","date_gmt":"2024-02-16T01:10:56","guid":{"rendered":"https:\/\/nsfocusglobal.com\/?p=28188"},"modified":"2026-04-28T08:52:40","modified_gmt":"2026-04-28T08:52:40","slug":"nta-flow-configuration-example","status":"publish","type":"post","link":"https:\/\/nsfocusglobal.com\/pt-br\/nta-flow-configuration-example\/","title":{"rendered":"NTA Flow Configuration Example"},"content":{"rendered":"\n

NTA analyzes traffic and detects exceptions based on flow data sent by the routers and switches. To provide a better understanding of how to send flow data for NTA analysis, we will illustrate flow configuration through an example. Additionally, we’ll guide you on key considerations during the configuration process.<\/p>\n\n\n\n

In the given network environment, a switch (IP address: 10.66.249.61) manages the flow traffic from ports GigabitEthernet1\/0\/2 and GigabitEthernet1\/0\/3, directing it to the management interface of the NTA with the IP address 10.66.249.47.<\/p>\n\n\n\n

1. Configuration on the switch side:<\/strong><\/p>\n\n\n\n

1) This configuration command ensures that the flow from Collector ID 1 is directed to the NTA management interface IP on port 6343, with a description of ‘portal-test,’ and a maximum sFlow data section length of 1400 bytes.<\/p>\n\n\n\n