Contents

3  CWMP Configuration

3.1  Introduction to CWMP

3.2  Principles

3.2.1  CWMP Network Model

3.2.2  CWMP Implementation

3.2.3  CPE Management

3.3  Applications

3.4  Default Configurations

3.5  Configuring CWMP

3.5.1  Enabling CWMP

3.5.2  Configuring the CWMP Connection

3.5.3  Configuring CWMP Authentication

3.5.4  (Optional) Configuring the CWMP Uploading Function

3.5.5  Checking the Configuration

3.6  Configuration Examples

3.6.1  Example for Configuring CWMP

3.7  Common Configuration Error

3.7.1  Failure to Manage CPE Using CWMP

3.8  FAQ

3.8.1  How Can an AR Router Correctly Connect to an ACS?

3.9  References

3  CWMP Configuration

This chapter describes the basic concept, configuration procedures, and configuration examples of CWMP.

3.1  Introduction to CWMP

This section describes the definition, background, and functions of CWMP.

Definition

On a DSL network, device management is difficult because there are many user-side devices distributed at different locations. CWMP defines that the customer premises equipment (CPE) is remotely managed by an auto-configuration server (ACS). CWMP facilitates CPE management, reduces maintenance and operation costs, and improves troubleshooting efficiency.

CWMP, also called Technical Report 069 (TR-069), is a technical specification drafted by the Digital Subscriber's Line forum (DSL forum, which was later renamed as Broadband Forum).

Purpose

CWMP provides methods to manage and configure home network devices on the next generation network. Currently, terminal management faces the following problems:

  • Different vendors manage their terminals in different ways.

    Terminal vendors manage their terminals by using different protocols such as the Optical Network Terminal Management and Control Interface (OMCI) and Embedded Operations Channel (EOC) protocols. Carriers must integrate these vendors' network management systems multiple times to implement unified management.

  • Various terminals lead to complex terminal management.

    With emergence of new access technologies, various terminals are developed, such as access points (APs), optical network terminals (ONTs), and shared risk groups (SRGs), which are difficult to manage.

  • Troubleshooting is difficult because of a large number of terminals.

    On a network, most faults occur on the user side, where a large number of terminals are scattered; therefore, troubleshooting is difficult.

To solve the preceding problems, CWMP defines a mechanism to manage the CPE by an ACS. This facilitates CPE management, reduces maintenance and operation costs, and improves troubleshooting efficiency.

3.2  Principles

This section describes the implementation of CWMP.

3.2.1  CWMP Network Model

Figure 3-1 shows the CWMP network model.

Figure 3-1  CWMP network model

A CWMP network model contains:
  • ACS: manages and maintains CPEs on the network.
  • CPE: managed by the ACS.
NOTE:
A router is deployed as a CPE.

3.2.2  CWMP Implementation

CWMP Process

Figure 3-2 shows the CWMP working process when the ACS changes a parameter value on the CPE.
Figure 3-2  CWMP process

The CWMP process is as follows:

  1. A CPE initiates a session.

    If an ACS initiates a session, it sends a Connect request to the CPE (which functions as an HTTP server) to set up a session.

  2. The CPE and ACS use Security Socket Layer (SSL) protocol to set up a secure connection.
  3. The CPE invokes the Remote Procedure Call (RPC) method Inform to send an Inform request to the ACS, reporting device information and requesting a CWMP connection.
  4. After the CPE is authenticated, the ACS sends an Inform response. The Inform method is complete and the CWMP connection is set up.
  5. The CPE sends an empty HTTP post message to the ACS, indicating that the CPE does not invoke any more RPC methods supported by the ACS.
  6. The ACS invokes the GetParameterValues method to query CPE parameters.
  7. The CPE sends a GetParameterValues response containing the queried parameters to the ACS. The GetParameterValues method is complete.
  8. The ACS invokes the SetParameterValues method to set CPE parameters.
  9. The CPE sends a SetParameterValues response containing the parameter settings to the ACS. The SetParameterValues method is complete.
  10. The ACS sends an empty HTTP response to the CPE, indicating that the ACS does not invoke any more RPC methods supported by the CPE.
  11. The CPE terminates the connection.

As shown in Figure 3-2, the CWMP session goes through three phases.

Session initiation phase

