# Embedded Resilient Device Support - Programming

IMPORTANT: Cluster programming must be completed before creating resilient users and devices. See the Mitel Clustering Design and Implementation Guide for more information. See also the Resiliency Guidelines for information on provisioning resiliency for SIP devices.

## Creating a New Resilient Device

1. Log into the element that will be the home (primary) element for the resilient device. The element that you are logged into when you create the new device is the device's home (primary) element.

2. Do one of the following:

3. To create a resilient IP Phone, go to the User and Services Configuration form

or

2. To create a resilient IP Console, go to the IP Consoles form.

3. Click Add to create a new device and complete the required fields in the form.

4. Select the name of the Secondary Element from the drop-down list of cluster members.

   NOTE: You can select any element in the cluster to be the secondary element However, to support resiliency for the device, the selected element must be sharing data with the local element. Check the Network Elements form to ensure that the selected secondary element is sharing data with the local element.

5. Click Save. System Data Synchronization shares the device data at the Resilient Pair scope between the device's primary and secondary controller.

## Enabling Resiliency for an Existing Device

1. Log into the local element for the device. The local element for the device lists the device's directory number in the User and Services Configuration form or IP Consoles form. After you enable the resiliency for the device, the local element becomes the device's home (primary) element.

2. Do one of the following:

3. To enable resiliency for an IP Phone, access the User and Services Configuration form

or

1. To enable resiliency for an IP Console, access the IP Consoles form.

3. Select the name of the Secondary Element from the drop-down list of cluster members.

   NOTE: You can select any element from the cluster to be the secondary element. However, to support resiliency for the device, the selected element must be sharing data with the local element. Check the Network Elements form to ensure that the selected secondary element is sharing data with the local element.

4. Click Save. System Data Synchronization shares the device data at the Resilient Pair scope between the device's primary and secondary element.

## Changing the Secondary Controller

You cannot change the secondary element of resilient devices from the User and Services Configuration or IP Consoles forms in one operation. Instead, you must first disable resiliency for the device (by setting the "Secondary Element" field to "Not Assigned" and clicking Save). Then, re-enable resiliency for the device and assign a different secondary element.

## Disabling Device Resiliency

To disable resiliency from a device:

1. Go to the User and Services Configuration form ( ) or IP Consoles form ( ) on the home (primary) element for the resilient device.

2. Select the directory number of the resilient device and click Change.

3. In the Secondary Element field, select Not Assigned.

4. Click Save. The entry for the resilient device is deleted from the secondary controller.

## Deleting a Resilient Device

1. Go to the User and Services Configuration form ( ) or IP Consoles form ( ) on the home (primary) element for the resilient device.

2. Select the directory number of the resilient device and click Delete.

3. Click OK. The entry for the resilient device is deleted from the primary and secondary controllers.

Related Topics

- Embedded Resilient Device Support - Description

- Embedded Resilient Device Support - Conditions