Guest

Preview Tool

Cisco Bug: CSCun96969 - ASR1K traceback seen when attaching FNF record to a monitor

Last Modified

Mar 06, 2018

Products (1)

  • Cisco ASR 1000 Series Aggregation Services Routers

Known Affected Releases

15.2(4)S

Description (partial)

Symptom:
The ASR1002 running IOS_XE 3.7.0 (15.2(4)S) crashed after a configuration change inf FNF.

%FMANRP_NETFLOW-3-INVALIDFLOWDEFCPP: CPP Flow definition can not be 
created 1
Mar 19 12:18:33 lns3 1596693: -Traceback= 
1#fcbfdf6899eea283341cebf8c5320ad1  :10000000+6FBFE8 :10000000+6FC394 
:10000000+5B9F54C fnf_config:9DB4000+1B270 fman_rp:ED4B000+1D0
764 fman_rp:ED4B000+1D0954 :10000000+3326E78 :10000000+330110C
Mar 19 12:18:33 lns3 1596694: Mar 19 12:18:32.268: 
%FMANRP_NETFLOW-3-INVALIDFLOWDEFCPP: CPP Flow definition can not be 
created 1
Mar 19 12:18:33 lns3 1596695: -Traceback= 
1#fcbfdf6899eea283341cebf8c5320ad1  :10000000+6FBFE8 :10000000+6FC394 
:10000000+5B9F54C fnf_config:9DB4000+1B270 fman_rp:ED4B000+1D0764 
fman_rp:ED4B000+1D0954 :10000000+3326E78 :10000000+330110C
Mar 19 12:18:38 lns3 1596696: Mar 19 12:18:35.546: 
%IOSXE_OIR-6-OFFLINECARD: Card (fp) offline in slot F0
Mar 19 12:18:38 lns3 1596697: Mar 19 12:18:35.561: 
%ASR1000_RP_ALARM-6-INFO: ASSERT MAJOR module F0 Unknown state
Mar 19 12:18:38 lns3 1596698: Mar 19 12:18:35.561: 
%ASR1000_RP_ALARM-6-INFO: ASSERT CRITICAL module R0 No Working ESP
Mar 19 12:18:47 lns3 1596699: Mar 19 12:18:46.919: %SYS-5-CONFIG_I: 
Configured from console by icuk on vty0 (46.33.130.1)
Mar 19 12:19:50 lns3 1596700: Mar 19 12:19:49.743:

Conditions:
An FNF record that includes  one of the following key/non-key fields configured along with an extracted field will trigger the trace back.

one or more fields derived from the below:
 match/collect routing source/destination [peer] as [4-octet]
 along with an extracted field such as :
 collect application http host

Example:

flow record test-rec
 match routing source as 4-octet
 collect application http host
flow monitor test-mon
  record test-rec
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.