FAQs

CradlePoint Services (24)

View category →

Table of Contents

Purpose

This article will explain in detail the process of migrating group configurations from WiPipe Central (WPC) to Enterprise Cloud Manager (ECM).

Requirements

  1. An Administrator or Full-Access WPC account
  2. Existing group configurations in WPCNote: It is recommended to migrate group configurations first without any devices. This process allows for a review of the new ECM configurations prior to assigning any devices to the group.
  3. An Administrator or Full-Access ECM accountNote: 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.
  4. At least one WPC group for Series 3 devices (excluding the MBR95 and CTR35)

Directions

Initiate Group Migration from WPC

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

First, log into WPC.

Select Group

  1. Navigate to the Groups tab.
  2. Select the group you wish to migrate, you can select multiple groups.
  3. Click on the Migrate button.

Group Migration dialog appears. This dialog has the following items:

Input ECM Credentials

  1. An Overwrite existing ECM group configuration checkboxChecking 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.
  2. Migrate devices in selected groups checkboxLeaving 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 synchronization timer on the router, this reboot may not be immediate and will occur the next time it checks in with WPC.

WPC Group Migrated

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.

ECM Group Migrated

  1. Group name migrated from WPC
  2. No devices in the group (unless the Migrate devices in selected groups option was checked)Note: Settings for logs and alerts have changed from WPC and were no longer a part of the group configuration.
  3. Select the migrated group
  4. Click on the Settings link above the group list: the group settings dialog will display.

ECM Group Logging Review

  1. Reporting – Enable log and usage reporting as desired
  2. Connection PulseThe 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 a 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:

ECM Group Settings Review

  1. Select the group from the groups list
  2. Click the Configuration dropdown
  3. Choose Edit

Review the group settings to ensure the new ECM group is configured as desired.

ECM Group Settings Review

Note: ECM no longer has the Group tab in group configuration pages. All of the necessary functions still exist in the following locations:

ECM Group Tab Features

  1. Alert Config – in the group Settings dialog
  2. Commands – in the group Commands dropdown
  3. Device List – filter the Devices (3a) tab using the Show Accounts (3b) show accounts feature
  4. Rename Group – Click the pencil icon next to the Name field in the Groups list (only shows when the group is highlighted)
  5. Firmware – use the Firmware dropdown
  6. Sync Config – Adjusting the status reportinglog 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:

  1. Have the same group name
  2. Be assigned the same device model
  3. Be assigned the same firmware version
  4. 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.

Migrating Devices

After the group configuration is migrated, and the new settings are reviewed, the next step is to migrate devices.

Next Step: WPC to ECM Migration: Devices

Permalink

0 Comments - Leave a Comment

It is possible to manage a CradlePoint router through Enterprise Cloud Manager (ECM) with no active WAN connection, such as when it is used a failover device or configured in WiFi Bridge mode on an existing network. With the default settings, the router requires an active WAN connection to connect to ECM or obtain the current date/time from an NTP Server. To instead use the LAN to connect to ECM, you must set the CradlePoint to use the LAN Gateway feature.

  1. Log into the device’s administration pages.
  2. Go to System Settings > Administration.
  3. Select the Router Services tab.
  4. Select Use LAN Gateway and input the LAN Gateway Address. (This is the LAN IP address of the router that the CradlePoint is connected to.)                                                                                                                  Enabling a LAN gateway for Router Services
  5. The DNS server fields might not need to be changed: these match the static DNS values (set at Network Settings > DNS). You can leave the default values or set them manually here.

Once Router Services has been configured to use a LAN gateway, the device can now be managed by ECM via the LAN. However, because the device still does not have an active WAN connection, ECM will report the IP Address for the WAN source of the network the CradlePoint is connected through.



Notes

  • Setting up a LAN gateway for router services can be used to save money when a CradlePoint router is configured for 3G/4G failover behind another router. If your 3G/4G data plan is small/expensive, you can set router services to use the LAN connection (following the above steps) so that ECM doesn’t use 3G/4G data unnecessarily.
  • In addition to ECM, other “router services” also require a WAN connection by default but can be configured to use the LAN instead. For example, the above steps will enable a connection to an NTP (Network Time Protocol) server via the LAN.

Permalink

0 Comments - Leave a Comment

Welcome to CradlePoint Enterprise Cloud Manager

Enterprise Cloud Manager is the next generation management and application platform from CradlePoint. Enterprise Cloud Manager (ECM) integrates cloud management with your CradlePoint devices to improve productivity, increase reliability, reduce costs, and enhance the intelligence of your network and business operations.

Getting Started

Connecting Devices to Enterprise Cloud Manager:
Using Enterprise Cloud Manager:

Connecting Devices to Enterprise Cloud Manager

Upgrading Firmware

NOTE: Currently only Series 3 devices can connect to ECM (see: How to identify the Series of your CradlePoint router).
Connecting devices to CradlePoint Enterprise Cloud Manager requires at least firmware version 4.3.2 – you may need to upgrade firmware. You can upgrade firmware through the individual device’s administration pages or through WiPipe Central.

Upgrading Firmware through the Device Administration Pages

  1. Log into the device administration pages. Open a browser window and type “cp/” or “192.168.0.1” (these are the defaults – you may have changed them) in the address bar. Press ENTER/RETURN.
  2. When prompted for your password, type the eight character DEFAULT PASSWORD found on the product label – this is also the last eight characters of the MAC address. You may have personalized this password.
  3. Once you are logged in, navigate to System Settings → System Software. Under Firmware Upgrade, select the Automatic (Internet)option to upgrade to the newest firmware version. It is recommended that you save your settings using System Config Save/Restore.

Upgrading Firmware through WiPipe Central

  1. Log into WiPipe Central.
  2. Select the group that you want updated firmware for.
  3. Click on Group and select Firmware from the dropdown menu.
User-added image
  1. Select at least firmware version 4.3.2.

Registering Devices

Log into the device administration pages and go to Getting Started → Enterprise Cloud Manager Registration. Enter your ECM username and password, and click on “Register”.
User-added image
Your device is now registered in ECM.

Migrating Devices from WiPipe Central

The following articles detail the steps for safely migrating devices from WiPipe Central to Enterprise Cloud Manager:


Using Enterprise Cloud Manager

Navigating the User Interface

Once you have upgraded firmware to at least 4.3.2 and registered your devices, go to https://cradlepointecm.com and log in using your ECM credentials.
ECM login
Once you are logged in, the left navigation menu shows the following tabs:
  • Dashboard – Provides powerful insight into your network through WAN analytics including connectivity, data usage, and performance.
  • Devices – Monitor all the devices loaded into ECM. View statuses, change configurations, and update firmware by device.
  • Groups – Monitor devices by group. Add new groups and view statuses, change configurations, and update firmware by group.
  • Accounts & Users – Add new users and subaccounts and edit the existing ones.
  • Alerts – View a list of alerts generated by your devices and edit settings for alerts, including emailed alerts.
  • Reports – Select the date range, type of report, group(s), and identifier fields and export CSV reports.
  • Applications – Trial, buy, and manage cloud-based applications (e.g., CP Secure Threat Management). This tab is only available for top-level account administrators.

For contextual help, open the Help Panel by clicking on the question mark symbol in the top right corner.

ECM Help Panel
You have the ability to collapse or resize the Help Panel. Also, use your operating system/browser “Find” function to search the help text (e.g. click Ctrl+F or ⌘+F).The DevicesGroups, and Alerts → Log pages all display as grids. The grids are customizable. Reorder columns by dragging and dropping the column headers. Resize columns by dragging the edge of the column headers. Click on the column headers to sort rows by ascending/descending order.
To remove or add columns, click on the “Column Selection” icon in the top right corner of the grid. Select/deselect columns from the popup list that appears.
ECM column selection
To filter the display to show a subset of the grid items, you have two main options:
  1. Some of the fields in the grid are hyperlinks for filtering the grid (e.g. “Product”). From within the grid, click on a hyperlinked field and the grid will be filtered to display only the devices of that type. For example, click on “MBR1400v2” to display only MBR1400v2 devices.
  2. Input a string of characters into the search box (top right) to filter by devices that have that string in one of their fields. You can use partial strings, and the field does not have to start with the partial string. For example, “600” will display devices that have “IBR600” in the Product field. This searches most (but not all) of the fields.
ECM search box

Creating a New User

NOTE: Creating a new user is only available to account administrators.

  1. Click on Accounts & Users in the left menu.
  2. Select the desired account from the table.
  3. Click on Add in the top toolbar. Select “User” from the dropdown menu.
Add User
  1. Enter the information in the “Add User” dialog box. Note that the “Role” will determine the permissions the user will have in the account and all included subaccounts. Choose from the following roles:
    • Administrator: Administrators have full access to the account they are in, along with all subaccounts within that account.
    • Full Access User: Same access as administrators except cannot create/edit other users.
    • Read Only User: Cannot make any configuration changes or change settings; can only view information within Enterprise Cloud Manager (ECM) and run reports.
Add User Dialog Box
  1. Click on “OK” to save the new user.

Creating a Subaccount

NOTE: Creating a new subaccount is only available to account administrators.

  1. Click on Accounts & Users in the left menu.
  2. Select the desired account from the table.
  3. Click on Add in the top toolbar. Select “Subaccount” from the dropdown menu.
Add Subaccount
  1. Enter the name of the subaccount and click “OK”.
Add Subaccount Dialog Box

Managing Devices

Once you have added a device to ECM, you will see it listed in the Devices page. Manage individual devices within this page: view a device’s status, make configuration changes, move devices into a group, etc. The Devices page has three main views: RoutersNetwork Interfaces, and Rogue AP. In the views menu at the top, next to Devices, select one of these options (default view is Routers).
  • Routers displays all the routers.
  • Network Interfaces displays every network interface, including both LAN and WAN (e.g. modems, Ethernet connections, WiFi).
  • Rogue AP shows a list of wireless access points that your devices have seen; use this list to search for Rogue APs that could threaten your networks.

From within the Routers view, click on a device name to view in-depth WAN analytics for that device. This reveals the device dashboard, with charts for data usage, signal strength, and more.

Device dashboard
The most common way of managing devices is in groups. By putting devices in groups you can change the configuration and upgrade firmware by making a change to the group that is applied to all of the devices in that group.To create a group, select Groups in the left menu and click “Add” in the top toolbar.
Add Groups
Enter the Group Name you want to use, select the Product type you will be adding to that group (e.g., MBR1400v2, IBR600), and select theFirmware you want the devices in that group to have. You can also change the Subaccount (if desired). Click on “OK.NOTE: All the devices in a group must have the same type and same firmware.
Add Group Dialog Box
The new group is now listed on the Groups page.Now that the group is created, you can move devices into the group by first selecting them in the Devices page and then clicking “Move” on the top toolbar.
Move Device to Group
A popup window appears. Select a group (only groups with the appropriate device type are displayed) and click OK.
Select a Group
NOTE: The router will IMMEDIATELY be upgraded or downgraded to the version of firmware defined for the group. This could cause a router reboot if the firmware version of the router does not match the firmware version configured for the group.

Upgrading Firmware

Router firmware can be upgraded by group. Select a group from within the Groups page and click on Firmware in the top toolbar. In the dropdown menu, select the firmware version number.
Upgrading Firmware
You will be prompted to accept the firmware version change.
Confirm Firmware Upgrade
Click on “Yes” and the firmware upgrade will be applied IMMEDIATELY to all of the routers in the group.NOTE: The routers in the group will IMMEDIATELY be upgraded (or downgraded) to the version of firmware defined for the group. This will cause a router reboot if the firmware version of the router does not match the firmware version configured for the group.

Configuring Devices

You can apply a configuration change to a group or a specific device within a group (e.g. change failover priority, enable GPS, add a guest WiFi network, etc.). Configuration settings created for a group apply to all the devices within the group. Configuration settings created for a device apply only to that device and override configuration settings defined for the group it is in.1To change the configuration of a group select Group in the Application panel, select the group you want to configure, click “Configuration” in the top toolbar, and select “Edit” in the dropdown menu.
Configuring Devices
The Edit Configuration window shows, allowing you to make configuration changes.
Configuration Window
When making changes in the Edit Configuration window you must select “Apply” on each configuration page before leaving the page in order to save the changes made. Once you have completed all changes, select from the following buttons on the bottom of the window:
  • View Pending Changes – view all of the changes you made on all of the configuration pages
  • Commit  Changes – apply all of the changes made on all of the configuration pages to the group or device(s)
  • Discard Changes – close the configuration window without applying any of the changes made on the configuration pages

To configure an individual device, select Device in the left menu and select the device in the list. Click on “Configuration in the top toolbar” and then select “Edit” from the dropdown menu. The same rules and guidelines apply to device configuration that apply to the group configuration described above.

Setting Up Alerts

The Alerts page has two views for tracking device status changes:
  • The Log view shows a list of alerts sent from the routers to ECM.
  • The Settings view shows rules for alerts, including email notifications.

Toggle between these two views by clicking on the buttons at the top left.

Alerts

Alerts are of the following types:

  • Configuration Change
  • Configuration Rejected
  • Data Cap Threshold
  • ECM Connection State
  • Failed Login Attempt
  • Firmware Upgrade
  • Modem State
  • Reboot
  • Unrecognized Client
  • WAN Service Type
  • WAN Status Change
