Redistribute Global protect mappings to another FW

Reply
jesuscano
L4 Transporter

Redistribute Global protect mappings to another FW

Hi,

 

We can not identify GP users in a remote FW. We can see all AD mappings but not GP. I explain the scenario:

 

INTERNET  ---------------> FW Central (gateway GP) -----> MPLS --------------> Remote FW PALO ALTO

 

both PA are integrated with LDAP, but not have userid agents.

We can see the AD users in both PA, but when a user is connecting by Global protect, the remote FW Palo Alto can NOT identify the mapping USER/IP.

 

In FW Central we can see          10.0.0.1 domain/david.james  GP

but in FW remote                       10.0.0.1       uknown unknown

 

This is normal because GP is only in FW Central, but there is any way to redistribute the GP mapping to the remote FW???

 

thanks

 


Accepted Solutions
vsys_remo
Cyber Elite


@santonic wrote:

It redistributes User-ID info no matter which source it came from (GP, User-ID agent, AD, syslog...)


The only exception are mappings from Terminal Server agents which cannot be redistributed.

View solution in original post


All Replies
santonic
L5 Sessionator

jesuscano
L4 Transporter

Yes, but without userid agents? and GP users information?

 

what config we have to do in the FW which will receive the mappings??? i see that we only configure the FW will send the mappings, but in the fw receiving?

santonic
L5 Sessionator

You don't need agents for GP users. PA which terminates GP connections has all the info about these users.

 

On receiving PA you set the first PA as User-ID agent.

 

 

jesuscano
L4 Transporter

Ues, i know its not necessary agents for GP. But a FW can send all GP users info matches to another FWs???? or the FW can only send UIA/AD info to another FW?

santonic
L5 Sessionator

It redistributes User-ID info no matter which source it came from (GP, User-ID agent, AD, syslog...)

vsys_remo
Cyber Elite


@santonic wrote:

It redistributes User-ID info no matter which source it came from (GP, User-ID agent, AD, syslog...)


The only exception are mappings from Terminal Server agents which cannot be redistributed.

View solution in original post

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!