Loading...
Loading...
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.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.