A session can be initiated by a CPE or an ACS.
  • A CPE initiates a session in the following scenarios:

    • After startup, the CPE searches for an ACS based on the local configuration or the ACS URL allocated by the Dynamic Host Configuration Protocol (DHCP) server, and then initiates a session.

    • The CPE is configured to send Inform messages at intervals. The CPE will automatically send an Inform message to initiate a session when the interval arrives (1 hour for example).

    • The CPE is configured to send Inform messages at a specified time. The CPE will automatically send an Inform message at the time to initiate a session.

    • If session setup is interrupted unexpectedly and the number of CPE auto-connection retries has not reached the upper limit, the CPE automatically sets up a new connection.

  • An ACS initiates a session.

    An ACS can send a Connect request to a CPE at any time. After the CPE authenticates the request, a session between the CPE and the ACS is set up.

    The prerequisite for this method is that the CPE and the ACS have communicated with each other before. During the first communication between the CPE and the ACS, the ACS saves the CPE IP address in the address list. Then it can initiate a session in subsequent communication with the CPE.

CWMP uses security mechanisms to protect communication between a CPE and an ACS. The security mechanisms prevent the transactions between the CPE and the ACS from being tampered and ensure confidentiality of the transactions. CWMP supports the following security mechanisms:
  • CPE and ACS authentication:

    • CPE authentication on the ACS side: A CPE sends an Inform request based on the ACS URL configured locally to communicate with an ACS. After the CPE is authenticated (the ACS user name and password in the Inform request are the same as those configured on the ACS), a session is set up between the CPE and the ACS.

    • ACS authentication on the CPE side: An ACS sends an Inform reques containing a CPE IP address to communicate with a CPE. After the ACS is authenticated (the CPE user name and password in the HTTP request are the same as those configured on the CPE), a session is set up between the CPE and the ACS.

  • Security Socket Layer (SSL) authentication:

    It ensures transaction confidentiality and data integrity and enables the CPE and ACS to authenticate each other using certificates.

    SSL operates independently of application-layer protocols. Any types of application-layer protocols (including HTTP, FTP, and Telnet) can set up connections based on SSL. SSL finishes data encryption, key negotiation, and server authentication before the application-layer protocols set up connections. Therefore, all data transmitted by the application-layer protocols is encrypted.
    NOTE:
    Certificate contains personal or an enterprise's information and public key:
    • Public key: The two ends share a public key to encrypt data and verify signatures.
    • Private key: Each end has a private key to decrypt data and sign signature.
    • Signature: Information containing a signature cannot be modified by anyone except the creator. It ensures data security and integrity.

Communication phase

After a session is initiated, a CPE or an ACS can send requests to each other to perform operations. For example, the ACS can query and set CPE parameters, and the CPE can upload files to or download files from the file server specified by the ACS.

Session termination phase

Only a CPE can terminate a session.

If the ACS and CPE have sent all necessary requests and received all responses, the CPE terminates the session.

CWMP Operation Methods

An ACS manages and monitors a CPE by performing a series of operations. These operations are called RPC methods in CWMP.

CWMP supports the following standard RPC methods:

  • Generic method: Both the CPE and the ACS must support this method. Table 3-1 describes a generic method, which can be invoked by both the CPE and the ACS.

    Table 3-1  Generic method

    Method

    Description

    GetRPCMethods

    Used to obtain RPC methods supported by the CPE and the ACS.

  • CPE methods: The CPE must support these methods. Table 3-2 lists the CPE methods, which can be invoked only by the ACS.
    Table 3-2  CPE methods

    Method

    Description

    SetParameterValues Used by an ACS to set CPE parameters.
    GetParameterValues Used by an ACS to obtain CPE parameter values.
    GetParameterNames Used by an ACS to discover accessible parameters of a CPE.
    SetParameterAttributes Used by an ACS to set attributes of CPE parameters.
    GetParameterAttributes Used by an ACS to obtain CPE parameter attributes.
    AddObject Used by an ACS to create instances for a multi-instance object in the CPE data model.
    DeleteObject Used by an ACS to delete instances of a multi-instance object from the CPE data model.
    Download Used by an ACS to request a CPE to download a file from a specified URL and use the downloaded file to replace the local file on the CPE.
    Upload Used by an ACS to request a CPE to upload a file to a specified URL.
    Reboot Used by an ACS to remotely restart a CPE when the CPE is faulty or the CPE software is upgraded.
    FactoryReset Used by an ACS to restore the factory settings of a CPE.
  • ACS methods: The ACS must support these methods. Table 3-3 lists the ACS methods, which can be invoked only by the CPE.
    Table 3-3  ACS methods

    Method

    Description

    Inform Used by a CPE to send an Inform message to an ACS when the CPE needs to initiate a session with the ACS or periodically send local information to the ACS, or when the CPE bottom-layer configuration changes.
    TransferComplete Used by a CPE to notify an ACS that requested file download or upload is complete no matter whether the file is successfully downloaded or uploaded.

