Dear - yes - this IS RIGHT - the alarm should be cleared in case the model/device is deleted off the Spetrum modeling - or the device "is back again" .. BUT - we saw that symptom truly some times, when there is a "communication" weakness between SpectroSERVER and OC-server. The alarm is still listed - and once clicking to the alarm a popup message box comes up, that this alarm is already cleared. It appears the context between the alarm-table entry at OC-server level and the SpectroSERVERs alarm-table is inaccurate. This could be true to a temporary communication issue which did affect the OC-server alarm-table update. A OC-server restart will clean up that this situation as this will force the OC-server to reload the alarm-table from the SpectroSERVERs. There is currently no admin-option to "re-sycn" the OC-server alarmtable content to all SpectroSERVERs and versa.
But I saw an Idea raised for this - like the OC-server should:
- provide an admin option (i.e. via OC-weblogon / Administration / Debug / Alarmtable) - to click on alarm table re-sync button
- the OC-server periodically - i.e. once per day - will re-sync the alarm table from scratch/at all - and not doing this by alarm updates only - so having every 24h at least one fresh sync
hth - cheers, Joerg