Yes, I do. But, I had to reconfigure is since i took it out of the customers network and put it on my own for testing.
So at this point I'm not sure if it's the reconfiguration that is the issue or if it's the original issue still occuring. I'm having the tunnel come up but no traffic through it.
I am getting the following in the logs:
[Feb 9 10:26:29][24.xx.xx.19 <-> 74.xx.xx.206] Got IKE trigger from PFE for tunnel index: 67108867. Installing SAs if not already installed.
[Feb 9 10:26:39][24.xx.xx.19 <-> 74.xx.xx.206] iked_vpnm_timer_callback: VPN Monitor timer kicked in
[Feb 9 10:26:39][24.xx.xx.19 <-> 74.xx.xx.206] Get rtbl_idx=0 for ifl idx 73
[Feb 9 10:26:39][24.xx.xx.19 <-> 74.xx.xx.206] PING (74.xx.xx.206 via 74.xx.xx.206): 56 data bytes Tunnel-id:67108867 outgoing intf 73, rtbl idx 0
[Feb 9 10:26:39][24.xx.xx.19 <-> 74.xx.xx.206] VPNM send ping pkt (84/84) bytes for tunnel 67108867, seq 2870
[Feb 9 10:26:49][24.xx.xx.19 <-> 74.xx.xx.206] iked_vpnm_timer_callback: VPN Monitor timer kicked in
[Feb 9 10:26:49][24.xx.xx.19 <-> 74.xx.xx.206] Get rtbl_idx=0 for ifl idx 73
[Feb 9 10:26:49][24.xx.xx.19 <-> 74.xx.xx.206] PING (74.xx.xx.206 via 74.xx.xx.206): 56 data bytes Tunnel-id:67108867 outgoing intf 73, rtbl idx 0
[Feb 9 10:26:49][24.xx.xx.19 <-> 74.xx.xx.206] VPNM send ping pkt (84/84) bytes for tunnel 67108867, seq 2871
[Feb 9 10:26:59][24.xx.xx.19 <-> 74.xx.xx.206] iked_vpnm_timer_callback: VPN Monitor timer kicked in