3.2.3  CPE Management

CWMP provides many CPE management functions, which improve CPE operation efficiency and decrease network management problems. Main CPE management functions include:
  • Automatic configuration
  • File management
  • Status and performance monitoring
  • Fault diagnosis

Automatic Configuration

CWMP enables an ACS to automatically configure CPEs. When a CPE has set up a session with an ACS, the ACS automatically delivers configurations to the CPE. Automatic configuration parameters include:

  • URL: address of the ACS
  • Username: user name used by the CPE to set up a session with the ACS
  • Password: password used by the CPE to set up a session with the ACS
  • PeriodicInformEnable: indicates whether Inform messages are sent automatically
  • PeriodicInformInterval: interval at which Inform messages are sent
  • PeriodicInformTime: time when Inform messages are sent
  • ConnectionRequestUsername: CPE user name
  • ConnectionRequestPassword: CPE password

File Management

CWMP enables CPEs to:
  • Upload files

    A CPE can upload the configuration file and log files to the server specified by an ACS to back up important data.

  • Download files

    A CPE can use HTTP, HTTPS, or FTP to download web page files, configuration files, system software packages, patch files, license files, and any other files from a file server specified by an ACS. After downloading a file, the CPE checks the validity of the file and processes the file according to the check result. For example, if the downloaded file is a configuration file, the CPE automatically specifies it as the configuration file for next startup and sends the download result (succeeded or failed) to the ACS.

NOTE:
  • Currently, the CPE does not support file download using digital signature.

  • To download a file using HTTPS, the CPE must set up a Secure Sockets Layer (SSL) connection to the ACS.

Status and Performance Monitoring

CWMP enables an ACS to monitor the status and performance parameters of the connected CPEs. Performance and functions vary with CPEs. Therefore, an ACS must be able to identify performance of different CPEs and monitor configurations and configuration changes of each CPE.

CWMP allows network administrators to define monitoring parameters and obtain the CPE status and statistics using an ACS.

NOTE:

Currently, the CPE does not support the data model defined in TR-143 among all technical specifications that define status and performance monitoring.

Fault Diagnosis

CWMP enables an ACS to diagnose CPE faults using methods such as ping, traceroute, asynchronous transfer mode (ATM) loopback, and digital subscriber line (DSL) detection.

NOTE:

Currently, the CPE does not support the data model defined in TR-098 among all technical specifications that define fault diagnosis.

3.3  Applications

This section describes the applicable scenario of CWMP.

As shown in Figure 3-3, enterprise branches connect to the Internet through the enterprise gateway router. CWMP is deployed between the enterprise headquarters and branches. The router functions as a CPE. The enterprise headquarters control and manage the router using an ACS. After connecting to the router, the ACS manages the system startup file and configuration file for the router, configures the router, monitors the router status and performance, and diagnoses router faults.

Figure 3-3  CWMP application

3.4  Default Configurations

The following table describes the default CWMP configurations.

CWMP default configuration

Parameter

Default Value

CWMP function

Disabled

Function for the CPE to periodically send Inform messages

Disabled

Interval at which the CPE sends Inform messages

600 seconds

Maximum number of connection reattempts

3

Close-wait timer of the CPE

30 seconds

3.5  Configuring CWMP

This section describes how to configure CWMP.

Pre-configuration Tasks

Before configuring CWMP, complete the following tasks:
  • Ensuring that there is a reachable route between the router and the ACS

Configuration Procedure

To configure CWMP, perform the following operations in sequence. You can choose whether to perform optional operations based on site requirements.

3.5.1  Enabling CWMP

Context

The CWMP configurations take effect only after the CWMP function is enabled.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    cwmp

    The CWMP view is displayed.

  3. Run:

    cwmp enable

    The CWMP function is enabled.

    By default, the CWMP function is disabled.

