Hi!
You have different LMKs, so, the key @mfilippov used on his encironment can not be reused on different HSMs with different LMK. Also, can not be verified. When HSM receivs the key, ed. UE6A4D315D63932332163FBDA8ECCD2BF from @teryakif example first it decrypts the key inside itself using appropriate LMK pair (keys used in commands are cryptograms itself). Only decrypted key is checked to be parity adjusted.
So, you can generate the new ZPK key using Thales Simulator using A00001U host command or KG console command and try it.
If you need specific key to be used, first you should export ZPK under ZMK shared between HSM and HSM simulator and import it under HSM simulator LMK (it uses Thales Test Variant LMK), Only after such actions the key can be used with HSM simulator and will not return parity error.
Regards,
Juris
You have different LMKs, so, the key @mfilippov used on his encironment can not be reused on different HSMs with different LMK. Also, can not be verified. When HSM receivs the key, ed. UE6A4D315D63932332163FBDA8ECCD2BF from @teryakif example first it decrypts the key inside itself using appropriate LMK pair (keys used in commands are cryptograms itself). Only decrypted key is checked to be parity adjusted.
So, you can generate the new ZPK key using Thales Simulator using A00001U host command or KG console command and try it.
If you need specific key to be used, first you should export ZPK under ZMK shared between HSM and HSM simulator and import it under HSM simulator LMK (it uses Thales Test Variant LMK), Only after such actions the key can be used with HSM simulator and will not return parity error.
Regards,
Juris