Cisco Prime Infrastructure HA - Secondary server not registering on Primary

[EstebanLopezSilva]

I need some help regarding the HA configuration of CPI.

I followed the CPI 3.4 Administrator guide for its configuration, and set an Authentication key on the secondary server. When I tried to register the secondary server on the primary, I get the following error:

"authentication key does not match between primary x.x.x.x and secondary servers y.y.y.y"

I changed the auth key on the secondary server by using the ncs auth key command, saved, and reloaded the appliance, and still got the same error (I double checked for any typos). The secondary server has the role of secondary, and the primary says primary.

Both CPI are in the same network segment and there's no Firewall between them (they're both in the DMZ). 

Details about both servers:

Cisco Application Deployment Engine OS Release: 3.1

ADE-OS Build Version: 3.1.0.001

ADE-OS System Architecture: x86_64

Version inormation of installed application

-----------------------------------

Cisco Prime Infrastructure

********************************************************

Version : 3.4.0

Build: 3.4.0.0.348

I tried finding something similar on the community web with no luck, so any help would be appreciated!

Regards!

[marce1000]

Ref :  https://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/3-4/admin/guide/bk_CiscoPrimeInfastructure_3_4_AdminGuide/bk_CiscoPrimeInfastructure_3_4_AdminGuide_chapter_01010.html#con_1089399

                     Take into account these key parameters which must be honored :

 An authentication key of any length. It must contain at least three of the following types of characters: lowercase letters, uppercase letters, digits and special characters. You will enter this authentication key when you install the secondary server. The HA implementation uses this key to authenticate communications between the primary and secondary servers. Administrators also use the key to configure HA in the primary server, and to log on to the secondary server's Health Monitor page to monitor the HA implementation and troubleshoot problems with it.

M.