3.5.2  Configuring the CWMP Connection

Context

To allow the ACS to manage the CPE, set up a connection between the ACS and the CPE.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    cwmp

    The CWMP view is displayed.

  3. Run:

    cwmp acs url url

    The ACS's URL to which the CPE connects is specified.

    NOTE:

    To use the HTTPS URL, you must configure SSL authentication.

  4. (Optional) Run:

    cwmp permit interface { interface-type interface-number } &<1-5>

    Physical interfaces on the CPE to which the ACS can connect are specified.

    By default, the ACS can connect to all the physical interfaces on the CPE.

  5. (Optional) Run:

    cwmp cpe connect interface interface-type interface-number

    The CWMP connection interface is specified.

    Generally, a CPE obtains a CWMP connection interface from all the interfaces to which the ACS have reachable routes. If the obtained interface does not connect the CPE to the ACS, CWMP connection fails to be set up. Therefore, a CWMP connection interface needs to be specified manually.

  6. (Optional) The CPE can use the following methods to send inform messages:
    • Sending inform messages periodically
    1. Run:

      cwmp cpe inform interval enable

      The CPE is enabled to periodically send inform messages.

      By default, the CPE does not periodically send inform messages.

    2. Run:

      cwmp cpe inform interval seconds

      The interval at which a CPE sends inform messages is set.

      By default, a CPE sends an inform message every 600 seconds.

    • Sending an inform message at a specified time
    1. Run:

      cwmp cpe inform time time

      The time when a CPE sends an inform message is set.

      By default, no time is specified for the CPE to send an inform message.

    NOTE:

    You can configure either one or both methods.

  7. (Optional) Run:

    cwmp cpe inform product-class device-type

    The actual product type of the CPE is added to the session initiated by the CPE to the ACS.

    By default, the session initiated by the CPE to the ACS contains the product type AccessRouter.

  8. (Optional) Run:

    cwmp cpe connect retry times

    The maximum number of attempts the CPE can make to retry a connection is set.

    By default, the maximum number of attempts is 3.

  9. (Optional) Run:

    cwmp cpe wait timeout seconds

    The connection timeout interval is configured for the CPE. If no data is transmitted within the timeout interval, the connection between the CPE and ACS is torn down.

    By default, connection timeout interval is 30 seconds.

3.5.3  Configuring CWMP Authentication

Context

CWMP uses security mechanisms to protect communication between a CPE and an ACS. The security mechanisms prevent the transactions between the CPE and the ACS from being tampered and ensure confidentiality of the transactions.

The CWMP supports the following authentication mechanisms:
  • CPE and ACS authentication

  • SSL authentication

    When the ACS URL is in the HTTPS format, the CPE and ACS must authenticate each other, and the SSL connection is set up only after the CPE and ACS are authenticated. It ensures the confidentiality of communication between the ACS and the CPE and data integrity.

Procedure

  • Configure CPE and ACS authentication.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      cwmp

      The CWMP view is displayed.

    3. Configure ACS authentication.

      1. Run:

        cwmp acs username username

        The user name used to connect the CPE to the ACS is configured.

      2. Run:

        cwmp acs password cipher

        The password used to connect the CPE to the ACS is configured.

    4. Configure CPE authentication.

      1. Run:

        cwmp cpe username username

        The user name used to connect the ACS to the CPE is configured.

      2. Run:

        cwmp cpe password cipher

        The password used to connect the ACS to the CPE is configured.

  • Configure SSL authentication.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      cwmp

      The CWMP view is displayed.

    3. Run:

      
      cwmp ssl-client { client-root-cert rootcert-path1 [ rootcert-path2 ] | ssl-policy policy-name }

      The CPE is configured to validate the certificate from the ACS.

      NOTE:

      The system time must be correctly set; otherwise, certificate validation may fail. To use a new certificate, uninstall the existing certificate first.

      Before configuring a CPE to authenticate the ACS using an SSL policy, run the ssl policy policy-name type client command to configure the SSL policy on the CPE.

3.5.4  (Optional) Configuring the CWMP Uploading Function

Context

After a connection is set up between the CPE and the ACS, you can configure the CPE to upload the currently loaded configuration file to the ACS. This function is used to back up configuration files.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    cwmp

    The CWMP view is displayed.

  3. Run:

    cwmp request upload current-configuration

    The CPE is configured to upload the currently loaded configuration file to the ACS.

