<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://www.trisul.org/devzone/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://www.trisul.org/devzone/feed.php">
        <title>Trisul Network Analytics &lt;br/&gt; Developer Zone  netflow</title>
        <description></description>
        <link>https://www.trisul.org/devzone/</link>
        <image rdf:resource="https://www.trisul.org/devzone/ww.trisul.org/devzone/lib/tpl/dokuwiki/images/favicon.ico" />
       <dc:date>2026-04-20T05:29:26+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:asr?rev=1687784926&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:asrnatlog?rev=1740740427&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:ciscofnf?rev=1741004231&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:cisconatsyslog?rev=1740384871&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:config?rev=1743509664&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:extreme?rev=1689592296&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:junipermx?rev=1687346439&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:junipersrx?rev=1715780859&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:mikrotik?rev=1745314946&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:natsyslog?rev=1686300105&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:start?rev=1718005143&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:supported?rev=1739358772&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:templatefields?rev=1739449583&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.trisul.org/devzone/doku.php/netflow:whyfnf?rev=1740737973&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://www.trisul.org/devzone/ww.trisul.org/devzone/lib/tpl/dokuwiki/images/favicon.ico">
        <title>Trisul Network Analytics <br/> Developer Zone </title>
        <link>https://www.trisul.org/devzone/</link>
        <url>https://www.trisul.org/devzone/ww.trisul.org/devzone/lib/tpl/dokuwiki/images/favicon.ico</url>
    </image>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:asr?rev=1687784926&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-06-26T18:38:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Netflow configuration for Cisco ASR</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:asr?rev=1687784926&amp;do=diff</link>
        <description>Netflow configuration for Cisco ASR

Cisco ASR stands for Aggregation Services Router, it is used as an Edge router in many ISP and large enterprise networks.   The ASR 9000 is also used as a Core router in many large ISPs.  

The following is a useful configuration IPFIX configuration template. We recommend IPFIX.</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:asrnatlog?rev=1740740427&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-28T16:30:27+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>NAT logging for Cisco ASR</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:asrnatlog?rev=1740740427&amp;do=diff</link>
        <description>NAT logging for Cisco ASR

Cisco ASR 1000 series routers are popular as internet edge device. One of the functions ASR 1K provides is NAT deployed to conserve public IP space.   For these ISPs keeping a log of NAT translations is a regulatory compliance called IPDR (IP Data Record).  Trisul Network Analytics IPDR helps ISPs meet this compliance requirement.</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:ciscofnf?rev=1741004231&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-03-03T17:47:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Cisco Flexible Netflow configuration</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:ciscofnf?rev=1741004231&amp;do=diff</link>
        <description>Cisco Flexible Netflow configuration

Flexible Netflow (FNF) is a Cisco IOS technology that allows you more freedom to collect exactly the type of information you want in the Netflow records. 

Some of the popular models that support FNF are the Catalyst range of switches such as the Catalyst 3850 series, Catalyst 4500 series, etc. This article tells you how to configure Flexible Netflow.</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:cisconatsyslog?rev=1740384871&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-24T13:44:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Cisco NAT Syslog configuration</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:cisconatsyslog?rev=1740384871&amp;do=diff</link>
        <description>Cisco NAT Syslog configuration

For IPDR Flow logging the recommended method is NetFlow/IPFIX. However for some devices logging the NAT translations via SYSLOG can be preferable. 

To log NAT translations upon create and delete via syslog. Use the following command</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:config?rev=1743509664&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-04-01T17:44:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Simple NetFlow server configuration for ISP</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:config?rev=1743509664&amp;do=diff</link>
        <description>Simple NetFlow server configuration for ISP

This page describes a simple connection between Trisul NetFlow Server and an ISP Gateway router/switch.  We use Cisco ASR as a sample device. 

Key features:

 - Using a public IP for the NetFlow server
 - Using</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:extreme?rev=1689592296&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-07-17T16:41:36+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Extreme Switches</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:extreme?rev=1689592296&amp;do=diff</link>
        <description>Extreme Switches

Netflow configuration on Extreme Switches is really simple.


