0% found this document useful (0 votes)

148 views

TP-181 - CWMP Interoperability and Functionality Test Plan

TP-181 – CWMP Interoperability and Functionality Test Plan

Uploaded by

Óscar Leal

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

148 views

TP-181 - CWMP Interoperability and Functionality Test Plan

TP-181 – CWMP Interoperability and Functionality Test Plan

Uploaded by

Óscar Leal

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

TP-181 – CPE WAN Management

Protocol (TR-069)
Issue: 1 Amendment 2 (release-1.2-5)

Issue Date: January 2022

1 Purpose and Scope

1.1 Purpose
1.2 Scope
1.3 Test Execution
2 References and Terminology
2.1 Conventions
2.2 References
2.3 Abbreviations
3 Test Plan Impact
3.1 Energy Efficiency
3.2 IPv6
3.3 Security
4 Test Setup
4.1 Test Equipment
4.2 Test Setup and Execution
4.2.1 Common Test Setup
4.2.2 Determine WAN Interface
4.2.3 Test Execution
4.3 CPE Test Requirements and Prerequisites
4.4 ACS Test Requirements
4.5 Interoperability Testing
4.6 Test Validation
5 Test Procedures
5.1 Basic Setup
5.1.1 Factory Reset

January 2022 © The Broadband Forum. All rights reserved. 1 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.1.2 Time Setting (Device:2 Only)

5.1.3 Time Setting (InternetGatewayDevice:1 Only)
5.1.4 Firmware Download
5.1.5 GetRPCMethods
5.1.6 Configuration Backup and Restoration
5.1.7 PPP Interface Change
5.1.8 DHCP Provisioning
5.1.9 SPV on a Boolean Parameter
5.1.10 Encrypted Connection
5.1.11 GetParameterNames Vendor Specific Parameters
5.1.12 SetParameterValues Vendor Specific Parameters
5.2 Diagnostics
5.2.1 Diagnostics IPPing
5.2.2 Download Diagnostics over HTTP
5.2.3 Download Diagnostics over FTP
5.2.4 Upload Diagnostics over HTTP
5.2.5 Upload Diagnostics over FTP
5.2.6 TraceRoute
5.2.7 UDPEcho Test
5.3 Statistics and Monitoring
5.3.1 Current Interface Configuration (Device:2 Only)
5.3.2 Connected LAN Devices (InternetGatewayDevice:1 Only)
5.3.3 Connected LAN Devices – Wi-Fi (Device:2 Only)
5.3.4 Connected LAN Devices – DHCP (Device:2 Only)
5.3.5 Device Connect/Disconnect Notification Test
5.4 Port Mappings
5.4.1 Create a Port Mapping – Single Interface
5.4.2 Create a Port Mapping – All Interfaces (Device:2 only)
5.4.3 Create a Port Mapping – External Port Range
5.4.4 Create a Port Mapping – Lease Duration > 0
5.4.5 Create a Port Mapping – Remote Host Restriction
5.4.6 Create a Port Mapping – Multiple Entries – Precedence Rules
5.4.7 Modify a Port Mapping
5.4.8 Delete a Port Mapping
5.4.9 Create a Port Mapping – TCP
5.5 Advanced Firewall

January 2022 © The Broadband Forum. All rights reserved. 2 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.5.1 Default Policy (Device:2 Only)

5.5.2 Deny/Allow Outbound Protocols (Device:2 Only)
5.5.3 Deny/Allow Outbound Ports (Device:2 Only)
5.5.4 Deny/Allow Source IP Address (Device:2 Only)
5.6 Wi-Fi Provisioning
5.6.1 Wi-Fi Setup WEP 64 (InternetGatewayDevice:1 Only)
5.6.2 Wi-Fi Setup WEP 128 (InternetGatewayDevice:1 Only)
5.6.3 Wi-Fi Setup WPA Personal (InternetGatewayDevice:1 Only)
5.6.4 Wi-Fi Setup WPA2 Personal (InternetGatewayDevice:1 Only)
5.6.5 Wi-Fi Setup WPA-WPA2 Personal (InternetGatewayDevice:1 Only)
5.6.6 Wi-Fi Setup WEP 64 (Device:2 Only)
5.6.7 Wi-Fi Setup WEP 128 (Device:2 Only)
5.6.8 Wi-Fi Setup WPA Personal (Device:2 Only)
5.6.9 Wi-Fi Setup WPA Enterprise (Device:2 Only)
5.6.10 Wi-Fi Setup WPA2 Personal (Device:2 only)
5.6.11 Wi-Fi Setup WPA2 Enterprise (Device:2 Only)
5.6.12 Wi-Fi Setup WPA-WPA2 Personal (Device:2 Only)
5.6.13 Wi-Fi Setup WPA-WPA2 Enterprise (Device:2 Only)
5.6.14 Wi-Fi Setup WPA3 Personal (Device:2 only)
5.6.15 Wi-Fi Setup WPA3-Personal-Transition (Device:2 only)
5.6.16 Wi-Fi Setup WPA3-Enterprise (Device:2 only)
5.6.17 Wi-Fi Setup – Add SSID (Device:2 Only)
5.6.18 Wi-Fi Setup – Remove SSID (Device:2 Only)
5.7 Localized Strings
5.7.1 Non-Printable ASCII Characters in SetParameterValues RPC (Device:2 Only)
5.7.2 Multi-Byte Encoding in SetParameterValues RPC (Device:2 Only)
5.7.3 Non-ASCII Characters in ParameterKey (Device:2 Only)
5.7.4 Multi-Byte Encoding in ParameterKey (Device:2 Only)
5.7.5 Non-ASCII Characters in CommandKey (Device:2 Only)
5.7.6 Multi-Byte Encoding in CommandKey (Device:2 Only)
5.8 Configuration Backup and Restore – Incorrect Backup File
5.9 DHCP Provisioning – Disable DHCP
5.10 Diagnostics IPPing – Error Condition
5.11 TraceRoute Diagnostics – Error Condition
5.12 IPPing Diagnostics – Periodic Inform
5.13 Deny/Allow Inbound IPv6 (Device:2 Only)
5.14 Download Diagnostics over HTTPS – TotalBytesReceived

January 2022 © The Broadband Forum. All rights reserved. 3 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.15 Upload Diagnostics over HTTP - TotalBytesSent

6 Open Issues

List of Figures

1. Common Topology for Interoperability Testing

List of Tables

1. Required Test Equipment

January 2022 © The Broadband Forum. All rights reserved. 4 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Notice

The Broadband Forum is a non-profit corporation organized to create guidelines for broadband
network system development and deployment. This Test Plan is owned and copyrighted by the
Broadband Forum, and portions of this Test Plan may be owned and/or copyrighted by
Broadband Forum members.

Intellectual Property

Recipients of this document are requested to submit, with their comments, notification of any
relevant patent claims or other intellectual property rights of which they may be aware that might
be infringed by any implementation of this Test Plan, and to provide supporting documentation.

Recipients of this document may use it (a) for internal review and study purposes, (b) to provide
to the Broadband Forum the comments and notification requested in the preceding paragraph,
and (c) if the Recipient is a Broadband Forum member, to implement the Test Plan in a product
or service made commercially available. Any other use of this Test Plan is expressly prohibited
without the prior written consent of the Broadband Forum.

THIS TEST PLAN IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN
PARTICULAR, ANY WARRANTY OF NONINFRINGEMENT AND ANY IMPLIED WARRANTIES
ARE EXPRESSLY DISCLAIMED. ANY USE OF THIS TEST PLAN SHALL BE MADE ENTIRELY
AT THE USER’S OR IMPLEMENTER’S OWN RISK, AND NEITHER THE FORUM, NOR ANY
OF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY
USER, IMPLEMENTER OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE
WHATSOEVER, DIRECTLY OR INDIRECTLY, ARISING FROM THE USE OF THIS TEST
PLAN, INCLUDING BUT NOT LIMITED TO, ANY CONSEQUENTIAL, SPECIAL, PUNITIVE,
INCIDENTAL AND INDIRECT DAMAGES.

All copies of this Test Plan (or any portion hereof) must include the notices, legends and other
provisions set forth on this page.

January 2022 © The Broadband Forum. All rights reserved. 5 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

January 2022 © The Broadband Forum. All rights reserved. 6 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Issue History

Issue 1 25 25 January Tim Original

January 2019 Winters,
2019 UNH-
IOL
Marion
Dillon,
UNH-
IOL

Issue 1 22 22 Jason Clarifications to tests 5.1.8,

Corrigendum September September Walls, 5.5.1, 5.5.2, and incorrect
1 2020 2020 QA parameter name
Cafe (DestinationInterface →
DestInterface)

Issue 1 27 27 January Jason Adds WPA3 tests

Amendment January 2022 Walls, Moves document to web
2 2022 QA publishing
Cafe

Comments or questions about this Broadband Forum Test Plan should be directed to
[email protected].

Editors

Jason Walls, QA Cafe, [email protected]

Broadband User Services Work Area Director(s)

Jason Walls, QA Cafe

John Blackford, CommScope

January 2022 © The Broadband Forum. All rights reserved. 7 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Executive Summary
In order to ensure the continued growth of the TR-069 market and further the interoperability of
the protocol, the Broadband Forum is creating a TR-069 Certification Program. Within this
program, devices implementing a TR-069 management interface may be tested for their
conformance to the TR-069 specification and various use cases. The TR-069 Certification
Program started with the TR-069 Conformance Test Plan and now the CWMP Data Model
Implementation Test Plan. To provide a consistent scope for this verification, BBF developed
these test plans that are to be used by the testing agencies in the verification process.

This Test Plan provides a test plan that may be used to verify Interoperability of a CPE Device
with an ACS Server through use cases.

January 2022 © The Broadband Forum. All rights reserved. 8 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1 Purpose and Scope

1.1 Purpose
The purpose of this document is to provide a set of use test cases, which will be used as a
common testing language during Interoperability testing of a CPE Device with an ACS Server.

1.2 Scope
The tests detailed in this document are only intended to facilitate TR-069 interoperability use
case testing. The tests in this document are limited to ACSs and CWMP enabled CPE devices.

1.3 Test Execution

The tests detailed in this document are to be run in a controlled environment. There is no
specified order to the tests in this document.

January 2022 © The Broadband Forum. All rights reserved. 9 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

2 References and Terminology

2.1 Conventions
In this Test Plan, several words are used to signify the requirements of the specification. These
words are always capitalized. More information can be found be in RFC 2119 [4].

MUST This word, or the terms “REQUIRED”, means that the definition is an
absolute requirement of the specification.

MUST NOT This phrase means that the definition is an absolute prohibition of the
specification.

SHOULD This word, or the adjective “RECOMMENDED”, means that there could
exist valid reasons in particular circumstances to ignore this item, but the
full implications need to be understood and carefully weighed before
choosing a different course.

SHOULD This phrase, or the phrase “NOT RECOMMENDED” means that there
NOT could exist valid reasons in particular circumstances when the particular
behavior is acceptable or even useful, but the full implications need to be
understood and the case carefully weighed before implementing any
behavior described with this label.

MAY This word, or the adjective “OPTIONAL”, means that this item is one of
an allowed set of alternatives. An implementation that does not include
this option MUST be prepared to inter-operate with another
implementation that does include the option.

2.2 References
The following references are of relevance to this Test Plan. At the time of publication, the
editions indicated were valid. All references are subject to revision; users of this Test Plan are
therefore encouraged to investigate the possibility of applying the most recent edition of the
references listed below, including any released amendments or corrigendum materials.

A list of currently valid Broadband Forum Technical Reports is published atwww.broadband-

January 2022 © The Broadband Forum. All rights reserved. 10 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

forum.org.

[1] IR-069 Issue 2, TR-069 Conformance Test Plan, Broadband Forum, 2016
[2] OD-361, CWMP Certification Program Guidelines, Broadband Forum, 2016
[3] REC-xml, Extensible Markup Language (XML) 1.0 (Fifth Edition), W3C, 2008
[4] RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, IETF, 1997
[5] RFC 2131, Dynamic Host Configuration Protocol, IETF
[6] RFC 2132, DHCP Options and BOOTP Vendor Extensions, IETF
[7] RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6), IETF, 2003
[8] TR-069 Amendment 6, CPE WAN Management Protocol, Broadband Forum, 2018
[9] TR-098 Amendment 2 Corrigendum 1, Internet Gateway Device Data Model for TR-069,
Broadband Forum, 2014
[10] TR-181 Issue 2, Device Data Model, Broadband Forum

2.3 Abbreviations
This Test Plan uses the following abbreviations:

ACS Auto-Configuration Server

CN Common Name

CPE Customer Premise Equipment

CWMP CPE WAN Management Protocol

DHCP Dynamic Host Configuration Protocol

DNS Domain Name System

DSLAM DSL Access Multiplexer

DUT Device Under Test

FTP File transfer Protocol

HTTP Hypertext Transfer Protocol

HTTPS Hypertext Transfer Protocol over Secure Socket Layer

ID Identifier

IP Internet Protocol

IPv6 Internet Protocol version 6

January 2022 © The Broadband Forum. All rights reserved. 11 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

LAN Local Area Network

NAT Network Address Translation

NTP Network Time Protocol

RFC Request for Proposal

RPC Remote Procedure Call

SOAP Simple Object Access Protocol

SSL Secure Socket Layer

STB Set Top Box

STUN Session Traversal Utilities for NAT

TCP Transmission Control Protocol

TFTP Trivial File transfer Protocol

TLS Transport Layer Security

TR Technical Report

TTL Time to Live

UDP User Datagram Protocol,

URL Universal Resource Locator

URN Uniform Resource Name

UTC Coordinated Universal Time

UTF Universal Multiple-Octet Coded Character Set Transformation

Format

UUID Universally Unique Identifier

VoIP Voice over Internet Protocol

WAN Wide Area Network

XML Extensible Markup Language

WA Work Area

January 2022 © The Broadband Forum. All rights reserved. 12 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

3 Test Plan Impact

3.1 Energy Efficiency

TP-181 has no impact on Energy Efficiency.

3.2 IPv6
TP-181 intends to support the IPv6 protocol. However, in this issue of the Working Text, IPv6
specific test cases have not been identified.

3.3 Security
TP-181 requires the use of authentication when connecting CPE to an ACS. Use of an HTTPS
URL indicates that the CPE can establish an SSL or TLS connection to the ACS.

January 2022 © The Broadband Forum. All rights reserved. 13 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

4 Test Setup

4.1 Test Equipment

The necessary set of test equipment to deliver reliable and repeatable test results is specified in
Table 1.

Table 1: Required Test Equipment

ACS The ACS is an interoperability partner in this test plan

Traffic To verify certain test metrics, Traffic Analyzers MUST be present between
Analyzer the CPE and ACS and between the CPE and any LAN Device

Access For infrastructure needs, an Access Node will be provided to bridge

Node connections between the CPE and ACS

File Server The File Server MUST support HTTP PUT & GET, as well as FTP PUT &
GET

CPE The CPE is an interoperability partner in this test plan

Network There may be one or more Network Routers between the CPE & ACS. If
Router the CPE is a LAN CPE, one Network Router may be configured to provide a
Network Address Translation (NAT) function

Firewall The Firewall MUST support the ability to selectively block traffic based on
IP address

NTP Two NTP Servers. Public NTP Servers such as NIST Internet Time Servers
Server may be used

RADIUS To authenticate end devices in WPA Enterprise test cases

Server

DHCP To assign addresses and other provisioning information to the CPE on the
Server WAN

DNS To resolve addresses on the WAN

Server

January 2022 © The Broadband Forum. All rights reserved. 14 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

LAN To connect to the LAN side of a Gateway CPE

Device

Wireless To connect to the LAN side of a Gateway CPE over wireless

LAN
Device

4.2 Test Setup and Execution

The Interoperability test setup is shown below in Figure 1. The following pieces of test equipment
needs to be connected to the Internet and reachable over IP, but there is no other topology
requirement: ACS, DHCP Server, DNS Server, File Server, NTP Server, RADIUS Server. The
Access Node may not be required if the primary CPE connection is Ethernet.

January 2022 © The Broadband Forum. All rights reserved. 15 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Figure 1: Common Topology for Interoperability Testing

4.2.1 Common Test Setup

This section describes the test setup shared between all test cases. Any additional setup steps
will be described in the “Test Setup” section of the test case.

1. ACS is connected to the network

2. CPE is connected to the network and configured with an ACS URL that corresponds to the
ACS in step 1.

3. Have a Network Analyzer to capture traffic between ACS and CPE.

4.2.2 Determine WAN Interface

This section describes steps to determine the WAN interface of a device. These steps are
referenced in the Test Procedures.

For CPE that support the Device:2 data model:

January 2022 © The Broadband Forum. All rights reserved. 16 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

The ACS performs a GetParameterNames RPC on the Interface table. The interface with the
WAN IP address is the WAN interface.

For CPE that support the InternetGatewayDevice:1 root data model [9]:

The ACS performs a GetParameterValues RPC on

InternetGatewayDevice.Layer3Forwarding.DefaultConnectionService. This will return the
WAN interface.

4.2.3 Test Execution

Each test is defined as a separate entity that can be run independent of all other test procedures.
These tests, performed sequentially, may cause changes to the ACS & CPE states during the
course of testing.

4.3 CPE Test Requirements and Prerequisites

1. OD-361 section 3.4.4 [2] states that passing IR-069i2 [1] is a prerequisite for a CPE
undergoing this test plan.

2. Each test case includes a References section that refers to a version of a data model
definition or other standard document. For all Broadband Forum data models and
Broadband Forum Technical Reports, the test case references the earliest version the CPE
can support to run the test case.

3. Each test case includes a Profiles section that includes the profiles needed to run the test
case. Any additional requirements are included in the Optional Features section. If the CPE
supports the profile and the optional feature listed, the test case MUST be run.

January 2022 © The Broadband Forum. All rights reserved. 17 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Note: For test cases that require Baseline:1 or Baseline:2 support, the CPE MUST
support each parameter listed in the test case, but does not need to support each
parameter in the profile.

A list of test cases by profile is included below. Note, there may be additional
parameters required or required parameter values. Refer to the test case for complete
information.

None 5.1.5 GetRPCMethods

5.1.10 Encrypted Connection

Baseline:1 5.1.1 Factory Reset

5.1.4 Firmware Download
5.1.6 Configuration Backup and
Restoration
5.1.9 SPV on a Boolean Parameter
5.7.1 Non-Printable ASCII Characters in
SetParameterValues RPC (Device:2 Only)
5.7.2 Multi-Byte Encoding in
SetParameterValues RPC (Device:2 Only)
5.7.3 Non-ASCII Characters in
ParameterKey (Device:2 Only)
5.7.4 Multi-Byte Encoding in ParameterKey
(Device:2 Only)
5.7.5 Non-ASCII Characters in
CommandKey (Device:2 Only)
5.7.6 Multi-Byte Encoding in CommandKey
(Device:2 Only)

Time:1 5.1.2 Time Setting (Device:2 Only)

PPPInterface:1 5.1.7 PPP Interface Change

DHCPv4Server:1 5.1.8 DHCP Provisioning

Vendor specific parameters 5.1.11 GetParameterNames Vendor

Specific Parameters
5.1.12 SetParameterValues Vendor
Specific Parameters

January 2022 © The Broadband Forum. All rights reserved. 18 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

IPPing:1 OR IPPingDetailed:1 5.2.1 Diagnostics IPPing

Download:1 5.2.2 Download Diagnostics over HTTP

5.2.3 Download Diagnostics over FTP

Upload:1 5.2.4 Upload Diagnostics over HTTP

5.2.5 Upload Diagnostics over FTP

TraceRoute:1 5.2.6 TraceRoute

UDPEcho:1 5.2.7 UDPEcho Test

Baseline:2, IPInterface:1, 5.3.1 Current Interface Configuration

EtherenetInterface:1, WiFiSSID:1, (Device:2 Only)
WiFiRadio:1

