Prisma Access: Config load to a previous working version after deleting a sub-tenant on Panorama leads to validation error "interface '-' is not a valid reference"

Prisma Access: Config load to a previous working version after deleting a sub-tenant on Panorama leads to validation error "interface '-' is not a valid reference"

3629
Created On 02/28/22 23:08 PM - Last Modified 12/06/24 03:44 AM


Symptom


  • Prisma Access configured with Multi-tenants on Panorama.
  • Sub-tenant is deleted on Panorama.
  • Now loading a previous working versionĀ on Panorama leads to validation error "interface '-' is not a valid reference".


Environment


  • Panorama managed Prisma Access
  • Supported PAN-OS
  • Multi-Tenant configuration


Cause


Configuration mismatch due to deleted sub-tenants.



Resolution


  1. Manually configure theĀ missing sub-tenants.
  2. Commit the configuration.
  3. Retry loading the configuration snapshot and it should work fine.
  4. Refer to this article for importing Multi-Tenant configuration to Panorama.

To avoid the error:

  1. After deleting any sub-tenants, committing , and accepting this as your new production configuration... save a named-configuration snapshot with a self-explanatory name such as "tenant-deletion-newbaseline-Feb22.xml.
  2. If rollback is needed at some point later, choose a configuration no earlier than this snapshot.


Actions
  • Print
  • Copy Link

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

Choose Language