CDRouter_TR-069_User_Guide_6-1

CDRouter TR-069 User Guide

Version 6.1

QA Cafe ? 2009

support@bc0e41e4524de518964b7ddf

C D R o u t e r T R -069 U s e r G u i d e 2 QA Cafe ? 2009

1.Introduction

CDRouter TR-069 Add-on for CDRouter

CDRouter TR-069 adds TR-069 testing and functionality to our industry leading CPE and router test platform, CDRouter. CDRouter TR-069 has been designed from the ground up to work with implementations based on the Broadband Forum's CPE WAN Management Protocol described by Technical Report 69 (TR-069). CDRouter TR-069 currently supports TR-069 Amendments 1 and 2. With the CDRouter TR-069 add-on module enabled, CDRouter is enhanced to provide a built-in ACS during all testing sessions. The CDRouter TR-069 add-on module also contains several new test modules focusing on three major areas of TR-069 testing: 1. Fully automated Broadband Forum PD-128 testing ? pd128.tcl test module 2. Real-world testing that addresses functionality not currently covered in PD-128 ? tr69.tcl test module ? tr111_part1.tcl test module ? tr111_part2.tcl test module 3. CWMP data model profile verification testing for Broadband Forum TR-098 (through Amendment 2), TR-106 (through Amendment 2), and custom user-defined data models ? tr098_profiles.tcl test module (data mode for IGDs) ? tr106_profiles.tcl test module (data model for generic Devices) ? cwmp_profiles.tcl test module (user defined data models) By offering automated versions of the PD-128 test cases in addition to the growing battery of real-world and data model profile tests, CDRouter TR-069 can help you test your TR-069 device quickly and thoroughly.

CDRouter TR-069 Extended Data Model Add-on (TR69-EDM)

The Extended Data Model add-on for CDRouter TR-069 (TR69-EDM) provides support for testing supplementary profiles defined additional Broadband Forum data models not included with CDRouter TR-069. The TR69-EDM add-on is only available on systems that already have CDRouter and the CDRouter TR-069 add-on installed. TR69-EDM provides support for the profiles defined in Broadband Forum TR-104, TR-135, TR-140, TR-143, TR-157, and TR-196. The following six test modules are included with the TR69-EDM add-on:

C D R o u t e r T R -069 U s e r G u i d e 3 QA Cafe ? 2009

?

tr104_profiles.tcl (data model for VoIP devices) ?

tr135_profiles.tcl (data model for STB devices) ?

tr140_profiles.tcl (data mode for storage devices) ?

tr143_profiles.tcl (profiles for network testing and monitoring) ?

tr157_profiles.tcl (additional profiles) ? tr196_profiles.tcl (data model for Femto devices)

NOTE: This document covers the CDRouter TR-069 and TR69-EDM versions bundled with CDRouter 6.1.

C D R o u t e r T R -069 U s e r G u i d e 4

QA Cafe ? 2009

2.Test Methodology

Initial Setup

CDRouter TR-069 provides a built-in ACS for CPEs to communicate with. Prior to running any tests however, the CPE must be told how to connect to the ACS. There are no methods for automatic ACS discovery currently supported. Information on how to configure CDRouter TR-069's ACS can be found in Section 4.

Start-Up

During the start-up procedure, CDRouter TR-069 expects to receive an Inform RPC from the device being tested. This Inform should be triggered by rebooting the device, or by configuring the CPE Connection Request URL in the CDRouter configuration file. Once CDRouter has received the initial Inform, the testing procedure will begin.

Running

