Forum Discussion

  • Michael_Saleem's avatar
    Michael_Saleem
    Icon for MVP rankMVP
    Feb 12, 2025

    You can check by issuing a cURL command to the virtual server (this can be done directly from the BIG-IP's bash shell)

    run util bash

curl -IvLk --http2 https://<FQDN>


    If you see the following in the result output, then this means that the virtual server is not configured to support HTTP/2. You will need to create an http2 profile and a compatible client SSL profile (httprouter profile and server SSL profile will be needed too if you want HTTP/2 Full proxy) and apply it to the virtual server.

     

    ALPN, server did not agree to a protocol

  • Aswin_mk's avatar
    Aswin_mk
    Icon for MVP rankMVP
    Feb 12, 2025

    Hello,

     

    You can test this curl command aswell - curl -I --http2 -k https://<VIP>

  • F5_Design_Engineer's avatar
    F5_Design_Engineer
    Icon for MVP rankMVP
    Feb 12, 2025

    Hi Blue_Whale,

     

    To check if a Virtual IP (VIP) on your F5 LTM supports HTTP/2, you can follow these steps:

    1. Check the HTTP/2 Profile Assignment

    Ensure that the virtual server has an HTTP/2 profile assigned to it. You can do this via the F5 Configuration utility or the command line.

    Using the Configuration Utility:

    1. Log in to the F5 Configuration utility.
    2. Navigate to: Local Traffic -> Virtual Servers.
    3. Select the virtual server you want to check.
    4. Go to the "Resources" tab and look for the "HTTP/2 Profile" under "HTTP Profiles".

    Using the Command Line:

    You can use the tmsh command to list the virtual server configuration and check for the HTTP/2 profile.

    tmsh list ltm virtual <virtual_server_name> profiles

    Look for an HTTP/2 profile in the output.

    2. Verify HTTP/2 Support with Command Line Tools

    You can use command line tools like curl to verify if the VIP supports HTTP/2.

    curl -I --http2 https://<VIP_IP>

    • -I: Fetches the headers only.
    • --http2: Forces the use of HTTP/2.

    If the VIP supports HTTP/2, you should see HTTP/2 in the response headers.

    3. Check the BIG-IP Configuration

    Ensure that the BIG-IP system is configured to support HTTP/2. This includes having the necessary profiles and settings in place.

    Example Command:

    tmsh list ltm profile http2

    This command lists all HTTP/2 profiles configured on the system. Ensure that the profile is correctly configured and associated with the virtual server.

    4. Review the Documentation

    Refer to the F5 documentation for detailed steps on managing HTTP/2 traffic and configuring the HTTP/2 profile.

    If you follow these steps and still encounter issues, it might be helpful to check the logs for any errors or warnings related to HTTP/2 traffic.

     

    Kindly rate

    HTH

    F5 Design Engineer