Octet

Ping works but every application fails after a backup WAN path is added

TroubleshootingExpert

The ticket

On Thursday night the team added a backup path for branches: an IPsec tunnel over the internet from BR1 to a new headend router R3, behind a second firewall FW2. The primary path is a metro Ethernet circuit from BR1 to R1, behind FW1. FW1 and FW2 are separate Cisco ASAs, not a failover pair, so they do not share connection state. Both permit ICMP echo, echo-reply, time-exceeded and unreachable for troubleshooting.

Since Friday morning, BR1 users (10.40.0.0/24) cannot open any HQ application. "But ping works." Other branches are fine. All branch LANs live inside 10.40.0.0/16. SRV1 is 10.60.0.15, gateway 10.60.0.1 on CORE1.

10.255.1.210.255.1.110.255.2.210.255.2.110.254.1.210.254.1.110.254.2.210.254.2.1172.16.1.1172.16.1.2Metro Ethernet172.16.9.1172.16.9.2IPsec over internetSRV110.60.0.15CORE1FW1ASA primaryFW2ASA new backupR1R3New VPN headendBR1PC110.40.0.25

Book 3.3 Internet (IP)Book 8.5 Example Systems

Step 1 of 5

BR1 users say no HQ application opens, but ping works. What do you do first?