We are trying to prove the recovery procedure from AVA400 to AVA-c4, however during configuration import we receive internal error (code 1003). From the logs it appears that the difference in version is causing the problem:
Apr 18 11:33:28 localhost mgmtd: [mgmtd.INFO]: Configuration database with different version hash detected for db restored-20170418-113328-tmp: reg 62a9fb03 db bc5f5a07.
Apr 18 11:33:28 localhost mgmtd: [mgmtd.ERR]: md_db_open_internal(), mdm_db.c:2602, build (null): Error code 14150 (Cannot fallback config db when saving is not allowed) returned
Apr 18 11:33:28 localhost mgmtd: [mgmtd.ERR]: md_db_import(), mdm_db.c:4006, build (null): Error code 14150 (Cannot fallback config db when saving is not allowed) returned
The error is for the configuration database, which is probably because of the differences in hardware between the AVA400 and AVA-c4. For example, the database may have an IP address for the interface e0a but this interface does not exist on the AVA-c4.
Engineering is taking steps to make the exported configuration universally apply-able. In the meantime configure the AVA-c4 network and cloud settings using the bucket name of the AVA400. Next extract the encryption key from the configuration archive (it's a tgz file) then import it manually.
Thanks for the response, @jgercken. We actually use a KMIP server so there is no encryption key to extract from the configuration archive. Should I need to perform extra steps besides configuring the KMIP server in addition to the network and cloud settings?