To enable alerts, including emailed notifications, first select the Settings view and then click on Add at the top left. Create an alert notification rule by completing the fields.
Alert notification rule
Complete the following fields to create an alert notification rule:
  • Accounts/Groups (required) – Choose which sets of devices will follow the notification rule. If you select an account, both grouped and ungrouped devices within that account (including all subaccounts) will be assigned to this rule.
  • Alerts (required) – Select the alert types from the dropdown options.
  • Users (optional) – If you want emailed notifications for these alerts, select users from the list to receive those emails. If you just want these alerts logged, leave this field blank.
  • Interval (optional – Select a time interval from the dropdown options. If you select “Immediately,”  an email notification is sent every time one of the selected types of alerts are logged. Otherwise, the alerts are stored over the course of the time interval and then sent together.

Exporting Reports

Reports allow you to create a summary of information about groups of devices and export that information as a CSV file. Select from several fields to customize your reports. Select the type of report (Data Usage or Signal Quality), a range of dates, the group(s), and identifying fields and then click Run Report to view the report. You also have the option to save the settings of a report for future use.

Reports

Exporting Logs

To export a device’s logs as a CSV file, first enable log reporting for the group the device is in. (This is disabled by default because some users won’t use this functionality – it would unnecessarily use data.) Navigate to the Groups page, select the desired group, and click on Settings.
Enable log reporting
In the popup window that appears, ensure that “Enable Log Reporting” is selected.
Enable Log Reporting
Once log reporting is enabled, navigate to the Devices page, select the desired device, and click on Export → Export Logs to export the device’s logs as a CSV file.
Export logs

 


1  Both group and device settings apply to the device unless they are mutually exclusive, in which case the device settings win. If a configuration update causes an error, the configuration will roll back to the previous configuration, and the device is “suspended:” it will still operate, but new configuration settings are not accepted until the suspension is removed.

Permalink

0 Comments - Leave a Comment

Multi-Carrier Software-Defined Radio Switching

Products Supported: Any Cradlepoint router or modem with a LPE designation.

Firmware Version: 5.3.0 or newer – for information on upgrading firmware

Summary

With firmware 5.3.0 all LPE devices can switch the modem firmware to a different carrier. This Multi-Carrier Software-Defined Radio functionality is unique to Cradlepoint products and provides customers the flexibility to expand their coverage options, reduce inventory risk, and future-proof their carrier networks.

Please note that this only changes the modem firmware. To connect with this modem, you must also have an activated SIM from the new carrier in the device. Some LPE devices allow you to insert two SIM cards, so you can include SIMs from two different carriers in a single modem and remotely switch the modem firmware with ECM.

Although a single Cradlepoint modem may have two SIM card slots (e.g., IBR1100 integrated modem), it can only have one modem firmware version on that modem, and therefore only one carrier at a time. The exception is that the AER 2100 could have two distinct, integrated MC400 modems, each with two SIM slots. So while each modem by itself can only have one firmware version, the AER 2100 can support two integrated modems – on distinct carriers- simultaneously.

Select from the following methods for instructions on switching the carrier of the modem firmware.
1. USB flash drive
2. Local administration pages
3. ECM Carrier Switching


Configuration

Configuration Difficulty: Intermediate

Manual Carrier Switching

Preparation:

To update the Modem Carrier (switching the modem between Verizon, AT&T, Sprint or Generic (T-Mobile in USA and Rogers, Bell, Telus in Canada), the following conditions must be met:

  • Compatible product with a Cradlepoint “LPE” modem. (designated in the router or modem Part Number)
  • Router Firmware version of v5.3.0 or newer.
  • USB flash drive (at least 256MB capacity) or a computer locally connected to the router.
  • An activated SIM card for carrier being changed to and provisioned for the IMEI of the modem being changed. (This is especially important for Sprint)
Manual Carrier switching using USB drive:

Note: This process will force all attached LPE modems to the updated modem firmware. In the case of an AER 2100 with two MC400 integrated modems, you may not want both modems to have the same firmware. Either use one of the other methods to update modem firmware or remove one of the MC400s during this process.

  1. Download the appropriate Modem Carrier firmware from the CradlePoint connect portal. This will be a ZIP file labeled specifically for each carrier or Generic:
    • “MC7354_Sprint.zip” for Sprint in North America.
    • “MC7354_Verizon.zip” for Verizon in North America.
    • “MC7354_AT&T.zip” for AT&T in North America.
    • “MC7354_Generic.zip” for T-Mobile, Rogers, Bell and Telus in North America.
  2. Save the file to your computer.
  3. Unzip the file contents to extract the files to your computer.
  4. Locate the extracted files. There will be an “MDM” file and a “JSON” file.
  5. Copy the “MDM” and “JSON” files from the extracted location to the root of your USB stick. The files must be in the root of the flash drive.
  6. Safely eject the USB flash drive from your computer.
  7. Locate the SIM slot, door, or panel on the Cradlepoint router or modem, and insert the new SIM (this must be performed while the power is OFF).
  8. Power on the Cradlepoint router (and connect the modem if it is not embedded in the router).
  9. Wait for the router to start-up completely. This can be verified by navigating to the router’s admin page (192.168.0.1 by default).
  10. Plug the USB flash drive into any of the router’s spare USB ports.
  11. The MODEM firmware update process begins automatically
    • PLEASE WAIT. Do NOT remove the USB flash drive at this time. The router will reboot immediately if the USB flash drive is removed. The process takes up to 10 minutes.
  12. PRIOR TO REMOVING THE USB DRIVE, verify the modem is attempting to connect with the new carrier and SIM: In a browser, log into the router’s administration page, 192.168.0.1 by default. Enter the password when prompted.
  13. Browse to Internet > Connection Manager and watch for the Internal LPE connection status to progress from “Connecting” to “Connected”.
  14. If you receive an error:
    • Consider that you may have to manually update the APN if your SIM is provisioned for one other than the carrier’s default APN. Instructions on how to do this can be found here.
    • You may also need to make sure you are trying to use the same interface and SIM slot. Some products contain two SIM slots, and, therefore, there are two “Internal LPE” interfaces displayed in Connection Manager. If your active SIM is in slot 1, the “Internal LPE (SIM1)” will be the one to connect with that SIM; SIM slot 2 will correspond to “Internal LPE (SIM2)”.
    • Other troubleshooting steps may be found on Cradlepoint’s Support site or by contacting Cradlepoint Support.
  15. Regardless of the status at this time, the USB flash drive can be removed.
  16. The router will reboot itself, and attempt to connect using the new carrier/SIM.

Manual Carrier switching using a PC:
  1. Download the appropriate Modem Carrier firmware from the CradlePoint Connect Portal. This will be a ZIP file labeled specifically for each carrier or Generic:
    • “MC7354_Sprint.zip” for Sprint in North America.
    • “MC7354_Verizon.zip” for Verizon in North America.
    • “MC7354_AT&T.zip” for AT&T in North America.
    • “MC7354_Generic.zip” for T-Mobile, Rogers, Bell and Telus in North America.
  2. Save the file to your computer.
  3. Unzip the file contents to extract the files to your computer.
  4. Login to the router admin page and navigate to Internet > Connection Manager.
  5. In the WAN Interfaces table, select the desired LPE modem. *Note that for modems with two SIM slots, changing the firmware affects both SIM cards.
  6. Click Control.                                                                                                                                                                                                                                                                                                  User-added image
  7. Click Firmware.                                                                                                                                                                                                                                                                                                 User-added image
  8. Then click Manual Firmware Upgrade.                                                                                                                                                                                                                                                               User-added image
  9. Locate the files extracted in step 3 and select the .MDM file.
  10. The router UI will provide the progress status for every step and will eventually reboot. This process will take several minutes.
  11. After the router reboots it will, then attempt to connect to the new carrier.
  12. The new carrier SIM can be inserted either before or after doing the above steps. Remember that inserting a SIM on a COR model requires the router to be powered off.
  13. If you receive an error:
    • Consider that you may have to manually update the APN if your SIM is provisioned for one other than the carrier’s default APN. Instructions on how to do this can be found here.
    • You may also need to make sure you are trying to use the same interface and SIM slot. Some products contain two SIM slots, and, therefore, there are two “Internal LPE” interfaces displayed in Connection Manager. If your active SIM is in slot 1, the “Internal LPE (SIM1)” will be the one to connect with that SIM; SIM slot 2 will correspond to “Internal LPE (SIM2)”.
    • Other troubleshooting steps may be found on Cradlepoint’s Support site or by contacting Cradlepoint Support.

ECM Carrier Switching

Preparation:
  • Compatible product with a Cradlepoint “LPE” modem (designated in the router or modem Part Number)
  • Router Firmware version of v5.3.0 or newer
  • An activated SIM card for carrier being changed to, and provisioned for the IMEI of the modem being changed (This is especially important for Sprint)
ECM Carrier switching steps:
  1. Log into Enterprise Cloud Manager.
  2. Select the devices tab and then Network Interfaces from the drop down menu at the top.                                                                                                                                                                                        User-added image
  3. At the far right side of the page click the User-added image icon and make sure Modem FW, Modem FW Status, SIM, and Model fields are selected then close the column select window. The Modem FW column will show you which carrier the modem is configured for and the SIM column displays the carrier of the SIM card.
  4. Next we need to locate the modem we want to switch to another carrier. The easiest way to do this is by sorting the Router Name or Router ID column, or to search by a specific router name using the search tool.
  5. In the example shown below, the grid is filtered using the search tool (searched by a specific router name, IBR1100LPE) and the filter tool (selected Modems) in the top toolbar so that only the two relevant interfaces display.                                                                                                                                                                                                                                                                                                              User-added image
  6. To switch the carrier of the modem firmware, first select the desired interface. *Note that integrated modems with two SIM slots show two interfaces in the grid. Both will always have the same modem firmware, so selecting either one will have the same results.
  7. Once you have selected an interface, click Commands in the top toolbar and Switch Carrier in the drop down menu.                                                                                                                                                User-added image
  8. Please review the agreement notes before proceeding. This process could knock your device offline.
  9. Once you click the I Agree button, you can now select the desired carrier. *Note that the Generic modem firmware is equivalent, regardless of whether you select T-Mobile, Bell, Rogers, or Telus.                               User-added image

 

  1. After the selection, ECM checks one more time to make sure you want to change the firmware because of the risk of disconnecting the modem. Click OK to continue.
  2. The modem firmware switch takes a few minutes. The Modem FW Status column shows the state of the update, e.g., “Downloading (38%),” and the Modem FW column shows the update that is in the process:        User-added image
  3. Once complete, the Modem FW Status column says, “Upgrade Successful” and the Modem FW column is updated with the new firmware version:                                                                                                    User-added image
  4. If the update fails for some reason, reboot the router before trying again.

Troubleshooting

  • You may have to manually update the APN if your SIM is provisioned for one other than the carrier’s default APN. Instructions on how to do this can be found here.
  • You may also need to make sure you are trying to use the same interface and SIM slot. Some products contain two SIM slots, and, therefore, there are two “Internal LPE” interfaces displayed in Connection Manager. If your active SIM is in slot 1, the “Internal LPE (SIM1)” will be the one to connect with that SIM; SIM slot 2 will correspond to “Internal LPE (SIM2)”.
  • A factory reset will not affect the software defined radio.

 

Permalink

0 Comments - Leave a Comment

CradlePoint Enterprise Cloud Manager (ECM) is a cloud-based management service for configuring, monitoring, and organizing your CradlePoint routers. Key features include the following:

  • Group based configuration management
  • Health monitoring of router connectivity and data usage
  • Remote management and control of routers
  • Historical record keeping of device logs and status

Visit http://cradlepoint.com/ecm to learn more about CradlePoint ECM. If you do not have ECM credentials, sign up at: http://cradlepoint.com/ecm-signup.

image

Registering Your Router – Once you have signed up for ECM, click on the Register Router button to begin managing the router through ECM. Input your ECM Username and ECM Password and click Register. You have now registered the device with Enterprise Cloud Manager.

Suspending the ECM Client – Click on the Suspend Client button to stop communication between the device and ECM. Suspending the client will make it stop any current activity and go dormant. It will not attempt to contact the server while suspended. This is a temporary setting that will not survive a router reboot; to disable the client altogether use the Advanced Enterprise Cloud Manager Settings panel (below).

Enterprise Cloud Manager Settings (Advanced)

image

  • Enabled: Enable the ECM client to contact the server. While this box is unchecked, the ECM client will never attempt to contact the server. (Default: Enabled)
  • Server Host:Port: The DNS hostname and port number for your ECM server. (Default: stream.cradlepoint.com)
  • Session Retry Timer: How long to wait, in seconds, before starting a new ECM session following a connection drop or connectivity failure. Note that this value is a starting point for an internal backoff timer that prevents superfluous retries during connectivity loss.
  • Unmanaged Checkin Timer: How often, in seconds, the router checks with ECM to see if the router is remotely activated. Note that this value is a starting point for an internal backoff timer that reduces network usage over time.
  • Maximum Alerts Buffer: The maximum number of alerts to buffer when offline.

Permalink

0 Comments - Leave a Comment

General M2M Question (24)

View category →

The SIM slot is located on the front left (as you are looking at the side with the lights and the reset button) behind the plastic cover. To access the SIM slot on the device you must remove the plastic cover with a 2mm or 5/64″ hexagon Allen wrench. Install the SIM card with the gold contacts facing down and the cut-out facing to the right. The GX400/440 also includes a SIM lock-down feature to prevent the SIM from moving during extreme vibration. The cover has a tab to mechanically secure the SIM in place during extreme vibration. When replacing the cover, first place the front into the lip and push back to make sure the four holes are aligned before screwing the bolts back in place.

 

Learn More about the Sierra Wireless Gx440

 

Permalink


The LTE networks that supports the GX440 are the Verizon Wireless Network and the AT&T LTE Network in the US.

 

Learn More about the Sierra Wireless Gx440

 

Permalink


The GX400 for EVDO networks does NOT require a SIM card and activation can be done with the appropriate network operator representative and the ESN of the device located on the bottom.

The GX400 for HSPA+ DOES require a SIM card, which can be procured from the appropriate network operator representative.

  • Sim cards used for other AirLink HSPA devices CAN be used in the GX400.

The GX440 DOES require a SIM card. This is notable, since this is the first time that an AirLink device on the VZW network requires a SIM card. SIMs can be procured from your VZW representative during the course of account activation.

Permalink

0 Comments - Leave a Comment

The Sierra Wireless AirLink® products that support ALEOS Application Framework or AAF are the Sierra Wireless AirLink® GX440, the Sierra Wireless AirLink® GX400 and the Sierra Wireless AirLink® LS-300. USAT carries these products designed for the Verizon, AT&T, and Sprint carrier networks as well as through USAT’s Express M2M network services (ExpressM2M.com).

USAT has ALEOS Application Framework engineering teams on staff. Bring us your project for AAF, and we will bring intelligence to the edge for you.

You can view our Sierra Wireless AirLink GX440 and GX400 and LS300 products in the USAT web store.

Permalink


A custom AAF application can be used to collect and measure data and send custom alerts to many different destinations. This can allow you to push something that may have been server side processing down to the modem. Alternatively, you may have previously needed another computer connected in your solution to do this type of monitoring and response. Now with a custom AAF solution from USAT, you no longer need the expense of purchasing and maintaining the additional hardware. Also with fewer points of potential failure, the reliability of the solution increases.

Permalink

0 Comments - Leave a Comment

Cradlepoint Products (7)

View category →

IPv6 Settings

This is the product manual section for IPv6 Settings for the WAN. To edit these settings, go to Internet → Connection Manager. Select a WAN Interface and click on Edit to open up the WAN Configuration editor. IPv6 Settings is one of the tabs:

IPv6 configuration window


The IPv6 configuration allows you to enable and configure IPv6 for a WAN device. These settings should be configured in combination with the IPv6 LAN settings (go to Network Settings → WiFi / Local Networks, select the LAN under Local IP Networks, and click Edit) to achieve the desired result.

This is a dual-stacked implementation of IPv6, so IPv6 and IPv4 are used alongside each other. If you enable IPv6, the router will not allow connections via IPv4. When IPv6 is enabled, some router features are no longer supported. These are:

  • RADIUS/TACACS+ accounting for wireless clients and admin/CLI login
  • IP Passthrough (not needed with IPv6)
  • NAT (not needed with IPv6)
  • Bounce pages
  • UPnP
  • Network Mobility
  • DHCP Relay
  • VRRP, GRE, GRE over IPSec, OSPF, NHRP
  • Syslog
  • SNMP over the WAN (LAN works)

There are two main types of IPv6 WAN connectivity: native (Auto and Static) and tunneling over IPv4 (6to4, 6in4, and 6rd).

  • Native – (Auto and Static) The upstream ISP routes IPv6 packets directly.
  • IPv6 tunneling – (6to4, 6in4, and 6rd) Each IPv6 packet is encapsulated by the router in an IPv4 packet and routed over an IPv4 route to a tunnel endpoint that decapsulates it and routes the IPv6 packet natively. The reply is encapsulated by the tunnel endpoint in an IPv4 packet and routed back over an IPv4 route. Some tunnel modes do not require upstream ISPs to route or even be aware of IPv6 traffic at all. Some modes are utilized by upstream ISPs to simplify the configuration and rollout of IPv6.

Enable IPv6 and select the desired IPv6 connection method for this WAN interface.

  • Disabled (default) – IPv6 disabled on this interface.
  • Auto – IPv6 will use automatic connection settings (if available).
  • Static – Input a specific IPv6 address for your WAN connection. This is provided by the ISP if it is supported.
  • 6to4 Tunnel – Encapsulates the IPv6 data and transfers it to an automatic tunnel provider (if your ISP supports it).
  • 6in4 Tunnel – Encapsulates the IPv6 data and sends it to the configured tunnel provider.
  • 6rd Tunnel (IPv6 rapid deployment) – Encapsulates the IPv6 data and sends it to a relay server provided by your ISP.

When you configure IPv6, you have the option to designate DNS Servers and Delegated Networks. Because of the dual-stack setup, these settings are optional: when configured for IPv6, the router will fall back to IPv4 settings when necessary.

DNS Servers

Each WAN device is required to connect IPv4 before connecting IPv6. Because of this, DNS servers are optional, as most IPv4 DNS servers will respond with AAAA records (128-bit IPv6 DNS records, most commonly used to map hostnames to the IPv6 address of the host) if requested. If no IPv6 DNS servers are configured, the system will fall back to the DNS servers provided by the IPv4 configuration.

Delegated Networks

A delegated network is an IPv6 network that is inherently provided by or closely tied to a WAN IP configuration. The IPv6 model is for each device to have end-to-end IP connectivity without relying on any translation mechanism. In order to achieve this, each client device on the LAN network needs to have a publicly routable IPv6 address.

Auto

IPv6 auto-configuration mode uses DHCPv6 and/or SLAAC to configure the IPv6 networks. When you select Auto, all of the following settings are optional (depending on your provider’s requirements):

  • PD Request Size – Prefix Delegation request size. This is the size of IPv6 network that will be requested from the ISP to delegate to LAN networks. (Default: 63)
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

Static

As with IPv4, static configuration is available for situations where the WAN IPv6 topology is fixed.

  • IPv6 Address/CIDR – Input the IPv6 static IP address and mask length provided by your ISP (see the Wikipedia explanation of CIDR).
  • IPv6 Gateway IP – Input the IPv6 remote gateway IP address provided by your ISP.
  • Primary IPv6 DNS Server – (optional) Depending on your provider/setup, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6to4 Tunnel

Out of the box, 6to4 is the simplest mode to enable full end-to-end IPv6 connectivity in an organization if the upstream ISP properly routes packets to and from the 6to4 unicast relay servers.

  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6in4 Tunnel

The 6in4 tunnel mode utilizes explicit IPv4 tunnel endpoints and encapsulates IPv6 packets using 41 as the specified protocol type in the IP header. A 6in4 tunnel broker provides a static IPv4 server endpoint, decapsulates packets, and provides routing for both egress and ingress IPv6 packets. Most tunnel brokers provide a facility to request delegated networks for use through the tunnel.

  • Tunnel Server IP – Input the tunnel server IP address provided by your tunnel service.
  • Local IPv6 Address – Input the local IPv6 address provided by your tunnel service.
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6rd Tunnel

IPv6 Rapid Deployment (6rd) is a method of IPv6 site configuration derived from 6to4. It is different from 6to4 in that the ISP provides explicit 6rd infrastructure that handles the IPv4 ↔ IPv6 translation within the ISP network. 6rd is considered more reliable than 6to4 as the ISP explicitly maintains infrastructure to support tunneled IPv6 traffic over their IPv4 network.

  • 6rd Prefix – The 6rd prefix and prefix length should be supplied by your ISP.
  • IPv4 Border Router Address – This address should be supplied by your ISP.
  • IPv4 Common Prefix Mask – Input the number of common prefix bits that you can mask off of the WAN’s IPv4 address.
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

Permalink


Connection Manager


The router can establish an uplink via Ethernet, WiFi as WAN, or 3G/4G modems (integrated or external USB). If the primary WAN connection fails, the router will automatically attempt to bring up a new link on another device: this feature is called failover. If Load Balance is enabled, multiple WAN devices may establish a link concurrently.

WAN Interfaces

This is a list of the available interfaces used to access the Internet. You can enable, stop, or start devices from this section. By using the priority arrows (the arrows in the boxes to the left – these show if you have more than one available interface), you can set the interface the router uses by default and the order that it allows failover.

In the example shown, Ethernet is set as the primary Internet source, while a 4G LTE modem is attached for failover. The Ethernet is “Connected” while the LTE modem is “Available” for failover. A WiFi-as-WAN interface is also attached and “Available”.

  • Load Balance: If this is enabled, the router will use multiple WAN interfaces to increase the data transfer throughput by using any connected WAN interface consecutively. Selecting Load Balance will automatically start the WAN interface and add it to the pool of WAN interfaces to use for data transfer. Turning off Load Balance for an active WAN interface may require the user to restart any current browsing session.
  • Enabled: Selected by default. Deselect to disable an interface.

Click on the small box at the top of the list to select/deselect all devices for either Load Balance or Enabled.

Click on a device in the list to reveal additional information about that device.

Selecting a device reveals the following information:

  • State (Connected, Available, etc.)
  • Port
  • UID (Unique identifier. This could be a name or number/letter combination.)
  • IP Address
  • Gateway
  • Netmask
  • Stats: bytes in, bytes out
  • Uptime

Click “Edit” to view configuration options for the selected device. For 3G/4G modems, click “Control” to view options to activate or update the device.

WAN Configuration

Select a WAN interface and click on Edit to open the WAN Configuration editor. The tabs available in this editor are specific to the particular WAN interface types.

General Settings

Device Settings
  • Enabled: Select/deselect to enable/disable.
  • Force NAT: Normally NAT is part of the Routing Mode setting which is selected on the LAN side in Network Settings → WiFi / Local Networks. Select this option to force NAT whenever this WAN device is being used.
  • Priority: This number controls failover and failback order. The lower the number, the higher the priority and the more use the device will get. This number will change when you move devices around with the priority arrows in the WAN Interfaces list.
  • Load Balance: Select to allow this device to be available for the Load Balance pool.
  • Download bandwidth: Defines the default download bandwidth for use in Load Balance and QoS (quality of service, or traffic shaping) algorithms. (Range: 128 Kb/s to 1 Gb/s.)
  • Upload bandwidth: Defines the default upload bandwidth for use in Load Balance and QoS (quality of service, or traffic shaping) algorithms. (Range: 128 Kb/s to 1 Gb/s.)
  • MTU: Maximum transmission unit. This is the size of the largest protocol data unit that the device can pass. (Range: 46 to 1500 Bytes.)
  • Hostname (This only shows for certain devices.)
IPv4 Failure Check (Advanced)

If this is enabled, the router will check that the highest priority active WAN interface can get to the Internet even if the WAN connection is not actively being used. If the interface goes down, the router will switch to the next highest priority interface available. If this is not selected, the router will still failover to the next highest priority interface but only after the user has attempted to get out to the Internet and failed.

Idle Check Interval: The amount of time between each check. (Default: 30 seconds. Range: 10-3600 seconds.)

Monitor while connected: (Default: Off) Select from the following dropdown options:

  • Passive DNS (modem only): The router will take no action until data is detected that is destined for the WAN. When this data is detected, the data will be sent and the router will check for received data for 2 seconds. If no data is received the router behaves as described below under Active DNS.
  • Active DNS (modem only): A DNS request will be sent to the DNS servers. If no data is received, the DNS request will be retried 4 times at 5-second intervals. (The first 2 requests will be directed at the Primary DNS server and the second 2 requests will be directed at the Secondary DNS server.) If still no data is received, the device will be disconnected and failover will occur.
  • Active Ping: A ping request will be sent to the Ping Target. If no data is received, the ping request will be retried 4 times at 5-second intervals. If still no data is received, the device will be disconnected and failover will occur. When “Active Ping” is selected, the next line gives an estimate of data usage in this form: “Active Ping could use as much as 9.3 MB of data per month.” This amount depends on the Idle Check Interval.
  • Off: Once the link is established the router takes no action to verify that it is still up.

Ping IP Address: If you selected “Active Ping”, you will need to input an IP address. This must be an address that can be reached through your WAN connection (modem/Ethernet). Some ISPs/Carriers block certain addresses, so choose an address that all of your WAN connections can use. For best results, select an established public IP address. For example, you might ping Google Public DNS at 8.8.8.8 or Level 3 Communications at 4.2.2.2.

IPv6 Failure Check (Advanced)

The settings for IPv6 Failure Check match those for IPv4 Failure Check except that the IP address for Active Ping is an IPv6 address.

Failback Configuration (Advanced)

This is used to configure failback, which is the ability to go back to a higher priority WAN interface if it regains connection to its network.

Select the Failback Mode from the following options:

  • Usage
  • Time
  • Disabled

Usage: Fail back based on the amount of data passed over time. This is a good setting for when you have a dual-mode EVDO/WiMAX modem and you are going in and out of WiMAX coverage. If the router has failed over to EVDO it will wait until you have low data usage before bringing down the EVDO connection to check if a WiMAX connection can be made.

  • High (Rate: 80 KB/s. Time Period: 30 seconds.)
  • Normal (Rate: 20 KB/s. Time Period: 90 seconds.)
  • Low (Rate: 10 KB/s. Time Period: 240 seconds.)
  • Custom (Rate range: 1-100 KB/s. Time Period range: 10-300 seconds.)

Time: Fail back only after a set period of time. (Default: 90 seconds. Range: 10-300 seconds.) This is a good setting if you have a primary wired WAN connection and only use a modem for failover when your wired connection goes down. This ensures that the higher priority interface has remained online for a set period of time before it becomes active (in case the connection is dropping in and out, for example).

Disabled: Deactivate failback mode.

Immediate Mode: Fail back immediately whenever a higher priority interface is plugged in or when there is a priority change. Immediate failback returns you to the use of your preferred Internet source more quickly which may have advantages such as reducing the cost of a failover data plan, but it may cause more interruptions in your network than Usage or Time modes.

IP Overrides

IP overrides allow you to override IP settings after a device’s IP settings have been configured.

Only the fields that you fill out will be overridden. Override any of the following fields:

  • IP Address
  • Subnet Mask
  • Gateway IP
  • Primary DNS Server
  • Secondary DNS Server

IPv6 Settings

The IPv6 configuration allows you to enable and configure IPv6 for a WAN device. These settings should be configured in combination with the IPv6 LAN settings (go to Network Settings → WiFi / Local Networks, select the LAN under Local IP Networks, and click Edit) to achieve the desired result.

This is a dual-stacked implementation of IPv6, so IPv6 and IPv4 are used alongside each other. If you enable IPv6, the router will not allow connections via IPv4. When IPv6 is enabled, some router features are no longer supported. These are:

  • RADIUS/TACACS+ accounting for wireless clients and admin/CLI login
  • IP Passthrough (not needed with IPv6)
  • NAT (not needed with IPv6)
  • Bounce pages
  • UPnP
  • Network Mobility
  • DHCP Relay
  • VRRP, GRE, GRE over IPSec, OSPF, NHRP
  • Syslog
  • SNMP over the WAN (LAN works)

There are two main types of IPv6 WAN connectivity: native (Auto and Static) and tunneling over IPv4 (6to4, 6in4, and 6rd).

  • Native – (Auto and Static) The upstream ISP routes IPv6 packets directly.
  • IPv6 tunneling – (6to4, 6in4, and 6rd) Each IPv6 packet is encapsulated by the router in an IPv4 packet and routed over an IPv4 route to a tunnel endpoint that decapsulates it and routes the IPv6 packet natively. The reply is encapsulated by the tunnel endpoint in an IPv4 packet and routed back over an IPv4 route. Some tunnel modes do not require upstream ISPs to route or even be aware of IPv6 traffic at all. Some modes are utilized by upstream ISPs to simplify the configuration and rollout of IPv6.

Enable IPv6 and select the desired IPv6 connection method for this WAN interface.

  • Disabled (default) – IPv6 disabled on this interface.
  • Auto – IPv6 will use automatic connection settings (if available).
  • Static – Input a specific IPv6 address for your WAN connection. This is provided by the ISP if it is supported.
  • 6to4 Tunnel – Encapsulates the IPv6 data and transfers it to an automatic tunnel provider (if your ISP supports it).
  • 6in4 Tunnel – Encapsulates the IPv6 data and sends it to the configured tunnel provider.
  • 6rd Tunnel (IPv6 rapid deployment) – Encapsulates the IPv6 data and sends it to a relay server provided by your ISP.

When you configure IPv6, you have the option to designate DNS Servers and Delegated Networks. Because of the dual-stack setup, these settings are optional: when configured for IPv6, the router will fall back to IPv4 settings when necessary.

DNS Servers

Each WAN device is required to connect IPv4 before connecting IPv6. Because of this, DNS servers are optional, as most IPv4 DNS servers will respond with AAAA records (128-bit IPv6 DNS records, most commonly used to map hostnames to the IPv6 address of the host) if requested. If no IPv6 DNS servers are configured, the system will fall back to the DNS servers provided by the IPv4 configuration.

Delegated Networks

A delegated network is an IPv6 network that is inherently provided by or closely tied to a WAN IP configuration. The IPv6 model is for each device to have end-to-end IP connectivity without relying on any translation mechanism. In order to achieve this, each client device on the LAN network needs to have a publicly routable IPv6 address.

Auto

IPv6 auto-configuration mode uses DHCPv6 and/or SLAAC to configure the IPv6 networks. When you select Auto, all of the following settings are optional (depending on your provider’s requirements):

  • PD Request Size – Prefix Delegation request size. This is the size of IPv6 network that will be requested from the ISP to delegate to LAN networks. (Default: 63)
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

Static

As with IPv4, static configuration is available for situations where the WAN IPv6 topology is fixed.

  • IPv6 Address/CIDR – Input the IPv6 static IP address and mask length provided by your ISP (see the Wikipedia explanation of CIDR).
  • IPv6 Gateway IP – Input the IPv6 remote gateway IP address provided by your ISP.
  • Primary IPv6 DNS Server – (optional) Depending on your provider/setup, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6to4 Tunnel

Out of the box, 6to4 is the simplest mode to enable full end-to-end IPv6 connectivity in an organization if the upstream ISP properly routes packets to and from the 6to4 unicast relay servers.

  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6in4 Tunnel

The 6in4 tunnel mode utilizes explicit IPv4 tunnel endpoints and encapsulates IPv6 packets using 41 as the specified protocol type in the IP header. A 6in4 tunnel broker provides a static IPv4 server endpoint, decapsulates packets, and provides routing for both egress and ingress IPv6 packets. Most tunnel brokers provide a facility to request delegated networks for use through the tunnel.

  • Tunnel Server IP – Input the tunnel server IP address provided by your tunnel service.
  • Local IPv6 Address – Input the local IPv6 address provided by your tunnel service.
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

6rd Tunnel

IPv6 Rapid Deployment (6rd) is a method of IPv6 site configuration derived from 6to4. It is different from 6to4 in that the ISP provides explicit 6rd infrastructure that handles the IPv4 ↔ IPv6 translation within the ISP network. 6rd is considered more reliable than 6to4 as the ISP explicitly maintains infrastructure to support tunneled IPv6 traffic over their IPv4 network.

  • 6rd Prefix – The 6rd prefix and prefix length should be supplied by your ISP.
  • IPv4 Border Router Address – This address should be supplied by your ISP.
  • IPv4 Common Prefix Mask – Input the number of common prefix bits that you can mask off of the WAN’s IPv4 address.
  • Primary IPv6 DNS Server – (optional) Depending on your provider, this may be required. This only takes effect if the default global DNS setting on the Network Settings → DNS page is “Automatic”.
  • Additional IPv6 DNS Server – Secondary DNS server.
  • Delegated IPv6 Network – (optional) Network available for delegation to LANs. Depending on your provider, this may be required. Prefixes specified here only take effect if those supplied by the connection are insufficient to configure your LANs.
  • Delegated IPv6 Network – Additional network available for delegation to LANs.

Example Configuration:

Ethernet Settings

While default settings for each WAN Ethernet port will be sufficient in most circumstances, you have the ability to control the following:

  • Connect Method: DHCP (Automatic), Static (Manual), or PPPoE (Point-to-Point Protocol over Ethernet).
  • MAC Address: You have the ability to change the MAC address, but typically this is unnecessary. You can match this address with your device’s address by clicking: “Clone Your PC’s MAC Address”.

Connect Method

Select the connection type that you need for this WAN connection. You may need to check with your ISP or system administrator for this information.

  • DHCP (Dynamic Host Configuration Protocol) is the most common configuration. Your router’s Ethernet ports are automatically configured for DHCP connection. DHCP automatically assigns dynamic IP addresses to devices in your networks. This is preferable in most circumstances.
  • Static allows you to input a specific IP address for your WAN connection; this should be provided by the ISP if supported.
  • PPPoE should be configured with the username, password, and other settings provided by your ISP.

If you want to use a Static (Manual) or PPPoE connection, you will need to fill out additional information.

Static (Manual):

  • IPv4 Address
  • Subnet Mask
  • Gateway IP
  • Primary DNS Server
  • Secondary DNS Server

PPPoE:

  • Username
  • Password
  • Password Confirm
  • Service
  • Auth Type: None, PAP, or CHAP

Modem Settings

Not all modems will have all of the options shown below; the available options are specific to the modem type.

On Demand: When this mode is selected a connection to the Internet is made as needed. When this mode is not selected a connection to the Internet is always maintained.

IP WAN Subnet Filter: This feature will filter out any packets going to the modem that do not match the network (address and netmask).

Aggressive Reset: When Aggressive Reset is enabled the system will attempt to maintain a good modem connection. If the Internet has been unreachable for a period of time, a reset of the modem will occur in attempt to re-establish the connection.

Automatically check for new firmware: (Default: selected) The modem will automatically check for firmware updates by default.

Enable Aux Antenna: (Default: selected) Enable or disable the modem’s auxiliary diversity antenna. This should normally be left enabled.

GPS Signal Source: Select the antenna to be used for receiving GPS coordinates. Some products support a dedicated GPS antenna, while others use the auxiliary diversity antenna only (and some products support both).

Enable eHRPD: (Default: selected) Enable or disable the modem’s ability to connect via eHRPD (enhanced High Rate Packet Data) when connecting to a 3G EVDO network on Sprint. eHRPD routes EVDO traffic through the LTE systems, enabling easy transitions between LTE and EVDO. In rare cases it may make sense to bypass the LTE core, so this field allows you to disable eHRPD.

Modem Connection Mode: Specify how the modem should connect to the network. Not all options are available for all modems; this will default to Auto if an incompatible mode is selected.

  • Auto (all modes): Let the modem decide which network to use.
  • Auto 3G (3G or less): Let the modem decide which 2G or 3G network to use. Do not attempt to connect to LTE.
  • Force LTE: Connect to LTE only and do not attempt to connect to 3G or WiMAX.
  • Force WiMAX: Connect to WiMAX only and do not attempt to connect tot 3G or LTE.
  • Force 3G (EVDO, UMTS, HSPA): Connect to 3G network only.
  • Force 2G (1xRTT, EDGE, GPRS): Connect to 2G network only.

Network Selection Mode: Wireless carriers are assigned unique network identifying codes known as PLMN (Public Land Mobile Network). To manually select a particular carrier, select the Manual radio button and enter the network PLMN. Choose from the following options:

  • None/No Change
  • Auto: Selected by default
  • Home only
  • Manual: Input the PLMN code

Functional Mode: Selects the functional mode of the modem. IPPT (IP passthrough) mode causes the modem to act as a transport, passing Internet data and IP address information between the modem and the Internet directly. NAT mode causes the modem to NAT the IP address information. Consequently, IPPT mode does not allow user access to the modem web UI and NAT mode does allow user access to the modem web UI.

  • None/No Change
  • IPPT
  • NAT

Network-Initiated Alerts: This field controls whether the Sprint network can disconnect the modem to apply updates, such as for PRL, modem firmware, or configuration events. These activities do not change any router settings, but the modem connection may be unavailable for periods of time while these updates occur. The modem may also require a reset after a modem firmware update is complete.

  • Disabled: The request to update will be refused.
  • When Disconnected: The request to update will only be performed when the modem is either in a disconnected state or dormant state. If the modem is not in one of these states when the request is received, then the router will remember the request and perform the update when the modem becomes disconnected/dormant.
  • On Schedule: The request to update will only be performed at the specified scheduled time, no matter what the state of the modem is.

Network-Initiated Schedule: When you select “On Schedule” for Network-Initiated Alerts, you also select a time from this dropdown list. Modem updates will take place at this scheduled time.

AT Config Script: Enter the AT commands to be used for carrier specific modem configuration settings. Each command must be entered on a separate line. The command and associated response will be logged, so you should check the system log to make sure there were no errors.

NOTE: AT Config Script should not be used unless told to do so by your modem’s cellular provider or by a support technician.

AT Dial Script: Enter the AT commands to be used in establishing a network connection. Each command must be entered on a separate line. All command responses must include “OK”, except the final command response, which must include “CONNECT”.

Example:

AT
ATDT*99***2#

WiMAX Settings

WiMAX Realm: Select from the following dropdown options:

  • Clear – clearwire-wmx.net
  • Rover – rover-wmx.net
  • Sprint 3G/4G – sprintpcs.com
  • Xohm –xohm.com
  • BridgeMAXX – bridgeMAXX.com
  • Time Warner Cable – mobile.rr.com
  • Comcast – mob.comcast.net

TTLS Authentication Mode: TTLS inner authentication protocol. Select from the following dropdown options:

  • MSCHAPv2/MD5 (Microsoft Challenge Handshake Authentication Protocol version2/Message-Digest Algorithm 5)
  • PAP (Password Authentication Protocol)
  • CHAP (Challenge Handshake Authentication Protocol)

TTLS Username: Username for TTLS authentication.

TTLS Password: Password for TTLS authentication.

WiMAX Authentication Identity: User ID on the network. Leave this blank unless your provider tells you otherwise.

CDMA Settings

These settings are usually specific to your wireless carrier’s private networks. You should not set these unless directed to by a carrier representative. If a field below is left blank, that particular setting will not be changed in the modem. You should only fill in fields that are required by your carrier.

  • Persist Settings: If this is not checked, these settings will only be in place until the router is rebooted or the modem is unplugged.
  • Active Profile: Select a number from 0-5 from the dropdown list.

The following fields can be left blank. If left blank they will remain unchanged in the modem.

  • NAI (Username@realm): Network Access Identifier. NAI is a standard system of identifying users who attempt to connect to a network.
  • AAA Shared Secret (Password): “Authentication, Authorization, and Accounting” password.
  • Verify AAA Shared Secret
  • HA Shared Secret: “Home Agent” shared secret.
  • Primary HA
  • Secondary HA
  • AAA SPI: AAA Security Parameter Index.
  • HA SPI: HA Security Parameter Index.

SIM/APN/Auth Settings

SIM PIN: PIN number for a GSM modem with a locked SIM.

Authentication Protocol: Set this only if your service provider requires a specific protocol and the Auto option chooses the wrong one. Choose from Auto, PAP, and CHAP and then input your username and password.

Access Point Configuration: Some wireless carriers provide multiple Access Point configurations that a modem can connect to. Some APN examples are ‘isp.cingular” and “vpn.com”.

  • Default: Let the router choose an APN automatically.
  • Default Override: Enter an APN by hand.
  • Select: This opens a table with 16 slots for APNs, each of which can be set as IP, IPV4V6, or IPV6. The default APN is marked with an asterisk (*). You can change the APN names, select a different APN, etc. For Verizon modems, only the third slot is editable. Changes made here are written to the modem, so a factory reset of the router will not impact these settings.

Update/Activate a Modem

Some 3G/4G modems can be updated and activated while plugged into the router. Updates and activation methods vary by modem model and service provider. Possible methods are: PRL Update, Activation, and FUMO. All supported methods will be displayed when you select your modem and click “Control” to open the “Update/Activate” window. If no methods are displayed for your device then you will need to update and activate your device externally.

To update or activate a modem, select the modem in the WAN Interfaces table and click “Control”.

The modem does not support Update/Activate methods: A message will state that there is no support for PRL Update, Activation, or FUMO.

The modem supports Update/Activate methods: A message will display showing options for each supported method:

  • Modem Activation / Update: Activate, Reactivate, or Upgrade Configuration.
  • Preferred Roaming List (PRL) Update
  • Firmware Update Management Object (FUMO)

Click the appropriate icon to start the process.

If the modem is connected when you start an operation the router will automatically disconnect it. The router may start another modem as a failover measure. When the operation is done the modem will go back to an idle state, at which point the router may restart it depending on failover and failback settings.

NOTE: Only one operation is supported at a time. If you try to start the same operation on the same modem twice the UI will not report failure and the request will finish normally when the original request is done. However if you try to start a different operation or use a different modem, this second request will fail without interfering with the pending operation.

Process Timeout: If the process fails an error message will display.

Activation has a 3-minute timeout, PRL update has a 4-minute timeout, and FUMO has a 10-minute timeout.

Update Modem Firmware

Click on the Firmware button to open the Modem Firmware Upgrade window. This will show whether there is new modem firmware available.

If you select Automatic (Internet) the firmware will be updated automatically. Use Manual Firmware Upgrade to instead manually upload firmware from a local computer or device.

Reset the Modem

Click on the Reset button to power cycle the modem. This will have the same effect as unplugging the modem.

Configuration Rules (Advanced)

This section allows you to create general rules that apply to the Internet connections of a particular type. These can be general or very specific. For example, you could create a rule that applies to all 3G/4G modems, or a rule that only applies to an Internet source with a particular MAC address.

The Configuration Rules list shows all rules that you have created, as well as all of the default rules. These are listed in the order they will be applied. The most general rules are listed at the top, and the most specific rules are at the bottom. The router goes down the list and applies all rules that fit for attached Internet sources. Configuration settings farther down the list will override previous settings.

Select any of these rules and click “Edit” to change the settings for a rule. To create a new rule, click “Add.”

WAN Configuration Rule Editor

After clicking “Add” or “Edit,” you will see a popup with the following tabs:

  • Filter Criteria
  • General Settings
  • IP Overrides
  • IPv6 Settings
  • Ethernet Settings
  • Modem Settings
  • WiMAX Settings
  • CDMA Settings
  • SIM/APN/Auth Settings

Filter Criteria

If you are creating a new rule, begin by setting the Filter Criteria . Create a name for your rule and the condition for which the rule applies:

  • Rule Name: Create a name meaningful to you. This name is optional.

Make a selection for “When,” “Condition,” and “Value” to create a condition for your rule. The condition will be in the form of these examples:

When Condition Value
Port is USB Port 1
Type is not WiMAX
  • When:
    • Port – Select by the physical port on the router that you are plugging the modem into (e.g., “USB Port 2”).
    • Manufacturer – Select by the modem manufacturer, such as Sierra Wireless.
    • Model – Set your rule according to the specific model of modem.
    • Type – Select by type of Internet source (Ethernet, LTE, Modem, Wireless as WAN, WiMAX).
    • Serial Number – Select 3G or LTE modem by the serial number.
    • MAC Address – Select WiMAX modem by MAC Address.
    • Unique ID – Select by ID. This is generated by the router and displayed when the device is connected to the router.
  • Condition: Select “is,” “is not,” “starts with,” “contains,” or “ends with” to create your condition’s statement.
  • Value: If the correct values are available, select from the dropdown list. You may need to manually input the value.

Once you have established the condition for your configuration rule, choose from the other tabs to set the desired configuration. All of the tabs have the same configuration options shown above in the WAN Configuration section (i.e., the options for Configuration Rules are the same as they are for individual devices).

Permalink


Router Firmware Upgrade: Best Practices

Products Supported: Series 3 Click here to identify your router.


Quick Links

Summary

Configuration

Best Practices

Related Articles


Summary

This article provides instructions on how to upgrade your Series 3 Cradlepoint router through the local device and through Enterprise Cloud Manager(ECM). Best practices regarding firmware upgrades are also listed within this article.

Caution: Updating the firmware can permanently damage your router. The upgrade process will take several minutes. Do not unplug your router from the provided power supply during this process.

Note: Downgrading firmware to a version lower than 5.2.0 will require resetting the router to factory default settings.


Configuration

Configuration Difficulty: Easy

Local Router Upgrade

Automatically Upgrading from 5.4.x or Earlier

Note: The device has to be on the internet to update automatically

  • Step 1: Log into the router’s Setup Page. For help with logging in please click here.
  • Step 2: Navigate across the top menus to System Settings>System Software
User-added image
  • Step 3: Press the Automatic(Internet) button.
User-added image

Automatically Upgrading from 6.0.x or Later

Note: The device has to be on the internet to update automatically

  • Step 1: Log into the router’s Setup Page. For help with logging in please click here.
  • Step 2: Navigate across the left-hand menus to System>System Control>System Firmware
User-added image
  • Step 3: Press the Automatic(Internet) button.
User-added image

Downloading Firmware for Manual Upgrade

Note: These instructions are only for manual firmware upgrades. You do not need to download firmware when upgrading automatically or with ECM.

  • Step 1: Log into your Connect Portal account. The login page can be found here.
  • Step 2: Click the menu button. Hover over My Support and click Firmware Downloads.
User-added image
  • Step 3: Select the model of your router from the drop down menu.
User-added image
  • Step 4: Click download on the firmware version you are updating to
User-added image

Manually Upgrading from 5.4.x or Earlier
  • Step 1: Log into the router’s Setup Page. For help with logging in please click here.
  • Step 2: Navigate across the top menus to System Settings>System Software
User-added image
  • Step 3: Press the Manual Firmware Upload button.
User-added image
  • Step 4: In the box that appears press Choose File and use the pop up window to navigate to the firmware file
User-added image
  • Step 5: Press Begin Firmware Update
User-added image

Manually Upgrading from 6.0.x or Later
  • Step 1: Log into the router’s Setup Page. For help with logging in please click here.
  • Step 2: Navigate across the left-hand menu to System>System Control>System Firmware
User-added image
  • Step 3: Press the Manual Firmware Upload button.
User-added image
  • Step 4: In the box that appears press Select Firmware File and use the pop up window to navigate to the firmware file
User-added image
  • Step 5: Press Begin Firmware Update
User-added image

ECM Upgrade

  • Step 1: Log into your Enterprise Cloud Manager account. The login page can be found here.
  • Step 2: Navigate across the left-hand menu to Groups.
User-added image
  • Step 3: Create a new group for the device using the firmware the device is currently on.
User-added image
  • Step 4: Navigate to Devices and select the router. Press the move button and put it in the new group.
User-added image
User-added image
  • Step 5: Navigate back to the groups page and press firmware. Select the firmware you would like to upgrade to.
User-added image
  • Step 6: Press Run Now
User-added image

Best Practices

Configuration Backup

It is recommended that before upgrade you backup your configuration. Click here for help making backups.

Firmware Testing

Before upgrading routers in a live deployment, it is a good idea to test the firmware before updating all your devices. Testing beforehand also helps to have a smoother time when upgrading all your devices.

The best way to test is to have a lab environment where you can create a situation similar to your live network and test how your configuration will work with different firmware.

The next step would be to test a small controlled group of devices in production on the prospective firmware to ensure a smooth transition for that firmware to your network.

Stair Stepping

When upgrading firmware between major and minor versions, it is highly recommended to perform a stair-step upgrade. A stair step upgrade entails making short jumps between firmware versions as shown below.

           Example: From 5.1.1 to 6.1.0
                   Start:___5.1.1
                Update 1:_________5.2.0
                Update 2:_______________5.2.4
                Update 3:_____________________5.3.4
                Update 4:__________________________ 5.4.1 
                Update 5:_________________________________6.0.1
                     End:_______________________________________6.1.0

Permalink


Products Affected: AER31x0, AER2100, AER16x0, IBR11x0, IBR9x0, IBR6x0, IBR6x0B, IBR6x0C, IBR350, CBA850, and MBR1200B. Click here to identify your router.

Summary

Cradlepoint was notified of critical security vulnerabilities discovered in the dnsmasq network service (CVE-2017-14491 and others); in response Cradlepoint has taken steps to incorporate the dnsmasq version 2.78 into its latest NetCloud OS.

If exploited, this vulnerability could allow attackers to remotely execute code, forward the contents of process memory, or disrupt service on an affected router. As described in various sources, this flaw is difficult to trigger, requiring an attacker who controls a specific domain to send DNS requests to dnsmasq requiring it to cache replies from that domain. Through carefully constructing DNS requests and responses, dnsmasq could cause an internal buffer overflow using content influenced by the attacker.

More details can be found here: https://security.googleblog.com/2017/10/behind-masq-yet-more-dns-and-dhcp.html.


Affected Products

Cradlepoint recommends customers immediately upgrade products to the upcoming NetCloud OS versions (available 10/30/17) to mitigate this vulnerability. All router products are affected, including:

• AER3100 / AER3150
• AER2100
• AER1600 / AER1650
• IBR1100 / IBR1150
• IBR900 / IBR950
• IBR600 / IBR650
• IBR600B / IBR650B
• IBR600C / IBR650C
• IBR350
• MBR1200B
• CBA850

NOTE: Routers used in default configuration were not exposed on their WAN interfaces. Routers were exposed to their Local Network, including the Guest LAN (if enabled).

NetCloud Manager has been patched for all its own affected services. Usernames and passwords are not at risk.


NetCloud OS Patch

6.4.2 (Available 10/30/17) – All products listed above

6.4.3 (Available 12/11/17) – IBR900/IBR950 – FIPS

Remote NetCloud OS Upgrades

For remote devices, Cradlepoint recommends using NetCloud Manager to upgrade NetCloud OS, manage networks intelligently, and avoid costly truck rolls. If you haven’t deployed NetCloud Manager, you can start a free 30-day trial of NetCloud Manager today.
Local NetCloud OS Upgrades

For information on updating NCOS locally on the Cradlepoint please consult the below articles.

NCOS: Automatic NetCloud OS Update

NCOS: How to update the NCOS of a Cradlepoint router.


Interim Mitigation Until NetCloud OS Release

Because malicious tools could be used to obtain passwords during this period, Cradlepoint recommends the following steps to protect your network during the interim:

  1. Disable Guest Access via the NETWORKING > Local Networks > Local IP Networks tab.

Once NetCloud OS 6.4.2 or 6.4.3 is Available
1. Upgrade to the latest NetCloud OS version
2. Re-enable Guest Access if it was disabled

Permalink


Summary

Two new vulnerabilities that affect many modern microprocessors were published on January 3rd, 2018. These vulnerabilities could allow attackers to read the contents of memory used by other applications on the same server or even processes running in other virtual machines (VMs).

The first vulnerability, called Meltdown, affects only Intel CPUs and can be fixed with an operating system patch.

The second, called Spectre, affects CPUs from AMD and ARM. It requires a CPU design change and cannot be fixed in software.

Cradlepoint routers are not affected by either vulnerability.  However, Cradlepoint services like NetCloud Manager (NCM) and NetCloud Perimeter (NCP) run on servers that may be vulnerable.

What is it?

Both vulnerabilities are based on a CPU optimization called “speculative execution”. Both also require an attacker to install malware on the target system.

With Meltdown, an attacker — who can install and run a program on the target machine — can access the memory of all other programs running on that machine.

With Spectre, an attacker can “read” memory of other programs through indirect means.

For more information, please see

  1. https://googleprojectzero.blogspot.ca/2018/01/reading-privileged-memory-with-side.html
  2. https://security.googleblog.com/2018/01/more-details-about-mitigations-for-cpu_4.html
  3. https://meltdownattack.com

 

 

The related CVEs are shown below:

CVE-2017-5715 (Spectre) “branch target injection” mitigated by CPU microcode update from CPU vendor
CVE-2017-5753 (Spectre) “bounds check bypass”
CVE-2017-5754 (Meltdown) “rogue data cache load” fixed with OS update

What Cradlepoint devices or services may be affected?

All NCM and NCP services run on cloud servers which may be affected. However, most NCM services run on multi-tenant servers and Cradlepoint’s primary cloud provider has patched their servers so that NCM is not vulnerable to Meltdown attacks running in other tenant spaces.

 

NCM could still be vulnerable to Meltdown exploits which manage to install malware on the NCM VMs. The operating system patch to fix Meltdown is expected to be released soon.  Cradlepoint will then begin immediate execution of its plans to apply the patch to all NCM systems.

 

No Cradlepoint routers use CPU’s vulnerable to Meltdown.

 

For Spectre, Cradlepoint does not support installing compiled applications on any routers with the Spectre vulnerability. An attacker would need to install malware that exploits certain CPU instruction patterns. Such patterns can only exist in compiled programs and Cradlepoint does not support compiling SDK apps.

Published Date: 01/08/2018

Permalink


Cradlepoint Series 3 (104)

View category →

If you are not sure what model CradlePoint router you have, please click here.

This article was written based upon firmware version 5.0.0.

Description:

Use the Simple Network Management Protocol (SNMP) Settings sub-menu to enable or disable the SNMP protocol over either the LAN, WAN or both interfaces. For security, you can also set the community names for both Get and Set SNMP requests. SNMP versions 1, 2 and 3 are currently implemented. The supported MIB is the standard RFC 1213 MIB as maintained by the IETF. Additional Cellular-router MIB elements are available through CradlePoint’s WIPIPE-MIB.

Directions:

To enable SNMP login to the Setup Pages of the CradlePoint (for assistance in logging into the Setup Pages click here).

  1. Click on the System Settings tab, then click SNMP Configuration.User-added image
  2. Check the box next to Enable SNMP                                                                     User-added image

 

Enable on LAN
Enable SNMP on the local LAN ports so that a local device can manage the router.

Enable on WAN
Enable SNMP on the external WAN port so that an external device can manage the router.

SNMPv1
SNMP version 1 is the most basic version of SNMP

SNMPv2c
SNMP version 2 has the same features as v1 with some additional commands.

SNMPv3
SNMP version 3 includes all prior features with security available.

Get Community String
Variable length string which allows access to read-only data within this community group. The community names should never be “public” or “private”. Community names are a maximum of 15 characters long. Names should contain at least one number and one capital letter. Access to the community name should be limited to the Administrator of realms.

Set Community String
Variable length string which allows access to read and write data within this community group. The community names should never be “public” or “private”. Community names are a maximum of 15 characters long. Names should contain at least one number and one capital letter. Access to the community name should be limited to the Administrator of realms.

Authentication Type
Select the authentication and encryption type that will be used when connection to the router.  These settings must match the configuration used on any SNMP clients.

Enable SNMP Traps
Enabling traps will allow you to configure a destination server, community, and port for trap notifications.  Trap notifications are returned to the server with SNMPv1

System Contact
The email address of the system administrator

System Name
Router’s host name

System Location
Physical location of router

Note: The file attached to this document is the detailed SNMP Definitions

Permalink

0 Comments - Leave a Comment

QUICK LINKS:


OVERVIEW:

This configuration document will guide you through how to configure VLAN interfaces on CradlePoint Routers, and will feature a typical Enterprise VLAN topology design implementation.


SYSTEM REQUIREMENTS:

VLAN interface configuration is recommended for the following CradlePoint Routers:

  • AER2100
  • MBR1400
  • IBR600
  • IBR650


FIRMWARE VERSION:

This content was created using firmware 5.0.0


TECHNICAL TERMS:

  • Virtual LAN (VLAN):  Distinct broadcast domain of a single layer-2 network, configured using software rather than hardware. Achieved by adding 802.1Q headers to Ethernet Packets.
  • VLAN Interface:  A layer-3 interface that allows for VLAN tagging on specific Ethernet port groups
  • Trunk Port:  Ethernet port that sends and receives tagged frames from more than one VLAN


NETWORK TOPOLOGY:

For this example, we are going to use the following network topology design. We will split up the network devices into 7 different IP networks. These networks were designed much like a typical enterprise network for a datacenter that segments and separates physical and virtual servers and storage arrays. Below is a list of the VLANs and IP addressing information that are presented in this document. All of the networks will need to be configured with 802.1Q VLAN tagging for Trunking multiple VLANs over a single Ethernet port. All networks will participate in VLAN packet tagging.

User-added image
User-added image



CONFIGURATION:

Note: The following configuration examples were written for the MBR1400, but can be applied to any CradlePoint router that supports VLANs

Step 1:  Ethernet Port Configuration

Our topology will require Trunking of all IP networks on one orange Ethernet port to a single core switch. To achieve this, we will need to do the following:

  1. Create a new port group, by choosing Ethernet Port Configuration under Network Settings > WiFi / Local Networks.
  2. Click Add.
  3. Give the Ethernet port group a name, and move the desired port to the “Selected” side. Click Submit.
    • If your network design involves trunking to more than a single switch, then simply add more ports to the Selected side while configuring. The configuration should look something similar to the image below.User-added image

*Note* If you are currently managing the CradlePoint router from the orange port you are connected to, this step will cause loss of connectivity to the router. Managing the CradlePoint router from another LAN port, or using WiFi, is recommended for the duration of this configuration example.


Step 2:  VLAN Interface Configuration

We will create the VLAN interfaces that will later be associated with specific IP networks, for now this step will associate a VLAN interface (VID tag number) with the selected port group, specifically the Dot1QTrunk group we just configured.

  1. Navigate to the VLAN Interfaces tab under Network Settings > WiFi / Local Networks
  2. Create a new VLAN by selecting the Add button.
  3. Fill in the VID and the Port Group the VLAN interface will apply to.
    • In this configuration example, we will create 7 VLAN interfaces, one for each of the following VIDs; 101, 110, 111, 191, 171, 172, and 192. Ethernet Port group Dot1QTrunk should be selected for all 7 VLAN’s. User-added image

Step 3:  IP Networks

  1. To add a new IP network, click Add under “Local IP Networks.”
  2. On the General Settings tab, name your network and check the Enabled box.     User-added image
  3. On the IPv4 Settings tab, set the IP address according to your topology.               User-added image
  4. On the interfaces tab, make sure you move the VLAN ID to “Selected”.                  User-added image
  5. Click Submit.

*Note* – You can add your WiFi SSID’s to any network. It is recommended to not add public WiFi to any management VLAN’s.


FINAL CONFIGURATION SHOULD LOOK LIKE THE BELOW.

User-added image
User-added image

Permalink


If you are unsure of your CradlePoint Series or Model number, please click here.

This article was written based on firmware version 5.0.0.

 

 

Symptom:

Inability to access the CradlePoint router’s setup pages from any connected device.


Cause:

After making configuration changes you are unable to access the CradlePoint.  Changed the Wireless/WiFi or Administration password and are no longer able to access CradlePoint or setup pages.


Resolution:

Warning:  Performing a Factory Reset will erase all configuration changes that have been applied to the CradlePoint router

  1. Disconnect any devices that are connected physically to the CradlePoint, leave only the power cord connected to the router.
  2. With the router power ON use a straightened paper clip to press and hold the Reset Button on the CradlePoint router for at least 45 seconds.

Allow approximately 1 minute for the router to initialize and complete it’s boot up cycle before attempting to reconnect to the router.  The router has been returned to the original factory configuration, so be sure to use the default password and reconfigure WiFi security and/or any other configuration settings needed.

Permalink


This article explains the steps needed to get your Cable Modem connected to your CTR35 or CBR400 router.

This article was written based on 3.6.3 and 4.3.2 firmware versions.

Summary:

This article describes how to configure a CTR35 or CBR400 router models to connect to a Cable, DSL or Satellite modem.

Directions:

BEFORE YOU BEGIN:

CONFIGURING THE ROUTER:

  1. Click on the Network Settings tab and select WiFi/Local Networks from the drop-down menu. User-added image
  2. Scroll down to the Local Network Interfaces section and click on the Ethernet Port Configuration tab. User-added image
  3. In the drop-down next to your Ethernet port, change the mode to Internet (WAN)NOTE: if you are currently connected to your router with a cable, you will lose access to the router, and it will have to be reset. User-added image
  4. Change your router’s IP address to 192.168.50.1. Reference this article for detailed instructions.



CONNECTING THE MODEM: 

  1. If you already have your cable modem plugged into your router, unplug it.
  2. Power off both the CradlePoint router and the modem. If the modem doesn’t have an on/off switch, just pull out the power cord.
  3. While both devices are turned off, connect them with an Ethernet cable.
  4. Wait 30 seconds and power on just the modem.
  5. Wait until the modem connects to your ISP’s network (usually 30-35 seconds), then power the CradlePoint router back on.

After the CradlePoint router goes through its startup sequence, it will connect to your modem, and all devices that are connected to the CradlePoint wirelessly should have Internet access.

NOTE:  To access your router’s administrative console again, use the IP address that was specified during step #4 of router’s set up (typically 192.168.50.1).


IF YOU ARE UNABLE TO GET THROUGH TO THE INTERNET, PLEASE REVIEW THE FOLLOWING:

  • Check your computer’s network settings:
  • Call your Internet Service Provider and tell them you need to reset your cable/DSL/Satellite modem.  Your modem may have saved the information from the last connection you had, and you need to restore the cable modem to default settings.
  • Clone your computer’s MAC address in the CradlePoint router. Instructions

Permalink


If you are unsure of your CradlePoint Series or Model number, please click here.

This article was written based on firmware version 5.0.0.


Device Alerts:

This article describes the configuration for Device Alerts and Email notification in Series 3 CradlePoint Routers.  Device Alerts allow you to get automatic notifications through an SMTP email server of selected system events.  Since the router does not have its own SMTP server, you must enable an SMTP email server, such as Gmail, Yahoo, etc., to be able to receive Device Alerts.
 

Enabling Device Alerts:

1.  Login to the router’s setup page (login instructions).

2.  Click on the System Settings tab then select Device Alerts from the sub-menu.

3.  In the Alert Configuration section select which alerts will be reported, the frequency and the time for the email
     notifications.  Below is a synopsis of the available alert options.

  • Firmware Upgrade Available:  Notification of a new firmware release for this router.
  • WAN Device Status Change:   An attached WAN device has changed status. The possible statuses are plugged, unplugged, connected, and disconnected.
  • Login Failure:  A failed login attempt has been detected.
  • Full System Log:  The system log has filled.
  • Recurring System Log:   The router log is sent periodically.  This alert contains all of the system events since the last recurring alert. It can be scheduled for daily, weekly and monthly reports.  You also choose the time you want the Alert sent.

4.  In the SMTP Mail Server section enter the SMTP settings for your email account.  Each SMTP server will have
     different specifications for setup, so you have to look up your specific settings separately.  Contact your Email
     provider for more information.  Below is a brief synopsis of each field.

  • Server Address: The SMTP server URL.
  • Server Port: The SMTP port used by the email Server.
  • Authentication Required: Check this box if you are required to provide login credentials to sign into your email.  This is typically required.
  • User Name:  Your full email address.
  • Password:  Your email password.
  • From Address:  Your email address, the sender email for the Device Alerts.
  • To Address:  Your email address, the receiver email for the Device Alerts.
  • **NOTE: Please utilize all lower case letters when inputting To and From email addresses.**


             User-added image

5.  In the Advanced Delivery Options settings area select any of the following options.

  • Email Subject Prefix:  Optional alert email subject prefix.  This option is helpful to identify alerts from specific routers.
  • Retry Attempts:  The number of attempts made to send the alert to the mail server.  After the attempts are exhausted, the alert is discarded.
  • Retry Delay:  The delay between each retry attempt.

6.  Apply your new settings.

           User-added image

Permalink


Cradlepoint Series 2 (49)

View category →

If you are unsure of your CradlePoint Series or Model number, please click this link.

This article was written based on firmware version 2.0.0

To establish an Access Point Name (APN) on your Series 2 CradlePoint router, please follow the steps below:

Note: You will need obtain the correct APN to use with your cellular carrier and modem prior to starting these steps.  Please contact your cellular carrier to obtain the correct APN.

Access Point Name (APN) setup Procedure:

  1. Log into your router admin pages from an Internet Browser (Firefox, Internet Explorer, Google Chrome). If you are unsure how, please click here.
  2. Go to the Modem tab along the top.
  3. Then click Settings along the left side.
  4. Find the box titled Modem Specific Settings. User-added image
  5. Change the Modem Interface drop-down box to the port your modem is plugged into.
  6. Find the Section labeled Access Point Name (APN). If there is a blank box next to it, enter the APN provided by your cellular carrier into the box.
  7. If there is not an entry box, click Manual Entry.
  8. In the box that appears below Manual Entry input the APN provided by your cellular carrier.User-added image
  9. Then go back to the top of the page, click Save Settings and then Reboot Now.
  10. You may need to unplug and then replug your modem from the power source after the reboot.
  11. After the CradlePoint reboots, you should be able to access the Internet from a connected device.

Permalink


If you are not sure what model CradlePoint router you have, please click here.

This article was written based upon firmware version 2.0.0.


Overview:

In areas where the 4G (LTE) signal is low, unavailable, and/or unstable the modem may constantly change between a good 3G connection and unusable 4G connection.  While the modem disconnects from 3G service and attempts the 4G connection the internet is not available.  By default the CradlePoint router is set to have the modem connect to the highest speed network available.  This scenario is common in fringe 4G coverage areas.  In such a case, it is advised to restrict a Verizon 3G/4G (LTE) modem to a 3G connection only to eliminate these issues.


Directions:

It is advised that your router has the most recent Firmware release loaded.  For instructions to check the router Firmware version see How to check Firmware version and How to Update Series 2 Firmware.

  1. Log into the administrative console, the default location is http://192.168.0.1 Click here if you are unsure how to access the administration pages.
  2. Click the MODEM tab then select SETTINGS from gray sub-menu on the left.                                             User-added image
  3. Locate the MODEM SPECIFIC SETTINGS section then select the correct Modem Interface from the drop-down menu. User-added image
  4. In the LTE Multi Mode Settings sub-section change Connect Mode to Auto 3G (3G or less)User-added image
  5. Click Save Settings at the top of the page.                                                               User-added image
  6. When prompted select Reboot Now.                                                                         User-added image


After the router reboots the CradlePoint router will restrict the Verizon 3G/4G modem connection to 3G EVDO speeds (or lower if necessary).

Note:  If 4G (LTE) signal becomes available or change to a location where 4G (LTE) signal is available you may want to change this setting back to 4G(auto).

Permalink


If you are not sure what Series CradlePoint router you have, please click here.

This article was written based on firmware version 2.0.0 for Series 2 CradlePoint routers.

Symptom:

A specific computer, device, or program needs ports open or forwarded in a Series 2 CradlePoint router’s firewall.

Resolution:

There are three distinct methods of handling port forwarding on the Series 2 Routers, each for a different application.  The instructions for each are detailed below.

  1. Virtual Server allows you to forward ports to a device behind the CradlePoint.
  2. Gaming allows you to forward multiple ports to a device behind the CradlePoint.
  3. Special Applications allows you to forward multiple ports to all devices behind the CradlePoint.

Instructions for Virtual Server:

  1. Log into the routers administration page (login instructions).
  2. Select the Advanced tab
  3. On the left side of the page select Virtual Server.                                                                                                                                                                                                                              virtual server.jpg
  4. Go to the ADD VIRTUAL SERVER RULE section
  5. Make sure that the Enable: check box is checked
  6. In the Name: Field you can enter a descriptive name for the rule or you can select one of the predefined rules provided in the router.
  7. In the IP Address: field enter the LAN IP address of the machine hosting the application/server you wish to access from the internet.  The drop down list located next to this field displays machine names and IP addresses of connected devices.  NOTE: When setting up a Virtual Server it is very important that the LAN IP address of the application/server machine never change.  Refer to the “How to setup a DHCP reservation” document for more information.
  8. In the Protocol: field select either TCP, UDP, or Both from the drop down list.  If your protocol is not listed, you can select Other from the drop-down list and specific the number in the Protocol field.
  9. The Public Port: field is where you enter the port number used by the application you are using to access the application/server on the local LAN.  For example, if you are trying to setup a web site on your local network that you wish to access from the internet.  HTTP by default uses port 80, however if your ISP or Cell carrier blocks port 80 then you would need to change this public port to something like 8080.  So in the Public port field you would enter 8080, and then when you open your browser you would enter http://www.yourdomain.com:8080.
  10. The Private Port: field is where you would enter the internal port number to be used to access the internal application/server.  Most of the recent versions of application/servers have the ability to change the port number they listen on.  So back to the example in step 9, if your web site server is listening on port 8282 you would want to enter this number into the private port field.
  11. In the Schedule: drop down list you can select a user defined schedule for a time duration of when this rule should allow/deny port forwarding.  For more information see “How to setup Schedules.”
  12. In the Inbound Filter: drop down list you can select a user defined inbound filter which will either allow or reject the port forward request by external IP address.  For more information see “How to setup Inbound Filters.”
  13. Click the Save button.  You should now see the rule listed in the Virtual Server List.
  14. Click Save Settings button at the top of the page. (NOTE: if the rule does not take effect, go to TOOLS -> SYSTEM and click the reboot button)

Using the example ports from steps 9 and 10 you have created a rule that will cause the router to listen on port 8080 from the internet.  When traffic to the WAN connection of the router comes in on port 8080, it will change the port to 8282 and forward that traffic to the specified IP address entered in step 6.

In Fig. 1, located in the Virtual Server List is a rule created for FTP on the public port 21 to private port 21 to internal IP address 192.168.0.190

Instructions for Gaming:

  1. Log into the routers administration pages (login instructions).
  2. Select the ADVANCED tab on the bar across the top of the page
  3. On the left side of the page select GAMING                                                                                                                                                                                   gaming1.png
  4. Make sure that the Enable check box is selected
  5. In the Name field, you can enter a descriptive name for the rule or you can select one of the predefined rules provided in the router.  There is a large list of predefined rules for various games and applications.
  6. In the IP Address field enter the LAN IP address of the machine hosting the application/server you wish to access from the internet.  The drop down list located next to this field displays machine names and IP address of connected machines if they received an IP address via DHCP.   NOTE: When setting up a Gaming rule, it is very important that the LAN IP address of the application/server machine never change.  Refer to the “How to setup a DHCP reservation” document for more information.
  7. In the UDP ports field, enter your ports into the text box to the right. Ex. 3724, 6112, 6881-6999
  8. In the TCP ports field, enter your ports into the text box to the right. Ex. 3724, 6112, 6881-6999
  9. In the Schedule: drop down list you can select a user defined schedule for a time duration of when this rule should allow/deny port forwarding.  For more information see “How to setup Schedules.”
  10. In the Inbound Filter: drop down list you can select a user defined inbound filter which will either allow or reject the port forward request by external IP address.  For more information see “How to setup Inbound Filters.”
  11. Click the Save button. You should now see the rule listed in the Gaming Rules section.
  12. Click Save Settings button at the top of the page. (NOTE: if the rule does not take effect, go to Tools -> System and click the reboot button)

Instructions for Special Applications

  1. Log into the routers administration pages (login instructions)
  2. Select the ADVANCED tab on the bar across the top of the page
  3. On the left side of the page select Special Applications                                                                                                                                                                                                           specialapp.png
  4. Make sure that the Enable check box is selected
  5. In the Name field, you can enter a descriptive name for the rule or you can select one of the predefined rules provided in the router.
  6. In the Trigger ports field, select TCP, UDP, or Both from the drop down list. Enter your ports into the text box to the right.  Ex. 2000-2100
  7. In the Firewall ports field, select TCP, UDP, or Both from the drop down list. Enter your ports into the text box to the right.   Ex. 2000-2100
  8. In the Schedule: drop down list you can select a user defined schedule for a time duration of when this rule should allow/deny port forwarding.  For more information see “How to setup Schedules.”
  9. Click the Update button, then click Save Setting at the top of the page.

Using the example ports from steps 6 and 7 you have created a rule that will cause the router to open ports 2000-2100 from the internet. 

Permalink

0 Comments - Leave a Comment

If you are unsure of CradlePoint Series or Model number, please click here.

This article was written based on firmware version 2.0.0.

Overview:

All computers/devices that connect to a network get an IP Address (an IP Address is a number used to identify the specific device. Think “street address”).  Computers can acquire this IP address one of two ways:

  1. They assign one to themselves.
  2. They can choose to get one from the router itself.

Every time a computer disconnects/reconnects to the router, or turned off/on a new IP address is assigned to it by the router.  Any port forwarding/remote access rule in the router is based on the computer’s IP address.  Using port forwarding/remote access rules the computer in question is required to be assigned the same IP address assigned from the router.  DCHP Reservations provide this functionality.

Things to do before configuration:

  1. Make sure the router firmware is up to date (to check your firmware version, please click this link).
  2. Make sure the device you want to set up the reservation for is turned on and connected to the router via Wi-Fi or Ethernet.
  3. You will need to know the CURRENT IP Address of the device you want to set up a reservation for.

How to set Up:

  1. Log into the routers administration page (login instructions).
  2. Click the “BASIC” tab at the top, then to “DCHP” on the gray sub-menu on the left.   User-added image
  3. Locate the ADD DCHP RESERVATION section.                                                              User-added image
  4. Check Enable and under Computer Name click on the drop down menu and select the name of the device.
  5. The IP address and MAC address field should auto-fill.
  6. Click Save.
  7. Scroll to the top and click Save Settings.

The CradlePoint router will now only issue the reserved IP to the device (MAC address) that is associated with the rule.

Permalink


If you are unsure of the CradlePoint Series or Model number, please click here.

This article was written based on firmware version 2.0.0.

Description: 

By default, the CradlePoint router will attempt to connect to the highest speed network available.  If using a 3G/4G WiMAX modem in an area where only a 3G signal is reliable or available the CradlePoint will disconnect from 3G and attempt, unsuccessfully, to connect to the 4G WiMAX network.  While this connection is attempted, the Internet will be unavailable through the modem and router. For this reason, it may be necessary to set the CradlePoint router to connect only to 3G to avoid the connection interruptions due to any possible 4G connection attempt.

3G/4G WiMAX modems from these carriers may require this change:

  • Sprint
  • Clear
  • BridgeMAXX
  • Time Warner Cable
  • Comcast
  • Xohm
  • Rover

Directions:

It is highly recommended to update to the CradlePoint routers most recent firmware and WiMAX driver version,  How to Update Firmware.

  1. Log into the routers administration page (login instructions).
  2. Click the MODEM tab then select SETTINGS from the gray sub-menu on the left.                                        User-added image
  3. Locate the MODEM SPECIFIC SETTINGS section then select the Modem Interface drop-down to the slot that your modem is connected to.                                                                                                                                User-added image
  4. Locate the Dual WiMAX/3G Settings sub-section and change Connect Mode to 3G Only                               User-added image
  5. Click Save Settings at the top of the page then click Reboot Now when prompted.                                           User-added image

After the router reboots, only the 3G connection will connect, and the 4G connection will be disengaged.

Permalink


Sierra Wireless Products (44)

View category →

Cloud services can be used for applications built around Software as a Service (SaaS), Platform as a Service (PaaS), or Infrastructure as a Service (IaaS).

Sierra Wireless AirLink® has a platform called AirVantage. AirVantage has a powerful set of M2M application development tools and an open web services application programming interface (API) which can be leveraged in conjunction with ALEOS Application Framework (AAF) running inside of Sierra Wireless AirLink® GX-400 and GX-440 intelligent wireless gateways. USAT Corp is a premier partner of Sierra Wireless authorized to to optimize AAF coding in Lua, so that the devices are shipped live to the field during with device deployment. USAT’s DevProv+ suite of services ensures maximum success with a deployment of equipment utilizing the AirVantage platform.

AirVantage can also function as a device management backbone, communicating directly with devices in the field through the AirVantage Ready Agent. This also provides advanced asset management features to issue commands to assets or collect asset data and events. AirVantage Platform also includes embedded and application development tools to expedite time to market. The eclipse based programming tools are tied to the AirVantage Ready Agent as well as the services platform in order to create a comprehensive M2M development environment. This environment includes embedded M2M modeling tools and application simulation tools.

Another facet of AirVantage is AirVantage Smart Automation. This platform simplifies the connection to industrial equipment and the creation of embedded business logic without programming. This enables new services such as tiered monitoring and maintenance, demand response applications, and time- or location-based equipment usage models.

Smart Automation leverages the AirVantage Platform to facilitate subscription, device and asset management through a remote M2M application. The Smart Automation extension integrates these capabilities with industrial control systems. AirVantage Smart Automation makes it easy to set up custom business logic to collect, sort, prioritize, send and store data without the need for programming. Existing backend systems can be integrated or new M2M applications can be implemented using standard web services APIs.

Permalink


The Sierra Wireless LS300 is designed to a very compact form factor while still providing serial, USB, and Ethernet connections, along with full support for ALEOS and ALEOS Application Framework (AAF).
As of the LS-300 product release the space requirements for 4G-LTE radio modules will not allow the LS300 to support 4G-LTE data connectivity. Currently the Sierra Wireless AirLink GX-440 M2M modem supports 4G-LTE through major carriers including Verizon, Sprint and AT&T. Note that while the LS-400 does not currently support 4G-LTE or 4G Long Term Evolution it does support the HSPA+ standard which is marketed by AT&T and T-Mobile in the US as “4G” and used by worldwide GSM carriers including Vodafone.

Permalink


This functionality only applies to devices using MSCI to communicate with ALMS:

  • MP, RV, GX, LS and ES devices from ALEOS firmware version 4.4.0 and onwards
  • Raven, MP, PintPoint on firmware version 4.0.11 or later

For devices that communicate with ALMS using LWM2M, the password field is no longer required. The M3DA password will still be required for AAF applications.

Prerequisite: Initialize the value

This one-time action is necessary to initialize the current password value set on the device on the AirVantage side. To initialize the ACEmanager value for already registered systems, you will need to:

  1. Select a system and click on Edit in the action bar or directly in the Actions column.
  2. In the Applications section, click on the icon  to edit the credentials for the ALEOS firmware.
  3. Set the ACEmanager password (in MSCI section). You can also set the M3DA password in the specific section. Default values when device comes out of factory are 12345.

Note: Initializing the values is only required for gateways commuicating using MSCI, and is not required if your gateway is configured with LWM2M.

As an alternative, you can also set the password at Registration, in the Advanced section as described below:

Change the ACEmanager password for one device

  1. Select your system and dive into the system configuration.
  2. Click on edit. Select the ‘ACEmanager password’ setting.
  3. Enter the new value and click on Apply
  4. At next device heartbeat, the password will be configured on the device.

Change the ACEmanager password for a fleet of devices

Go into Monitor system list and select all the devices you want to update the password on by filtering to the correct devices and using the “select all” checkbox. In the action bar, select the ‘Apply setting (CSV)’ item from the menu.

  1. In the dialog box that opens the first step will be to define a unique identifier to be used to provide the list of systems for which you want to change names. Let’s choose the Serial Number.
  2. Choose the version of firmware (application) that is used on the devices. All selected devices should be running the same version of ALEOS.
  3. The second field under ‘Setting’ is the value you want to change on each device. In this case, we want to change the ACEmanager password, so search for and select the ‘ACEmanager password’ setting.
  4. You will have to provide a .csv file with the values you want to apply to each device. Select ‘Generate’, and the system will generate this .csv file with the existing information for each device. Refer to the screenshot below for an example. In a tool that can edit .csv files, update the password field for each device as required. Save the updated file.
  5. Click the ‘Select a CSV…’ button and upload the updated .csv file to the system.
  6. Click on ‘Apply setting (CSV)’. For each device, at the next heartbeat, the ACEmanager password will be updated on the device.

ACEmanager password is considered sensitive information and therefore we highly recommend to configure each of your devices with a unique password.

While these instructions have been tailored for updating the ACEmanager password, any ALEOS setting can be updated in this way.

Permalink


Yes, the Sierra Wireless AirLink® LS300 is RoHS Certified. The M2M modem is branded with an RoHS sticker on the modem, and USAT has a certificate of compliance on file from Sierra Wireless for the AirLink® LS300 RoHS Certification (available on request). The certificate is a DECLARATION OF EUROPEAN UNION RoHS COMPLIANT PRODUCT, and that Sierra Wireless Inc certifies that the products identified below to be “”RoHS Compliant””:

Sierra Wireless AirLink® LS300 Modem

Restriction of Hazard Substances (or RoHS) compliant defines that the product conforms to the requirements of the European Union’s restriction on use of hazardous substances in electrical and electronics equipment’s directive,2002/95/EC (RoHS directive) which limits the content of the following elements:

  • Lead (Pb)
  • Mercury (Hg)
  • Cadmium (Cd)
  • Hexavalent Chromium (Cr6+)
  • Polybrominated biphenyls (PBB)
  • Polybrominated diphenyl ethers (PBDE)

Hexavalent chromium is used in primers, chrome coatings and chrome plating.

PBB and PBDE are used in plastics as flame retardants.

The RoHS directive is with respect to any homogenous components used in the product as shipped by Sierra Wireless, in its entirety.

The RoHS directive is vitally important for USAT’s clients in the European Union, global carrier partners such as Vodafone and AT&T, as well as North American enterprises with sales and offices in Europe. RoHS is also an environmental sustainability directive which USAT is proud that our suppliers, such as Sierra Wireless, support.

Permalink


Yes. The AirLink GX400 can be configured to monitor the input, respond to specific types of events, and even trigger digital output. The device can also be configured to change its power mode in order to conserve power. These features can be configured to your needs.

The AirLink GX400 is equipped with an I/O port interface which includes 1 low power timer enable input and 1 digital I/O. These may be connected to sensors and switches to monitor status and remotely control equipment. AirLink GX400 board supports a low power timer enable input pin and a digital I/O pin which are connected to the CPU processor. The I/O signal comes in from the power connector, through a PolySwitch resettable fuse, and ties into the CPU pins with protection circuitry.

Digital Input

Digital Input can be used in two different modes: the switch mode or the voltage sensing mode.

The switch mode senses contact closures. The digital input can report either an open or closed state, and can be wired to a ground signal via a switch. When the switch is open, the input reads “”3.3V””. When the switch is closed, the input reads “”OV””.

Examples of using the input with a switch to ground:

  • When a door or other latch is opened or closed
  • Counting pulses or other electronic events
  • When a gauge reaches a certain point
  • When a container fills or empties
  • When a switch or valve is opened or closed
  • When the tow bar is raised or lowered
  • Connected to a sensor, the level of fuel in a vehicle
  • When the trunk of a vehicle is opened or closed
  • When the ignition is turned on or off

Digital Output

Digital Output of open collector design is capable of driving an external device such as a pull-up resistor or relay. As an example, a relay could be connected between the output pin and an external voltage. The voltage on the relay cannot exceed 30V. The digital output pin can handle up to 150mA.

Examples of using the digital output with an external relay or pull-up resistor:

  • Setting off an alarm or siren
  • Triggering a process to start on another device
  • Opening or closing a valve or switch
  • Locking or unlocking a door. Inputt
  • Turning a light on or off
  • Opening the vehicle’s trunk or doors

Permalink


Digi Products (3)

View category →

Firewall concerns:
Firewalls (and the IT security people that maintain them) are generally concerned with protecting a location’s Local Area Network from unauthorized use – both from traffic coming at the network from the outside world, and traffic from within the local area network going outward.  A Remote Management-capable Digi product falls into the latter category, because the Digi device creates an outbound TCP socket connection to the Device Cloud or Remote Manager server.  This  EDP (easy device protocol) socket connection is tunnel through which data gets pushed from your Gateway to to the Device Cloud, so that data can be accessed from anywhere in the world.

The following article describes:

  • The IP socket connections used when a Digi RF Gateway,TransPort Router, or edp-capable device (using Digi Cloud Connector) makes a Remote Management connection to Device Cloud or Remote Manager
  • How to determine the IP address in use for a given Device Cloud or Remote Manager DNS name

Locations where it is likely that Firewall Rules will be needed:

Those who are trying to connect to Device Cloud or Remote Manager from a location which has strict outbound firewall rules will especially need the guidance found within this article.  Some likely examples for this type of network security environment include:  Government offices/buildings and institutions, Schools, Universities, and some Businesses (especially ones that do government contract work).

 

What network port(s) does a Gateway or Connect-capable device use to connect to Device Cloud?

By default, the TCP and/or UDP port(s) your Device Cloud-capable Gateway or device uses to connect with Device Cloud will depend in part on the age/default configuration of your Gateway, the device’s configuration, as well as the particular model.

TCP Port 3197:  The outbound EDP/non-SSL (non-secure) socket connection from NDS-based products like the ConnectPort X2 / X4 / X5 / X8 Gateways, and ERT/Ethernet Gateway (especially if the product hasolder firmware), which may still be configured to create an un-encrypted Device Cloud socket connection.

Note:  If possible, the firmware of older products should be updated so that the Device Cloud configuration settings can changed to use of SSL socket connections into the Device Cloud instead (see next entry below).

TCP Port 3199:   The outbound EDP/SSL (secure) socket connection from NDS-based products like the ConnectPort X2 / X4 / X5 / X8 Gateways, and ERT/Ethernet Gateway with newer firmware which are configured to create a secure SSL socket connection into Device Cloud.  Required on ALL Linux-based Gateways, examples:  XBee Gateway ZB andConnectPort X2e for Smart Energy.  Can also be required if the Device Cloud account is configured to accept SSL connections only (new Device Cloud option as of version 2.16)

UDP Port 53:  Outbound DNS (Domain Name Service) name recognition service, i.e. translates the my.devicecloud.com name for Device Cloud connectivity.

Note:  DNS service is not a requirement.  If access to DNS service is not allowed or possible from your network, the device’s remote connectivity address would need to use the IP address of my.devicecloud.com (52.73.23.137), rather than the DNS name itself (see below under What IP address is needed for outbound Firewall rule(s)? for more details).

UDP Port 123:  The outbound socket connection to an NTP (time) server is required for ALL Linux-based Gateways such as the XBee Gateway and ConnectPort X2e, as well as  gateways and devices configured for NTP time management.

Important Note for all XBee and ConnectPort X2e Gateways (and Gateways configured for NTP Time Management)

The XBee Gateway and ConnectPort X2e are Linux-based gateways which require outbound access to UDP port 123 (NTP), in order to generate the secure (SSL) TCP socket connection into Device Cloud.  Any Gateways which are configured for NTP time management will have this requirement as well, since the Gateway connects to an NTP server in order to to keep an accurate date/time.

If your XBee (or CP-X2e) Gateway is added to your Device Cloud account but never shows up in a Connected state, check to ensure that outbound NTP access is available for the Gateway through your local network Firewall.  ConnectPort X2 and X4 gateways would still connect to Device Cloud (assuming TCP port 3199 isn’t blocked), but the Gateway might show an epoch 1970-based date/time if no other Time Sources are configured.
What IP address is needed for outbound Firewall rule(s)?

The best way to determine that is to do an nslookup of the DNS name for the Remote Management server you want your device(s) to connect to.  As of the date of this article (6/16/2015), here is how this looked from my Windows 7 commandline (Start – Run – CMD) prompt when doing nslookup of our various Remote Management and NTP ring servers:

Digi Device Cloud and Remote Manager device connectivity address:

C:\>nslookup my.devicecloud.com

Name:    my.devicecloud.com
Address:  52.73.23.137

Past Device Cloud connectivity addresses which may still be in use on devices (all device configurations should be updated to use of the my.devicecloud.com address, then re-connected to the server at the new address):

devicecloud.digi.com
login.etherios.com
my.idigi.com
app.idigi.com

devicecloud-uk.digi.com
login.etherios.co.uk
my.idigi.co.uk

Digi Primary NTP Time Server Ring addresses:

C:\>nslookup time.devicecloud.com

Name:     time.devicecloud.com
Addresses:  52.25.29.129, 52.2.40.158

Secondary/Tertiary NTP Time Server addresses for pool usage:

C:\>nslookup 0.time.devicecloud.com

Name:     0.time.devicecloud.com
Addresses:  52.2.40.158

C:\>nslookup 1.time.devicecloud.com

Name:     1.time.devicecloud.com
Addresses:  52.25.29.129

Deprecated NTP/Time server addresses which may still be in use on devices (all devices should be updated to use time.devicecloud.com within their configuration):

time.digi.com
time.etherios.com

time.etherios.co.uk
0.idigi.pool.ntp.org
1.idigi.pool.ntp.org
2.idigi.pool.ntp.org

Making the Firewall Rules:

If the IP address of the DNS name ever changes (before this article is updated to reflect it), a Windows CLI command can be used to determine the IP address of our server:

nslookup <DNS name of server>

The Name and Address fields will be the DNS name and IP address for the Remote Management or Time server listed.  Your firewall rule will need to allow access for the appropriate network port used based on your Gateway’s Device Management configuration, as well as UDP port 123 if NTP Time Management is in use.

Important Note regarding deprecated DNS names:

If your Gateway is configured to use an idigi.* or etherios.* DNS name, it should be re-configured to use the my.devicecloud.com url at your earliest convenience. You will need to create firewall rules for all IP addresses/ports used, for all Remote Management and Time (NTP) DNS server names used within your device.

Permalink


Cloud services can be used for applications built around Software as a Service (SaaS), Platform as a Service (PaaS), or Infrastructure as a Service (IaaS).

Digi International has a platform called iDigi. iDigi is a cloud platform for both device network management and for data management. The iDigi Device Cloud is designed using a high-availability architecture, with redundancy and failover characteristics. It is a highly scalable system that can host single units to tens of thousands of Digi devices. It also has web services APIs for secure application integration and data messaging. iDigi device clouds are located in Chicago and in London and you can select to which cloud your data is subscribed.

Device management also include the ability to send commands to remote devices. Standard web service calls are available to manage traditional device settings. An optional Server Command Interface / Remote Command Interface (SCI/RCI) mechanism is available for any custom device or application commands that may be required.

iDigi Manager Pro is a pay-as-you-go model, starting at $1.59 per registered device, per month. Sending data to and from the iDigi Device Cloud is billed on a transactional basis and are available at different usage levels. Data is managed through iDigi, which means that iDigi provides a collection point of data. iDigi is not a (long-term) data storage solution–Digi Dia data is stored for 1 day, and iDigi files are stored for 7 days.

Permalink


Unlike the ConnectPort WAN, the serial ports on the standard builds of the Digi Transport line are DTE not DCE serial, this means that a null modem cable should be used instead of a cross-over cable.

Null modem is a communication method to connect two DTEs (computer, terminal, printer etc.) directly using an RS-232 serial cable. The name stems from the historical use of the RS-232 cable to connect two teleprinter devices to modems in order to communicate with one another; null modem communication was possible by instead using RS-232 to connect the teleprinters directly to one another.

Permalink


Digi Transport (18)

View category →

There are five main methods by which new firmware can be loaded onto Digi TransPort or Sarian routers: Digi Device Cloud (DC), Web interface, FlashWriter, S/FTP and USB flash drive.

Note that, because of changes in the firmware, the procedure for loading firmware has changed for the S/FTP and USB flash drive procedures beginning at firmware version 5.2.9.13.  Please note the different procedures when using these methods.

1. Digi Device Cloud / Remote Manager 2.0

After setting up your account on DC and configuring your TransPort to connect to DC, log into your DC account and add the TransPort if it is not already added. You will need to download the correct firmware to your PC. The “FTP” version of the firmware file is needed. (See the Web interface method in #2.) Right-click on the TransPort and select Firmware, then Update Firmware. Select Browse and navigate to the firmware file. Select the Update Firmware button. Wait while the process is completed.
Scheduled firmware updates using DC. In DC go to Schedules. Click on New Schedule. On the Device tab there is the option for Gateway Firmware Update. Click on it. Now a window will pop up with a ‘Browse’ to button. Click on it and browse to where you have the file saved on your desktop. You’ll also need to give a ‘Description’ to the operation before you can proceed. The Description field is at the top of the New Schedule window in yellow.

Then hit the Schedule button in the lower right hand corner. A new window will pop up showing you all the devices in your account. Pick which ones you want the firmware to be loaded too and on the left hand side pick the Future option and then the time/date you want it to happen.

That’s it. You can monitor the progress of the operation in the Operations window right next to the Schedules window. You have to keep hitting the refresh button to update though. If you’ve chosen multiple units to upload then double click on the operation and you’ll see which units completed and which ones, if any, failed.

2. Web interface method

The Web interface method of upgrading firmware can be used locally or remotely. It is available only in Digi TransPort firmware versions 5.149 and later. The method involves clicking the “Update Firmware” option in the Web interface, browsing to a local or remote zip file containing the firmware, then clicking the “Update” button to start the automated update process. Only individual firmware files are replaced during the upgrade, so when a unit is upgraded via the Web interface method its current saved configuration will be retained.
How to upgrade the firmware on a Digi TransPort router using the Web interface

3. FlashWriter method

The FlashWriter method of upgrading firmware can be used only locally, i.e. a serial and/or Ethernet connection between your PC and the router to be upgraded is required. With the FlashWriter method the entire system flash will be overwritten, which means that any configuration will be lost.
How to upgrade the firmware on a Digi TransPort router using Flashwriter – Serial Procedure
How to upgrade the firmware on a Digi TransPort router using Flashwriter – Ethernet Method

4. S/FTP method

The SFTP or FTP method of upgrading firmware can be used locally or remotely. A little more background knowledge is required in order to use the S/FTP method. It is assumed that the user is familiar with the operation of S/FTP client software and Telnet or SSH client software. Only individual firmware files are replaced during the upgrade, so when a unit is upgraded via S/FTP its current saved configuration will be retained.
How to upgrade the firmware on a Digi TransPort router using FTP to a firmware version earlier than 5.2.9.13
How to upgrade the firmware on a Digi TransPort router using FTP to firmware version 5.2.9.13 or later

5. USB flash drive method

The USB flash drive method of upgrading firmware can be used only locally. The USB flash drive method is especially useful for upgrading routers during a site visit. Once the USB drive is configured the update process involves simply inserting the USB drive into the front of the router, waiting for a few minutes for a flashing LED sequence to indicate that the upgrade is complete, removing the USB drive then rebooting the router (for example by power-cycling it). There are two methods of upgrading firmware with a USB flash drive:

Method A) Loading a complete flash memory image onto the router, in the form of a ‘.all file’ – this is similar to the FlashWriter method, in that the entire system flash will be overwritten and any existing configuration will be lost.

Method B) Upgrading individual firmware files – this is similar to the FTP or Web interface methods, in that since only individual firmware files are updated, any current saved configuration will be retained.
How to upgrade the firmware on a Digi TransPort router using a USB flash drive to a firmware version earlier than 5.2.9.13
How to upgrade the firmware on a Digi TransPort router using a USB flash drive to firmware version 5.2.9.13 or later

Permalink


When using a Digi TransPort Router with a Public SIM card, the issue of reaching this device by it’s IP address happens as most/all providers will dynamically assign IP addresses that will change at every connection / reconnection.

To overcome this problem, it is possible to use a Dynamic DNS host configured in the router. The Router will update the service provider with it’s current IP Address and / or any IP Address changes. This will allow the device to be reached without knowing it’s currently assigned IP Address

Digi TransPort Routers currently supports 3 service providers type :
– DynDNS.org
– No-IP.org
– Other

In this example, No-IP.org will be used as they allow registration of free Dynamic DNS hosts.

Before you can successfully register the IP address of your router with a service provider, you must create an account on their web site. In this example, no-ip will be used.

1- Sign-UP for a Free Account on No-IP

Go to https://www.noip.com/sign-up and sign-up for a free DDNS Account. When registering, the “hostname” will be the name used to reach your device, for example: “digitesteu.ddns.net

User-added image

2- Configure Digi TransPort DDNS settings

Open a web browser to the IP Address of the Digi TransPort Routers and navigate to Configuration – Network > Dynamic DNS

– Select the Service Provider, in this example: No-IP
– Enter the Host and Domain Name previously chosen during registration at the service provider, in this example: digitesteu.ddns.net
– Destination port can be left to 0. This will by default use HTTP port 80.
– DynDNS User Name is the username chosen during registration.
– DynDNS Password and Confirm Password is the password chosen during registration
– When is which interface to use to send DDNS updates. By default, use default route.

Click Apply and Save Configuration

User-added image

3- Verify DDNS update

3.1 – On Digi TransPort Router

Navigate to Management > Event Log. A line should show the DynDNS update success :

12:47:01, 10 Mar 2015,DynDNS 0 host 0 updated: good 90.121.121.151

3.2 – On No-IP.org website

Navigate to https://www.noip.com/members/dns/ and login with the previously created account credentials.

Under Manage Hosts, the domain name should be displayed with the current Digi TransPort’s Routers IP.

User-added image

4- Test Connection

Now that the DDNS update is done, open a web browser to the selected domain name (in this example : digitesteu.ddns.net). The Web interface of the Digi TransPort Router should be displayed

User-added image

Permalink


Gobi 2000/3000 Sprint Provisioning
Overview
This document is intended for Gobi Transport units over the Sprint network.  The purpose is to quickly walk you through running the Gobi Carrier Wizard, how to provision the device for Sprint networks.  It also highlights items to look at and how to test the unit.

Assumptions
This guide assumes that you have a PC that is able to reach the TransPort through the Ethernet interface to gain access to the WebUI for configuration purposes.

Information You Might Need
If possible, please try to gather the following information from Sprint as it might be necessary for possible issues:
MSL – Master Subsidiary Lock is required to allow the PTN and the MSID to be programmed
PTN – The phone number, which should contain 10 digits
MSID – The Mobile Station Identity or MIN, again 10 digits

Running the Gobi Carrier Wizard
The first thing that will need to do be done is run the Gobi Carrier Wizard to enable the device for Sprint. The following steps will guide you through this process:

1) Log into the WebUI through the Ethernet interface. (Default IP address is 192.168.1.1)

