Symptoms
If an iRule command refers to a transport-config, the iRule fails validation even if the object exists.
Impact
Validation fails even though object exists. Unable to directly refer to a transport-config from an iRule command.
Conditions
-- 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
}
}
Workaround
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.
Fix Information
iRule validation logic has been improved to check for the existence of a transport config object.
