Autonomous Systems with NetFlow

Posted in NetFlow, NetFlow Analyzer, Network Traffic Monitor on August 26th, 2010 by Jon Mills
autonomous-systems-with-netflow

captivated audience

Such a dilemma, when it comes to Autonomous System NetFlow exports, which do you prefer: peer-as or origin-as?  If you don’t care about Autonomous System reports, you still just might find this post interesting.  I’ll try to keep you captivated!

Autonomous System
First of all, what is an Autonomous System? Within the Internet, an Autonomous System (AS) is a collection of connected Internet Protocol (IP) routing prefixes under the control of one or more network operators that presents a common, clearly defined routing policy to the Internet. A single ISP can support multiple Autonomous Systems Numbers (ASN). The ASNs supported by the ISP are advertised via their Internet router using the BGP Protocol. So what is BGP?

Read more »


Jon Mills
Marketing & Public Relations Manager
Follow Me On Twitter
Tags: , , , , , ,

Packet Loss via Netflow: MFSN

Posted in NetFlow, NetFlow Analyzer, Network Health Report, Network Traffic Analysis, Network Traffic Monitor, Scrutinizer on December 1st, 2009 by Jo-G
packet-loss-via-netflow-mfsn

How do you know if the NetFlow collector is saving or even getting all of the NetFlow datagrams that are being sent to it or that it is receiving? It is important to know if any flows are missing.

Why do we care?

This is a great question. We care because a loss of flow exports is usually caused by one of three things:

    1. The network dropped some packets
    2. The router can’t keep up
    3. The NetFlow receiver / collector can’t keep up

NetFlow sequence numbers are becoming increasingly important. When building a NetFlow collector it is important that the engine scales while staying accountable. If you look at the NetFlow v9 packet format you will notice something called the package_sequence.

Read more »

Tags: , , , , , , , , , , , , , , , , , , , ,

NetFlow impact on hardware performance

Posted in NetFlow on November 4th, 2009 by mike@plixer.com
netflow-impact-on-hardware-performance

NetFlow impact on hardware performance carries a common misconception. Competitors of Cisco would like you to believe that enabling NetFlow will often bring the router or switch to its knees. The sFlow founders would also like you to believe this. Although we are sFlow supporters, I thought I would take an opportunity to set the record straight.  Read more »

Michael Patterson
Scrutinizer Product Manager
Tags: , , , , , , , ,

Halloween: Setting up Procurve sFlow

Posted in sFlow on October 31st, 2009 by mike@plixer.com
halloween-setting-up-procurve-sflow

We’ve noticed that HP is definitely making inroads into the switch market. People are still buying Cisco routers, but consumers are realizing that they can use less expensive switches on the periphery. The list of features on the HP Procurve is impressive, however, their promptness to market a feature doesn’t mean it was implemented well, or even free of bugs. Read more »

Michael Patterson
Scrutinizer Product Manager
Tags: , , , , , , ,