User guide

Support of CWMP with TR-069 Devices Port Management (non-iMAP Devices)
5-227
AlliedView NMS Administration Guide (Controlling and Provisioning Network Devices)
• The upstream port cannot be determined, and so provisioning is done using the CPE MAC address. This is similar to pro-
visioning an iMG without an iMAP. Refer to 7.11.
• An Auto-Configuration Server (ACS) URL must be configured in the CPE for using TR-069 for communicating with the
ACS (the NMS). The current release of the Comtrend CPE is not able to use DHCP to configure the ACS URL, and so
for SP5 the Comtrend Boot Configurator must be used. Refer to 5.7.6.5.
• Customer ID (SysContact on CPE) is limited to 15 characters. If more than 15 characters are used when provisioning a
triple play customer, the iMAP ADSL bond port will use the entire string, but the Comtrend CPE SysContact will be
truncated to 15 characters, resulting in more complex customer management.
• Derived voice service is not supported unless the VoIP phone is connected directly an Ethernet port and the CPE can pro-
vide a bridged Ethernet connection. When provisioned this way, the VoIP features will not be managed by NMS.
• The only supported internet service is Bridged.
• For Video, only IGMP snooping enabled is supported on the CPE.
• Only a subset of wireless features can be configured using the NMS.
• The Compare Profile feature is not supported.
• The MDTI feature software configuration is not supported, since the software file uses a different format.
• The NMS must use the configuration file to make most of the changes to the CPE and then sends it back to the CPE using
TFTP or CWMP (the default is TFTP). Therefore, when any changes are made (using the Service Management panels),
the configuration file is updated and the CPE must reboot for the changes to take effect. During this reboot services are
dropped until the CPE returns to service.
5.7.6.4 Provisioning Flow
Taking the feature limitations into account, as listed in 5.7.6.3, provisioning the Comtrend CPE involves the following con-
cepts:
1. Before a Comtrend CPE device is sent to a customer, it will first need to be connected to a PC (the NMS server) to enable
the default device configuration. The provider will run the Comtrend Boot Configurator Tool and upload the default boot
configuration to the CPE which will add the management VLAN and TR-069 information so that it can be managed
using TR-069. It also includes the Inform interval.
2. Existing iMG/RG profiles (General, Internet and Video) can be used, but not all values in these profiles will apply. Non-
applicable parameters will be skipped when the profile is deployed or used to provision the CPE.
3. When provisioning the Triple Play form, the CPE MAC address is required because it cannot be correctly determined
automatically and mapped with device port when needed.
Note: With the Comtrend provisioned with a specific MAC address, it cannot simply be swapped with another
unit when performing provisioning or maintenance and having the NMS automatically provision the new
unit. The old unit would need to be deprovisioned, then the provisioning process would need to start
again.
4. The Comtrend CPE only allows one CLI login session at a time (for example, if CLI is used to initiate TFTP to the
device). Therefore, login to the CPE device will fail if another user is already logged in.
Caution: While an administrator is logged into the CPE, the NMS cannot login, and so some features will
not work.
5.7.6.5 Comtrend Boot Configurator
The Comtrend Boot Configurator is a tool that allows updating the Comtrend CPEs to use management configuration param-
eters and is similar to the boot configurator used for iMG/RGs. (Refer to 7.2.5). The main difference is that since Comtrend
CPEs do not support getting the TFTP server address through DHCP, you must use the tool to generate the default configura-
tion and then upload it to the device. The following figure shows a sample Comtrend Boot Configurator panel with values
filled in.