Dell EMC Solutions Enabler 9.2 SRDF Family CLI User Guide

When an SRDF/Metro pair is RW on the SRDF link and has reached the ActiveActive or ActiveBias pair state, both sides of the SRDF device pair share the ID that the R1 device advertised at the time the devices were made RW on the link. This device ID is "owned" by the winner side of the device pair, originally the R1 side.

A set bias R2 or suspend -keep r2 operation transfers ownership of the device pair's ID to the R2 side, which now becomes the R1 side as a result of acquiring the bias. (See Setting SRDF/Metro preference and Setting bias when suspending the group for more on setting bias.)

After a deletepair operation, the device side that last owned the ID (the winner side, referred to as the R1 in displays and exported data) uses that ID. The other device side (loser side) uses the original R2's device ID.

Once a device has been removed from an SRDF/Metro configuration using deletepair or half_deletepair, its original ID can be restored, if necessary.

The following rules and restrictions apply to restoring the native personality of a device which has a federated personality as a result of a previous SRDF/Metro configuration:

• Devices must be unmapped and unmasked.
• Devices should not be SRDF devices.
• Devices must have a federated WWN.
• Devices cannot be Data Domain devices.

The following SYMCLI commands have the set -no_identity option that restores the personality of devices removed from SRDF/Metro configurations:

• Devices: symdev set -no_identity
• Device groups: symdg set -no_identity
• Composite groups: symcg set -no_identity
• Storage groups: symsg set -no_identity

The steps to restore device personality vary depending on whether the bias was changed before the devices are deleted from the SRDF/Metro group configuration.

Identities of both sides should be restored. Not doing so could expose the two different devices to a host using the same ID. Use the symdev show command to display which IDs need to be reset.