Maintenance

Siemens

Maintenance

Contents
1
1.1
1.2
1.3
1.4
1.5
1.6
2
2.1
2.2
2.3
2.4
3
3.1
3.2
3.3
3.4
3.5
4
4.1
5
6

Alarm handling
Basic information
General definitions
Alarm displays
Alarm suppression
Alarm report
Maintenance mode
Engineering Order Wire (EOW)
Overview to EOW
Call types and allocation of numbers
Tones and signals
Call setup
Basic troubleshooting
SDH alarm scheme
Optical safety management
Loopbacks for test
Examples of the alarm situations
Basic fault clearance
Field maintenance
Requirements applicable to personnel
Exercise
Solution

TR3271EU00TR_0302
2004 Siemens AG

3
4
6
8
20
22
23
25
26
26
28
30
33
34
38
40
46
56
61
62
67
73

Siemens

Maintenance

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Alarm handling

Fig. 1

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

1.1

Basic information

Fault Management is concerned with the detection, localization, isolation and

reporting of failures of the transmission signals processed by the hiT 70xx and of the
hiT 70xx equipment itself.
The failures and the failure processing are differentiated in two failure classes:

transmission failures

equipment failures

In addition to these two failure categories the hiT 70xx supports external alarm
contacts, which can be used for signaling any kind of failure.
Failures are reported via the QST management interface to the OS and may also
lead to alarm indications at the TNMS (card indications, NE indications).
Any alarm message (raised alarm or cleared alarm) is saved in an alarm log in order
to provide an alarm history. Furthermore a list of current alarms is kept for every NE
and is updated according to changes reported by the respective NE.

WARNING
Alarms, which are suppressed in the NE, are treated as cleared and are
therefore not contained in the current alarm list even if the corresponding fault
condition exists in the NE.

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

hiT 70xx Alarms

TNMS CT

Alarm Log
Alarm List
Raised alarms

Fig. 2 SURPASS hiT70xx alarms

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

Maintenance

Siemens

1.2

General definitions

Alarm Severity
Depending on the significance of the alarm messages and the alarm severity
assigned to them, they trigger different reactions. A minor fault which, for example,
has the effect of degrading the transmission signal (increased bit error rate) usually
has no significant effect on operation; for this reason, it results in a low priority alarm
message (minor). In contrast, serious faults can cause an interruption of service
and therefore result in a high priority alarm message (major), which requires
immediate fault clearance.
There are four classes of alarm priorities:

Critical (red LED symbol): Critical alarm

Major (orange LED symbol): Major alarm

Minor (yellow LED symbol): Alarm of no great significance

Warning (blue LED symbol): Alarm acting as a warning

Alarm Types

Traffic related:
Communication alarms: The communication alarms originate from TPs
(terminationPoint).
Quality of Service Alarms: The QoS alarms originate from TPs with
performance activities.

Equipment related:
Equipment alarms: The equipment alarms originate from specific cards.
Environmental alarms: The environmental alarms originate from outside the
Network Element (via telemetry interfaces TIF)
Processing error alarms: The processing error alarms originate from Software.

Alarm event types

There are the following two basic types of alarm events:

Raised: indicates the beginning of a certain alarm

Cleared: indicates the clearing of a previously reported alarm.

After having received an alarm-raised notification the TNMS assumes that this alarm
is present until a corresponding alarm cleared notification is received.

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Alarm Types:
Communications:

Associated with procedures and/or processes required to convey

information from one point to another

Quality of service:

Associated degradation in the quality of a service

Processing error:

Associated software or processing fault

Equipment:

Associated equipment fault

Environmental:

Associated condition relating to an enclosure in which the equipment

resides

Acknowledge state :
No alarm:

Indicates that there is currently no alarm for this managed resource.

Unacknowledged:

Indicates that there is at least one unacknowledged alarm for this managed
resource. There may be also acknowledged alarms.

Acknowledged:

Indicates that there are one or more alarms for this managed resource, all
of them in the acknowledged state.

Alarm event types :

Raised:

indicates the beginning of a certain alarm

Cleared:

indicates the clearing of a previously reported alarm

Fig. 3 General definitions

Acknowledge state
The acknowledge state is used by the network operator during the fault correction
process in order to keep track of the alarm work state. Every current alarm has an
acknowledge state attribute.

No alarm: Indicates that there is currently no alarm for this managed resource.

Unacknowledged: Indicates that there is at least one unacknowledged alarm

for this managed resource. There may be also acknowledged alarms.

Acknowledged: Indicates that there are one or more alarms for this managed
resource, all of them in the acknowledged state.

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

1.3
1.3.1

Alarm displays
Alarm displays on modules

To assist in maintenance, there are two LEDs on the front of the modules which are
visible once the sub-rack cover has been removed.
A red Fault LED indicates that an internal hardware failure happened, the card
program system is not OK or the software has made a reset. It is fed from an
externally supplied voltage (ULED) so that it can also illuminate when the drawer
power supply fails.
A green OK LED indicates that the card is in normal operation and may carry active
traffic.
In addition to the red and the green LED which have the same behavior as on other
cards, the Ethernet cards contain a yellow and green LED for each port. This will give
information on the Link Status and Link Activity to the operator and service
technicians.
The following alarm displays are available on the SURPASS hiT 7070 and SURPASS
hiT 7050 Modules and cards:

Fig. 4 SURPASS hiT 7070 plug in module

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Fig. 5 SURPASS hiT 7050 plug in module

OK FAULT

Fig. 6 SURPASS hiT 7050 plug in module

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

1.3.2

Alarm displays on sub racks

The indication elements (LEDs) at the sub racks and on the modules are a useful aid
particularly if neither an operating terminal, nor a network management system have
been connected to the SURPASS hiT 70xx series equipment when an alarm occurs.
The LEDs signal alarms at sub rack and module level.
Alarms raised in the sub rack are summarized with only two possible priority levels.
There is no further information about the alarm.
Configurable alarm table for external alarm interface
Each equipment or transport alarm has configurable assignment to a severity state
(major or minor) which is indicated by the NEAP LEDs in case of raised alarms.
The tables of alarm severities are configurable by the operator at OS/LCT and
include the following fields per entry (alarm):

alarm identification

card or transport function

severity (major, minor or severity not assigned)

