Forum Discussion

jhonyy_rg's avatar
jhonyy_rg
Icon for Altostratus rankAltostratus
Aug 23, 2023

monitor does not work https

The custom https monitor that we have created does not work, before uploading the f5 version, it worked correctly, We don't know if there may be any syntax error, due to this version, or another parameter., this monitor check 

 

  • Hi jhonyy_rg , 
    I played around your current version on F5 Bug tracker ,

    and I think you are hiting in this bug >>>  https://cdn.f5.com/product/bugtracker/ID1026781.html 

    > in your send string I see \r\n\r\n so it's doubled , try to remove one  "\r\n" to make your send sring has singe "\r\n" not doubled. 

    > Or try one workaround that are in the bug article which i sent above. 

    >> To capture monitor traffic : 

    tcpdump -s0 -nni 0.0:nnnp src host <Self_IP address> and dst host <Backeend_server_IP> and dst port 443 -vw /var/tmp/HTTPs_monitor.pcap
    
    
    # if you don't know which selfip address monitor your server use ip route get utility on bash like below : 
    
    bash#ip route get < Backend_server_IP > 
    
    This command will give you which self IP on your bigip monitor your server. 
    
    Note : if your appliace in HA group ( you have active and standby ) this Capture will work efficient with you as , F5 bigip monitor the backend servers using selfip address and send real data traffic using Floating ip address on HA deployment. 
    So if you run standalone not HA , This Capture command will capture ( Real data traffic and monitor traffic too ) because standalone systems use selfip address to handle users data traffic as well as bigd or monitor traffic. 


    Check this and let me know 🙂 

5 Replies

  • Hi jhonyy_rg , 

    What is the new version that you have upgraded to or the current running version. 

    Also , it will be good to take a packet capture for this https monitor traffic from bigip selfip and backend server. 

    • jhonyy_rg's avatar
      jhonyy_rg
      Icon for Altostratus rankAltostratus

      hellow mohamed

      thanks for you answer

      the version of f5 is 

      BIG IP 15.1.7

      How do I capture packets, could you give me an example?

      • Hi jhonyy_rg , 
        I played around your current version on F5 Bug tracker ,

        and I think you are hiting in this bug >>>  https://cdn.f5.com/product/bugtracker/ID1026781.html 

        > in your send string I see \r\n\r\n so it's doubled , try to remove one  "\r\n" to make your send sring has singe "\r\n" not doubled. 

        > Or try one workaround that are in the bug article which i sent above. 

        >> To capture monitor traffic : 

        tcpdump -s0 -nni 0.0:nnnp src host <Self_IP address> and dst host <Backeend_server_IP> and dst port 443 -vw /var/tmp/HTTPs_monitor.pcap
        
        
        # if you don't know which selfip address monitor your server use ip route get utility on bash like below : 
        
        bash#ip route get < Backend_server_IP > 
        
        This command will give you which self IP on your bigip monitor your server. 
        
        Note : if your appliace in HA group ( you have active and standby ) this Capture will work efficient with you as , F5 bigip monitor the backend servers using selfip address and send real data traffic using Floating ip address on HA deployment. 
        So if you run standalone not HA , This Capture command will capture ( Real data traffic and monitor traffic too ) because standalone systems use selfip address to handle users data traffic as well as bigd or monitor traffic. 


        Check this and let me know 🙂