For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Zuke's avatar
Zuke
Icon for Cirrostratus rankCirrostratus
Apr 28, 2021
Solved

BIG-IQ : Error when adding device

I'm standing up a new pair of APM/LTM guests on a BIG-IQ CM. When I add the guests, the standby APM guest fails to import. From the BIG-IQ GUI, I get this message: Trust establishment fail...
  • Zuke's avatar
    May 06, 2021
    curl --verbose -sku "admin:<redacted>" https://bigip2/mgmt/shared/identified-devices/config/device-info  | jq -r
     
    > GET /mgmt/shared/identified-devices/config/device-info HTTP/1.1
    > Authorization: Basic YWRtaW46XmlhTCpSXlBCaC54ajgzOHVLLzhA
    > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/1.0.1l zlib/1.2.3 libidn/1.18
    > Host: <redacted>
    > Accept: */*
    > 
    < HTTP/1.1 400 Bad Request
    < Date: Wed, 05 May 2021 15:02:27 GMT
    < Server: Jetty(9.2.22.v20170606)
    < Set-Cookie: BIGIPAuthCookie=SN8F4Fr0VS8JJ4KZDAobOZ4BkXkfRKADH22x2Hpa; path=/; Secure; HttpOnly
    < Set-Cookie: BIGIPAuthUsernameCookie=admin; path=/; Secure; HttpOnly
    < X-Frame-Options: SAMEORIGIN
    < Strict-Transport-Security: max-age=16070400; includeSubDomains
    < Content-Type: application/json; charset=UTF-8
    < Pragma: no-cache
    < Cache-Control: no-store
    < Cache-Control: no-cache
    < Cache-Control: must-revalidate
    < Expires: -1
    < Content-Length: 0
    < X-Content-Type-Options: nosniff
    < X-XSS-Protection: 1; mode=block
    < Content-Security-Policy: default-src 'self'  'unsafe-inline' 'unsafe-eval' data: blob:; img-src 'self' data:  http://127.4.1.1 http://127.4.2.1
    < Connection: close
    < 
    * Closing connection #0
    * SSLv3, TLS alert, Client hello (1):
    } [data not shown]

    The issue was related to RPM processes being stuck on the guest. I ran the above curl command (per F5 support) from both BIG-IQ and the guest itself and the results were the same. Running a filesystems check and rebooting the guest fixed the issue. Thanks Lucy.