Forum Discussion
Single iApps, two traffic-groups
Seems to work. Most things that are possible with TMSH are possible with iApps.
tmsh::create cm traffic-group /Common/TG_A
tmsh::create cm traffic-group /Common/TG_B
tmsh::create ltm virtual-address 10.1.1.1 traffic-group TG_A
tmsh::create ltm virtual-address 10.1.1.2 traffic-group TG_B
tmsh::create ltm virtual VS_A destination 10.1.1.1:80
tmsh::create ltm virtual VS_A destination 10.1.1.2:80
After a little more research, it appears that this is intentional. The iApp itself (sys application service) has a traffic-group property, and all objects owned by the iApp are required to belong to the same traffic group. Attempting to change the traffic-group of one of the objects results in an error such as "can not be modified because it is in use by application (/Common/test.app/test) that does not have a matching traffic group." Furthermore, in my example from above, setting the iApp's traffic-group automatically changes the traffic group of both virtual-addresses.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com