Sync Configuration Between Two ISE Standalone Nodes

[imhessam]

I have two Cisco Identity Services Engine (ISE) standalone nodes, Node1 and Node2. My goal is to sync the configuration from Node1 to Node2, but I want to avoid any IP address conflicts in my network. Both nodes have different management IP addresses and hostnames, and I do not want to change them during the configuration sync.

I plan to back up Node1's configuration and restore it to Node2. However, I want to ensure that only the configuration (policies, authentication profiles, etc.) is restored to Node2, and the network-related settings like IP addresses and hostnames are excluded from the restoration to avoid conflicts.

Can anyone provide detailed steps on how to:

Backup Node1’s configuration without including network settings.

Restore the backup to Node2 while ensuring that the IP addresses and hostnames of Node2 are not overwritten.

Verify that Node2 is synced properly and avoid any issues with IP conflicts in the network.

Any advice or best practices would be greatly appreciated!

Thanks in advance!

[Arne Bier]

Hello @imhessam 

The short answer - not possible to be selective about the config backup process - config backup process is not customisable and you will get everything in one file. There are hundreds (if not thousands) of files and database backups in there. 

Config backup doesn't include any IP address details if you tell ISE during the restore process that you DON'T want to restore the ADE-OS (the ISE "CLI config").  Therefore, backup node1, and then restore it on node2 (which can have a different hostname and IP address) - it will be fine.