Forum Discussion

Peter_Baumann_5's avatar
Peter_Baumann_5
Icon for Nimbostratus rankNimbostratus
Nov 06, 2015

Upgrade from v11.6.0 HF4 to v11.6.0 HF6 breaks some monitors

Hi all, Is there any problem known with v11.6.0 HF6 upgrade with http monitors? The customer was using the following http monitors in v11.6.0 HF4: `GET /_layouts/15/success.aspx HTTP/1.1\r\nHost...
application delivery
bug
deployment
LTM
monitor
  • Chris_103447's avatar
    Chris_103447
    Nov 16, 2015

    I got bit by this last night, which resulted in extended downtime until we found the cause. On our LTM-VE (standalone), it only doubled the backslashes, which allowed it to work on some pools still. Our 2000s HA pair got triple backslashes, though, and marked everything down as a result. Not good.

     

    https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-ltm-11-5-1.htmlrn_ki

     

    ID 453256 seems to point to an issues with double quotes are backslashes in monitors. Seems pretty hard to avoid getting hit by it (I'd probably over/under escape).

     

    https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-ltm-11-6-0.htmlrn_ki

     

    Different ID, 291584, points to another backslash issue where the workaround is to delete the extras.

     

RossVermette's avatar
RossVermette
Icon for Nimbostratus rankNimbostratus
Nov 27, 2015

Ran into this also. Apparently the extra "\" check was added in some version after 11.6.0 HF1. One other issue I noticed is that if you use "auth" username/password in your monitor, make sure there is no "\r\n" at the end of your send string(even though the online help screen says it needs one), as what would happen in packet the HTTP header there would be new line between the http header and the auth header, which would cause a 400 bad response from a backend server that you're monitoring.