Error: Request to 'ACQUIRE-CONFIG' has Failed, System Acquiring from, Configurations do not Match

Asset ID:	1-75-1598162.1
Update Date:	2017-05-09
Keywords:

Solution Type Troubleshooting Sure

Solution 1598162.1 : Error: Request to 'ACQUIRE-CONFIG' has Failed, System Acquiring from, Configurations do not Match

Applies to:

Acme Packet 4500 - Version All Versions and later
Net-Net 3810 - Version All Versions and later
Acme Packet 3820 - Version All Versions and later
Acme Packet OS

Purpose

How to troubleshoot error: Request to 'ACQUIRE-CONFIG' has Failed, System acquiring from, configurations do not match

Troubleshooting Steps

When attempting an acquire config, an error such as "System acquiring from, configurations do not match" may be displayed.

For example:

# acquire-config 1.1.1.1
Current config will be replaced by the acquired config.
Continue? [y/n]?: y
Acquire-Config received, processing.
waiting 120000 for request to finish
Request to 'ACQUIRE-CONFIG' has Failed,
System acquiring from, configurations do not match.

When this happens, check the following items:

1.) Perform a 'delete-config' on the session border controller (SBC) which is attempting the acquisition of the config from the Active, subsequently reboot it, and then try the acquire-config again.

2.) If the same issue still occurs, then check if the user/enable passwords on the Active exactly match that of the Standby SBC.

3.) Verify that in the redundancy-config, the peer names exactly match the target names in the boot parameters, as any variance would cause acquire-config to fail as well.

4.) Type "display-running" and "display-current" on the Active SBC to check for any version mismatch between the running-config & current-config.

Assuming all the above conditions are met, acquire-config should then be successful.

Note: If wancom1 and wancom2 are directly connected, crossover cables must be used.

Attachments

This solution has no attachment