Hoping someone can give a little help. Got Genieacs installed and running and talking to my device. The issues I have is under listing of devices nothing is showing up in the values. I followed the above suggestion of editing the two config files. This then populated the Software Version field but nothing else. Are there any other changes I need to make to the config file to see the rest of the fields.

Thanks

So a little bit of an updated i forced refreshed and now I have the serail number field which is actual the mac address and the prodcut class fields. Still nothing under the real mac address field , IP and WLAN SSID fields.

Thanks again

Well I figured it out in case anyone else is in the boat i am in all the right device parameters can be found when you show your device you then just edit and add or delete from the two files index_parameters.yml and summary_parameters.yml

Hi Mikrotik.
How to interpretate this error ? Why it cannot do config overwrite ?

14:03:43 tr069,warning couldn't apply config overwrite
14:03:43 tr069,debug starting session, events: [7 TRANSFER COMPLETE, M Download (1), ]
14:03:43 tr069,debug send: Inform
14:03:43 tr069,debug rcvd: InformResponse
14:03:43 tr069,debug send: TransferComplete ["resolving error"]
14:03:43 tr069,debug rcvd: TransferCompleteResponse
14:03:43 tr069,debug session finished with error: ""
14:03:43 tr069,info performing config overwrite
14:03:43 tr069,warning couldn't apply config overwrite
14:03:43 tr069,debug scheduled next Session retry after 10 seconds

Already found issue. It will be good to have better verbosity for xml tr069-packets

I am getting the error also
warning couldn't apply config overwrite
Did you get a fix or an example of the vendor file?

regarding genieacs

for editing the

genieacs-gui/config/index_parameters.yml
genieacs-gui/config/summary_parameters.yml

i found this page very helpfull :
https://wiki.mikrotik.com/wiki/Manual:T ... eters-6.39

example what worked for me :

MK Serial : Device.DeviceInfo.SerialNumber
MK Device type : Device.DeviceInfo.ModelName
MK Software version: Device.DeviceInfo.SoftwareVersion
MK Identity : Device.DeviceInfo.X_MIKROTIK_SystemIdentity

Thanks for the guide. I'm going to try it with the most recent LTS version Ubuntu.

Thanks for the guide. I'm going to try it with the most recent LTS version Ubuntu.

Just checking in if came right with this? I tried the genieacs and freeacs on lts 18.04.2 and cant for life of me get it right and got to certain point then either ruby just having issues with genie and cant remember what freeacs complained about.

Think an update to this guide is necessary.

Thanks for the guide. I'm going to try it with the most recent LTS version Ubuntu.

Just checking in if came right with this? I tried the genieacs and freeacs on lts 18.04.2 and cant for life of me get it right and got to certain point then either ruby just having issues with genie and cant remember what freeacs complained about.

Think an update to this guide is necessary.

I've tested all kinds of provision with freeacs and posted some step-by-step howto with screens. In Russian. There are some few tricky things about software upgrade but in general all works like a charm with freeacs.

Thanks for the guide. I'm going to try it with the most recent LTS version Ubuntu.

Just checking in if came right with this? I tried the genieacs and freeacs on lts 18.04.2 and cant for life of me get it right and got to certain point then either ruby just having issues with genie and cant remember what freeacs complained about.

Think an update to this guide is necessary.

A working Step by Step guide for installing Genieacs with Gui on a ubuntu server is available on youtube https://youtu.be/9nPLRkH7UFI !

Thanks for your instruction.It helps me a lot.

For Step By Step Guide On Installing GenieACS For Mikrotik EcoSystem Please Have A Look At My Video Tutorials :

https://youtu.be/-9RW6V2bZqw

I found one free ACS Test PlatForm,
http://39.106.195.193:9090/acscloud/

Thank you! I was stumped on this a year ago and gave up!

Thanks for the guide, I am going to sticky this

dear all,

a working of TR069 with GenieACS v1.2.3 (Step-by-Step) with recent Ubuntu LTS version can be found on viewtopic.php?t=172399

the instalation using the recent version of :
● Ubuntu 20.04 LTS
● nodejs v14.15.4
● MongoDB v4.4.0
● GenieACS v1.2.3 => v1.2.5 now

still waiting someone from MikroTik to stick the mention tutorial

Paul Darius

for genieacs, use "3 Vendor Configuration File" and push to the router

P

Someone can have some information about tr069 working behind NAT such as XMPP or STUN server or Mikrotik is involved to evelop the USP support?

Anybody using Zhone ZNID devices here. We are struggling with Mikrotik handing out Option 43 to these devices. I am a bit confused about what I should see in a DHCP debug log. I am assuming I would see the Option 43 data sent to the CPE also on the mechanics of it. Does the CPE ask for Option 43 and if the Mikrotik is configured properly it would send it?

First you need to enable auto-detection of device models.

#/opt/freeacs-tr069/config/application-config.conf
# Discovery Mode can be set to true if you want to automatically add a new
# unittype and unit. This mode is violating the security of the system,
# because it allows unknown units to connect and then changes will be performed
# in the database. So use this option with caution, preferably when you want to
# add a new unittype to the system. Default is false.
#discovery.mode = false
discovery.mode = true
Then this option can be disabled, a second server can be started to train new models, and then transferred to prod via export / import, but for a start it is very useful.

On your trial Mikrotik, you need to import the certificate that we made for Nginx – acs_mydomain_ru.chained.crt v System / Certificates / Import…
Then install the tr069-client package and specify the ACS URL: .https: //acs.mydomain.ru: 8099 / tr069 / prov Username: . And you’re done.
By clicking Apply, the device will connect to the server via https, the Periodic inform interval will change in the window, and a new Unit type and, accordingly, Unit will appear on the server

This concludes the first part. We have a working autoconfiguration server serving devices over a secure connection on a separate port that is easy to monitor. The second part will contain pictures, scripts and combat experience with devices.