Hi dwayne,
It doesn't seem to be an ike gateway timeout. When looking at the event log, I can't see any issues with it. The event log can be seen below.
2019-05-04 08:36:18 system info 00542 BGP peer 169.254.23.17X changed to
Established state
2019-05-04 08:36:17 system info 00542 BGP peer 169.254.23.4X changed to
Established state
2019-05-04 08:36:16 system info 00536 IKE 34.250.138.25X Phase 2 msg ID
3c52af4a: Completed negotiations with
SPI 0d3a492c, tunnel ID 1, and
lifetime 3600 seconds/0 KB.
2019-05-04 08:36:16 system info 00536 IKE 34.250.138.25X phase 2:The
symmetric crypto key has been
generated successfully.
2019-05-04 08:36:16 system info 00536 IKE 34.250.138.25X Phase 2: Initiated
negotiations.
2019-05-04 08:36:15 system info 00536 IKE 52.31.30.3X Phase 2 msg ID
d825cdfa: Completed negotiations with
SPI 0d3a492b, tunnel ID 2, and
lifetime 3600 seconds/0 KB.
2019-05-04 08:36:15 system info 00536 IKE 52.31.30.3X phase 2:The symmetric
crypto key has been generated
successfully.
2019-05-04 08:36:15 system info 00536 IKE 52.31.30.3X Phase 2: Initiated
negotiations.Could this be an issue with the routes in the SSG?
Best wishes,
Christopher