WiPipe (WPC) to Enterprise Cloud Manager (ECM) Migration: Groups
This document provides details on the process of migrating group configurations from WiPipe Central (WPC) to Enterprise Cloud Manager (ECM).
An Administrator or Full-Access WPC account
An Administrator or Full-Access ECM account
Note: Settings for logs and alerts will not transfer in the migration. Settings for data capture and historical information, such as saved reports, will not transfer. Migrated groups will take ECM defaults for any settings not migrated.
Existing group configurations in WPC
Note:It is recommended to first migrate group configurations without any devices. This allows for a review of the new ECM configurations prior to assigning any devices to the group.
At least one WPC group for Series 3 devices (excluding the MBR95 and CTR35)
Initiate Group Migration from WIPC
Note: Prior to migrating groups from WPC, please ensure groups and devices are at firmware 4.4.0 or above as described in [Preparing to Migrate from WPC to ECM]
- Navigate to the Groups tab.
- Select the group you wish to migrate (you can select multiple groups).
- Click on the Migrate button.
A Group Migration dialog appears. This dialog has the following items:
Leaving this option unchecked will only migrate the group configuration to ECM. Checking this option will migrate all devices that currently belong to the WPC group into the matching ECM group. If no ECM group exists, the group will be created first. Note: In order to detach from WPC and connect to ECM the router must reboot. Depending on the syncronization timer on the router, this reboot may not be immediate and will occur the next time it checks in with WPC.
- An Overwrite existing ECM group configuration checkbox.
Checking this option will overwrite the ECM group configuration with the current WPC group configuration. If no ECM group with the same name exists, this option has no effect.
- A Migrate devices in selected groups checkbox.
Validate Group Migration in ECM
Immediately after migrating the group configuration it will be visible in ECM; it is highly recommended to validate the ECM configuration prior to migrating any devices into it.
- Group name migrated from WPC
- No devices in group (unless the Migrate devices in selected groups option was checked)
Note: Settings for logs and alerts have changed from WPC and are no longer a part of the group configuration.
- Select the migrated group
- Click on the Settings link above the group list: the group settings dialog will display
- Reporting - Enable log and usage reporting as desired
- Connection Pulse
The Connection Pulse is how often the “heartbeat” is sent to the ECM server. It is recommended to leave this at its default setting. Adjusting it to higher frequency will increase data usage. Lowering the frequency risks dropping the ECM session. If the session is dropped, the router will be forced to reestablish the SSL connection, which requires significantly more data than the keep-alive.
Click OK to confirm Reporting, and Connection Pulse settings
Note: Alerts are configured under the Alerts tab in ECM and are not saved as part of the group configurations like they were in WPC.
Open the group Edit Configuration window to review the group configuration settings:
- Select the group from the groups list
- Click the Configuration dropdown
- Choose Edit
Review the group settings to ensure the new ECM group is configured as desired.
Note: ECM no longer has the Group tab in group configuration pages. All of the necessary functions still exist in the following locations:
- Alert Config - in the group Settings dialog
- Commands - in the group Commands dropdown
- Device List - filter the Devices (3a) tab using the Show Accounts (3b) show accounts feature
- Rename Group - Click the pencil icon next to the Name field in the Groups list (only shows when the group is highlighted)
- Firmware - use the Firmware dropdown
- Sync Config - Adjusting the status reporting, log reporting, and heartbeat notification interval are in the group settings dialog (item 1). Firmware updates are now pushed to the device (item 2), instead of the device checking with the server for updates at set intervals.
- Alternative: Create Groups in ECM First
Instead of migrating group configurations from WPC, you can create and configure groups in ECM first. In order to use this method, the group must:
- Have the same group name
- Be assigned the same device model
- Be assigned the same firmware version
- Belong to the same account not a sub-account
Note: When creating ECM groups first , it is recommended to migrate devices from the WPC device list. If the ECM group configurations do not match the WPC group configurations, WPC will require a group configuration overwrite in order to migrate devices. Migrating from the device list does not require the group configurations to match.
Next Step: WIPC to ECM Migration: Devices
Getting Started with Enterprise Cloud Manager
Enterprise Cloud Manager FAQ
Preparing to Migrate from WiPipe Central (WPC) to Enterprise Cloud Manager (ECM)
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 email@example.com.