Transitioning from an active PSK to a keychain
For greenfield deployments, it is recommended that the user choose between an active PSK or a keychain for PSK rotation, as the two methods behave differently.
Existing deployments can upgraded from an active PSK implementation by configuring a keychain on the CA's static CAK. The keychain always takes precedence over an active PSK configuration under the static CAK, even if the keychain key entries are not active or the MKA sessions for the keychain are not operationally up.
To configure a keychain, the CA must be administratively disabled first. When a CA is administratively disabled, all MKA sessions using that CA are deleted.
Active PSK configuration can be restored by administratively disabling the CA again and removing the keychain.