2) Once in the WebUI, click on Wizards on the upper-left hand side, as shown in the screenshot below:
User-added image

3) Click on the GOBI Carrier Wizard, and then click Next, as shown in the screenshot below:
User-added image
4) Choose Sprint, and click Next, as shown below:
User-added image

5) On the next page, you will see a line that says “Save configuration changes here”, with the “here” being blue in color and underlined. Click the ‘here’ link and then click Save on the next screen. Reboot the device after saving.

6) After the device reboots, log back into the WebUI.

7) Navigate to Configuration > Network > Interfaces > Mobile > CDMA Provisioning.

8) Under the section titled Automatic Provisioning, click the Start button. DO NOT fill in any of the 3 parameters unless told to by Digi.  DO NOT fill out anything under Manual Provisioning.
User-added image

9) This process will take ~2 minutes to complete. Once the process completes, a message at the top of the page will indicate if it has either been successful or failed to provision. If successful, click the Reboot link and reboot the device.  If failed, try provisioning again.  Please email Digi Technical Support with the debug.txt file (please see “When contacting Digi Technical Support” below) if the failure continues.

Once the unit is provisioned, it could take another minute or so before it establishes an IP address.

Indicators, WebUI

LED Displays

For the WR41 & WR44
W-WAN NET
Will illuminate steady if the unit is able to log on to the Sprint mobile network.

