05-06-2022 11:48 PM
As shown in the network topology above.
Regarding NetFlow FNF, I created 2 flow-records (1 each for IPv4 and IPv6), 2 flow-exporters (1 each for IPv4 and IPv6), 2 flow-monitors (1 each for IPv4 and IPv6), and then The g1/0 interface is bound with a total of 4 Flow export configurations for the inbound and outbound direction and IPv4/IPv6. The configurations are as follows (the configuration file and NetFlow packet capture file are also uploaded in the attachment).
But when I ping the IPv6 address (2003::F043:5531:E4AB:8A33) of the PC connected to R1 on the R2 device and try to let R1 export NetFlow, I found that the IPv6 DataSet of the NetFlow packets exported by the R1 device is not as expected. Both the source and destination IP addresses are :: instead of the actual IPv6 address (2003::F043:5531:E4AB:8A33), and the same configuration exists on both GNS3 and real devices.
May I ask what is the problem? Is there a problem with my configuration? How to solve it? Thank you.
! 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 !
05-07-2022 02:36 PM
Hello,
which IOS images are you running in GNS3, Dynamips or IOSv ?
05-07-2022 05:00 PM
My GNS3 image(dynamips) is c7200-adventerprisek9-mz.152-4.M11
05-08-2022 09:50 PM
IOS Version:
Cisco IOS Software, 7200 Software (C7200-ADVENTERPRISEK9-M), Version 15.2(4)M11, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Sun 16-Oct-16 07:53 by prod_rel_team
ROM: ROMMON Emulation Microcode
BOOTLDR: 7200 Software (C7200-ADVENTERPRISEK9-M), Version 15.2(4)M11, RELEASE SOFTWARE (fc2)
R1 uptime is 0 minutes
System returned to ROM by unknown reload cause - suspect boot_data[BOOT_COUNT] 0x0, BOOT_COUNT 0, BOOTDATA 19
System image file is "tftp://255.255.255.255/unknown"
Last reload reason: unknown reload cause - suspect boot_data[BOOT_COUNT] 0x0, BOOT_COUNT 0, BOOTDATA 19
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide