Forum Discussion

LucidCobia's avatar
LucidCobia
Icon for Altocumulus rankAltocumulus
Jan 04, 2023

How to delete proxy sys db configurations on ASM?

Hello Everyone,

I'm having an issue here where I'd like to totally remove the Proxy Configurations.As what happens here is that the ASM tries to resolve <null> as a domain so the update fails.

We are using TMOS v14.1

Thanks in advance!

 

    • LucidCobia's avatar
      LucidCobia
      Icon for Altocumulus rankAltocumulus

      Thank you! This is exactly what I was looking for.

  • Hello LucidCobia , 
    Do you want to get updates via proxy ? if you want that , Follow the below KB to configure " db proxy.* " replace the " NULL " Values :
    https://support.f5.com/csp/article/K10942531
    Also below KB Can be useful : 
    > https://support.f5.com/csp/article/K15931914

    To get an overview about how F5 gets its updates , look at the below article : 
    > https://support.f5.com/csp/article/K8217#proxy1


    Otherwise , F5 can get its updates with routes dependances , I mean F5 relies on it default routes to get these updates , without looking to get its updates via Proxy. 

    I hope this helps you. 

    • LucidCobia's avatar
      LucidCobia
      Icon for Altocumulus rankAltocumulus

      Hello Mohamed_Ahmed_Kansoh ,

      Thanks for your response, but this is the opposite of what I'm trying to acheive.

      We decided we don't want to use the proxy service that's why the proxy.host is <null>

      However, during the auto upadtes the ASM tries to resolve the <null> as if the proxy is configured.

      2022-12-22 12:14:40 ERROR Curl:53 - Curl fail: exit = 5, /usr/bin/curl -X POST -H Content-Type: text/xml;charset=UTF-8 -H SOAPAction: SoftwareUpdate --user dpi@f5.com:DPIautoSIGupdate -H User-Agent: bigip/14.1.4 -d @- --proxy https://<null>:9400 https://callhome.f5.com/soa/softwareupdate/ , with error:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                       Dload  Upload   Total   Spent    Left  Speed

        0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (5) Could not resolve proxy: <null>

  • Hi LucidCobia 

    By default the BIG-IP does not use a proxy to run system update, it will use the default management route ,but In some scenarios you may want to configure the BIG-IP to run system updates using a web proxy ,so if you need this you can do it by using below steps:

    1. Log in to tmsh by typing the following command:
      tmsh

    2. Set the destination proxy server by using the following command syntax :
      modify /sys db proxy.host value <hostname>
      Note: In this command syntax, <hostname> is the destination proxy host name.

    3. Set the destination proxy server port by using the following command syntax:
      modify /sys db proxy.port value <port>
      Note: In this command syntax, <port> is the numeric port value of your proxy host.

    4. Set the destination proxy server protocol by using the following command syntax:
      modify /sys db proxy.protocol value <protocol>
      Note: In this command syntax, <protocol> is http or https.

    5. To set the destination proxy server username, use the following command syntax:
      modify /sys db proxy.username value <username>
      Note: In this command syntax, <username> is the username for authentication to the proxy server.

    6. To set the destination proxy server username password, use the following command syntax:
      modify /sys db proxy.password value <password>
      Note: In this command syntax, <password> is the username password when authenticating to the proxy server.

    7. Exit tmsh by typing the following command:
      quit

    Thanks,