Pass Through VPN Tunnel traffic creates invalid netflow export in ASA 5500 series
I have a question about the Netflow functionality in Cisco ASA 5500 series.
The netflow traffic data is reported correct, if there is no VPN users connected to the network through ASA.
When VPN users connect to the Network through VPN , netflow export from ASA shows VPN traffic as multiple times the real value. This leads to incorrect spikes in traffic.
Please let me know if this is a known bug/limitation in ASA.
Network setup is as below.
ISP connects to the ASA firewall. ASA to the VPN router. The tunnel ends at the router interface, so the VPN traffic is a 'pass through' traffic for ASA. Netflow export from the VPN router is perfect. Only ASA export shows spikes.
Site to Site IPSec VPN with Dynamic IP Endpoint is typically used when we have a branch sites which obtains a dynamic public IP from the Internet ISP. For example an ADSL connection.One important note is that Site-to-Site VPN with Dynamic remote routers P...
On R1, configure a key ring that defines the peer R3:Address: 18.104.22.168Local and remote pre-shared key: cisco R1(config)#crypto ikev2 keyring KRR1(config-ikev2-keyring)# peer R3R1(config-ikev2-keyring-peer)# address 22.214.171.124R1(config-ikev2-keyring-pee...
This document shows how to use the Port Radius NAS PORT Id Attribute in a compound condition to control access with 802.1X.A user jdoe is allowed to access the network only through the physical port FastEthernet 0/1 of the switch and the user jwhite is al...
This document provides a configuration example of Security Assertion Markup Language (SAML) Authentication on FTD managed over FDM. The configuration allows Anyconnect users to establish a VPN session authenticating with a SAML Identity Serv...
DMVPN Dual Hub Dual Cloud Pros and ConsProsNo single point of failureQuick failover if routing protocols are tunedLoad balancing is easyTraffic engineering is easyEasy to work with multiple ISPsConsNeed 2 tunnels per spokeConfiguration is more complicated...