pPITTPSinkR1 — ETSI published formal attachments
This managed object class represents the point where the incoming interface signal is converted into an internal logic level and the timing is recovered from the line signal. The upStream connectivity pointer is NULL for an instance of this class. A communicationsAlarm notification shall be issued if a Loss of Signal (LOS) is detected. The probableCause parameter of the notification shall indicate lossOfSignal [3]. The operational state is disabled if a failure of the equipment affecting an instance of this class prevents the resource from operation If the attribute alarmSeverityProfilePointer points to an instance of the MOC alarmSeverityAssignmentProfile then the perceivedSeverity associated with the probableCause in the communicationsAlarm is determined by the assignment given in the attribute alarmSeverityAssignmentList of that instance. The value 'non-alarmed' of the severity assigned to a problem inhibits the emission of the potential communicationsAlarm notification of that problem. This behaviour meets the ability to configure the defect correlation filter not to report selected fault causes (i.e. problems) and hence no associated failures will be alerted by communicationsAlarm notifications. The alarmSeverityProfilePointer may point to an instance of alarmSeverityAssignmentProfile which is auto-created by the NE according the name-binding label 'defaultNMONAlarmSeverityAssignment-managedElement'. This relationship of the termination point reflects the NMON state during which no communicationsAlarm is reported at all. When the severity changes to a value 'non-alarmed' for a problem which has been notified by an instance of this class then a communicationsAlarm notification with the perceivedSeverity 'cleared' is issued and the corresponding entry in the attributes currentProblemList and alarmStatus is removed. When the severity changes from 'non-alarmed' to a value other than 'non-alarmed' then a pending, persistent defect will be notified. If the alarm severity cannot be assigned by the way of an alarmSeverityAssignmentProfile object (e.g. the attribute alarmSeverityProfilePointer has the value NULL or no assignment is given in the attribute alarmSeverityAssignmentList) then one of the two choices applies when reporting alarms: a) agent assigns the severity, b) the value 'indeterminate' is used.