Tr 069 manager

From Teltonika Networks Wiki Main Page > TRB Gateways > TRB140 > TRB140 Manual > TRB140 WebUI > TRB140 Services section > TRB140 TR-069The information in this page is updated in accordance with firmware version TRB1_R_00.07.13.1.SummaryTR-069 (Technical Report 069) is an application layer protocol designed for management of equipment connected to a remote network.This chapter of the user manual provides an overview of the UPnP page in TRB140 devices.TR-069 is additional software that can be installed from the System → Package Manager page.TR-069 Client Configuration Field Value Description Enable off | on; default: off Turns TR-069 client on or off. Periodic enable off | on; default: on Turns periodic data transmissions to server on or off. Accept server request off | on; default: off When enabled the device accepts connection requests from servers. Sending interval integer [60..9999999]; default: 100 Periodic data transmission frequency (in seconds). Username string; default: easycwmp Username used for authentication to a TR-069 server. Password string; default: easycwmp Password used for authentication to a TR-069 server. URL host | ip; default: IP address or hostname of a TR-069 server. Management via TR-069TR-069 can be used to set or get values from RUT devices. Below is a list of commands used for device management via TR-069. R - read only; RW - read/write; string(64) - 64 bit string; string(256) - 256 bit string; unsignedInt - integer storing only positive values.Device Information: DeviceInfo.HardwareVersion - device hardware version (e.g., 0201) R DeviceInfo.Manufacturer - device manufacturer (e.g., Teltonika) R DeviceInfo.ManufacturerOUI - organizationally unique identifier of the device manufacture (e.g., 001E42) R DeviceInfo.ProductClass - device model (e.g., TRB140) R DeviceInfo.ProvisioningCode - provisioning code R DeviceInfo.SerialNumber - device serial number (e.g., 1000111111) R DeviceInfo.SoftwareVersion - device software version (e.g., TRB1_R_00.0X.XX) R DeviceInfo.SpecVersion - device special version (e.g., 1.0) RDevice Mobile Information: MobileInfo.Modem.1-1.CellID - cell ID MobileInfo.Modem.1-1.ConnState - connection state (e.g., Connected) R MobileInfo.Modem.1-1.ConnType - connection type (e.g., LTE) R MobileInfo.Modem.1-1.EARFCN - absolute radio frequency channel number (e.g., 75) R MobileInfo.Modem.1-1.ECIO - signal, measured in dB R MobileInfo.Modem.1-1.ICCID - SIM ICCID R MobileInfo.Modem.1-1.IMEI - modem IMEI R MobileInfo.Modem.1-1.IMSI - international mobile subscriber identity R

TR-069 AgentThe digital subscriber line (DSL) Forum's TR-069, CPE WAN Management Protocol (CWMP), is used for communications between a customer premise equipment (CPE) and an auto-configuration server (ACS). The TR-069 Agent feature manages a collection of CPEs, with the primary capability for auto-configuration and dynamic service provisioning, software image management, status and performance monitoring and diagnostics. Finding Feature InformationLimitations for the TR-069 AgentPrerequisites for the TR-069 AgentInformation About the TR-069 AgentHow to Configure and Enable the TR-069 AgentConfiguration Examples for TR-069 AgentAdditional References for TR-069 AgentFeature Information for TR-069 AgentGlossaryFinding Feature Information Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/​go/​cfn. An account on Cisco.com is not required. Limitations for the TR-069 AgentThe following table provide the limitations of the parameters in TR-069.Table 1 TR-069 Parameters TR-069 Parameter Expected Value Supported on Cisco ISR G2 Supported on Cisco 4451 InternetGatewayDevice. WANDevice.2. WANConnectionDevice.1.WANIPConnection.1.Uptime Time No No Internet gatewy device. WAN device2. WAN common interface config enabled. For Internet registration entry for Internet gateway device. WAN device. WAN common Interface configuration does not include the parameter enabled for Internet. True or Flase No No InternetGatewayDevice.DeviceInfo.SoftwareVersionentPhysicalSoftwareRev for the Cisco ISR4451 Chassis is NULL, hence InternetGatewayDevice.DeviceInfo.SoftwareVersion is also NULL Version Yes No WAN access type is DSL (Internet gateway device. WAN device2. WAN common interface configuration. WAN access type) The WAN DSL interface configuration data is populates when the WAN access type is Ethernet (Internet Gateway device. WAN device. WAN common interface configuration interface config. WAN access type). The WAN Ethernet interface configuration date populates. Populate the details Yes Yes InternetGatewayDevice.Layer3Forwarding.Forwarding.1.MTUregistration entry for InternetGatewayDevice.Layer3Forwarding.Forwarding. does not include the parameter MTU MTU value No No Internet gateway device. Layer 3 forwarding. Forwarding 1. MTU registration entry for Internet gateway device. Layer 3 forwarding. Forwarding does not include the parameter MTU. MTU value No No Set parameter values- Internet gateway device. Time. NTP server 5 in Cisco 4451, config t, archive, path boot flash should be configured to set

The value in Cisco ISR G2; only one storage path and it is the flash memory. ntp server 100.12.12.1 YES (no archive) YES (configure archive) Prerequisites for the TR-069 Agent The CPE should have an IP address and a WAN connection should be established to access the ACS. Information About the TR-069 AgentTR-069 AgentHTTP Digest Authentication SupportHTTP Cookie Support Per RFC2965Device Gateway Association and Port Mapping SupportTR-069 Agent The TR-069 Agent allows an ACS to provision a CPE or collection of CPEs. The provisioning mechanism includes specific provisioning parameters and a general mechanism for adding vendor-specific provisioning capabilities as needed. The identification mechanisms included in the protocol allow CPE provisioning based either on the requirements of each specific CPE, or on collective criteria such as the CPE vendor, model, software version, or other criteria. The provisioning mechanism allows CPE provisioning at the time of initial connection to the broadband access network and the ability to reprovision at any subsequent time. This includes support for asynchronous ACS-initiated reprovisioning of a CPE. The TR-069 Agent also supports image upgrade, configuration application, file downloads, configuration and log file uploads, and CPE monitoring. Note The TR-069 Agent CPE devices must be set up and enabled for TR-069. An ACS used to communicate with the CPE must be TR-069 compliant in order to enable the TR-069 Agent. RPC Support The following remote procedure calls (RPCs) supported with the TR-069 Agent: Standard RPCs GetRPCMethods SetParameterValues GetParameterValues GetParameterNames SetParameterAttributes GetParameterAttributes AddObject DeleteObject Reboot Download Upload Vendor RPCs X_00000C_SetConfiguration X_00000C_ShowStatus CWMP Vendor Profile Schema The following details the CWMP vendor profile schema: For SetConfiguration, rollback {running-config | startup-config} block of clis separated by newline [\n] character IOS Configuration command 1 IOS Configuration command 2 parameterkey ErrorOption => string with length 64Target => string with length 64 On success, 0 On failure, ClientCWMP fault IOS Configuration command that failedparse_cmd() return value IOS Configuration command that failedparse_cmd() return value For ShowStatus, IOS Exec command 1 IOS Exec command 2 IOS Exec command 3 On success, IOS Exec command 1 output of command 1 IOS Exec command 2 output of command 2 IOS Exec command 3 output of command 3 On failure, ClientCWMP fault HTTP Digest Authentication Support The TR-069 Agent uses HTTP as the transport and needs support for digest authentication from the HTTP client infrastructure. Note This feature is not a TR-069 Agent-exclusive feature and can be used in