topic Re: Problem with XML in Automation/API Discussions

Problem with XML

stafols — Fri, 18 Jan 2013 12:33:30 GMT

Hi all!

Trying to create and VPN tunnel with the XML-api , but I am not clever enough

Below is working fine, I can create the Tunnel and do almost all settings....

wget -O dum1.txt --no-check-certificate "https://192.168.3.114/api/?type=config&key=%palokey%&action=set&xpath=/config/devices/entry[@name='localhost.localdomain']/network/tunnel/ipsec/entry[@name='StaffanTunnel']&element=<auto-key><ipsec-crypto-profile>Staffan</ipsec-crypto-profile></auto-key><tunnel-monitor><enable>no</enable></tunnel-monitor><anti-replay>yes</anti-replay><copy-tos>no</copy-tos><tunnel-interface>tunnel</tunnel-interface>"

Here I am failing, when trying to set the IKE gw for the tunnel, what is wrong with the syntax?? (tried a lot of different things, this is just one example)

Want in the end to do everything in one request if possible, but have split the XML:s now to easier do troubleshooting.

wget -O dum1.txt --no-check-certificate "https://192.168.3.114/api/?type=config&key=%palokey%&action=edit&xpath=/config/devices/entry[@name='localhost.localdomain']/network/tunnel/ipsec/entry[@name='StaffanTunnel']/auto-key/ike-gateway/entry[@name='StaffanGW']/"

Output error is in this example: <response status="error" code="12"><msg><line>Invalid target object in edit handler</line></msg></response>

Running version 5.0.2 on VMware, production later on will be PA-5050s

Regards Staffan

Re: Problem with XML

cviaud — Thu, 24 Jan 2013 06:49:31 GMT

Hi,

If think your error is due to the use of the edit action in your second example, you didn't set the element that changed ( in XML API ref doc you will see

http(s)://hostname/api/?type=config&action=edit&key=keyvalue&xpath=xpath-value&element=element-value )

try that (check the end of the url)

&action=edit&xpath=/config/devices/entry[@name='localhost.localdomain']/network/tunnel/ipsec/entry[@name='StaffanTunnel']/auto-key/ike-gateway&element=<entry name='StaffanGW'/>

or try to use the set action.

BTW you have to define first the IKE GW before attaching it to an ipsec-tunnel.

Below an example with an IKE GW named titi, psk test attached to interface with ip 192.168.100.254/24 and a peer-ip 1.1.1.1 and profile myprofile

note: I configured some parameters as example, if some parameters are missing just add them to your config.

note 2: the last command is the same than your last command and I got a : <response status="success" code="20"><msg>command succeeded</msg></response>

Define GATEWAY with PSK (name titi - PSK : test)

action=set

xpath=/config/devices/entry[@name='localhost.localdomain']/network/ike/gateway/entry[@name='titi']/authentication/pre-shared-key

element=<key>test</key>

Define GATEWAY local IP (use this Ip: 192.168.100.254/24)

action=set

xpath=/config/devices/entry[@name='localhost.localdomain']/network/ike/gateway/entry[@name='titi']/local-address

element=<ip>192.168.100.254/24</ip>

Define GATEWAY peer IP (in this case the peer GW is 1.1.1.1)

action=set

xpath=obj="/config/devices/entry[@name='localhost.localdomain']/network/ike/gateway/entry[@name='titi']/peer-address

element=<ip>1.1.1.1</ip>

Define IKEv1 crypto ( profile myprofile )

action=set

xpath=/config/devices/entry[@name='localhost.localdomain']/network/ike/gateway/entry[@name='titi']/protocol/ikev1

element=<ike-crypto-profile>myprofile</ike-crypto-profile><

Attach the ipsec-tunnel to IKE GATEWAY

action=set

xpath=/config/devices/entry[@name='localhost.localdomain']/network/tunnel/ipsec/entry[@name='toto']/auto-key/ike-gateway

element=<entry name='titi'/>

regards

Re: Problem with XML

stafols — Thu, 24 Jan 2013 12:57:18 GMT

Thanks a lot!

All the other stuff with cryptos and gateways I did work out easily!

But just the small change from edit to set, did the last thing I was not able to do...

Now it is time to create hundreds of tunnels....

Regards Staffan