Looks like it might be bug 15982024 where the target is already part of a cluster. Can you check your unpromoted targets (Setup -> Add Target -> Auto Discovery Results -> tab Agent Based Targets) and see if a cluster on either of those hosts is already discovered but not yet promoted. If so, you can try to delete that discovered cluster, and retry the cmd.
The following examples show possible log file locations:
If you do not specify a configuration directory when you run the
setup verb (
-dir option is omitted), EM CLI assumes the
.emcli configuration directory is located within your local home directory. The log files are placed at the root level of the
.emcli directory. The
.emcli directory must be local (not mounted remotely).