Seen this issue twice now. The first time was with one of our remote sites. The tunnel just stopped working one day. We confirmed the config on remote side matched the backup config and had not been changed in over a year. Config on local side matched backup and the only recent changes had been to some servers to an access list. After two days of troubleshooting, we were able to get someone into the comm closet to power cycle the modem. After that, the tunnel magically worked again.
Last night around midnight this issue hit our main data center and took down our tunnel to AWS. Once the sleep fog cleared I realize this was the exact same issue we had a month back with our remote site. No config changes on either side. Restarting tunnel and reboot FW did not fix the issue. After a remote power cycle of the modem then tunnel started working again.
Anyone else seen this? My best guess the tunnel management port is passing traffic but something is stopping the traffic port from passing traffic.
No comments:
Post a Comment