After one or more identity collections are run, some of the users now have duplicate identities. Ever since upgrading NCM to 7.2 the we see two backups running within an hour. Issue The application is then upgraded to 7.0.1 or above.
We then merge the addresses and address groups into our Panorama and finally merge the security policies to the appropriate device group to get the rules setup for the new firewall. We have a nightly job scheduled that does a config backup on all nodes in NCM.
#Duplicacy upgrading update
We always run the remove duplicate objects step(s) as we prep a configuration. When using a constituent update batch to enter new constituents there is no duplicate check to a constituent record if the original constituent record was. We are running Expedition version 1.1.65, Spark Dependencies 0.1.3-h2 and Best Practices 3.21.3. We have built a number of the firewalls on this Panorama (converting Cisco ASA configs to PA VM-500s).
We have over 7700 address groups defined and this was a 5 hour exercise to run the commit many, many times to find the problem address groups, remove the duplicate objects within them and then commit those changes to Panorama and run the commit again, in order to find the next one. Fragmenting the backup among these systems results in inherently less efficient deduplication and over buying when new systems are added for performance.
#Duplicacy upgrading upgrade
As we attempted to commit the upgrade to the Panorama, we encountered the new requirement that Panorama 10.0.x code enforces no duplicate address objects allowed within an address group. The big data enterprise then has multiple often dozens of individual systems that need ongoing tuning, upgrading, maintenance as well as space, power and cooling in the data center. We upgraded our Panorama from 9.1.8 to 10.0.7 over the weekend.
0 kommentar(er)
