Last Modified: Nov 07, 2022
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Fixed In:
12.1.0
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 1.2.3.4 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 1.2.3.4 log packet order 0 port-range 443,80,22,389 } } customization-group putty_resource_app_tunnel_customization }
Use tmsh to modify the resource.
None
