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?
Hi,
QAction 900001 is indeed something that is automatically added.
It doesn't do much: it's simply keeping track of the number of alarms in the element and fills that in on an internal table. Just a simple counter increment when there's a new alarm.
Indeed, when the element goes in timeout it will trigger that QAction to increment the counter. I would expect that the element goes in timeout and because of that QAction 900001 is then executed, instead of the other way around that QAction 900001 would be causing the element to go in timeout (which I’m not expecting to be the case).
Is this the only internally added QAction or are there others that you know of?
There are others in the 9000xx range. You can see these QAction dlls being generated in Skyline DataMiner -> ProtocolScripts folder. Such as protocolName.protocolVersion.QAction.900011.dll and QAction.900012.dll . These dlls will only be present when the QAction gets called (like for 900001 when the element went into timeout), if the QAction never gets called then the matching dll also won’t be present.
These QAction 9000xx dlls are being used for the “General Parameters” that are by default present in every element. For example clicking on [Add Connection] button on the “DataMiner Connectivity Framework” sub page of the “General Parameters” will call QAction 900007 that will execute the logic to add a row to the [Connections] table on that same sub page.
Thanks for elaborating!
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.
For example when the element goes in timeout, it’ll execute the QAction?