Hosts:2 5.3.3 Connected LAN Devices – Wi-Fi

(Device:2 Only)

Hosts:2, DHCPv4ServerClientInfo:1, 5.3.4 Connected LAN Devices – DHCP

DHCPv6ServerClientInfo (Device:2 Only)

Hosts:1 5.3.5 Device Connect/Disconnect

Notification Test

NAT:1 5.4.1 Create a Port Mapping – Single

Interface
5.4.2 Create a Port Mapping – All
Interfaces (Device:2 only)
5.4.3 Create a Port Mapping – External
Port Range
5.4.4 Create a Port Mapping – Lease
Duration > 0
5.4.5 Create a Port Mapping – Remote
Host Restriction
5.4.6 Create a Port Mapping – Multiple
Entries – Precedence Rules
5.4.7 Modify a Port Mapping
5.4.8 Delete a Port Mapping
5.4.9 Create a Port Mapping – TCP

January 2022 © The Broadband Forum. All rights reserved. 19 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

AdvancedFirewall:1 5.5.1 Default Policy (Device:2 Only)

5.5.2 Deny/Allow Outbound Protocols
(Device:2 Only)
5.5.3 Deny/Allow Outbound Ports (Device:2
Only)
5.5.4 Deny/Allow Source IP Address
(Device:2 Only)

WiFiRadio:1, WiFiSSID:1, 5.6.6 Wi-Fi Setup WEP 64 (Device:2 Only)

WiFiAccessPoint:1 5.6.7 Wi-Fi Setup WEP 128 (Device:2 Only)
5.6.8 Wi-Fi Setup WPA Personal (Device:2
Only)
5.6.9 Wi-Fi Setup WPA Enterprise
(Device:2 Only)
5.6.10 Wi-Fi Setup WPA2 Personal
(Device:2 only)
5.6.11 Wi-Fi Setup WPA2 Enterprise
(Device:2 Only)
5.6.12 Wi-Fi Setup WPA-WPA2 Personal
(Device:2 Only)
5.6.13 Wi-Fi Setup WPA-WPA2 Enterprise
(Device:2 Only)
5.6.14 Wi-Fi Setup WPA3 Personal
(Device:2 only)
5.6.15 Wi-Fi Setup WPA3-Personal-
Transition (Device:2 only)
5.6.16 Wi-Fi Setup WPA3-Enterprise
(Device:2 only)
5.6.17 Wi-Fi Setup – Add SSID (Device:2
Only)
5.6.18 Wi-Fi Setup – Remove SSID
(Device:2 Only)

January 2022 © The Broadband Forum. All rights reserved. 20 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

None 5.1.5 GetRPCMethods

5.1.10 Encrypted Connection

Baseline:1 5.1.1 Factory Reset

5.1.4 Firmware Download
5.1.6 Configuration Backup and
Restoration
5.1.9 SPV on a Boolean Parameter
5.3.5 Device Connect/Disconnect
Notification Test
5.4.1 Create a Port Mapping – Single
Interface
5.4.3 Create a Port Mapping – External
Port Range
5.4.4 Create a Port Mapping – Lease
Duration > 0
5.4.5 Create a Port Mapping – Remote
Host Restriction
5.4.6 Create a Port Mapping – Multiple
Entries – Precedence Rules
5.4.7 Modify a Port Mapping
5.4.8 Delete a Port Mapping
5.4.9 Create a Port Mapping – TCP

Time:2 5.1.3 Time Setting

(InternetGatewayDevice:1 Only)

Baseline:2 5.1.7 PPP Interface Change

5.3.2 Connected LAN Devices
(InternetGatewayDevice:1 Only)
5.1.8 DHCP Provisioning

Vendor specific parameters 5.1.11 GetParameterNames Vendor

Specific Parameters
5.1.12 SetParameterValues Vendor
Specific Parameters

January 2022 © The Broadband Forum. All rights reserved. 21 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Baseline:1, IPPing:1 5.2.1 Diagnostics IPPing

Download:1 5.2.2 Download Diagnostics over HTTP

5.2.3 Download Diagnostics over FTP

Upload:1 5.2.4 Upload Diagnostics over HTTP

5.2.5 Upload Diagnostics over FTP

TraceRoute:1 5.2.6 TraceRoute

UDPEcho:1 5.2.7 UDPEcho Test

WiFiLan:1 5.6.1 Wi-Fi Setup WEP 64

(InternetGatewayDevice:1 Only)
5.6.2 Wi-Fi Setup WEP 128
(InternetGatewayDevice:1 Only)
5.6.3 Wi-Fi Setup WPA Personal
(InternetGatewayDevice:1 Only)
5.6.4 Wi-Fi Setup WPA2 Personal
(InternetGatewayDevice:1 Only)
5.6.5 Wi-Fi Setup WPA-WPA2 Personal
(InternetGatewayDevice:1 Only)

4.4 ACS Test Requirements

The ACS MUST be configurable to include an interface that allows control of the ACS to execute
the test procedures. An API SHOULD be provided to the test lab to support automation of this
test plan. The ACS MUST allow its certificates to be configured.

4.5 Interoperability Testing

This test plan tests the ACS/CPE system, therefore a failure may indicate a deficiency from either
the ACS or CPE.

January 2022 © The Broadband Forum. All rights reserved. 22 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

4.6 Test Validation

A test is considered successful (or passed) when the corresponding test procedure has been
completed and the specified success metrics are attained. Tests can be validated by observing
functional changes in the DUTs, through feedback interfaces on the devices under test, results
attained from the ACS, and via a Traffic Analyzer connected to the relevant links.

January 2022 © The Broadband Forum. All rights reserved. 23 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5 Test Procedures

5.1 Basic Setup

5.1.1 Factory Reset

5.1.1.1 Purpose:

To verify that an ACS can perform a Factory Reset on the CPE.

5.1.1.2 References:

InternetGatewayDevice:1 [9]
Device:2 [10]

5.1.1.3 Profiles:

Baseline:1 Baseline:1

5.1.1.4 Optional Features:

Factory Reset RPC

5.1.1.5 Parameters:

The following parameter is required to be implemented for this test. CPE supports FactoryReset
RPC.
For CPE that support the Device:2 data model:

ProvisioningCode <string>

January 2022 © The Broadband Forum. All rights reserved. 24 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

For CPE that support the InternetGatewayDevice:1 [9] data model:

ProvisioningCode <string>

5.1.1.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.1.1.7 Procedure:

1. ACS performs a GetParameterValues RPC on the above parameter to determine its value.
2. ACS performs a SetParameterValues RPC on the above parameter for a value that is
different than the value returned in step 1.
3. ACS performs a FactoryReset RPC to the CPE.
4. Allow the ACS to perform bootstrap procedures on the CPE, if it is configured to do so.
5. ACS performs a GetParameterValues RPC on the above parameter.

5.1.1.8 Test Metrics:

1. Validate that the FactoryReset successfully occurs via FactoryResetResponse and a “0

BOOTSTRAP” Inform RPC is sent by CPE.
2. Validate that the value of the above parameter returned in step 5 is different than it was set
to in Procedure step 2.

5.1.2 Time Setting (Device:2 Only)

5.1.2.1 Purpose:

To verify that an ACS can set time configuration on the CPE.

5.1.2.2 References:

Device:2 [10]

January 2022 © The Broadband Forum. All rights reserved. 25 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.1.2.3 Profiles:

Time:1 N/A

5.1.2.4 Optional Features:

None

5.1.2.5 Parameters:

The following parameters are required to be implemented for this test:

Enable True

Status Returned from device

NTPServer1 <IP Address of NTP Server1>

NTPServer2 <IP Address of NTP Server2>

CurrentLocalTime Returned from device

LocalTimeZone <Local Time Zone definition in IEEE 1003.1 (POSIX)

format>

5.1.2.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have two NTP servers accessible on the WAN.
3. Have the ability to block data communications to the NTP Servers.

5.1.2.7 Procedure:

1. ACS performs a SetParameterValues RPC on the NTPServer1, NTPServer2, TimeZone,

and Enable parameters.
2. Test setup blocks NTPServer2 address.
3. CPE is rebooted.
4. ACS performs a GetParameterValues RPC on the Status and CurrentLocalTime parameters.
5. Test setup blocks NTPServer1 address and unblocks NTPServer2 address

January 2022 © The Broadband Forum. All rights reserved. 26 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

6. CPE is rebooted
7. ACS performs a GetParameterValues RPC on the Status and LocalTime parameters.

5.1.2.8 Test Metrics:

1. Validate that the SetParameterValuesResponse is received successfully for setting both

NTPServer1 and NTPServer2.
2. After the reboot, validate that the Traffic Analyzer shows CPE communication with
NTPServer1.
3. Validate that the time is set on the CPE via the GetParameterValuesResponse.
4. After the reboot, validate that the Traffic Analyzer shows CPE communication with
NTPServer2.
5. Validate that the time is set on the CPE via the GetParameterValuesResponse.

5.1.3 Time Setting (InternetGatewayDevice:1 Only)

5.1.3.1 Purpose:

To verify that an ACS can set time configuration on the CPE.

5.1.3.2 References:

InternetGatewayDevice:1 [9]

5.1.3.3 Profiles:

N/A Time:1

5.1.3.4 Optional Features:

None

5.1.3.5 Parameters:

January 2022 © The Broadband Forum. All rights reserved. 27 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

The following parameters are required to be implemented for this test:

NTPServer1 <IP Address of NTP

Server1>

NTPServer2 <IP Address of NTP

Server2>

CurrentLocalTime Returned from device

LocalTimeZone <Time Zone offset>

5.1.3.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have two NTP servers accessible on the WAN.
3. Have the ability to block data communications to the NTP Servers.

5.1.3.7 Procedure:

1. ACS performs a SetParameterValues RPC on the NTPServer1, NTPServer2, and TimeZone

parameters.
2. Test setup blocks NTPServer2 address.
3. CPE is rebooted.
4. ACS performs a GetParameterValues RPC on the LocalTime parameters.
5. Test setup blocks NTPServer1 address and unblocks NTPServer2 address
6. CPE is rebooted
7. ACS performs a GetParameterValues RPC on the CurrentLocalTime parameter.

5.1.3.8 Test Metrics:

1. Validate that the SetParameterValuesResponse is received successfully for setting both

January 2022 © The Broadband Forum. All rights reserved. 28 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.1.4 Firmware Download

5.1.4.1 Purpose:

To verify that an ACS can perform a firmware download on the CPE.

5.1.4.2 References:

InternetGatewayDevice:1 [9]
Device:2 [10]

5.1.4.3 Profiles:

Baseline:1 Baseline:1

5.1.4.4 Optional Features:

None

5.1.4.5 Parameters:

The following parameter is required to be implemented by the CPE for this test.
For CPE that support the Device:2 data model:

SoftwareVersion Returned from

device

For CPE that support the InternetGatewayDevice:1 data model:

SoftwareVersion Returned from

device

5.1.4.6 Test Setup:

January 2022 © The Broadband Forum. All rights reserved. 29 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. Refer to Common Test Setup for setup steps.

2. Have a file server accessible on the WAN with known credentials.
3. Place firmware to download on the file server.

5.1.4.7 Procedure:

1. ACS issues a GetParameterValues RPC on the CPE SoftwareVersion parameter listed in

the parameters section to learn the CPEs current software version
2. ACS issues a Download RPC to the CPE with the following arguments set

CommandKey <string>

FileType “1 Firmware Upgrade Image”

URL URL of firmware image on the file

server

Username File server username

Password File server password

FileSize Size of file to download in bytes

TargetFileName Name of the firmware to download

DelaySeconds

SuccessURL <empty>

FailureURL <empty>

Allow the CPE to complete firmware download from the file server, apply the firmware, and
reboot if necessary After CPE issues a “7 TRANSER COMPLETE” event code, the ACS issues a
GetParameterValues RPC on the on the CPE SoftwareVersion parameter listed in the
parameters section to learn the CPEs new software version

5.1.4.8 Test Metrics:

1. Ensure the software version reported by the CPE before the firmware download is different
than the software version reported by the CPE after the firmware download.

January 2022 © The Broadband Forum. All rights reserved. 30 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.1.5 GetRPCMethods

5.1.5.1 Purpose:

This test is designed to verify that the ACS can schedule a GetRPCMethods RPC to a CPE and
get back the correct response

5.1.5.2 References:

Section A.3.1.1/TR-069 [8]

5.1.5.3 Profiles:

N/A N/A

5.1.5.4 Optional Features:

None

5.1.5.5 Parameters:

None.

5.1.5.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.1.5.7 Procedure:

1. ACS schedules a GetRPCMethods RPC on the CPE.

2. Allow the CPE to respond with the GetRPCMethodsResponse

5.1.5.8 Test Metrics:

January 2022 © The Broadband Forum. All rights reserved. 31 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. Verify that the CPE responds to the GetRPCMethods RPC

2. Verify that the GetRPCMethodsResponse contains all mandatory RPCs

5.1.6 Configuration Backup and Restoration

5.1.6.1 Purpose:

This test is designed to verify that the ACS can schedule an upload of a CPE’s configuration and
then perform a restoration of that same configuration.

5.1.6.2 References:

Section A.4.1.5/TR-069a1 or later [8]

5.1.6.3 Profiles:

Baseline:1 Baseline:1

5.1.6.4 Optional Features:

Upload RPC

5.1.6.5 Parameters:

These arguments are for the Upload and Download RPCs. Note, if the CPE supports Upload
FileType “3 Vendor Configuration File <i>”, the test case MUST be run using that FileType.

CommandKey <string>

FileType “3 Vendor Configuration File <i>” OR “1 Vendor Configuration File”

URL URL of firmware image on the file server

Username File server username

Password File server password

January 2022 © The Broadband Forum. All rights reserved. 32 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

DelaySeconds

CommandKey <string>

FileType “3 Vendor Configuration File”

URL URL of configuration file on the file server

Username File server username

Password File server password

FileSize Size of file to download in bytes

TargetFileName Name of the configuration file to

download

DelaySeconds

SuccessURL <empty>

FailureURL <empty>

The following parameter path is required to be implemented for this test.

For CPE that support the Device:2 data model:

For CPE that support the InternetGatewayDevice:1 data model:

5.1.6.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a file server accessible on the WAN with known credentials that can accept uploads
and downloads.
3. If CPE supports “3 Vendor Configuration File <i>” Upload FileType, perform a
GetParameterValues RPC on the partial path above to determine the correct instance

January 2022 © The Broadband Forum. All rights reserved. 33 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

number to upload.

5.1.6.7 Procedure:

1. ACS performs a GetParameterValues RPC on PeriodicInformInterval to determine its value.

2. ACS schedules an Upload RPC on the CPE with the parameters above.
3. Allow the upload to complete.
4. ACS performs a SetParameterValues RPC on PeriodicInformInterval for a value that is
different than the value returned in step 1.
5. Wait for the CPE to send 2 Periodic Informs and check the interval between them.
6. ACS schedules a download RPC on the CPE with the parameters above.
7. Allow the download to complete.
8. Wait for the CPE to send 2 Periodic Informs and check the interval between them.

5.1.6.8 Test Metrics:

1. Verify that the CPE responds to the Upload RPC with an UploadResponse
2. Verify that the DUT uploaded the configuration to the server
3. Verify that the CPE sends Periodic Informs at the interval set in Step 4.
4. Verify that the CPE responds to the Download RPC with a DownloadResponse
5. Verify that the CPE sends Periodic Informs at the interval returned from the device in Step 1.

5.1.7 PPP Interface Change

5.1.7.1 Purpose:

This test is designed to verify that the ACS can configure the PPP interface of the CPE.

5.1.7.2 References:

InternetGatewayDevice:1.4
Device:2 [10]

5.1.7.3 Profiles:

January 2022 © The Broadband Forum. All rights reserved. 34 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

PPPInterface:1 Baseline:2

5.1.7.4 Optional Features:

None

5.1.7.5 Parameters:

This test is only applicable to CPE that use PPP to obtain an IP address. The following
parameters are required to be implemented for this test.
For CPE that support the Device:2 data model:

Username username1, username2

Password password1, password2

Reset true

For CPE that support the InternetGatewayDevice:1 data model:

Username username1,
username2

Password password1,
password2

Reset true

5.1.7.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Setup two valid sets of credentials on the PPP server, username1/password1 and
username2/password2

5.1.7.7 Procedure:

January 2022 © The Broadband Forum. All rights reserved. 35 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. ACS determines the instance number of the PPP interface.

2. ACS performs a GetParameterValues RPC on the CPE for Username and Password.
3. Allow the CPE to respond with a GetParameterValuesResponse
4. ACS performs a SetParameterValues RPC on the CPE for Username, Password, and Reset,
using the second set of valid credentials, username2/password2.
5. Allow the CPE to respond with a SetParameterValuesResponse and establish a new PPP
session.
6. ACS performs a GetParameterValues RPC on the CPE for Username and Password.
7. Allow the CPE to respond with a GetParameterValuesResponse.
8. Reboot the device.
9. ACS performs a GetParameterValues RPC on the CPE for Username and Password.

5.1.7.8 Test Metrics:

1. Validate that the CPE sends a GetParameterValuesResponse in step 3 containing

Username=username1 and Password=<empty string>.
2. Validate that the CPE sends a SetParameterValuesResponse in step 5 with Status=1 and
that the CWMP session is successfully ended.
3. Validate that the CPE successfully establishes a new PPP session using the new
credentials.
4. Validate that the CPE sends a GetParameterValuesResponse in step 7 containing
Username=username2 and Password=<empty string>.
5. Validate that the CPE sends a GetParameterValuesResponse in step 9 containing
Username=username2 and Password=<empty string>.

5.1.8 DHCP Provisioning

5.1.8.1 Purpose:

To verify that an ACS can configure the basic DHCPv4 configuration required on a CPE device.

5.1.8.2 References:

InternetGatewayDevice:1 [9]
Device:2 [10]
RFC 2131 [5]

January 2022 © The Broadband Forum. All rights reserved. 36 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

RFC 2132 [6]

RFC 3315 [7]

5.1.8.3 Profiles:

DHCPv4Server:1 Baseline:2

5.1.8.4 Optional Features:

DHCPLeaseTime is included in data model for CPE that support the InternetGatewayDevice:1
data model.

5.1.8.5 Parameters:

The following parameters are required to be implemented for this test.

For CPE that support the Device:2 root data model:

Enable true

Interface Returned from

device

MinAddress <minimum address>

MaxAddress <maximum address>

LeaseTime 60

For CPE that support the InternetGatewayDevice:1 root data model:

DHCPServerConfigurable true

DHCPServerEnable true

MinAddress <minimum
address>

January 2022 © The Broadband Forum. All rights reserved. 37 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

MaxAddress <maximum
address>

DHCPLeaseTime 60

5.1.8.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. CPE supports the appropriate DHCP parameters in the parameters section
3. Have a LAN device that can connect to the CPE via DHCP.
4. Have a Network Analyzer to capture traffic between the CPE and LAN device.
5. If the DUT implements the Device:2 root data model, determine whether or not an existing
entry exists for the object specified above.

5.1.8.7 Procedure:

1. If the DUT implements the Device:2 root data model, and no entry exists for
Device.DHCPv4.Server.Pool.{i}., perform an AddObject RPC on Device.Server.Pool.,
recording the InstanceNumber value returned in the AddObjectResponse.
2. On the ACS schedule a SetParameterValues RPC on the appropriate Configurable
parameters in the Parameters Section, setting the DHCP pool’s minimum and maximum to
be completely outside the existing range, if any (for example, by setting the new minimum
above the current maximum).
3. Allow the end system to connect to the CPE via DHCP.
4. Perform a reboot of the CPE
5. Allow the end system to connect to the CPE via DHCP

5.1.8.8 Test Metrics:

1. Verify that the SetParameterValuesResponse RPC is correct for all parameters