TIP
In the Network Element Alarm Panel NEAP of the SURPASS hiT 7070 there is an
acknowledge key ACO for manual acknowledgment of the alarm messages.

ADDRESS
1

UBAT
2

EQUIPMENT-AL
3

COM-AL

4 MAJOR MINOR MAJOR MINOR ACO ACO-B

QF2

Red visual indicator

RJ45 connector

Yellow visual indicator

RJ11 connector

Green visual indicator

Ground Jack

Push-button

D-Sub 9 pin (male) connector

Fig. 7 Network element alarm panel NEAP (SURPASS hiT 7070)

10

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

TIF/Alarms

T3/T4

EOW

2 1
UBAT

Major
Minor

ACO

OK Fault

Fig. 8 Alarm indications and service connectors (SURPASS hiT 7050)

Fig. 9 NEAP Configuration

TR3271EU00TR_0302
2004 Siemens AG

11

Maintenance

Siemens

1.3.3

Alarm displays on TNMS CT

There are several ways of displaying alarms on the TNMS CT:

A collective alarm indication for the NE in the status bar of the TNMS CT.

A detailed alarm list and alarm log in the menu bar of the TNMS CT.

Collective alarm indication

In the alarm status field in the Main Status Bar (the bottom line of the display) five
LED symbols can show network element alarms of different severity as a collective
message. This alarm indication is automatic; the operator does not have to call it up.
It remains visible until the fault that triggered the alarm is cleared. A blue frame
around an LED symbol indicates that one or more alarms of this severity have not yet
been acknowledged.
There are five classes of alarm severities:

12

Critical (red LED symbol): Critical alarm

Major (orange LED symbol): Major alarm

Minor (yellow LED symbol): Minor alarm

Warning (blue LED symbol): Alarm acting as a warning

Indeterminate (white LED symbol): Indeterminate alarm

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Alarm
List

Alarm
Log

Collective
Alarm
Indication

Fig. 10 Alarm displays on TNMS CT

Alarm list and alarm log

The Alarm List and Alarm Log display current and historical information on alarms in
the following columns:
Time: Indicates the date and time the alarm has been created. The time-stamp may
be local or GMT.
Parent Node: Indicates the type, version and name of the associated Multi NE.
NE: Indicates the ID of the associated NE.
Object Type: Indicates the type of the alarming object inside the NE.
Location: Indicates the alarm location inside the NE, e.g. slot number.
Cause: Indicates the reason for the alarm.
Severity: Indicates the severity of the alarm, i.e. cleared, warning, minor, major,
critical or indeterminate.
Alarm Class: Indicates the type of alarm, e.g. environmental, communication.
State: The alarm state can be acknowledged or unacknowledged (Alarm List only).
Cleared Time: Indicates the date and time the alarm has been cleared (Alarm Log
only).

TR3271EU00TR_0302
2004 Siemens AG

13

Maintenance

Siemens

1.3.4

Alarm displays on module view

A detailed listing of all alarms - both current and historical, recorded since the
operating terminal began monitoring alarms - can be found in the alarm list.
1. It can be opened by choosing the main menu item "Fault ->Alarm List".
2. By choosing the required alarm severities and the alarm state (acknowledged or
unacknowledged) the data output can be filtered.

Fig. 11 Current alarm list

14

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Fig. 12 Alarm history

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

15

Maintenance

Siemens

1.3.5

Hierarchical alarm display

Module and functional symbols in hierarchically arranged windows are used for alarm
signaling and fault tracing.
Generally speaking, alarms are displayed by the concerned module or function
symbol flashing red. Because of the hierarchical arrangement, the symbol
responsible for the message and all higher level symbols will start flashing.
Thus, by following the red flashing through the hierarchy, starting from the highest
level, the fault can be exactly pinpointed. Choosing the option "Fault -> Alarm..."
allows the fault to be identified.
By choosing the Menu item "Fault -> Acknowledge" the alarm is acknowledged, and
the module stops flashing, but remains red in color, thus reminding the user that the
alarm is not yet cleared. Should another fault occur on the same module / function,
the symbol starts flashing once more.
According to the three operational views, three types of alarms are distinguished.
Alarms in the Module View
Module symbols signal faulty modules as well as transmission alarms within the
modules.
The corresponding alarm window of the module supplies further information about
the module (equipment alarms).
When selecting a transmission module, the traffic flow view of the module's ports is
displayed in the lower part of the module view. Here, transmission faults are
displayed also (transmission alarms of the chosen module).
Alarms in the Traffic Flow
A symbol for a traffic or transmission function signals an alarm, as does - in
hierarchical classification - the corresponding port symbol (in the lower part of the
Module view window) and the corresponding functional symbol of the Traffic Flow
window. For the latter, an alarm window provides details of all possible alarms, and
highlights the current alarms.

16

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Fig. 13 Alarms in the traffic flow

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

17

Siemens

Maintenance

Alarms in the NE
In the NE symbol, the central functions of the network element (Timing and TIF
alarms) are supervised and alarms can be displayed.
Alarms in the Sub rack
In the Sub rack symbol, the power supply of the sub rack is supervised and alarms
can be displayed.

18

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Fig. 14 Alarms in the NE / sub rack

Fig. 15 Alarms in the sub rack

TR3271EU00TR_0302
2004 Siemens AG

19

Maintenance

Siemens

1.4

Alarm suppression

Suppression set for an alarm has the effect of preventing the NE issuing an alarm
message to the operating terminal if there is a fault. No alarm can therefore be
signaled at the operating terminal interface for this particular fault condition. Alarm
suppression is signaled by the A-indicator on the concerned module/function
symbol changing color from wheat to dark gray.
Alarm suppression can be set for each individual alarm in the alarm windows:

Alarm
NoNoAlarm
suppression
suppression

Fig. 16 Alarm suppression_1

20

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

NoAlarm
Alarm
With
suppression
suppression

Fig. 17 Alarm suppression_2

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

21

Maintenance

Siemens

1.5

Alarm report

The report of the secondary (maintenance) alarms SSF and AIS and the remote
alarm RDI can be suppressed per individual alarm via the report control switch.
This results in the following behavior:

If the report control switch is disabled an active failure is cleared immediately.

If the report control switch is enabled and the corresponding fault cause is
active the failure is raised after the persistence time.

Alarm
Report

Fig. 18 Alarm report (Example with 2Mbit/s port)

22

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

1.6

Siemens

Maintenance mode

