Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.0.0
Opened: Apr 07, 2015 Severity: 3-Major Related Article:
K54534430
tmsh listing of a nonexistent ltm monitor returns incorrect results. (tmos)# list ltm monitor gateway-icmp http ltm monitor gateway-icmp http { adaptive disabled destination *:* interval 5 time-until-up 0 timeout 16 user-defined IP_TOS 0 user-defined SEND "GET /\r\n" }. Note there is no gateway-icmp monitor named http present. The output corresponds to the HTTP monitor.
tmsh listing of a nonexistent ltm monitor returns incorrect results. For example, the following command returns a gateway-icmp http configuration even though it does not exist: (tmos)# list ltm monitor gateway-icmp http.
The issue arises only when querying for a nonexistent monitor whose name matches a valid monitor type, for example, http, https, icmp, and so on.
Use the following command to return the correct results: tmsh list ltm monitor gateway-icmp gateway-icmp. (tmos)# list ltm monitor gateway-icmp does_not_exist 01020036:3: The requested monitor (/Common/does_not_exist) was not found. The listing of non-existing monitor also returns an error as expected.
'tmsh list ltm monitor monitor_type monitor_name' no longer returns output when the named monitor is not the of the specified monitor type. For example, if there is an HTTP monitor on a system named 'http', the query 'list ltm monitor gateway-icmp http' no longer lists the HTTP monitor, even though it is not type gateway-icmp. Note that if the command asks for a monitor that does not exist on the system, the system returns a message similar to the following: 01020036:3: The requested monitor (/Common/http1) was not found. However, if only the type is different, there is no not-found message posted.