Application services template with iworkflow issue

I am using iworkflow 2.2.0 and BIG-IP 12.1.2

Are you using one of the JSON template files with the iApp or are you trying to create your own Service Templates from scratch? If not I would start there as a best practice. Download those files here:

These files the cover the most common use cases. If you want to create your own template they also provide additional details about required values that may help you when creating your own service templates.

If you are creating your own service template and using the GUI be sure you don't have an extra space after your values as that might be what is causing this error. If that is not the case the review any values you provided that include a backslash and remove them.

If neither of these tips help provide a little more detail regarding what you are trying to create and the values you have provided.

Hi Angus,

I was actually using the template downloaded from . I had downloaded the appsvcs_integration_v2.0.004.tmpl from github previously and had issues with it. appsvcs_integration_v2.0.004.tmpl works now via iworkflow after a few tweaks. I was able to deploy VIP/pools to Big-ip via Service template/L4-L7 services. I had two different Devices (2 separate device groups) in the "Clouds" and when I deploy config it only applies to one Big-ip1 and not the other(Big-ip2). When I remove Big-ip1 then it does apply to Big-ip2.

What I am trying to achieve is to have same config to both Big-ips, I cant have them on the same config-sync group/HA as they are on different DCs and no layer 2 extension between them.

It sounds like maybe these two BIG-IPs are part of the same cloud? If so when using the GUI it will only push your configs to one of them which one is selected by iWorkflow. When using the REST API you can select which one to target but that would still not solve your problem.

I would recommend one cloud for each DC with the respective BIG-IP maintained within assuming I understand your config correctly.

yes the two big-ips are part of the same cloud. The 2nd Big-ip is in the redundant DC will have the same IP addresses/subnets as the primary DC when there is failure in primary DC internet. Routing has been setup and working. But I just need to now sync the configuration items for the F5s so that the redundant DC big-ip is ready to take over. So I might try REST API as per your advise but I thought it was achievable via iWorkflow.

I think I see your issue, if you create two clouds with one device in each you will have to also create two L4-l7 services which if you are completing manually may be prone to error. You can of course provision the same Service Template to both clouds and provision both clouds to the same Tenant.

When I mentioned using the REST API, I was referring to using the REST proxy on iWorkflow to push these services not the REST proxy on BIG-IP. This may allow you to push the same L4-L7 Service template to both devices in the same cluster as you can manually select which one to use. Using the iWorkflow REST proxy allows provides for the RBAC controls and central point of administration just as you have experience using the GUI.

ok so if I POST JSON payload via postman/python, something like https://{{iWorkflow1_Mgmt_IP}}/mgmt/cm/cloud/tenants/myTenant1/services/iapp and payload, is this what you mean REST proxy on iWorkflow?

Yes, that looks about right. These articles may help explain it a bit further:

• https://support.f5.com/csp/article/K44541081
• https://devcentral.f5.com/articles/iworkflow-201-episode-01-introducing-the-icontrol-rest-api-20880
• https://devcentral.f5.com/articles/iworkflow-201-episode-02-deploying-a-services-template-via-the-icontrol-rest-api-21378?tag=iWorkflow

There are also a number of helpful how to articles on devCentral for iWorkflow here:

• https://devcentral.f5.com/wiki/iWorkflow.HowToSamples.ashx

Thanks Angus I will go through the articles provided.