It is possible to set the entire network element to Operation or Maintenance mode. If

the signaling (operating) mode is configured for Operation, all spontaneous alarm
messages are signaled, provided that no masking with alarm suppression has taken
place.
If Maintenance mode is configured for corrective maintenance measures, the
transmission of all alarms is suppressed (from the NE to the operating terminal).
The NE state is configured using main menu items:
1. "NE State -> Set to Operation" or "NE State -> Set to Maintenance"
and
2. is displayed in the main status bar.

Fig. 19 Maintenance mode

TR3271EU00TR_0302
2004 Siemens AG

23

Siemens

24

Maintenance

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Engineering Order Wire (EOW)

Fig. 20

TR3271EU00TR_0302
2004 Siemens AG

25

Maintenance

Siemens

2.1

Overview to EOW

EOW processing capability is provided by the hiT 70xx Network Elements. Goal of
EOW processing is to support a telephone link to one or more other network
elements by using the RSOH byte E1 and/or the MSOH byte E2 for EOW
communication.
Requirements for using the engineering order wire (EOW) are:

that the connection setup is configured using the OH bytes, and

that a telephone number for selective or group calling has been assigned to the
network element.

A telephone handset for DTMF dialing with integrated keypad and internal buzzer is
used to provide the EOW facilities. The key functions are shown in the Fig xx.

2.2

Call types and allocation of numbers

2.2.1

Call types

With the call types selective calling, group calling and collective calling it is possible
to call an individual subscriber, a group of subscribers or all subscribers collectively.
Selective calling
Selective calling is used to call an individual subscriber.

Lift the telephone handset and enter the 3-digit number of the desired network
element.

Group calling
Group calling is used to call a group of network elements as part of a conference call.
Here network elements with the same tens digit or the same hundreds digit can be
called at the same time as a group. To call a group a 0 should be dialed for the ones
digit and/or the tens digit.

Lift the telephone receiver and enter the telephone number of the desired group
of network elements, replacing either the last or the last-but-one digit by 0.

Collective calling
Collective calling is used to call all subscribers of the conference at the same time.

Lift the telephone receiver and enter the telephone number 000.

Examples:

26

No. 120 signals 121 to 129

No. 100 signals 111 to 199

No. 000 signals 111 to 999 (= collective calling)

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Function of the Telephone Keys

0...9

Telephone number

A...C

Keys for manual entry of DTMF signals.

Enable conference; activates selective receiver and separates PBX interfaces from
conference

Initiates a special function in combination with two following dialing numbers

*09

