Skip to content
Dan Morphis edited this page Oct 15, 2018 · 2 revisions

The devices tab consists of two parts, filters and the list view, and gives you an overview over all CPEs (that were connected to GenieACS once) Thos occurs regardless of their current online state. As more CPEs connect to the ACS, the longer and confusing that list gets. It is advised to apply one or more filter.


Filter:

Text? With these filters, as previously mentioned you can combine them with another, you can narrow down your selection to present you only those CPEs you want to see. There is a transition from home tab to devices tab with preset filter (lastInform). So if you choose all online CPEs on home, only those who match that creteria will be presented on the devices tabs. If you want to see all entries change to Devices directly via GUI.




**List view:**

If you selected the list view (no filter) a table is presented for all known entries. Those entries are presented with some data (which are known and stored in GenieACS database, if unknown you see blank):

  • Serial Number of the device
  • Product class of the device
  • Software version of the device
  • MAC address of the Interface (over which the connection to GenieACS was established)
  • IP address of current PPPoE Session (over which the connection to GenieACS was established)
  • WLAN SSID of the device
  • Last inform

List view of devices

On the lower end there is link Download with which you can download the whole (displayed, depending on filters) list as .csv file.

Not seen in the image, but when you move your mouse pointer right to the Last inform value a show link will be displayed. Via that link you can open all information for the chosen CPE which are known and stored in the database.


Device view:

The "view" page for a given CPE is divided into 3 segments:

  • Summary header
  • Task queue
  • Device parameters


Summary header:

The summary segment displays some general data of the CPE. Definition of what parameters are to be displayed can be found in /pathtogenieacs-gui/config/summary_parameters.yml. If you want to changed those, you have to change the "backend" (GenieACS) too. For that, see

The default summary looks like this:

Summary header in CPE view

Hint!: Above the summary header is the tag function. With this you can assign a tag value (be it unique or as group tag) for the purpose to allow grouping of devices for search and preset conditions (tag is a preset condition, see Presets tab). It's not TR-069 functionality, just a mechanism implemented in GenieACS.

Task queue:

The next segment is the task queue. If CPE isn't recognized online anymore, GenieACS stores a task and the status can be seen here. Apparently there is no running task at the moment

Task queue

Device parameters:

The last segment is device parameters, main object on devices view. Here you can find all parameters (according to the specifications (e.g. TR-069, TR-098 etc.) & proprietary ones) who were sent from CPE to ACS and stored in the database.

Above the parameters table you find a search bar. If you look for a certain parameter and you know it's name, simply enter it here and if it's in the list, it will be displayed solely.

It is not shown in screenshot, but when you hover over an entry, options like edit (to change the value) or refresh (to retrieve the latest value) are displayed. What option is displayed depends on the implemented service model within the TR069 client of the CPE. The same applies to proprietary Nodes.

Device parameters entry list

Below the parameters table you furher find 3 option

  • Reboot - reboots the CPE
  • Factory reset - resets the CPE to it's factory defaults
  • Push File - sends file to the CPE

The Push File link is mainly used for upgrading device's firmware. The reason this was not called simply "Upgrade" is because it's not strictly just for firmware upgrade. You could push configuration files, web content (for device's admin portal), or other kind of files depending on the device. But the main use is firmware upgrade.

Clone this wiki locally