Once testing has begun, CDRouter TR-069 will use the built-in ACS to communicate with the CPE. No additional user interaction is needed! Seven modules are included with CDRouter TR-069: pd128.tcl Automated version of PD-128 test plan tr69.tcl Additional TR-069 tests tr111_part1.tcl TR-111 Part 1 test cases tr111_part2.tcl TR-111 Part 2 test cases tr098_profiles.tcl CWMP profile testing for TR-098 (IGD) tr106_profiles.tcl CWMP profile testing for TR-106 cwmp_profiles.tcl CWMP profile testing for user defined profiles Six additional modules are available with the TR69-EDM add-on: tr104_profiles.tcl CWMP profile testing for TR-104 (VoIP) tr135_profiles.tcl CWMP profile testing for TR-135 (STB) tr140_profiles.tcl CWMP profile testing for TR-140 (Storage) tr143_profiles.tcl CWMP profile testing for TR-143 tr157_profiles.tcl CWMP profile testing for TR-157 tr196_profiles.tcl CWMP profile testing for TR-196 (Femto) To run only the TR-069 related test modules from the buddy command-line:

C D R o u t e r T R -069 U s e r G u i d e 5 QA Cafe ? 2009

# buddy –module pd128.tcl,tr69.tcl,tr111_part1.tcl,tr111_part2.tcl, tr098_profiles.tcl,tr106_profiles.tcl,tr104_profiles.tcl,tr135_p rofiles.tcl,tr140_profiles.tcl,tr143_profiles.tcl,tr157_profiles .tcl,tr196_profiles.tcls,cwmp_profiles.tcl –trace –pt

For additional execution options, see the CDRouter User Guide or the CDRouter Quick Start Guide.

C D R o u t e r T R -069 U s e r G u i d e 6

QA Cafe ? 2009

3.Requirements and License

In order to run the CDRouter TR-069 or TR69-EDM add-ons, your license file must be updated to enable the CDRouter TR-069 functionality. Note that the TR69-EDM add-on requires the CDRouter TR-069. Please follow the instructions from support@bc0e41e4524de518964b7ddf on updating your license file to enable CDRouter TR-069 and TR69-EDM (if applicable). CDRouter will report the status of all available add-ons during the installation process and during startup. To verify that the CDRouter TR-069 or TR69-EDM add-ons are enabled on your system, execute the command buddy –info as root and look for the lines “TR69 is enabled” and “TR69-EDM is enabled”. If these lines are present, the CDRouter TR-069 and TR69-EDM add-ons are enabled and ready to use. Copyright (c) 2001-2009 by QA Cafe Built on 2009-05-22 on seagull, pktsrc version 5.0 build 194

Using license installed at: /etc/cdr-mp.lic Registered to: qacafe Maintenance, Support and Upgrades until: 2010-03-10 Licensed to run: cdr-mp Buddyweb is enabled IKE is enabled TR69 is enabled TR69-EDM is enabled

INFO(setup): Starting buddy Mon May 25 18:04:49 EDT 2009 INFO(setup): Loaded OS version Linux-2.6.24-18-generic i686 INFO(setup): Loaded Tcl version 8.5.0 INFO(setup): Loaded buddy version 1.45 INFO(setup): (buildd@terranova) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7))

C D R o u t e r T R -069 U s e r G u i d e 7 QA Cafe ? 2009

4.Configuration

ACS Configuration

The ACS has several configuration entries to control its setup. The following table describes each entry.

C D R o u t e r T R -069 U s e r G u i d e 8 QA Cafe ? 2009

C D R o u t e r T R -069 U s e r G u i d e 9 QA Cafe ? 2009

C D R o u t e r T R -069 U s e r G u i d e 10 QA Cafe ? 2009

C D R o u t e r T R -069 U s e r G u i d e 11 QA Cafe ? 2009

Additional TR-069 Parameters

C D R o u t e r T R -069 U s e r G u i d e 12 QA Cafe ? 2009 There are a few additional parameters that control the overall behavior of CDRouter TR-069.

C D R o u t e r T R -069 U s e r G u i d e 13 QA Cafe ? 2009

C D R o u t e r T R -069 U s e r G u i d e 14 QA Cafe ? 2009

C D R o u t e r T R -069 U s e r G u i d e 15 QA Cafe ? 2009

C D R o u t e r T R -069 U s e r G u i d e 16