2. Verify that the end system connects to the CPE within the designated range.
3. Verify that that end system connects to the CPE within the designated range after the reboot

5.1.9 SPV on a Boolean Parameter

January 2022 © The Broadband Forum. All rights reserved. 38 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.1.9.1 Purpose:

This is a test case to verify that the ACS can change the Boolean on a CPE and receive the
correct response.

5.1.9.2 References:

Section A.3.2.1/TR-069a1 or later [8]

5.1.9.3 Profiles:

Baseline:1 Baseline:1

5.1.9.4 Optional Features:

None

5.1.9.5 Parameters:

Writable boolean parameter from the device’s data model.

5.1.9.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.1.9.7 Procedure:

1. ACS establishes a session

2. ACS performs a GetParameterValues RPC on the CPE on a Boolean parameter.
3. ACS schedules a SetParameterValues RPC on the CPE, to change the Boolean parameter
to the opposite of the value returned in step #2.
4. Allow the CPE to respond with the SetParameterValuesResponse.
5. ACS schedules a GetParameterValues RPC on the CPE, to request the Boolean parameter.
6. Allow the CPE to respond with the GetParameterValuesResponse

January 2022 © The Broadband Forum. All rights reserved. 39 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.1.9.8 Test Metrics:

1. Verify that the CPE responds to the SetParameterValues RPC

2. Verify that the SetParameterValuesResponse contains status 0.
3. Verify that the GetParameterValuesResponse contains the changed value.

5.1.10 Encrypted Connection

5.1.10.1 Purpose:

To verify that an ACS and CPE can interoperate using Encryption protocols.

5.1.10.2 References:

Section 3.3/TR-069a1 [8]

5.1.10.3 Profiles:

N/A N/A

5.1.10.4 Optional Features:

Secure CWMP

5.1.10.5 Parameters:

Readable Parameter from the device’s data model.

5.1.10.6 Test Setup:

1. Load the appropriate Certificate of Authentication onto the CPE.

2. Have the private portion of the certificate on the ACS.
3. Refer to Common Test Setup for setup steps.

January 2022 © The Broadband Forum. All rights reserved. 40 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.1.10.7 Procedure:

1. Allow the CPE to establish an encrypted CWMP session with the ACS.
2. On the ACS schedule a GetParametersValues RPC on the CPE.
3. Allow the CPE to respond with the GetParametersValuesResponse containing the requested
parameters.

5.1.10.8 Test Metrics:

1. Verify that the CWMP session is encrypted.

2. Verify that the GetParameterValuesResponse is valid.

5.1.11 GetParameterNames Vendor Specific Parameters

5.1.11.1 Purpose:

To verify that vendor specific CPE objects and parameters can be read and processed in an
ACS.

5.1.11.2 References:

Vendor supplied vendor-specific parameters

5.1.11.3 Profiles:

Vendor specific Vendor specific

parameters parameters

5.1.11.4 Optional Features:

None

5.1.11.5 Parameters:

January 2022 © The Broadband Forum. All rights reserved. 41 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Vendor supplied vendor specific parameter, type, and purpose. Vendor supplied vendor specific
object and purpose.

5.1.11.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Obtain a list of vendor specific parameters from the vendor

5.1.11.7 Procedure:

1. Allow the CPE to establish an CWMP session with the ACS

2. Schedule a GetParameterNames RPC on the CPE entire data model.

5.1.11.8 Test Metrics:

1. Verify that the ACS can process all vendor specific parameters and objects.

5.1.12 SetParameterValues Vendor Specific Parameters

5.1.12.1 Purpose:

To verify that vendor specific CPE parameter can be written by an ACS.

5.1.12.2 References:

Vendor supplied technical survey containing vendor specific information.

5.1.12.3 Profiles:

Vendor specific Vendor specific

parameters parameters

5.1.12.4 Optional Features:

January 2022 © The Broadband Forum. All rights reserved. 42 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

None

5.1.12.5 Parameters:

Vendor supplied vendor-specific parameter, type, and purpose.

5.1.12.6 Test Setup:

Refer to Common Test Setup for setup steps. Obtain a writable vendor specific parameter,
parameter type, and parameter purpose from the vendor.

5.1.12.7 Procedure:

1. ACS performs a GetParameterValues RPC on the parameter in Test Setup #3.

2. ACS performs a SetParameterValues RPC on the parameter in Test Setup #3 for a value
that is different than the value returned in Step 1.
3. ACS performs a GetParameterValues RPC on the parameter in Test Setup #3.
4. Reboot the device.
5. ACS performs a GetParameterValues RPC on the parameter in Test Setup #3.

5.1.12.8 Test Metrics:

1. Verify that the SetParameterValues RPC in Step 2 completes and the CPE responds with a
correct SetParameterValuesResponse RPC.
2. Verify that the GetParametersValues RPC in Step 3 completes and the CPE responds with a
correct GetParameterValuesResponse RPC.
3. Verify that the value in the GetParameterValues in Step 3 matches the value set in Step 2.
4. Verify that the value in the GetParameterValues in Step 5 matches the value set in Step 2.

5.2 Diagnostics

5.2.1 Diagnostics IPPing

5.2.1.1 Purpose:

January 2022 © The Broadband Forum. All rights reserved. 43 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

To verify that an ACS can perform an IP Ping Diagnostics test on the CPE.

5.2.1.2 References:

InternetGatewayDevice:1 [9]
Device:2 [10]

5.2.1.3 Profiles:

IPPing:1 OR IPPing:1, Baseline:1

IPPingDetailed:1

5.2.1.4 Optional Features:

None

device

FailureCount Returned from

device

DefaultConnectionService Returned
from device

5.2.1.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a host on the WAN network that can answer pings.
3. Refer to Determine WAN Interface to determine the WAN interface. This will be used for the
Interface parameter.

5.2.1.7 Procedure:

1. ACS performs a SetParameterValues RPC on the ping diagnostics parameters in the

parameter section above.

January 2022 © The Broadband Forum. All rights reserved. 45 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

2. ACS performs a GetParameterValues on the InternetGatewayDevice.IPPingDiagnostics or

Device.IP.Diagnostics.IPPing to determine results of ping test

5.2.1.8 Test Metrics:

1. Verify that the CPE transmitted 3 ICMP Echo Requests to the target Host.
2. Validate that the CPE sends an Inform RPC to the ACS with Event Code “8 DIAGNOSTICS
COMPLETE”.
3. Validate that the DiagnosticsState is set to “Complete”.
4. Verify that the SuccessCount and FailureCount match what is seen on the network capture.

5.2.2 Download Diagnostics over HTTP

5.2.2.1 Purpose:

To verify that an ACS and CPE can interoperate while performing the download diagnostics
function over HTTP. This test will be run if supported on the CPE.

5.2.2.2 References:

InternetGatewayDevice.1.3
Device:2 [10]

5.2.2.3 Profiles:

Download:1 Download:1

5.2.2.4 Optional Features:

None

5.2.2.5 Parameters:

The following parameters are required to be implemented for this test:

January 2022 © The Broadband Forum. All rights reserved. 46 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

For CPE that implement the Device:2 root data model:

DiagnosticsState Requested

Interface Returned from device

DownloadURL <URL of file on HTTP

server>

TestBytesReceived Returned from device

TotalBytesReceived Returned from device

DownloadTransports Returned from device

For CPE that implement the InternetGatewayDevice:1 root data model:

DiagnosticsState Requested

Interface Returned from device

DownloadURL <URL of file on HTTP

server>

TestBytesReceived Returned from device

TotalBytesReceived Returned from device

DownloadTransports Returned from

device

The DownloadTransports parameter MUST include HTTP for this test to be executed.

5.2.2.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an HTTP server and file to perform the download. The file should be big enough for the
file transfer to last at least 30 seconds.

5.2.2.7 Procedure:

January 2022 © The Broadband Forum. All rights reserved. 47 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. On the ACS schedule a SetParameterValues RPC on the Interface, DownloadURL and

DiagnosticsState parameters listed in the parameters section.
2. Allow the CPE to perform the specific diagnostic tests and send an Inform message with an
event code of “8 DIAGNOSTICS COMPLETE”.
3. On the ACS schedule a GetParameterValues RPC on the DownloadDiagnostics object.
4. Perform a reboot of the CPE.
5. On the ACS schedule a GetParameterValues RPC on the DownloadDiagnostics object.

5.2.2.8 Test Metrics:

1. Verify that the SetParameterValuesResponse RPC is correct

2. Verify that an Inform message is received with an event code of “8 DIAGNOSTICS
COMPLETE”
3. Verify that the GetParameterValuesResponse contains a valid value for the DiagnosticsState
parameter.
4. Verify that TestBytesReceived is correct.
5. Verify that EOMTime – BOMTime is within 1 second of the time that the file server reports
the transfer took.
6. Verify that the GetParameterValuesResponse contains a valid value for the DiagnosticsState
parameter.
1. If the value is “Completed” verify that the values in the DownloadDiagnostic object are
the same as they were before the reboot.
2. Verify that TotalBytesReceived is within 1% of the measured traffic.

5.2.3 Download Diagnostics over FTP

5.2.3.1 Purpose:

To verify that an ACS and CPE can inter-operate while performing the download diagnostics
function over FTP. This test will be run if supported on the CPE.

5.2.3.2 References:

InternetGatewayDevice.1.3
Device:2 [10]

January 2022 © The Broadband Forum. All rights reserved. 48 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.2.3.3 Profiles:

Download:1 Download:1

5.2.3.4 Optional Features:

DownloadTransports includes FTP

5.2.3.5 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

DiagnosticsState Requested

Interface Returned from device

DownloadURL <URL of file on FTP

server>

TestBytesReceived Returned from device

DownloadTransports Returned from device

For CPE that implement the InternetGatewayDevice:1 root data model:

DiagnosticsState Requested

Interface Returned from device

DownloadURL <URL of file on FTP

server>

TestBytesReceived Returned from device

TotalBytesReceived Returned from device

January 2022 © The Broadband Forum. All rights reserved. 49 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

DownloadTransports Returned from

device

The DownloadTransports parameter MUST include FTP for this test to be executed.

5.2.3.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an FTP server and file to perform the download. The file should be big enough for the
file transfer to last at least 30 seconds.

5.2.3.7 Procedure:

1. On the ACS schedule a SetParameterValues RPC on the Interface, DownloadURL and

5.2.3.8 Test Metrics:

1. Verify that the SetParameterValuesResponse RPC is correct

January 2022 © The Broadband Forum. All rights reserved. 50 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.2.4 Upload Diagnostics over HTTP

5.2.4.1 Purpose:

To verify that an ACS and CPE can inter-operate while performing the upload diagnostics
function over HTTP. This test will be run if supported on the CPE.

5.2.4.2 References:

InternetGatewayDevice.1.3
Device:2 [10]

5.2.4.3 Profiles:

Upload:1 Upload:1

5.2.4.4 Optional Features:

None

5.2.4.5 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

DiagnosticsState Requested

Interface Returned from device

UploadURL <URL of HTTP server>

TestFileLength <value long enough for the upload to last

30 seconds>

TotalBytesSent Returned from device

UploadTransports Returned from device

January 2022 © The Broadband Forum. All rights reserved. 51 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

For CPE that implement the InternetGatewayDevice:1 root data model:

DiagnosticsState Requested

Interface Returned from device

UploadURL <URL of HTTP server>

TestFileLength <value long enough for the upload to last

30 seconds>

TotalBytesSent Returned from device

UploadTransports Returned from

device

The UploadTransports parameter MUST include HTTP for this test to be executed.

5.2.4.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an HTTP server to perform the Upload.
3. Wireshark running between ACS and CPE.

5.2.4.7 Procedure:

1. On the ACS schedule a SetParameterValues RPC on the Interface, UploadURL and

DiagnosticsState parameters listed in the parameters section.
2. Allow the CPE to perform the specific diagnostic tests and send an Inform message with an
event code of “8 DIAGNOSTICS COMPLETE”.
3. On the ACS schedule a GetParameterValues RPC on the UploadDiagnostics object.
4. Perform a reboot of the CPE
5. On the ACS schedule a GetParameterValues RPC on the UploadDiagnostics object.

5.2.4.8 Test Metrics:

1. Verify that the SetParameterValuesResponse RPC is correct

2. Verify that an Inform message is received with an event code of “8 DIAGNOSTICS

January 2022 © The Broadband Forum. All rights reserved. 52 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

COMPLETE”
3. Verify that the GetParameterValuesResponse contains a valid value for the DiagnosticsState
parameter.
4. Verify that the test server received a file of TestLengthBytes size.
5. Verify that EOMTime – BOMTime is within 1 second of the time that the file server reports
the transfer took.
6. Verify that the GetParameterValuesResponse contains a valid value for the DiagnosticsState
parameter.
1. If the value is “Completed” verify that the values in the UploadDiagnostic object are the
same as they were before the reboot.
2. Verify that TotalBytesSent is within 1% of the measured traffic.

5.2.5 Upload Diagnostics over FTP

5.2.5.1 Purpose:

To verify that an ACS and CPE can inter-operate while performing the upload diagnostics
function over FTP. This test will be run if supported on the CPE.

5.2.5.2 References:

InternetGatewayDevice.1.3
Device:2 [10]

5.2.5.3 Profiles:

Upload:1 Upload:1

5.2.5.4 Optional Features:

UploadTransports includes FTP

5.2.5.5 Parameters:

January 2022 © The Broadband Forum. All rights reserved. 53 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

The following parameters within the InternetGatewayDevice.UploadDiagnostics table (for devices

that implement the InternetGatewayDevice:1 root data model) and
Device.IP.Diagnostics.UpLoadDiagnostics table (for devices that implement the Device:2 root
data model) are required to be implemented for this test:
For CPE that implement the Device:2 root data model:

DiagnosticsState Requested

Interface Returned from device

UploadURL <URL of FTP server>

TestFileLength <value long enough for the upload to last

30 seconds>

UploadTransports Returned from device

For CPE that implement the InternetGatewayDevice:1 root data model:

DiagnosticsState Requested

Interface Returned from device

UploadURL <URL of FTP server>

TestFileLength <value long enough for the upload to last

30 seconds>

UploadTransports Returned from

device

The UploadTransports parameter MUST include FTP for this test to be executed.

5.2.5.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an FTP server to perform the Upload.

5.2.5.7 Procedure:

January 2022 © The Broadband Forum. All rights reserved. 54 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. On the ACS schedule a SetParameterValues RPC on the Interface, UploadURL and

DiagnosticsState parameters listed in the parameters section.
2. Allow the CPE to perform the specific diagnostic tests and send an Inform message with an
event code of “8 DIAGNOSTICS COMPLETE”.
3. On the ACS schedule a GetParameterValues RPC on the UploadDiagnostics object.
4. Perform a reboot of the CPE
5. On the ACS schedule a GetParameterValues RPC on the UploadDiagnostics object.

5.2.5.8 Test Metrics:

1. Verify that the SetParameterValuesResponse RPC is correct

2. Verify that an Inform message is received with an event code of “8 DIAGNOSTICS
COMPLETE”
3. Verify that the GetParameterValuesResponse contains a valid value for the DiagnosticsState
parameter.
4. Verify that the test server received a file of TestLengthBytes size.
5. Verify that EOMTime – BOMTime is within 1 second of the time that the file server reports
the transfer took.
6. Verify that the GetParameterValuesResponse contains a valid value for the DiagnosticsState
parameter.
1. If the value is “Completed” verify that the values in the UploadDiagnostic object are the
same as they were before the reboot.

5.2.6 TraceRoute

5.2.6.1 Purpose:

This test is designed to validate that the CPE supports TraceRoute diagnostics test and reports
results appropriately to the ACS.

5.2.6.2 References:

InternetGatewayDevice:1.4
Device:2 [10]

5.2.6.3 Profiles:

January 2022 © The Broadband Forum. All rights reserved. 55 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

TraceRoute:1 TraceRoute:1

5.2.6.4 Optional Features:

None

5.2.6.5 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

DiagnosticsState Requested

Interface Returned from

device

Host <IP address>

NumberOfTries

Timeout 5000

DataBlockSize 128

DSCP

MaxHopCount 30

For CPE that implement the InternetGatewayDevice:1 root data model:

DiagnosticsState Requested

Interface Returned from

device

Host <IP address>

January 2022 © The Broadband Forum. All rights reserved. 56 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

NumberOfTries

Timeout 5000

DataBlockSize 128

DSCP

MaxHopCount 30

DefaultConnectionService Returned
from device

5.2.6.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a host on the WAN network that can answer the CPE’s traceroute mechanism.

5.2.6.7 Procedure:

1. Establish a CWMP session between the CWMP Analyzer and DUT with successful Inform
exchanges.
2. Schedule a GetParameterValues RPC on the current WAN interface.
3. Schedule a SetParameterValues RPC on the DUT on the trace route diagnostic parameters
listed above.
4. Schedule a GetParameterValues RPC on the DUT on Diagnostic State.
5. Schedule a GetParameterValues RPC on the CPE on the RouteHops table.

5.2.6.8 Test Metrics:

1. The DUT can properly respond to the GetParameterValues request on WAN interface.
2. The DUT is able to properly respond to the SetParameterValues for diagnostics parameter.
3. Verify that the CPE performed the TraceRoute test on the target Host.
4. Validate that the CPE sends an Inform RPC to the ACS with Event Code “8 DIAGNOSTICS

January 2022 © The Broadband Forum. All rights reserved. 57 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

COMPLETE”.
5. Validate that the DiagnosticsState is set to “Complete”.
6. Validate that the Entries in the RouteHops table match the traceroute traffic on the WAN.

5.2.7 UDPEcho Test

5.2.7.1 Purpose:

This test is designed to verify that the ACS can configure the UDPEcho service on the CPE and
that the CPE implements that service correctly.

5.2.7.2 References:

InternetGatewayDevice:1.3
Device:2 [10]

5.2.7.3 Profiles:

UDPEcho:1 UDPEcho:1

5.2.7.4 Optional Features:

None

5.2.7.5 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

Enable <boolean>

Interface <empty string>

SourceIPAddress <IP Address of UDP

Client>

January 2022 © The Broadband Forum. All rights reserved. 58 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

UDPPort <port>

PacketsReceived Returned from device

PacketsResponded Returned from device

For CPE that implement the InternetGatewayDevice:1 root data model:

Enable <boolean>

Interface <empty string>

SourceIPAddress <IP Address of UDP

Client>

UDPPort <port>

PacketsReceived Returned from device

PacketsResponded Returned from device

5.2.7.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. UDP client available at source to send UDPEcho packets

5.2.7.7 Procedure:

1. ACS schedules a SetParameterValues RPC on the CPE, setting Enable to false.

2. Allow the CPE to respond with the SetParameterValuesResponse
3. Orderly terminate the session
4. Use the UDP client at source to send n UDP Echo packets to the CPE
5. ACS schedules a SetParameterValues RPC on the CPE, setting the SourceIPAddress and
UDPPort that will be used, and setting Enable to true.
6. Allow the CPE to respond with the SetParameterValuesResponse
7. ACS schedules a GetParameterValues RPC on the CPE, reading PacketsReceived and
PacketsResponded.
8. Allow the CPE to respond with the GetParameterValuesResponse
9. Orderly terminate the session
10. Use the UDP client at source to send n UDP Echo packets to the CPE

January 2022 © The Broadband Forum. All rights reserved. 59 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

11. ACS schedules a GetParameterValues RPC on the CPE, reading PacketsReceived and
PacketsResponded.
12. Allow the CPE to respond with the GetParameterValuesResponse

5.2.7.8 Test Metrics:

1. CPE responds correctly to the various RPCs

2. During step 4, the UPD client receives no response packet
3. During step 7, the counters read have a value of zero
4. During step 10, the UPD client receives n response packets (no loss expected in the closed
test network)
5. During step 12, PacketsReceived and PacketsResponded are both n.

5.3 Statistics and Monitoring

5.3.1 Current Interface Configuration (Device:2 Only)

