flow monitor Flow-Monitor exporter Whatsupgold record netflow-original
interface GigabitEthernet0/0/1.909 ip flow monitor Flow-Monitor unicast input ip flow monitor Flow-Monitor unicast output
it works because the record is configured as "netflow-original" and it uses the old standard keys.
But when I try to use a custom record like this:
flow record AS-Path match routing source as peer match routing destination as peer match ipv4 destination address collect counter bytes long collect counter packets long collect timestamp sys-uptime first collect timestamp sys-uptime last ! ! flow monitor Flow-Monitor exporter Whatsupgold record netflow-original
Whatsupgold does not show anything.
Is it something wrong with the configuration or there is a compatibility issue between the new version of Netflow and Whatsupgold?
This is all I have on my router and I use it on flow monitor:
ip flow-export source GigabitEthernet0/0 ip flow-export version 9 ip flow-export interface-names ip flow-export destination 172.16.1.248 9996
I assume youve told flow monitor what port to listen to for netflow. Once you do that, under flow sources it should just pop up but it takes a few minutes sometimes. Either version 5 or 9 will work, so Ive read but I use 9.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...