QA Cafe ? 2009

Example 1. CDRouter TR-069 Basic Configuration

In the example below, CDRouter is configured with the CPE Connection Request URL so that it can initiate new TR-069 sessions from the start. The CPE Connection Request username and password are statically configured on the CPE and the CPE is also configured with the username and password of the ACS. testvar acsIp 6.0.0.1 testvar acsPort 80 testvar acsTransport http testvar acsAuth digest testvar acsDigestQopAuth yes testvar acsCpeConnReqURL http://192.168.200.2:80/XML/000FCC-23570008.xml testvar acsDeviceDiscovery no testvar acsDefaultUser 000FCC-23570008 testvar acsDefaultPassword acs123 testvar acsCpeDefaultUser cpeurl testvar acsCpeDefaultPassword cpe123 testvar tr69InitiateConnection yes testvar tr69DownloadImage /home/user/fw_image_ver2.bin

C D R o u t e r T R -069 U s e r G u i d e 17

QA Cafe ? 2009 Example 2. CDRouter TR-069 Configuration with Device Discovery In the example below, CDRouter is configured to use device discovery by configuring testvar acsDeviceDiscovery to yes. When the first Inform is received from the device, CDRouter will attempt to configure the CPE Connection Request URL username and password. The CPE is also configured with the username and password of the ACS.

testvar acsIp 6.0.0.1 testvar acsPort 80 testvar acsTransport http testvar acsAuth digest testvar acsDigestQopAuth yes testvar acsWaitForInform 120 testvar acsDeviceDiscovery yes testvar acsDefaultUser 000FCC-23570008 testvar acsDefaultPassword acs123 testvar acsCpeDefaultUser cpeurl testvar acsCpeDefaultPassword cpe123 testvar tr69InitiateConnection yes testvar tr69DownloadImage /home/user/fw_image_ver2.bin Firmware Upgrade

CDRouter-TR-069 contains support for downloading new images to the CPE as part of the PD-128 firmware download tests. To enable firmware download tests, the path to the desired firmware image must be configured with the testvar tr69DownloadImage . The full path to the file should be used. By default, CDRouter TR-069 will wait up to 5 minutes for a download to complete. This is generally sufficient for a 1 – 3 megabyte image file. For larger image files, the download timeout can be adjusted by configuring the testvar tr69DownloadTimeout .

Log Messages

CDRouter TR-069 protocol messages can be filtered out using the –show and –hide options from the command-line or the BuddyWeb Advanced Tab. The following protocols are specific to CDRouter TR-069: ACS All ACS protocol messages Examples: To show only ACS log messages % buddy –show ACS

To exclude all ACS related messages

% buddy –hide ACS

C D R o u t e r T R -069 U s e r G u i d e 18 QA Cafe ? 2009

5.TR-111 Parts 1 and 2

CDRouter TR-069 supports TR-111 Parts 1 and 2. By default, support for TR-111 Part 1 and 2 is disabled. NOTE: TR-111 Parts 1 and 2 have been incorporated into the TR-069 specification as Annexes F and G, respectively, starting with TR-069 Amendment 1. This functionality (as defined in Annexes F and G of TR-069 Amendments 1 and 2) is referenced as TR-111 Part 1 and TR-111 Part 2 within CDRouter TR-069.

TR-111 Part 1

Support for TR-111 Part 1 in an IGD device under test can be enabled by configuring the testvar supportsTr111Part1 to yes. This testvar defaults to no. When TR-111 Part 1 is enabled, CDRouter can run the TR-111 Part 1 tests from the pd128.tcl module. There is also an additional tr111_part1.tcl module with additional coverage of TR-111 Part 1. During any TR-111 Part 1 testing, CDRouter will create LAN side devices to associate with the IGD device. NOTE: TR-111 Part 1 testing requires at least 1 Ethernet LAN interface.

TR-111 Part 2

