Table of Contents
Advertisement
Technical Description
•
•
•
•
•
•
•
•
•
The system can also be configured to send SNMP v1 traps. These traps are
translated from the IRP format using co-existence rules for v1 and v2/v3 traps
(RFC 2576).
For a full description of alarms see user documentation.
9.4.2
Test Functions
Test functions can be used to verify that the transmission system is working
properly or they can be used to locate a faulty unit or interface.
9.5
Performance Management
9.5.1
General
The purpose of Performance Management for the Packet Terminal is to monitor
the performance of the RF Interface according to G.826.
The following performance counters are used:
•
•
•
•
42
Notification identifier: uniquely identifies each notification.
Alarm identifier: only applicable for alarms, identifies all alarm notifications
that relate to the same alarm.
Managed object class: identifies the type of the source.
Managed object instance: identifies the instance of the source like 1/11/1A.
Event time: time when alarm/event was generated.
Event type: X.73x compliant alarm/event type like communications alarm
and equipment alarm.
Probable cause: M.3100 and X.733 compliant probable cause, for example,
Loss Of Signal (LOS).
Perceived severity: X.733 compliant severity, for example, critical or
warning.
Specific problem: free text string detailing the probable cause.
Errored Seconds (ES)
Severely Errored Seconds (SES)
Background Block Error (BBE) (only structured interfaces)
Unavailable Seconds (UAS)
1/221 02-CSH 109 172/1-V1 Uen E | 2012-11-07
Advertisement
Table of Contents
