Operational Defect Database
BugZero found this defect 1122 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1013937
In-TMM HTTP and HTTPS monitors require RFC-compliant send strings to work.
Last update date:
4/26/2024
Affected products:
BIG-IP
BIG-IP All
Affected releases:
13.1.0
13.1.0.1
13.1.0.2
13.1.0.3
13.1.0.4
13.1.0.5
13.1.0.6
13.1.0.7
13.1.0.8
13.1.1
13.1.1.2
13.1.1.3
Fixed releases:
No fixed releases provided.
Description:
Pool members that should be marked UP are incorrectly marked DOWN. ... No monitor traffic is seen on the wire. ... If pool member monitor logging is enabled, an entry similar to the following example can be seen in the logs: [0][1399] 2021-02-11 11:11:34.709360: ID 44 :TMM::handle_message(TMA_Message<tma_msg_args_notify>*): tmm monitor failed to connect [ tmm?=true td=true tr=false tmm_mid=0:1 addr=::ffff:192.168.10.100:80 srcaddr=none ] If tma debug logging is enabled, an entry similar to the following example can be seen in the logs: Feb 11 11:12:14 bigip1.local debug tmm[2259]: 01ad0019:7: Monitor Agent TMM ... Impact ... Pool member monitoring is impacted and unreliable. ... Conditions ... - In-tmm monitoring is enabled (the bigd.tmm db key is set to enable). - A HTTP or HTTPS monitor has been configured with a send string which is not RFC-compliant. ... For instance, the following string incorrectly includes a space before the Host header: "GET / HTTP/1.1\r\n Host: example.com\...
