When attempting to synchronize two JDMs, users may encounter the error "Cannot change random mac prefix when GNFs are defined or running." This issue arises because the MAC prefix is consumed by GNFs, preventing the sync from occurring if the GNFs are already defined or running.
During the commit synchronization process, the following errors are observed:
server1: configuration check succeeds server0: error: Cannot change random mac prefix when GNFs are defined or running error: configuration check-out failed server1: error: remote commit-configuration failed on server0
To resolve this issue, follow the procedure below. This assumes all routing engines on Server 1 are functioning as the master.
Procedure:
Shutdown GNFs in JDM0
request virtual-network-functions <GNF name> stop
2. Delete GNF Configuration on JDM0
config delete virtual-network-function commit no-sync
3. Verify and Update GNF Images (if necessary)
If the GNFs are on the same release, skip step 3 and step 4.
If the image on Server 0 differs from the required version:
request virtual-network-functions delete-image <GNF-name>
4. Add Correct GNF Images
request virtual-network-functions add-image <file-path> <GNF-name>
5. Commit Changes and Sync from the Active JDM
Once the images are successfully added, navigate to the active JDM (JDM1) and execute:
commit sync force