Copying iApps

I have searched long and far, but I can't find better documentation on copying iApps. How are people adding IPv6 versions of their IPv4 iApps? (Of course, F5 should allow us to simply list both the IPv4 and IPv6 addresses in the HTTP iApp, which is the best solution.)

Here is the method that I have been using to make an IPv6 version (a copy) of an IPv4 iApp. I don't know good it is, so please provide critical feedback.

1) Login to the tmsh CLI

2) Display the existing config for your IPv4 iApp

list sys application service myapp_iapp.app/myapp_iapp

3) Copy that output and change the pool address from IPv4 to IPv6:

OLD = pool__addr { value 10.20.30.40 }

NEW = pool__addr { value 1111:2222:3333:4444::40 }

4) Next, edit the name of the iApp by appending _v6 to the end (or whatever you prefer):

OLD = sys application service myapp_iapp.app/myapp_iapp {

NEW = sys application service myapp_iapp_v6.app/myapp_iapp_v6 {

5) Test the new config by entering this command:

load sys config from-terminal merge verify

Paste your updated IPv6 config and hit control-D.

6) If there are no errors, you can submit the new config by using:

load sys config from-terminal merge

And again paste the same IPv6 config to enter it into the system.

You should be able to see your new IPv6 version iApp with:

list sys application service myapp_iapp_v6.app/myapp_iapp_v6

7) The last step is to activate the new iApp from the F5 web interface

iApps > Application Services, select your IAPP, click “Reconfigure”.

Verify that everything is correct and then click “Finished”.

😎 You should now have an IPv6 version of your application. Remember that the IPv4 and IPv6 versions are not linked, so any changes from now on will need to be done on both iApps. (Another important reason F5 should allow dual-stack iApps!)