# Feature History for SME Key Management

Table 1-5 lists the release history for this feature.

Table 1-12 Feature History for SME Key Management

Feature Name | Releases | Feature Information
Software change | OL-25317-01 | In Release OL-25317-01, Fabric Manager is changed to DCNM for SAN (DCNM-SAN).
4.1(1c) | In Release 4.1(1b) and later, the MDS SAN-OS software is changed to MDS NX-OS software. The earlier releases are unchanged and all references are retained.
Migrating KMC server | 4.1(1c) | In 4.1(1c), the KMC server can be migrated.
Accounting log | 4.1(1c) | In 4.1(1c) and later, users can view the rekey operations and their status in the SME tab of the Fabric Manager Web Client.
High availability KMC server | 4.1(3) | High availability KMC can be configured by using a primary and secondary servers. In 4.1(3), HA settings are available on the Key Manager Settings page. The primary and secondary servers can be chosen during cluster creation. The primary and secondary server settings can be modified in the Cluster detail page.
Auto replication of media keys | 4.1(3) | In 4.1(3) Tape Key replication was known as Remote Replication. A remote replication relationship can be set between volume groups. SME allows you to automatically replicate the media keys from one SME cluster to one or more clusters. In 4.1(3), remote replication relationship settings are available.
Host names are accepted as server addresses | 4.1(3) | You can enter IP addresses or host names for the servers.
Volume key rekey | 3.3(1c) | Volume keys are rekeyed to ensure better security or when key security is compromised.
Master key rekey | 3.3(1c) | In the advanced mode, the smart card replacement triggers a master key rekey and a new version of the master key is generated for the cluster. The new set of master keyshares are stored in the smart cards. All the volume group keys are also synchronized with the new master key.