Cisco Configuration Guide,Cisco SD-WAN Controllers Release 20.8.x Release 4.2

Destination-based NetFlow Accounting

Updated: September 24, 2008

Want to summarize with AI?

On this page

Overview

Supported features
Limitations
Configuring Destination-based NetFlow Accounting

Overview

Destination-based NetFlow Accounting Short Desc

Destination-based NetFlow accounting (DBA) is a usage-based billing application that tracks and records traffic according to its destination. It enables service providers to do destination-specific accounting and billing. The destination-based NetFlow accounting record includes the destination peer autonomous system (AS) number and the BGP next-hop IP address.

Note

When an EBGP neighborship is established towards a directly connected peer (neighborship toward's the Peer routers Global IPv6 address configured on the directly connected interface), the EBGPv6 peer will advertise both the Link Local Next Hop (LL NH) and the Global Next Hop.

DBA is supported on ASR9000 Gigabit Ethernet and ASR9000 Enhanced Gigabit Ethernet linecards.

The following parameters are collected and exported to destination:

Destination peer AS number
BGP next-hop IP address
Ingress interface
Egress interface
Forwarding status
Incoming IPv4 TOS
Counter of packets in the flow
Counter of bytes in the flow
Timestamp for the first and last packets in the flow
Counter of packets in the flow (64 bits)
Counter of bytes in the flow (64 bits)
Timestamp for the first and last packet in the flow. This is the timestamp when the flow is reported from hardware to the NetFlow server.

Supported features

Destination-based NetFlow accounting supports the following features.

IPv4 and IPv6 addresses
Configuration on physical interfaces, bundle interfaces, and logical subinterfaces
IPv4 unicast and multicast traffic
Only ingress traffic
Only full mode NetFlow
NetFlow export format Version 9 over User Datagram Protocols (UDPs)
Normal and permanent cache type (active and inactive timeout aged flow records)

Limitations

The following are the limitations for Destination-based NetFlow accounting.

MPLS IPv4 and IPv6
Configuration for individual Modular QoS Command-Line Interface (MQC) classes
Simultaneous configuration of destination-based NetFlow accounting with IPv4 and IPv6 sampled NetFlow on the same interface, in the same direction.
Layer 2 switched MPLS traffic
Egress traffic
Sampled mode NetFlow
NetFlow export formats version 5, version 8, IP Flow Information Export (IPFIX), or Stream Control Transmission Protocol (SCTP).
Immediate cache type

Configuring Destination-based NetFlow Accounting

To tracks and records traffic according to its destination using destination-based Netflow accounting, you must configure a Flow Monitor and enable NetFlow on the interface.

Procedure

	1.	Create a Flow Monitor using the command to define the type of traffic to be monitored. The record type specifies the type of packets that are sampled as the packets pass through the router. For enabling Destination based NetFlow accounting, use the record type. `Router#configure Router(config)# flow monitor-map fmm-ipv4 Router(config-fmm)# record ipv4 destination-tos Router(config-fmm)# exit`
	2.	Apply a Flow Monitor Map to a physical interface using the command to enable NetFlow on the router. `Router#configure Router(config)#interface POS 0/1/0/0 Router(config-if)#flow ipv4 monitor fmm-ipv4 ingress Router(config-if)#commit Router(config-if)#root Router(config)#exit`
	3.	View the running configuration to verify the configuration that you have configured. `Router# show run flow monitor-map fmm-ipv4 record ipv4 destination-tos ! interface preconfigure POS0/1/0/0 flow ipv4 monitor fmm-ipv4 ingress ! end`
	4.	Verify the Flow Monitor configuration using the command. `Router#show flow monitor-map fmm-ipv4 Flow Monitor Map : fmm-ipv4 ------------------------------------------------- Id: 1 RecordMapName: ipv4-destination-tos CacheAgingMode: Normal CacheMaxEntries: 65535 CacheActiveTout: 1800 seconds CacheInactiveTout: 15 seconds CacheUpdateTout: N/A CacheRateLimit: 2000 HwCacheExists: False HwCacheInactTout: 50 RP/0/RSP0/CPU0:ios#`

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.