Configure a Device Cluster with an Offline Configuration

You add a device cluster, which can contain a single device group or multiple device groups and associate it with a single offline configuration that you added. All targeted devices in the device cluster must share the same software version, and platform.

Add a Device Cluster Network Function

Pre-requisite: If you are not using the default Home group to add a device cluster NF, you must specify a device group. See the Configure Device Groups section in the Device Manager chapter for more information.

  1. Expand the Device Manager slider and click Devices.
  2. In the Managed Devices - Group View pane, click Add.
  3. In the Select Network Function Type dialog box select the plug-in product vendor type from the Categories table.

    Note:

    Other EM plugin product vendor types may also display in this table if they are installed in Oracle Communications Session Delivery Manager.
  4. In the Network Function Type drop-down list, select the Device Cluster NF type and click Continue.
  5. In the Add Network Function: Device Cluster dialog box, complete the following fields:
  6. Click Apply.
    The NF now appears in the Managed Devices pane.

Associate the device cluster with its offline configuration.

Associate a Device Cluster with an Offline Configuration

Once you have added a device cluster to an NF, the device cluster must be associated with an offline configuration.

Pre-requisites: You must add an offline configuration before you associate the device cluster with an offline configuration. See the Add an Offline Configuration section for more information.

  1. Expand the Device Manager slider and click Devices.
  2. In the Managed Devices pane, select the device cluster that you want to associate with an offline configuration and click Edit.
  3. In the Associate Offline Configuration to NF Device Cluster dialog box, view and complete the following fields:
  4. Click Apply.

Add a Device to a Device Cluster

Now that you have associated a device cluster to its offline configuration you can add devices to the device cluster.

Pre-requisites: A device is eligible to be added to a device cluster if it meets the following criteria:
  • The device must contain a platform and software version that matches the Offline Configuration.
  • The device must be accessible through SSH over the network.
  • The device has all required entitlements enabled, and licenses installed, as needed, to provide any services enabled by the Offline Configuration.

Note:

Ensure that any device that is added to the cluster is not currently being managed by OCSEM. If a device is being managed by OCSEM, remove it from OCSEM so that you can add it to the device cluster.
  1. Expand the Device Manager slider and click Devices.
  2. In the Managed Devices - Group View pane, select to expand the device cluster to which you are adding a device.
  3. Select the device cluster and click Add.
  4. In the Add Device to scalability group dialog box, complete the following fields:
  5. Click Check Device to verify that the device has the same software version that the offline configuration uses.
  6. Click Next to configure the necessary data variables offered by the offline configuration.
  7. In the next dialog box, enter the device-specific parameters for each data variable that you are provided (through the offline configuration).

    Note:

    See the Create Data Variables to Support Device Specific Values section for more information about how data variables are created in an offline configuration.
  8. The device must already be active and on the network for the activation process to start (it has already booted). Click Finish to start the activation process.
    In the Managed Devices table, enable the hidden Activation Status column to see the device status. If the device activates successfully, the Activated status displays. If the device failed to activate, the Activation Failed status displays.

    For example, one scenario for a device that fails to activate could be if it was re-booted and failed to re-boot during the activation process.