5.3.1.1 Purpose:

This test is designed to verify that the ACS can determine the current configuration of the
interfaces on the CPE.

5.3.1.2 References:

Section 4/TR-181i2

5.3.1.3 Profiles:

Baseline:2, IPInterface:1, EtherenetInterface:1, WiFiSSID:1, N/A

WiFiRadio:1

5.3.1.4 Optional Features:

January 2022 © The Broadband Forum. All rights reserved. 60 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

None

5.3.1.5 Parameters:

device

5.3.1.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.3.1.7 Procedure:

1. On the ACS schedule a GetParameterValues RPC for the InterfaceStack on the CPE.
2. Allow the CPE to respond with a GetParameterValuesResponse
3. On the ACS schedule a GetParameterValues on each interface returned in the
InterfaceStack.

5.3.1.8 Test Metrics:

1. Verify that the CPE responds to the GetParameterValues RPC.

2. Verify that the InterfaceStack table refers to objects that exist.
3. Verify that each entry in the InterfaceStack table corresponds to the correct LowerLayer.
4. Verify Enable, IPAddress and SubnetMask or MACAddress from all Interface objects.

5.3.2 Connected LAN Devices (InternetGatewayDevice:1 Only)

January 2022 © The Broadband Forum. All rights reserved. 62 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.3.2.1 Purpose:

This test is designed to verify that the ACS can determine the current connected LAN devices on
the CPE and get back the correct response

5.3.2.2 References:

InternetGatewayDevice:1.4

5.3.2.3 Profiles:

N/A Baseline:2

5.3.2.4 Optional Features:

None

5.3.2.5 Parameters:

The following parameters are required to be implemented for this test:

5.3.2.8 Test Metrics:

1. Verify that the CPE responds to the GetParameterValues RPC

2. Verify that the Layer2Interface parameter matches the InterfaceType parameter.
3. Verify that the values of the above parameters returned match each LAN device connected
to the CPE.
4. Verify that the Active parameter is set to “true”.

5.3.3 Connected LAN Devices – Wi-Fi (Device:2 Only)

5.3.3.1 Purpose:

This test is designed to verify that the ACS can determine the current connected LAN devices on
the CPE and get back the correct response

5.3.3.2 References:

January 2022 © The Broadband Forum. All rights reserved. 64 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Device:2.2

5.3.3.3 Profiles:

Hosts:2 N/A

5.3.3.4 Optional Features:

None

5.3.3.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have one LAN device connected on the Wi-Fi interface of the CPE.
3. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

5.3.3.7 Procedure:

1. Connect the LAN device so it is configured with an address.

2. On the ACS schedule a GetParameterValues RPC for Device.Hosts. on the CPE.
3. Allow the CPE to respond
4. On the ACS schedule a GetParameterValues RPC for the AssociatedDevice returned.
5. Allow the CPE to respond

5.3.3.8 Test Metrics:

1. Verify that the CPE responds to the GetParameterValues RPC

2. Verify that the values of the above parameters returned match the LAN device
3. Verify that the Active parameter is set to “true”
4. Verify that the value of SignalStrength is within the valid range
5. Verify that the value of Retransmissions is within the valid range

January 2022 © The Broadband Forum. All rights reserved. 66 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.3.4 Connected LAN Devices – DHCP (Device:2 Only)

5.3.4.1 Purpose:

This test is designed to verify that the ACS can determine the current connected LAN devices on
the CPE and get back the correct response

5.3.4.2 References:

Device:2.2 [10]
RFC 2131 [5]
RFC 2132 [6]
RFC 3315 [7]

5.3.4.3 Profiles:

Hosts:2, DHCPv4ServerClientInfo:1, N/A

DHCPv6ServerClientInfo:1

5.3.4.4 Optional Features:

None

1. Verify that the CPE responds to the GetParameterValues RPC

2. Verify that the values of the above parameters returned match the LAN device
3. Verify that Option Tag 61 is the DHCP client id
4. Verify that the Active parameter is set to “true”

5.3.5 Device Connect/Disconnect Notification Test

January 2022 © The Broadband Forum. All rights reserved. 69 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.3.5.1 Purpose:

This test is designed to verify that the ACS can determine when the set of LAN devices on the
CPE changes and get back the correct response

5.3.5.2 References:

Device:2 [10]
InternetGatewayDevice:1 [9]

5.3.5.3 Profiles:

Hosts:1 Baseline:1

5.3.5.4 Optional Features:

None

5.3.5.5 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

HostNumberOfEntries Returned from

device

Active Returned from

device

For CPE that implement the InternetGatewayDevice:1 root data model:

January 2022 © The Broadband Forum. All rights reserved. 70 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

HostNumberOfEntries Returned from

device

Active Returned from

device

5.3.5.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have one device connectable on each interface that the CPE supports.
3. Have a Network Analyzer to capture traffic between the CPE and each LAN device.

5.3.5.7 Procedure:

1. On the ACS schedule a SetParameterAttributes RPC with active notification on the CPE for
HostNumberOfEntries
2. Connect a device to the CPE on each interface the CPE supports.
3. Verify that the ACS receives a notification containing the HostNumberOfEntries parameter.
4. On the ACS schedule a SetParameterAttributes RPC with active notification on the CPE for
each host object’s active parameter (Host.{i}.Active).
5. Disconnect a device from the CPE
6. Verify that the ACS receives a notification containing the Active parameter.
7. Schedule a GetParameterNames RPC on the CPE for Host.

5.3.5.8 Test Metrics:

1. Verify that the CPE responds to the SetParameterAttributes RPC

2. Verify the CPE sends an Inform containing a “4 VALUE CHANGE” for each device that is
connected to the CPE. Verify the ParameterList includes the HostNumberOfEntries
parameter.
3. Verify the CPE sends an Inform containing a “4 VALUE CHANGE” when the device is
disconnected from the CPE. Verify the ParameterList includes the Host.{i}.Active parameter.
If the CPE does not list inactive host, verify that the GetParameterNames does not include
the Host instance of the inactive device.

January 2022 © The Broadband Forum. All rights reserved. 71 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.4 Port Mappings

5.4.1 Create a Port Mapping – Single Interface

5.4.1.1 Purpose:

To verify that an ACS can create a port mapping, the CPE can create the port mapping that the
ACS requested, and that internet traffic can traverse the port mapping.

5.4.1.2 References:

InternetGatewayDevice:1 [9]
Device:2 [10]

5.4.1.3 Profiles:

NAT:1 Baseline:1

5.4.1.4 Optional Features:

None

5.4.1.5 Parameters:

The following parameters are required to be implemented by the CPE for this test:

For devices that support the Device:2 root data model:

Enable true

Interface Returned from device

LeaseDuration

ExternalPort 1400

January 2022 © The Broadband Forum. All rights reserved. 72 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

InternalPort 1401

Protocol UDP

InternalClient <IP Address of the End Device

(laptop)>

For devices that support the InternetGatewayDevice:1 root data model:

PortMappingEnabled true

PortMappingLeaseDuration

ExternalPort 1400

InternalPort 1401

PortMappingProtocol UDP

InternalClient <IP Address of the End Device (laptop)>

5.4.1.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a LAN device connected to the LAN side of the CPE
3. Have a device connected on the WAN side of the CPE that can send UDP traffic.
4. ACS ensures that the port mapping being created doesn’t already exist by retrieving all
instances of the PortMapping table via a GetParamterValues RPC
1. If PortMapping already exists, remove it via the DeleteObject RPC
2. Refer to Determine WAN Interface to determine the WAN interface.
3. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

January 2022 © The Broadband Forum. All rights reserved. 73 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.4.1.7 Procedure:

1. ACS performs an AddObject RPC to create a new PortMapping instance.

2. ACS performs a SetParameterValues RPC on the parameters above using the returned
PortMapping instance number.
3. ACS performs a GetParameterValues RPC on the PortMapping instance.
4. Reboot the CPE.
5. ACS performs a GetParameterValues RPC on the PortMapping instance.
6. Send UDP traffic to the CPE’s IP Address with destination port 1400 from the WAN side of
the CPE.

5.4.1.8 Test Metrics:

1. Validate that the values of the PortMapping instance match the values that were set.
2. Validate that the CPE retains the PortMapping instance and configuration across a reboot.
3. Validate that the UDP traffic is forwarded to the LAN Device’s IP address, port 1401.

5.4.2 Create a Port Mapping – All Interfaces (Device:2 only)

5.4.2.1 Purpose:

To verify that an ACS can create a port mapping, the CPE can create the port mapping that the
ACS requested, and that internet traffic can traverse the port mapping.

5.4.2.2 References:

Device:2 [10]

5.4.2.3 Profiles:

NAT:1 N/A

5.4.2.4 Optional Features:

None

January 2022 © The Broadband Forum. All rights reserved. 74 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.4.2.5 Parameters:

The following parameters are required to be implemented by the CPE for this test:

Enable true

AllInterfaces true

LeaseDuration

ExternalPort 1400

InternalPort 1401

Protocol UDP

InternalClient <IP Address of the End Device

(laptop)>

5.4.2.6 Test Setup:

1. Refer to Common Test Setup for setup steps. Have a LAN device connected to the LAN
side of the CPE Have a device connected on the WAN side of the CPE that can send UDP
traffic. ACS ensures that the port mapping being created doesn’t already exist by retrieving
all instances of the PortMapping table via a GetParamterValues RPC
1. If PortMapping already exists, remove it via the DeleteObject RPC
2. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

5.4.2.7 Procedure:

1. ACS performs an AddObject RPC to create a new PortMapping instance.

2. ACS performs a SetParameterValues RPC on the parameters above using the returned
PortMapping instance number.
3. ACS performs a GetParameterValues RPC on the PortMapping instance.
4. Send UDP traffic to the CPE’s IP Address with destination port 1400 from the WAN side of
the CPE.

5.4.2.8 Test Metrics:

January 2022 © The Broadband Forum. All rights reserved. 75 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. Validate that the values of the PortMapping instance match the values that were set.
2. Validate that the UDP traffic is forwarded to the LAN Device’s IP address, port 1401.

5.4.3 Create a Port Mapping – External Port Range

5.4.3.1 Purpose:

To verify that an ACS can create a port mapping, the CPE can create the port mapping that the
ACS requested, and that internet traffic can traverse the port mapping.

5.4.3.2 References:

InternetGatewayDevice:1.4
and Device:2 [10]

5.4.3.3 Profiles:

NAT:1 Baseline:1

5.4.3.4 Optional Features:

ExternalPortEndRange is included in Data Model

5.4.3.5 Parameters:

The following parameters required to be implemented for this test:

For devices that support the Device:2 root data model:

Enable true

Interface Returned from device

LeaseDuration

ExternalPort 1400

January 2022 © The Broadband Forum. All rights reserved. 76 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

ExternalPortEndRange 1405

InternalPort 1401

Protocol UDP

InternalClient <IP Address of the End

Device>

For devices that support the InternetGatewayDevice:1 root data model:

PortMappingEnabled true

PortMappingLeaseDuration

ExternalPort 1400

ExternalPortEndRange 1405

InternalPort 1401

PortMappingProtocol UDP

InternalClient <IP Address of the End Device>

5.4.3.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

January 2022 © The Broadband Forum. All rights reserved. 77 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

2. Refer to Determine WAN Interface to determine the WAN interface.

3. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

5.4.3.7 Procedure:

1. ACS performs an AddObject RPC to create a new PortMapping instance.

2. ACS performs a SetParameterValues RPC on the parameters above using the returned
PortMapping instance number.
3. ACS performs a GetParameterValues RPC on the PortMapping instance.
4. Send UDP traffic to the CPE’s IP Address with destination port 1400 from the WAN side of
the CPE.
5. Send UDP traffic to the CPE’s IP Address with destination port 1403 from the WAN side of
the CPE.

5.4.3.8 Test Metrics:

1. Validate that the values of the PortMapping instance match the values that were set.
2. Validate that the UDP traffic to port 1400 is forwarded to the LAN Device’s IP address, port
1401.
3. Validate that the UDP traffic to port 1403 is forwarded to the LAN Device’s IP address, port
1401.

5.4.4 Create a Port Mapping – Lease Duration > 0

5.4.4.1 Purpose:

To verify that an ACS can create a port mapping, the CPE can create the port mapping that the
ACS requested, and that internet traffic can traverse the port mapping.

5.4.4.2 References:

InternetGatewayDevice:1 [9]
Device:2 [10]

5.4.4.3 Profiles:

January 2022 © The Broadband Forum. All rights reserved. 78 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

NAT:1 Baseline:1

5.4.4.4 Optional Features:

LeaseDuration or PoerMappingLeaseDuration supports non-zero value

5.4.4.5 Parameters:

The following parameters required to be implemented for this test:

For devices that support the Device:2 root data model:

Enable true

Interface Returned from device

LeaseDuration 120

ExternalPort 1400

InternalPort 1401

Protocol UDP

InternalClient <IP Address of the End

Device>

For devices that support the InternetGatewayDevice:1 root data model:

PortMappingEnabled true

January 2022 © The Broadband Forum. All rights reserved. 79 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

PortMappingLeaseDuration 120

ExternalPort 1400

InternalPort 1401

PortMappingProtocol UDP

InternalClient <IP Address of the End Device>

5.4.4.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5. Refer to Determine WAN Interface to determine the WAN interface.

6. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

5.4.4.7 Procedure:

1. ACS performs an AddObject RPC to create a new PortMapping instance.

2. ACS performs a SetParameterValues RPC on the parameters above using the returned
PortMapping instance number.
3. ACS performs a GetParameterValues RPC on the PortMapping instance.
4. Send UDP traffic to the CPE’s IP Address with destination port 1400 from the WAN side of
the CPE.
5. Wait for the PortMapping Instance to expire.

January 2022 © The Broadband Forum. All rights reserved. 80 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

6. Send UDP traffic to the CPE’s IP Address with destination port 1400 from the WAN side of
the CPE.

5.4.4.8 Test Metrics:

1. Validate that the values of the PortMapping instance match the values that were set.
2. Validate that the UDP traffic to port 1400 is forwarded to the LAN Device’s IP address, port
1401.
3. Validate that the UDP traffic to port 1400 is NOT forwarded to the LAN Device after the
PortMapping Instance expires.

5.4.5 Create a Port Mapping – Remote Host Restriction

5.4.5.1 Purpose:

To verify that an ACS can create a port mapping, the CPE can create the port mapping that the
ACS requested, and that internet traffic can traverse the port mapping.

5.4.5.2 References:

InternetGatewayDevice:1 [9]
and Device:2 [10]

5.4.5.3 Profiles:

NAT:1 Baseline:1

5.4.5.4 Optional Features:

RemoteHost supports a non-empty string

5.4.5.5 Parameters:

The following parameters required to be implemented for this test:

January 2022 © The Broadband Forum. All rights reserved. 81 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

For devices that support the Device:2 root data model:

Enable true

Interface Returned from device

LeaseDuration

RemoteHost <IP Address of Telnet Client1>

ExternalPort 1400

InternalPort 1401

Protocol UDP

InternalClient <IP Address of the End

Device>

For devices that support the InternetGatewayDevice:1 root data model:

PortMappingEnabled true

PortMappingLeaseDuration

RemoteHost <IP Address of one WANDevice1>

ExternalPort 1400

InternalPort 1401

PortMappingProtocol UDP

InternalClient <IP Address of the End Device>

5.4.5.6 Test Setup:

January 2022 © The Broadband Forum. All rights reserved. 82 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. Refer to Common Test Setup for setup steps.

2. Have a LAN device connected to the LAN side of the CPE
3. Have devices connected on the WAN side of the CPE: WANDevice1, and WANDevice2 that
can both send UDP traffic.
4. ACS ensures that the port mapping being created doesn’t already exist by retrieving all
instances of the PortMapping table via a GetParamterValues RPC
1. If PortMapping already exists, remove it via the DeleteObject RPC.
2. Refer to Determine WAN Interface to determine the WAN interface.
3. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

5.4.5.7 Procedure:

1. ACS performs an AddObject RPC to create a new PortMapping instance.

2. ACS performs a SetParameterValues RPC on the parameters above using the returned
PortMapping instance number.
3. ACS performs a GetParameterValues RPC on the PortMapping instance.
4. Send UDP traffic to the CPE’s IP Address with destination port 1400 from WANDevice1.
5. Send UDP traffic to the CPE’s IP Address with destination port 1400 from WANDevice2

5.4.5.8 Test Metrics:

1. Validate that the values of the PortMapping instance match the values that were set.
2. Validate that the UDP traffic to port 1400 from WANDevice1 is forwarded to the LAN
Device’s IP address, port 1401.
3. Validate that the UDP traffic to port 1400 from WANDevice2 is NOT forwarded to the LAN
Device.

5.4.6 Create a Port Mapping – Multiple Entries – Precedence

Rules

5.4.6.1 Purpose:

To verify that an ACS can create a port mapping, the CPE can create the port mapping that the
ACS requested, and that internet traffic can traverse the port mapping.

January 2022 © The Broadband Forum. All rights reserved. 83 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.4.6.2 References:

InternetGatewayDevice:1 [9]
and Device:2 [10]

5.4.6.3 Profiles:

NAT:1 Baseline:1

5.4.6.4 Optional Features:

None

5.4.6.5 Parameters:

The following parameters required to be implemented for this test:

For devices that support the Device:2 root data model:

Enable true

Interface Returned from device

LeaseDuration

ExternalPort

InternalPort 1401

Protocol UDP

InternalClient <IP Address of the End

Device>

For devices that support the InternetGatewayDevice:1 root data model:

January 2022 © The Broadband Forum. All rights reserved. 84 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

PortMappingEnabled true

PortMappingLeaseDuration

ExternalPort

InternalPort 1401

PortMappingProtocol UDP

InternalClient <IP Address of the End Device>

5.4.6.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a LAN device connected to the LAN side of the CPE
3. Have two devices connected on the WAN side of the CPE: WANDevice1, and WANDevice2
that can both send UDP traffic.
4. ACS ensures that the port mapping being created doesn’t already exist by retrieving all
instances of the PortMapping table via a GetParamterValues RPC
1. If PortMapping already exists, remove it via the DeleteObject RPC.
2. Refer to Determine WAN Interface to determine the WAN interface.
3. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

5.4.6.7 Procedure:

1. ACS performs an AddObject RPC to create a new PortMapping instance.

2. ACS performs a SetParameterValues RPC on the parameters above using the returned
PortMapping instance number. ExternalPort is 0, InternalPort is 1401.
3. ACS performs an AddObject RPC to create a new PortMapping instance.
4. ACS performs a SetParameterValues RPC on the parameters above using the returned

January 2022 © The Broadband Forum. All rights reserved. 85 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

PortMapping instance number. ExternalPort is 1400, InternalPort is 1402.

5. ACS performs a GetParameterValues RPC on the PortMapping instance.
6. Send UDP traffic to the CPE’s IP Address with destination port 1399 from WANDevice1.
7. Send UDP traffic to the CPE’s IP Address with destination port 1400 from WANDevice2.

5.4.6.8 Test Metrics:

1. Validate that the values of the PortMapping instance match the values that were set.
2. Validate that the UDP traffic to port 1399 from WANDevice1 is forwarded to the LAN
Device’s IP address, port 1401.
3. Validate that the UDP traffic to port 1400 from WANDevice2 is forwarded to the LAN
Device’s IP address, port 1402.

5.4.7 Modify a Port Mapping

5.4.7.1 Purpose:

To verify that an ACS can change a port mapping, the CPE can change the port mapping in the
way that the ACS requested, and that internet traffic can traverse the altered port mapping.

5.4.7.2 References:

InternetGatewayDevice:1 [9]
Device:2 [10]

5.4.7.3 Profiles:

NAT:1 Baseline:1

5.4.7.4 Optional Features:

None

5.4.7.5 Parameters:

January 2022 © The Broadband Forum. All rights reserved. 86 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

