Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
13.0.0, 12.1.3
Opened: Jan 18, 2016 Severity: 2-Critical Related Article:
K17124802
If an iRule command refers to a transport-config, the iRule fails validation even if the object exists.
Validation fails even though object exists. Unable to directly refer to a transport-config from an iRule command.
-- iRule command refers to a transport-config. -- iRule validation occurs. Example: create ltm pool p1 members add { 10.2.3.4:5060 } create ltm message-routing sip transport-config tc1 profiles add { udp sipsession } create ltm virtual vs1 destination 10.1.1.50:5060 profiles add { udp sipsession siprouter } create ltm rule r1 ltm rule r1 { when MR_INGRESS { MR::message route config tc1 pool p1 <==command refers to tc1 which is a transport-config object } }
If the name of the transport-config is loaded into a Tcl variable, the Tcl variable can be use to indirectly refer to the transport-config object.
iRule validation logic has been improved to check for the existence of a transport config object.