RNs

cogbu — Tue, 28 Mar 2023 16:20:39 GMT

3 service connections are being advertised through the 10.0.0.0/8 network via EBGP from data centers. I noticed that traffic from the RN-SPN loopback addresses is all reaching the on-prem environment (10.0.0.0/8) via the same service connection when we'd expect IBGP in Prisma to send traffic to on-prem networks via the nearest service connection. The traffic in question is RN-SPN user-id client connections to one of the user-id collectors that are situated in the Amsterdam data center. there are three SCs, one in US, EMEA, and APAC. But user-id client traffic from our RN-SPNs is all reaching our on-prem networks via the SC in APAC. No matter if the RN-SPN is located in LATAM, for example. I would expect to see RN-SPNs located in LATAM and NAM to reach our on-prem environment via our US-based SC and all EMEA RN-SPNs to go via the EMEA SC. But the user-id traffic from all RN-SPNs is pushed down from Prisma to on-prem via the APAC SC.

set up is using hot potato routing

Is this expected when all three SCs are operational?

topic Re: RNs in Prisma Access Discussions

RNs

Re: RNs