Duplice Object IDs in Panorama XML

Announcements

Changes to the LIVEcommunity experience are coming soon... Here's what you need to know.

Reply
Chacko42
L4 Transporter

Duplice Object IDs in Panorama XML

Hi Community,

 

We went from 9.1 to 10.0 on Panorama and recently did an Expedition merge (latest version) with an ASA.

Since then, a few objects which are unreferenced in global-find, are unable to be deleted.

When checking panorama running config, I noticed, that a group-name is duplicate in the shared section, with different object ID's:

Chacko42_0-1616764126647.png

Manually cleaning that up, seems to work, but what went wrong?

Shouldn't expedition or the commit validate that kind of stuff?

 

Best Regards
Chacko

Accepted Solutions
Chacko42
L4 Transporter

After manually deleting the duplicate objects from xml config, panorama is working fine again.

I guess the used expedition versioned we used then (can't tell exactly which one it was) had a little problem with the new pan-os-10 config.

I noticed the problem, when importing the panorama xml to expedition, "invalid xml" was alerted.

Best Regards
Chacko

View solution in original post


All Replies
Chacko42
L4 Transporter

After manually deleting the duplicate objects from xml config, panorama is working fine again.

I guess the used expedition versioned we used then (can't tell exactly which one it was) had a little problem with the new pan-os-10 config.

I noticed the problem, when importing the panorama xml to expedition, "invalid xml" was alerted.

Best Regards
Chacko

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!