Special function in combination with PBX subscribers (prevents separation of the PBX
from conference via button # for a time span of 10 s)

999

Special function in combination with PBX subscribers (separates subscriber from net)

Fig. 21 Function of the Telephone Keys

Number Scheme

Number dialed

Subscriber group
reached

Collective calling

000

000 to 999

Group calling

X00

X00 to X99

XY0

XY0 to XY9

XYZ

XYZ

Selective calling

Note

where: X, Y, Z = 1 to 9

Fig. 22 Number Scheme

TR3271EU00TR_0302
2004 Siemens AG

27

Maintenance

Siemens

2.2.2
Note

Allocation of numbers
where: X, Y, Z = 1 to 9

Fig. 22 gives the number codes for the various subscribers/subscriber groups.
The telephone numbers X00, XY0 and 000 are reserved for group calling and
collective calling and can thus not be used as selective calling numbers. Since digit
0 may not be included for selective calling numbers (nor may 109, 208...), the
available number of purely selective calling numbers is restricted to 729. In addition,
the telephone number combination *09 should be avoided as it is assigned to a
special function.

2.3

Tones and signals

Fig. 23 shows a graphical diagram of the audible and visual signaling in the EOW
area.
If, in addition to EOW equipment with 3-digit telephone numbers there also is
equipment with 2-digit telephone numbers in the network (e.g. SL16... series 1), you
should make sure when allocating telephone numbers that unique subscriber
assignment is assured (e.g. do not allocate the numbers 141, 142,... if there already
is a 2-digit telephone number of 14 and vice versa).

28

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Tones and Signals

Dial tone (three-tone signal at 2-second intervals)
Sounds for 10 seconds after pickup the handset.
Ringing tone (single tone at 5-second intervals)
Sounds if conference is free.
Busy tone (single tone at 1-second interval)
Sounds if conference is busy.
Break-in tone (three double tones)
Sounds if a subscriber is breaking into an existing
conference.
Negative acknowledge tone (single tone, 2 times)
Sounds if wrong dialing is made.
Ringing signal tone via buzzer in handset
(single tone at 5-second intervals)
activated only with handset on hook.
Green telephone LED
off: Handset is on-hook
flashes: Incoming call
on: Handset is picked up

Fig. 23 Tones and Signals

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

29

Maintenance

Siemens

2.4
2.4.1

Call setup
General information

Depending on the type of call selected, all EOW telephones are always connected to
each other via the transmission link, i.e. each subscriber who connects to the same
conference can listen and join in (Party line mode).
You can break into existing EOW connections at any time by lifting the handset and
pressing #.
When collective calling is used all subscribers are reached simultaneously by the
ringing signal via the interconnected equipment and can each participate in the call.
When operating with selective calling individual subscribers or also subscriber groups
(group calling) can be dialed using a three-digit telephone number. The subscriber
receiving the call, but others on the party line as well, can break into the conference,
take part in the conversation or simply listen.
For setting up a connection to specific network elements it is necessary to activate
their DTMF receivers (signal/key A) and reset them again after the call (signal/key B).
The type of EOW indicates whether this is done automatically or by pressing
additional keys.

2.4.2

Outgoing call

The procedure for setting up a conference or for the EOW to break into an existing
conference is shown as a flowchart in Fig. 24 and Fig. 25.
Breaking into the conference is signaled to other conference participants by a breakin tone.

2.4.3

Incoming call

In the case of an incoming call, for network elements with an Subrack Alarm Panel Phone Indication, the green telephone LED starts flashing.
If the telephone handset is on-hook the internal buzzer is activated. At the same time
the ringing signal is output at an optional external ringer. The telephone handset is
switched into the conference as soon as it is lifted.
The procedure for an incoming call is shown in the form of a flowchart in Fig. 26.

30

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Setting up a Conference Call (I)

Pickup handset

Busy tone

Press # button to connect to busy conference

The conference participants will hear the break-in tone

Notify the other participants if you would like to call a new subscriber
Press # button to activate the DTMF receivers for calling a new subscriber.
NOTE: All PBX connections are disconnected from the conference
(this can be avoided by dialing special function *09 before #.
All other participants remain in the conference if they did not hang up.
Conference LED is continuously on
Dial tone

Dial subscriber number (selective, group, collective call)

Fig. 24 Setting up a Conference Call/Breaking into the Conference Call (I)

Setting up a Conference Call (II)

Call tone (not in case of group or collective call)

If the suggested subscriber is connected to another conference you

will here the busy tone. But do not hang up and wait a while. The subscriber
will hear a notification tone and can change to your conference.

The conference is established. If one would like to add more participants repeat
the following steps:
(special function 09) > # button > dial tone > dial number > call tone
The special function *09 avoids disconnection of the PBX from the conference
for the next 10 seconds.
Before closing the conference, one participant should press the # button.
This will activate the conference for new calls.
Hang up
Conference LED is switched off

Fig. 25 Setting up a Conference Call/Breaking into the Conference Call (II)

TR3271EU00TR_0302
2004 Siemens AG

31

Maintenance

Siemens

Receiving a Call with the Telephone Handset On-hook

Incoming call from a conference
The internal ringer is activated

the conference LED is flashing and the contact for the external ringer is
activated with the ringing frequency for 30 seconds.
Pick up the handset. The ringers are deactivated.

The conference LED is continuously on.

The connection to the conference is established. If you would like
to add more participants repeat the following steps:
press # button > dial number > call tone
Before closing the conference, one participant should press the
# button. This will activate the conference for new calls.

Hang up
Conference LED is switched off

Fig. 26 Receiving a Call with the Telephone Handset On-hook

Time to exercise NOW !!!

Exercise 2
Title:
Objectives:

Pre-requisite:

Engineering Order Wire (EOW)

The participant shall be able to:
z Set up a conference call
z break into an existing conference call
z close a conference
Real NEs with EOW feature available and configured

Fig. 27 Exercise 2

32

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Basic troubleshooting
TxDeg
auLOP
SD
SSF
AIS

TxFail

TS_T3
FERF

MIS-SL

LOS
UNEQ

Fig. 28

TR3271EU00TR_0302
2004 Siemens AG

33

Maintenance

Siemens

3.1

SDH alarm scheme

Large numbers of alarm and error messages are an integral part of SDH networks. In
SDH, these are referred to as defects and anomalies, respectively. They are coupled
to network sections and the corresponding overhead information. The advantage of
this detailed information is illustrated as follows:
Complete failure of a circuit results, for example, in a LOS alarm (loss of signal) in the
receiving network element. This alarm triggers a complete chain of subsequent
messages in the form of AIS (alarm indication signals). The transmitting side is
informed of the failure by the return of an RDI alarm (remote defect indication). The
alarm messages are transmitted in fixed bytes in the SOH or POH. For example, byte
G1 is used for the HP-RDI alarm.
If the received signal contains bit errors, the sensor indicates BIP errors. Since this is
not the same as a complete failure of the circuit, the alarm here is referred to as an
anomaly that is indicated back in the direction of transmission. The return message is
called a REI (remote error indication).

34

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

STM-N Alarm Scheme

High Order Path
Multiplex Section
Regenerator
Section

Regenerator
Section
K2

MS
RDI
HP
RDI

AIS

MS-AIS

LOS/LOF

AIS

MS
RDI
HP
RDI

K2
MS BIP

BIP Err.

G1
MS
REI

B1

B2
HP
BIP

M1

HP
REI

B3

G1

SDH
Multiplexer

SDH
Regenerator

SDH
Multiplexer

Fig. 29 Sections in a SDH network

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

35

Maintenance

Siemens

With the help of the overhead data bytes, we can send forward and backward from
the reporting network element certain alarm conditions. This information helps to
localize the fault as quickly as possible.
Using a process of prioritization, and elimination, we can determine where the fault is,
what is possibly causing it and what needs to be done to fix it.
The following diagram attempts to show the Alarms raised, their subsequent actions,
destinations in the forward and backward directions.
The following description should help to read the diagram:

(J0), (C2), (H4) etc are bytes to be found in the RSOH, MSOH, POH High and
low order.

The line shows the direction the Alarm is sent, with a description of the alarm
event for example Loss of Signal, or Loss of frame.

The following show all the alarms that cause the forwarding onwards or
backwards of the next alarm indication as required.

The alarm names indicate the alarms that all cause the subsequent alarm
indication and the "1" indicates the contents of the STM frame contains all "1"s
in the AU-4.

LOS/LOF

Detected and Raised

(Object, where the alarm is generated.)
Generation and Sent
Fig. 30 Symbol description

36

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Fig. 31 SDH maintenance interactions

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.

37

Maintenance

Siemens

3.2

Optical safety management

All versions of optical interfaces comprise ALS circuits (Automatic Laser Shutdown),
which are activated whenever the optical carrier fails, in accordance with ITU-T
Recommendation G.958 and IEC standard 825 Appendix 2.
In the presence of a LOS (Loss-of-signal) alarm the Laser is automatically switched
OFF (LSOFF) leaving the optical connection in ALS status. The Laser recovering can
be performed in automatic or manual mode.
The automatic Laser recovering mode is enabled by default and it is performed
without any action of operators: when the optical carrier has been restored the optical
connection is recovered after the restore time (90s 10 sec).
If the optical carrier has been restored the optical connection is immediately
recovered.
In the case of manual laser restart the Laser will be re-activated for a time lasting
(normal 2s or extended 90s) and it will be switch OFF again.
The specific equipment configuration allows the possibility to enable/disable the
automatic laser shutdown (disabled by default), according to the EM settings.

Tx

Rx
LSOFF
LSOFF

Rx

Tx

Optical carrier break

Loss-off-signal (LOS) alarm

Loss-off-signal (LOS) alarm

Automatic Laser Shut-down (ALS)

Automatic Laser Shut-down (ALS)

Fig. 32 Automatic Laser Shutdown

38

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Force
Laser
Shutdown
Automatic
Laser
Shutdown

Manual
Laser
Restart

Fig. 33 Optical Safety management

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

39

Maintenance

Siemens

3.3

Loopbacks for test

SURPASS hiT 7070 and hiT 7050 FP1 NEs provide two types of loopbacks, to test
the traffic flow without external cabling for commissioning, maintenance and fault
isolation purpose. The loopback is configurable by software:

Outward loopback

Inward loopback

TIP
While the outward port loops are supported for SDH as well as PDH cards, the
inward loops are supported on PDH cards only.
Outward loopback
The outward loopback (line loop back or external loop back) is the loop from the card
input (receive) port to the card output (transmit) port.
This type of loop back can be done for all SDH traffic cards (hiT 7070 SC, hiT 7070
DC, hiT 7050 FP1) and PDH traffic cards (hiT 7070 SC and hiT 7050 FP1 only).
TIP
There is no port loopback support on any of the Ethernet cards and on PDH cards
plugged in a PDH MicroShelf the outward loopback function is not supported.
The port loop-backs are implemented transparent only. The signal is looped back but
also forwarded to its destination point. A non-transparent loop, where the signal is
looped back but AIS signal is sent toward the destination point, is not supported.

On hiT 7070 SDH traffic cards all VC4s of a port are looped back to the port by
means of the switch matrix.

On PDH traffic cards of hiT 7070 SC systems, outward port loops are emulated
by means of VC12 cross-connections within the LO switch matrix (SF10G,
SF2G5). For traffic interface cards in the PDH MicroShelf, no outward port loops
can be established as no according LO switch matrix can be directly associated
with the PDH port (no direct relationship as it is the case at hiT 7070 SC).

At the hiT 7050 FP1 all VCn (VC4, VC3 and VC12) of a port, according to the
configuration, are looped back to the port by means of the switch matrix.

Inward loopback
The inward loop back (internal loop back) is the loop of the output signal, coming
from the switching matrix, to the interface card, i.e. the output signal is looped back to
the internal of the Network Element.
This type of loop back can be done on all PDH cards. The inward port loops are
established directly at the PDH cards.
Also for the inward loops there is no AIS-insertion downstream, i.e. only the
transparent loop types are supported.

40

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Loopbacks for Test

Outward loopback (line loop back or external loop back)
HO/LO switch

Framer

Phy. Port

STM-N / PDH

Inward loopback (internal loop back)

HO/LO switch

Framer

Phy. Port

PDH

There
There is
is NO
NO port
port loopback
loopback support
support on
on any
any of
of the
the Ethernet
Ethernet cards
cards
On
On PDH
PDH cards
cards plugged
plugged in
in aa PDH
PDH MicroShelf
MicroShelf only
only Inward
Inward Loopback
Loopback funtion
funtion is
is supported
supported

Fig. 34 Loopbacks for Test

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

41

Maintenance

Siemens

Port Loopback Configuration

For traffic ports the operator can configure at the operating terminal and depending
on the port type:

loop of the external traffic interface (loop the incoming signal at the SDH or PDH
input port back to the output port)

loop of the internal traffic interface (loop the incoming signal from the switching
matrix back to the matrix; available on PDH ports only)

TIP
Loop configuration is done on a port basis, i.e. the whole port is looped.
Default value: No loop
Function: Configuration of Port Loopback.

42

Step

Name of the Window

Used Menu or Command

"Module View" Window Select (LMB) module symbol.

"Module View" Window From the port list in the bottom

window segment select (RMB)
port symbol. From open menu
select "Port Configuration"

"Port Config" Window

Select the loopback parameter to

be configured.

"Port Config" Window

Confirm selection with the

"Apply" button.

Remarks
"Port Config"
Window opens

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Fig. 35 hiT 7070 SDH port loopback configuration

3
2

Fig. 36 hiT 7050 SDH port loopback configuration

TR3271EU00TR_0302
2004 Siemens AG

43

Maintenance

Siemens

Fig. 37 hiT 7070 PDH port loopback configuration

44

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

2
3

Fig. 38 hiT 7050 PDH port loopback configuration

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

45

Maintenance

Siemens

3.4

Examples of the alarm situations

3.4.1

Example of an alarm situation with LOS

LOS - Loss Of Signal:

The LOS state is considered to have occurred when the amplitude of the relevant
signal has dropped below prescribed limits for a prescribed period.
Refer to ITU-T Recommendation G.780

Loss of Signal (LOS)

Object
OS

SDH
Multiplexer

Alarm
LOS

SDH
Multiplexer

SDH
Multiplexer

Object
OS

Alarm
LOS

Fig. 39 Example with LOS

46

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

3.4.2

Siemens

Example of an alarm situation with RDI

RDI - Remote Defect Indication:

Remote Defect Indication (RDI) is a signal, which conveys the defect status of the
characteristic information received by the Trail Termination sink function back to the
network element, which originated the characteristic information.
Refer to ITU-T Recommendation G.780

Remote Defect Indication (RDI)

Only one
Direction is
affected

SDH
Multiplexer

Alarm
LOS

SDH
Multiplexer

SDH
Multiplexer

ALS
is
deactivated

Object
MS

Object
OS

Alarm
RDI

By default is suppressed

Fig. 40 Example with RDI

TR3271EU00TR_0302
2004 Siemens AG

47

Maintenance

Siemens

3.4.3

Example of an alarm situation with AIS

AIS - Alarm Indication Signal:

Alarm Indication Signal (AIS) is a code sent downstream in a digital network as an
indication that an upstream failure has been detected and alarmed. It is associated
with multiple transport layers.
Refer to ITU-T Recommendation G.780

Alarm Indication Signal (MS-AIS)

Object
OS

SDH
Multiplexer

Alarm
LOS

SDH
Regenerator

Object
MS

Alarm
AIS

SDH
Multiplexer

By default is suppressed
Fig. 41 Example with MS-AIS

48

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

3.4.4

Siemens

Examples of alarm situations with SSF

SSF - Server Signal Fail:

Server Signal Fail (SSF) is a signal fail indication output at the CP (Connection Point)
of an adaptation function.
Refer to ITU-T Recommendation G.780

3.4.4.1

Example: Multiplex Section MS

Server Signal Fail (MS-SSF)

Object
OS

SDH
Multiplexer

Object
MS

Alarm
LOS

Object
RS

SDH
Multiplexer

Alarm
SSF

SDH
Multiplexer

Alarm
SSF

Object
OS

Alarm
LOS

By default is suppressed
Fig. 42 Example with SSF within a multiplex section

TR3271EU00TR_0302
2004 Siemens AG

49

Maintenance

Siemens

3.4.4.2

Example: higher order path

Server Signal Fail (VC-4 SSF)

Object
OS

Alarm
LOS

SDH
Multiplexer

SDH
Multiplexer

2
140 Mb/s

Object
MS

Object
MS

Alarm
SSF

Object
AU-4

Alarm
AIS

Object Alarm
VC-4 TTP SSF

SDH
Multiplexer

Alarm
SSF

Object
OS

Alarm
LOS

140 Mb/s

By default is suppressed

Object Alarm
VC-4 TTP SSF

Fig. 43 Example with SSF on a Higher Order Path

50

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

3.4.4.3

Example: lower order path

Server Signal Fail (VC-12 SSF)

Object
OS

Object
MS

Alarm
LOS

Alarm
SSF

Object
Alarm
TU-12 CTP AIS

Object Alarm
VC-4 CTP SSF

SDH
Multiplexer

SDH
Multiplexer

SDH
Multiplexer

1
2
2 Mbit/s

Object
Alarm
VC-4 CTP SSF

Object
OS

Object
MS

Alarm
LOS

2 Mbit/s

Object
Alarm
VC-12 TTP SSF

Alarm
SSF

By default is suppressed

Object
Alarm
VC-12 TTP SSF

Fig. 44 Example with SSF on a lower order path

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

51

Maintenance

Siemens

3.4.5

Examples of alarm situations with unequipped

Uneq. - Unequipped VCs:

These signals indicate to downstream transport processing functions that the virtual
container is unoccupied, not connected to a path termination source function.
Additional information on the quality is only available by means of the BIP monitoring.
Refer to ITU-T Recommendation G.780

3.4.5.1

Example: missing CC at one end of a path without mux-structure

Unequipped VC-4
6

Object
VC-4

Alarm
RDI

VC-4-CC
is missing.

3
5

Object Alarm
VC-4 UNEQ

SDH
Multiplexer

Object
VC-4

Alarm
RDI

Object Alarm
VC-4
UNEQ

SDH
Multiplexer

SDH
Multiplexer

1
140 Mbit/s
4

Object Alarm
VC-4
UNEQ

Alarms only visible if

Connection Supervision
for VC4 is enabled.
Default setting: Disabled.

Object Alarm
VC-4 UNEQ

140 Mbit/s

By default is suppressed

Fig. 45 Unequipped VC-4

52

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

3.4.5.2

Siemens

Example: missing CC at one end of a path with mux-structure

Unequipped VC-12

Object
VC-12

Object
VC-12

Alarm
RDI

SDH
Multiplexer

Object
VC-12

SDH
Multiplexer

Alarm
UNEQ

Object
VC-12

Alarm
UNEQ

Object Alarm
VC-12 UNEQ

Alarm
RDI

SDH
Multiplexer

2 Mbit/s

2 Mbit/s CC
is missing.

Alarms only visible if

for VC4 (MUX structure)
Connection Supervision
is enabled.
Default setting: Disabled.

2 Mbit/s

Object
VC-12

Alarm
UNEQ

By default is suppressed

Fig. 46 Path with mux-structure

TIP
By default configuration Unequipped alarms are generated for all not Cross
Connected PDH TPs.

TR3271EU00TR_0302
2004 Siemens AG

53

Maintenance

Siemens

3.4.5.3

Example: missing CC inside a path with mux-structure

Unequipped VC-12

2 Mbit/s CC
is missing.
1

Object
VC-12

Object
VC-12

Alarm
RDI

SDH
Multiplexer

SDH
Multiplexer

Alarm
UNEQ

SDH
Multiplexer

1
3

Object
VC-12

2 Mbit/s
2

Object
VC-12

Alarm
UNEQ

Alarm
UNEQ

Object
VC-12

Alarms only visible if

for VC4 (MUX structure)
Connection Supervision
is enabled.
Default setting: Disabled.

Alarm
RDI

2 Mbit/s

Object
VC-12

Alarm
UNEQ

By default is suppressed

Fig. 47 Path with mux-structure

TIP
By default configuration Unequipped alarms are generated for all not Cross
Connected PDH TPs.

54

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

3.4.5.4

Siemens

Example: missing CC inside a path without mux-structure

Unequipped VC-4
Mux. Structure
is not activated
and a CC is
missing.
1

Object
VC-4

SDH
Multiplexer

Alarm
UNEQ

SDH
Multiplexer

Object
VC-12

Alarm
SSF

SDH
Multiplexer

1
2
2 Mbit/s

Object
VC-12
3

Object
VC-12

Alarm
SSF

Alarm
SSF

Object
VC-4

Alarm
UNEQ

Alarms only visible if

for VC4 (MUX structure)
Connection Supervision
is enabled.
Default setting: Disabled.

3
2 Mbit/s

Object
VC-12

Alarm
SSF

By default is suppressed

Fig. 48 Path without mux-structure

TIP
By default configuration Unequipped alarms are generated for all not Cross
Connected PDH TPs.

TR3271EU00TR_0302
2004 Siemens AG

55

Maintenance

Siemens

3.5

Basic fault clearance

Basic options for alarm containment and alarm evaluation

Basic Fault Clearance

Alarm

LEDs on the
alarm panel of the
sub rack or modules

Detailed
identification of the
alarm on the screen
of TNMS CT

Referring to the
Remedial actions
in the on-line help

Fig. 49 Basic fault clearance

3.5.1

Initial step: check LED's

The initial approach to fault finding is to observe LED indications. This will help you to
determine where the fault might be quickly. The observation of these LED's can be
done without the need to connect a TNMS CT.
WARNING
Before you open housing covers of all NE's SURPASS hiT 7000 series and
when doing any work with the sub-rack open, you must observe the safety
measures given in the OGL (Operator Guidelines).

56

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

The following tables should help you to locate the LED on the Sub-rack and Modules.

ADDRESS
1

UBAT
2

EQUIPMENT-AL
3

COM-AL

4 MAJOR MINOR MAJOR MINOR ACO ACO-B

QF2

NEAP
LED Name

LED Color

EQUIPMENT-AL
EQUIPMENT-AL
COM-AL
COM-AL
ACO
UBAT 1
UBAT 2
UBAT 3
UBAT 4

Red
Yellow
Red
Yellow
Blue
Green
Green
Green
Green

MAJOR
MINOR
MAJOR
MINOR

Explanation
Major equipment alarm
Minor equipment alarm
Major communication alarm
Minor communication alarm
Acknowledged alarm
Power supply UBAT1 is working
Power supply UBAT2 is working
Power supply UBAT3 is working
Power supply UBAT4 is working

MFP1 Drawer
LED Name

LED Color

ACO
TIF/Alarms

T3/T4

2 1
UBAT

Major

Major alarm
Minor alarm
Acknowledged alarm
Power supply UBAT1 is working
Power supply UBAT2 is working
Service LED
Fault alarm LED

Minor

Red
Yellow
Blue
Green
Green
Green
Red

MAJOR
MINOR
ACO
UBAT 1
UBAT 2
OK
FAULT

Explanation
EOW

OK Fault

Fig. 50 Alarm LED indications on SURPASS hiT 7070 and SURPASS hiT 7050 sub racks

Modules (Cards)
LED Name

LED Color

OK
FAULT

Green
Red

Explanation
Service LED
Fault alarm LED

SURPASS hiT 7070

SURPASS hiT 7050

Fig. 51 Alarm LED indication on modules

TR3271EU00TR_0302
2004 Siemens AG

57

Maintenance

Siemens

3.5.2

Next step: log in with TNMS CT

Once all LEDS have been checked, further fault analysis must be done via the TNMS
CT operating terminal.
Once log in has been achieved, alarm information and status will be displayed on the
screen. Clicking with RMB on modules or functions that are red or flashing red will
take you to the "Fault" option in the sub-menu.
Note that some modules or functions may have a number of "Subviews". One needs
to keeping clicking on each resultant "Subviews" until the "Fault" option is seen.
When one has reached the "Fault" option you can select either

"Equipment Alarms" (or "Communication Alarms")

"Acknowledge"

Fig. 52 Alarm information on TNMS CT screen

58

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

3.5.3

Siemens

Next step: embedded online help

In addition to the information received from the alarm window refer to the "Remedial
Action" columns in the on-line help alarm tables. They contain specific instructions
regarding fault clearance.
Clicking "F1" button on the keyboard or via main menu bar "Online Help" the page
"Alarm Names, Severities and Remedial Actions" containing Remedial Action
needs to be opened.

Fig. 53 Online help window

TR3271EU00TR_0302
2004 Siemens AG

59

Maintenance

Siemens

Special Fault Clearance

In the event of faults occurring which cannot be eliminated by applying the fault
clearance procedures and other instructions contained in the OGL, you may contact
the relevant Siemens AG Service Agency. In order to provide effective support for the
fault clearance operations, the following basic details will be required:

60

Complete reference numbers for the equipment affected by the fault

Software release numbers for the equipment affected by the fault

An accurate description of the fault (time of occurrence, apparent associations

with other factors, etc.)

Details of the attempts already made to rectify the fault.

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Field maintenance

UX
X-M
X
MU
XL-

UX
T-M

XX

12
U-5
CP
12
U-5
CP
RE
DO

UX
L-M

X
-MU
DT
X
MU
PT-

UX
SI-M

Fig. 54

TR3271EU00TR_0302
2004 Siemens AG

61

Maintenance

Siemens

4.1
4.1.1

Requirements applicable to personnel

The network element manager

The Network Element Manager is assigned to a regional network management

center or to a field service region. He is responsible for all corrective and routine
maintenance for all equipment installed in the particular region. He advises and
supports the Network Element Assistant.
In case of faults within the network, the Network Element Manager receives precise
information about an alarm from the NMC Operator, the Fault Management Expert or
he recognizes the alarm himself. He performs alarm analysis using the appropriate
manuals and defines the measures for fault clearance. He then notifies the Network
Element Assistant or the Network Element Manager dedicated to field service about
the measures to be taken, or he may perform the job himself. The maintenance
personnel must travel to the appropriate location, and perform, if necessary, further
alarm analysis on site. This includes taking measurements or other related tasks,
replacing the defective unit, performing local function tests for verification and
restoring the service in cooperation with the Network Element Manager working at
the relevant network management facilities. Module Replacement procedures that
require the Operating Terminal are performed by the Network Element Manager (e.g.
replacement of a controller module).

4.1.2

The network element assistant

The Network Element Assistant is assigned to a central or regional network

management center (NMC) or to a service region. His main tasks are standard fault
clearance and other routine, preventive maintenance tasks.
The Network Element Assistant receives information about an alarm and detailed
instructions on the replacement of the defective unit. He replaces the defective unit,
performs local function tests for verification and restores the service in cooperation
with the Network Element Manager.
On request by the Network Element Manager, Configuration Management Expert,
Fault Management Expert or Performance Management Expert he performs routine,
preventive or other related maintenance tasks.

62

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Network Element
Manager

Network Element
Assistent

Fig. 55

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

TR3271EU00TR_0302
2004 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

63

Maintenance

Siemens

4.1.3

Module replacement

Before replacing any suspect module, try to reactivate the system by means of a
hardware reset (e. g. pulling and re-inserting the module, however, do not attempt
this if the red fault LED on the module is lit.

When replacing modules, you must comply with the safety regulations, as
described in Chapter 2 of the Operators Guidelines (OGL).

When replacing a module, it is essential to check and record the optical and the
electrical transmitting power, using an optical or electrical power meter
respectively, before the modules are returned to service.

The module setup procedure can only commence once the module has been
correctly inserted into the slot, as far as the stop, and then locked.

Modules can be removed from or plugged into the sub-rack while they are live.

After a module has been replaced, the module status must be checked using
the LCT/NCT.

As the modules are pulled out or plugged in, spontaneous error messages and
error messages can suppressed if the complete network element or the module
to be replaced is configured in the Maintenance operating mode: "NE State...
-> Set to Maintenance".

4.1.3.1

Replacement of the SCOH module

WARNING
The new SCOH module must contain the same APS (Application Program
System) as the replaced module; otherwise there can be uncontrolled APS
changeover with a variety of consequences, which may even include traffic
interruptions.
The HW/SW compatibility numbers of the new and the replaced module must
be identical or the APS currently active must support both the old and the new
compatibility number.
1) Remove the faulty SCOH module from the sub-rack.
2) Pull out the MMC card from the faulty SCOH module (placed at the front panel of
the SCOH).
TIP
The current NE-VCDB is stored in the MMC card.

64

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

3) Insert the MMC card to the new SCOH module.