W-WAN SIM
This LED should not light up since you do not a SIM for a Sprint account.

W-WAN DAT
Represents data passing to and from the network.

Signal Strength
Here is a guide for the signal strength:

  • -113 dBm or less (0 LED) -> effectively no signal
  • -112 dBm to –87 dBm (1 LED) -> weak signal
  • -86 dBm to –71 dBm (2 LEDs) -> medium strength signal
  • -70 dBm or greater (3 LEDs) -> strong signal

The minimum recommended strength indication is 2 LEDs. If you have no or 1 LEDs lit, it is recommended that you fit an external antenna to the unit.

For the WR21
Service
Illuminates steady when there is a network connection to the WWAN interface and flashes when data is transmitted or received.

WWAN
Flashes to show which network mode the unit is operating in:
Off – no service
1 blink – GPRS mode
2 blinks – EDGE mode
3 blinks – UMTS mode
4 blinks – HSDPA mode
5 blinks – HSUPA mode
On steady – CDMA mode

Strength
Here is a guide for the signal strength:

  • -113 dBm or less (0 LED) -> effectively no signal
  • -112 dBm to –87 dBm (1 LED) -> weak signal
  • -86 dBm to –71 dBm (2 LEDs) -> medium strength signal
  • -70 dBm or greater (3 LEDs) -> strong signal