The following parameters required to be implemented for this test:

For devices that support the Device:2 root data model:

Enable true

Interface Returned from device

LeaseDuration

ExternalPort 1400

InternalPort 1401

Protocol UDP

InternalClient <IP Address of the End

Device>

For devices that support the InternetGatewayDevice:1 root data model:

PortMappingEnabled true

PortMappingLeaseDuration

ExternalPort 1400

InternalPort 1401

PortMappingProtocol UDP

InternalClient <IP Address of the End Device>

5.4.7.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

January 2022 © The Broadband Forum. All rights reserved. 87 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

2. Have a LAN device connected to the LAN side of the CPE

3. Have a device connected on the WAN side of the CPE that can send UDP traffic.
4. ACS ensures that the port mapping being created doesn’t already exist by retrieving all
instances of the PortMapping table via a GetParamterValues RPC
1. If PortMapping already exists, remove it via the DeleteObject RPC.
2. Refer to Determine WAN Interface to determine the WAN interface.
3. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

5.4.7.7 Procedure:

1. ACS performs an AddObject RPC to create a new PortMapping instance.

2. ACS performs a SetParameterValues RPC on the parameters above using the returned
PortMapping instance number. ExternalPort is 1400, InternalPort is 1401.
3. Send UDP traffic to the CPE’s IP Address with destination port 1400 from the WAN side of
the CPE.
4. ACS performs a SetParameterValues RPC on the parameters above using the returned
PortMapping instance number. ExternalPort is 1401, InternalPort is 1402.
5. ACS performs a GetParameterValues RPC on the PortMapping instance.
6. Send UDP traffic to the CPE’s IP Address with destination port 1401 from the WAN side of
the CPE.

5.4.7.8 Test Metrics:

1. Validate that the UDP traffic to port 1400 is forwarded to the LAN Device’s IP address, port
1401.
2. Validate that the values of the PortMapping instance match the values that were set.
3. Validate that the UDP traffic to port 1401 is forwarded to the LAN Device’s IP address, port
1402.

5.4.8 Delete a Port Mapping

5.4.8.1 Purpose:

To verify that an ACS can remove a port mapping, the CPE can remove the port mapping that
the ACS requested, and that internet traffic will not traverse the across the removed port
mapping.

January 2022 © The Broadband Forum. All rights reserved. 88 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.4.8.2 References:

InternetGatewayDevice:1 [9]
and Device:2 [10]

5.4.8.3 Profiles:

NAT:1 Baseline:1

5.4.8.4 Optional Features:

None

5.4.8.5 Parameters:

The following parameters are required to be implemented by the CPE for this test:

For devices that support the Device:2 root data model:

Enable true

Interface Returned from device

LeaseDuration

ExternalPort 1400

InternalPort 1401

Protocol UDP

InternalClient <IP Address of the End Device

(laptop)>

For devices that support the InternetGatewayDevice:1 root data model:

January 2022 © The Broadband Forum. All rights reserved. 89 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

PortMappingEnabled true

PortMappingLeaseDuration

ExternalPort 1400

InternalPort 1401

PortMappingProtocol UDP

InternalClient <IP Address of the End Device (laptop)>

5.4.8.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a LAN device connected to the LAN side of the CPE
3. Have a device connected on the WAN side of the CPE that can send UDP traffic.
4. ACS ensures that the port mapping being altered already exists by retrieving all instances of
the PortMapping table via a GetParamterValues RPC
1. If PortMapping does NOT already exist, add it via the DeleteObject/SetParameterValues
RPC: see “Create a PortMapping (single interface)” test for procedures
2. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

5.4.8.7 Procedure:

1. Send UDP traffic to the CPE’s IP Address with destination port 1400 from the WAN side of
the CPE.
2. ACS performs a DeleteObject RPC on the PortMapping Instance.
3. ACS validates that the PortMapping entry no longer exists by retrieving all instances of the
PortMapping table via a GetParamterValues RPC
4. Send UDP traffic to the CPE’s IP Address with destination port 1400 from the WAN side of

January 2022 © The Broadband Forum. All rights reserved. 90 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

the CPE.

5.4.8.8 Test Metrics:

1. Validate that the UDP traffic to port 1400 is forwarded to the LAN Device’s IP address, port
1401.
2. Validate that the PortMapping Instance no longer exists in the table.
3. Validate that the UDP traffic to port 1400 is NOT forwarded to the LAN Device after the
PortMapping has been deleted.

January 2022 © The Broadband Forum. All rights reserved. 91 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.4.9 Create a Port Mapping – TCP

5.4.9.1 Purpose:

To verify that an ACS can create a port mapping, the CPE can create the port mapping that the
ACS requested, and that internet traffic can traverse the port mapping.

5.4.9.2 References:

InternetGatewayDevice:1 [9]
Device:2 [10]

5.4.9.3 Profiles:

NAT:1 Baseline:1

5.4.9.4 Optional Features:

None

5.4.9.5 Parameters:

The following parameters are required to be implemented by the CPE for this test:

For devices that support the Device:2 root data model:

Enable true

Interface Returned from device

LeaseDuration

ExternalPort 1400

InternalPort 1401

Protocol TCP

January 2022 © The Broadband Forum. All rights reserved. 92 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

InternalClient <IP Address of the End Device

(laptop)>

For devices that support the InternetGatewayDevice:1 root data model:

PortMappingEnabled true

PortMappingLeaseDuration

ExternalPort 1400

InternalPort 1401

PortMappingProtocol TCP

InternalClient <IP Address of the End Device (laptop)>

5.4.9.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a LAN device connected to the LAN side of the CPE
3. Have a device connected on the WAN side of the CPE that can send TCP traffic.
4. ACS ensures that the port mapping being created doesn’t already exist by retrieving all
instances of the PortMapping table via a GetParamterValues RPC
1. If PortMapping already exists, remove it via the DeleteObject RPC
2. Refer to Determine WAN Interface to determine the WAN interface.
3. Have a Network Analyzer to capture traffic between the CPE and the LAN device.

5.4.9.7 Procedure:

January 2022 © The Broadband Forum. All rights reserved. 93 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. ACS performs an AddObject RPC to create a new PortMapping instance.

2. ACS performs a SetParameterValues RPC on the parameters above using the returned
PortMapping instance number.
3. ACS performs a GetParameterValues RPC on the PortMapping instance.
4. Reboot the CPE.
5. ACS performs a GetParameterValues RPC on the PortMapping instance.
6. Send TCP traffic to the CPE’s IP Address with destination port 1400 from the WAN side of
the CPE.

5.4.9.8 Test Metrics:

1. Validate that the values of the PortMapping instance match the values that were set.
2. Validate that the CPE retains the PortMapping instance and configuration across a reboot.
3. Validate that the TCP traffic is forwarded to the LAN Device’s IP address, port 1401.

5.5 Advanced Firewall

5.5.1 Default Policy (Device:2 Only)

5.5.1.1 Purpose:

To verify the ACS can configure a firewall with a default policy on the CPE.

5.5.1.2 References:

Device:2.2

5.5.1.3 Profiles:

AdvancedFirewall:1 N/A

5.5.1.4 Optional Features:

January 2022 © The Broadband Forum. All rights reserved. 94 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

None

5.5.1.5 Parameters:

The following parameters are required to be implemented for this test:

Enable true

Config Advanced

AdvancedLevel Device.Firewall.Level.{i}.

Chain Returned from

device

DefaultPolicy Accept

Enable true

Target Drop

SourceIP <Unused IP
Address>

5.5.1.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a device that can send and receive TCP and UDP connections connected to the LAN
side of the CPE (End Device)
3. Have a device that can send and receive TCP and UDP connections connected on the WAN
side of the CPE (WAN Device)
4. Have a Network Analyzer to capture traffic between the CPE and the End Device.

5.5.1.7 Procedure:

January 2022 © The Broadband Forum. All rights reserved. 95 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. Configure ACS to send an AddObject RPC for Device.Firewall.Level and record the returned
instance number.

2. Configure ACS to send a GetParameterValues RPC for Device.Firewall.Level.{i}.Chain.

3. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule using the path
returned in step 2 and record the returned instance number.

4. ACS performs a SetParameterValues RPC on the parameters above except

Device.Firewall.Enable using the returned instance numbers from steps 1-3.

5. ACS enables the Firewall by sending a SetParameterValues RPC for Device.Firewall.Enable

with the value set to “true.”

6. End Device attempts to open a TCP connection with WAN Device.

7. WAN Device attempts to open a TCP connection with End Device.

8. ACS configures the Firewall by sending a SetParameterValues RPC with following

Name/Value pairs:

DefaultPolicy Drop

9. End Device attempts to open a TCP connection WAN Device.

10. WAN Device attempts to open a TCP connection with End Device.

5.5.1.8 Test Metrics:

1. In Step 6, CPE forwards traffic to the WAN side.

2. In Step 7, CPE forwards traffic to the LAN side.
3. In Step 9, CPE does not forward traffic to the WAN side.
4. In Step 10, CPE does not forward traffic to the LAN side.

5.5.2 Deny/Allow Outbound Protocols (Device:2 Only)

5.5.2.1 Purpose:

January 2022 © The Broadband Forum. All rights reserved. 96 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

To verify the ACS can configure a firewall on the CPE that denies or allows specific outbound
protocols.

5.5.2.2 References:

Device:2.2

5.5.2.3 Profiles:

AdvancedFirewall:1 N/A

5.5.2.4 Optional Features:

None

5.5.2.5 Parameters:

The following parameters are required to be implemented for this test:

Enable true

Config Advanced

AdvancedLevel Device.Firewall.Level.{i}.

Chain Returned from

device

DefaultPolicy Drop

Enable true

January 2022 © The Broadband Forum. All rights reserved. 97 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Target Accept

SourceIP <Unused IP Address>

DestInterface Default WAN

Interface

Protocol 6 (TCP), 17 (UDP)

5.5.2.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Refer to Determine WAN Interface to determine the WAN interface.
3. Device that can send and receive TCP and UDP connections connected to the LAN side of
the CPE (End Device)
4. Device that can send and receive TCP and UDP connections connected on the WAN side of
the CPE (WAN Device)
5. Have a Network Analyzer to capture traffic between the CPE and the End Device.

5.5.2.7 Procedure:

1. Configure ACS to send an AddObject RPC for Device.Firewall.Level and record the returned
instance number.

2. Configure ACS to send a GetParameterValues RPC for Device.Firewall.Level.{i}.Chain.

3. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule using the path
returned in step 2 and record the returned instance number.

4. ACS performs a SetParameterValues RPC on the following parameters using the instance
numbers returned in steps 1-3.

Config Advanced

AdvancedLevel Device.Firewall.Level.{i}.

January 2022 © The Broadband Forum. All rights reserved. 98 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Chain Returned from

device

DefaultPolicy Drop

Target Accept

DestIP <Unused IP
Address>

SourceIP <Unused IP
Address>

5. ACS enables the Firewall by sending a SetParameterValues RPC for Device.Firewall.Enable

with the value set to “true.”

6. End Device attempts to open a TCP connection with WAN Device.

7. End Device attempts to open a UDP connection with WAN Device.

8. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule. and record the
returned instance number.

9. ACS Configures the new Firewall Rule by sending a SetParameterValues RPC with the
following name/value pairs using the instance number returned in step 8.

Enable true

Target Accept

DestInterface Default WAN

Interface

Protocol 6 (TCP)

10. End Device attempts to open a TCP connection with WAN Device.

January 2022 © The Broadband Forum. All rights reserved. 99 of 179

CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

11. End Device attempts to open a UDP connection with WAN Device.

12. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule. and record the
returned instance number.

13. ACS Configures the new Firewall Rule by sending a SetParameterValues RPC with the
following name/value pairs using the instance number returned in step 12.

Enable true

Target Accept

DestInterface Default WAN

Interface

Protocol 17 (UDP)

14. End Device attempts to open a TCP connection with WAN Device.

15. End Device attempts to open a UDP connection with WAN Device.

5.5.2.8 Test Metrics:

1. In Step 6, CPE does not forward TCP traffic to the WAN side.
2. In Step 7, CPE does not forward UDP traffic to the WAN side.
3. In Step 10, CPE forwards TCP traffic to the WAN side.
4. In Step 11, CPE does not forward UDP traffic to the WAN side.
5. In Step 14, CPE forwards TCP traffic to the WAN side.
6. In Step 15, CPE forwards UDP traffic to the WAN side.

5.5.3 Deny/Allow Outbound Ports (Device:2 Only)

5.5.3.1 Purpose:

To verify the ACS can configure a firewall on the CPE that denies or allows specific outbound
ports.

January 2022 © The Broadband Forum. All rights reserved. 100 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.5.3.2 References:

Device:2.2

5.5.3.3 Profiles:

AdvancedFirewall:1 N/A

5.5.3.4 Optional Features:

None

5.5.3.5 Parameters:

The following parameters are required to be implemented for this test:

Enable true

Config Advanced

AdvancedLevel Device.Firewall.Level.{i}.

Chain Returned from

device

DefaultPolicy Drop

Enable true

Target Accept

DestInterface Default WAN

Interface

January 2022 © The Broadband Forum. All rights reserved. 101 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

DestIP <Unused IP Address>

SourceIP <Unused IP Address>

Protocol 6 (TCP), 17 (UDP)

DestPort int[-1:65535]

5.5.3.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.5.3.7 Procedure:

1. Configure ACS to send an AddObject RPC for Device.Firewall.Level and record the returned
instance number.

2. Configure ACS to send a GetParameterValues RPC for Device.Firewall.Level.{i}.Chain.

3. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule using the path
returned in step 2 and record the returned instance number.

4. ACS performs a SetParameterValues RPC on the following parameters using the instance
numbers returned in steps 1-3.

Config Advanced

AdvancedLevel Device.Firewall.Level.{i}.

Chain Returned from

device

January 2022 © The Broadband Forum. All rights reserved. 102 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

DefaultPolicy Drop

Target Accept

DestIP <Unused IP
Address>

SourceIP <Unused IP
Address>

5. ACS enables the Firewall by sending a SetParameterValues RPC for Device.Firewall.Enable

with the value set to “true.”

6. End Device attempts to open a TCP connection, destination port 80, with WAN Device.

7. End Device attempts to open a TCP connection, destination port 443, with WAN Device.

8. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule and record the
returned instance number.

9. ACS Configures the new Firewall Rule by sending a SetParameterValues RPC with the
following name/value pairs using the instance number returned in step 8.

Enable true

Target Accept

DestInterface Default WAN

Interface

Protocol

DestPort 80

10. End Device attempts to open a TCP connection, destination port 80, with WAN Device.

11. End Device attempts to open a TCP connection, destination port 443, with WAN Device.

January 2022 © The Broadband Forum. All rights reserved. 103 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

12. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule and record the
returned instance number.

13. ACS Configures the new Firewall Rule by sending a SetParameterValues RPC with the
following name/value pairs using the instance number returned in step 12.

Enable true

Target Accept

DestInterface Default WAN

Interface

Protocol

DestPort 443

14. End Device attempts to open a TCP connection, destination port 80, with WAN Device.

15. End Device attempts to open a TCP connection, destination port 443, with WAN Device.

5.5.3.8 Test Metrics:

1. In Step 6, CPE does not forward TCP traffic with destination port 80 to the WAN side.
2. In Step 7, CPE does not forward TCP traffic with destination port 443 to the WAN side.
3. In Step 10, CPE forwards TCP traffic with destination port 80 to the WAN side.
4. In Step 11, CPE does not forward TCP traffic with destination port 443to the WAN side.
5. In Step 14, CPE forwards TCP traffic with destination port 80 to the WAN side.
6. In Step 15, CPE forwards TCP traffic with destination port 443 to the WAN side.

5.5.4 Deny/Allow Source IP Address (Device:2 Only)

5.5.4.1 Purpose:

To verify the ACS can configure a firewall on the CPE that denies or allows specific outbound
ports.

January 2022 © The Broadband Forum. All rights reserved. 104 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.5.4.2 References:

Device:2.2

5.5.4.3 Profiles:

AdvancedFirewall:1 N/A

5.5.4.4 Optional Features:

None

5.5.4.5 Parameters:

The following parameters are required to be implemented for this test:

Enable true

Config Advanced

AdvancedLevel Device.Firewall.Level.{i}.

Chain Returned from

device

DefaultPolicy Drop

Enable true

Target Accept

DestInterface Default WAN

Interface

January 2022 © The Broadband Forum. All rights reserved. 105 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

DestIP <Unused IP Address>

SourceIP <Unused IP Address>

Protocol 6 (TCP), 17 (UDP)

DestPort int[-1:65535]

5.5.4.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Refer to Determine WAN Interface to determine the WAN interface.
3. Two Devices that can send and receive TCP and UDP connections connected to the LAN
side of the CPE (End Device 1 and End Device 2)
4. Device that can send and receive TCP and UDP connections connected on the WAN side of
the CPE (WAN Device)
5. Have a Network Analyzer to capture traffic between the CPE and the End Device.

5.5.4.7 Procedure:

1. Configure ACS to send an AddObject RPC for Device.Firewall.Level and record the returned
instance number.

2. Configure ACS to send a GetParameterValues RPC for Device.Firewall.Level.{i}.Chain.

3. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule using the path
returned in step 2 and record the returned instance number.

4. ACS performs a SetParameterValues RPC on the following parameters using the instance
numbers returned in steps 1-3.

Config Advanced

AdvancedLevel Device.Firewall.Level.{i}.

Chain Returned from

device

January 2022 © The Broadband Forum. All rights reserved. 106 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

DefaultPolicy Drop

Target Accept

DestIP <Unused IP
Address>

SourceIP <Unused IP
Address>

5. ACS enables the Firewall by sending a SetParameterValues RPC for Device.Firewall.Enable

with the value set to “true.”

6. End Device 1 attempts to open a TCP connection, destination port 80, with WAN Device.

7. End Device 2 attempts to open a TCP connection, destination port 80, with WAN Device.

8. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule and record the
returned instance number.

9. ACS Configures the new Firewall Rule by sending a SetParameterValues RPC with the
following name/value pairs using the instance number returned in step 8.

Enable true

Target Accept

DestInterface Default WAN

Interface

Protocol

DestPort 80

SourceIP End Device1 IP

10. End Device 1 attempts to open a TCP connection, destination port 80, with WAN Device.

January 2022 © The Broadband Forum. All rights reserved. 107 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

11. End Device 2 attempts to open a TCP connection, destination port 80, with WAN Device.

12. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule and record the
returned instance number.

13. ACS Configures the new Firewall Rule by sending a SetParameterValues RPC with the
following name/value pairs using the instance number returned in step 12.

Enable true

Target Accept

DestInterface Default WAN

Interface

Protocol

DestPort 80

SourceIP End Device2 IP

14. End Device 1 attempts to open a TCP connection, destination port 80, with WAN Device.

15. End Device 2 attempts to open a TCP connection, destination port 80 with WAN Device.

5.5.4.8 Test Metrics:

1. In Step 6, CPE does not forward TCP traffic from End Device 1 to the WAN side.
2. In Step 7, CPE does not forward TCP traffic from End Device 2 to the WAN side.
3. In Step 10, CPE forwards TCP traffic from End Device 1 to the WAN side.
4. In Step 11, CPE does not forward TCP traffic from End Device 2 to the WAN side.
5. In Step 14, CPE forwards TCP traffic from End Device 1 to the WAN side.
6. In Step 15, CPE forwards TCP traffic from End Device 2 to the WAN side.

5.6 Wi-Fi Provisioning

January 2022 © The Broadband Forum. All rights reserved. 108 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.6.1 Wi-Fi Setup WEP 64 (InternetGatewayDevice:1 Only)

5.6.1.1 Purpose:

To verify that an ACS can set a valid wireless LAN configuration on the CPE using WEP 64
encryption.

5.6.1.2 References:

InternetGatewayDevice:1.4

5.6.1.3 Profiles:

