EasyManua.ls Logo

Worldcast Systems RELIO - Principle of Re-Transmissions; Acknowledgements Functioning; Events Leading to Sending of SNMP Notification

Default Icon
61 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Relio 4.2.x User Manual 07/2015
Page 41
Head Office : Parc dactivites Kennedy - 20, avenue Neil Armstrong 33700 Bordeaux-Merignac (France)
Tel +33 (0)5 57 928 928 Fax +33 (0)5 57 928 929 contact@worldcastsystems.com www.worldcastsystems.com
3.25.1. Principle of re-transmissions / acknowledgements functioning
As long as its acknowledgement has not been received, the notification will be re-transmitted at a rate of one
sending every <d> seconds, a maximum of <n> times; where <d> and <n> are the fields respectively <Ack Timeout>
(1) and <Max Retries> (2).
If acknowledgement does not arrive following <n> attempts, the notification is “frozen”, that-is-to-say, it is put on
standby until a new notification of the same type occurs. It can also be manually “unfrozen” using the “Replay
Traps” button (3).
It is important to note that non transmitted notifications are not lost. They are kept to be re-transmitted when
conditions permit it once again. When a new notification occurs the “frozen” notification is re-activated, and a
cycle of sending attempts starts up again.
3.25.2. Events leading to sending of SNMP notification
o EquipmentOn (identifier: 161): it is equivalent to ColdStart except that it can be acknowledged and
re-transmitted if necessary. Transmitted just after ColdStart.
o HeartBeat (identifier: 168): notification sent at regular intervals to give equipment sign of life.
Configurable on page “SNMP agent”.
o ConfigurationChanged (identifier: 169): transmitted when system configuration is modified.
o EquipmentFault (identifier: 1610): transmitted on application critical error or system breakdown.
o Phone Alert Enable (identifier: 2000): transmitted when the phone alert function is enabled.
Specific applicative alarms (ScriptEasy)
o ScriptEasy Info alarm (identifier: 1610000): ScriptEasy INFO type alert (event having no distinct
beginning or end)
o ScriptEasy On/Off alarm (identifier: 1610001): ScriptEasy ON/OFF type alarm (event marking
beginning or end of a state)
o Manager alarm (identifier: 1610002): ScriptEasy alarm compatible with the Broadcast Manager.
Remember to click the ‘Update’ button in each section to lock in any changes.