# Embedded Resilient Device Support - Conditions

The following conditions apply:

- MCD Release 4.0 or later software is required on all the elements in the cluster.

- Resiliency is only supported for IP devices. Refer to the Resiliency Guidelines for a list of the IP devices that support resiliency.

- You can only configure resiliency for a device from the device's local (home) element. You cannot configure or disable device resiliency from the device's secondary element. However, after you have created a resilient device, you can modify its parameters, with the exception of certain key types (see below), from the secondary element. The modifications are distributed to the home element via SDS.

- For a resilient device, you cannot configure the following key types on the device from the Multiline Set Keys form at the secondary element:

- single-line

- multicall, or

- key system

You must program these keys in the Multiline Set Keys form of device's primary element.

- Resiliency must be configured before you assign multicall keys to a device. If multicall keys have already been assigned, clear them, configure resiliency, and then reassign the keys.

- Although you can modify the parameters of a resilient device in the Multiline IP Sets, Single-line IP Sets, and Wireless IP Sets form, you cannot delete resilient devices from these forms.

- You configure resilient phones from the User and Services Configuration form and configure resilient IP consoles from the IP Consoles form.

- You can use the Import and Export buttons in the User and Services Configuration and IP Consoles forms to import and export resilient device data.

- You can configure or disable resiliency for the 5560 IPT.

- Line appearances of non-prime directory numbers on a resilient device, are hosted by the same primary and secondary controllers as the prime directory number. You cannot assign the line appearance of a non-prime directory number to have a different secondary controller than that of the prime directory number.

- IP Console softkeys must be unique to the same primary controller and secondary controller combination within the cluster. For example, if you create softkey 1001 on IP console 1000 at primary controller A with secondary controller B, the same RDN entry is created on each node in the cluster: 1001 A, B. Then, if you

- attempt to create key 1001 on IP console 2000 on primary controller C with secondary controller D, this request will be rejected because the primary and secondary controllers are different (C, D).

- attempt to create key 1001 on IP Console 3000 on primary controller A with secondary controller C, this request will be rejected. Again the primary and secondary controller combinations are different (A, C).

- attempt to create key 1001 on IP Console 5000 B A, the request will be rejected. The controller combination is (B, A).

- program key 1001 on IP console 4000 A B, this action is allowed because the primary and secondary combination is the same (A, B).

- When you delete softkeys using the Console Softkeys form, the software ensures that only the last instance of the key for the RDN entry is deleted.

Related Topics

- Embedded Resilient Device Support - Description

- Embedded Resilient Device Support - Programming