N/A WiFiLan:1

5.6.1.4 Optional Features:

WEPEncryptionLevel includes “40-bit”

5.6.1.5 Parameters:

The following parameters are required to be implemented for this test. A CPE MUST support
WEP-64 encryption in order to run this test.

Enable true

RadioEnabled true

SSID <string>

Channel <unsignedint>

BeaconType Basic

BeaconAdvertisementEnabled true

BasicEncryptionModes WEPEncryption

WEPEncryptionLevel Returned from

device

January 2022 © The Broadband Forum. All rights reserved. 109 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

BasicAuthenticationMode None

WEPKey 5-character
hexadecimal string

5.6.1.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.1.7 Procedure:

1. Perform a GetParameterValues on the WLANConfiguration partial path listed in the

parameters section to learn the existing stack hierarchy.
2. Configure the wireless LAN settings on the CPE using a single SetParameterValues.
3. Reboot the CPE.
4. The End Device connects to the CPE’s newly created wireless LAN access point.
5. Stimulate network traffic across the wireless LAN connection

5.6.1.8 Test Metrics:

1. Verify that WEPEncryptionLevel includes “40-bit”.

2. Verify that the SetParameterValuesResponse is valid.
3. Settings persist across reboot.
4. The End Device can connect to the wireless LAN connection.
5. The End Device has appropriate network access through the wireless LAN connection.

5.6.2 Wi-Fi Setup WEP 128 (InternetGatewayDevice:1 Only)

5.6.2.1 Purpose:

To verify that an ACS can set a valid wireless LAN configuration on the CPE using WEP 128

January 2022 © The Broadband Forum. All rights reserved. 110 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

encryption.

5.6.2.2 References:

InternetGatewayDevice:1.4

5.6.2.3 Profiles:

N/A WiFiLan:1

5.6.2.4 Optional Features:

WEPEncryptionLevel includes “104-bit”

5.6.2.5 Parameters:

The following parameters are required to be implemented for this test. A CPE MUST support
WEP-128 encryption in order to run this test.

Enable true

RadioEnabled true

SSID <string>

Channel <unsignedint>

BeaconType Basic

BeaconAdvertisementEnabled true

BasicEncryptionModes WEPEncryption

WEPEncryptionLevel Returned from Device

BasicAuthenticationMode None

January 2022 © The Broadband Forum. All rights reserved. 111 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

WEPKey 13-character
hexadecimal string

5.6.2.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.2.7 Procedure:

1. Perform a GetParameterValues on the WLANConfiguration partial path listed in the

5.6.2.8 Test Metrics:

1. Verify that WEPEncryptionLevel includes “104-bit”.

5.6.3 Wi-Fi Setup WPA Personal (InternetGatewayDevice:1

Only)

5.6.3.1 Purpose:

To verify that an ACS can set a valid Wireless LAN configuration on the CPE using WPA
Personal encryption.

January 2022 © The Broadband Forum. All rights reserved. 112 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.6.3.2 References:

InternetGatewayDevice:1.4

5.6.3.3 Profiles:

N/A WiFiLan:1

5.6.3.4 Optional Features:

BeaconType supports “WPA”

5.6.3.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

RadioEnabled true

SSID <string>

Channel <unsignedint>

BeaconType WPA

BeaconAdvertisementEnabled true

WPAEncryptionModes AESEncryption

WPAAuthenticationMode PSKAuthentication

PreSharedKey Hexadecimal
string

5.6.3.6 Test Setup:

January 2022 © The Broadband Forum. All rights reserved. 113 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.3.7 Procedure:

1. Perform a GetParameterValues on the WLANConfiguration partial path listed in the

5.6.3.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

2. Settings persist across reboot.
3. The End Device can connect to the wifi connection.
4. The End Device has appropriate network access through the wifi connection.

5.6.4 Wi-Fi Setup WPA2 Personal (InternetGatewayDevice:1

Only)

5.6.4.1 Purpose:

To verify that an ACS can set a valid Wireless LAN configuration on the CPE using WPA2-
Personal encryption.

5.6.4.2 References:

InternetGatewayDevice:1.4

5.6.4.3 Profiles:

N/A WiFiLan:1

January 2022 © The Broadband Forum. All rights reserved. 114 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5.6.4.4 Optional Features:

BeaconType supports “11i”

5.6.4.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

RadioEnabled true

SSID <string>

Channel <unsignedint>

BeaconType 11i

BeaconAdvertisementEnabled true

IEEE11iEncryptionModes AESEncryption

IEEE11iAuthenticationMode PSKAuthentication

PreSharedKey Hexadecimal
string

5.6.4.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks

5.6.4.7 Procedure:

1. Perform a GetParameterValues on the WLANConfiguration partial path listed in the

January 2022 © The Broadband Forum. All rights reserved. 115 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

5. Stimulate network traffic across the wireless LAN connection

5.6.4.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

2. Settings persist across reboot.
3. The End Device can connect to the wifi connection.
4. The End Device has appropriate network access through the wifi connection.

5.6.5 Wi-Fi Setup WPA-WPA2 Personal

(InternetGatewayDevice:1 Only)

5.6.5.1 Purpose:

To verify that an ACS can set a valid Wireless LAN configuration on the CPE using WPA-WPA2-
Personal encryption.

5.6.5.2 References:

InternetGatewayDevice:1.4

5.6.5.3 Profiles:

N/A WiFiLan:1

5.6.5.4 Optional Features:

BeaconType includes “WPAand11i”

5.6.5.5 Parameters:

The following parameters are required to be implemented for this test.

January 2022 © The Broadband Forum. All rights reserved. 116 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

Enable true

RadioEnabled true

SSID <string>

Channel <unsignedint>

BeaconType WPAand11i

BeaconAdvertisementEnabled true

IEEEEncryptionModes AESEncryption

IEEEAuthenticationMode PSKAuthentication

PreSharedKey Hexadecimal
string

5.6.5.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.5.7 Procedure:

1. Perform a GetParameterValues on the WLANConfiguration partial path listed in the

5.6.5.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

2. Settings persist across reboot.
3. The End Device can connect to the wifi connection.

January 2022 © The Broadband Forum. All rights reserved. 117 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

4. The End Device has appropriate network access through the wifi connection.

5.6.6 Wi-Fi Setup WEP 64 (Device:2 Only)

5.6.6.1 Purpose:

To verify that an ACS can set a valid wireless LAN configuration on the CPE using WEP 64
encryption.

5.6.6.2 References:

Device:2 [10]

5.6.6.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.6.4 Optional Features:

ModesSupported includes “WEP-64”

5.6.6.5 Parameters:

The following parameters are required to be implemented for this test. A CPE MUST support
WEP-64 encryption in order to run this test.

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or 5GHz

OperatingStandards <appropriate
setting>

January 2022 © The Broadband Forum. All rights reserved. 118 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WEP-64

ModesSupported Returned from device

WEPKey 5-character hexadecimal

string

5.6.6.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.6.7 Procedure:

1. Perform a GetParameterValues on the root partial path listed in the parameters section to
learn the existing stack hierarchy.
2. If no SSID objects exist, perform an AddObject RPC on the Device.Wifi.SSID. partial path.
1. Record the instance number received in the AddObjectResponse.
2. If no AccessPoint objects exist, perform an AddObject RPC on the
Device.Wifi.AccessPoint. partial path
3. Record the instance number received in the AddObjectResponse
4. Configure the Wifi settings on the CPE using a single SetParameterValues.
5. Reboot the CPE.
6. Perform a GetParameterValues on the Stats object listed in the Parameters section and
note the values.

January 2022 © The Broadband Forum. All rights reserved. 119 of 179
CWMP Interoperability and Functionality Test Plan TP-181 Issue 1 Amendment 2

7. The End Device connects to the CPE’s newly created wifi access point.
8. Stimulate network traffic across the Wifi connection
9. Perform a GetParameterValues on the Stats object listed in the Parameters section and
note the values.

5.6.6.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

2. Settings persist across reboot.
3. The End Device can connect to the wireless LAN connection.
4. The End Device has appropriate network access through the wireless LAN connection.
5. The Stats object has updated to reflect the network traffic across the wireless LAN
connection.

5.6.7 Wi-Fi Setup WEP 128 (Device:2 Only)

5.6.7.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WEP 128 encryption.

5.6.7.2 References:

Device:2 [10]

5.6.7.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.7.4 Optional Features:

ModesSupported includes “WEP-128”

5.6.7.5 Parameters :

The following parameters are required to be implemented for this test. A CPE MUST support
WEP-128 encryption in order to run this test.

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WEP-128

ModesSupported Returned from device

WEPKey 13-character hexadecimal

string

5.6.7.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.7.7 Procedure:

5.6.7.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

2. Settings persist across reboot.
3. The End Device can connect to the wifi connection.
4. The End Device has appropriate network access through the wifi connection.
5. The Stats object has updated to reflect the network traffic across the wifi connection.

5.6.8 Wi-Fi Setup WPA Personal (Device:2 Only)

5.6.8.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WPA Personal
Encryption.

5.6.8.2 References:

Device:2 [10]

5.6.8.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.8.4 Optional Features:

ModesSupported includes “WPA-Personal”

5.6.8.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WPA-Personal

ModesSupported Returned from

device

PreSharedKey hexadecimal string

5.6.8.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.8.7 Procedure:

Perform a GetParameterValues on the root partial path listed in the parameters section to learn
the existing stack hierarchy. If no SSID objects exist, perform an AddObject RPC on the
Device.Wifi.SSID. partial path. #. Record the instance number received in the
AddObjectResponse. #. If no AccessPoint objects exist, perform an AddObject RPC on the
Device.Wifi.AccessPoint. partial path #. Record the instance number received in the
AddObjectResponse #. Configure the Wifi settings on the CPE using a single
SetParameterValues. #. Reboot the CPE. #. Perform a GetParameterValues on the Stats object
listed in the Parameters section and note the values. #. The End Device connects to the CPE’s
newly created wifi access point. #. Stimulate network traffic across the Wifi connection #.
Perform a GetParameterValues on the Stats object listed in the Parameters section and note the
values.

5.6.8.8 Test Metrics:

1. Verify that the SetParameterValuesResponse to be valid.

5.6.9 Wi-Fi Setup WPA Enterprise (Device:2 Only)

5.6.9.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WPA Enterprise
Encryption.

5.6.9.2 References:

Device:2 [10]

5.6.9.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.9.4 Optional Features:

ModesSupported includes “WPA-Enterprise”

5.6.9.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WPA-Enterprise

RadiusServerIPAddr <IP address of RADIUS

server>

RadiusServerPort <Port of RADIUS Server>

RadiusSecret <string>

5.6.9.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a RADIUS Server set up configured with a secret and a user account with a known
username and password.
3. Have an End Device with the ability to connect to wireless networks.

5.6.9.7 Procedure:

5.6.9.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

2. Settings persist across reboot.
3. Verify CPE sends a Radius request on End Device connection to the Radius server and
receives a valid response.
4. The End Device can connect to the wifi connection.
5. The End Device has appropriate network access through the wifi connection.
6. The Stats object has updated to reflect the network traffic across the wifi connection.

5.6.10 Wi-Fi Setup WPA2 Personal (Device:2 only)

5.6.10.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WPA2-Personal
encryption.

5.6.10.2 References:

Device:2 [10]

5.6.10.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.10.4 Optional Features:

ModesSupported includes “WPA2-Personal”

5.6.10.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WPA2-Personal

ModesSupported Returned from

device

PreSharedKey hexadecimal string

5.6.10.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.10.7 Procedure:

1. Perform a GetParameterValues on the root partial path listed in the parameters section to
learn the existing stack hierarchy.

2. If no SSID objects exist, perform an AddObject RPC on the Device.Wifi.SSID. partial path.
1. Record the instance number received in the AddObjectResponse.
2. If no AccessPoint objects exist, perform an AddObject RPC on the
Device.Wifi.AccessPoint. partial path
3. Record the instance number received in the AddObjectResponse
4. Configure the Wifi settings on the CPE using a single SetParameterValues.
5. Reboot the CPE.
6. Perform a GetParameterValues on the Stats object listed in the Parameters section and
note the values.
7. The End Device connects to the CPE’s newly created wifi access point.
8. Stimulate network traffic across the Wifi connection
9. Perform a GetParameterValues on the Stats object listed in the Parameters section and
note the values.

5.6.10.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

5.6.11 Wi-Fi Setup WPA2 Enterprise (Device:2 Only)

5.6.11.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WPA2-Enterprise
Encryption.

5.6.11.2 References:

Device:2 [10]

5.6.11.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.11.4 Optional Features:

ModesSupported includes “WPA2-Enterprise”

5.6.11.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WPA2-Enterprise

RadiusServerIPAddr <IP address of RADIUS

server>

RadiusServerPort <Port of RADIUS Server>

RadiusSecret <string>

5.6.11.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a RADIUS Server set up configured with a secret and a user account with a known
username and password.
3. Have an End Device with the ability to connect to wireless networks.

5.6.11.7 Procedure:

5.6.11.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

5.6.12 Wi-Fi Setup WPA-WPA2 Personal (Device:2 Only)

5.6.12.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WPA-WPA2-Personal
encryption.

5.6.12.2 References:

Device:2 [10]

5.6.12.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.12.4 Optional Features:

ModesSupported includes “WPA-WPA2-Personal”

5.6.12.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WPA-WPA2-Personal

ModesSupported Returned from device

PreSharedKey hexadecimal string

5.6.12.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.12.7 Procedure:

8. Stimulate network traffic across the Wifi connection

9. Perform a GetParameterValues on the Stats object listed in the Parameters section and
note the values.

5.6.12.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

5.6.13 Wi-Fi Setup WPA-WPA2 Enterprise (Device:2 Only)

5.6.13.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WPA-WPA2-
Enterprise Encryption.

5.6.13.2 References:

Device:2 [10]

5.6.13.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.13.4 Optional Features:

ModesSupported includes “WPA-WPA2-Enterprise”

5.6.13.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WPA-WPA2-Enterprise

ModesSupported Returned from device

RadiusServerIPAddr <IP address of RADIUS

server>

RadiusServerPort <Port of RADIUS Server>

RadiusSecret <string>

5.6.13.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a RADIUS Server set up configured with a secret and a user account with a known
username and password.
3. Have an End Device with the ability to connect to wireless networks.

5.6.13.7 Procedure:

5.6.13.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

5.6.14 Wi-Fi Setup WPA3 Personal (Device:2 only)

5.6.14.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WPA3- Personal
encryption.

5.6.14.2 References:

Device:2 [10]

5.6.14.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.14.4 Optional Features:

ModesSupported includes “WPA3-Personal”

5.6.14.5 Parameters:

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WPA3-Personal

ModesSupported Returned from

device

SAEPassphrase hexadecimal string

5.6.14.6 Test Setup:

1. Refer to Section 4.2.1, Common Test Setup, for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.14.7 Procedure:

a. Record the instance number received in the AddObjectResponse.

3. If no AccessPoint objects exist, perform an AddObject RPC on the Device.Wifi.AccessPoint.

partial path

a. Record the instance number received in the the AddObjectResponse

4. Configure the Wifi settings on the CPE using a single SetParameterValues.

5. Reboot the CPE.
6. Perform a GetParameterValues on the Stats object listed in the Parameters section and note
the values.
7. The End Device connects to the CPE’s newly created wifi access point.
8. Stimulate network traffic across the Wifi connection
9. Perform a GetParameterValues on the Stats object listed in the Parameters section and note
the values

5.6.14.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

5.6.15 Wi-Fi Setup WPA3-Personal-Transition (Device:2 only)

5.6.15.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WPA3- Personal-
Transition encryption.

5.6.15.2 References:

Device:2 [10]

5.6.15.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.15.4 Optional Features:

ModesSupported includes “WPA3-Personal-Transition”

5.6.15.5 Parameters:

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WPA3-Personal-Transition

ModesSupported Returned from device

SAEPassphrase hexadecimal string

5.6.15.6 Test Setup:

1. Refer to Section 4.2.1, Common Test Setup, for setup steps.

2. Have an End Device with the ability to connect to wireless networks.

5.6.15.7 Procedure:

a. Record the instance number received in the AddObjectResponse.

3. If no AccessPoint objects exist, perform an AddObject RPC on the Device.Wifi.AccessPoint.

partial path

a. Record the instance number received in the the AddObjectResponse

4. Configure the Wifi settings on the CPE using a single SetParameterValues.

the values

5.6.15.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

5.6.16 Wi-Fi Setup WPA3-Enterprise (Device:2 only)

5.6.16.1 Purpose:

To verify that an ACS can set a valid Wi-Fi configuration on the CPE using WPA3- Enterprise
encryption.

5.6.16.2 References:

Device:2 [10]

5.6.16.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.16.4 Optional Features:

ModesSupported includes “WPA3-Enterprise”

5.6.16.5 Parameters:

Enable true

Channel <unsignedInt>

OperatingFrequencyBand 2.4GHz or
5GHz

OperatingStandards Auto

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDAdvertisementEnabled true

SSIDReference Device.WiFi.SSID.{i}.

ModeEnabled WPA3-Enterprise

RadiusServerIPAddr <IP address of RADIUS

server>

RadiusServerPort <Port of RADIUS server>

RadiusSecret <string>

5.6.16.6 Test Setup:

1. Refer to Section 4.2.1, Common Test Setup, for setup steps.

2. Have a RADIUS Server set up configured with a secret and a user account with a known
username and password.
3. Have an End Device with the ability to connect to wireless networks.

5.6.16.7 Procedure:

a. Record the instance number received in the AddObjectResponse.

3. If no AccessPoint objects exist, perform an AddObject RPC on the Device.Wifi.AccessPoint.

partial path

a. Record the instance number received in the the AddObjectResponse

4. Configure the Wifi settings on the CPE using a single SetParameterValues.

5. Reboot the CPE.
6. Perform a GetParameterValues on the Stats object listed in the Parameters section and note
the values.
7. The End Device connects to the CPE’s newly created wifi access point, authenticated from
the RADIUS Server.
8. Stimulate network traffic across the Wifi connection
9. Perform a GetParameterValues on the Stats object listed in the Parameters section and note
the values

5.6.16.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

2. Settings persist across reboot.
3. Verify CPE sends a Radius request on End Device connection to the Radius server and
receives a valid response.
4. The End Device has appropriate network access through the wifi connection.
5. The Stats object has updated to reflect the network traffic across the wifi connection.

5.6.17 Wi-Fi Setup – Add SSID (Device:2 Only)

5.6.17.1 Purpose:

To verify that an ACS can add an SSID object successfully to a preexisting Wifi configuration and
that the new SSID is able to be successfully used to gain appropriate network access.

5.6.17.2 References:

Device:2 [10]

5.6.17.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.17.4 Optional Features:

None

5.6.17.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDReference Device.WiFi.SSID.{i}.

5.6.17.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a pre-existing, working Wi-Fi Configuration on the CPE.
3. Have an End Device with the ability to connect to existing wireless networks.

5.6.17.7 Procedure:

1. Perform a GetParameterValues on the root partial path listed in the parameters section to

