Cortex - many aged-out connections on 35.244.133.254

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cortex - many aged-out connections on 35.244.133.254

L0 Member

Hello,
We are experiencing a high number of aged-out connections from our Cortex agents and brokers on 35.244.133.254.
When the connection is successful, the app-id traps-management-service is detected by our firewall.
Do you also encounter this behavior?
Thanks !

 

2 REPLIES 2

L6 Presenter

@RezhoPsq wrote:

Hello,
We are experiencing a high number of aged-out connections from our Cortex agents and brokers on 35.244.133.254.
When the connection is successful, the app-id traps-management-service is detected by our firewall.
Do you also encounter this behavior?
Thanks !

 


@RezhoPsq My guess that address 35.244.133.254 is a part of Cortex's infra.  That IP space is registered to GPC and Palo uses GPC for a lot of their services.  Also, if you look through your system logs you'll see other services like URL and others connecting to "35" addresses registered to GPC.

Yes no doubt about it : Enable access to required PANW resources • Cortex XDR 3.x Documentation • Palo Alto Networks documen...

But why so many TCP aged-out ? Generally, it means there's a network problem.

  • 581 Views
  • 2 replies
  • 0 Likes
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!