The minimum recommended strength indication is 2 LEDs. If you have no or 1 LEDs lit, it is recommended that you fit an external antenna to the unit.

WebUI

Locating the Mobile IP Address
On the Home page, you should see the Mobile IP address under PPP1 (W-WAN (CDMA)).

NOTE: If you get an IP address of 120.x.x.x, this is a false mobile IP address.  Please see the Troubleshooting section of this document.
User-added image

Under Management > Network Status > Interfaces > Mobile
User-added image

NOTE:  Use the above screenshot as a reference for the below information.

Mobile Connection  

Registration Status
This is the registration status of the mobile module with respect to the cellular network.
Ideally, it will show up as registered.

Signal Strength
The signal strength in dBm being received by the mobile module.
Here is a guide for the signal strength:

  • -113 dBm or less (0 LED) -> effectively no signal
  • -112 dBm to –87 dBm (1 LED) -> weak signal
  • -86 dBm to –71 dBm (2 LEDs) -> medium strength signal
  • -70 dBm or greater (3 LEDs) -> strong signal

The minimum recommended strength indication is 2 LEDs. If you have no or 1 LEDs lit, it is recommended that you fit a high-gain external antenna to the unit.

Mobile Statistics
IP Address
The IP address of the mobile interface.

Primary DNS Address / Secondary DNS Address
The primary and secondary DNS addresses used by the mobile interface

