In the element logging I found references to QAction 900001 being executed while I can't find that QAction in the protocol.
At the time of the QAction being executed the device seems to go in timeout and it's possible the device doesn't recover.
The device in question is the Ericsson RX8200.
Is QAction 900001 a hidden QAction in software? What does it do?
Floris Cockaerts [SLC] [DevOps Advocate] Answered question 12th October 2021
To expand on Laurens' response, these are the QActions currently added by server-side to the protocol (as of 10.1.12) and their trigger parameters:
- 900000: trigger=65015, [Reset alarms for PID]
- 900001: trigger=65016, [Increment PID]
- 900004: trigger=65024, [Property value]
- 900007: trigger=65074, [Add Connection]
- 900008: trigger=65075, [Add Interface Property]
- 900009: trigger=65076, [Add Connection Property]
- 900011: trigger=65128, ReplicationDmaRowCountTrigger
- 900012: trigger=65129, ClearTableAfterStartupTrigger
- 900013: trigger=66155, [DVE delete/add]
- 900014: trigger=66157, [Interface delete/add]
- 900015: trigger=66165, [Generic DVE Link delete/add]
As you can see, most of these are related to the DCF tables in the general parameters, while some take care of certain functionality in the background.
Floris Cockaerts [SLC] [DevOps Advocate] Answered question 12th October 2021