Suppose the two EMSA instances are EMSA-1 and EMSA-2.

1). Logon to EMSA-1
EMSA-1 EMS CLI> support-enable
setup EMS Support CLI > reset-all

Are you sure you want to reset all EMS data? (no): yes

After the “reset-all” is completed, you will be logged out of the CLI and will need to log back in and rerun the setup.

2). If you fix the misconfiguration issue, if you are using “FT”, you do not want the misconfiguration in the standby instance synced back automatically. You should stop the FT mode temporarily. 

Logon to EMSA-2.

EMSA-2 EMS CLI > stop local
Stopping local EMS instance 0
Stopping local EMS instance 1


3). Log back in to EMSA-1. If an EMS-Gateway is already active, it will be reset by 'reset-all' to the mgmt-gateway. You will need to log back in to re-setup using the mgmt-IP address. Note: defaults from the previous setup will be remembered as the default for each question.

After logging back to CLI using the mgmt-IP address, it will automatically ask to set all parameters. After finishing setting up the parameters, EMS servers on appliances will be automatically started in the “WAIT-FOR-PEER” status.

Saving configuration...
Configuration saved.
Applying configuration...
WARNING: EMS server(s) on this appliance will be restarted.

4). If the EMS-gateway is configured, you will be logged out automatically and will need to log back into EMSA-1 with the EMS-Gateway IP.

You should notice:
_____ INSTANCE 0 , ROLE = PRIMARY _____
EMS State - WAIT-FOR-PEER
_____ INSTANCE 1 , ROLE = SECONDARY _____
EMS State - WAIT-FOR-PEER


setup EMS CLI > forcestart

Note: All post-setup modifications made to the JSON will be lost and need to be reapplied.


5). Go to EMSA-2
EMSA-2 EMS CLI >start local

EMSA-2 EMS CLI > restore-primary-active

restore-primary-active

Moving active servers forces clients to reconnect - are you sure? (no): yes
Switching active host for instance 1

The post-setup modifications made to the JSON in EMSA-1 will be synced to EMSA-2 automatically.