Data Received
The number of data bytes that have been received on the mobile interface whilst it has been connected.

Data Sent
The number of data bytes that have been sent on the mobile interface whilst it has been connected.

Mobile Information  
Current system ID
The current system ID reported by the mobile module.

Current network ID
The current network ID reported by the mobile module.

Network
The current network reported by the mobile module.

Signal strength 1xRTT
The signal strength in dBm being received by the mobile module from 1xRTT networks.

Signal strength EVDO
The signal strength in dBm being received by the mobile module from EVDO networks.

Manufacturer
The manufacturer of the mobile module.  For a Gobi module, you should see either Huawei Incorporated or Qualcomm Incorporated.

Model
The model of the mobile module.  Examples for the Gobi would be Huawei EM680, Qualcomm Gobi 2000, Qualcomm Gobi 3000.

MDN
The Mobile Directory Number (MDN) of the mobile module.

MIN
The Mobile Identification Number (MIN) of the mobile module.

ESN
The Electronic Serial Number (ESN) of the mobile module.

MEID
The Mobile Equipment Identifier (MEID) of the mobile module.

Firmware
The firmware running on mobile module.

Bootcode
The bootcode firmware running on the mobile module.

Hardware version
The hardware version of the mobile module.

Registration State
See Registration Status.

Roaming status
The current roaming status of the mobile module.

Service capabilities
EVDO, CDMA 1x, or both

Radio band
1900 MHz for Sprint.

Channel
The transmission channel in use.  25 for Sprint.

Preferred system
Specifies what you configured it for: CDMA, EVDO, or Auto.  You can set this under Configuration > Network > Interfaces > Mobile > Advanced.

PRL version
The version of the Preferred Roaming List (PRL) loaded on the mobile module.

Activation status
The activation state of the mobile module. It can be of the following:

  • 0 – Not activated
  • 1 – Activated

Raising and Lowering the Cellular Link
Under Management > Connections > PPP Connections > PPP 1 – W-WAN, you should see the Mobile IP Address, the Primary and Secondary DNS Address, as well as buttons to Drop or Raise the link.
NOTE: If you get an IP address of 120.x.x.x, this is a false mobile IP address.  Please see the Troubleshooting section of this document.
User-added image

Locating the Event Log

Under Management > Event Log
This page displays the current contents of the event log on the router.  This log records events throughout the Digi device’s system including cellular information.  Some of this cellular information you might see would be status codes, error codes, signal strengths, tower locations, & service available.
Note: The newest information is on top of this file.

Testing
Once you have set up the mobile settings on your unit and you see a mobile IP address, there are a couple of quick tests you can do to ensure your device is working.

Ping test

Unfortunately, you cannot do a ping test on the Sprint Network.  Sprint blocks this port (please see Sprint EVDO Blocked Ports under Troubleshooting, below).

Accessing the Internet

If you have a laptop or computer directly connected to your Transport, you can try opening a browser and accessing the Internet (for example ‘http://www.digi.com’).

NOTE: In order for this step to be a valid test, you must ensure you do not have another source to the Internet, such as being connected to your company’s network either via Ethernet or over Wi-Fi.

If this fails, please email Digi Technical Support with the debug.txt file (please see “When contacting Digi Technical Support” below).

Access the Transport Remotely

With Sprint as a cellular provider, they block certain ports.  A complete list of these blocked ports may be found in the Troubleshooting section below.  One of those ports is port 80, which is HTTP, which is the protocol normally used to access the Internet. With Sprint blocking this port, a user will no longer be able to remote into the Transport by simply entering the address (i.e. http://x.x.x.x where the x’s are representing the mobile IP address of the Transport).  Locally, the user will still have access to it using the local IP address.

In order to resolve the issue of getting into the Transport using the mobile IP address, there are two methods.

  1. With the Transport, there are two services for entering the Web GUI, HTTP or HTTPS.  Sprint blocks port 80, which is HTTP, but they do not block port 443, which is HTTPS.  To change to HTTPS, go to Configuration > Network > Network Services, then click the “Enable Secure Web Server” button.  You will then click the Apply button and then the Save.  Then click the Save All button.  Note that you will lose your connection.  At this point, in order to access either remotely or locally, you will need to specify “https” (i.e. https://x.x.x.x where the x’s are representing your local or remote address of the Transport).
  2. The HTTP service, in the Transport, besides the normal port 80, also accepts port 8080.  This means that you can keep the default settings and then enter the unit remotely specifying port 8080 (i.e. http://x.x.x.x:8080 where the x’s are representing the mobile IP address of the transport).  Note that locally you may still enter the WebUI of the Transport as you normally would (http://x.x.x.x where the x’s are representing the local IP address of the Transport).  To change to HTTP (which is the default setting), go to Configuration > Network > Network Services, then click the “Enable Web Server” button.  You will then click the Apply button and then the Save.  Then click the Save All button.

If you have a mobile terminated account, you should be able to access the Transport remotely.  Find a laptop or PC that has Internet access (outside of the Transport), open a browser, and specify, using https, the mobile IP address of the Transport (i.e. https://166.55.x.x).

If this fails, please verify that you have Web Server enabled (Configuration > Network > Network Services).  Having IP Forwarding (Configuration > Network > IP Routing/Forwarding > IP Port Forwarding/Static NAT Mapping) or IP Passthrough (Configuration > Network > IP Passthrough) enabled could affect these results as well.  Otherwise, if you cannot access your Transport remotely, the issue could be that you have a mobile originated account or a private account.  You should check this with your provider.

Mobile Originated vs. Mobile Terminated

Mobile Origination – Allows for outbound data to pass through the Digi and receive responses from the data request, but it does not allow for data originating from the Internet to pass through the Digi or to devices beyond it.

Mobile Termination – Allows for 2-way communication of data, where data from the Internet can reach the Digi and beyond, and data from the Digi can go to the Internet.

Troubleshooting
Ensure you are on the latest firmware
Updating your firmware may resolve your issue as well as enhancements to both your Transport and traces for troubleshooting.

  1. To check your firmware, go to Administration > System Information and note your Firmware Version
  2. Compare the firmware version to our latest release by going to www.digi.com > Support > Firmware Updates.
  3. Enter your Transport Model (i.e. WR21) in the field and then click on your particular model.
  4. It should bring you to a page for your product.  Choose the fimrware for the type of upgrade you will performing, either via FTP (WebUI) or FlashWriter, from the options on the page and save the file to your PC.
  5. Please follow “TransPort Firmware Upgrade Instructions” that is available under the General Firmware page listed above.

False Mobile IP Address Sprint units
120.x.x.x – If you see an IP address in the 120.x.x.x network for your mobile IP address, you should note that this is a false IP address.  Please attempt to re-provision your Transport.  If you still receive a false IP address, please provide the debug.txt file to Tech Support (please see “When contacting Digi Technical Support” below).  You may also need to contact Sprint, as well.

Sprint EVDO Blocked Ports
80/tcp filtered http
113/tcp filtered auth
135/tcp filtered msrpc
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
445/tcp filtered microsoft-ds
559/tcp filtered teedtap
901/tcp filtered samba-swat
1022/tcp filtered unknown
1023/tcp filtered netvenuechat
1025/tcp filtered NFS-or-IIS
1433/tcp filtered ms-sql-s
3128/tcp filtered squid-http
3306/tcp filtered mysql
4000/tcp filtered remoteanything
4899/tcp filtered radmin
5000/tcp filtered UPnP
17300/tcp filtered kuang2
27374/tcp filtered subseven

Permalink


1)  Log into the WebUI, and navigate to Configuration – Network > IP Routing/Forwarding > IP Port Forwarding/Static NAT Mappings.

NOTE:  Use the below screenshot as a reference for steps 2-5

User-added image

2)  Fill in the Minimum and Maximum TCP/UDP ports the TransPort should listen on.  These can be the same port if only 1 port is being passed through, or a range of multiple ports if those are needed to pass through.

3)  Fill in the IP address of the LAN device the connection needs to get to.

4)  Fill in the TCP/UDP port of the LAN device the connection needs to get to.  Click Add when finished.

5)  Click Apply and Save the settings.

NOTE:  A reboot may be necessary at this point in time for the rules to take effect.

6)  Navigate to Configuration – Network > Interfaces > Mobile.

7)  Expand Mobile Settings, and change the NAT option to IP address and Port as shown in the screenshot below:

User-added image

8)  Click Apply and Save the changes.

Permalink


For most model TransPorts, the PPP 1 interface is the default cellular WAN interface.  If needed, an Ethernet interface may be used instead for WAN connectivity, for example, to connect to a separate non-cellular modem via Ethernet for Internet access.

Generally, all that needs to be done for this to work is to change the Interface of the Default Route to the Ethernet port and to enable NAT on the Ethernet WAN port.

To change the Interface of the Default Route to the Ethernet port, from the TransPort’s web interface, navigate to Configuration – Network > IP Routing/Forwarding > Static Routes > Default Route 0, and then change the “Default Route 0” Interface from PPP 1 (or whatever it currently is) to the appropriate Ethernet port, for example Ethernet 0.

For the vast majority of applications, enable NAT on the Ethernet WAN port.  In this “Ethernet as a WAN” scenario, NAT should only be disabled on the Ethernet WAN port in certain circumstances, for example, when using a private APN (and even then it may still need to be enabled).  To enable NAT on the Ethernet WAN port from the TransPort’s web interface, navigate to Configuration – Network > Interfaces > Ethernet > ETH x* > Advanced, and then check “Enable NAT on this interface”.  *Select the appropriate Ethernet port that’s being used for WAN (usually Eth 0 but not always).  Optionally check the option to enable NAT for “IP address and Port” instead of just “IP address” to avoid any potential Port Forwarding issues in the future.

Notes:

  • If the TransPort has multiple Ethernet ports, consider either enabling Port Isolate mode or utilizing Hub Groups.  Using an Ethernet port as the WAN interface will work without enabling Port Isolate mode or utilizing Hub Groups, but there are considerations.  If using the default Hub Mode instead of Port Isolate mode, traffic will route out of a single Ethernet port, for example Eth 0, and respond on that same port.
    • To enable Port Isolate mode from the TransPort’s web interface, navigate to Configuration – Network > Interfaces > Ethernet > ETH 0 > Advanced, and then click the “Switch to Port Isolate mode” button, unless the device is already in Port Isolate mode.
    • A Hub Group can alternatively be utilized by putting the WAN Ethernet port (Eth 0 for example) in a Hub Group that’s separate than the other ports.
    • For more information about Hub Mode vs. Port Isolate mode, and Hub Groups, please review the TransPort User Guide:  http://ftp1.digi.com/support/documentation/90001019.pdf
  • Be sure the TransPort’s Ethernet IPv4 port settings are configured correctly, to match the Ethernet-attached device.
  • Be sure to Apply any configuration changes, save the configuration, and then Reboot the TransPort.
  • WAN failover between Ethernet and Cellular may also be desired.  Please reference Quick Note 53 for information on this type of failover scenario.

Permalink


Digi Remote Manager (5)

View category →

Remote Manager uses tags to categorize devices.  You may want to edit the tags associated with a device if the purpose of a device changes or if you use tags to create a new sub-category of devices. Device tags are stored in Remote manager and not on the device.

To add a tag to a device:

  1. Click Device Management > Devices.
  2. Select the device you want to update.
  3. Click More > Edit Tags. The Edit Tags dialog appears.
  4. Enter the name of a tag in the text box and click Add Tag.
  5. Click Save. The new tag is associated with the device.

To edit tags for a device:

  1. Click Device Management > Devices.
  2. Select the device you want to update.
  3. Click More > Edit Tags. The Edit Tags dialog appears.
  4. Click the tag name you want to edit. The tag name appears in the text box.
  5. Edit the tag name as needed and click Change Tag.
  6. Click Save. The new tag is associated with the device.

To remove a tag from a device:

  1. Click Device Management > Devices.
  2. Select the device you want to update.
  3. Click More > Edit Tags. The Edit Tags dialog appears.
  4. Click the red X under action to delete the corresponding tag underStream Name.
  5. Click Save. The new tag is associated with the device.

Permalink


The groups feature allows you to add or create a group and assign a list of devices to that group. You can create a hierarchical structure of device groups to help organize your device inventory.

To create a group

  1. Click Device Management > Devices.
  2. Click the Groups button and select Add Group. The Add Group dialog appears.
  3. Type a group name.
  4. Choose the folder where you want to place the new group. The default is the root level.
  5. Click the Add Group button. The group name appears in the folder structure under the root directory in the left pane.

To add a device to a group
You can add one or more devices to a device group, and can add up to 500 devices to a group at one time.

  1. Click Device Management > Devices.
  2. Select the device(s) you want to add to a group:
  • Click any device list item to select that device.
  • Use Control-click or Shift-click to select multiple devices or a range of devices.
  1. Click More in the Devices toolbar and select Assign to Groupfrom the Organize category. The Add to Group dialog appears.
  2. Choose a group from the drop-down list.
  3. Click Assign to Group. The devices are added to the selected device group.