4) Plug in new SCOH module with the inserted MMC card to the sub-rack. After the
SCOH module is plugged in, it begins its startup sequence and accepts the last
valid NE configuration data (VCDB) from the MMC card.
WARNING
The data in the MMC card belongs always to the sub-rack!
5) Connect TNMS CT to the NE and prove that NE is "Active" and in "Operation"
mode.

4.1.4

Disconnection of power supplies

You can disconnect the power supply to the system at any time, however, without the
need of taking special steps to prepare the equipment. This can be done for example
by disconnecting from the rack fuse panel those fuses, which are assigned to the
particular system sub-rack. However, Please remember:
WARNING
Disconnection of the power supply will result in interruption to the entire
payload transmission.
When the power supply is restored, the system will start up automatically. As the
power comes up, the status of individual modules is indicated by the red and green
LEDs on each of the modules.
Naturally, the TNMS CT can be switched on or off independently of the system power
supply.

TR3271EU00TR_0302
2004 Siemens AG

65

Siemens

66

Maintenance

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Exercise

TR3271EU00TR_0302
2004 Siemens AG

67

Siemens

68

Maintenance

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Exercise 1
Title:

Maintenance

Objectives:

The participant shall be able to

z explain the different alarm displays
z describe the different alarm lists
z evaluate alarms
z describe the procedures for module replacement

