Failed to fetch ingest/query FQDN for customer (curl failed)

cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to fetch ingest/query FQDN for customer (curl failed)

L5 Sessionator

Hi Team,

 

I'm trying to onboard one of our firewals to the Cortex Data Lake. It has the logging service license and when I put in the onboarding PSK and click status, I get:

 

Failed to fetch ingest/query FQDN for customer (curl failed)

 

I've tried

 

- Giving the firewall an NTP server

- Removing and re-adding the license

- Manually fetching the certificate (it fails)

 

> request logging-service-forwarding certificate fetch

Successfully scheduled logging service certificate fetch job with a job id of 2132

> show jobs id 2132

Enqueued Dequeued ID Type Status Result Completed
------------------------------------------------------------------------------------------------------------------------------
2019/10/14 10:18:24 10:18:24 2132 LCaaS-certificate-fetch FIN FAIL 100 %
Warnings:
Details:

 

- Manually fetching the customer info (it fails)

 

> request logging-service-forwarding customerinfo fetch

Successfully fetch Logging Service region info

 

> request logging-service-forwarding customerinfo show

Server error : Unable to read the LCaaS customer information. Please re-fetch region info

1 ACCEPTED SOLUTION

Accepted Solutions

@LukeBullimore: Yes, TAC case already closed. If you are not on 9.0.4 or 8.1.13 (not available yet), you need to contact TAC to set the tenant-id for cortex/logging service.

Problem is fixed in the versions mentioned above - no workarounds available, so TAC creates root access to device and edits local files on each firewall

Best Regards
Chacko

View solution in original post

6 REPLIES 6

L4 Transporter

Hi - I'm experiencing exactly the same error and opened a TAC case for this.

Do you got any feedback on your situation?

Best Regards
Chacko

Same here.. Guess I'll be opening one as well.

@cdowdy @Chacko42 

 

Did you both get anything useful from your TAC case? This is still a problem for us and its fallen off my radar up until now.

 

Cheers,

Luke.

@LukeBullimore: Yes, TAC case already closed. If you are not on 9.0.4 or 8.1.13 (not available yet), you need to contact TAC to set the tenant-id for cortex/logging service.

Problem is fixed in the versions mentioned above - no workarounds available, so TAC creates root access to device and edits local files on each firewall

Best Regards
Chacko

View solution in original post

Yep, did that on Friday. Easy fix for TAC with root.  

 

[root@XXXXXXXXX ~]# sdb -i cfg.saas.custid
cfg.saas.custid: string (10 bytes)
[root@XXXXXXXXX ~]# sdb cfg.saas.custid=None
cfg.saas.custid: None
[root@XXXXXXXXX ~]# sdb cfg.saas.custid=123456789
cfg.saas.custid: 123456789
[root@XXXXXXXXX ~]# sdb -i cfg.saas.custid
cfg.saas.custid: int (len 4)

 

re-license FW's from Panorama

 

Finally, on each fw:

request logging-service-forwarding certificate delete

request logging-service-forwarding certificate fetch

L0 Member

Hi All,

I have seen this issue with other customers and I was able solve it with following steps :

  1. Delete Logging Service License key :

    Rutger@panGW> delete license key Logging_Service_xx_xx_xx.key​
    successfully removed Logging_Service_xx_xx_xx.key

  2. Request license Fetch:
    Rutger@panGW> request license fetch License entry:
    License entry:
    Feature: Logging Service
    Description: Device Logging Service
    Serial: xxxxxxxxx
    Authcode:
    Issued: July 29, 2019
    Expires: July 27, 2022
    Expired?: no
    Log Storage TB: 1

  3. Check to see if the logging service region is being fetched. 
    In my case it was not so it was manually entered via cli:

    Rutger@panGW> request logging-service-forwarding customerinfo show
    Server error : Unable to read the LCaaS customer information. Please re-fetch region info​

  4. Configure Location Manually via CLI:
    Rutger@panGW> configure
    Entering configuration mode
    Rutger@panGW# set deviceconfig setting logging logging-service-forwarding logging-service-regions {LOCATION, Example Europe or Americas}
    Rutger@panGW# exit
    Exiting configuration mode
    COMMIT YOUR CHANGES
  5. Delete the logging service certificate

    Rutger@panGW request logging-service-forwarding certificate delete
    Successfully deleted Logging Service certificate.

  6. MANUALLY enter the PSK that you generated from the data lake

    Rutger@panGW> request logging-service-forwarding certificate fetch-noproxy pre-shared-key YOUR_KEY_HERE
    Successfully scheduled logging service certificate fetch job with a job id of 12


  7. Check the job ID it should say finished OK successful

Now your Firewall is onboarded with data lake

PS: in an active-passive cluster you only need to this on one of both firewalls, all the rest will be synced over the HA.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!