3.5.5  Checking the Configuration

Prerequisites

All the CWMP configurations are complete.

Procedure

  • Run the display cwmp configuration command to check CWMP configurations on the router.
  • Run the display cwmp password command to check CWMP password on the router.
  • Run the display cwmp status command to check CWMP status on the router.
  • Run the display cwmp request upload status command to check the status of configuration file uploading from the router to the ACS.

3.6  Configuration Examples

This chapter provides CWMP configuration examples.

3.6.1  Example for Configuring CWMP

Networking Requirements

As shown in Figure 3-4, multiple hosts in Enterprise A access an enterprise gateway router. The router connects to the Internet.

The enterprise headquarters want to upgrade router software and hardware, download configuration files to the router automatically, and restart the router remotely during upgrade or troubleshooting. The CWMP function needs to be configured on the router to provide these functions.

Figure 3-4  The ACS manages the router by using CWMP

Configuration Roadmap

To meet the enterprise requirements, configure CWMP:

  1. To ensure that the CPE can initiate a connection to the ACS, configure the CWMP connection on the router.
  2. To ensure connection security, configure CWMP authentication on the router.

Procedure

  1. Configure the router IP address and route based on Figure 3-4 and ensure that the route is reachable.

    <Huawei> system-view
    [Huawei] sysname Router
    [Router] interface gigabitethernet 1/0/0
    [Router-GigabitEthernet1/0/0] ip address 10.1.1.1 24
    [Router-GigabitEthernet1/0/0] quit
    [Router] ospf 1
    [Router-ospf-1] area 0
    [Router-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
    [Router-ospf-1-area-0.0.0.0] quit
    [Router-ospf-1] quit

  2. Enable the CWMP function on the router.

    [Router] cwmp
    [Router-cwmp] cwmp enable

  3. Configure the CWMP connection of the router.

    # Configure the URL used by the router to connect to the ACS.

    [Router-cwmp] cwmp acs url http://10.2.1.1/acs

    # Configure the interface on the router to connect to the ACS.

    [Router-cwmp] cwmp cpe connect interface gigabitethernet 1/0/0

    # Enable the router to send Inform messages.

    [Router-cwmp] cwmp cpe inform interval enable

    # Set the interval at which the router sends Inform messages to 1000 seconds.

    [Router-cwmp] cwmp cpe inform interval 1000

    # Set the maximum number of connection attempts to 5.

    [Router-cwmp] cwmp cpe connect retry 5

    # Set the close-wait timer of the router to 100 seconds.

    [Router-cwmp] cwmp cpe wait timeout 100

  4. Configure the CWMP authentication of the router.

    # Set parameters for authenticating the router.

    [Router-cwmp] cwmp acs username newacsname
    [Router-cwmp] cwmp acs password cipher
    Enter Password(<6-255>):
    Confirm password:

    # Set parameters for authenticating the ACS.

    [Router-cwmp] cwmp cpe username newcpename
    [Router-cwmp] cwmp cpe password cipher
    Enter Password(<6-255>):
    Confirm password:
    [Router-cwmp] quit

  5. Verify the configuration.

    # You can see the CWMP function status, URL of the ACS, user name and password, Inform message sending status, interval for sending Inform messages, time when an Inform message is sent, close-wait timer, and maximum number of connection attempts.

    [Router] display cwmp configuration
      CWMP is enabled
      ACS URL:                              http://10.2.1.1/acs
      ACS username:                         newacsname
      ACS password:                         %@%@u<GgDA|}*!%lp>R@.[/M"e0_%@%@
      Inform enable status:                 enabled
      Inform interval:                      1000s
      Inform time:                          - 
      Wait timeout:                         100s
      Reconnection times:                   5
    

    # You can see the CWMP function status, URL of the ACS, user name and password, method to obtain the URL of the ACS, status of the connection between the CPE and the ACS, and time when the last connection is set up.

    [Router] display cwmp status
     CWMP is enabled
     ACS URL:                              http://10.2.1.1/acs
     ACS information is set by:            user
     ACS username:                         newacsname
     ACS password:                         %@%@u<GgDA|}*!%lp>R@.[/M"e0_%@%@
     Connection status:                    connected
     Time of last successful connection:   2012-09-28 21:10:22+00:00  
    

Configuration Files

Configuration file of the router

#
 sysname Router
#
interface GigabitEthernet1/0/0
 ip address 10.1.1.1 255.255.255.0
#
ospf 1
 area 0.0.0.0
  network 10.1.1.0 0.0.0.255
#
cwmp
 cwmp enable
 cwmp cpe inform interval enable
 cwmp acs url http://10.2.1.1/acs
 cwmp acs username newacsname
 cwmp acs password cipher %@%@u<GgDA|}*!%lp>R@.[/M"e0_%@%@
 cwmp cpe username newcpename
 cwmp cpe password cipher %@%@^<d}J,qcv&zbd}H2:,wL"eTh%@%@
 cwmp cpe inform interval 1000
 cwmp cpe connect retry 5
 cwmp cpe wait timeout 100
 cwmp cpe connect interface GigabitEthernet1/0/0