learn the existing stack hierarchy. Take special note of the existing SSID object’s
LowerLayers parameter (Device.Wifi.SSID.{j}.LowerLayers)
2. Perform an AddObject RPC on “Device.Wifi.SSID.” and record the instance number and
status returned.
3. If the status of the Add Object RPC returned a 1, reboot the device.
4. Perform a Get Parameter Values RPC on the path from Procedure step 2 and confirm the
object was added successfully.
5. Peform an AddObject RPC on “Device.WiFi.AccessPoint.” and record the instance number
and status returned.
6. If the status of the Add Object RPC returned a 1, reboot the device.
7. Perform a Get Parameter Values RPC on the path from Procedure step 5 and confirm the
object was added successfully.
8. Configure the Wifi settings on the CPE to utilize the new SSID object using the
SetParameterValues RPC:
1. Device.Wifi.SSID.{i}.LowerLayers = <Value returned in Procedure step 1>
2. Device.Wifi.SSID.{i}.Enable = true
3. Device.Wifi.SSID.{i}.SSID = <Value different from Device.Wifi.SSID.{j}.SSID>
4. Device.Wifi.AccessPoint.{k}.SSIDReference = Device.Wifi.SSID.{i}
5. The End Device connects to the CPE’s newly created Wi-Fi SSID using the same
authentication method and credentials that the preexisting configuration uses.
6. Reboot the CPE
7. Perform a GetParameterValues on the Stats object listed in the Parameters section and
note the values.
8. The End Device connects to the CPE’s newly created wifi SSID using the same
authentication method and credentials that the preexisting configuration uses.
9. Stimulate network traffic across the Wifi connection.
10. Perform a GetParameterValues on the Stats object listed in the Parameters section and
note the values.

5.6.17.8 Test Metrics:

1. Verify that the SetParameterValuesResponse is valid.

2. Settings persist across reboot.
3. The End Device can connect to the new SSID.
4. The End Device has appropriate network access using the new SSID.
5. The Stats object has updated to reflect the network traffic across the Wi-Fi connection.

5.6.18 Wi-Fi Setup – Remove SSID (Device:2 Only)

5.6.18.1 Purpose:

To verify that an ACS can remove an SSID object successfully from a preexisting Wifi
configuration and that the new SSID is able to be successfully used to gain appropriate network
access.

5.6.18.2 References:

Device:2 [10]

5.6.18.3 Profiles:

WiFiRadio:1, WiFiSSID:1, N/A

WiFiAccessPoint:1

5.6.18.4 Optional Features:

None

5.6.18.5 Parameters:

The following parameters are required to be implemented for this test.

Enable true

SSID <string>

LowerLayers Device.WiFi.Radio.{i}.

SSIDReference Device.WiFi.SSID.{i}.

5.6.18.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have a preexisting, working Wifi configuration on the CPE.
3. Have an End Device (Laptop) with the ability to connect to wireless networks.

5.6.18.7 Procedure:

1. Verify that the existing Wifi configuration is operating correctly by connecting the End Device
to it. Note the SSID that was connected to.
2. Perform a GetParameterValues on the root partial path listed in the parameters section to
learn the existing stack hierarchy. Note the instance number of the SSID object with the
SSID field matching the one connected to in Procedure Step 1 as well as the instance
number of the AccessPoint with the SSIDReference field mapped to the appropriate SSID.
3. Peform a DeleteObject RPC on the Device.Wifi.SSID.{instance noted in Procedure Step 2}
and Device.Wifi.AccessPoint.{instance noted in Procedure Step 2}, noting the returned
value.
4. If the status returned is 1, reboot the CPE.
5. Perform a GetParameterValues on Device.Wifi.SSID. And Device.Wifi.AccessPoint. to
confirm deletion.
6. Attempt to re-connect the End Device to the removed SSID.
7. If status returned in the DeleteObject was 0, reboot the CPE and then perform a
GetParameterValues on Device.Wifi.SSID. And Device.Wifi.AccessPoint. to confirm deletion
persisted across reboot.

5.6.18.8 Test Metrics:

1. End Device can initially connect to the SSID

2. Deletion of SSID object persists across reboot.
3. The End Device cannot connect to the deleted SSID.

5.7 Localized Strings

5.7.1 Non-Printable ASCII Characters in SetParameterValues

5.7.1.1 Purpose:

To verify that an ACS can configure localized strings in the device.

5.7.1.2 References:

Device:2 [10]
REC-xml Section 4.4 [3]

5.7.1.3 Profiles:

Baseline:1 N/A

5.7.1.4 Optional Features:

None

5.7.1.5 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

ProvisioningCode <string>

5.7.1.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.7.1.7 Procedure:

1. ACS triggers a new session with the CPE

2. The CPE establishes the session
3. ACS performs a SPV on the above parameter and sets a new value, which is randomly

generated and fulfills these criteria:

4. The string contains non-printable ASCII characters
5. The string contains XML characters, which have to be escaped like “<,>, &”
6. ACS ends the session
7. ACS triggers a new session with the CPE
8. The CPE establishes the session
9. ACS performs a GPV on the above parameter
10. ACS ends the session
11. Repeat steps 1-8 with a new randomly generated string.
12. Repeat steps 1-8 with a new randomly generated string.

5.7.1.8 Test Metrics:

1. Validate that both session can be successfully executed

2. Validate that the GPV and SPV are successful
3. Validate that the string returned in step 7 matches the string set in step 3
4. Validate that the string is properly encoded in step 3 and step 7

5.7.2 Multi-Byte Encoding in SetParameterValues RPC

(Device:2 Only)

5.7.2.1 Purpose:

To verify that an ACS can configure strings in the CPE that are 64 characters but more than 64
bytes.

5.7.2.2 References:

Device:2 [10]
REC-xml Section 4.3.3 [3]

5.7.2.3 Profiles:

Baseline:1 N/A

5.7.2.4 Optional Features:

None

5.7.2.5 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

ProvisioningCode <string>

5.7.2.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.7.2.7 Procedure:

1. ACS triggers a new session with the CPE

2. The CPE establishes the session
3. ACS performs a SPV on the above parameter and sets a new value, which is randomly
generated and fulfills these criteria:
4. The string uses a multi-byte encoding
5. The string contains 64 characters
6. ACS ends the session
7. ACS triggers a new session with the CPE
8. The CPE establishes the session
9. ACS performs a GPV on the above parameter
10. ACS ends the session

5.7.2.8 Test Metrics:

1. Validate that both session can be successfully executed

2. Validate that the GPV and SPV are successful
3. Validate that the string returned in step 7 matches the string set in step 3
4. Validate that the string is properly encoded in step 3 and step 7

5.7.3 Non-ASCII Characters in ParameterKey (Device:2 Only)

5.7.3.1 Purpose:

To verify that an ACS can configure localized strings in the device.

5.7.3.2 References:

Device:2 [10]
REC-xml Section 4.4 [3]

5.7.3.3 Profiles:

Baseline:1 N/A

5.7.3.4 Optional Features:

None

5.7.3.5 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

ProvisioningCode <string>

ParameterKey <string>

5.7.3.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.7.3.7 Procedure:

1. ACS triggers a new session with the CPE.

2. The CPE establishes the session.
3. ACS performs a SetParameterValues RPC on the ProvisioningCode and sets a new value.
In the SPV the ACS uses a ParameterKey, which is randomly generated and fulfills these
criteria:
4. The string contains non-printable ASCII characters
5. The string contains XML characters, which have to be escaped like “<,>, &”.
6. ACS ends the session.
7. ACS triggers a new session with the CPE.
8. The CPE establishes the session.
9. ACS performs a GetParameterValues on ParameterKey.
10. ACS ends the session.
11. Repeat steps 1-8 with a new randomly generated string.
12. Repeat steps 1-8 with a new randomly generated string.

5.7.3.8 Test Metrics:

1. Validate that both session can be successfully executed.

2. Validate that the GetParameterValues RPC and the SetParameterValues RPC are
successful.
3. Validate that the string returned in step 7 matches the string set in step 3.
4. Validate that the string is properly encoded in step 3 and step 7.

5.7.4 Multi-Byte Encoding in ParameterKey (Device:2 Only)

5.7.4.1 Purpose:

To verify that an ACS can configure strings in the CPE that are 32 characters but more than 32
bytes.

5.7.4.2 References:

Device:2 [10]
REC-xml Section 4.3.3 [3]

5.7.4.3 Profiles:

Baseline:1 N/A

5.7.4.4 Optional Features:

None

5.7.4.5 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

ProvisioningCode <string>

ParameterKey <string>

5.7.4.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.7.4.7 Procedure:

1. ACS triggers a new session with the CPE

2. The CPE establishes the session
3. ACS performs a SetParameterValues RPC on the ProvisioningCode and sets a new value.
In the SPV the ACS uses a ParameterKey, which is randomly generated and fulfills these
criteria:
4. The string uses a multi-byte encoding
5. The string contains 32 characters
6. ACS ends the session
7. ACS triggers a new session with the CPE
8. The CPE establishes the session

9. ACS performs a GetParameterValues RPC on ParameterKey.

10. ACS ends the session

5.7.4.8 Test Metrics:

1. Validate that both session can be successfully executed

2. Validate that the GetParameterValues RPC and the SetParameterValues RPC are
successful
3. Validate that the string returned in step 7 matches the string set in step 3
4. Validate that the string is properly encoded in step 3 and step 7

5.7.5 Non-ASCII Characters in CommandKey (Device:2 Only)

5.7.5.1 Purpose:

To verify that an ACS can configure localized strings in the device.

5.7.5.2 References:

Device:2 [10]
REC-xml Section 4.4 [3]

5.7.5.3 Profiles:

Device:2 InternetGatewayDevice:1

5.7.5.4 Optional Features:

None

5.7.5.5 Parameters:

None.

5.7.5.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.7.5.7 Procedure:

1. ACS triggers a new session with the CPE

2. The CPE establishes the session
3. ACS performs a Reboot RPC with a Commandkey parameter which is randomly generated
and fulfills these criteria:
4. The string contains non-printable ASCII characters.
5. The string contains XML characters, which have to be escaped like “<,>, &”
6. ACS ends the session
7. The CPE performs a reboot and reports the CommandKey to the ACS.
8. Repeat steps 1-5 with a new randomly generated string.
9. Repeat steps 1-5 with a new randomly generated string.

5.7.5.8 Test Metrics:

1. Validate that both session can be successfully executed

2. Validate that the Reboot RPC is successful.
3. Validate that the string returned in step 5 matches the string set in step 3 after escaping.
4. Validate that the string is properly encoded in step 3 and step 5

5.7.6 Multi-Byte Encoding in CommandKey (Device:2 Only)

5.7.6.1 Purpose:

To verify that an ACS can configure strings in the CPE that are 32 characters but more than 32
bytes.

5.7.6.2 References:

Device:2 [10]
REC-xml Section 4.3.3 [3]

5.7.6.3 Profiles:

Baseline:1 N/A

5.7.6.4 Optional Features:

None

5.7.6.5 Parameters:

None.

5.7.6.6 Test Setup:

1. Refer to Common Test Setup for setup steps.

5.7.6.7 Procedure:

1. ACS triggers a new session with the CPE

2. The CPE establishes the session
3. ACS performs a Reboot RPC with a Commandkey parameter which is randomly generated
and fulfills these criteria:
4. The string uses a multi-byte encoding using UTF-8.
5. The string contains 32 characters
6. ACS ends the session
7. The CPE performs a reboot and reports the CommandKey to the ACS.

5.7.6.8 Test Metrics:

1. Validate that both session can be successfully executed

2. Validate that the Reboot RPC is successful
3. Validate that the string returned in step 5 matches the string set in step 3 after escaping.
4. Validate that the string is properly encoded in step 3 and step 5

5.8 Configuration Backup and Restore –

Incorrect Backup File

5.8.0.1 Purpose:

This test is designed to verify that the CPE responds to invalid restoration of a configuration with
a correct fault code.

5.8.0.2 References:

Section A.4.1.5/TR-069a1 or later [8]

5.8.0.3 Parameters:

These parameters are for the Download RPC:

Download parameters:

CommandKey: a unique value

FileType: "3 Vendor Configuration File"

URL: location of the invalid file

Username: used to authenticate CPE with file server

Password: used to authenticate CPE with file server

FileSize: size of the file in bytes

TargetFileName: name of file

DelaySeconds: 0

SuccessURL: Empty string

FailureURL: Empty string

5.8.0.4 Test Setup:

1. ACS connected to the network

2. CPE connected to the network and configured with an ACS URL that corresponds to the
ACS in #1
3. Have device to capture traffic between the device and both the file server and ACS
4. Establish a server to download files.

5.8.0.5 Procedure:

1. ACS schedules a download RPC on the CPE with the parameters above
2. Allow CPE to respond DownloadResponse or TransferComplete

5.8.0.6 Test Metrics:

1. Verify that the CPE responds to the Download RPC with a DownloadResponse or
TransferComplete with one of the following fault codes: 9003 (Invalid argument),

5.9 DHCP Provisioning – Disable DHCP

5.9.0.1 Purpose:

To verify that an ACS can configure the basic DHCPv4 configuration required on a CPE device.

5.9.0.2 References:

TR-181i2a7

5.9.0.3 Parameters:

The following parameters within the InternetGatewayDevice.LANDevice.

{i}.LANHostConfigManagement. table (for devices that implement the InternetGatewayDevice:1
root data model) and Device.DHCPv4.Server.Pool.{i}. table (for devices that implement the
Device:2 root data model) are required to be implemented for this test:

Server DHCPServerConfigurable – true

Configurable

Server Enable DHCPServerEnable Disable FALSE

Interface – Interface Returned from

Device

Minimum Address MinAddress MinAddress <minimum

address>

Maximum Address MaxAddress MaxAddress <maximum

address>

Lease Time DHCPLeaseTime – 60

5.9.0.4 Test Setup:

1. ACS connected to the network

2. CPE connected to the network and configured with an ACS URL that corresponds to the
ACS in #1
3. CPE supports the appropriate DHCP parameters in the parameters section
4. If a Device CPE, verify that the Interface parameter is a valid path name in the IP Interface

table.
5. Have an end system that can attempt to connect to the CPE via DHCP.

5.9.0.5 Procedure:

1. If the DUT implements the Device:2 root data model, perform an AddObject RPC on
Device.Server.Pool., recording the InstanceNumber value returned in the
AddObjectResponse
2. On the ACS schedule a SetParameterValues RPC on the appropriate Configurable
parameters in the Parameters Section
3. Allow the end system to connect to the CPE via DHCP.
4. Perform a reboot of the CPE
5. Allow the end system to attempt connect to the CPE via DHCP

5.9.0.6 Test Metrics:

1. Verify that the SetParameterValuesResponse RPC is correct for all parameters

2. Verify that the end system doesn’t connect to the CPE within the designated range.
3. Verify that that end system doesn’t connects to the CPE within the designated range after
the reboot

5.10 Diagnostics IPPing – Error Condition

5.10.0.1 Purpose:

To verify that an ACS can perform an IP Ping Diagnostics test on the CPE where the CPE returns
a Error_NoRouteToHost.

5.10.0.2 References:

InternetGatewayDevice:1.6 and Device:2.6

5.10.0.3 Parameters:

The following parameters within the InternetGatewayDevice.IPPingDiagnostics. table (for devices

that implement the InternetGatewayDevice:1 data model) or Device.IP.Diagnostics.IPPing. table
(for devices that implement the Device:2 data model) are required to be implemented for this
test:

Diagnostics State DiagnosticsState DiagnosticsState Requested

Interface Interface Interface Return

from
device

Host Host Host Unknown

Host

Number of NumberOfRepetitions NumberOfRepetitions

Repetitions

Time out Timeout Timeout 1000

Data block size DataBlockSize 128

DSCP DSCP DSCP

TimeZone LocalTimeZone LocalTimeZone

The following WAN Interface parameters are to determine the WAN interface of the CPE,
InternetGatewayDevice.Layer3Forwarding.Default and Device.IP.Interface:

Connection DefaultConnectionService Interface Returned from Device

The following Diagnostics parameters are to determine the state of the IP ping test of the CPE,
InternetGatewayDevice.IPPingDiagnostics and Device.IP.Diagnostics.IPPing:

DiagnosticsState DiagnosticsState DiagnosticsState Returned from

Device

5.10.0.4 Test Setup:

1. ACS connected to the network

2. CPE connected to the network and configured with an ACS URL that corresponds to the
ACS in Setup #1
3. Wireshark running between ACS and CPE.

5.10.0.5 Procedure:

1. ACS performs a GetParameterValues RPC on the WAN Interface parameter to determine

the current interface in the parameter section above.
2. ACS performs a SetParameterValues RPC on the ping diagnostics parameters in the
parameter section above.
3. ACS performs a GetParameterValues on the InternetGatewayDevice.IPPingDiagnostics or
Device.IP.Diagnostics.IPPing to determine results of ping test

5.10.0.6 Test Metrics:

1. Validate that an Inform RPC is sent from the ACS with Event Code “8 DIAGNOSTICS
COMPLETE”
2. Validate that the DiagnosticsState is set to Error_NoRouteToHost.

5.11 TraceRoute Diagnostics – Error Condition

5.11.0.1 Purpose:

This test is designed to validate that the CPE supports TraceRoute diagnostics test and reports
results appropriately to the ACS.

5.11.0.2 References:

InternetGatewayDevice:1.6 and Device:2.6

5.11.0.3 Parameters:

The following parameters with the InternetGatewayDevice.TraceRouteDiagnostics. table (for

devices that implement the InternetGatewayDevice:1 data model) and
Device.IP.Diagnostics.TraceRoute. (for devices that implement the Device:2 data model) are
required to be implemented for this test:

Interface Interface Return from

device

Host Host Host Ping host

Number of NumberOfTries
Tries

Time out Timeout Timeout 5000

Data block size DataBlockSize DataBlockSize 128

DSCP DSCP DSCP

Max Hop Count MaxHopCount MaxHopCount

Diagnostic DiagnosticsState DiagnosticsState

State

5.11.0.4 Test Setup:

1. ACS connected to the network

2. CPE connected to the network and configured with an ACS URL that corresponds to the

ACS in Setup #1
3. Wireshark running between ACS and CPE.
4. Ensure there are at least 2 hops between the CPE and Host

5.11.0.5 Procedure:

5.11.0.6 Test Metrics:

1. The DUT can properly respond to the GetParameterValues request on WAN interface.
2. The DUT is able to properly respond to the SetParameterValues for diagnostics parameter.
3. Validate that the DiagnosticsState is set to “Error_MaxHopCountExceeded”

5.12 IPPing Diagnostics – Periodic Inform

5.12.0.1 Purpose:

To verify that an ACS can perform an IP Ping Diagnostics test on the CPE and receive a periodic
inform without an Diagnostic complete event before the diagnostic completes.

5.12.0.2 References:

InternetGatewayDevice:1.6 and Device:2.6

5.12.0.3 Parameters:

The following parameters within the InternetGatewayDevice.IPPingDiagnostics. table (for devices

that implement the InternetGatewayDevice:1 data model) or Device.IP.Diagnostics.IPPing. table
(for devices that implement the Device:2 data model) are required to be implemented for this
test:

Diagnostics State DiagnosticsState DiagnosticsState Requested

Interface Interface Interface Return

from
device

Host Host Host Unknown

Host

Number of NumberOfRepetitions NumberOfRepetitions 10000

Repetitions

Time out Timeout Timeout 100000

Data block size DataBlockSize 128

DSCP DSCP DSCP

TimeZone LocalTimeZone LocalTimeZone

The following WAN Interface parameters are to determine the WAN interface of the CPE,
InternetGatewayDevice.Layer3Forwarding.Default and Device.IP.Interface:

Connection DefaultConnectionService Interface Returned from Device

The following Diagnostics parameters are to determine the state of the IP ping test of the CPE,
InternetGatewayDevice.IPPingDiagnostics and Device.IP.Diagnostics.IPPing:

DiagnosticsState DiagnosticsState DiagnosticsState Returned from

Device

The following parameters are to set to ensure the CPE performs a periodic inform prior to the
completion of Diagnostic, InternetGatewayDevice.ManagementServer and
Device.IP.Diagnostics.ManagementServer:

PeriodicInformInterval PeriodicInformInterval PeriodicInformInterval 30

5.12.0.4 Test Setup:

1. ACS connected to the network

2. CPE connected to the network and configured with an ACS URL that corresponds to the
ACS in Setup #1
3. Wireshark running between ACS and CPE.

5.12.0.5 Procedure:

1. ACS performs a SetParameterValues RPC on the ManagementServer parameters in the

