Symptom
Router crashes while configuring Netflow:
STLD1-630.03.05-ASR1(config-flow-monitor)# description match all traffic
STLD1-630.03.05-ASR1(config-flow-monitor)#$flow ipv4 original-output
Exception to IOS Thread:
Frame pointer 0x7F2B8A2073A0, PC = 0x7F2CA993DBF4
UNIX-EXT-SIGNAL: Segmentation fault(11), Process = Exec
-Traceback= 1#f64d76e418c90a6501cfc1e888936c0b :7F2CA1967000+7FD6BF4 :7F2CA1967000+801736E :7F2CA1967000+801998D :7F2CA1967000+7F8C4C1 :7F2CA1967000+8019A1F :7F2CA1967000+7F85AD3 :7F2CA1967000+7F833B3 :7F2CA1967000+7F83A76 :7F2CA1967000+7F8DB47 :7F2CA1967000+7F8D9FB :7F2CA1967000+800FB41 :7F2CA1967000+75FEF94 :7F2CA1967000+75FE042 :7F2CA1967000+75FC2FA :7F2CA1967000+C5C2D49 :7F2CA1967000+7619C90
Conditions
Making configuration changes for Netflow like the below example can trigger this crash:
conf t
no flow monitor Internet-flow
show run
interface GigabitEthernet0/0/0
no service-policy type performance-monitor input All-traffic
exi
flow monitor All-traffic
description match all traffic
record netflow ipv4 original-output
Workaround
The crash is seen when we have the monitor ( type performance-monitor) with the same name as another monitor (type FNF) along with a record. Avoiding such a condition should keep the crash from happening.
Further Problem Description
