We have two ISP connections. The primary (Outside) connection (100Mbps) has most of our VPN connections, but the secondary (Backup) connection (500 Mbps) has the VPN connection to our AWS instance.
This weekend, we started a database sync to AWS. While doing this sync, our primary connection pegged out at it's 100 Mbps limit, according to Solarwinds interface monitoring.
Our secondary connection is less than 1% utilization, according to Solarwinds.
There's no way to communicate with the AWS instance except over the VPN - netflow data shows the communication going to the 172.19.0.0/24 space we have in AWS, which is only accessible over said VPN, attached to the secondary interface.
Why would the ASA be reporting this traffic as traversing through the primary interface instead of the secondary?
edit: ASA ver 9.4(2)11
edit: Added ASA interface names to first line.
No comments:
Post a Comment