parameter section above.
2. ACS performs a GetParameterValues RPC on the WAN Interface parameter to determine
the current interface in the parameter section above.
3. ACS performs a SetParameterValues RPC on the ping diagnostics parameters in the
parameter section above.
4. ACS performs a GetParameterValues on the InternetGatewayDevice.IPPingDiagnostics or
Device.IP.Diagnostics.IPPing to determine results of ping test

5.12.0.6 Test Metrics:

1. During diagnostic: Validate that the Inform RPC does not have a “8 DIAGNOSTICS
COMPLETE” Event Code
2. After diagnostic:-Validate that an Inform RPC is sent from the ACS with Event Code “8
DIAGNOSTICS COMPLETE”

5.13 Deny/Allow Inbound IPv6 (Device:2 Only)

5.13.0.1 Purpose:

To verify the ACS can configure a firewall on the CPE that allows certain IPv6 traffic from the
WAN side.

5.13.0.2 References:

Device:2.2

5.13.0.3 Parameters:

The following parameters are required to be implemented for this test:

Enable true

Config Advanced

AdvancedLevel Device.Firewall.Level.{i}.

Chain Returned from

device

DefaultPolicy Drop

Enable true

Target Accept

DestInterface Default WAN

Interface

DestIP IPv6 Address

SourceIP IPv6 Address

Protocol int[-1:255]

DestPort int[-1:65535]

5.13.0.4 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Refer to Determine WAN Interface to determine the WAN interface.
3. Two Devices that can send and receive TCP and UDP connections over IPv6 connected to
the LAN side of the CPE (End Device 1 and End Device 2)
4. Device that can send and receive TCP and UDP connections over IPv6 connected on the
WAN side of the CPE (WAN Device)
5. Have a Network Analyzer to capture traffic between the CPE and the End Device.

5.13.0.5 Procedure:

1. Configure ACS to send an AddObject RPC for Device.Firewall.Level and record the returned
instance number.

2. Configure ACS to send a GetParameterValues RPC for Device.Firewall.Level.{i}.Chain.

3. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule using the path
returned in step 2 and record the returned instance number.

4. ACS performs a SetParameterValues RPC on the following parameters using the instance
numbers returned in steps 1-3.

Config Advanced

AdvancedLevel Device.Firewall.Level.{i}.

Chain Returned from

device

DefaultPolicy Drop

Target Accept

DestIP <Unused IP
Address>

SourceIP <Unused IP
Address>

5. ACS enables the Firewall by sending a SetParameterValues RPC for Device.Firewall.Enable

with the value set to “true.”

6. WAN Device attempts to open a TCP connection over IPv6, destination port 25, with End
Device 1.

7. WAN Device attempts to open a TCP connection over IPv6, destination port 25, with End
Device 2.

8. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule and record the
returned instance number.

9. ACS Configures the new Firewall Rule by sending a SetParameterValues RPC with the
following name/value pairs using the instance number returned in step 8.

Enable true

Target Accept

DestInterface Default WAN

Interface

Protocol

DestPort 25

DestIP End Device1 IP

10. WAN Device attempts to open a TCP connection over IPv6, destination port 25, with End
Device 1.

11. WAN Device attempts to open a TCP connection over IPv6, destination port 25, with End
Device 2.

12. Configure ACS to send an AddObject RPC for Device.Firewall.Chain.{i}.Rule and record the
returned instance number.

13. ACS Configures the new Firewall Rule by sending a SetParameterValues RPC with the
following name/value pairs using the instance number returned in step 12.

Enable true

Target Accept

DestInterface Default WAN

Interface

Protocol

DestPort 25

DestIP End Device2 IP

14. WAN Device attempts to open a TCP connection over IPv6, destination port 25, with End
Device 1.

15. WAN Device attempts to open a TCP connection over IPv6, destination port 25, with End
Device 2.

5.13.0.6 Test Metrics:

1. In Step 6, CPE does not forward TCP traffic from WAN Device to End Device1.
2. In Step 7, CPE does not forward TCP traffic from WAN Device to End Device2.
3. In Step 10, CPE forwards TCP traffic from WAN Device to End Device1.
4. In Step 11, CPE does not forward TCP traffic from WAN Device to End Device2.
5. In Step 14, CPE forwards TCP traffic from WAN Device to End Device1.
6. In Step 15, CPE forwards TCP traffic from WAN Device to End Device2.

5.14 Download Diagnostics over HTTPS –

TotalBytesReceived

5.14.0.1 Purpose:

To verify that an ACS and CPE can interoperate while performing the download diagnostics
function over HTTPS. This test will be run if supported on the CPE.

5.14.0.2 References:

InternetGatewayDevice.1.3
Device:2 [10]

5.14.0.3 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

DiagnosticsState Requested

Interface Returned from device

DownloadURL <HTTPS URL of file on

server>

TestBytesReceived Returned from device

TotalBytesReceived Returned from device

DownloadTransports Returned from device

For CPE that implement the InternetGatewayDevice:1 root data model:

DiagnosticsState Requested

Interface Returned from device

DownloadURL <HTTPS URL of file on

server>

TestBytesReceived Returned from device

TotalBytesReceived Returned from device

DownloadTransports Returned from

device

The DownloadTransports parameter MUST include HTTP for this test to be executed.

5.14.0.4 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an HTTP server and file to perform the download over HTTPS. The file should be big
enough for the file transfer to last at least 30 seconds.

5.14.0.5 Procedure:

1. On the ACS schedule a SetParameterValues RPC on the Interface, DownloadURL and

5.14.0.6 Test Metrics:

1. Verify that the SetParameterValuesResponse RPC is correct

parameter.
1. If the value is “Completed” verify that the values in the DownloadDiagnostic object are
the same as they were before the reboot.
2. Verify that TotalBytesReceived is within 1% of the measured traffic.

5.15 Upload Diagnostics over HTTP -

TotalBytesSent

5.15.0.1 Purpose:

To verify that an ACS and CPE can inter-operate while performing the upload diagnostics
function over HTTP. This test will be run if supported on the CPE.

5.15.0.2 References:

InternetGatewayDevice.1.3
Device:2 [10]

5.15.0.3 Parameters:

The following parameters are required to be implemented for this test:

For CPE that implement the Device:2 root data model:

DiagnosticsState Requested

Interface Returned from device

UploadURL <HTTPS URL of server>

TestFileLength <value long enough for the upload to last

30 seconds>

TotalBytesSent Returned from device

UploadTransports Returned from device

For CPE that implement the InternetGatewayDevice:1 root data model:

DiagnosticsState Requested

Interface Returned from device

UploadURL <HTTPS URL of server>

TestFileLength <value long enough for the upload to last

30 seconds>

TotalBytesSent Returned from device

UploadTransports Returned from

device

The UploadTransports parameter MUST include HTTP for this test to be executed.

5.15.0.4 Test Setup:

1. Refer to Common Test Setup for setup steps.

2. Have an HTTP server to perform the Upload over HTTPS.
3. Wireshark running between ACS and CPE.

5.15.0.5 Procedure:

1. On the ACS schedule a SetParameterValues RPC on the Interface, UploadURL and

DiagnosticsState parameters listed in the parameters section.
2. Allow the CPE to perform the specific diagnostic tests and send an Inform message with an
event code of “8 DIAGNOSTICS COMPLETE”.
3. On the ACS schedule a GetParameterValues RPC on the UploadDiagnostics object.
4. Perform a reboot of the CPE
5. On the ACS schedule a GetParameterValues RPC on the UploadDiagnostics object.

5.15.0.6 Test Metrics:

1. Verify that the SetParameterValuesResponse RPC is correct

2. Verify that an Inform message is received with an event code of “8 DIAGNOSTICS
COMPLETE”
3. Verify that the GetParameterValuesResponse contains a valid value for the DiagnosticsState
parameter.
4. Verify that the test server received a file of TestLengthBytes size.
5. Verify that EOMTime – BOMTime is within 1 second of the time that the file server reports
the transfer took.
6. Verify that the GetParameterValuesResponse contains a valid value for the DiagnosticsState

parameter.
1. If the value is “Completed” verify that the values in the UploadDiagnostic object are the
same as they were before the reboot.
2. Verify that TotalBytesSent is within 1% of the measured traffic.

6 Open Issues

Item x

InteliLite-AMF25 - Global Guide PDF
100% (4)
InteliLite-AMF25 - Global Guide PDF
661 pages
Calibration Quick Ref Card
No ratings yet
Calibration Quick Ref Card
2 pages
Global Cache: Installation and Operations Guide
No ratings yet
Global Cache: Installation and Operations Guide
26 pages
InteliLite 9 Global Guide
100% (1)
InteliLite 9 Global Guide
393 pages
SecoNET Tech 1-En
No ratings yet
SecoNET Tech 1-En
71 pages
Beamforming (TDD) Feature Parameter Description
No ratings yet
Beamforming (TDD) Feature Parameter Description
56 pages
Reference Manual: Web-Based Interface Ruggedized ABB FOX Router AFR677
No ratings yet
Reference Manual: Web-Based Interface Ruggedized ABB FOX Router AFR677
192 pages
Baumer PROFINET MA EN
No ratings yet
Baumer PROFINET MA EN
43 pages
ERAN Feature Documentation ERAN16.1 - 10 20230721170353
No ratings yet
ERAN Feature Documentation ERAN16.1 - 10 20230721170353
331 pages
Global Cache: Installation and Operations Guide
No ratings yet
Global Cache: Installation and Operations Guide
27 pages
MX300 E-Manual PDF
No ratings yet
MX300 E-Manual PDF
148 pages
13 VoLTE
No ratings yet
13 VoLTE
341 pages
InteliGateway Global-Guide 2022-05
No ratings yet
InteliGateway Global-Guide 2022-05
61 pages
Secondary Micro User Guide
No ratings yet
Secondary Micro User Guide
52 pages
Volume v Part 3 Section 2(2)
No ratings yet
Volume v Part 3 Section 2(2)
130 pages
Palo Alto Networks Certified Network Security Engineer (Pcnse) Exam Blueprint
No ratings yet
Palo Alto Networks Certified Network Security Engineer (Pcnse) Exam Blueprint
11 pages
bwx_8305
No ratings yet
bwx_8305
75 pages
Cherry Bomb: Cherry Blossom Internal Validation and Verification (V&V) Report For Cherry Blossom Version 5.0 (CDRL 15c) (U)
No ratings yet
Cherry Bomb: Cherry Blossom Internal Validation and Verification (V&V) Report For Cherry Blossom Version 5.0 (CDRL 15c) (U)
6 pages
TR-124_Issue8
No ratings yet
TR-124_Issue8
186 pages
Manual For All Netlink Ethernet Versions
No ratings yet
Manual For All Netlink Ethernet Versions
65 pages
Palo Alto Networks Certified Network Security Engineer (Pcnse) Exam Blueprint
No ratings yet
Palo Alto Networks Certified Network Security Engineer (Pcnse) Exam Blueprint
11 pages
GS3 PGE Technical Reference
No ratings yet
GS3 PGE Technical Reference
129 pages
Baumer BUDE-PROFINET MA EN
No ratings yet
Baumer BUDE-PROFINET MA EN
41 pages
Energy Conservation and Emission Reduction
No ratings yet
Energy Conservation and Emission Reduction
147 pages
InteliLite 9 1 3 0 Global Guide
No ratings yet
InteliLite 9 1 3 0 Global Guide
422 pages
Ether RM Web L2E Rel60 en
No ratings yet
Ether RM Web L2E Rel60 en
204 pages
Outline Testout Routingswitchingpro Enus 6 - 0 - X
0% (1)
Outline Testout Routingswitchingpro Enus 6 - 0 - X
22 pages
Pac120 5715-719uk
No ratings yet
Pac120 5715-719uk
88 pages
InteliLite-AMF20 - Global Guide PDF
50% (2)
InteliLite-AMF20 - Global Guide PDF
506 pages
Profinet RT Mca 120 Programming Guide PDF
No ratings yet
Profinet RT Mca 120 Programming Guide PDF
60 pages
PCAN PassThru API Rev 05.00 - UserMan - Eng
No ratings yet
PCAN PassThru API Rev 05.00 - UserMan - Eng
29 pages
Huawei LTE Carrier Aggregation
No ratings yet
Huawei LTE Carrier Aggregation
856 pages
KAS ReleaseNotes
No ratings yet
KAS ReleaseNotes
21 pages
SGP 21-v2 4
No ratings yet
SGP 21-v2 4
106 pages
Mmwave SDK User Guide
No ratings yet
Mmwave SDK User Guide
80 pages
User Manual For Professional Firmware WZR-HP-G300NH / WZR-HP-G300NH2
No ratings yet
User Manual For Professional Firmware WZR-HP-G300NH / WZR-HP-G300NH2
184 pages
ComAp Manual AIO - Gas 1.1.0 GlobalGuide en 2018 01
100% (1)
ComAp Manual AIO - Gas 1.1.0 GlobalGuide en 2018 01
934 pages
TBEN-S2-2COM-4DXP: Compact I/O Module For Serial Data Transmission
No ratings yet
TBEN-S2-2COM-4DXP: Compact I/O Module For Serial Data Transmission
171 pages
Sun Ultra 10 Manual
No ratings yet
Sun Ultra 10 Manual
268 pages
ePMP - Release Notes - System Release 4.7.0.1
No ratings yet
ePMP - Release Notes - System Release 4.7.0.1
7 pages
CSFB Emergency Call
No ratings yet
CSFB Emergency Call
63 pages
InteliLite AMF25 1 7 0 Global Guide PDF
No ratings yet
InteliLite AMF25 1 7 0 Global Guide PDF
741 pages
Mobility Management in Connected Mode
No ratings yet
Mobility Management in Connected Mode
130 pages
Reference Manual: Web-Based Interface Industrial ETHERNET (Gigabit) Switch RS20/RS30/RS40, MS20/MS30, OCTOPUS
No ratings yet
Reference Manual: Web-Based Interface Industrial ETHERNET (Gigabit) Switch RS20/RS30/RS40, MS20/MS30, OCTOPUS
214 pages
WorldCast Horizon Manual v2.0 - A4
No ratings yet
WorldCast Horizon Manual v2.0 - A4
85 pages
InteliMains 210 1 0 0 Global Guide
No ratings yet
InteliMains 210 1 0 0 Global Guide
620 pages
MS60044 - 03E MTU GO Premium System Documentation
No ratings yet
MS60044 - 03E MTU GO Premium System Documentation
109 pages
TENDA_ONT_XPON_HG10CV2.0_Manual
No ratings yet
TENDA_ONT_XPON_HG10CV2.0_Manual
153 pages
5G RAN Sharing_Hw
No ratings yet
5G RAN Sharing_Hw
122 pages
Jade Administrator'S Guide: Usage Restricted According TO License Agreement
No ratings yet
Jade Administrator'S Guide: Usage Restricted According TO License Agreement
37 pages
Premier Hb9210™ Technical Manual Rev 05
No ratings yet
Premier Hb9210™ Technical Manual Rev 05
250 pages
Wi-Fi WPS Test Plan Wi-Fi Alliance
No ratings yet
Wi-Fi WPS Test Plan Wi-Fi Alliance
48 pages
Barox Switch Programming Manual
No ratings yet
Barox Switch Programming Manual
69 pages
SGP 22-v3 0
No ratings yet
SGP 22-v3 0
482 pages
G10
No ratings yet
G10
60 pages
Implementing Cisco Application Centric Infrastructure v1.0 (300-620)
No ratings yet
Implementing Cisco Application Centric Infrastructure v1.0 (300-620)
2 pages
Baseband Deployment-compressed
No ratings yet
Baseband Deployment-compressed
78 pages
Jet Essentials
No ratings yet
Jet Essentials
57 pages
MikroTik MTCNA
From Everand
MikroTik MTCNA
Ehab Abo Elazm
No ratings yet
CompTIA A+ Complete Review Guide: Core 1 Exam 220-1101 and Core 2 Exam 220-1102
From Everand
CompTIA A+ Complete Review Guide: Core 1 Exam 220-1101 and Core 2 Exam 220-1102
Troy McMillan
5/5 (2)
Fortinet FCP - FortiGate 7.6 Administrator Exam Preparation
From Everand
Fortinet FCP - FortiGate 7.6 Administrator Exam Preparation
Georgio Daccache
No ratings yet
TR 521
No ratings yet
TR 521
70 pages
TR 522
No ratings yet
TR 522
44 pages
TR 451
No ratings yet
TR 451
113 pages
TR-181 - Device Data Model For CWMP and USP
No ratings yet
TR-181 - Device Data Model For CWMP and USP
223 pages
TR-369a2 - User Services Platform (USP)
No ratings yet
TR-369a2 - User Services Platform (USP)
213 pages
80066cajournal May2024 17
No ratings yet
80066cajournal May2024 17
8 pages
Variable and Verbal Expressions PDF
No ratings yet
Variable and Verbal Expressions PDF
4 pages
Cascading Style Sheets Level 2 (CSS2) :: Page 1 of 2
No ratings yet
Cascading Style Sheets Level 2 (CSS2) :: Page 1 of 2
2 pages
Intel® NUC Kits NUC13ANKv7
No ratings yet
Intel® NUC Kits NUC13ANKv7
19 pages
Introduction
No ratings yet
Introduction
51 pages
Users Manual 515778
No ratings yet
Users Manual 515778
75 pages
DDOOCP Assignment Spring 2024 - Winter 2024 (7039) 1
No ratings yet
DDOOCP Assignment Spring 2024 - Winter 2024 (7039) 1
4 pages
AG198 Datasheet
No ratings yet
AG198 Datasheet
1 page
Gartner 2006 PDF
No ratings yet
Gartner 2006 PDF
11 pages
Tic Tac Toe: Bachelor of Technology
No ratings yet
Tic Tac Toe: Bachelor of Technology
16 pages
The Social Experiment - 9
No ratings yet
The Social Experiment - 9
1 page
Free Internet Access Program
No ratings yet
Free Internet Access Program
2 pages
PMC240 Quiz 2
No ratings yet
PMC240 Quiz 2
4 pages
TM112 TMA Spring2019 2020
No ratings yet
TM112 TMA Spring2019 2020
4 pages
VATSIM P1 Rating: VATSIM Online Pilot Rating
No ratings yet
VATSIM P1 Rating: VATSIM Online Pilot Rating
19 pages
3 Robert Sokolowski - Natural and Artificial Intelligence
No ratings yet
3 Robert Sokolowski - Natural and Artificial Intelligence
20 pages
Manual 2346 PDF
No ratings yet
Manual 2346 PDF
12 pages
2024 Electric Capital Developer Report
No ratings yet
2024 Electric Capital Developer Report
218 pages
Foxboro Evo SCD6000 RTU RoHS Compliance Information - 20191106 - R1
No ratings yet
Foxboro Evo SCD6000 RTU RoHS Compliance Information - 20191106 - R1
6 pages
Configure L2TP Over IPsec Between Window
No ratings yet
Configure L2TP Over IPsec Between Window
28 pages
3 MediaGrid Version 4.1 To 4.3 Updates
No ratings yet
3 MediaGrid Version 4.1 To 4.3 Updates
55 pages
Logcat
No ratings yet
Logcat
16 pages
Control System Analysis New CHP 1 and 2
No ratings yet
Control System Analysis New CHP 1 and 2
109 pages
Next Best Actions Pilot Documentation
No ratings yet
Next Best Actions Pilot Documentation
87 pages
Storage Devices
No ratings yet
Storage Devices
85 pages
KH105 Multi Channel Process Indicator Manual: Xiamen Kehao Automation Co., LTD
No ratings yet
KH105 Multi Channel Process Indicator Manual: Xiamen Kehao Automation Co., LTD
17 pages
Hardware Setup and Software Installation
No ratings yet
Hardware Setup and Software Installation
50 pages
Serene Joshua Finalresume
No ratings yet
Serene Joshua Finalresume
1 page
Rks Elektrik Unhan 1
No ratings yet
Rks Elektrik Unhan 1
28 pages