Bug ID 528332: Providing a comma separated list of port-range intead of a dash separated list via TMSH for App Tunnels resource, causes failure during modify operation.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:

Opened: Jun 17, 2015

Severity: 3-Major


After a resource for an App Tunnel is added with a port range in a comma-separated list, instead of a dash-separated list, the modify action on the resource from the Admin UI will show errors. When a port-range is provided using Admin UI for the resource, it does not allow the user to introduce a comma-separated list. This problem only occurs when a user uses tmsh to introduce a comma-separated port range for the App Tunnel resource and then tries to modify it using the Admin UI.


The issue with modify operation for the comma-separated port-range is only seen through Admin UI; the user can still modify the comma-separated port range resource using tmsh.


An example of a tmsh command that introduces the comma-separated port-range list after which the issue crops up on the Admin UI modify operation on that resource: (cfg-sync Standalone)(Active)(/Common)(tmos.apm.resource.app-tunnel)# modify putty { apps add { item1 { host port-range 443,80,22,389 log packet }}} (cfg-sync Standalone)(Active)(/Common)(tmos.apm.resource.app-tunnel)# list putty apm resource app-tunnel putty { acl-order 108 apps { item1 { host log packet order 0 port-range 443,80,22,389 } } customization-group putty_resource_app_tunnel_customization }


Use tmsh to modify the resource.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips