Category     

WPC to ECM Migration: Devices

« Go Back

Information

 
Content

WiPipe (WPC) to Enterprise Cloud Manager (ECM) Migration: Devices


Quick Links

Summary

Requirements

Directions

Related Articles


Summary

This document provides details on the process of migrating devices from WiPipe Central (WPC) to Enterprise Cloud Manager (ECM).


Requirements

  • An Administrator or Full-Access WPC account
  • An Administrator or Full-Access ECM account
  • Existing Devices managed in WPC:
    1. Must not have a pending firmware update
    2. Must not be in a configuration rollback status
    3. Must have ECM-compatible firmware installed, (4.4.0 or newer)
    4. Must be migrated to a corresponding ECM group (if in a group)
    5. May be migrated from the UNASSIGNED category

Note: If a device is currently offline (red status icon) it will not receive the reboot instruction from WIPC and WPC will not send the reboot instruction when it reconnects. In this case the device will have to wait for the ECM Unmanaged timer to expire before it attempts to connect to ECM, this timer extends on each failure, but will usually reconnect within one day.

Note: Settings for logs and alerts will not transfer in the migration. Settings data capture and historical information, such as saved reports, will not transfer. Migrated groups will take ECM defaults for any settings not migrated.


Directions

  • Initiate Device Migration from WPC

Note:  Devices can be migrated by using either the devices tab or the group configuration tab.

  • Migrating Devices with Group Configuration

    User-added image

    Note: It is highly recommended to first migrate the group configuration without any devices, review the configuration options in ECM, and then migrate devices into the group.

    1. Overwrite existing ECM group configuration check box

      Checking this option will overwrite the ECM group configuration with the current WIPC group configuration. If a matching ECM does not exist, the group will be created and this option has no effect. If an ECM group does exist, the configurations must match or devices will not migrate; ether select this option or [Migrate Devices From the Device List].

    2. Migrate devices in selected groups check box

      Checking this option will migrate all devices that currently belong to the WPC group into the matching ECM group. If an ECM group does not exist, the group will be created before the devices are migrated.

    Note: In order to detach from WPC and connect to ECM the router must reboot. Depending on the synchronization timer on the router, this reboot may not be immediate and will occur the next time it checks in with WPC.

    Click Migrate to migrate all devices assigned to this group to ECM. A summary of the migration results will be displayed that includes both device and group results

    User-added image

  1. The group name is listed before its devices
  2. Devices are indented under the group name and listed by MAC address and device name
  3. The summary indicates all items migrated, both groups and devices
  • Migrating Devices from the Device List
User-added image
  1. Navigate to the Devices tab
  2. Select the device(s) you wish to migrate
  3. Click on the Migrate button

A Device Migration dialog box will appear

User-added image

A significant difference between the device and group migration dialog is the Copy device configuration to ECM option. Deselecting this box will prevent the WIPC device configuration from being copied to ECM. If a matching ECM group is not found, the device migration will fail.

Note: When migrating devices with the Group Configuration detailed earlier, the device configurations are automatically included.

Note: Unlike migrating with group configurations, the device migrations will not check for matching group configurations before migrating. Devices will sync any differences in the ECM configuration after migration.

Note: In order to detach from WPC and connect to ECM the router must reboot. Depending on the synchronization timer on the router, this reboot may not be immediate and will occur the next time it checks in with WPC.

  • Migrated Devices in WPC
User-added image

In WPC migrated devices have a new Device Migrated status icon and description.

  • Validate Device Migration in ECM

 

After migrating devices from WPC, verify visibility and device configurations in ECM.

User-added image

Note: The migration from WPC immediately registers the device with ECM and creates its activation record. However, the device itself may take some time to first check-in. The device has to perform its final check-in with WPC to receive the migration instructions; the default check-in interval in WPC is once an hour.

After the device reboots, it should check into ECM as soon as it has WAN connectivity.

Note: The WPC device name field will be stored in the ECM description field (below).

  1. Online Status: This column shows a green circle for “Online” devices, a red stop icon for “Offline” devices, and a gray lock icon for “Initialized” devices. Devices are considered “Initialized” if they have been loaded into ECM by Cradlepoint Operations, but the device itself has never checked in to ECM. When initialized devices eventually connect to ECM, they will change to “Online”.
  2. Router Status: This column indicates whether the router is has a pending configuration sync, a pending firmware update, a suspended configuration, or whether the device is requiring a reboot in order to allow feature licenses to be applied.
  3. Name: The name of the device that is displayed in ECM. If the device has not been given a name, this field will show the router’s default name, for example IBR650-2c2.
  4. Description: This column allows an ECM account holder to provide an additional description for the router. For devices migrated from WIPC, the description field will default to the old WPC device name.
User-added image

Review the device configuration carefully, because ECM reads local configuration changes to establish the baseline device configuration. This is a significant change from WPC that was unable to read and display local device configurations.

In ECM there are three levels of configurations. In order of precedence they are: device, group and local. This means in the event of conflicting options, the device configurations (in ECM) are applied above all; group configurations are applied above local configurations; and any conflicting local configurations (on the device) will always be overwritten by the higher priority group or device configuration from ECM.

User-added image


Related Articles/Links


Published Date: 11/6/2015

This article not have what you need?  Not find what you were looking for?  Think this article can be improved?  Please let us know at suggestions@cradlepoint.com
 


 
Knowledge Home | Product