Pre-requisite:

pre-read the chapter maintenance

Task
Answer the following statements as true or false

Query
T

F
In the alarm status field (main status bar) up to five LED symbols can be
shown for network element alarms to indicate different severity.
the red LED symbol indicates a critical alarm
the green LED symbol indicates a major alarm
the yellow LED symbol indicates a minor alarm
the blue LED symbol indicates a unknown alarm
the alarm list contains a detailed listing of all individual alarms
the history alarm list can contain up to 100 entries
it is possible to set the entire network element to either operation or
maintenance. If the maintenance mode is configured the transmission of all
alarms from the NE to the OT is suppressed
Alarms which are not shown via the TNMS CT are signaled on the hardware
display elements,
on each module a red fault LED indicates any internal card alarms
modules must not be removed or inserted under voltage
Module Replacement: After a new module has been plugged into the
corresponding slot of the sub rack it will go through an automatic startup
phase and the main controller downloads the configuration.

TR3271EU00TR_0302
2004 Siemens AG

69

Siemens

70

Maintenance

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Exercise 2
Title:

Engineering Order Wire (EOW)

Objectives:

The participant shall be able to:

z Set up a conference call
z break into an existing conference call
z close a conference

Pre-requisite:

Real NEs with EOW feature available and configured

Task
1. From node "Nuernberg/Mainz" establish a selective call to node
"Ulm/Essen".