See Extreme Networks Netflow Documentation 



set netflow export-interval 1
set netflow export-destination 10.10.100.100  2055
set netflow export-version 9
set netflow port *.*.* enable rx
set netflow cache enable
set netflow template timeout 1</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:junipermx?rev=1687346439&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-06-21T16:50:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Sample Netflow configuration for Juniper MX routers</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:junipermx?rev=1687346439&amp;do=diff</link>
        <description>Sample Netflow configuration for Juniper MX routers

Here is a minimal configuration for Juniper MX Netflow/J-Flow

The setup

	*  Trisul Network Analytics is installed on IP 10.10.100.100
	*  The router IP is 20.20.200.200 
	*  We want to enable IPFIX  , alternately you can use Netflow-v9</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:junipersrx?rev=1715780859&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-05-15T19:17:39+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Juniper SRX Simple Netflow Configuration</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:junipersrx?rev=1715780859&amp;do=diff</link>
        <description>Juniper SRX Simple Netflow Configuration

You can use Version 5 of Netflow for most common visibility tasks.

Trisul Network Analytics the Netflow server is running on 10.10.10.1

Version 5

To configure v5 Netflow for basic visibility or IPDR purposes, you can use the following</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:mikrotik?rev=1745314946&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-04-22T15:12:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Configuring NetFlow in MikroTik</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:mikrotik?rev=1745314946&amp;do=diff</link>
        <description>Configuring NetFlow in MikroTik

NetFlow is a network protocol developed by Cisco that provides network monitoring and accounting capabilities. MikroTik routers support NetFlow versions 1, 5, 9, and IPFIX. Here's a step-by-step guide to configuring NetFlow in MikroTik:</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:natsyslog?rev=1686300105&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-06-09T14:11:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>NAT syslog for Mikrotik</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:natsyslog?rev=1686300105&amp;do=diff</link>
        <description>NAT syslog for Mikrotik

Many providers want to store the NAT logs for compliance purposes.

On Microtik there is a UI where you can enable syslog but that is heavy and logs all packets. We only need NAT syslog for new connections.

Use this



[admin@MikroTik] &gt; 

/ip firewall filter add chain=forward action=log connection-state=new protocol=tcp in-interface=LAN log-prefix=&quot;nat&quot;</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:start?rev=1718005143&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-06-10T13:09:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>NetFlow</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:start?rev=1718005143&amp;do=diff</link>
        <description>NetFlow

NetFlow is an extremely useful tool for collecting network data from a vast array of network elements in a cost-effective way.

To achieve deep visibility, we recommend enabling NetFlow across your entire network and directing the logs to a Trisul context.</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:supported?rev=1739358772&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-12T16:42:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Trisul NetFlow Device support</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:supported?rev=1739358772&amp;do=diff</link>
        <description>Trisul NetFlow Device support

Trisul Network Analytics has been deployed and tested with the following devices and NetFlow versions and variants.

Netflow versions

	*  All versions of NetFlow supported  5, 9, 10, IPFIX with all major features like NBAR, QOS, UserID, AppID</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:templatefields?rev=1739449583&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-13T17:56:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Supported Template Fields</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:templatefields?rev=1739449583&amp;do=diff</link>
        <description>Supported Template Fields

NetFlow v9 , v10 , and IPFIX use a template based architecture. This allows for flexibility in the metrics that are reported per flow. Each metric has a special Template ID and position as reported in special Template Packets sent periodically.</description>
    </item>
    <item rdf:about="https://www.trisul.org/devzone/doku.php/netflow:whyfnf?rev=1740737973&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-28T15:49:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Do you really need Flexible NetFlow</title>
        <link>https://www.trisul.org/devzone/doku.php/netflow:whyfnf?rev=1740737973&amp;do=diff</link>
        <description>Do you really need Flexible NetFlow

Flexible NetFlow(r) (FNF)  is a feature available in Cisco routers and switches. If you are running IOS 15 or later you should have it.

We see a lot of customers struggle to configure FNF correctly because it is a much more involved process. Common mistakes</description>
    </item>
</rdf:RDF>
