Manual:TR069-client: Difference between revisions
|Line 336:||Line 336:|
''Note: Our suggestion is to only use ACS that is actively maintained, however, ones in the list appear to be abandoned''
''Note: Our suggestion is to only use ACS that is actively maintained, however, ones in the list appear to be abandoned ''
Revision as of 09:26, 16 February 2017
TR069-client implements CPE WAN Management Protocol (CWMP) for remote device management, which is standardized by the Broadband Forum (BBF). CWMP works over IP network using HTTP(S) to communicate with an Auto Configuration Server (ACS), which can monitor, configure attributes and update the firmware of a remote device.
Typically used by ISPs to manage CPEs, but also can be used for Network Infrastructure Device management.
TR069-client menu Parameters. When the package is installed (first available in RouterOS 6.38). The configuration is in /tr069-client
Client configuration settings.
|enabled||enable/disable CWMP protocol|
|acs-url||URL of ACS. Examples: "https://example.com:8080/path/", "http://192.168.1.100/"|
|username||HTTP authentication username (used by CPE to "login" into ACS)|
|password||HTTP authentication password (used by CPE to "login" into ACS)|
|periodic-inform-enabled||enable/disable CPE periodical session initiation. Timer is started after every successful session. When session is started by periodic interval then Inform RPC contains "2 PERIODIC" event. Maps to "Device.ManagementServer.PeriodicInformEnable" Parameter|
|periodic-inform-interval||timer interval of periodic inform. Maps to "Device.ManagementServer.PeriodicInformInterval"|
|client-certificate||certificate of client/CPE, which can be used by ACS for extra authentication|
Reald only parameters to monitor state of the client.
|status||informative status of CWMP.
|last-session-error||user-friendly error description indicating why the previous session didn't finish successfully|
|retry-count||consecutive unsuccessful session count. If > 0, then last-session-error should indicate error. Resets to 0 on a successful session, disabled protocol or reboot|
|reset-tr069-config||completely resets and forgets tr069-client configuration and state (without affecting other ROS configurations). Use when CWMP goes into unresponsive/hanged state and should be restored without re-installation of the RouterOS.|
CWMP client usually starts communication(Session) with ACS on different events - first boot, reboot, periodic interval, remote request, value change etc. In each session, CPE and ACS can call RPCs to be "executed" on the other side. CPE always starts with Inform RPC, which contains connection reason, device info and some Parameter values depending on configuration. When CPE has nothing more to say, then ACS executes its RPCs (which most of the time are Parameter management RPCs).
Parameters and Data Models
Parameters are simple name+value pairs and each vendor can decide which Parameters to support in its devices. A combination of all supported Parameters is called Data Model (DM). BBF defines three root Data Models(TR-098, TR-181:1, TR-181:2) on which vendors should base their supported Parameters. RouterOS Data Model is based on "TR-181 Issue 2 Amendment 11", which is the newest DM and recommended by BBF.
Device., writable: 0 Device.RootDataModelVersion, writable: 0 Device.InterfaceStackNumberOfEntries, writable: 0 Device.DeviceInfo., writable: 0 Device.DeviceInfo.Manufacturer, writable: 0 Device.DeviceInfo.ManufacturerOUI, writable: 0 Device.DeviceInfo.ModelName, writable: 0 Device.DeviceInfo.Description, writable: 0 Device.DeviceInfo.ProductClass, writable: 0 Device.DeviceInfo.SerialNumber, writable: 0 Device.DeviceInfo.HardwareVersion, writable: 0 Device.DeviceInfo.SoftwareVersion, writable: 0 Device.DeviceInfo.ProvisioningCode, writable: 1 Device.DeviceInfo.UpTime, writable: 0 Device.DeviceInfo.X_MIKROTIK_SystemIdentity, writable: 1 Device.DeviceInfo.X_MIKROTIK_ArchName, writable: 0 Device.DeviceInfo.VendorConfigFileNumberOfEntries, writable: 0 Device.DeviceInfo.MemoryStatus., writable: 0 Device.DeviceInfo.MemoryStatus.Total, writable: 0 Device.DeviceInfo.MemoryStatus.Free, writable: 0 Device.DeviceInfo.ProcessStatus., writable: 0 Device.DeviceInfo.ProcessStatus.CPUUsage, writable: 0 Device.DeviceInfo.VendorConfigFile., writable: 0 Device.DeviceInfo.VendorConfigFile.1., writable: 0 Device.DeviceInfo.VendorConfigFile.1.Name, writable: 0 Device.DeviceInfo.VendorConfigFile.1.Description, writable: 0 Device.DeviceInfo.VendorConfigFile.1.UseForBackupRestore, writable: 0 Device.ManagementServer., writable: 0 Device.ManagementServer.URL, writable: 1 Device.ManagementServer.Username, writable: 1 Device.ManagementServer.Password, writable: 1 Device.ManagementServer.PeriodicInformEnable, writable: 1 Device.ManagementServer.PeriodicInformInterval, writable: 1 Device.ManagementServer.ParameterKey, writable: 0 Device.ManagementServer.ConnectionRequestURL, writable: 0 Device.ManagementServer.ConnectionRequestUsername, writable: 1 Device.ManagementServer.ConnectionRequestPassword, writable: 1 Device.ManagementServer.AliasBasedAddressing, writable: 0 Device.InterfaceStack., writable: 0 Device.DNS., writable: 0 Device.DNS.Client., writable: 0 Device.DNS.Client.ServerNumberOfEntries, writable: 0 Device.DNS.Client.Server., writable: 1 Device.DNS.Client.Server.1., writable: 1 Device.DNS.Client.Server.1.Enable, writable: 1 Device.DNS.Client.Server.1.Status, writable: 0 Device.DNS.Client.Server.1.DNSServer, writable: 1 Device.DNS.Client.Server.1.Type, writable: 0 Device.Cellular., writable: 0 Device.Cellular.InterfaceNumberOfEntries, writable: 0 Device.Cellular.AccessPointNumberOfEntries, writable: 0 Device.Cellular.Interface., writable: 0 Device.Cellular.AccessPoint., writable: 0 Device.WiFi., writable: 0 Device.WiFi.RadioNumberOfEntries, writable: 0 Device.WiFi.SSIDNumberOfEntries, writable: 0 Device.WiFi.AccessPointNumberOfEntries, writable: 0 Device.WiFi.Radio., writable: 0 Device.WiFi.Radio.1., writable: 0 Device.WiFi.Radio.1.Enable, writable: 1 Device.WiFi.Radio.1.Status, writable: 0 Device.WiFi.Radio.1.LowerLayers, writable: 0 Device.WiFi.Radio.1.SupportedFrequencyBands, writable: 0 Device.WiFi.Radio.1.OperatingFrequencyBand, writable: 1 Device.WiFi.Radio.1.SupportedStandards, writable: 0 Device.WiFi.Radio.1.OperatingStandards, writable: 1 Device.WiFi.Radio.1.PossibleChannels, writable: 0 Device.WiFi.Radio.1.Channel, writable: 1 Device.WiFi.Radio.1.AutoChannelSupported, writable: 0 Device.WiFi.Radio.1.AutoChannelEnable, writable: 1 Device.WiFi.SSID., writable: 1 Device.WiFi.SSID.1., writable: 1 Device.WiFi.SSID.1.Enable, writable: 1 Device.WiFi.SSID.1.Status, writable: 0 Device.WiFi.SSID.1.LowerLayers, writable: 1 Device.WiFi.SSID.1.BSSID, writable: 0 Device.WiFi.SSID.1.MACAddress, writable: 0 Device.WiFi.SSID.1.SSID, writable: 1 Device.WiFi.SSID.1.Stats., writable: 0 Device.WiFi.SSID.1.Stats.BytesSent, writable: 0 Device.WiFi.SSID.1.Stats.BytesReceived, writable: 0 Device.WiFi.SSID.1.Stats.PacketsSent, writable: 0 Device.WiFi.SSID.1.Stats.PacketsReceived, writable: 0 Device.WiFi.SSID.1.Stats.ErrorsSent, writable: 0 Device.WiFi.SSID.1.Stats.ErrorsReceived, writable: 0 Device.WiFi.SSID.1.Stats.DiscardPacketsSent, writable: 0 Device.WiFi.SSID.1.Stats.DiscardPacketsReceived, writable: 0 Device.WiFi.AccessPoint., writable: 1 Device.WiFi.AccessPoint.1., writable: 1 Device.WiFi.AccessPoint.1.Enable, writable: 1 Device.WiFi.AccessPoint.1.Status, writable: 0 Device.WiFi.AccessPoint.1.SSIDReference, writable: 1 Device.WiFi.AccessPoint.1.SSIDAdvertisementEnabled, writable: 1 Device.WiFi.AccessPoint.1.AssociatedDeviceNumberOfEntries, writable: 0 Device.WiFi.AccessPoint.1.Security., writable: 0 Device.WiFi.AccessPoint.1.Security.ModesSupported, writable: 0 Device.WiFi.AccessPoint.1.Security.ModeEnabled, writable: 1 Device.WiFi.AccessPoint.1.Security.KeyPassphrase, writable: 1 Device.WiFi.AccessPoint.1.AssociatedDevice., writable: 0 Device.Ethernet., writable: 0 Device.Ethernet.InterfaceNumberOfEntries, writable: 0 Device.Ethernet.LinkNumberOfEntries, writable: 0 Device.Ethernet.Interface., writable: 0 Device.Ethernet.Interface.1., writable: 0 Device.Ethernet.Interface.1.Enable, writable: 1 Device.Ethernet.Interface.1.Status, writable: 0 Device.Ethernet.Interface.1.LowerLayers, writable: 0 Device.Ethernet.Interface.1.Stats., writable: 0 Device.Ethernet.Interface.1.Stats.BytesSent, writable: 0 Device.Ethernet.Interface.1.Stats.BytesReceived, writable: 0 Device.Ethernet.Interface.1.Stats.PacketsSent, writable: 0 Device.Ethernet.Interface.1.Stats.PacketsReceived, writable: 0 Device.Ethernet.Interface.1.Stats.ErrorsSent, writable: 0 Device.Ethernet.Interface.1.Stats.ErrorsReceived, writable: 0 Device.Ethernet.Interface.1.Stats.DiscardPacketsSent, writable: 0 Device.Ethernet.Interface.1.Stats.DiscardPacketsReceived, writable: 0 Device.Ethernet.Link., writable: 1 Device.Ethernet.Link.1., writable: 1 Device.Ethernet.Link.1.Enable, writable: 1 Device.Ethernet.Link.1.Status, writable: 0 Device.Ethernet.Link.1.LowerLayers, writable: 1 Device.IP., writable: 0 Device.IP.InterfaceNumberOfEntries, writable: 0 Device.IP.Interface., writable: 1 Device.IP.Interface.1., writable: 1 Device.IP.Interface.1.Enable, writable: 1 Device.IP.Interface.1.Status, writable: 0 Device.IP.Interface.1.LowerLayers, writable: 1 Device.IP.Interface.1.IPv4AddressNumberOfEntries, writable: 0 Device.IP.Interface.1.IPv4Address., writable: 1 Device.IP.Interface.1.IPv4Address.1., writable: 1 Device.IP.Interface.1.IPv4Address.1.Enable, writable: 1 Device.IP.Interface.1.IPv4Address.1.Status, writable: 0 Device.IP.Interface.1.IPv4Address.1.IPAddress, writable: 1 Device.IP.Interface.1.IPv4Address.1.SubnetMask, writable: 1 Device.IP.Interface.1.IPv4Address.1.AddressingType, writable: 0 Device.IP.Diagnostics., writable: 0 Device.IP.Diagnostics.IPPing., writable: 0 Device.IP.Diagnostics.IPPing.DiagnosticsState, writable: 1 Device.IP.Diagnostics.IPPing.Interface, writable: 1 Device.IP.Diagnostics.IPPing.Host, writable: 1 Device.IP.Diagnostics.IPPing.NumberOfRepetitions, writable: 1 Device.IP.Diagnostics.IPPing.Timeout, writable: 1 Device.IP.Diagnostics.IPPing.DataBlockSize, writable: 1 Device.IP.Diagnostics.IPPing.DSCP, writable: 1 Device.IP.Diagnostics.IPPing.SuccessCount, writable: 0 Device.IP.Diagnostics.IPPing.FailureCount, writable: 0 Device.IP.Diagnostics.IPPing.AverageResponseTime, writable: 0 Device.IP.Diagnostics.IPPing.MinimumResponseTime, writable: 0 Device.IP.Diagnostics.IPPing.MaximumResponseTime, writable: 0 Device.IP.Diagnostics.IPPing.AverageResponseTimeDetailed, writable: 0 Device.IP.Diagnostics.IPPing.MinimumResponseTimeDetailed, writable: 0 Device.IP.Diagnostics.IPPing.MaximumResponseTimeDetailed, writable: 0 Device.IP.Diagnostics.TraceRoute., writable: 0 Device.IP.Diagnostics.TraceRoute.DiagnosticsState, writable: 1 Device.IP.Diagnostics.TraceRoute.Interface, writable: 1 Device.IP.Diagnostics.TraceRoute.Host, writable: 1 Device.IP.Diagnostics.TraceRoute.NumberOfTries, writable: 1 Device.IP.Diagnostics.TraceRoute.Timeout, writable: 1 Device.IP.Diagnostics.TraceRoute.DataBlockSize, writable: 1 Device.IP.Diagnostics.TraceRoute.DSCP, writable: 1 Device.IP.Diagnostics.TraceRoute.MaxHopCount, writable: 1 Device.IP.Diagnostics.TraceRoute.ResponseTime, writable: 0 Device.IP.Diagnostics.TraceRoute.RouteHopsNumberOfEntries, writable: 0 Device.IP.Diagnostics.TraceRoute.RouteHops., writable: 0 Device.PPP., writable: 0 Device.PPP.InterfaceNumberOfEntries, writable: 0 Device.PPP.Interface., writable: 1 Device.Routing., writable: 0 Device.Routing.RouterNumberOfEntries, writable: 0 Device.Routing.Router., writable: 0 Device.Routing.Router.1., writable: 0 Device.Routing.Router.1.Enable, writable: 0 Device.Routing.Router.1.Status, writable: 0 Device.Routing.Router.1.IPv4ForwardingNumberOfEntries, writable: 0 Device.Routing.Router.1.IPv4Forwarding., writable: 1 Device.Routing.Router.1.IPv4Forwarding.1., writable: 1 Device.Routing.Router.1.IPv4Forwarding.1.Enable, writable: 1 Device.Routing.Router.1.IPv4Forwarding.1.Status, writable: 0 Device.Routing.Router.1.IPv4Forwarding.1.StaticRoute, writable: 0 Device.Routing.Router.1.IPv4Forwarding.1.DestIPAddress, writable: 1 Device.Routing.Router.1.IPv4Forwarding.1.DestSubnetMask, writable: 1 Device.Routing.Router.1.IPv4Forwarding.1.GatewayIPAddress, writable: 1 Device.Routing.Router.1.IPv4Forwarding.1.Interface, writable: 1 Device.Routing.Router.1.IPv4Forwarding.1.Origin, writable: 0 Device.DHCPv4., writable: 0 Device.DHCPv4.ClientNumberOfEntries, writable: 0 Device.DHCPv4.Client., writable: 1 Device.DHCPv4.Server., writable: 0 Device.DHCPv4.Server.PoolNumberOfEntries, writable: 0 Device.DHCPv4.Server.Pool., writable: 1 Device.X_MIKROTIK_Interface., writable: 0 Device.X_MIKROTIK_Interface.GenericNumberOfEntries, writable: 0 Device.X_MIKROTIK_Interface.Generic., writable: 0
RouterOS Update via TR069-client
CWMP standard defines that CPE's firmware can be updated using Download RPC with FileType="1 Firmware Upgrade Image" and single URL of a downloadable file (HTTP and HTTPS are supported). Standard also states that downloaded file can be any type and vendor specific process can be applied to finish firmware update. Because MikroTik's update is package based (and also for extra flexibility), an XML file is used to describe firmware upgrade/downgrade. For now, XML configuration supports providing multiple URLs of files, which will be downloaded and applied similarly as regular RouterOS update through firmware/package file upload.
An example of RouterOS bundle package and tr069-client package update (don't forget to also update tr069-client package). An XML file should be put on some HTTP server, which is accessible from CPE for download. Also, downloadable RouterOS package files should be accessible the same way (can be on any HTTP server). Using ACS execute Download RPC with URL pointing to XML file (e.g. "https://example.com/path/upgrade.xml") with contents:
<upgrade version="1" type="links"> <config/> <links> <link> <url>https://example.com/routeros-mipsbe-X.Y.Z.npk</url> </link> <link> <url>https://example.com/tr069-client-X.Y.Z-mipsbe.npk</url> </link> </links> </upgrade>
CPE will download XML, parse/validate its contents, download files from provided URLs and try to upgrade. The result will be reported with TransferComplete RPC.
Other configuration options
Different ways how to apply configuration on the device running RouterOS with tr069 package.
This is CWMP standard RPC, which performs RouterOS configuration factory-reset. The reset process is performed in the same way as executing command:
/system reset-configuration skip-backup=yes
Note that the default factory configuration can be different for each device (see ) and executing this command removes all configurations and executes internally stored default-configuration script.
[Best Practices Guide for preparing CPE with custom factory settings for TR069 http://wiki.mikrotik.com/wiki/Tr069-best-practices]
The same Download RPC can be used to perform complete configuration overwrite (not yet implemented via other means) OR configuration alteration, a great care must be taken to execute the intended process by selecting the correct script file extension (.overwrite or .alter).
RouterOS has a lot of configuration attributes and not everything can be ported to CWMP Parameters, that's why RouterOS provides a possibility to execute its powerful scripting language to configure any attribute. A configuration alteration (which is really a regular script execution) can be performed using Download RPC FileType="3 Vendor Configuration File" with downloadable file extension ".alter". This powerful feature can be used to configure any ROS attributes which are not available through CWMP Parameters.
Overwrite all configurations
Full ROS configuration overwrites can be performed using Download RPC FileType="3 Vendor Configuration File" with the downloadable file extension .overwrite.
- HTTP should only be used when testing initial setup in the secured/private network because Man-in-the-middle attacker could read/change configuration parameters. In the production environment, HTTPS is a MUST.
- CWMP's incoming connection validation by design is safe because CPE will not communicate with any other device except previously configured ACS. Connection Request only signals CPE to start a new connection + new session with previously configured ACS.
Ordering is alphabetical. MikroTik does not imply any one vendor superiority of another. If some ACS is missing you can notify us of the existence of it and it might be added to the list.
We have tested and verified to be working the following commercial ACS solutions:
Note: Our suggestion is to only use ACS that is actively maintained, however, ones in the list appear to be abandoned or rarely updated