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 fault elements that the probe generates.

Table 1. Fault elements
Element Name	Element Description
`$ackdatetm`	This element contains the date when an operator acknowledged the fault.
`$ackopid`	This element contains the identifier of the operator who acknowledged the fault.
`$acksta`	This element indicates the acknowledgement state. This attribute can take the following values: `0`: The event has not been acknowledged. `1`: The event has been acknowledged.
`$alarmtype`	This element contains alarm type information.
`$blknr`	This element contains the block number.
`$chgctrstamp`	This element contains the sequence number of the fault to notify the FMS user interface.
`$clearcnt`	This element contains the number of off states in a pumping period.
`$edatetm`	This element contains the time and date when the fault event disappeared.
`$filtertm`	This element contains the expiry time of the filter period.
`$fltcheck`	This element contains the status in the database consistency check.
`$fltcodegpt`	This element contains the general problem type.
`$fltcodepbc`	This element contains the value of the SDH probable cause.
`$fltcodespt`	This element contains the specific problem type.
`$fltid`	This element contains the identifier of the fault.
`$fltstate`	This element indicates the status of the fault. This attribute can take the following values: `0`: The fault status is off. `1`: The fault status is on.
`$flttype`	This element contains a code for the fault type.
`$forcedon`	This element indicates whether the fault was forced by the software.
`$hwtype`	This element contains the hardware type of the faulty table.
`$ifnr`	This element contains the interface number.
`$logblknr`	This element contains the logical block number.
`$mid`	This element contains the NTU identifier of the modem.
`$mtnevent`	This element indicates the maintenance status of the circuit. This attribute can take the following values: `1`: PMA `2`: DMA `3`: MEI
`$nid`	This element contains the identifier of the node.
`$ntulink`	This element contains the number of the link (interface) to which a possible NTU is connected.
`$ntypemask`	This element contains masked node type information.
`$pdatetm`	This element contains the time and date when the fault was polled.
`$periodcnt`	This element contains the number of faults recorded during the occurrence period.
`$rmsstate`	This element contains the recovery status of the circuit. This element can take the following values: `0`: The status is undefined. `1`: The circuit has not recovered. `2`: The circuit has recovered.
`$sa`	This element contains the service alarm status.
`$sdatetm`	This element contains the time and date when the fault event appeared.
`$srkadr`	This element contains the subrack address.
`$srkhwtype`	This element contains the type of subrack hardware.
`$svrty`	This element contains the severity code as an integer between 1 and 5.
`$tid`	This element contains the identifier of the trunk.
`$ttypemask`	This element contains the masked trunk information.
`$unnr`	This element contains the unit number.
`$unslot`	This element contains the slot position of the unit.
`$vtypemask`	This element contains information on the masked view type.
Active Network Event Extended Fault Data
`$FaultSrc`	This element contains the source of the fault (only available with version R14 of Tellabs 8100).
`$NodeName`	This element contains the network event name.
`$TrunkName`	This element contains a description of the network event.

The following table describes the circuit elements that the probe generates.

Table 2. Circuit elements
Element Name	Element Description
`$acksta`	This element indicates the acknowledgement state. This attribute can take the following values: `0`: The event has not been acknowledged. `1`: The event has been acknowledged.
`$catid`	This element contains the identifier of the service category.
`$cid`	This element contains the identifier of the circuit.
`$custid`	This element contains the customer identifier.
`$eventtime`	This element contains the event time from AMS event table.
`$eventtype`	This element indicates the circuit event as described in the amsevent table. This attribute can take the following values: `21`: The circuit has broken. `22`: The circuit has recovered. `23`: The circuit has been repaired. `24`: The circuit has been restored. `41`: The circuit has broken. This is a network terminating unit (NTU) line fault. `42`: The circuit has broken. This is an NTU line fault.
`$fltstate`	This element indicates the fault status of the circuit. This attribute can take the following values: `0`: The fault status is off. `1`: The fault status is on.
`$mtnevent`	This element contains the maintenance status of the circuit.
`$operid`	This element contains the identifier of the operator.
`$rmstate`	This element contains the recovery status of the circuit.
`$sa`	This element contains the service alarm status of the circuit as one of the following values: `0`: The service alarm is off. `1`: The service alarm is on.
Active Extended Faulty Circuits Data
`$CircuitName`	This element contains the circuit name.
`$CustomerName`	This element contains the customer name.