Query
true

false

On node "Ulm/Essen" the conference LED is flashing

On node "Nuernberg/Mainz" the conference LED is continuously on
On node "Ulm/Essen" the ringers are activated
2. Pick up the handset at node "Ulm/Essen"

Query
true

false

On node "Ulm/Essen" the conference LED is flashing

On node "Nuernberg/Mainz" the conference LED is continuously on
On node "Ulm/Essen" the ringers are deactivated
3. From node "Muenchen/Dortmund" establish a selective call to node
"Ulm/Essen".

Query
true

false

It is not possible to call node "Ulm/Essen" because the EOW conference is busy

TR3271EU00TR_0302
2004 Siemens AG

71

Maintenance

Siemens

4. Close the conference

true

false

Before closing the conference, one participant should press the # button. This will
activate the conference for new calls.
To close the conference, one participant should press the # button.

72

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Solution

TR3271EU00TR_0302
2004 Siemens AG

73

Siemens

74

Maintenance

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Solution 1
Title:

Maintenance

Objectives:

The participant shall be able to

z explain the different alarm displays
z describe the different alarm lists
z evaluate alarms
z describe the procedures for module replacement

Pre-requisite:

pre-read the chapter maintenance

Task
Answer the following statements as true or false

Query
T

F
In the alarm status field (main status bar) up to five LED symbols can be
shown for network element alarms to indicate different severity.
the red LED symbol indicates a critical alarm
the green LED symbol indicates a major alarm
the yellow LED symbol indicates a minor alarm
the blue LED symbol indicates a unknown alarm
the alarm list contains a detailed listing of all individual alarms
the history alarm list can contain up to 100 entries
it is possible to set the entire network element to either operation or
maintenance. If the maintenance mode is configured the transmission of all
alarms from the NE to the OT is suppressed
Alarms which are not shown via the TNMS CT are signaled on the hardware
display elements,
on each module a red fault LED indicates any internal card alarms
modules must not be removed or inserted under voltage
Module Replacement: After a new module has been plugged into the
corresponding slot of the sub rack it will go through an automatic startup
phase and the main controller downloads the configuration.

