flow record IPV6-FLOW-RECORD
match ipv6 protocol
match ipv6 source address
match ipv6 destination address
collect ipv6 dscp
collect transport source-port
collect transport destination-port
collect interface input
collect interface output
collect counter bytes
collect counter packets
!
flow record IPV4-FLOW-RECORD
match ipv4 dscp
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
collect transport source-port
collect transport destination-port
collect interface input
collect interface output
collect counter bytes
collect counter packets
!
flow exporter FLOW-EXPORTER-SVV
destination X.X.X.X
source GigabitEthernet0/2
transport udp 9996
!
flow monitor IPV6-FLOW-MONITOR
record IPV6-FLOW-RECORD
exporter FLOW-EXPORTER-SVV
cache timeout active 60
flow monitor IPV4-FLOW-MONITOR
record IPV4-FLOW-RECORD
exporter FLOW-EXPORTER-SVV
cache timeout active 60
!
interface GigabitEthernet0/2
description LAN
ip flow monitor IPV4-FLOW-MONITOR input
ip flow monitor IPV4-FLOW-MONITOR output
ipv6 flow monitor IPV6-FLOW-MONITOR input
ipv6 flow monitor IPV6-FLOW-MONITOR output
Any ideas what is wrong; do we need to make changes to the flexible netflow setup to make this work? If we switch it back to traditional netflow the QoS classes show up just fine again.
Another issue we've had since upgrading from version 9.5 to 9.9 is that while in version 9.5 we could see the IPv6 addresses in source/destination/conversation it now only shows 0.0.0.0. Could this also be related to the flexible netflow configuration or a bug in netflow analyzer?
kind regards
Michel