Forum Discussion

Mario_Velazque1's avatar
Mario_Velazque1
Icon for Nimbostratus rankNimbostratus
Aug 19, 2014

LTMVE 11.3 vs 11.4 http monitor

i was playing with VE editions in my lab, a very simple scenario, one web server, listening on port 7010 and 7020. each port is a different pool member. everything else is configured with defaults.

 

with 11.3 (trial edition) pool members are monitored with http(no need to modify nothing since monitor knows the http server is listening on other port) works fine

 

with 11.4 (lab edition) same configuration, monitors goes immediately to offline, it seams they don't recognize that the port is 7010 or 7020. i made sure http service was running correctly (used curl and tcpdump)

 

any suggestion on how to fix this? or there is a mayor change in the way monitors are implemented in 11.4?

 

thanks in advance

 

Mario

 

APM
application delivery
deployment
LTM
security
TMOS
virtualization

5 Replies

Sort By
    • Mario_Velazque1's avatar
      Mario_Velazque1
      Icon for Nimbostratus rankNimbostratus
      Aug 20, 2014
      yes tcpdump and curl output are the same, also checked link you sent but no luck, 11.4 still offline.
    • Mario_Velazque1's avatar
      Mario_Velazque1
      Icon for Nimbostratus rankNimbostratus
      Aug 20, 2014
      yes tcpdump and curl output are the same, also checked link you sent but no luck, 11.4 still offline.
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Aug 20, 2014

    yes tcpdump and curl output are the same, also checked link you sent but no luck, 11.4 still offline.

     

    it must not be the same.

     

    who sent reset first? was the connection reset during ssl handshake or after the handshake? if it was during the handshake, was cipher suite same?

     

    if the connection was reset after the handshake, you may have to decrypt traffic. the server private key is needed. to decrypt traffic, remove https monitor from the pool first, start tcpdump and then re-assign the monitor (we have to capture from the very first packet).

     

    another way is to use openssl s_client to test health monitor's send and receive string.

     

    testing HTTPS with openssl

     

    http://blog.yimingliu.com/2008/02/04/testing-https-with-openssl/