取消
显示结果 
搜索替代 
您的意思是: 
cancel
647
查看次数
0
有帮助
0
回复

关于Flexible Netflow (FNF)在IPv6场景下的数据导出源和目的IP地址为::的问题。

angelyouyou
Level 1
Level 1
 

 

2022-05-06_223823.png

如上面的网络拓扑所示。

关于NetFlow FNF,我创建了2个flow-record(IPv4和IPv6各1个)、2个flow-exporter(IPv4和IPv6各1个)、2个flow-monitor(IPv4和IPv6各1个),然后在g1/0接口上绑定了出入方向、IPv4/IPv6共计4条Flow导出配置,配置如下(附件中也上传了配置文件和NetFlow抓包文件)。

但是当我在R2设备上ping R1下挂的PC机IPv6地址(2003::F043:5531:E4AB:8A33)尝试让R1导出NetFlow时,我发现R1设备导出NetFlow报文的IPv6 DataSet不符合预期,源和目的IP地址都是::,而不是实际的IPv6地址(2003::F043:5531:E4AB:8A33),在GNS3和真实设备上相同配置都存在该问题

2022-05-06_232234.png

请问一下这是什么问题?是否我的配置存在问题?该如何解决?多谢。

!
flow record fr-ipv4
description Ipv4Flow
match ipv4 source address
match ipv4 destination address
match interface input
match interface output
match flow direction
collect ipv4 protocol
collect transport tcp flags
collect counter bytes
collect counter packets
collect timestamp sys-uptime first
collect timestamp sys-uptime last
!
!
flow record fr-ipv6
description Ipv6Flow
match ipv6 source address
match ipv6 destination address
match interface input
match interface output
match flow direction
collect ipv6 protocol
collect transport tcp flags
collect counter bytes
collect counter packets
collect timestamp sys-uptime first
collect timestamp sys-uptime last
!
!
flow exporter fe-ipv4
destination 10.1.1.254
transport udp 9999
template data timeout 30
!
!
flow exporter fe-ipv6
destination 10.1.1.254
transport udp 9999
template data timeout 30
!
!
flow monitor fm-ipv4
exporter fe-ipv4
cache timeout inactive 10
cache timeout active 1
record fr-ipv4
!
!
flow monitor fm-ipv6
exporter fe-ipv6
cache timeout inactive 10
cache timeout active 1
record fr-ipv6
!
!
flow-sampler-map sampler
mode random one-out-of 1000
!
!
interface GigabitEthernet1/0
 ip address 10.1.12.1 255.255.255.0
 ip flow monitor fm-ipv4 input
 ip flow monitor fm-ipv4 output
 ip flow monitor fm-ipv6 input
 ip flow monitor fm-ipv6 output
 negotiation auto
 ipv6 address 2012::1/64
 ipv6 enable
 flow-sampler sampler
 ospfv3 1 ipv6 area 0
!

 

0 条回复0
快捷链接