cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2957
Views
5
Helpful
2
Replies

Netflow exporter displays incorrect source address

BRUNO WOLLMANN
Level 1
Level 1

Hi,

 

I'm in the process of configuring FnF on an ASR1000 and have run into an issue. I'm wondering if anyone else has experienced an issue where the source IP address displayed doesn't match the IP address of the source interface. I've configured Loopback0 as the source but when I do a "show flow exporter" it always displays the IP address of the Loopback1 interface. In fact, it doesn't matter what source interface I use, the source IP address displayed is always from my L1 interface.

 

I have not performed a capture yet to see if this is just cosmetic or if netflow traffic is actually sourced from L1.

 

asr1#sh ver
Cisco IOS XE Software, Version 03.10.04.S - Extended Support Release
Cisco IOS Software, ASR1000 Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.3(3)S4, RELEASE SOFTWARE (fc1)
System image file is "bootflash:asr1001-universalk9.03.10.04.S.153-3.S4-ext.bin"

asr1#sh flow exporter 
Flow Exporter ehs_exporter:
  Description:              Netflow Exporter
  Export protocol:          NetFlow Version 9
  Transport Configuration:
    Destination IP address: 172.24.110.153
    Source IP address:      172.24.253.209
    Source Interface:       Loopback0
    Transport Protocol:     UDP
    Destination Port:       2055
    Source Port:            63080
    DSCP:                   0x0
    TTL:                    255
    Output Features:        Used
  Options Configuration:
    interface-table (timeout 600 seconds)
    vrf-table (timeout 600 seconds)


asr1#sh ip int b
Interface              IP-Address      OK? Method Status                Protocol
GigabitEthernet0/0/0   unassigned      YES NVRAM  up                    up      
Gi0/0/0.176            unassigned      YES unset  up                    up      
Gi0/0/0.232            unassigned      YES unset  up                    up      
Gi0/0/0.240            172.30.1.241    YES NVRAM  up                    up      
GigabitEthernet0/0/1   172.30.1.238    YES NVRAM  up                    up      
GigabitEthernet0/0/2   unassigned      YES NVRAM  up                    up      
Gi0/0/2.176            172.30.1.177    YES NVRAM  up                    up      
GigabitEthernet0/0/3   172.31.159.134  YES NVRAM  administratively down down    
GigabitEthernet0       unassigned      YES NVRAM  administratively down down    
Loopback0              172.30.2.10     YES NVRAM  up                    up      
Loopback1              172.24.253.209  YES NVRAM  up                    up      
Tunnel10               172.30.10.10    YES NVRAM  up                    up      
Tunnel100              172.30.100.10   YES NVRAM  up                    up      

 

Any help is appreciated.

Thanks,

Bruno

 

 

1 Accepted Solution

Accepted Solutions

jmandersson
Level 1
Level 1

Hi!

 

Yes, I've seen that, on a different platform though (Cat6k/SUP2T).

In my case the problem was a miss in the configuration regarding VRF´s. The intended source interface was in a VRF but no VRF was configured in the flow exporter/ destination.

 

Regards,

Johan

View solution in original post

2 Replies 2

jmandersson
Level 1
Level 1

Hi!

 

Yes, I've seen that, on a different platform though (Cat6k/SUP2T).

In my case the problem was a miss in the configuration regarding VRF´s. The intended source interface was in a VRF but no VRF was configured in the flow exporter/ destination.

 

Regards,

Johan

Hi Johan,

 

You are correct. I completely missed the vrf option on the destination command.

 

Thanks for your help,

Bruno