Commit failing with 'IKEv2 gateway <ike-gateway object name> peer gateway address x.x.x.x is not unique among gateways using local address y.y.y.y'

Commit failing with 'IKEv2 gateway <ike-gateway object name> peer gateway address x.x.x.x is not unique among gateways using local address y.y.y.y'

10477
Created On 01/24/23 19:09 PM - Last Modified 09/21/26 09:01 AM


Symptom


  • Prisma Access commit and push fail with the error message below: 

    IKEv2 gateway <ike-gateway object name> peer gateway address <ip addr1> is not unique among gateways using local address <ip addr2>

Environment


  • Prisma Access
  • Remote Networks
  • IPSec Tunnels

Cause


  • A new Remote network site is created using an existing IPSEC termination node.
  • The existing IPSEC termination node being used has another remote network tunnel with the same Peer IKE gateway IP address.
  • The duplicate IP address causes the conflict and is not supported.

Resolution


  1. Use a different IPSEC termination node for the new Remote Network site.
  2. This configuration will cause the tunnel to use a new service IP.
Other users also viewed:
Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000kGUjCAM&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail