Technical data

290 Fabric OS Encryption Administrator’s Guide (DPM)

53-1002720-02

Fabric OS and DPM Compatibility Matrix

DPM 3.1 introduces the GKA feature, which is incompatible with the RKM 2.1.1 client. DPM 3.2

offers a solution to resolve this incompatiability issue with the RKM 2.1.1 client. DPM 3.1 client is

compatible with DPM 3.x servers, but is not compatible with RKM 2.x servers.

Because of the limitations associated with the RKM 2.1.1 client and the DPM 3.1 server, it is

recommended that you move to DPM 3.2 server instead of v3.1.

Table 15 identifies Fabric OS and DPM compatibility.

Splitting an encryption group into two encryption groups

In this example, which is represented in Table 16, you have one encryption group with four nodes

from which you want to remove two of the nodes and add them to a new encryption group.

1. Enter the following command on FOS1 to reclaim the VI/VT WWN base for FOS3:

Admin:switch> cryptocfg --reclaimWWN -membernode <FOS3-WWN>

When prompted, enter yes.

2. Enter the following command on FOS1 to propagate the change to all nodes in the EG:

Admin:switch> cryptocfg --commit

3. Enter the following command in FOS1 to eject node FOS3 from the EG:

Admin:switch> cryptocfg --eject -membernode <FOS3-WWN>

4. Enter the following command on FOS1 to deregister the ejected node from the encryption

group:

TABLE 15 Compatibility Matrix

Fabric OS version Client SDK Server version

RKM 2.7.x DPM 3.2

v7.0.1 and earlier RKM 2.1.1 Yes Yes

v7.1.0 and later DPM 3.1 No Yes

TABLE 16 Splitting an encryption group

Encryption group Nodes

Original EG FOS1 (Group Leader)

FOS2

FOS3

FOS4

New EG1 FOS1 (Group Leader)

FOS2

New EG2 FOS3 (Group Leader)

FOS4