I think in your case, the way that NetFlow is implemented has it do the flow lookup and creation (NetFlow) stage prior to
the feature lookup (NAT) stage on the incoming traffic. Therefore, the NetFlow record will be created prior to NAT and you'll get the external addresses in your flow record. As a workaround, you could think about enabling NetFlow on the LAN interface(s) and collect the traffic that's being sent out to your serial interface, thereby creating flow records with internal NAT addresses. Depending on what you want to achieve and the nature of the traffic this may or may not work
Please refer the following URL for info on netflow collector.
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 ...