Thanks for posting the config information. I have looked at it and do not yet see a problem. If you do an extended ping in which you specify the destination of 10.222.242.70 (the NetFlow destination) and specify the source of 10.102.255.98 (the loopback of the router) does that traffic get encrypted?
It might also be helpful if you would post the output of extended trace in which you specify the destination of 10.222.242.70 (the NetFlow destination) and specify the source of 10.102.255.98 (the loopback of the router). This will verify whether the data is using the expected path.
I do not understand how the extended ping does get encrypted but the NetFlow does not. Based on the crypto map and the access list used to select traffic it seems to me that NetFlow should be encrypted. One thought that occurs to me is to ask you to do the extended ping again specifying destination as the NetFlow destination, specifying the source as the NetFlow source, and specifying packet size as maximum size.
I also wonder about the QOS. I see this on the multilink interface:
service-policy output WAN512_QoS
and wonder what that is doing. Perhaps you can post that part of the config.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...