Logging service not connected to Cortex Data Lake

cancel
Showing results for 
Search instead for 
Did you mean: 

Logging service not connected to Cortex Data Lake

L2 Linker

Hi All,

 

We cant enable the logging service and not connected to Cortex Data lake. The region field showing empty.

Oblagonte_0-1646008371347.png

 

 

 

Any idea on how to check and troubleshoot?

 

Cortex Data Lake 

 

1 ACCEPTED SOLUTION

Accepted Solutions

L2 Linker

Hi All,

 

We checked the CDL status and found an error "failed to validate server certificate for endpoint api.paloaltonetworks.com"

These errors generally comes when one of the port or fqdns is not allowed in the environment.
https://docs.paloaltonetworks.com/cortex/cortex-data-lake/cortex-data-lake-getting-started/get-start...
Further we checked the traffic logs and found port 444 was not allowed and hitting the interzone default rule season end reason was policy deny.
We configured a new security policy rule and allowed the required ports to make the connection between firewall and CDL, in security rule we called a CDL log forwarding profile to forward the log types to the CDL.
We verified and could see live logs started ingesting into the CDL hub.

View solution in original post

6 REPLIES 6

Cyber Elite
Cyber Elite

Hi @Oblagonte,

This field should have a drop down options.

Do you have latest content updates installed? Are you trying to push this configuration from Panorama or configure it locally on the firewall?

 

You may also want to check the following KB, there are some useful commands - https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMXKCA4

Hi @Astardzhiev 

 

It is configure locally on the firewall and content updates was latest. Is there any idea?

 

Seems like there are limited documentation related to this.

 

Thanks for your idea

This is result for request logging-service-forwarding status.

 

Oblagonte_0-1646185777403.png

Any idea?

Hey @Oblagonte ,

The third line from the bottom look strange...

- Is there any network device on the path from firewall management to Internet that could apply SSL decryption? If firewall is failing to validate API certificate, it is possible that traffic is being decrypted and certificate is replaced with CA that FW does not expect

 

Have you checked the link I shared in my previous post?

What output you get from all commands from steps 1,2 and 3? Please hide any sensitive data as customer ID, FQDNs, etc.

Hi,

Thanks for the respond. Below is the result of the command.

 

> request logging-service-forwarding customerinfo show


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

 

> request logging-service-forwarding certificate info

Certificate chain verification: OK
Public and private key pair match: Yes

Certificate expired: No

Certificate details:

Certificate:
Data:
Version: 3 (0x2)
Serial Number:
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXxx
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN=XX-Client-Issuing-XXX-XX, O=Palo-Alto-Networks-Inc., C=US
Validity
Not Before: XXXXXXXXXXXXXXXXXXXXXXXX
Not After : XXXXXXXXXXXXXXXXXXXXX
Subject: CN=XXXXXXX/serialNumber=XXXXXXXXX, OU=Cloud, O=Paloalto, L =XXXXXXXXXX, ST=CA, C=US

Authority Information Access:
CA Issuers - XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXx
OCSP - XXXXXXXXXXXXXXXXXXXXXXXXXx

X509v3 Certificate Policies:
Policy: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

X509v3 Extended Key Usage:
TLS Web Client Authentication
X509v3 CRL Distribution Points:

Full Name:
URI:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

X509v3 Subject Key Identifier:
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
X509v3 Key Usage: critical

Successfully fetch LCaaS certificate info

L2 Linker

Hi All,

 

We checked the CDL status and found an error "failed to validate server certificate for endpoint api.paloaltonetworks.com"

These errors generally comes when one of the port or fqdns is not allowed in the environment.
https://docs.paloaltonetworks.com/cortex/cortex-data-lake/cortex-data-lake-getting-started/get-start...
Further we checked the traffic logs and found port 444 was not allowed and hitting the interzone default rule season end reason was policy deny.
We configured a new security policy rule and allowed the required ports to make the connection between firewall and CDL, in security rule we called a CDL log forwarding profile to forward the log types to the CDL.
We verified and could see live logs started ingesting into the CDL hub.

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!