Meinberg LANTIME, Operating Instructions Manual

Page: 106 / 153

SNMP Trap Reference
All traps can be found under the mbgLtTraps section in the Meinberg MIB. A
special trap exists for every notification event the timeserver knows. Please note that
the traps are only sent if you configured the notification type “SNMP trap” for the
event, otherwise no trap is generated. All traps have a string parameter included,
which contains the plain text event message for the appropriate event (you are able to
change the default text messages, see web interface and/or CLI setup section to find
out how to do this).
Here is a list of all traps the timeserver knows:
mbgLtTrapNTPNotSync (mbgLtTraps.1): Whenever the NTP daemon (ntpd)
looses sync, it will generate this trap and send it to the configured SNMP trap
receivers.
mbgLtTrapNTPStopped (mbgLtTraps.2): This trap is sent when the NTP daemon
stopped, manually or because of an error condition.
mbgLtTrapServerBoot (mbgLtTraps.3): After finishing the boot process, this trap
is generated.
mbgLtTrapReceiverNotResponding (mbgLtTraps.4): Trap to be sent when the in-
ternal receiver of the timeserver is not responding.
mbgLtTrapReceiverNotSync (mbgLtTraps.5): If the internal receiver looses sync,
the SNMP trap receivers will receive this trap.
mbgLtTrapAntennaFaulty (mbgLtTraps.6): This trap will be sent whenever the
timeserver recognises a broken connection to the antenna of the receiver.
mbgLtTrapAntennaReconnect (mbgLtTraps.7): After the connection to the antenna
has been re-established, this trap is sent.
mbgLtTrapConfigChanged (mbgLtTraps 8): After reloading its configuration, the
timeserver generates this trap.
mbgLtTrapLeapSecondAnnounced (mbgLtTraps 9): If a leap second has been an-
nounced by the internal GPS receiver, this trap will be sent.
mbgLtTrapTestNotification (mbgLtTraps 99): This trap is sent whenever you are
requesting a test notification; it is only used for testing the connection between
the timeserver and your SNMP trap receivers.
106