Support for TR-111 Part 2 in an IGD device or LAN side TR-069 device under test can be enabled by configuring the testvar supportsTr111Part2 to yes. This testvar defaults to no. When TR-111 Part 2 is enabled, CDRouter will attempt to read the NATDetected and UDPConnectionRequestAddress parameters when it first learns about a TR-069 device. CDRouter will also enable STUN on the device and setup active notification of these parameters. If NAT is detected and the UDPConnectionRequestAddress is provided, CDRouter will switch to UDP style connection request attempts instead of TCP based requests. By default, the ACS STUN server does not require authentication on STUN Binding Requests. When the ACS configures the STUN settings on the CPE, it automatically generates a STUN username and STUN password for the CPE. The ACS server will only require authenticated STUN Binding Requests when the testvar STUNAuth is test to yes. The ACS will configure the maximum and minmum STUN keep alive intervals to 60 seconds by default. These can be changed using the testvars STUNMaximumKeepAlivePeriod and STUNMinimumKeepAlivePeriod .

C D R o u t e r T R -069 U s e r G u i d e 19

QA Cafe ? 2009 bc0e41e4524de518964b7ddfN Side TR-069 Devices

Starting with CDRouter TR-069 release 3.8, LAN side TR-069 aware devices can be tested using the pd128.tcl test module. When testing a LAN side TR-069 device, the device must be connected to an IGD device that provides a WAN connection and NAT. Since the LAN side device is now behind NAT, the device must either support TR-111 Part 2 or a port mapping must be created on the IGD. When working with port mappings on the IGD, CDRouter must either be configured with a URL that works with the port mapping on the IGD, or CDRouter can create a port mapping dynamically. CDRouter TR-069 currently supports testing TR-104 VoIP and TR-135 STB devices using the pd128.tcl module. LAN side TR-069 devices can be configured using testvar groups. Each LAN side TR-069 device must be named tr069_device2 through tr069_device8. The testvar group contains configuration items unique to each TR-069 LAN side device. Only a small number of testvars are required for each LAN device. When LAN side TR-069 devices are used, the Serial Number and OUI for all TR-069 devices must be configured. To tell CDRouter to run all test cases against a LAN side TR-069 device instead of the normal IGD device, the global testvar acsTargetDevice must be set to the testvar group name of the desired LAN side device. Otherwise, CDRouter will default to running all TR-069 tests against the IGD defined in the main CDRouter configuration. The following table describes each entry available to LAN side TR-069 devices:

C D R o u t e r T R -069 U s e r G u i d e 20 QA Cafe ? 2009

C D R o u t e r T R -069 U s e r G u i d e 21

QA Cafe ? 2009

Example 1. LAN side TR-104 device with TR-111 Part 2

In the example below, CDRouter is assumed to already have a working configuration for an IGD device with TR-069 enabled. A new device with TR-104 and TR-111 support has been added to the LAN side of the IGD. The following configuration will allow CDRouter to run all TR-069 related tests against the LAN side TR-104 device. testvar acsTargetDevice tr069_device2 testvar supportsTr111Part2 yes testvar_group tr069_device2 { testvar acsDefaultUser myata testvar acsDefaultPassword qacafe123 testvar tr69DeviceOui 001122 testvar tr69DeviceSn 123 testvar tr69DownloadImage /home/files/myata.bin testvar tr69DeviceType VoIP

}

Example 2. LAN side TR-135 device with static Port Mapping on IGD In the example below, CDRouter is assumed to already have a working configuration for an IGD device with TR-069 enabled. A new device with TR-135 support has been added to the LAN side of the IGD. The device does not support TR-111 and a port mapping has been created on the IGD device with a public IP address of 192.168.200.2. The LAN side device must define a URL that can be used through the IGD for the normal TCP based connection request mechanism. The following configuration will allow CDRouter to run all TR-069 related tests against the LAN side TR-135 device. testvar acsTargetDevice tr069_device3 testvar supportsTr111Part2 no

本文来源：https://www.bwwdw.com/article/pxhl.html