An engineer is troubleshooting BGP routing between a customer data center and Prisma Access over a Service Connection. The data center router is advertising routes, but Prisma Access is not installing them into the routing table. What is the most likely cause?
Trap 1: The BGP hold timer is set higher than 180 seconds
Hold timers do not prevent route installation if the BGP session is successfully established.
Trap 2: BGP authentication type is set to MD5 instead of SHA-256
Prisma Access supports MD5 and standard BGP authentication; mismatch would prevent peering entirely rather than accepting peers without installing routes.
Trap 3: The Autonomous System Number (ASN) is a private 4-byte ASN
Prisma Access supports both public and private ASNs for BGP peering.
- A
The advertised prefixes overlap with the reserved Prisma Access internal service subnet 10.255.0.0/16
Prisma Access reserves specific internal subnets (like 10.255.0.0/16) and will drop or ignore conflicting advertised prefixes.
- B
The BGP hold timer is set higher than 180 seconds
Why wrong: Hold timers do not prevent route installation if the BGP session is successfully established.
- C
BGP authentication type is set to MD5 instead of SHA-256
Why wrong: Prisma Access supports MD5 and standard BGP authentication; mismatch would prevent peering entirely rather than accepting peers without installing routes.
- D
The Autonomous System Number (ASN) is a private 4-byte ASN
Why wrong: Prisma Access supports both public and private ASNs for BGP peering.