[c-nsp] MPLS-AWARE NETFLOW

[SECURITY @ CYTANET]

For us the reason we want to use Netflow in the core is mainly to do simplify troubleshooting in the core especially in the cases of congested links or in the event of unbalanced core links. A lot of services are passing from the core including multicast TV, VOICE, Internet etc, and it will be of great benefit if Netflow can be present on the core. 

Another way to observed the core traffic is to enable NETFLOW on all EGDE routers.

----- Original Message -----
From: "Roland Dobbins" <rdobbins at arbor.net>
To: cisco-nsp at puck.nether.net
Sent: Thursday, 20 November, 2014 10:08:29 AM
Subject: Re: [c-nsp] MPLS-AWARE NETFLOW


On 20 Nov 2014, at 14:22, Mark Tinka wrote:

> A lot of people "consider" this option as a way to keep costs down so 
> as not to have to deploy too many licenses or resources to support too 
> many edge routers.

The problem with this is that two of the primary benefits of NetFlow - 
edge-to-edge traceback and detailed peering analysis - are negated by 
this approach.

Better to do a partial edge deployment and then expand it over time, 
IMHO.

-----------------------------------
Roland Dobbins <rdobbins at arbor.net>
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/