#
return

3.7  Common Configuration Error

This topic describes the common CWMP configuration error, including the fault symptoms and troubleshooting procedure.

3.7.1  Failure to Manage CPE Using CWMP

Symptoms

The fault symptoms are as follows:
  • The router cannot set up a connection with the ACS.
  • The ACS fails to issue configurations to the router.

Procedure

  1. Check that there is a reachable route between the router and ACS.

    Run the ping command on the router to ping the ACS.

    NOTE:
    If you have configured the ACS's URL as a domain name, use the display dns dynamic-host command to obtain the IP address, and enter the IP address in the ping command.
    <Huawei> display dns dynamic-host
    Host                                     TTL   Type   Address(es)
    huawei.com                               114   IP     2.1.1.3 
    • If the ping fails, check the route configuration.
    • If the router can ping the ACS, go to step 2.

  2. Verify the CWMP settings on the router.

    Run the display cwmp configuration command to check whether the CWMP function is enabled and the ACS's URL, user name, and password are correctly set.

    <Huawei> display cwmp configuration
      CWMP is enabled
      ACS URL:                         http://www.acs.com:80/acs
      ACS username:                    hwcpe
      ACS password:                    %$%$gw1.QU~4M1I@RDF>b/VP,@7.%$%$
      Inform enable status:                 disabled
      Inform interval:                      600s
      Inform time:                          -
      Wait timeout:                         30s
      Reconnection times:                   3
    

    If the CWMP settings are incorrect, modify them based on Table 3-4, and run the undo cwmp enable and cwmp enable commands to re-enable the CWMP function.

    Table 3-4  CWMP settings
    Item Method
    Enable the CWMP function. Run the cwmp enable command in the CWMP view.
    Configure the URL used by the router to connect to the ACS. Run the cwmp acs url url command in the CWMP view.
    Configure the user name used by the router to connect to the ACS. Run the cwmp acs username username command in the CWMP view.
    Configure the ACS's password used by the router to connect to the ACS.

    Run the cwmp acs password cipher command in the CWMP view.

3.8  FAQ

3.8.1  How Can an AR Router Correctly Connect to an ACS?

  1. Ensure that the AR router can ping the ACS successfully.
  2. Ensure that the AR router is configured with the same URL as the ACS.
  3. Run the undo cwmp enable command and then the cwmp enable command in the CWMP view of the AR router to trigger a session connection.
  4. If no connection is established, the AR router and ACS may fail to exchange packets. Capture packets on the ACS to locate the packet exchange failure. After the packet exchange failure is rectified, perform step 3 again to trigger a session connection.

3.9  References

This section lists references of CWMP.

Document

Description

Remarks

CPE/ACS Application

The application uses the CPE WAN Management Protocol on the CPE and ACS, respecitively. The application is locally defined and not specified as part of the CPE WAN Management Protocol

N/A

RPC Methods

The specific RPC methods that are defined by the CPE WAN Management Protocol

N/A

SOAP

A standard XML-based syntax used here to encode remote procedure calls. Specifically Simple Object Access Protocol (SOAP) 1.1.

Only one authentication password can be configured.

HTTP

RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1

N/A

SSL/TLS

The standard Internet transport layer security protocols. Specifically, either SSL 3.0 (Security Socket Layer), or TLS 1.0 (Transport Layer Security).

N/A

TCP/IP

Standard TCP/IP

N/A