To move/remove a device from a group

  1. Click Device Management > Devices.
  2. Click a group name in your list of device groups you wish to remove the device from.
  3. Select the device(s) you want to remove from a group:
  • Click any device list item to select that device.
  • Use Control-click or Shift-click to select multiple devices or a range of devices.
  1. Click More in the Devices toolbar and select Assign to Groupfrom the Organize category. The Add to Group dialog appears.
  2. Choose a group from the drop-down list.  You may also select the “/” to move it to the root directory.
  3. Click Assign to Group. The devices are added to the selected device group or root.

To edit device group properties
You can edit device group properties, including the group name and its parent in the groups hierarchy.

  1. Click Device Management > Devices.
  2. Click a group name in your list of device groups.
  3. Click Groups and select Edit Group from the drop-down.
  4. Make changes to the group name and location as needed.
  5. Click Edit Group to confirm your changes.

To Remove a device group
Removing a device group removes the group itself and moves all devices in that group to the parent level in your device list.

  1. Click Device Management > Devices.
  2. Click to select the device group you want to remove from the device hierarchy in the left panel under Groups.
  3. Click Groups and select Remove Group from the drop-down. A confirmation dialog appears asking you to confirm that you want to remove that group.
  4. Click Yes to confirm. The group is deleted and any devices in that group move to the parent level in your device hierarchy.

To show or hide device groups
This feature will allow you to toggle the Groups display to hidden or visible.

  1. Click Device Management > Devices.
  2. Click the Show/Hide Groups button on the far left side of theDevices toolbar.

Permalink


This article describes how to configure Digi Device Cloud or Digi Remote Manager to send an E-Mail notification when a device goes offline.

Note: This article assumes that you have already created a Digi Device Cloud account or a Digi Remote Manager account, that your device is configured to connect to the cloud and added to your account.

Guidelines for NDS devices (Digi Connect WAN 3G, ConnectPort X etc..) can be found here : Configure a Digi Connect WAN or ConnectPort Gateway for Device Cloud connection

Guidelines for Digi TransPort can be found here : Configuring a Digi TransPort for Remote Manager connectivity

Guidelines for adding a Digi device to the Digi Device Cloud or Remote Manager platform can be found here : Adding a Digi Device to the Digi Device Cloud or Remote Manager Platform and here Add a Digi TransPort to your Remote Manager account

Create an Alarm

1. Log into your Digi Device Cloud or Digi Remote Manager account.
2. Click on the Device Management tab.
3. Click on the Alarms tab.
4. Click on the Add button

User-added image

The Add Alarm window will open.

1. Select Device Offline in the Alarm Type drop down menu.
2. Chose a name for the Alarm. (default is Device Offline)
3. Chose a description for the Alarm. (default is Detects when a device disconnects from Device Cloud and fails to reconnect within the specified time)
4. Chose for how long the cloud should wait before firing an alarm (defaul is 5 minutes. This is recomended in case of cellular devices that can sometimes lose network connectivity due to bad reception and allow it to reconnect)
5. Resets when device reconnects will allow the alarm status to be reset as soon as the device reconnects to the cloud.
6. Chose the Scope of the alarm. It can be per group or per device. Per Group allows to select the root directory (in this case the alarm will be applied to all devices on this account) or a single group.
7. Click Create to create the Alarm.

User-added image

Create an E-Mail Notification

1. Navigate to Admin Account Settings > Notifications
2. Click on the Add button.

User-added image

1. Chose a name for the Notification
2. Chose a Description for the notification. This will be shown in the “Subject” field of the E-Mail
3. Chose an E-Mail address to send the notification to.
4. Select if you wish to receive a daily summary of your alarms and at which time.
5. Check this box to receive an E-Mail notification each time an alarm triggers (Each time a device goes offline this will trigger an alarm which in result will trigger an E-Mail)

User-added image

6. Select “Send notification for the following alarms” and in the box, type the name of previously created alarm, by default “Device Offline” and press enter.
7. In the list, chose the previously created alarm and click on the “+” icon

User-added image

8. Click Save

User-added image

Testing

To test that the Alarms and notification are working, simply disconnect/turn off one of your devices which are monitored by this alarm. After the selected delay triggers, the alarm should fire and you should receive an E-Mail similar to this one :

User-added image

Permalink


Introduction:

This article will discuss how to configure your Digi TransPort router for use with Remote Manager by utilizing the built-in Web User Interface (WebUI) of the Digi TransPort itself.

Changing the Remote Manager connection settings from the WebUI

The Digi TransPort WebUI can be accessed locally via the local IP address (LAN or WAN), or the Cllular Mobile IP address (provided your cellular account is one which supports Mobile Termination, and that you left a pinhole for HTTP or HTTPS through which to get to the WebUI if configured for IP Passthrough).

If you know the Mobile IP address and have met the conditions above, you should be able to open the TransPort’s WebUI by opening a browser to the Mobile IP of your TransPort at this time, but keep in mind that accessing the TransPort WebUI via the Local IP is preferred if available, since it doesn’t affect your cellular bill, is faster, and generally less prone to connection loss.

If you can get to the Local IP of the TransPort (this is an Ethernet or Wi-Fi connected TransPort and you’re at that location), you should access the TransPort’s WebUI using the Local IP address instead. The Digi Device Discovery Tool for Windows can be used to discover the Local IP address of the TransPort, if unknown. If you run the Device Discovery Tool and see a “No devices found?” message, and you’ve verified your TransPort is both powered on and has a solid Link LED present, you may want to check this article for Digi Device Discovery Troubleshooting Tips.

Assuming you can access either the Mobile (WAN) or Local (LAN) IP address and are now looking at the Web User Interface of your Digi TransPort:

1. Open Configuration -> Remote Management -> Remote Manager on the WebUI, then click the check box for “Enable Remote Management and Configuration using Remote Manager”. It should look similar to this:

2. On the page above, from the drop down menu, select the desired Device Cloud server :remotemanager.digi.com for the US Cloud or remotemanager-uk.digi.com for the EU Cloud.

3. Ensure the “Automatically reconnect to the server after being disconnected” box is checked as shown in the example, and configured with the 10 second value listed (or a reasonable alternative), as this is the box that tells your router to re-connect to the Remote Management server, should the connection get broken for some reason

4. Apply any changes by clicking the Apply button, when configuration is complete.

5. Click the blue “here” link to save the configuration, as shown below:

6. Click the “Save All” button from the ensuing page and you should get a message saying “The configuration has been saved successfully!”, then click the OK button.

7. After a minute or so, you should see that your Transport has established (i.e. state = ESTAB) a Remote Management connection to the Remote Manager server by viewing the Management -> Connections -> IP Connections page under the “General Purpose Sockets” listing towards the bottom:

In Closure: If all went well, your Digi TransPort should now be “Connected” on the Remote Manager server you selected in step 1 above.

Permalink


Adding your Digi TransPort to Remote Manager

  1. Log into your Digi Remote Manager account.
  2. Click on the Device Management tab.
  3. Click on the Add Devices button on the tool bar

  4. Add the Digi TransPort by either discovering it locally, or manually adding the Device ID, using either of the the two methods described below:

Discovery method:

  1. After hitting Add Devices (step 3 above), click the Discover >> button.

  2. Click the Discover button on the 2nd Add Devices screen.

  3. Select the Digi TransPort to be added, and click OK.

Manual method:

  1. After hitting Add Devices (step 3 above), click the dropdown which defaults to MAC Address, and select Device ID instead.

  2. Populate the entry field to the right of Device ID with the Device ID of your Digi TransPort.  This can be obtained from the Digi TransPort WebUI Home page if needed.

  3. Click the Add button, then click OK.

Your Digi TransPort should now be added to Remote Manager:

After your device is added, it should show up in the list of devices as disconnected (a Red icon beside the device means Disconnected, see below).

After a minute or so, refresh the device list by clicking the Refresh button, and verify a Connected state as seen below.  A Blue icon indicate the device is connected to Remote Manager.

 

Conclusion:

If you see the Blue/Connected icon next to your TransPort, it means that your device was properly configured, and you can now manage your TransPort on Remote Manager.  If still not connected after a a few minutes, you’ll want to re-check your TransPort Remote Management and Network configurations, as well as make sure you aren’t running into any Firewall issues between the TransPort and Remote Manager.

Permalink


Digi Device Cloud (5)

View category →

HOW TO: Change the Device Cloud Name on Gateways Using Device Manager from the Device Cloud
To change the server name for the Device Cloud connection from your Device Cloud account, you will navigate to the Device Management tab, right click on the desired Digi device and select Properties.