TR3271EU00TR_0302
2004 Siemens AG

75

Siemens

76

Maintenance

TR3271EU00TR_0302
2004 Siemens AG

Maintenance

Siemens

Solution 2
Title:

Engineering Order Wire (EOW)

Objectives:

The participant shall be able to:

z Set up a conference call
z break into an existing conference call
z close a conference

Pre-requisite:

Real NEs with EOW feature available and configured

Task
5. From node "Nuernberg/Mainz" establish a selective call to node
"Ulm/Essen".

Query
true

false

On node "Ulm/Essen" the conference LED is flashing

On node "Nuernberg/Mainz" the conference LED is continuously on
On node "Ulm/Essen" the ringers are activated
6. Pick up the handset at node "Ulm/Essen"

Query
true

false

On node "Ulm/Essen" the conference LED is flashing

On node "Nuernberg/Mainz" the conference LED is continuously on
On node "Ulm/Essen" the ringers are activated
7. From node "Muenchen/Dortmund" establish a selective call to node
"Ulm/Essen".

Query
true

false

It is NOT possible to call node "Ulm/Essen" because the EOW conference is busy

TR3271EU00TR_0302
2004 Siemens AG

77

Maintenance

Siemens

8. Close the conference

true

false

Before closing the conference, one participant should press the # button. This will
activate the conference for new calls.
To close the conference, one participant should press the # button.

78

TR3271EU00TR_0302
2004 Siemens AG