pdhCurrentDataFarEndPackage — ETSI published formal attachments
Instances of the pdhCurrentDataFarEnd managed object class are used to hold the current far end register counts for a PDH path during a collection period. The following performance primitives are observed: Defect Seconds (pF_DS) and conditionally Errored Blocks (nF_B). The Errored Blocks are count in the attribute fEBBE if an instance of this class is subordinate of a PDH-termination point monitoring a frame and block structured paths. These primitives are provided by monitoring functions represented in superior PDH termination points and are defined in PDH path layers according to EN 300 417-5-1 [10]. For these performance primitives the following performance events are defined: FEES Far End Errored Second. FESES Far End Severely Errored Second. In addition, the following optional performance events are defined: FEUAS Far End Unavailable Second: This counter is used to store one second intervals pertaining to an unavailable time period at the far end. FEBBE Far End Errored Blocks for frame and block structured paths. FECSES Far End Consecutive SES. This managed object class uses the pdhPathHistoryDataFarEnd managed object class for history retention. A QOS alarm shall be sent as soon as a threshold is reached or crossed. At the end of the granularity period the QOS alarm is implicitly cleared and, providing there are no other outstanding threshold crossing QOS alarms, thresholdCrossing removed from the currentProblemList (i.e. No Notification is Sent). A new QOS alarm shall be sent if the threshold is reached or crossed again during the next granularity period. Only one threshold value per performance counter will be supported.