Quoting last summer's Andreas Tikart question below.
Did anyone here happen to solve this problem, the VPN activation from within the cisco box would be great...
Thanks,
Patrick
----------------------------------------------------------------------------------------- Andreas Tikart
07-25-2004, 02:45 AM Hi,I want to open an IPSec tunnel automaticly. For this I created a cronjob with sends pings though the tunnel forcing the IPSec tunnel to open. Unfortunally the policy-list is removed from the running-config after the job has run once. I think the ping-command fullfills the requirements for using in cronjobs (no manually entered input required, command will not be canceled by keystoke).
Does anyone know whats wrong ?
Thanks
Andreas
------- Schnipp ------- Schnipp ------- Schnipp -------
kron occurrence Job2 in 15 recurring policy-list StartIpsecTunnel
kron policy-list StartIpsecTunnel cli ping ip 192.168.25.252 source 172.19.10.1
------- Schnipp ------- Schnipp ------- Schnipp -------
Jun 28 09:11:45: Major 1, Minor 0 Jun 28 09:11:45: Timer Event Job2 Jun 28 09:11:45: Kron delay for next Job2 900000 Jun 28 09:11:45: Call parse_cmd 'ping ip 192.168.25.252 source
172.19.10.1' Jun 28 09:11:46: Kron CLI return 0 ' **CLI 'ping ip 192.168.25.252 source 172.19.10.1': Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.168.25.252, timeout is 2 seconds:Packet sent with a source address of 172.19.10.1 !!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 104/105/108 ms' Jun 28 09:11:46: Major 4, Minor 7 Jun 28 09:11:46: Respond to end of CLI Process Jun 28 09:11:46: Forcing Removing Policy StartIpsecTunnel Jun 28 09:11:46: Removing Policy StartIpsecTunnel Jun 28 09:11:46: Removing CLI 'ping ip 192.168.25.252 source 172.19.10.1' Jun 28 09:11:46: Done Removing Policy StartIpsecTunnel------------------------------------------------------------------------------------------