Elements

The probe breaks event data down into tokens and parses them into elements. Elements are used to assign values to ObjectServer fields; the field values contain the event details in a form that the ObjectServer understands.

The following table describes the elements that theTSM for Nortel DMS generates. Not all the elements described are generated for each event; the elements that the probe generates depends upon the event type.

Table 1. Elements
Element name	Element description
`$AdditionalLineNN`	This element identifies the number, as indicated by NN, and content of the additional lines contained in a message of variable length. If the event is not being processed as a report, any lines following the first line of the event are passed as elements called `AdditionalLine`, followed by a number. For example: `AdditionalLine01`, `AdditionalLine02`, and so forth.
`$Alarm`	This element indicates the alarm type of the log report: critical alarm major alarm minor alarm
`$Class`	This element contains the event class that identifies the log subsystem.
`$Date`	This element contains the date of event in MMMDD format. For example, JAN01.
`$Date`	This element contains the e raw line of data received.
`$Date`	This element contains the raw line of data received.
`$EventID`	This element contains the identifier of the event in a report or a normal event.
`$EventType`	This element contains the type of event.
`$HeaderLine`	This element contains the initial line of the event.
`$HeaderText`	This element contains a text message associated with the event.
`$Host`	This element contains the name of the host from which the event was received.
`$InvalidEvent`	If the probe receives an incomplete or invalid alarm, this element contains full details of the alarm.
`$Minutes`	This element contains the number of minutes after the hour that the report was generated.
`$Node`	This element contains the name that identifies the DMS switch generating the event log.
`$NodeName`	This element contains the node name that identifies the DMS switch generating the event log.
`$Office event`	This element contains the node name that identifies the DMS switch generating the event log.
`$OfficeID`	Used to hold the two-character office code found after the `$Node` element in header lines of `ECORE_FORMAT = TRUE` format.
`$Port`	This element contains the name of the port from which the event was received.
`$ReportFlag`	This element indicates whether the event is a report or a normal.
`$ReportID`	This element indicates from which subsystem the event originated.
`$RestartLine`	If the TSM receives an SOS message while parsing an event, this element contains the SOS message.
`$SeqNo`	This element contains the sequence number of event.
`$Severity`	This element indicates the alarm type of the log report. Possible values are: critical alarm major alarm minor alarm
`$SubClass`	This element contains the sub class of the event.
`$TextType`	This element contains the type of event.
`$Threshold`	This element indicates whether a threshold was set for the log report.
`$Time`	This element contains the time of event in HH:MM:SS format.
`$Warning`	This element is used by DMS if it could not send all events to the TSM due to port bandwidth limitations.