From the Properties screen, navigate to Advanced Configuration > Remote management connection > Remote management connection 1.  Type in the server name (en://my.devicecloud.com) in the Server address field:

User-added image

Click Save to save the changes.  Your device may disconnect from the Device Cloud and reconnect using the new name.

Permalink


The following example shows how to create a task on Digi’s Device Cloud to change the Remote Management Server Address in a TransPort.
Log into Device Cloud
Click on Device Management > Schedules and then click New Schedule
User-added image

Click Start Walkthrough
Type in the description at the top of the screen for the task
On the left menu, select Command Line Interface
For the first command, enter cloud 0 server my.devicecloud.com
On the left menu, select Command Line Interface, again
For the second command, enter config 0 saveall
Then click Schedule at the bottom right hand corner
User-added image

Either select Immediate or Future to schedule when you wish to apply this change
If you choose Future, you will need to use the drop down buttons to specify the date and time and then you will see the scheduled job on the next screen.
If you choose Immediate, it will simply complete the job.
You will need to select the devices you wish to apply these changes to.  If selecting more than one, use the “Ctrl” button to select these.
Select Run Now at the bottom of the screen if you choose Immediate or Schedule if you choose Future.
User-added image

Here are the results for a scheduled job.
User-added image

After the scheduled event, you can check to see if it performed by going to Device Management  >  Operations.  You should be able to see if it successfully completed or not.  You may also click on Operation Details for each individual device.
User-added image
You can also see the changes in each individual device by going to Device Management > Devices, selecting a particular device by double clicking on it, click on Configuration, Remote Management, Remote Manager, Remote Manager Config, then check the Connect to Device Cloud server.  At first you will see the previous server name, but if you click Refresh at the bottom of the page, it will update.
User-added image

Permalink


This article describes how to configure Digi Device Cloud or Digi Remote Manager to send an E-Mail notification when a device goes offline.

Note: This article assumes that you have already created a Digi Device Cloud account or a Digi Remote Manager account, that your device is configured to connect to the cloud and added to your account.

Guidelines for NDS devices (Digi Connect WAN 3G, ConnectPort X etc..) can be found here : Configure a Digi Connect WAN or ConnectPort Gateway for Device Cloud connection

Guidelines for Digi TransPort can be found here : Configuring a Digi TransPort for Remote Manager connectivity

Guidelines for adding a Digi device to the Digi Device Cloud or Remote Manager platform can be found here : Adding a Digi Device to the Digi Device Cloud or Remote Manager Platform and here Add a Digi TransPort to your Remote Manager account

Create an Alarm

1. Log into your Digi Device Cloud or Digi Remote Manager account.
2. Click on the Device Management tab.
3. Click on the Alarms tab.
4. Click on the Add button

User-added image

The Add Alarm window will open.

1. Select Device Offline in the Alarm Type drop down menu.
2. Chose a name for the Alarm. (default is Device Offline)
3. Chose a description for the Alarm. (default is Detects when a device disconnects from Device Cloud and fails to reconnect within the specified time)
4. Chose for how long the cloud should wait before firing an alarm (defaul is 5 minutes. This is recomended in case of cellular devices that can sometimes lose network connectivity due to bad reception and allow it to reconnect)
5. Resets when device reconnects will allow the alarm status to be reset as soon as the device reconnects to the cloud.
6. Chose the Scope of the alarm. It can be per group or per device. Per Group allows to select the root directory (in this case the alarm will be applied to all devices on this account) or a single group.
7. Click Create to create the Alarm.

User-added image

Create an E-Mail Notification

1. Navigate to Admin Account Settings > Notifications
2. Click on the Add button.

User-added image

1. Chose a name for the Notification
2. Chose a Description for the notification. This will be shown in the “Subject” field of the E-Mail
3. Chose an E-Mail address to send the notification to.
4. Select if you wish to receive a daily summary of your alarms and at which time.
5. Check this box to receive an E-Mail notification each time an alarm triggers (Each time a device goes offline this will trigger an alarm which in result will trigger an E-Mail)

User-added image

6. Select “Send notification for the following alarms” and in the box, type the name of previously created alarm, by default “Device Offline” and press enter.
7. In the list, chose the previously created alarm and click on the “+” icon

User-added image

8. Click Save

User-added image

Testing

To test that the Alarms and notification are working, simply disconnect/turn off one of your devices which are monitored by this alarm. After the selected delay triggers, the alarm should fire and you should receive an E-Mail similar to this one :

User-added image

Permalink


The following example shows how to create a task on Digi’s Device Cloud to change the Remote Management Server Address in a TransPort.
Log into Device Cloud
Click on Device Management > Schedules and then click New Schedule
User-added image

Click Start Walkthrough
Type in the description at the top of the screen for the task
On the left menu, select Command Line Interface
For the first command, enter cloud 0 server my.devicecloud.com
On the left menu, select Command Line Interface, again
For the second command, enter config 0 saveall
Then click Schedule at the bottom right hand corner
User-added image

Either select Immediate or Future to schedule when you wish to apply this change
If you choose Future, you will need to use the drop down buttons to specify the date and time and then you will see the scheduled job on the next screen.
If you choose Immediate, it will simply complete the job.
You will need to select the devices you wish to apply these changes to.  If selecting more than one, use the “Ctrl” button to select these.
Select Run Now at the bottom of the screen if you choose Immediate or Schedule if you choose Future.
User-added image

Here are the results for a scheduled job.
User-added image

After the scheduled event, you can check to see if it performed by going to Device Management  >  Operations.  You should be able to see if it successfully completed or not.  You may also click on Operation Details for each individual device.
User-added image
You can also see the changes in each individual device by going to Device Management > Devices, selecting a particular device by double clicking on it, click on Configuration, Remote Management, Remote Manager, Remote Manager Config, then check the Connect to Device Cloud server.  At first you will see the previous server name, but if you click Refresh at the bottom of the page, it will update.
User-added image

Permalink


One very useful aspect of Device Management on the Digi Device Cloud is the ability to view the Connection History of a device.  This of course refers to the connection history of that device as viewed from Device Cloud, and is a record of a device’s connections and disconnections with the server, for whatever reason.

Device Cloud Connection History (from the device UI):

Getting the Connection History from the Data Streams API:

As seen above, the Connection History of a device is something which Device Cloud keeps track of.  A screen like the one above may be useful when wanting to know the current state of a device or what’s been going on with it, but short of taking a screenshot or copying/pasting that information into a text file, the information isn’t very portable.  The good news is, the Connection History is something which is also tracked as a Data Stream, and each of the Connect/Disconnect events is a separate Data Point within that Stream.

To query the Data Stream Connection History if the same device, we must query for the Data Points which make up that Stream as follows:

/ws/DataPoint/{deviceId}/management/connections/

Example Request:  /ws/DataPoint/00000000-00000000-00409DFF-FF5DF1CB/management/connections/

Response (for a single Data Point of the Stream):

<?xml version=”1.0″ encoding=”ISO-8859-1″?>
<result>
<resultSize>206</resultSize>
<requestedSize>1000</requestedSize>
<pageCursor>27f2d9aa-beab-11e5-92dc-fa163ea15feb</pageCursor>
<requestedStartTime>-1</requestedStartTime>
<requestedEndTime>-1</requestedEndTime>
<DataPoint>
<id>f5e6756c-75c8-11e5-8dc1-fa163ee3abab</id>
<cstId>70</cstId>
<streamId>00000000-00000000-00409DFF-FF5DF1CB/management/connections</streamId>
<timestamp>1445194168409</timestamp>
<timestampISO>2015-10-18T18:49:28.409Z</timestampISO>
<serverTimestamp>1445194168412</serverTimestamp>
<serverTimestampISO>2015-10-18T18:49:28.412Z</serverTimestampISO>
<data>{“connectTime”:”2015-10-18T03:14:07.442Z”,”disconnectTime”:”2015-10-18T18:49:28.409Z”,”type”:”Wi-Fi”,”remoteIp”:”213.35.189.122″,”localIp”:”192.168.82.204″,”bytesSent”:70412,”bytesReceived”:69588,”session”:”6b861b2f-bd52-4455-b9fc-dc92693460db”}</data>
<description/>
<quality>0</quality>
</DataPoint>…
</result>

As can be seen in the <resultSize> field, there were 206 Data Points in the response to the query, so I’ve only listed one Data Point as an example of the type of data retrieved from the Connection History Data Stream.

Permalink


NetCloud Engine (82)

View category →

Summary

This article describes the steps necessary to set up the ADConnect App.


Configuration

This simple app lets you specify which AD Name Servers to use over NetCloud Engine, so that your remote machines know how to reach your domain controllers. In just three steps, you can provide domain access for remote machines, without policy updates, DNS changes, or firewall configuration. Once you apply this change, all the devices on this network will be pushed down the DNS setting on the NetCloud Engine Virtual Interface. (All the PC’s must be running 300 and above to get the DNS setting)

Note: This article will be reformatted after the release of our next NetCloud Engine update

Note: ADConnect will not apply to NetCloud Gateway routers, or the external devices behind them.

Three Step Overview:

  1. Install the NetCloud Engine client on your Domain Controller(s), and your remote machines
  2. Convert the device to a server

    User-added image

  3. Specify your Name Servers, and you’re done. Your remote machines now have full domain access, from anywhere.

    User-added image
    Key features:

  • NetCloud Engine networks are 100% compatible with Active Directory domains and services
  • Extend domain services to members and devices anywhere
  • Domain membership is maintained over time, without the need for periodic domain “check-ins.”

Note: After you enable ADConnect, you will need to setup a SmartZone to ensure optimal routing of local traffic.

Permalink


Summary

This article describes the steps necessary to re-install NetCloud Engine after you have cloned a device.


Issue

If you clone a machine after NetCloud Engine was installed even if you uninstall NetCloud Engine before you cloned it, you will not be able to reinstall NetCloud Engine again unless you remove the NetCloud Engine generated system ID.

Important Note: Make sure you uninstall the NetCloud Engine client first before manually making the following changes.


Solution

  • On a Windows computer, use regedit and delete the following Pertino Folder:
    • HKEYLOCALMACHINE\SOFTWARE\Pertino
  • On a linux computer, delete the pertino.conf file:
    • /etc/pertino.conf
  • On a Mac, delete the com.pertino.config.plist file:
    • /Library/Preferences/Pertino/com.pertino.config.plist file

Permalink


Summary

This article addresses persistent “Failed to create dispatcher” exceptions that prevent the Windows client from connecting to its assigned Tunnel Server (TS). The client will cycle endlessly trying to repair the TS connection.

Here is sample gateway.log output (in the C:\Program Files\Pertino\logs folder):

2015-09-05 00:33:36,979 UTC [0x00001bd8] INFO (g2.tunnelClientThread:361) – Failed to create dispatcher: An exception occurred. The error type is: class TunnelProtocolDispatcher::Exception The error text is: Could not allocate event base! Previous errno: 9 [Bad file descriptor] Last error: 6 [The handle is invalid.] Source file name: \gatetun-common\tunnelprotocol\dispatcher\tunnelprotocol_dispatcher.cpp, #416 Function name: TunnelProtocolDispatcher::TunnelProtocolDispatcher

The backtrace is: …

The key information is “The error text is: Could not allocate event base!” The NetCloud Engine Gateway Service (pgateway) uses Libevent for different areas of functionality that require asynchronous event handling. On Windows the client only uses Libevent for its internal dispatcher that manages its connection to the client’s TS.

Libevent uses environment variables with an “EVENTNO” prefix to determine which of its internal event multiplexing subsystems to use. On Windows, Libevent only has access to its “WIN32” subsystem. If a system environment variable, “EVENTNOWIN32″ exists on a Windows client, Libevent will fail and be unable to allocate any event base.

The easiest remedy is to remove the system environment variable via the System control panel (“Advanced system settings”, “Environment variables”, system NOT user dialog panel). Once it has been removed, the system will need to be restarted for the change to be noticed.

Permalink


Summary

On the NetCloud Engine network, devices are identified by the computer name, so in order for all machines to be associated to the same workgroup, each one needs to have a unique computer name. The purpose of this article is to provide instructions on how to change the name of your computer so that it is unique in your NetCloud Engine network.


Configuration

Configuration Difficulty: Beginner

Instructions for Windows

  • Step 1: Press the Windows key and the letter “E” on your keyboard at the same time to bring up the Windows Explorerwindow.
  • Step 2: Right click on Computer and then select Properties.
  • Step 3: Next to the computer name on the right, select Change settings.
  • Step 4: Select Change…, and in the Computer name text box add a unique name, then click OK.
    • Note: Windows allows for a max of 15 characters for the computer name.
  • Step 5: You will be required to reboot Windows for the settings to apply.

Instructions for Mac

  • Step 1: Click on the Launchpad from the Dock.
  • Step 2: Click on System Preferences.
  • Step 3: Under Internet & Wireless, click on Sharing.
  • Step 4: In the top section, change the Computer Name to be unique (among other devices on your NetCloud Engine Network).
  • Step 5: (Optional) To make sure the change is immediate, click on the NetCloud Engine icon in the menu bar and select Disconnect.
    • Step 5b: Once the icon changes to show a Pause symbol, click on it again and select Connect.

Permalink


Summary

When you upgrade your NetCloud Engine client, AVG falsely detects an issue with a temporary file we generate in the temp directory.


Configuration

Configuration Difficulty: Intermediate
  • Step 1: Select ‘Allow’ to prevent AVG from blocking NetCloud Engine.
    • Note: A re-installation of NetCloud Engine will be required if ‘Allow’ is not selected

User-added image

Permalink


NetCloud Manager (6)

View category →

Summary

The Applications Tab within NCM allows you to purchase, try and manage applications within NCM.


 

Overview

The Applications tab will display all available applications.

You can purchase or try an application by selecting the appropriate button.

Once your account has the application entitled the Buy and Try buttons will be replaced by a Manage button.

User-added image

Clicking Try will create a trial entitlement for 10 devices.

Clicking Buy will bring up a tab for locating a partner to purchase the entitlement.

By clicking Manage you can Add or Remove devices. You can also determine which devices are entitled.

User-added image

To Add a device to an entitlement click the Add button. You will be presented with a dialog to select routers to add. You can locate devices with the Search field by Name or MAC or Product as needed. Place a checkmark next to the device(s) you wish to add to the entitlement and the press Save.

User-added image

To Remove devices from an entitlement, select the device(s) you wish to remove and then press Remove.

User-added image

In the right column you can find the following information:

  • Entitlement Details
    • Available: Remaining entitlements
    • Assigned: How many entitlements have been applied to devices
    • Non NCM Devices: Devices with this entitlement that are not in NCM
    • Total Allowed: Total number of entitlements purchased.
  • Buy More: Buy more entitlements
  • Features: What the entitlement offers
  • Requirements: Any requirements placed upon the entitlement
  • Support Products: Which Cradlepoint products will work with this application
  • Supported NetCloud OS Version: NCOS requirements for devices to use this entitlement

User-added image

Permalink


NETCloud Manager

The default NCM configuration generates the approximate data usage that is presented below. Protocol and carrier overhead can increase these values but these values do provide a generally good rule of thumb for data generated by use of NCM.

IMPORTANT: Things that could dramatically increase your data usage:

  1. Enabling logging, stats and alerting
  2. A high number of events being logged on the router
  3. Firmware upgrades pushed from NCM
  4. Modem disconnecting and reconnecting loops.

Routers managed through NCM:

  • By default, a Connection Pulse that are approximately 66 bytes is sent to NCM every 2 minutes.
    So 720 heartbeats/day x 66 bytes = 47520 bytes/day, 47520 bytes/day x 30 = 1,425,600 bytes/month (1.43 MB/month).
  • By default Usage Reporting that are approximately 10-20KB per report (depending on how many WAN devices are utilized on the Cradlepoint router) are sent to NCM every hour.
    So 20 KB/hour x 24 = 480 KB/day; 480 KB/day x 30 = 14400 KB/month (.014 GB/month or 14 MB/month)
  • By default Log Reports that are approximately 100KB (depending on how many events are logged on the router) are sent to NCM every hour. These reports can vary in size dramatically depending on events that are logged on the router; client connects/disconnect, modem state, etc.
    So a minimum amount of data sent would be 100 KB/hour x 24 hours = 2400 KB/day; 2400 KB/day x 30 = 72000 KB/month (.069 GB/month or 69 MB/month).

Routers not managed through NCM:

  • Every time the router is powered on it sends a 50 byte heartbeat to the NCM Server and then sends a heartbeat every 86400 seconds, (once per day).
    So the volume of data generated is approximately 50 bytes/day x 30 days = 1500 bytes/month (.0000014 GB/month or .0014 MB/month).

(The timers above can be adjusted higher or lower, depending on your data caps).


Advanced Failure Check

A ping packet is 64 bytes of data. If Advanced Failure Check set to an Idle Check Interval to 3600 (1 ping per hour) would generate 64 bytes/hour x 24 hours = 1536 bytes/day.
Then 1536 bytes/day x 30 days = 46080 bytes/month (.000042 GB/month or .042 MB/month).

NOTE: Increasing the time interval on NCM check in or Advanced Failure Check will cause data generation to increase.

Permalink


Summary

This article describes how to set up alerts, export reports, and export logs from NetCloud Manager (NCM).

NOTE: On July 13, 2017, NetCloud Alerts currently generated from the legacy Enterprise Cloud Manager (ECM) will be updated with the name change to NetCloud Manager (NCM). Automated systems that consume this information may need to be updated accordingly.
Email and API Alert changes include:

  • Alert titles will change from “Cradlepoint ECM Alert Notification” to “Cradlepoint NCM Alert Notification”
  • Alert subjects will change from “ECM Alert: <friendly info>” to “NCM Alert: <friendly info>”
  • Emailed Alert summary report subject will change from “ECM Alert Summary” to “NCM Alert Summary”
  • Connection State Alert name will change from “ECM Connection State” to “NCM Connection State”
  • Firmware Upgrade alert name will change from “Firmware Upgrade” to “NetCloud OS Upgrade” with an alert description changing to “The router NetCloud OS was successfully upgraded to X.X.X”

Setting Up Alerts

The Alerts page has two views for tracking device status changes:

  • The Log view shows a list of alerts sent from the routers to NCM.
  • The Settings view shows rules for alerts, including email notifications.

Toggle between these two views by clicking on the buttons at the top left.

User-added image

Alerts are of the following types (see Definitions below):

  • Configuration Change
  • Configuration Rejected
  • Configuration Unacknowledged
  • Ethernet WAN Disconnected
  • Ethernet WAN Plugged In
  • Ethernet WAN Unplugged
  • Data Cap Threshold
  • Device Location Unknown
  • NCM Connection State
  • Firmware Upgrade
  • Geofence Proximity Change
  • Reboot
  • Temperature Limit Exceeded
  • Modem WAN Connected
  • Modem WAN Device Plugged In
  • Modem WAN Device Unplugged
  • Modem WAN Disconnected
  • WAN Service Type
  • Account Locked
  • Failed Login Attempt
  • Intrusion Activity
  • IP Address Banned
  • IPS Engine Failure
  • Successful Login
  • Unrecognized Client
  • WiFi as WAN Connected
  • WiFi as WAN Disconnected
  • WiFi as WAN Network Available
  • WiFi as WAN Network Unavailable

To enable alerts, including emailed notifications, first select the Settings view and then click on Add at the top left. Create an alert notification rule by completing the fields.

User-added image

Complete the following fields to create an alert notification rule:

  • Accounts/Groups (required) – Choose which sets of devices will follow the notification rule. If you select an account, both grouped and ungrouped devices within that account (including all subaccounts) will be assigned to this rule.
  • Alerts (required) – Select the alert types from the dropdown options.
  • Users (optional) – If you want emailed notifications for these alerts, select users from the list to receive those emails. If you just want these alerts logged, leave this field blank.
  • Interval (optional) – Select a time interval from the dropdown options. If you select “Immediately,” an email notification is sent every time one of the selected types of alerts are logged. Otherwise, the alerts are stored over the course of the time interval and then sent together.

Potential NCM Alert Issues

  • Receiving the Email Alert seem to take longer than expected.
    • Once NCM is aware of the alert, it will verify the alert, and send it out to the configured email address. We do not have control over the alert once we have sent it to its destination address.
      • We have seen some mail servers reject, or display abnormally long delays in the alert deliveries.
        • To trouble shoot/verify if this is the issue, configure a different email address with a different domain and test the behavior of the alerts.
  • Times can also vary depending on the number and type of WAN connections being used for this device.
    • If a device only has one internet source, only one connection to NCM, then you can expect delays in the alerts. The alerts are configured in NCM, then NCM lets the router know what to watch for. If the router experiences any issue pertaining to the configured alerts, the router will then report this back to NCM. However the caveat is if the router loses its internet source or connection to NCM, then the router cannot report the issues to NCM until it regains its connection to NCM.
    • In cases where you have more than one internet connection the alerts should be fairly on queue, so long as the router can check into NCM via its second internet connection to report its alerts.

Exporting Reports

Reports allow you to create a summary of information about groups of devices and export that information as a CSV file. Select from several fields to customize your reports. Select the type of report (Data Usage or Signal Quality), a range of dates, the group(s), and identifying fields and then click Run Report to view the report. You also have the option to save the settings of a report for future use.

1366IMG24.png


Exporting Logs

To export a device’s logs as a CSV file, first enable log reporting for the group the device is in. (This is disabled by default because some users won’t use this functionality – it would unnecessarily use data.) Navigate to the Groups page, select the desired group, and click on Settings.

User-added image

In the popup window that appears, ensure that Enable Log Reporting is selected.

User-added image

Once log reporting is enabled, navigate to the Devices page, select the desired device, and click on Export → Export Logs to export the device’s logs as a CSV file.

User-added image


Alert Definitions

  • Account Locked – If Advanced Security Mode is turned on for a device, the account will lock for 30 minutes after six failed attempts to log into the device. To enable this setting, open the configuration pages in Groups or Devices and go to System Settings → Administration. Open the Router Security tab and select Advanced Security Mode.
  • Configuration Change – This displays when there has been a local configuration change. Sample alert: The device configuration has changed.
  • Configuration Rejected – A configuration change that was sent to the device has been rejected.
  • Configuration Unacknowledged – A configuration change that was sent to the device was not acknowledged by the device.
  • Data Cap Threshold – If you have a data cap threshold set, this sends an alert when the threshold is reached. A data cap threshold must be configured under Internet → Data Usage. Sample alert: The (Internal LTE/EVDO Port:int1) rule exceeded 100 percent of its 150 MB daily cycle.
  • Device Location Unknown – Displays when no location has been reported for 24 hours if the device has GPS enabled. If a manual location is being used the alert will not be generated.
  • NCM Connection State – Displays when the device loses or regains its connection to NCM. Sample alert: The device entered the “online” state.
  • Ethernet WAN Connected – An Ethernet WAN device is now active.
  • Ethernet WAN Disconnected – An Ethernet WAN device is no longer active.
  • Ethernet WAN Plugged In – An Ethernet WAN device is now attached.
  • Ethernet WAN Unplugged – An Ethernet WAN device has been removed.
  • Failed Login Attempt – Someone attempted to log into the device administration pages locally and failed. Sample alert: An attempt to log in as the admin user from 192.168.0.142 has failed.
  • NetCloud OS Upgrade – The device NetCloud OS has been upgraded.
  • Geo-fence Proximity Change – Displays whenever the device enters or exits the specified geo-fence.
  • GPIO State Change – A device GPIO pin has changed state. To update the GPIO configuration, open the configuration pages in Groups or Devices, select the System → GPIO Configuration tab. Requires at least 6.0.2 NetCloud OS.
  • Intrusion Activity – This is only relevant for devices with CP Secure Threat Management. Whenever the Threat Management deep packet inspection engine detects an intrusion, the event is recorded in the logs. These events are grouped together for 15 minutes and then reported in NCM, so even if you select “Immediately” in the Interval field below, an emailed alert might not arrive for approximately 15 minutes after an intrusion. Intrusion Activity alerts include the intrusion details and the action taken by the engine (e.g., “Blocked”). To edit Threat Management settings, open the configuration pages in Groups or Devices and select Network Settings → Threat Management. For more information about Threat Management, visit the Knowledge Base article.
  • IP Address Banned – If the Ban IP Address setting is turned on for a device and someone from a particular IP address attempts and fails to log into the device administration pages six times, that IP address will be banned for 30 minutes. To enable this setting, open the configuration pages in Groups or Devices and go to System Settings → Administration. Open the Router Security tab and click on Advanced Security Mode. Select the Ban IP Address option.
  • IPS Engine Failure – This is only relevant for devices with CP Secure Threat Management. In the unlikely event that the Threat Management engine fails, an alert is logged. You can set the router to either allow or deny traffic with a failed engine: to edit this setting, open the configuration pages in Groups or Devices and select Network Settings → Threat Management. For more information about Threat Management, visit the Knowledge Base article.
  • IPSec Tunnel Down – An IPSec tunnel that was successfully connected has gone down.
  • Modem WAN Connected – A modem WAN device is now active.
  • Modem WAN Device Plugged In – A modem WAN device is now attached.
  • Modem WAN Device Unplugged – A modem WAN device has been removed.
  • Modem WAN Disconnected – A modem WAN device is no longer active.
  • Modem WAN Standby – A modem WAN device is now in standby. This means the modem is connected to the carrier, but is not sending any data. A modem in standby will failover faster than a modem not in standby. Standby can be turned on in the router’s configuration in the Connection Manager grid.
  • Reboot – Displays when the device has been rebooted. Sample alert: The device has been rebooted.
  • Rogue Access Point Detected – Displays after running a WiFi site survey when a rogue access point not marked as known is detected broadcasting the same SSID as the device running the site survey. This helps identify potential access point hijacking, evil twin, and man-in-the-middle WiFi attacks.
  • Router App Custom Alert – A custom alert that is generated by the custom code inside a router app.
  • Router App Execution State Changed – A router app that is running on a group goes into a different execution state (start, stop, error, etc).
  • Unexpected Router App Installed – An unexpected router app is found installed, an expected router app is unexpectedly uninstalled, or a router app unknown to the system is found installed.
  • Successful Login – A user has logged into the router locally (requires at least NetCloud OS 5.0.1).
  • Temperature Limit Exceeded – For products with an internal temperature sensor (COR IBR1100 and IBR1150) and configured temperature limits, this alert displays when one of those limits is reached. To set these temperature limits for the COR IBR1100 Series, open the configuration pages in Groups or Devices, select System Settings → Administration, and click on the Temperature tab.
  • Unrecognized Client – A client with an unrecognized MAC address has attempted to connect to the device. MAC logging must be enabled for this alert to display. In the configuration pages, go to: Network Settings → MAC Filter / Logging to enable MAC logging.
  • WAN Service Type – A WAN device has changed its service type, such as switching from 3G to 4G. Possible service types include: DHCP, LTE, HSPA+, etc. Sample alert: The lte-2ae6ec8e service type has changed to LTE.
  • WiFi as WAN Connected – WiFi as WAN is now active.
  • WiFi as WAN Disconnected – WiFi as WAN is no longer active.
  • WiFi as WAN Network Available – A WiFi as WAN network is now attached.
  • WiFi as WAN Network Unavailable – A WiFi as WAN network has been removed.
  • Zscaler TLS Tunnel State – This displays the state of the Zscaler TLS tunnel when using Zscaler Internet Security in TLS Tunnel mode. If there is a connection error more information can be found in the router’s system log.

Permalink


For customers with NetCloud Manager (NCM), there are three main ways to edit a device’s configuration: in NCM, through Group and Device configurations, and locally, through the router’s own administrative page.

  • NCM Group configuration has the lowest priority.
  • NCOS Local configuration has high priority.
  • NCM Device configuration has the highest priority.

The router’s default configuration is used as a basis for comparison for configuration files. It is overwritten by any custom local configurations or NCM configurations.

The Group configuration in NCM is overwritten by both the custom Local router configuration and the Device configuration in NCM.

The NCM Device and Local router configurations are synonymous in most cases. When making a configuration change at the local level, the changes will then sync with the NCM Device level, and vice versa. The two scenarios where the NCM Device level configuration will override Local changes are:

  • when conflicting changes are made at both the Local and NCM Device level while the device is offline. Once brought online and checks into NCM, the NCM Device level changes will have priority.
  • when a new change is made locally while the NCM Device level configuration is still syncing the previous change. The new change will be overwritten by the last NCM Device level configuration once the sync completes.

In general, the preferred method for managing devices that are registered in NCM is through the Group configuration. If there are more specific settings needed for individual devices, use the Device configuration in NCM. For example, it is possible to make the administration password standard for an entire group, and then create individual SSIDs for each device – both through NCM.

Troubleshooting

If most of the devices in a group are functioning as intended, but one member of the group is not behaving the same as the others, there may be a device level configuration that is overriding the group configuration. To remove the Device configuration and keep the Group configuration, log in to NetCloud Manager, select the Devices tab, highlight your router, click Configuration and select Clear

Clear Device configuration


 

Determining where a router gets its configuration

The individual config symbol found on the NCM Devices page indicates that the router is running a non-default configuration. The same symbol, when found on the NCM Groups pages tells us that the group contains one more routers that are running configuration settings that do not match the router default or the group configuration. (Tip: clicking the individual config symbol on the Groups page will automatically display all routers with unique configurations.)

The Configuration Summary option in NCM displays a color-coded output of the router’s configuration. The target configuration displays the total sum of the different configurations the router is running:

  • settings in purple are pulled from the Group configuration in NCM
  • settings in green are pulled from the Device configuration in NCM
  • settings in grey exist only on the router’s local configuration file, and are not synced to the Device configuration in NCM (possibly because the config sync was suspended, or the router went offline before syncing)

User-added image


 

Resetting a Router Managed in NetCloud

If you factory reset a device that is managed by NetCloud Manager, the Cradlepoint will automatically connect to the internet, check back in with NetCloud Manager and re-apply the Group and Device configuration stored in NetCloud. To get the device to a factory default state, the NetCloud Device and Group configuration need to be removed from the device.

To factory reset a device that is in NetCloud Manager, do the following first before trying a software or hardware reset, otherwise, it will be reverted to its previous configuration.

Step 1: Log in to Netcloud Manager. Open the Devices tab and select your Cradlepoint Router.
Step 2: If the device is in a group: highlight the router, click “Move”, select the parent account, and click “Ok”.

Highlight your router and select "move"
Select the root account and click "ok"

Step 3: Once the device is removed from the group, highlight your router, click “Configuration” and select “Clear”.

Highlight your router, click "Configuration" and select "Clear"

Step 4: Once the router has been removed from its group and the device level configuration has been cleared, you can factory reset by clicking “Commands” and selecting “Restore to Defaults”. You may also use the hardware reset button or System > System Control > Device Options > Factory Reset Router in the local web interface.

Highlight your router, click "Configuration" and select "Clear"

Permalink


NetCloud Manager: Traffic Analytics

The following products do not support Traffic analytics:

  • Series 2 Devices
  • CBA850
  • CBA750B
  • CBA400
  • CBA450
  • MBR1200B
  • MBR1400
  • IBR350
  • IBR1100
  • IBR1150
  • IBR600B
  • IBR650B
  • IBR600
  • IBR650

Click here to identify your router.


Quick Links

Summary

Configuration

Troubleshooting

Related Articles


Summary

This article is intended to guide the user through navigating, configuring, and understanding the NetCloud Manager Traffic Analytics feature.

Enabling the Traffic Analytics feature requires NCM Enterprise.  To learn more about NCM Enterprise, including setting up a demo, please visit Network Management & Applications .


Configuration

Enabling Traffic Analytics Difficulty: Beginner

Traffic analytics can be enabled through NCM under the account dashboard or in the device dashboard after selecting specific device.

To enable Traffic Analytics, follow the directions listed below.

Step 1: Log into your NCM account
Step 2: If your router is not already registered to NCM, refer to this article for help registering your device to NCM.  Otherwise, skip to the next step.

User-added image

Step 3: Click on the Dashboard tab.
Step 4: Click on Traffic tab underneath the Dashboard menu.
Step 5: Click on the Settings button.
User-added image
Step 6: Find the device you wish to enable Traffic Analytics on on (either through the list or through the search bar) and check the associated box.
Step 7: Click on the Enable button above the top of the devices table, and then click on “Client and Traffic”.
User-added image
Step 8: The prompt will ask if you are sure you wish to enable the feature, select Yes.

Note: After enabling Traffic Analytics for a device it will take 24 hours to start showing reported data.

Note: The same process can be completed through the device dashboard by clicking the same Traffic menu button.

Dashboard vs Device Level

Traffic Analytics can be found under both the account dashboard and the device dashboard.
User-added image

Account Traffic Analytics can be viewed by clicking on the Dashboard button and clicking on the Traffic button under the account dashboard menu.
User-added image

Device Traffic Analytics can be viewed by clicking on the Devices button, selecting the desired device from the list, and clicking on the Traffic button under the devices dashboard menu.
Both Client Data Analytics pages will present the same information, but the device level will only present information on clients connected to that particular device.

Adjust Data Range and Category Difficulty: Beginner 

The Traffic Analytics page has settings to specify the desired data range time period, the category of traffic to present on the page and data source information.  This can help present only the relevent information desired for a particular user.  To change these settings follow the directions listed below:

Step 1: Log into your NCM account.
User-added image
Step 2: Access the Traffic Analytics page through the account or device dashboard
User-added image
Step 3: To change the data range, click on the Data Range field and select from YesterdayLast 7 DaysLast 15 DaysLast 30 Days, or Custom Range to specify a broader date range.
User-added image
Step 4: To change the data source, click on the Data Source field and select from AllEthernet, WiFi, or Unknown to specify what types of client data types you want to have displayed.
User-added image
Step 5: You see which categories of data and applications are using what percentage of the total data used by scrolling down to the Top Categories and Top Applications sections.
User-added image
Step 6: You can view what percentage of your data is being used by which category and which application by scrolling down to the Percent of Total Usage and Data Usage by Day sections.
User-added image
Step 7: Filter the type of data displayed by category by clicking on the drop down menu for Category.
User-added image
Step 8: Filter the type of data displayed by application by clicking on the drop down menu for Application.
User-added image
Step 9: The last section of the page shows Data Usage by Category, Application, RouterClient, or Day.  Select one of these filters to view specific data usage numbers such as total data usage, download and upload data for the selected filter.

Troubleshooting

  • No traffic statistics displayed

If you are viewing the Traffic Analytics page on the Dashboard and there is nothing displayed, please check the following:

Traffic Analytics may not have enabled for the device.
The device might have been added recently (within 24 hours) and does not yet have data to display.

  • “Not Available” displayed in app category field

    Traffic category/application may result in “Not Available” when the application engine cannot categorize the traffic.  This may be caused if:

1. Application is not one of the applications identified by the engine; including any home-grown applications

2. Traffic is tunneled/encrypted not allowing the engine to inspect the application

 

Permalink