If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:docsis syncstate
BoxMatrix >> System >> docsis_syncstate | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
Devices | Filesystems | Partitions | Sockets | Netlink | Pipes | Interfaces | Bridges | Ports | Events | Sources | Sinks | AVMIPC | Processes | Watchdogs | Memory | Slab | Vmalloc | ProcFS | SysFS | Research |
AVMIPC-State
AVMIPC-State: | docsis_syncstate - type State | Wiki | Freetz | IPPF | whmf | AVM | Web |
Location: | System >> AVMIPC-Datastore - Origin: AVM | ||||||
Listeners: | me_docsisinfod.ctl, me_dsld.ctl | ||||||
Properties: | Firmware: 7.29 | ||||||
Function: | State of the DOCSIS sync in JSON format. |
Goto: JSON-Data - Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
docsisinfo_syncstate provides the realtime state of the DOCSIS sync in JSON format.
This state is sent by pumaglued on the ARM CPU of Puma6 and Puma7 models.
Listeners are docsisinfod on the ARM CPU and dsld on the ATOM CPU.
The textual part of the sync state comes from libavm_docsis_stats.so which is only used by docsis_startstop.
Possible states are:
NOT SYNCHRONIZED (OTHER) NOT SYNCHRONIZED (NOT READY) NOT SYNCHRONIZED RANGING IN PROGRESS (DS TOPOLOGY RESOLUTION) RANGING IN PROGRESS RANGING COMPLETE REGISTRATION: US PARAMETERS ACQUIRED REGISTRATION: EAE IN PROGRESS REGISTRATION: DHCPV4 IN PROGRESS REGISTRATION: DHCPV6 IN PROGRESS REGISTRATION: DHCPV4 COMPLETE REGISTRATION: DHCPV6 COMPLETE REGISTRATION: TOD ESTABLISHED REGISTRATION: CONFIG FILE DOWNLOAD COMPLETE REGISTRATION: IN PROGRESS NOT OPERATIONAL: REGISTRATION COMPLETE NOT OPERATIONAL: BPI INIT OPERATIONAL OPERATIONAL: FORWARDING DISABLED OPERATIONAL: RF MUTE ALL OPERATIONAL: SECURITY ESTABLISHED NOT RUNNING OPERATIONAL: CM STAT %d
JSON-Data
Sample output of a 6490 fw 7.29 calling rpc aicmd avmipcd datastore query docsis_syncstate full
.
If the sample contains a size
info then it's a snippet of rpc aicmd avmipcd datastore show full
from Supportdata2.
docsis_syncstate : size 25, set by local , local:docsisinfod DATA: <<!EOF! 0 0 0 # NOT SYNCHRONIZED^@!EOF!
This box has no sync since it is in IP-Client mode.
The Model-Matrix below shows that this state is not propagated to the ATOM in this mode, that's why rpc
had to be used.
Please help with Supportdata2 of a 64xx/65xx/66xx with DOCSIS sync to improve this article and many others!
Dependencies
Daily updated index of all dependencies of this state. Last update: 2024-11-15 05:19 GMT.
A **
in the Mod
column marks info from Supportdata2 probes, which will always stay incomplete.
A -
in the Mod
column marks manual research, the Firmware
then shows where the Object
occurs, not the Relation
.
Relation | Typ | Object | Mod | Firmware | Info | Origin |
---|---|---|---|---|---|---|
Listener | sock | me_docsisinfod.ctl | 2** | 7.29 | avmipc endpoint of docsisinfod | AVM |
Listener | sock | me_dsld.ctl | 1** | 7.29 | avmipc_command endpoint of dsld | AVM |
Sender | cmd | pumaglued (avmcmd) | - | 6.83 - 8.00 | Inter-CPU connector for the ARM side of Puma6 / Puma7 models. | AVM |
3 dependencies for this state |
Model-Matrix
Daily updated index of the presence, path and size of this state for each model. Last update: 2024-11-15 05:19 GMT.
Showing all models using this state. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom/rtl)
label in the Model
column shows which CPU is meant for Multi-Linux models.
Note that this list comes from Supportdata2 probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata2 file or just a disabled feature.
Model | Firmware | Listeners | Size |
---|---|---|---|
FRITZ!Box 6430 Cable (arm) | 7.29 | me_docsisinfod.ctl | 25 |
FRITZ!Box 6430 Cable (atom) | 7.29 | me_dsld.ctl | 25 |
FRITZ!Box 6490 Cable (arm) | 7.29 | me_docsisinfod.ctl | 25 |
FRITZ!Box 6490 Cable (atom) | 7.29 | - | 0 |
FRITZ!Box 6660 Cable (atom) | 7.29 | - | 37 |
5 models use this state |
Help Supportdata2
The data in this article is incomplete since it was manually collected using the Supportdata2 project.
Unlike the Supportdata-Probes which have been collected for years Supportdata2 is brand new and only has a few probes.
If you have access to a shell then please help to extend the Supportdata2 collection to improve this data.
It's easy and it's done in minutes. Please send created data as an Email attachment to the address listed here. Thanks!