23948552

5 — Installation
XPIC
The MPT-HLS modules support XPIC. In configurations with XPIC, two RTs must be
connected to enable cross-polar signal cancellation.
XPIC connector port
The MPT-HLS module has a dedicated port for XPIC, as shown in Figure 5.312.
Figure 5.312 — XPIC connector port
A dedicated multi-pair RJ45 terminated cable must be used for XPIC connections. The
cable is available in three lengths, depending on usage, as listed in Table 5.94.
Table 5.94 — XPIC cables
Cable code Cable length Used for
3CC52204AA 3m Intra-rack connections on the low subrack or

between subracks
3CC52204BA 5m Intra-rack connections on the high subrack
3CC52204CA 10 m Inter-rack connections
1524 User Manual 3DB19901AEAA Edition 01

5 — Installation
Supported XPIC connections
Figure 5.313 shows the supported XPIC configurations, which are:
• Intra-rack connections between two RTs on the same sub-rack (in red)
• Intra-rack connections between two RTs on different sub-racks (in blue)
• Inter-rack connections between two RTs on different rack (in purple)
Figure 5.313 — Supported XPIC configurations
User Manual 3DB19901AEAA Edition 01 1525

5 — Installation
Low subrack intra-rack cabling considerations
For intra-rack connections for RTs on the lower subrack, the 3 m cable is always sufficient.
Route the cable from one MPT-HLS to the cable duct on the adjacent side of the rack. Pass
the cable down the duct to the bottom of the subrack, then across the base of the rack to the
duct on the other side of the rack. Route the cable upwards and extract it from the duct
adjacent to the other MPT-HLS. Any excess cable can be managed by rolling up the cable
and putting it in the free space at the base of the MPR-LH subrack.
High subrack cabling considerations
There is no free space in the upper subrack to manage excess cable. Alcatel-Lucent
recommends that you use a 5 m cable and route the cable to the cable barrel above the rack.
Route the cable from one MPT-HLS to the cable duct on the adjacent side of the rack and
pass the cable upwards towards the barrel. Pass the cable down the duct on the other side
and extract it adjacent to the other MPT-HLS.
5.1.10 — MPT-HLS installation in an LSY rack

An existing LSY system can be upgraded by addition or substitution of LSY transceivers
with MPT-HLS transceivers.
Depending on the configuration of the system to be upgraded and on the final configuration
to be achieved, different operations shall be addressed.
5.1.10.1 — LSY existing installations
LSY systems can be found installed in configurations with or without ADM (1650SMC/
1662SMC). Figure 5.314 and Figure 5.315 are representative of these two cases.

5 — Installation
Figure 5.314 — LSY system without ADM

5 — Installation
Figure 5.315 — LSY system with ADM
5.1.10.2 — Upgrade use cases
Addition, partial replacement or full replacement of the LSY transceivers with MPT-HLS
transceivers can be performed.
Looking at the existing installations described, four cases are possible:
a. Addition of MPT-HLS transceivers or partial replacement of LSY transceivers in a

system without ADM
b. Addition of MPT-HLS transceivers or partial replacement of LSY transceivers in a
system with ADM
c. Full replacement of LSY transceivers with MPT-HLS in a system without ADM
d. Full replacement of LSY transceivers with MPT-HLS in a system with ADM
The existing LSY transceiver sub-shelf and the eventual ADM will stay in place.
The changes will impact the TRU, the fan units, the Base Band. Moreover the new MPT-
HLS transceivers shall be equipped with special adapters before to insert into the sub-shelf.

5 — Installation
This section provides a short description of cases and operation to be addressed. In the
following section all operations will be detailed.
Case a: Addition of MPT-HLS transceivers or partial replacement of LSY

transceivers in a system without ADM
In case of addition or partial substitution on MPT-HL transceivers in a LSY system without

ADM, the existing Base Band sub-shelf shall be kept (to control the remaining LSY
transceivers).
The fan unit for the transceiver sub-shelf shall be replaced by the new MPT cooling system.
The MSS sub-shelf shall be added into the rack in the empty space previously reserved for
ADM.
The branching sections shall be expanded through additional circulators/filters in case of

addition of transceivers with respect to old LSY system.
The existing LSY Power distribution unit (LSY Top Rack Unit (TRU)) shall be kept and
upgraded. Two additional breakers (value 2A) for fan unit and two for MSS-8 (value 10A)
must be inserted in it.
Procedure:
1. Keep the Base band sub-shelf.

2. Replace fan unit for transceiver sub-shelf.
3. Install the MSS sub-shelf in the free room.
4. Expand the branching section (only in case of addition of channels or transceivers).
5. Keep the existing LSY TRU and upgrade it through addition of breakers for new fan
unit and MSS.

5 — Installation
Figure 5.316 — Case a
Case b: Addition of MPT-HLS transceivers or partial replacement of LSY

transceivers in a system with ADM
In case of addition or partial substitution of MPT-HLS transceivers in an LSY system with

ADM, the existing Base Band sub-shelf and the ADM sub-shelf are kept.
The fan unit for transceiver sub-shelf will be replaced by the new MPT cooling system.
In this case there will be not enough space in the rack to place the MSS sub-shelf. It must
be placed in another rack provided with the MPT TRU. This power distribution unit will
power the MSS sub-shelf and the second 4X fan unit (if present, see Cooling system (fan
module) replacement).
The existing ADM fan unit shall be kept.
When transceivers are added to the old LSY system, the branching section must be
expanded using additional circulators/filters.
The existing LSY Power distribution unit (LSY Top Rack Unit (TRU)) shall be kept. The
2A breakers for the old fan unit of transceivers sub-shelf shall be used for one 4X fan unit
of the new one.
Procedure:
1. Keep the Base band and ADM sub-shelves.


5 — Installation
3. Keep the old fan unit for ADM.

4. Install the MSS sub-shelf in another rack.
6. Keep the existing LSY TRU, use the existing breaker for fans to serve part of the new
fan unit.
7. Equip the TRU of the new rack with breakers for MSS and one 4X fan module (if the
upgraded system foresees two 4X fan module in the fan unit for transceiver).
Figure 5.317 — Case b
Case c: Full replacement of LSY transceivers with MPT-HLS in a system

without ADM
In case of full replacement of LSY transceivers with MPT-HLS in a system without ADM,
the existing Base Band sub-shelf shall be removed.
The fan unit for transceiver sub-shelf shall be replaced through the new MPT cooling
system.
The MSS sub-shelf shall be added into the rack in the space left free by the removed Base
Band sub-shelf.
The existing LSY Power distribution unit (LSY Top Rack Unit (TRU)) shall be kept. The
breakers formerly used for Base Band shall be substituted with new ones for MSS-8
powering. New additional breakers for fan unit (for one 4X fan unit) must be inserted in it.

5 — Installation
Procedure:
1. Remove the Base band sub-shelf.

3. Install the MSS sub-shelf in the room left free by the removed Base Band.
4. Expand the branching section (only in case of addition of channels/transceivers).
5. Keep the existing LSY TRU and upgrade it through addition/substitution of breakers
for new fan unit and MSS.
Figure 5.318 — Case c
Case d: Full replacement of LSY transceivers with MPT-HLS in a system

with ADM
In case of full replacement of LSY transceivers with MPT-HLS in a system with ADM, the
existing Base Band sub-shelf shall be removed.
The existing ADM sub-shelf shall be kept.
The fan unit for the transceiver sub-shelf and those for ADM shall be replaced by the new
MPT cooling system.
The MSS sub-shelf shall be added into the rack in the space left free by the removed Base
Band.

5 — Installation
The existing LSY Power distribution unit does not have enough breakers slots to serve all
the new system parts. It must be replaced with an MPT TRU.
Procedure:
1. Remove the Base band sub-shelf.

2. Replace fan unit for transceiver sub-shelf and for ADM sub-shelf.
3. Install the MSS sub-shelf in the room left free by the removed Base Band.
5. Replace the existing LSY TRU with a new MPT TRU equipped with breakers for all
system parts.
Figure 5.319 — Case d
5.1.10.3 — Common operation description

5 — Installation
Existing TRU upgrading or replacement
TRU upgrading
In the LSY system the TRU provides the power distribution to the entire system through
the breakers. Figure 5.320 shows the front view of a TRU and the positioning of breakers
for each section. The breakers that must be installed will depend on the system
configuration. Note also that the effective position of each breaker can be different from the
one reported in the picture. Check for the real usage of each breaker before initiating the
system upgrading.
Table 5.95 describes breaker utilization in the LSY TRU.
Figure 5.320 — Front view of LSY TRU
Table 5.95 — TRU breaker utilization in 9600 LSY
Breaker number Usage Current limit
1A and 1B Transceiver slot 1 to 5 20 A
2A and 2B Transceiver slot 6 to 10 20 A
3A and 3B Base Band subrack 10 A
4A and 4B ADM 4A
5A and 5B Fan unit for BB subrack 2A
6A and 6B Fan unit for ADM 2A
Depending on system deployment period, the TRU can be found in the following versions:
• 3DB05602AA – most recent version of TRU

• 3DB00734AA – previous version of TRU
The breakers to be used with the two TRUs are different: Table 5.96 provides the codes.

5 — Installation
Table 5.96 — Breakers for TRU
Breaker value Part number
Breakers for 3DB056024AA
2A 1AB162710010
10A 1AB162710011
20A 1AB162710013
Breakers for 3DB00734AA
2A 1AB162710002
10A 1AB162710005
20A 1AB162710007
The two versions also differ in the way to plug the cables into the breaker holder. With the
most recent version (3DB05602AA) the cable requires crimp contacts for the connection;
see Figure 5.321.
Figure 5.321 — Connection of supply cables to the breaker holder bar for
3DB05602AA TRU
In the old version of the TRU (3DB00734AA) the cables are plugged to the breaker holder
bar without crimp contacts; see Figure 5.322.

5 — Installation
Figure 5.322 — Connection of supply cables to the breaker holder bar for
3DB00734AA TRU
In case of TRU upgrading additional breakers shall be added or changed. See Upgrade use
cases for specific operation case by case.
Figure 5.323 shows a breaker for the LSY TRU. To insert a breaker, position it and push it
into its slot; see Figure 5.324.
Figure 5.323 — Breaker for LSY TRU
Figure 5.324 — Breaker insertion in LSY TRU

5 — Installation
To extract a breaker, pull it. To facilitate this operation, two tool-screws have been put in
the TRU. Screw the tools to the breaker (on the top and bottom treaded holes as indicated
in Figure 5.325) and pull it down.
Figure 5.325 — Use of tool-screw for breaker extraction
Note on cabling for system upgrading:
The already installed supply cables of the system functions that will be kept will not be
changed. For the new functions to be installed (Fan units and MSS-8) new supply cables
will be provided as part of the material for the system upgrading.
Table 5.97 — Supply cords for system upgrading
Supply cable for system upgrading Part number
2x1 mm2 power cord for Fan unit 3CC52208AAAA
2x6 mm2 power cord for MSS-8 3CC52209AAAA
These new cables include the crimp connectors to be used with the 3DB05602AA version
of the TRU.
Figure 5.326 shows the routing of the MSS-8 and fan unit cable.

5 — Installation
Figure 5.326 — Supply cords for fan unit and MSS-8 pre-assembled with crimp
connectors and plug-in to terminals
In case of system upgrading with a 3DB00734AA TRU, the end of the cords terminated
with the crimp connectors must be cut and the cable ends have to be peeled (15mm) for the
connection on the breaker holder bar terminals as shown in Figure 5.322.
TRU replacement
In case of TRU replacement (case d in Upgrade use cases) the existing LSY TRU must be
completely removed.
Unplug all the cables arriving to it and dismount the unit.
Assemble the new unit (MPT TRU, 3CC50156AA). The procedures to be followed are the
same as those described in Installation of the 20-slot TRU.
5.1.10.4 — Cooling system (fan module) replacement
The use of MPT-HLS transceivers on a LSY system requires an upgrade of the cooling
system.
An LSY system is always equipped with a fan unit right below the Base Band section (fan
unit for transceiver sub-shelf). Another fan unit (fan unit for ADM) placed right below the
ADM section, is installed only in case of systems equipped with ADM.
In case of system upgrading, the fan unit for transceiver sub-shelf must always be replaced.
The fan unit for ADM will be replaced only in case of full replacement of LSY transceivers
in a system equipped with ADM (case d)).
The cooling system to be used for replacement will be the one used in standard MPT-HLS
systems. It consists of a support containing one or two 4X fan modules, as shown in
Figure 5.327.

5 — Installation
Figure 5.327 — Two 4x fan modules in the fan support
One or two 4X fan modules shall be used for cooling the transceivers sub-shelf.
As a general rule: up to five transceivers in an homopolar configuration can be cooled by a

single 4X fan module. More than five transceivers in homopolar configuration and all
heteropolar configurations need two 4X fan modules.
Only a 4X fan module is required to cool the ADM section (case d)).
In a LSY system the alarms of the fan units are managed by the base band section through
a CAN-BUS connection. This connection must be reconfigured once the cooling system is
changed.
The main operations to be followed for cooling system replacement are described in the
following sections.
Fan unit for transceiver sub-shelf replacement
Procedure:
1. Shut down the fan module acting on the two breakers (battery A and B) on the TRU.
2. Remove the RX branching cover from the rack by unscrewing the four screws; see
Figure 5.328.
Note: Do not remove the nuts from the rack. They can be used for the placement of the
new RX branching cover; see Powering of new fan units.

5 — Installation
Figure 5.328 — Remove Rx branching cover
3. Unplug the two supply cables and the two CAN-BUS cables.
Note: The CAN-BUS connector 2 is closed with a CAN-BUS terminator when the ADM is not
installed in the system. This terminator shall be used to terminate the CAN-BUS control
in the Base Band in configurations where it shall be kept (case b) (see CAN-BUS
reconfiguration after fan unit replacement) so it must be kept for this purpose.
Figure 5.329 — Supply cables and CAN-BUS connectors

5 — Installation
Figure 5.330 — Supply cables and CAN-BUS connectors unplugged
4. Remove the fan unit by unscrewing the four screws fixing it to the rack, see
Figure 5.331.
Figure 5.331 — Remove the fan unit
5. If the Base Band section needs to be kept (cases a and b) carefully remove the dust that
is accumulated into the grid placed in the bottom side of the Base Band sub-shelf, see
Figure 5.332.
Figure 5.332 — Bottom side of base band shelf before and after dust removal
6. The supply and CAN-BUS cables will not be used anymore in the upgraded system so
they can be removed from the rack.

5 — Installation
7. Place the new fan support in the same position of the old one. To do it, use the same
nuts on the rack that were used for the old fan unit.
IMPORTANT NOTICE: Prior to placing the fan support:
• The shock absorber rubber band must be placed on the back. Remove the protective
band from the adhesive tape of the shock absorber and stick it to the internal side
of the back cover of the rack. The position of the shock absorber band has to be in
the middle of the two nuts for the fan support fixation, see Figure 5.333.
Figure 5.333 — Shock absorbing rubber band
• In configurations where the Base band shelf will stay in place (case a and b) the
gasket 3DB80783AAAA must be applied (this item is contained into the
3DB80781AAAA Kit of cover branching) :Remove the protective band on the
gasket adhesive and stick it in the bottom side of the Base Band sub-shelf as
indicated in Figure 5.334.
Figure 5.334 — Placement of the 3DB80783AAAA gasket

5 — Installation
Fan unit for ADM sub-shelf replacement
In case of full replacement of LSY transceivers with MPT-HLS in a system with ADM
(case d) the fan unit of ADM must be replaced by a new MPT-HLS fan unit. Only one 4X
fan module on the fan support will be used in this case.
Procedure:
1. Shut down the fan module acting on the two breakers (battery A and B) on the TRU.
2. Unplug the two supply cables the CAN-BUS cable.
3. Unscrew and remove the fan unit.
4. The supply and CAN-BUS cables will not be used anymore in the upgraded system so
they can be removed from the rack.
5. Remove dust from the bottom of ADM sub-shelf if needed.
6. Place the new fan support in the same position of the old one. To do it, use the same
nuts on the rack that were used for the old fan unit.
Powering of new fan units
Once mounted on the system the new fan units must be powered.
Use the 3CC52208AAAA pre-assembled Fan unit power cord for the purpose. This cable
has one end terminated with special crimp connectors for the connections on the TRU
terminals. The other end is free and must be terminated with the connector for the plug-in
to the 4X fan unit. The procedures to be followed are the same as those described in
Connecting and routing power supply cables for the fan module.
Pass the cables on the duct (left side or right side depending on 4Xfan module position) and
drive them towards the top of the rack as shown in Figure 5.335.
Figure 5.335 — Routing of supply cables for fans
Pass the cables from the backside into the TRU and connect to the terminal corresponding
to the breaker.

5 — Installation
In case of only one 4X fan unit installed for the transceiver sub-shelf, the already existing
2A breaker (used for the old fan unit) shall be used. In case of two 4X fan unit an additional
2A breaker must be inserted in the TRU (see Upgrade use cases).
CAN-BUS reconfiguration after fan unit replacement
In an LSY system the alarms of the fan units are managed by the base band section through
a CAN-BUS connection. The following pictures show the connection scheme in case of
systems with or without ADM:
Figure 5.336 — CAN-BUS connection scheme for LSY systems without ADM
Figure 5.337 — CAN-BUS connection scheme for LSY systems with ADM
In upgrading systems without ADM in which the Base Band is kept (case a) the CAN BUS
connection must be removed but the connector on the Base Band must be terminated. Use
the CAN BUS terminator that was in the old transceivers fan unit for the purpose, as shown
in Figure 5.338.

5 — Installation
Figure 5.338 — CAN-BUS terminator for case a
In upgrading systems with ADM in which the Base Band is kept (case b) the CAN BUS
connection scheme must be changed as shown in Figure 5.339.
Figure 5.339 — CAN-BUS terminator for case b
Alarm management for replaced fan units
Alarms for the new MPT-HL fan units for the transceiver sub-shelf shall be managed
through the new MPT-HLS transceivers. The Fan management section provides all details
for these connections.
The alarm management of the new fan unit for ADM (case d in Upgrade use cases) will be
performed by MSS housekeeping (AUX board in MSS-8).
5.1.10.5 — Upgrading of the transceivers sub-shelf
In an LSY system upgrade, the operations related to the transceiver sub-shelf mainly
consist of the following:
• preparation of the slots for the insertion of new MPT-HL transceivers

• adaptation of the transceivers
• insertion and connection of the new transceivers.

5 — Installation
No changes to powering of the transceiver sub-shelf are needed. The 20A breakers already
present in the TRU do not need to be changed.
Preparation of the slots
The unused positions in a LSY transceiver sub-shelf are closed with covers in the front and
top of each slot.
To enable a slot for an additional transceiver the covers must be removed, as shown in
Figure 5.340.
Figure 5.340 — Removal of front and top cover to enable a new slot on the sub-shelf
Preparation of the MPT-HLS transceiver and insertion into the sub-shelf
Different dimensions of the MPT-HL transceivers with respect to the LSY ones impose the
addition of mechanical and electrical adapters in the transceiver body.
The kit 3DB80504AAAA contains all required adapters. It consists of three adapters: one
to be put on the top, another on the bottom and the last on the back of the transceiver.
Figure 5.341 shows the positioning of the three adapters.

5 — Installation
Figure 5.341 — Placement of MPT-HLS transceiver adapters
The adapters must be screwed to the transceiver main body using Philips M2.5 screws
(included in the kit). Use a tightening torque of 0.53 Nm.
The new transceiver can be now inserted into the sub-shelf. Align it to the slot rails and push
to connect the backside supply connectors. Block the transceiver with the two screws in the
top and bottom position, as shown in Figure 5.342.

5 — Installation
Figure 5.342 — MPT-HLS transceivers in the LSY sub-shelf with details of the blocking
screws
RF connections of the MPT-HLS transceiver in a LSY sub-shelf and

branching cover placement
Once inserted into the sub-shelf the MPT-HLS transceiver RF connection to and from
branching filters must be completed.
The position of RF IN (RX or RX DIV) and OUT (TX) connector is different in a MPT-
HLS transceiver with respect to an LSY one. The RF cables needed are provided in kits
which will always contain one cable for TX, one for RX, and one for RX DIV. In a system
without a diversity receiver the RX DIV cable is not required.
Table 5.98 provides the kit references and the cable usage.

5 — Installation
Table 5.98 — RF cables reference table for MPT-HLS transceivers in an LSY rack
System frequency Kit reference Content Cable reference Usage

range
6L,6U,7,8GHz 3DB80543AAAA 2x 230mm RF cable 3DB80693AAAA TX and RX DIV

M90/M90
1x250mm RF cable 3DB80693AAAA RX

M90/M90
10, 11, 13GHz 3DB80797AAAA 2x 280mm RF cable 3DB80748AAAA TX and RX

M90/M90
1x280mm RF cable 3DB80748AAAA RX DIV

M90/M
Figure 5.343 shows the RF connections between the TX/RX connectors and branching
filters.
Figure 5.343 — RF connections for new MPT-HL transceivers in a LSY sub-shelf
After the RF connections for all new transceivers are completed, the new RX branching
cover must be mounted in the rack.
The cover branching kit 3DB80781AAAA contains the cover. The screws and nuts to be
used for rack fixation are also included.

5 — Installation
The new cover must be placed in the same position as the old one removed during fan unit
replacement, as shown in Figure 5.344 (see Fan unit for transceiver sub-shelf replacement).
The nuts already present in the rack can be used.
Figure 5.344 — New RX branching cover placement
Note: The 3DB80781AAAA kit contains the 3DB80783AAAA gasket to be used in between
new fan unit and Base Band.
5.1.10.6 — Branching section expansion

5 — Installation
In case of addition of new transceivers with respect to the old installation the branching
section must be upgraded through the addition of the TX/RX/(RX DIV) circulators and
filters relative to the new channels to be introduced.
The branching expansion procedure is the same as described for standard MPT-HLS
systems. See Branching expansion.
5.1.10.7 — Positioning and powering of the MSS-8 sub-shelf
The positioning of the MSS-8 sub-shelf in case of LSY system upgrading will depend on
the existing system to be upgraded and on the final configuration to be achieved (see
Upgrade use cases).
Specific positions on the rack have to be used depending on the case.
Assembly note: placement/adaptation of MSS sub-rack into the LSY 21" rack is achieved
using brackets (3DB18181AAAB for MSS-8). The brackets must be mounted on the MSS-
8 sub-shelf prior to mounting it on the system rack.
Placement of MSS-8 in systems without ADM that will maintain the Base
Band sub-shelf (case a)
The MSS-8 sub-shelf will be placed in the empty space previously reserved for ADM; see
Figure 5.345.
Figure 5.345 — Placement of MSS-8 in the ADM reserved empty space

5 — Installation
Holes number 14 and 16 on the rack must be used to place the nuts and screws of the
brackets.
Placement of MSS-8 in systems where Base Band is removed (case c

and d)
The MSS-8 sub-shelf will be placed in the space left free after the Base Band removal, as
shown in Figure 5.346.
Figure 5.346 — Placement of MSS-8 in the space left by Base Band removal
Holes number 31 and 33 on the rack must be used to place the nuts and screws of the
brackets.
Powering of MSS-8 sub-shelf
Two cords (3CC52209AAAA) must be used for the supply connections of the MSS-8 sub-
shelf.
The cable is terminated at one end with the connector for the MSS-8. The other end is
terminated with the special crimp connector for the connection to the 3DB05602AA LSY
TRU terminals. If another TRU is used, the crimp connectors must be removed by cutting
the wires.

5 — Installation
Insert the cables in the duct (left side) and drive them toward the top of the rack. Pass the
cables from the backside into the TRU and connect to the terminal corresponding to the
breakers (value 10A).
5.1.11 — MPT-HLS system expansion

An MPT-HLS system can be upgraded in field by adding channels (system expansion).
This operation involves the following system components:
• RT sub-rack: enabling the slots for new transceivers

• branching section: addition of filters and/or circulators for the new channels (branching
expansion)
The cooling system and the TRU section will be impacted too if, after system expansion,
the overall number of transceivers will be more than five.
The following sections detail the instructions to be followed in each part of the system.
5.1.11.1 — Preparation of the system for expansion
In principle, operations related to expansion do not require complete shut-down of the

system. However, synch-loss of working channels in a system not ready for expansion must
be considered during operations on RX branching sections.
To make operations on the RT sub-rack and on the RX branching section possible, the RX
branching front cover must be removed: unscrew the four screws fixing the cover to the
rack. See Figure 5.347.
Figure 5.347 — Remove RX branching cover

5 — Installation
Remember to re-mount the front cover in its position after the system expansion procedures
are concluded. The front cover permits the correct air flow for the system cooling.
5.1.11.2 — RT sub-rack operations for system expansion
In an already-installed system the transceivers are placed in the RT sub-rack. In case of

system expansion, new transceivers are placed in the free slots. The operations to be
performed are upgrading of the supply distribution back panel of the rack and enabling of
the new slots.
Back panel upgrading
The supply distribution on the RT sub-rack is performed by one or two back-panels, as

shown in Figure 5.348. Each back-panel serves up to five RTs.
Figure 5.348 — Systems with one or two back panels mounted
In case of expansion beyond the fifth channel in a system not ready for expansion, the
second back panel must be mounted and the supply cables from TRU must be routed.
Note: The dummy plates must be removed from the unused slots to permit mounting of
the new back-panel. See the next section for more information.
Procedure:
1. Use the back-panel contained into the 3DB80268AA kit (it is already complete with the
labels and protection caps)
2. Make sure that the yellow protection caps are in place covering the terminals of supply
connectors. If not put them in the correct position as shown in Figure 5.349.

5 — Installation
Figure 5.349 — Yellow protection caps
3. Mount the back plane on the metallic support bar by attaching it with the six screws, as
shown in Figure 5.350.
Figure 5.350 — Mount the back plane on the support bar
4. Two 6mm2 zip power cables (1AC007800069) must be used to connect the TRU to the
back panel for power. Plug the cables into the two green connectors of the back panel:
the connectors are already plugged to the back panel. Follow the procedure described
in MPR-LH subrack installation.
5. Drive the two cables inside the rack towards the top, as shown in Figure 5.351, and
finally towards the TRU for the breakers plugging, see TRU upgrading.

5 — Installation
Figure 5.351 — Cables inside the rack
Enabling new slots on the RT sub-rack
The free slots are not enabled by default for new transceivers. They are closed by plastic
dummy plates in the front and top sides, as shown in Figure 5.352.
Figure 5.352 — RT subrack with dummy plates
Perform the following procedure to enable a slot for a new transceiver:

5 — Installation
1. Remove the front dummy plates of the slot to be enabled and of the adjacent one. Apply
slight pressure with a finger tip to disengage the two plastic teeth from the bottom
metallic bar. Pull backward and lift upward to completely remove the plate, as shown
in Figure 5.353.
Figure 5.353 — Front dummy plate removal
2. Remove the top dummy plates of the slot to be enabled and of the adjacent one. Apply
slight pressure with a finger tip to disengage the two plastic teeth from the top metallic
bar. Pull upwards to lift and remove the plate, as shown in Figure 5.354.
Figure 5.354 — Top dummy plate removal
3. A septum plate will be present next to the last transceiver installed: remove it by
unscrewing the two fixation screws to the top and bottom metallic bars; see
Figure 5.355.

5 — Installation
Figure 5.355 — Septum plate to be removed
4. Place the top (3DB80216AAAA) and bottom (3DB80217AAAA) support guides as

indicated in Figure 5.356 and Figure 5.357.
Note: The top and bottom support guides and fixation screws are contained in the
3DB80227AA kit (sub-rack extension kit for one RT).

5 — Installation
Figure 5.356 — Bottom support guide placement

5 — Installation
Figure 5.357 — Top support guide placement
5. Screw the two centering pins on the back panel on the position corresponding to the
supply connector to be used for the new slot to be enabled; see Figure 5.358.
Figure 5.358 — Centering pin placement on back panel

5 — Installation
Note: The top and bottom support guides and fixation screws are contained in the
3DB80227AA kit (sub-rack extension kit for one RT).
6. Remove the protection caps from the two supply connectors corresponding to the new
slot on the back plane, as shown in Figure 5.359.
Figure 5.359 — Protection cap removal
7. Mount the septum plate in the position beside the new enabled slot. Enter the two
extrusions on the back of the plate in the corresponding holes on the rear top and bottom
metallic bars of the sub-rack. Fix it with the screws to the top and bottom front bars of
the sub-rack, as shown in Figure 5.359.

5 — Installation
Figure 5.360 — Remount the septum plate
8. Mount the top and frontal dummy plastic plates in the position adjacent to the newly
enabled slot.
A new slot is now enabled.
Figure 5.361 — RT sub-rack before and after new slot enabled
A new transceiver can be put in. If the branching section is already set for the new channel
the RF and high level connections for the new transceivers can be set up. Follow the
instructions in MPT-HLS Module installation.
5.1.11.3 — Branching expansion

5 — Installation
The RF branching sections in an MPT-HLS system are the set of circulators and filters in
the TX, RX and RX diversity pipe that are needed to discriminate the RF channels.
Their position in a rack is indicated in Figure 3.18. As illustrated in the figure, in an

operating system the RX and RX diversity branching sections are behind the RX branching
cover. Any operation on these sections will require the removal of this cover. Remember to
place it again after operations are completed.
The branching expansion procedure details how to enable the branching section to support
new channel frequencies in case of system expansion. This section deals of the addition of
filters or circulators/filters to an existing TX, RX and eventually RX diversity set. If not
differently indicated, the information in this section applies to MPT-HLS systems working
at the following frequencies:
• 6L
• 6U
• 7 GHz
• 8 GHz
• 10 GHz
• 11 GHz
• 13 GHz
Note that the branching expansion procedure is the same for the LSY system upgrading
with MPT-HLS transceivers. The instructions reported in this section apply to LSY systems
working at the frequencies reported in Table 5.99.
Table 5.99 — LSY system upgrading - frequency list for branching expansion
System 6L 6U 7 GHz 8 GHz 10 GHz 11 GHz 13 GHz

frequency
System 9662 9667 9674 9681 9610 9611 9613

identification LSY LSY LSY LSY LSY LSY LSY
Use cases
An MPT-HLS system (or LSY system) can be found in the field in the following settings:
• System ready for expansion: the branching section is equipped with a set of circulators
and filters for the existing channels plus a set of extra circulators intended to be used
for future expansion. For the branching expansion in this case only the addition of the
filters is needed (TX, RX and eventually diversity), at the right frequency for the new
channels. Figure 5.362 shows a system that is ready for expansion. One channel is
working; three circulators are ready to be completed with filters for expansion.

5 — Installation
Figure 5.362 — Detail of a branching section in a system ready for expansion
• System not ready for expansion: the branching section is equipped only with the set of
circulators and filters for the existing channels. The branching expansion in this case is
obtained by adding the circulators and filters (TX, RX and eventually diversity) at the
right frequency for the new channels. Figure 5.362 shows a system that is not ready for
expansion. Three channels are working; new circulators must be mounted for any
additional channels.
Figure 5.363 — Detail of a branching section in a system not ready for expansion
Operational note:
Regardless of the system frequency, the screws used for branching upgrading must be
M4 or M3. Use the torque forces reported in Table 5.100 during tightening operations.
Table 5.100 — Torque forces for screws used in the branching sections
Screw type Torque (Nm)
M4 2.1

5 — Installation
Table 5.100 — (Continued)Torque forces for screws used in the branching sections
Screw type Torque (Nm)
M3 0.9
Branching upgrade in a system ready for expansion
In a system ready for expansion the branching sections (TX, RX and eventually RX
diversity) are already equipped with extra circulators. These circulators are not in use; they
are ready for the addition of the RF filters serving the new channels.
The front side of unused circulators is covered by a metallic plate fixed by four screws.
Figure 5.364 shows the TX and RX branching sections for a system ready for expansion
(up to four channels). The details A and B show the metallic plate closing the unused
circulators.
Figure 5.364 — TX and RX branching sections in a system ready for expansion
To add a channel to the branching:
1. Remove the metallic plate of the not used circulator next to the last used one in the TX
section, as shown in Figure 5.365.

5 — Installation
Figure 5.365 — Remove the metallic plate
2. Mount the filter corresponding to the new TX frequency.

3. Repeat the same operation on the next circulator in case of more than one channel
expansion, as shown in Figure 5.366.
Figure 5.366 — Repeat on the next circulator
4. Perform the same operation in the RX (and eventually in the RX Div) branching
section. Figure 5.366 shows a completed example.

5 — Installation
Figure 5.367 — Example of a system branching (TX, RX and RX diversity) expanded to

five channels
Note: Each RF filter is tuned on its channel frequency reported on it with a label. Make
sure to place it on the right Transceiver Channel /Circulator position.
M4x10 screws are used to fix the filters to the circulators. Use the torque force reported
in tab.3 during tightening.
Branching upgrade in a system not ready for expansion
In a system not ready for expansion no extra circulators are included in the existing
branching sections. New circulators and filters must be added for system expansion.
The following cases can be encountered:
• Branching expansion from two to ten new channels for system in homopolar
configuration and from two to four channels in heteropolar systems
• Branching expansion for the fifth channel for systems in heteropolar configuration

5 — Installation
These cases shall be treated separately for the Tx and Rx and Rx Div branching sections.
Tx branching expansion for homopolar systems or up to four channels in a

heteropolar system
Perform the following procedure:
1. Remove the last circulator termination, see Figure 5.368.
Figure 5.368 — Remove the circulator termination
2. Assemble the new expansion circulators to the last circulator of the existing set, see
Figure 5.369. Use the M4x12 screws plus nuts contained in the kits provided for
expansion (see Table 5.104 for the kit list). Use the torque force reported in Table 5.100
during tightening.
Figure 5.369 — Assemble the new expansion circulator
3. Assemble the channel filters; see Figure 5.370. Use M4x10 screws contained in the
provided kit for expansion. Use the torque force reported in tab.3 during tightening.

5 — Installation
Figure 5.370 — Assemble the channel filters
Note: Each RF filter is tuned to the channel frequency reported on its label; make sure
to place it on the correct transceiver channel or circulator.
4. Mount the second branching support bracket; see Figure 5.371. The first support
bracket is always used: it is attached to the first isolator. The second bracket shall be
used only if three or more isolators will be present. It must be fixed to the last odd
isolator installed. Note that in an installed system the second bracket is already present
even if not used. In this case it is fixed in a neutral place on the back support bar.

5 — Installation
Figure 5.371 — Mount the second branching support bracket
Tx branching expansion for the fifth channel in heteropolar systems
The information in this section is valid for systems working at the frequency 6L, 6U, 7,
8GHz. For systems working at 10, 11 or 13GHz the fifth channel expansion is performed
according to the procedure in Tx branching expansion for homopolar systems or up to four
channels in a heteropolar system.
In heteropolar systems up to five channels in one polarization can be placed in the left side
of the sub-rack. The corresponding channels in the other polarization shall be placed in the
right side. This is valid for the upper sub-rack. In case of heteropolar system equipped with
the lower sub-rack the channel polarizations are reversed.
Figure 5.372 shows the TX branching section with four channels per polarization in a
heteropolar system.
Figure 5.372 — Four channels Tx heteropolar branching

5 — Installation
To avoid mechanical interference when adding the fifth channel the new circulator (for both
polarizations) must be mounted rotated 90° with respect to the others.
Procedure:
1. Remove the fourth circulators terminations; see Figure 5.373.
Figure 5.373 — Remove the fourth circulator terminations
2. Mount the fifth circulators: the left rotated 90° clockwise (see Figure 5.374) and the
one on the right rotated 90° counter clockwise (see Figure 5.375).
Note: Mount the termination on the free port prior to mount the isolators.

5 — Installation
Figure 5.374 — Left circulator
Figure 5.375 — Right circulator
3. Assemble the fifth channel filters.

4. The second support bracket must be placed in the third circulator.

5 — Installation
Rx and Rx Diversity branching expansion for homopolar systems or up to four

channels in a heteropolar system
Aside from the addition of new circulators/filters, the Rx and Rx Diversity branching
expansion also requires the addition or changing of a waveguide stub needed for a
mechanical adaptation. Figure 5.376 shows an Rx branching with two and three channels
and the changing of the waveguide stub.
Figure 5.376 — Rx branching with two and three channels
The same situation is faced for the expansion of the Rx div branching section and the
waveguide stubs to be used are the same.
Waveguide stubs are frequency-dependent. They are available for any expansion need and
the reference codes are reported in Table 5.101 and Table 5.102.
Table 5.101 — Waveguide stubs for 6L, 6U, 7, 8 GHz systems
Configuration Part number
2nd channel 3DB02412AA
3rd channel 3DB02413AA
4th channel 3DB02414AA

5 — Installation
Table 5.101 — Waveguide stubs for 6L, 6U, 7, 8 GHz systems (Continued)
Table 5.102 — Waveguide stubs for 10, 11, 13 GHz systems
2nd channel 3DB03890AA
3rd channel 3DB03891AA
Sequence of operations for Rx (and eventually the Rx Div.) branching expansion

1. Remove the existing waveguide stub and the U-shaped waveguide section by
unscrewing these parts from the lateral waveguide and from the last circulator.

5 — Installation
Figure 5.377 — Screws to be removed
2. Add the circulators for expansion to the last circulator of the existing set.
3. Mount the second branching support bracket. Follow the rules described in Tx
branching expansion for homopolar systems or up to four channels in a heteropolar
system.
4. Separate the U-shaped waveguide from the old waveguide stub and replace it with the
new one. The new waveguide must be consistent with the total number of channels
after expansion; see Table 5.101 and Table 5.102.
5. Assemble the U-shaped waveguide plus stub to the lateral waveguide and to the last
circulator of the new set.
6. Assemble the new Rx (Rx div) channel filters.

5 — Installation
Figure 5.378 — Expansion of RX and RX div branching from two to three channels in an homopolar
system
Rx and Rx diversity branching expansion for the fifth channel in heteropolar

systems
The information in this section is valid for systems working at the frequency 6L, 6U, 7,
8GHz. For systems working at 10, 11 or 13GHz the fifth channel expansion is performed
according to the procedure in Rx and Rx Diversity branching expansion for homopolar
systems or up to four channels in a heteropolar system.
To avoid mechanical interference when adding the fifth channel the new circulator (for both
polarizations) must be mounted rotated 90° with respect to the others. To match with the
positioning of the waveguide pipes the existing waveguide stub shall be substituted with S-
shaped ones. This is illustrated by Figure 5.379.
Figure 5.379 — Fifth channel expansion
In some cases the fixation position of the circulators to the support brackets must be
changed as part of expanding the branching to the fifth channel (see Figure 5.380). The
operation will result in a movement towards the front of the entire set of circulators/filters:
use the back holes on the circulator body to fix the bracket.

5 — Installation
Figure 5.380 — Change of position of the bracket fixation points
The operation described above must be executed in the following cases:
a. On Rx Diversity branching only in case of expansion to the 5th channel for heteropolar
systems with one sub-rack
b. On Rx and Rx Diversity in case of expansion to the 5th channel for heteropolar systems
with two sub-racks (four polarizations)
Sequence of operation for Rx and Rx diversity branching expansion for the fifth
channel in heteropolar systems
1. Remove the existing waveguide stub and the U-shaped section by unscrewing the these
parts from the lateral waveguide and from the last circulator.

5 — Installation
Figure 5.381 — Remove the existing waveguide stub
2. In case of need change the position of the brackets fixations points of the isolators (see
description in the previous step).
3. Add the circulators for expansion to the last circulator of the existing set. Take care to
mount the fifth circulator rotated 90° clockwise for the left side of the branching and
counter clockwise for the right side.
4. Separate the U-shaped waveguide from the old stub and replace it with the new S-
shaped waveguide as in Figure 5.382.
Figure 5.382 — S-shaped waveguide
Depending on the system configuration (one or two RT sub-rack) and on the Rx or Rx

Diversity sections, different S-shaped waveguides have to be used. Table 5.103 reports
the item identification and the use case for 6L, 6U, 7 and 8GHz system frequencies.
Table 5.103 — Waveguide bendings (S-Shaped) for 6L, 6U, 7, 8GHz branching
expansion
3DB80389AAAA Rx branching in heteropolar systems with

one sub-rack only

5 — Installation
Table 5.103 — Waveguide bendings (S-Shaped) for 6L, 6U, 7, 8GHz

branching expansion (Continued)
3DB80388AAAA • Rx Div. Branching in heteropolar

systems with one sub-rack only
• Rx and Rx Div. Branching in
heteropolar systems with two sub-
racks (four polarizations)
These parts are included in the expansion kits; see Table 5.104.
5. Assemble the U-shaped waveguide plus the S-shaped one in between the 5th
circulators and the lateral waveguides
6. Assemble the new Rx or Rx div channel filters; see Figure 5.383.
Figure 5.383 — Assemble the new Rx (Rx div) channel filters
5.1.11.4 — Cooling system upgrading
On homopolar systems with up to five transceivers per sub-rack the cooling system presents
only one 4xfan module per sub-rack; see Fan configurations and cabling. If after system
expansion the overall number of transceivers per sub-rack exceeds five, the second 4xfan
module must be added in the fan support tray. Follow the instructions for Fan installation
procedures.

5 — Installation
5.1.11.5 — TRU upgrading
Two 2A breakers (Batt. A and Batt.B) per sub-rack must be added to the existing TRU for
cooling system upgrading (see Cooling system upgrading).
If a system expansion involves the placement of the second back-panel (see Back panel
upgrading) two 2A breakers (Batt.A and Batt.B) must be added to the existing TRU.
See Installation of the 20-slot TRU for installation information.
5.1.11.6 — Available kits for system expansion
A set of kits is available to cover all the foreseen system expansion needs. Table 5.104
provides a description of available codes.
Table 5.104 — List of extension kits
Identification code Description System frequency Configuration
3DB80268AA Back panel kit 6L to 13GHz All
3DB80227AA Sub-rack extension 6L to 13GHz All

kit for one RT
3DB80414AB One channel 6L to 8GHz Homopolar systems

extension kit (Tx and heteropolar
and Rx) systems with one
sub-rack
3DB80414AB One channel 6L to 8GHz Homopolar systems

extension kit (Rx and heteropolar
Div) systems with one
sub-rack
3DB80617AA One channel 10 to 13GHz All

extension kit (Tx
and Rx)
3DB80618AA One channel 10 to 13GHz All

extension kit (Rx
Div)
3DB80417AB 5th channel 6L to 8GHz Homopolar systems

extension kit Tx and heteropolar
and Rx systems with one
sub-rack

5 — Installation
Table 5.104 — List of extension kits (Continued)
Identification code Description System frequency Configuration
3DB80419AB 5th channel 6L to 8GHz Homopolar systems

extension kit Rx Div and heteropolar
systems with one
sub-rack
3DB80421AA One channel 6L to 8GHz Heteropolar

extension kit (Tx systems with two
and Rx) sub-rack (four
polarizations)
3DB80422AA One channel 6L to 8GHz Heteropolar

extension kit (Rx systems with two
Div) sub-rack (four
polarizations)
3DB80423AB 5th channel 6L to 8GHz Heteropolar

extension kit (Tx systems with two
and Rx) sub-racks
3DB80424AB 5th channel 6L to 8GHz Heteropolar

extension kit (Rx systems with two
Div) sub-racks
5.1.12 — Antenna Alignment

This section includes:
• Preparation
• Signal Measurement
• Aligning the Antenna
• Main Beams and Side Lobes
5.1.12.1 — Preparation
Warning: To make sure of the continuity and avoid short circuit, all cables / connectors
connections (such as RJ45, Coaxial, Ethernet, or Optical Fiber) made on the field have to
be verified and checked with Cable tester. The waterproofness must also be checked.
Before aligning antennas ensure:

5 — Installation
• The radios are powered up at both ends of the link.

• Transmit and receive frequencies are correctly set.
• Transmit powers are correctly set and transmit mute is turned off.
Note: If frequency and/or power settings are not correct for the application,
interference may be caused to other links in the same geographical area.
5.1.12.2 — Signal Measurement
Two receive signal-strength indicators are provided to assist antenna alignment, RSL in the
WebEML Performance screen, and the RSSI voltage at the connectors: a BNC connector
on the ODU300, LEMO connector on the MPT-HC/MPT-XP/MPT-MC and RJ45
Connector on the MPT-HL transceiver. See:
• Using RSL Data

• Using the RSSI Voltage at the ODU300
• Using the RSSI Voltage at the MPT-HC/MPT-XP/MPT-MC
• Using the RSSI voltage at the MPT-HLS
• RSL Measurement Guidelines
Using RSL Data
As WebEML is accessed via connection to the MSS, a separate means of communication

such as two-way radio or cell phone is required between the WebEML operator and the
person at the antenna.
To align using RSL:
1. Monitor RSL in the WebEML Performance screen.

2. Set antenna alignment for maximum RSL.
3. Repeat for the far end of the link.
4. Compare actual RSLs with the expected RSLs from the link installation datapack. For
MPT-HC/MC/XP systems, the RSL measurement accuracies are:
a. ± 2 dB for levels -40 to -70 dBm, over a temperature range of 0 to +35°C.
b. ±4 dB for levels -25 to -85 dBm, over an extended -33 to +55°C range.
For MPT-HL systems the measurements’ accuracies are:
a. ±5 db for levels -102 to – 90 dBm
b. ±3 db for levels –90 to – 85 dBm

5 — Installation
c. ±2 db for levels –85 to – 35 dBm

d. ±3 db for levels –35 to – 20 dBm
The accuracy ranges are valid over the operative temperature range of the equipment.
Using the RSSI Voltage at the ODU300
A voltmeter, such as a multimeter, is used to measure RSSI voltage at the BNC connector
on the ODU. A suitable BNC to banana-plug connecting cable is available as an optional
ODU accessory.
1. Connect the voltmeter to the BNC connector. Center pin is positive. Use a low voltage
range for best resolution, nominally 2.5 Vdc FSD.
2. Adjust antenna alignment until the voltmeter reading is at minimum value.
Check and record the peak voltage at each end. The RSSI voltage provides a direct
relationship with RSL, as follows:
Table 5.105 — Typical RSSI voltage levels with RSL for ODU300
Units Measurement (with ODU300)
BNC (Vdc) 0.25 0.5 0.75 1.0 1.25 1.5 1.75 2.0 2.25 2.5
RSL (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100
1. Compare actual RSLs to the expected RSLs from the link installation datapack. Refer
to RSL Measurement Guidelines.
2. Replace the BNC weatherproofing.
Note: Failure to replace the RSSI BNC weatherproof cap may result in damage to the
ODU.
Using the RSSI Voltage at the MPT-HC/MPT-XP/MPT-MC
A voltmeter, such as a multimeter, is used to measure RSSI voltage.
Use the MPT Service Cord for the power monitoring in addition to a voltmeter.
1. Connect a voltmeter to the MPT-HC/MPT-XP/MPT-MC through the MPT Service

Cord.

5 — Installation
2. Adjust antenna alignment until the voltage reading is at maximum value.

relationship with RSL, as follows:
Table 5.106 — Typical RSSI voltage levels with RSL for MPT-HC/XP/MC
Units Measurement (with MPT-HC/MPT-XP/MPT-MC)
Service kit cable 5 4.71 4.12 3.5 2.9 2.3 1.71 1.11 0.59 0.14
(Vdc)
RSL (dBm) -10 -20 -30 -40 -50 -60 -70 -80 -90 -100
1. Compare actual RSLs to the expected RSLs from the link installation datapack. Refer
to RSL Measurement Guidelines.
MPT Service Cord operative information
Figure 5.384 shows the cable P/N 3CC52191AAXX to be used during the Commissioning
to point the antenna.
Figure 5.384 — MPT Service Cord

5 — Installation
Connector usage:
• (M1) LEMO connector, to be plugged into LEMO connector on MPT-HC/MPT-XP/

MPT-MC.
• banana plugs (M3) and (M4): output is a 0 to +5V DC voltage proportional to the radio
Rx field. During equipment line–up, through a multi–meter it is possible to easily point
the antenna until the measured voltage is the maximum, corresponding to the maximum
radio Rx field.
• (M2) Connector: for Alcatel–Lucent internal use only.
RSL Measurement Guidelines
Interference for ODU300 (Not applicable for MPT-HC/MPT-XP/MPT-MC)
The RSSI filter has a nominal 56 MHz bandwidth, which means that depending on the
channel bandwidth used, multiple adjacent channels will be included within the filter
passband. Normally this will not cause a problem as antenna discrimination (beamwidth)
and good frequency planning should exclude adjacent channel interferers. However at sites
where this is not the case, ATPC should not be enabled.
• ATPC operates on the RSL. Any interferer that affects the RSL will adversely affect
ATPC operation
• Check for interference by muting the Tx at the far end and checking RSSI/RSL at the
local end
RSSI/RSL Accuracy
When checking RSSI/RSL against the predicted link values ensure appropriate allowances
are made for Tx power-setting accuracy, path-loss calculation accuracy, and RSSI/RSL
measurement accuracy.
• For a worst-case the overall accuracy is the sum of the individual accuracy limits,
which for an ODU300 link would be ±4 dB of the predicted value (±2 dB for transmit,
±2 dB for receive, 0 to 35°C), aside from the path-loss calculation accuracy, which
should be within limits of ±3 dB.
• Typically, where the measured RSSI/RSL is more than 4 dB lower than the expected
receive level you should check the path survey results, path calculations and antenna
alignment.
Note: When checking RSSI/RSL ensure the measurement is made under normal, unfaded
and interference-free path conditions.

5 — Installation
• A discrepancy of 20 dB or greater between the measured and calculated RSSI/ RSLs

suggests an antenna is aligned on a side lobe, or there is a polarization mismatch.
Using the RSSI voltage at the MPT-HLS
A voltmeter, such as a multimeter, is used to measure RSSI voltage.
Use the PRX Main + Diversity MPT-HL cord (3CC50210AA) in addition to the voltmeter.
To measure the signal using the RSL voltage:
1. Connect a voltmeter to the MPT-HL transceiver proper connector (see Figure 5.385)
using the PRX Main + Diversity cord.
Figure 5.385 — Connect a voltmeter to the MPT-HLS
2. Perform antenna alignment (see Aligning the Antenna) and maximize the voltage
reading.
relationship with RSL. Table 5.107 shows the typical values to be expected:

5 — Installation
Table 5.107 — Typical RSSI voltage levels with RSL for MPT-HLS
Units Measurements (with MPT-HLS)
PRX 4.94 4.31 3.72 3.10 2.46 1.86 1.25 0.62 0.26
cord
(Vdc)
RSL -20 -30 -40 -50 -60 -70 -80 -90 -100
(dBm)
4. Compare actual RSL to the expected RSLs from the link installation datapack. See RSL
Measurement Guidelines.
PRX Main + Diversity MPT-HLS cord operative information
Figure 5.386 shows the cable (3CC50210AA) to be used for RSSI voltage reading during
antenna alignment operations. The cable permits the measurements of RSSI levels for both
the main receiver and the diversity receiver when present. The wiring table provides
connection information.
Figure 5.386 — Cable for RSSI voltage reading
Table 5.108 — Wiring table for PRX cable
Signal M1 M2 M3 M4
standard RJ45 red banana plug black banana plug blue banana plug
unshielded plug
connector
RX PW MAIN 6 X
GND 7 X
RX PW DIV 8 X
Cable usage:

5 — Installation
The RJ45 connector (M1) must be plugged to the PRX connector on the MPT-HL
transceiver. The black banana plug (M3) must be plugged to the common of the voltmeter/
multimeter. The red banana plug (M2) will provide the Vdc level (positive) relative to the
Main receiver power level. The blue banana plug (M4) will provide the Vdc level (positive)
relative to the Diversity receiver (if present).
5.1.12.3 — Aligning the Antenna
Antenna alignment involves adjusting the direction of each antenna until the received
signal strength reaches its maximum level at each end of the link.
Fine adjustment for azimuth (horizontal angle) and elevation (vertical angle) is built into
each antenna mount.
Adjustment procedures will be provided with each antenna.
If the horizontal adjuster does not provide sufficient range to locate the main beam, the
antenna mounting brackets will need to be loosened and the antenna swiveled on its pole
mount to locate the beam.
Before doing this ensure the horizontal adjuster is set for mid-travel.
Some mounts for larger antennas have a separately clamped swivel base to allow the
loosened antenna to swivel on it without fear of slippage down the pole. Where such a
mount is not provided a temporary swivel clamp can often be provided using a pair of pipe
brackets bolted together immediately below the antenna mount.
Note: Ensure antennas are aligned on the main beam, and not a side lobe. For guidance,
refer to the sections Locating the Main Beam (see Locating the Main Beam) and Tracking
Path Error (see Tracking Path Error). Ensure ATPC is turned off during the alignment
procedure.
Standard Alignment Procedure
To align an antenna:
1. Loosen the azimuth adjuster on the antenna mount (horizontal angle) and adjust
azimuth position for maximum signal strength. Ensure antennas are aligned on the
main beam, and not a side lobe.
2. Tighten the azimuth securing mechanism. Ensure signal strength does not drop as it is
tightened.
3. Loosen the elevation adjuster (vertical angle) and adjust for maximum signal strength.
Ensure antennas are aligned on the main beam, and not a side lobe.

5 — Installation
4. Tighten the elevation securing mechanism. Ensure signal strength does not drop as it is
tightened. The terminal is now aligned and ready to carry operational traffic.
5. Record RSL and/or RSSI voltage in the commissioning log.
Additional procedure for CCDP XPIC links with MPT-HC/MPT-XP/MPT-

HLS
Note: Procedures are provided for the alignment of dual polarized antennas, and for
protected XPIC links.
For CCDP (Co-channel Dual Polarized) XPIC (Cross Polarized Interference Cancellation)
links it is important that antenna feeds are correctly aligned to achieve optimum XPIC
performance.
While a dual-feed antenna may be specified with a cross polarization discrimination of 30

dB, unless the antenna-to-antenna alignment over a link is correct, the effective
discrimination can be significantly less.
• The horizontal-to-vertical receive signal discrimination for satisfactory XPIC

operation must not be less than 25 dB, and where possible should be set for optimum
discrimination using this procedure.
• High performance shielded antennas typically exhibit 30 dB cross polarization
discrimination whereas 40 dB is typical for purpose-designed, high polarization
discrimination antennas.
• The received-signal V and H discrimination can be checked using the Measurement
tab-panel of the MPT-HC/MPT-XP/MPT-HLS, as shown in Figure 5.387.

5 — Installation
Figure 5.387 — XPD measurement
The cross pole discrimination measures the V and H signal discrimination in dB at the input
to the MPT-HC/MPT-XP/MPT-HLS (from the antenna feeds). The improvement in signal
discrimination provided by the XPIC function is in addition to this measurement.
Note: This alignment procedure is intended for dual-polarized antennas, but is also
generally applicable to installations using separate antennas for V and H planes.
Alignment Procedure for Dual polarized Antenna
The following procedure details steps required to:
• Check and if necessary set feedhead alignment using a spirit level.

• Align the antennas at each end using just one of the feeds, H or V (Standard co-plane
antenna alignment).
• Where the V and H waveguide ports on an antenna are not marked they can be
identified by the orientation of the waveguide slots.
• Where a dual-polarized antenna presents the same orientation on both ports, one
should have a straight waveguide feed to the antenna feedhead, the other will
include a 90 degree twist or have a straight waveguide feed but with a polarization
rotator in the feedhead. Generally the polarization rotator will act on the outer-most
waveguide on the feedhead.

5 — Installation
• For convention, if ports are not marked for V and H, it is recommended that the
port that has the straight waveguide feed or is connected to the inner-most
waveguide at the feedhead is selected as the horizontal antenna feed port. The
following graphic of an antenna feedhead assembly illustrates this. The top port is
connected to the inner feed on the feedhead, and with the port orientation shown
provides a horizontally polarized feed. The lower port has a rotator included in the
feedhead to provide a vertical feed.
• Ensure the same port is selected for vertical at both ends.

Where possible, the same ‘above and below’ relationship of the feed ports should
be used at both ends. For example, if at one end the horizontal feed port is located
above the vertical port, as in the example above, then the same relationship should
be used at the other end.
• Check cross pole discrimination (XPD) in the Measurement tab-panel of the MPT-HC/
MPT-XP/MPT-HLS.
• Optimize alignment of the feed-heads to achieve maximum cross polarization
discrimination.
Note: This procedure assumes that the antennas used at each end of the link do comply
with their cross-polarization discrimination specification. If in doubt, refer to the
antenna supplier.
Procedure:
1. Static Feedhead Alignment

This procedure would normally be completed in conjunction with antenna alignment,
step 2, to ensure no misalignment of skew angle is introduced during the pan and tilt
process.It should be completed before any feedhead weatherproofing is applied, so that
a spirit level can be used against the flange to check and set precise physical vertical /
horizontal alignment of the feeds:
• Do not rely on antenna markings as these will not be accurate where a mount is not
perfectly level.

5 — Installation
• Set the spirit level against the flange of the feedhead. Take care that only the flange
of the feedhead is measured, so that no error is introduced by any minor
misalignment of the mating flexible waveguide flange. See Figure 5.388.
Figure 5.388 — Checking Feedhead Flange with a Spirit level
• If not exactly vertical or horizontal, adjust the feedhead skew angle (rotate the
feedhead) until correct (spirit level bubble is precisely centered). For a typical
feedhead check both flanges for level, using an end point half way between the
level points of the two flanges should there be any discrepancy between the two.
2. Align Antennas
Align the antennas at both ends using the standard (co-plane) alignment procedure, but
using just one of the feeds, V or H. Refer to Standard Alignment Procedure (see
Standard Alignment Procedure).
If major adjustment to the pointing of the antenna is made during this process, recheck
the feedhead skew angle.
When correct, proceed to step 3.
3. Check Operation and End-End Feedhead Alignment
Power-up both V and H links and check they are operating normally and are alarm-free.
Use the Measurement tab-panel of the MPT-HC/MPT-XP/MPT-HLS to check that:
• Tx power measurements are within 1 dB (typically). If not check Tx power
settings.
• RSL measurements are within 2 dB. See Using RSL Data (see Using RSL Data)
for guidance on measurement accuracy.

5 — Installation
• Links are operating error-free.
Note: Where there is potential for interference from other links in the same
geographical area, check by turning the far end transmitter(s) off and measuring the
local end RSL on both V and H feeds.
4. Use the cross pole discrimination (XPD) measurement provided in the Measurement
tab-panel of the MPT-HC/MPT-XP to measure the actual V and H signal
discrimination from each antenna.
• Where measured XPDs are better than 25 dB no further adjustment is needed
• Where less than 25 dB proceed to the next step.
Caution: It is possible for a spurious XPD figure of about 50 dB to appear in instances

where there is major mis-alignment. Note that the raw XPD should never read higher than
the XPD specification of the antennas, which for most high performance dual-pol antennas
will be between 30 dB to 35 dB.
Note: The alignment procedures listed under steps 1 and 2 should result in a
discrimination of better than 25 dB, as measured in the Measurement tab-panel of the
MPT-HC/MPT-XP, which is comfortably within the operating limits of XPIC. However, for
best results and greater operating margins during fading, feedhead alignment should be
optimized using the following procedure.
5. Optimize End-End Feedhead Alignment

This procedure corrects for any minor rotational alignment between antennas at each
end.
One antenna is the reference antenna and its feed-head assembly is not adjusted during
this procedure.
Note: Only check/adjust skew angles on one antenna. If both antennas are adjusted and
re-adjusted there is potential for progressive misalignment to occur. Select one antenna
as the reference antenna. On long hops and where fading is prevalent there is potential
for the V and H plane paths to be affected differently and to therefore exhibit variable
cross-polarization discrimination. This alignment procedure must be conducted during
periods of known, stable path conditions.
6. Determine which end of the link is to provide the reference antenna, and at the opposite
end open the Measurement tab-panel of the MPT-HC/MPT-XP/MPT-HLS for the V
and H.
7. Adjust the feedhead skew angle of the antenna for maximum XPD on both V and H
link. If the maximums for each are at (slightly) different angles, adjust for a mid-point.

5 — Installation
Note: Ensure that as you adjust the skew angle, the physical antenna alignment does not
shift, which would make it necessary to repeat step 2. Check that antenna mounting bolts
and azimuth and elevation adjuster locks have been correctly tightened. The maximum
points may be quite sharp, rotate the feedhead slowly to ensure they are not missed.
8. Check the XPD on the link at the reference end of the link, which should be within 1 to
2 dB of the measurements at the adjusted end.
9. On completion ensure feedhead bolts are correctly tightened - check that XPDs do not
change during tightening.
10. Retain feed-head adjustment data for the commissioning records.
5.1.12.4 — Main Beams and Side Lobes
This section describes how to locate the main beam, and typical tracking path errors.
Locating the Main Beam
Ensure the antennas are aligned on the main beam, and not a side lobe.
Once a measurable signal is observed, very small alignment adjustments are required to
locate the main beam. For instance, a 1.2m antenna at 23 GHz typically has 0.9° of
adjustment from center of main beam to the first null (0.4° to the -3 dB point). Antenna
movement across the main beam will result in a rapid rise and fall of signal level. As a
guide, 1 degree of beam width is equivalent to moving approximately 1.0 mm around a
standard 114 mm (4.5 in.) diameter O/D pipe.
Antennas can be verified as being on main beam (as opposed to a side lobe) by comparing
measured receive signal level with the calculated level.
Signal strength readings are usually measurable when at least a main beam at one end and
first side lobes at the other are aligned.
The strongest signal occurs at the center of the main beam. The highest first lobe signal is
typically 20 - 25 dB less than the main beam signal. When both antennas are aligned for
maximum main beam signal strength, the receive signal level should be within 2 dB of the
calculated level for the path. This calculated level should be included in the installation
datapack for the link.
Figure 5.389 is an example of a head-on, conceptual view of the beam signal strength, with
concentric rings of side lobe peaks and troughs radiating outward from the main beam.

5 — Installation
Figure 5.389 — Indicative head-on signal pattern for a parabolic antenna
Tracking Path Error
Side lobe signal readings can be confused with main beam readings. This is particularly true
for the first side lobe as the signal level at its center is greater than the signal level at the
edges of the main beam, and if tracking on an incorrect elevation (or azimuth) a false
impression of main beam reception can be obtained. This illustration shows an example of
this with a simplified head-on view of an antenna radiation pattern, and tracking paths for
three elevation settings.
Figure 5.390 — Example Tracking Path Signals

5 — Installation
Line AA represents the azimuth tracking path of a properly aligned antenna.The main beam
is at point 2, and the first side lobes at points 1 and 3. Line BB represents the azimuth
tracking path with the antenna tilted down slightly. Signal strength readings show only the
first side lobe peaks, 4 and 5. In some instances the side lobe peaks are unequal due to
antenna characteristics, which can lead to the larger peak being mistaken for the main
beam. The correct method for locating the main beam in this case is to set the azimuth
position midway between the first side lobe peaks, and then adjust the elevation for
maximum signal.
Line CC represents an azimuth tracking path with the antenna tilted down further still. The
first side lobe signal peaks (6 and 7) appear as one peak, leading to a mistaken interpretation
of a main beam. The correct method for locating the main beam is to set the azimuth at mid
peak, between 6 and 7, and then adjust elevation for maximum signal.
This first side lobe peaking is probably the most frequent cause of misalignment in both
azimuth and elevation, especially so if one side lobe peaks higher than the other, as shown
in Figure 5.391 A common error is to move the antenna left to right along line DD, or top
to bottom along line EE, always ending up with the maximum signal at position 1.
Figure 5.391 — Example Tracking Path Signals on the First Side Lobe
5.2 — Software local copy

This section explains how to prepare the TCO Suite and WebEML environment in your PC.
• Getting Started
• PC Characteristics
• Local copy of the Software Package (SWP) to the PC
• Local copy of the WebEML and TCO Suite Software to PC

5 — Installation
• Local Copy of WebEML (JUSM/CT)

• Local Copy of Provisioning Tool installation
• Configure PC Network Card to Connect to NE
• Download Software Package to NE
• Server Access Configuration
• Init SW Download
• Software Status Detail
5.2.1 — Getting Started
Note: Read the following before starting.
The operator must be familiar with the use of personal computers in WINDOWS
environment, internally from which the NE application software operates.
TCO Suite and WebEML applications are on one DVD-ROM. Software Package (SWP) is
on another CD. Verify versions of the DVD-ROM and CD-ROM.
To properly install TCO Suite and WebEML applications, a PC is required, having the
characteristics specified here below.
5.2.2 — PC Characteristics
The PC to use for TCO Suite and WebEML applications must meet following
characteristics:
Table 5.109 — PC Hardware Configuration
PC Hardware Configuration
CPU AMD Althon / Intel Celeron / Intel Pentium 4 or higher
Application Needed RAM 512MB (needed), 1GB (suggested) for each application
instance
Minimum disk space 1GB (for full WebEML local copy, JRE excluded)
DVD-ROM Drive needed
Primary Network Interface Ethernet Card 10/100 Mbit/sec or higher

5 — Installation
Table 5.109 — PC Hardware Configuration (Continued)
PC Hardware Configuration
Screen resolution 4:3 displays: 1152x864

16:9 displays: 1440x900
Table 5.110 — Operating Systems Supported
Operating Systems Supported Version
Microsoft Windows:
XP Professional SP 3 (or newer updates, if available)
Windows 7 SP1 (or newer updates, if available)
Alcatel-Lucent recommends Windows 7 in an IPv6 environment.
Table 5.111 — Java Runtime Environment
Java Runtime Environment Java 7 update 17 x 86 32bit (Note)
Note: TCO Suite contains 32-bit Java VM only. This can be used with 32-bit Internet
browsers only such as Mozilla Firefox, Internet Explorer or Google Chrome.
Please note that reference Microsoft Windows operating systems do not allow a 64-bit
Internet browser (not even Microsoft Internet Explorer 64-bit) as default browser for the
system in use. In case a 64-bit browser needs to be used, manually install a 64-bit Java VM
and load (e.g.: from the browser "File" > "Open" command) the Start.html file you can find
in the TCO Suite DVD-ROM root directory.
If a more recent Java VM version 7 is installed, there is no need to remove it or to set a

specific configuration. TCO Suite and WebEML will automatically use Java 7 update 17
only for its own session. All other java applications, web applications or applets using the
newer version as default will continue to work with the newer version.
Table 5.112 — Tested FTP Servers
Tested FTP Servers (for software Download feature)
Apache FTP Server
VSFTPD, (version 2.0.5)
FileZilla FTP Server (version 0.9.41)

5 — Installation
Warning: Disable all firewall software on PC or, at least, enable ports associated to
WebEML (SNMP, FTP, Telnet, http, UDP, rmi).
Web browser
No Web browser has to be installed on the PC for the Craft Terminal application.
TCO specific requirements:
• For TCO Provisioning Tool and Alarms and Settings interface, the only guaranteed
configuration is a PC directly connected to the NE via a single, direct network cable.
Remote configuration is allowed but in this case the connectivity has to be assured by
the operator;
• Standard user can be used to run the applications but for TCO Suite usage
Administrator password is needed;
• Regardless the screen resolution, for optimal rendering and tools usage, minimum
HTML page size shown shall be 1024x768 pixels.
5.2.2.1 — Local copy of the Software Package (SWP) to the PC
Follow these steps to copy the Software Package (SWP) to the PC.
1. Insert the SWP CD into the CD-ROM drive.

2. Click on the Local Copy button to copy the software to your local PC.
3. The File copy window opens. Click on the... button to choose a directory to copy the
package to.

5 — Installation
4. Choose a directory location for the Local Copy of Software Package. Select the
directory and click on OK to begin the copy process.
Warning: Special characters (\ / : * ? < > |) cannot be used.
5. The files will be copied from the CD to the PC and will create a directory named ECT.

5 — Installation
6. Click on the Close button.

7. Remove the SWP CD from the CD-ROM drive.
Note: In case of third party FTP/SFTP servers running on the same PC where the NEtO/
JUSM is running, the SWP package must be copied to a directory under the default path;
%USERPROFILE%/9500MPR-E/res/home.
5.2.3 — Local copy of the WebEML and TCO Suite Software to

PC
Follow these steps to copy the WebEML/TCO Suite software to the PC.
1. Insert the TCO SW Suite DVD-ROM into the DVD-ROM drive.
Note: The TCO SW Suite DVD-ROM will auto-run as soon as the DVD-ROM is read by the
PC. If auto-run does not start, user must run (double-click with left mouse button on it)
the Start.exe file, available on DVD-ROM root, to launch the Software Package.
2. A start panel opens.

5 — Installation
3. The main menu opens.
4. Click on the Settings button.

5 — Installation
5. Choose one of the Settings options to copy software to the PC.

• Local Copy of WebEML (JUSM/CT)
• Local Copy of Provisioning Tool installation
5.2.3.1 — Local Copy of WebEML (JUSM/CT)
1. Choose Local Copy of WebEML (JUSM/CT) to copy the WebEML software to your
PC.
2. Select the directory and click Open.
Note: The default directory is C:\Alcatel-Lucent.

5 — Installation
3. Select the SW component(s) to copy and click on Copy.
4. The copy is now in progress.

5 — Installation
5. Wait until the following message will appear. Click OK.
6. Click Yes to set a link on the desktop.
Note: On the desktop a link to the WTPMS in offline mode is also automatically created.

5 — Installation
7. Click on the WebEML icon on the desktop to start the application.
An alternative way to run the WebEML or create a local copy is the following:
1. Click on the MSS-8 & MSS-4 or MSS-1 icon to perform the Local Copy of the
WebEML.
2. Click on Operational & Maintenance.

5 — Installation
3. Follow the instructions in steps 2 through 6.

You can also click on the Provisioning Tool button to run the Provisioning Tool, or
click on the Alarms&Settings button to run the Alarms&Settings tool.
5.2.3.2 — Local Copy of Provisioning Tool installation
1. Choose Local Copy of Provisioning Tool to copy the Provisioning Tool software to
your PC. Choose the directory location and click Open. The default directory is
C:\Alcatel-Lucent.
The files will be copied from the CD to the PC in a created directory.

2. When the file has been successfully copied, click the OK button.

5 — Installation
3. The user has the option to create a shortcut link on the PC desktop. Click Yes or No.
4. An icon similar to this one will be created on the desktop if the user clicked yes.
5.2.4 — Configure PC Network Card to Connect to NE

This example uses a Microsoft Windows XP Professional system.
1. Connect a CAT 5/5E cable from the PC network card to NMS connector on Slot 1
Core-E card.
2. Click on the START menu on the Windows desktop and open up the CONTROL
PANEL.
3. Open up the NETWORK CONNECTIONS. Highlight the network card as shown
below.

5 — Installation
4. Double click on Properties to display the screen below and scroll down the list to
highlight the Internet Protocol (TCP/IP) line. Click the OK button.

5 — Installation
5. As default the DHCP server on the MPR is enabled. Set the PC to get automatically an
IP address.
6. If for any reason the DHCP server on the MPR has been disabled, enter the IP address
of 10.0.1.3 for the PC network card as shown below. Click OK.

5 — Installation
Note: The 10.0.1.3 IP address example shown below is derived from the default NE IP
address (10.0.1.2) plus 1. If there is an IP address conflict within your network, increment
the last number by two.
Note: It is suggested to keep enabled only one network connection on a PC.
7. To check the connectivity between the PC and the NE, open up a DOS window or
Command Prompt. Click on the START menu on the Windows desktop and open up
the RUN window as shown below.
8. Type cmd and click OK to open up a DOS window.
The DOS window will display.

5 — Installation
9. In the DOS window, click the cursor after the > and type ping 10.0.1.2 to verify a
connection between the PC and the NE. The Ping statistics for the IP address 10.0.1.2
should display 4 packets sent and 4 packets received.
Note: The 10.0.1.2 IP address is the default NE IP address.
5.2.5 — Non-administrator user

The system supports non-administrator users and user groups.

5 — Installation
It is NOT mandatory that TCO Suite applications be launched by a user with Administrator
privileges. Full control permissions are required to allow TCO Suite software applications
to write their own log files.
Non-administrator users MUST have full control permissions applied to the folder where
the TCO Suite is saved for proper operation of the TCO Suite software applications.
Note: Non-administrator users MUST have full control permissions applied to the folder
where the TCO Suite is saved for proper operation of the TCO Suite software applications.
Note: Prior to performing this procedure, the non-administrator user and/or user group
MUST be enabled as a user and/or member of a non-administrator group on the computer.
1. Using file manager, navigate to the folder where the TCO Suite is saved (typically: C:/
Alcatel).
2. Select the folder (Alcatel) where the TCO Suite is saved.
3. Right-click on the folder and then select Properties.
4. Select the Security tab. See Figure 5.392.
Figure 5.392 — Folder properties security tab

5 — Installation
5. Select the non-administrator user or the non-administrator user group.

See Figure 5.392.
6. Enable Allow, Full Control check box. See Figure 5.392.
7. Click the Apply button. See Figure 5.392.
8. Verify the non-administrator user/group has full control permissions.
See Figure 5.393.
Figure 5.393 — Non-administrator ‘Full Control’ permissions provisioned
9. Click the OK button.
5.2.6 — Download Software Package to NE

After the switching on of the equipment click on the MPRE-WebEML icon on your
desktop.
The Server Access Configuration menu option in the menu bar allows the user to configure
the FTP/SFTP server to be used to download the Software Package (SWP) to the NE.
1. Open NEtO, enter the IP address of the NE, then click OK and Show. On the JUSM
main screen, click on the SW Download dropdown menu and select Server Access
Configuration.

5 — Installation
5.2.6.1 — Server Access Configuration
The user has the choice of implementing Step 3 OR Step 4 below. Afterwards, continue to
Step 4.
1. Choose the FTP or SFTP radio button.

2. Perform one of the following:
• Enter the Username and Password login information to access the FTP server. In
the Address field, write the IP address of the FTP server. In the Port field, write
the port to be used and in the Root field, write the directory into which the software
has been downloaded.
Figure 5.394 — Server Access Configuration for FTP server
• Enter the Username and Password login information to access the SFTP server.
In the Hostkey Fingerprint field write the server’s hostkey fingerprint. In the
Address field, write the IP address of the SFTP server. In the Port field, write the
port to be used and in the Root field, write the directory into which the software
has been downloaded.

5 — Installation
Figure 5.395 — Server Access Configuration for SFTP server
3. Click the Set Default button and the screen below will appear showing the default
configuration.
The WebEML is the default FTP and SFTP server.
The following parameters apply for FTP:
• Username: anonymous
• Password
• Address: Local host IP address
• Port: 21
• Root Dir: /
The following parameters apply for SFTP:
• Username: swp-administrator1
• Password: not displayed
• Hostkey fingerprint: F1:A4:96:42:97:A3:2B:45:7E:D6:4C:58:5D:00:77:42
• Address: Local host IP address
• Port: 22
• Root Dir: /
Note: The set default parameters can be changed by writing different values in the fields
and then by clicking on the OK button.
4. Click the OK button.
5.2.6.2 — Enable FTP/SFTP server

5 — Installation
Note: Do not start NEtO Servers (FTP/SFTP) when a 3rd party FTP/SFTP Servers is already
started on the PC. Due to interactions between Java and Windows OS, the TCP ports could
be bound by both the 3rd party Server and the NEtO Server.
From the NEtO Servers Manager enable the appropriate FTP/SFTP server depending upon
the server setup in Server Access Configuration, see Figure 5.396.
Figure 5.396 — Enable SFTP server
If the FTP/SFTP server cannot be started, for example if a third party FTP/SFTP server is
already connected to the port, an error message appears.
Figure 5.397 — FTP/SFTP Server error message
5.2.6.3 — Init SW Download
The download takes the following times:
• SWP download (from PC to Core-E): 11 minutes

• MPT download (automatically starts after the SWP download: all the MPT are
downloaded in parallel): 5 minutes
• activation of the FPGA of the units:
• PDH: 3 minutes
• SDH: 20 minutes
• EAS: 1 minute

5 — Installation
• Modem: 20 minutes
• MPT access: 15 minutes
• ASAP: 1 minute
• AUX: less than 1 minute
• ODU300: 40 seconds
All the units are activated in series. At the end of the activation of an FPGA a traffic hit
is caused.
1. On the JUSM main screen, click on the SW Download dropdown menu and select Init
SW Download. This menu option allows the user to download software to the NE for
initial downloads and upgrades.
2. Click the Add button to add the available software packages on the PC.
Note: Before starting the software download it is recommended to set the RTPC mode to
the maximum Tx power.

5 — Installation
3. Browse to the directory where the NE software was saved, select the related descriptor
(DSC) file, and click the Open button.
4. Highlight the description file (i.e. R95M.DSC) and click the Open button.
5. Highlight the line as shown below and click on the Init Download button.

5 — Installation
A dialog window opens to verify that an FTP or SFTP server is running.
6. Click the Yes button to begin the download process.

When the SW download starts, a screen showing the in progress operation of the
download appears. The download is aborted when the Abort button is pressed.

5 — Installation
7. Click Ok.
5.2.6.4 — Software Status Detail
1. On the WebEML main screen, click on the SW Download dropdown menu and select
SW Status.
This screen shows the last two software versions details ( Tab 1 Committed Software
and Tab 2 Standby Software) stored on the NE. In this example, Tab 1 Committed
Software shows the current committed software running on the NE. Tab 2 Standby
Software shows the standby software or previous software.
Tab 1 Committed Software
This is the current software running on the NE.

5 — Installation
Tab 2 Standby Software
This is the software that was downloaded above or was the previous SW version.
1. Select Tab 2 and click on the Software Management Action drop down list.
2. Select Activation from the Software Management Action drop down list.
3. Click the Apply Action button to confirm the action.

5 — Installation
4. Click Confirm on the “Do you confirm the action?” message.

5. Click OK on the “Action command sent successfully!” message.
6. The card will reboot automatically with the new software in Tab 2 and will display this
message. Click OK.
Note: After the Core-E card reboots, the Tab 2 software version that was activated above
will be listed under the Tab 1 SW status detail and is the committed software running the
NE. The previous software will be listed under Tab 2 now.

5 — Installation

6 — Provisioning
The Provisioning can be performed by using:
• Provisioning tool (refer to Provisioning by Provisioning Tool)

• WebEML (refer to Provisioning by WebEML)
Note: Graphics in this chapter may not match the current release.
6.1 — Provisioning by Provisioning Tool

The Provisioning Tool allows to create and modify provisioning files.
6.1.1 — Start Provisioning Tool

Double click on the TCO Provisioning tool icon on the Desktop (for the local copy on the
PC see Local Copy of Provisioning Tool installation).
The Provisioning Tool can be used "offline" and "online".
• In case of offline, it allows to prepare the provisioning in back office. Minimizing time
on field and mistakes.
• With the online mode you can either apply the "offline" configuration or fulfill online.
This tool is recommended for first installation.
WebEML is more flexible and mandatory to configure AUX and ATM boards (not yet
supported in provisioning tool).
Select:

6 — Provisioning
• the direct connection to the NE by putting a check mark on “Connect to NE”. When
you locally connect the PC to the NE, in the IP Address field automatically (through
the autodiscovery) appears the IP Address of the NE (in the NE the default
configuration of the DHCP server is enabled; for this reason your PC must be
configured to obtain an IP Address automatically).
• Click on OK.
Note: If the DHCP server is disabled, the IP address to be entered is the IP address of the
NMS Ethernet port.
or
• the off-line configuration by putting a check mark on “Do not connect to NE” and by
clicking on Apply.
Figure 6.1 — Provisioning Tool Connectivity
The screen in Figure 6.2 will display if you are working off-line or the screen in Figure 6.3,
if you are directly connected to the NE.

6 — Provisioning
Figure 6.2 — Provisioning Tool Screen (off-line)

6 — Provisioning
Figure 6.3 — Provisioning Tool Screen (direct connection to the NE)
If the NE does not have an empty configuration, the following screen with the following
message will appear.

6 — Provisioning
Figure 6.4 — Clear Database and Restart NE
Press the Clear Database and Restart NE button and then press Create to create a new
configuration or press Open to open a previously created configuration.
Note: If you don't press the Clear Database and Restart NE button at the end of the
configuration you can save the file, but you cannot apply the configuration to the NE. (The
Apply button will not be available at the end of the procedure).
Note: If you need to create a configuration using at least two MPT-HC/MC/XPs on the
same polarization (for example, frequency diversity or N+0), if the channels are not in the
same sub-band, contact Alcatel-Lucent. This check is not required if one antenna is in use
per sub-band.

6 — Provisioning
6.1.1.1 — Configuration Screen Options
The screen below is a generic one that depicts all of the pull-down options possible
depending on which card is selected in the card slot. Protections options shown below are
for all cards. See the screens shown below for more information.
Warning: The Provisioning Tool allows to configure all the units, except the MSS-1, EAS
unit, ASAP unit and AUX unit. These units must be configured with the WebEML.
Warning: To configure an MSS-4 or MSS-8 extract the ASAP and/or AUX units, if any.
Note: The SDH unit is available in 2 versions:
•SDHACC (operation in transparent mode)

•SDHCHAN (operation in channalized mode)
Note: The Site Name and Site Location fields must not include the special characters (\
/ : * ? < > |).

6 — Provisioning
Figure 6.5 — Configuration Options Screen
Warning: If from this NE remote NEs have to be reached, remember to configure properly
the Routing Protocol of the TMN-RF channel, if the remote NE is connected through the
radio link (refer to Figure 6.11 or Figure 6.12 or Figure 6.14 or Figure 6.16) or of the NMS
Ethernet Port, if the remote NE is connected through the Ethernet cable (refer to
Figure 6.30).
Buttons:
• Restore: allows to restore in the screen the initial data without any change
• Prev: the procedure goes back to the previous step (the changed data may be lost after
the Warning message)
• Next: the procedure goes on to the next step (some checks and data storage is done)
• Cancel: the procedure goes back to step 1 (Opening screen)
• Help: by clicking on this button the operator calls the help on line.

6 — Provisioning
Figure 6.6 — Core-E Configuration (Sheet 1 of 2)

6 — Provisioning
Figure 6.7 — Core-E Configuration (Sheet 2 of 2)
Note: The Ethernet Advanced features of the Ethernet ports must be configured with the
WebEML.

6 — Provisioning
Note: Protection for MPT-HC, MPT-XP, or MPT-MC units on the Core-E must be configured
with the WebEML.
Figure 6.8 — E1 Configuration

6 — Provisioning
Figure 6.9 — STM-1 Configuration (SDHACC)

6 — Provisioning
Figure 6.10 — STM-1 Configuration (SDHCHAN)

6 — Provisioning
Figure 6.11 — Modem Provisioning (without Adaptive Modulation)

6 — Provisioning
Figure 6.12 — Modem Provisioning (with Adaptive Modulation)

6 — Provisioning
Figure 6.13 — MPT Access configuration (1+0)
Note: The selection of the Power Supply mode to supply the MPT can be: PFoE (through
1 cable for MPT-MC or MPT-HC) or QMA (through 2 cables for MPT-HC).

6 — Provisioning
Figure 6.14 — MPT-Access Provisioning (without Adaptive Modulation)

6 — Provisioning
Note: This field is available only with the MPT-HC/MPT-XP with the XPIC+RPS external
module installed and if in the Mode area in the Option field a mask with XPIC has been
selected.
The XPIC can be configured in 1+0 or 1+1 HSB (with or without Adaptive Modulation).
Note: NOT ALL the channel spacings and modulation schemes can support the XPIC
Configuration.
To configure the XPIC go to Figure 6.15.
Figure 6.15 — MPT-HC/MPT-XP with XPIC

6 — Provisioning
Figure 6.16 — MPT-Access Provisioning (with Adaptive Modulation)

6 — Provisioning
Figure 6.17 — MPT Access configuration (protection enabling: 1+1)

6 — Provisioning
Figure 6.18 — MPT-Access Provisioning (without Adaptive Modulation) (1+1)

6 — Provisioning
Note: This field is available only with the MPT-HC/MPT-XP with the XPIC+RPS external
module installed and if in the Mode area in the Option field a mask with XPIC has been
selected.
The XPIC can be configured in 1+0 or 1+1 HSB (with or without Adaptive Modulation).
Note: NOT ALL the channel spacings and modulation schemes can support the XPIC
Configuration.
To configure the XPIC go to Figure 6.15.

6 — Provisioning
Figure 6.19 — MPT-Access Provisioning (with Adaptive Modulation) (1+1)

6 — Provisioning
Figure 6.20 — Synchronization Configuration (Master)

6 — Provisioning
Figure 6.21 — Synchronization Configuration (Slave)

6 — Provisioning
Figure 6.22 — XPIC Configuration

6 — Provisioning
Figure 6.23 — Ring Configuration

6 — Provisioning
Figure 6.24 — Cross Connections Configuration

6 — Provisioning
Figure 6.25 — Segregated Port Configuration

6 — Provisioning
Figure 6.26 — 802.1D management

6 — Provisioning
Figure 6.27 — 802.1Q management

6 — Provisioning
Figure 6.28 — VLAN Management

6 — Provisioning
Figure 6.29 — Port VLan configuration
Note: The Port VLan Configuration screen opens only if in the Bridge Configuration
screen the 802.1Q (Virtual Bridge) has been selected.

6 — Provisioning
Figure 6.30 — Network Configuration

6 — Provisioning
Figure 6.31 — Trusted Managers screen

6 — Provisioning
Figure 6.32 — Typical Report Panel
By pressing the Save button an XML file is created with extension mcml.
6.2 — Provisioning by WebEML
6.2.1 — Start WebEML

1. Double click on the WebEML icon on the Desktop (for the local copy on the PC refer
to Local copy of the WebEML and TCO Suite Software to PC).
2. Enter the IP Address or DNS name.
3. Click OK. The Login window opens.

6 — Provisioning
Figure 6.33 — Network Element Overview
4. Enter your Login Name – must not be more than 20 characters.
Note: There are four user profiles defined.
•Administrator (full access also for NMS local system security parameters).
•CraftPerson: person in charge for installation and the maintenance at radio site; full access
to NE but not for security parameters, only for own password.
•Operator (person in charge to operate at the network level, not at the radio side).
•Viewer (view screens only).
Note: At the NE installation time, two default user accounts are created on the NE
independently from the SNMP operating mode.
•Profile: administrator
•Username: initial
•Password: adminadmin
•Profile: craftPerson
•Username: Craftperson
•Password: craftcraft
To change the Default UserName and Password see Profile Management Menu.
5. Enter your Password – must not be less than six (6) or more than 20 characters and
must be composed of full ASCII characters set (UPPER/lower case, numeric and
special characters).
6. Click on the Login button.

6 — Provisioning
Figure 6.34 — How to Login
7. Click on the Show button. An acknowledgement window opens.
Figure 6.35 — Acknowledgement of Authorization window
8. Click on the Accept button to proceed. The JUSM opens.
6.2.2 — Provisioning
Note: Changes to provisioning do not have to be made in any particular order.
The following is the recommended sequence.
1. Enable Plug-In Cards

2. Provision Plug-In Cards
3. Provision XPIC (if required)
4. Provision Synchronization
5. Provision NTP protocol
6. Provision NE Time

6 — Provisioning
7. Provision VLAN (if required)

8. Provision Cross-Connections
9. Provision AUX Cross-Connections
10. Provision Ethernet Ring
11. Provision LAG
12. Provision QoS
13. Provision Ethernet Connectivity fault management
14. Provision System
15. Provision management parameters (sections 6.2.2.16 to 6.2.2.22)
Warning: If remote NEs have to be reached from this NE, remember to configure the
Routing Protocol of the PPP RF channel, if the remote NE is connected through the radio
link or of the NMS Ethernet Port, if the remote NE is connected through the Ethernet
cable. See chapter 4 to configure routing.
6.2.2.1 — Enable Plug-In Cards
All the cards that can be inserted in MSS-4 or MSS-8 chassis must be enabled in the
equipment section:
• SFP optical plug-in

• Spare CORE-E (in slot 2 only)
• E1-PDH Access card
• STM-1 Access card
• Modem Access card (ODU300 interconnection)
• MPT Access card (MPT interconnection)
• AUX board
• ASAP board
• EAS board
• EASv2 board
• MPT-HLS radio
• FAN board
Enable the MSS cards by using the following procedures. See Figure 6.36 through
Figure 6.63.

6 — Provisioning
Enable SFP optical plug-in
See Figure 6.36 Follow the steps to enable the optional SFP plug-in for the optical 1000
Mb/s Ethernet interface.
Figure 6.36 — Enable SFP optical plug-in
Enable ports in the main Core-E Card to interface the MPT-HC and MPT-
MC
The main Core-E card itself does not need to be enabled. See Figure 6.37 and follow the
steps to enable the ports to interface with an MPT-HC or MPT-MC.

6 — Provisioning
Figure 6.37 — Enabling one port in the Core-E card
Note: Up to six MPT-HC or four MPT-MC can be connected to one Core-E unit, in protected
or unprotected configurations. Each port is protected by the other port of the same type,
that is, Port #2 protects Port #1, Port #4 protects Port #3 and Port #6 protects Port #5.

6 — Provisioning
Figure 6.38 — Enabling Protection configuration with MPT-HC/MPT-MC
Enable Spare Core-E Card
See Figure 6.39. Follow the steps to enable the Spare Core-E Card in slot 2.

6 — Provisioning
Figure 6.39 — Enable Spare Core-E Card
Enable E1 Access Card
See Figure 6.40, Figure 6.41, and Figure 6.42. Follow the steps to enable the E1 Access
Card(s).

6 — Provisioning
Figure 6.40 — Enabling E1 Access Card

6 — Provisioning
Figure 6.41 — Enabling E1 Access Card on the same row (to implement protected
configuration)

6 — Provisioning
Figure 6.42 — Enabling E1 Access Card protection
Enable STM-1 Access Card
See Figure 6.43. Follow the steps to enable the STM-1 Access Card(s).

6 — Provisioning
Figure 6.43 — Enabling STM-1 Access Card

6 — Provisioning
Figure 6.44 — Enabling SFP for SDHACC
Figure 6.45 — Enabling SFP for SDHCHAN

6 — Provisioning
Figure 6.46 — Enabling STM-1 Access Card on the same row (to implement protected configuration)

6 — Provisioning
Figure 6.47 — Enabling STM-1 Access Card protection
Enable Modem Card (to interface ODU300)
See Figure 6.48. Follow the steps to enable the Modem Card(s).
Note: The ODU is automatically enabled when Modem Card is enabled.

6 — Provisioning
Figure 6.48 — Enabling Modem Card

6 — Provisioning
Figure 6.49 — Enabling Modem Card on the same row (to implement protected configuration)

6 — Provisioning
Figure 6.50 — Enabling Modem Card protection
Enable MPT Access Card (to interface the MPT-HC and MPT-MC)
See Figure 6.51. Follow the steps to enable the MPT Access Card.

6 — Provisioning
Figure 6.51 — Enabling MPT Access Card

6 — Provisioning
Figure 6.52 — Enabling one port in the MPT Access card
Note: Two unprotected or protected MPT-HC or MPT-MC can be connected to one MPT
Access unit.

6 — Provisioning
Figure 6.53 — Enabling MPT Access Card - 1

6 — Provisioning
Figure 6.54 — Enabling one port in the MPT Access card - 1

6 — Provisioning
Figure 6.55 — Enabling Protection configuration with MPT-HC/MPT-MC
Enable ASAP Card
See Figure 6.56. Follow the steps to enable the ASAP Card.

6 — Provisioning
Figure 6.56 — Enabling ASAP Card - Wrong Figure shown
Enable EAS Card
See Figure 6.57. Follow the steps to enable the EAS Card.

6 — Provisioning
Figure 6.57 — Enabling EAS Card
Enable EASv2 Card
See Figure 6.58. Follow the steps to enable the EASv2 Card.

6 — Provisioning
Figure 6.58 — Enabling EASv2 Card
Enable AUX Card
See Figure 6.59. Follow the steps to enable the AUX Card.

6 — Provisioning
Figure 6.59 — Enabling AUX Card
Enable MPT-HLS radio
See Figure 6.60 and Figure 6.61 and follow the steps to enable the MPT-HLS radio card.
See Figure 6.62 and follow the steps to enable the fan.

6 — Provisioning
Figure 6.60 — Enable the subrack for an MPT-HLS radio
3
2
23757
To enable the radio card:
1. Click on the top level element in the Equipment view.

2. In the Settings panel, choose SR-MPT-HLS from the Top Rack or Bottom Rack drop-
down.
3. Click Apply. The top or bottom subrack appears in the Equipment view.

6 — Provisioning
Figure 6.61 — Enable the MPT-HLS radio
5 6 7
23758
4. Click on one of the vertical slots of the subrack.

5. In the Settings panel, choose MPT-HLS from the Equipment Type drop-down.
6. Choose one of the ports on the EASv2 card from the Interface drop-down.
7. Click on the Apply button. An SD check box is displayed.
8. If the diversity combiner is in use, select the SD check box and click on the Apply
button.
9. The card is enabled. The fan slot is outlined in red.
To enable the fan:

6 — Provisioning
Figure 6.62 — Enable the MPT-HLS fan
4
23759
1. Click on the horizontal slot above the radio slots.

2. In the settings panel, choose SR-FAN4 from the Equipment Type drop-down.
3. Choose an EAS channel from the Fan Handler MPTs drop-down.
4. Click Apply.

6 — Provisioning
Enable Fan Unit
See Figure 6.63. Follow the steps to enable the Fan Unit.
Figure 6.63 — Enabling Fan Unit
6.2.2.2 — Provision Plug-In Cards

6 — Provisioning
See Figure 6.64 through Figure 6.67 to provision MSS plug-in card parameters after the
cards have been enabled.
To configure radios, see section RADIO VIEW for RADIO DOMAIN.
Provision Housekeeping inputs (MSS-1 or A-FANS unit)
See Figure 6.64. Follow the steps to provision housekeeping inputs for the MSS-1 or A-
FANs unit.
Figure 6.64 — Housekeeping input provisioning (MSS-1 or A-FANS unit)
1 Double
left click
Or
1 Double
left click
23337
For the configuration of the MSS-1 tab-panels refer to MSS External Input Point view (to
open this view double click on the HK inputs on an MSS-1).
For the configuration of the A-FANS tab-panels refer to MSS A-FANS main view (to open
this view double click on an A-FANS card).
Provision MPTACC Card
See Figure 6.66 and follow the steps to provision the EAS Card.

6 — Provisioning
Figure 6.65 — MPTACC Card Provisioning
• Configure the power source as explained in Power Source.

• Configure the MPT as explained in RADIO VIEW for RADIO DOMAIN.
Provision EAS Card
See Figure 6.66 and follow the steps to provision the EAS Card.

6 — Provisioning
Figure 6.66 — EAS Card Provisioning
• Configure the user Ethernet ports as explained in EAS VIEW for P8ETH and EASv2.
Provision EASv2 Card
See Figure 6.67 and follow the steps to provision the EASv2 Card.

6 — Provisioning
Figure 6.67 — EASv2 Card Provisioning
• Configure the power source as explained in Power Source.

• Configure the user Ethernet ports as explained in EAS VIEW for P8ETH and EASv2.
6.2.2.3 — Provision XPIC
The XPIC configuration can be implemented only with the MPT-HC/MPT-XP.
For the configuration refer to XPIC configuration.
6.2.2.4 — Provision Space Diversity

6 — Provisioning
The Space Diversity configuration can be implemented only with an MPT-HLS with an Rx
Diversity module installed.
6.2.2.5 — Provision Synchronization
All the NEs radios in the network must be synchronized to the same clock. One radio in the
network is provisioned Master. All other radios in the network must be provisioned Slave.
The slave radios all sync to the clock provided by the master.
For the Synchronization configuration refer to Synchronization Tab-panel.
6.2.2.6 — Provision NTP protocol
This menu allows to enable the NTP (Network Time Protocol).

6 — Provisioning
Figure 6.68 — Provisioning NTP protocol
It is recommended that NTP be used to maintain consistent NE times within the network.
This allows for easy correlation of alarm/event/PM timestamps with actual time and with a
NMS. To minimize NTP traffic within the TMN network, each NE should use the next NE
toward the NMS as its primary time server.
Put a check mark in the NTP protocol field to enable the protocol and write in the Main
Server address field the IP address of the server, which is in charge to distribute the time
to all the NEs in the network. In the Spare Server address field write the IP address of the
Spare Server, if any.
The Server reachability field is a read-only field, which shows the reachability of the NTP
servers. The following information can appear:
• "Main server reachable"

• "Spare server reachable"
• "None servers reachable"

6 — Provisioning
• "Both servers reachable"
Click on Apply to send to the NE the NTP Configuration.
Refresh push-button can be used to update the screen.
6.2.2.7 — Provision NE Time
The user can synchronize the NE time from either the PC/laptop or Network Time Protocol
(NTP) servers. Time and date provisioning is accomplished using the NE Time
Configuration screens. See Figure 6.69 and follow the steps to provision Network
Equipment Time.

6 — Provisioning
Figure 6.69 — NE Time Provisioning
6.2.2.8 — Provision VLAN (if required)
To provision the VLAN management, if required, refer to VLAN management.
6.2.2.9 — Provision Cross-Connections

6 — Provisioning
The available cross-connections are listed in the following sections:
• To create the TDM cross-connections refer to TDM Cross-Connections.

• To create the SDH cross-connections with SDHACC - Transparent mode refer to SDH
Cross-Connections with SDHACC - Transparent mode.
• To create the SDH cross-connections with SDHCHAN - Channalized mode refer to
SDH Cross-Connections with SDHCHAN - Channalized mode.
• To create the ATM Cross-connections refer to ATM Cross-Connections.
• To create the LAG-LAG Cross-connections refer to LAG-LAG Cross-Connections.
• To create the Ring Cross-connections refer to Ring Cross-Connections.
6.2.2.10 — Provision AUX Cross-Connections
From the Configuration menu select AUX Cross-Connections.
Valid Cross Connections:
• Local User Service Cross-Connection

• Pass-through User Service Cross-Connection

6 — Provisioning
Figure 6.70 — Auxiliary Cross Connections menu
6.2.2.11 — Provision Ethernet Ring
See Ethernet Ring Configuration View.
6.2.2.12 — Provision LAG
See Figure 6.71. Follow the steps to provision the LAG.

6 — Provisioning
Figure 6.71 — LAG creation
6.2.2.13 — Provision QoS
See Figure 6.72 Follow the steps to provision the QoS.

6 — Provisioning
Figure 6.72 — QoS configuration
6.2.2.14 — Provision Ethernet Connectivity fault management
See Figure 6.73 Follow the steps to provision the Ethernet Connectivity fault management.

6 — Provisioning
Figure 6.73 — Ethernet Connectivity fault management
6.2.2.15 — Provision System
See Figure 6.74 Follow the steps to provision the system parameters as explained in System
Settings Menu.

6 — Provisioning
Figure 6.74 — System Setting

6 — Provisioning
6.2.2.16 — Provision Local NE IP Address
See Figure 6.75. Follow the steps to enter the NE IP address, allowing the network to
communicate with the NE.
Note: The figure shows IPv4.
Figure 6.75 — NE IP address provisioning
Note: After IP address change, the NE restarts.

6 — Provisioning
6.2.2.17 — Provision TMN in-band
To provision TMN In-band on the Core-E unit, see Settings tab-panel for TMN In-band.
6.2.2.18 — Provision TMN Ethernet Port
To provision TMN Ethernet Port on the Core-E unit, see Settings tab-panel for TMN
Ethernet port.
6.2.2.19 — Provision Ethernet Port 4 for TMN (if required)
To provision TMN Ethernet Port#4 on the Core-E unit, see Settings tab-panel for TMN
Ethernet Port #4.
6.2.2.20 — Provision IP Static Routing
See Figure 6.76. Follow the steps to provision.

6 — Provisioning
Figure 6.76 — IP Static Routing Provisioning

6 — Provisioning
6.2.2.21 — Provision OSPF Static Routing
See OSPF Static Routing Provisioning. Follow the steps to provision Open Shortest Path
First (OSPF) protocol static (automatic) routing.

6 — Provisioning
Figure 6.77 — OSPF Static Routing Provisioning
6.2.2.22 — IPv6 pre-provisioning

6 — Provisioning
See Figure 6.77. Follow the steps to provision Open Shortest Path First (OSPF) protocol
static (automatic) routing.
Figure 6.78 — IPv6 Pre-provisioning
Choose IPv6 Pre-provisioning to set IPv6 parameters before activating IPv6 on the NE. If
you activate IPv6 on the NE without performing pre-provisioning, default parameters will
be applied.
Caution: Mixed configuration of IPv4 and IPv6 NEs is not supported. Before activating IPv6,
ensure that all NEs in the network are IPv6 capable, that is, running R4.1.0 or higher. A
controlled activation will be required; see your local guidelines.
To pre-provision the NE for IPv6:
1. Choose IPv6 Pre-provisioning from the IP Configuration menu. The first window
opens. Configure the IP parameters for the NE and the TMN ports.

6 — Provisioning
Figure 6.79 — IPv6 Pre-provisioning step 1 of 3
2. Click on the Next button. The second window opens. Configure the OSPF and static
routing information.

6 — Provisioning
3. Click on the Next button. The third window opens, displaying a summary of your
settings.

6 — Provisioning
4. Perform one of the following:

a. Click on the Apply button to complete the configuration
b. Click on the <Prev button to return to the previous screen
c. Click on the Close button to close the window without completing the
provisioning.

7 — Maintenance and Trouble-clearing
7.1 — Introduction
This section contains information and procedures to aid in restoring the equipment to its
proper operating condition after it has been determined that a problem exists.
The following warnings and cautions apply while operating, performance testing,
troubleshooting, or repairing the 9500 MPR-E series radios.
Danger: Short circuits in low-voltage, low-impedance dc circuits can cause severe arcing
that may result in burns or eye injury. Remove rings, watches, and other metal jewelry
while working with primary circuits. Exercise caution to avoid shorting power input
terminals.
Caution: Units with the electrostatic-sensitive (ESS) symbol contain ESS devices. Store
these units in an antistatic container when not in use, and anyone handling a unit should
observe antistatic precautions. Refer to the Special Precautions pages in the front of the
instruction book for detailed handling information.
Note: Ensure that all antennas are properly aligned and waveguide is in good physical
condition.
Note: Before performing procedures that might in any way affect transmission, it is
recommended that the person performing the procedure understand the Rules and
Regulations pertaining to the equipment and be properly authorized to operate the
equipment.
7.2 — Maintenance Philosophy

This section provides information and procedures for equipment maintenance down to the
Card level. Card repair is not covered in this manual.
The use of maintenance procedures in this section may result from failure of a periodic
check, an alarm indication, or unacceptable performance.
7.3 — Personal Computer (PC)/Laptop

Connect the RJ45 Interface cable between WebEML connector on the Core-E Card and the
PC.
7.4 — Troubleshooting
This section provides guidance on:
• Before Going to Site Checklist

• Troubleshooting Basics
• Troubleshooting Path Problems
• Troubleshooting Configuration Problems
• Troubleshooting Ethernet Problems
• Troubleshooting TMN Problems
• Analyzing Ethernet Traffic
7.4.1 — Before Going to Site Checklist

Where possible, before going to site obtain the following information:
• Does the fault require immediate action?

• Determine who is the best-placed person to attend the fault.
• Confirm the nature and severity of the reported fault, its location, 9500 MPR-E type,
frequency band, high/low end ODU, capacity modulation and configuration
(nonprotected, protected, diversity). Ask:
• Is just one 9500 MPR-E link affected, or a number of links in the same
geographical area?
• Is the path down completely or is traffic passing but with a BER alarm?
• Is only one or a number of tributaries affected?

• Could the fault be in the equipment connected to 9500 MPR-E, rather than in 9500
MPR-E? Are there alarms on other, connected equipment?
• Is it a hard or intermittent fault?
• Do alarms confirm which end of an alarmed link is faulty?
• Could the weather (rain, ice, high wind, temperature) be a factor in the reported fault?
Note: If the fault suggests a rain fade or other weather related fade condition and it
matches the prevailing weather conditions, do not take any action until the weather
abates.
• Does link history suggest any fault trends?

• Does the fault history for the link indicate a likely cause?
• Is the 9500 MPR-E link newly installed?
• Has there been any recent work done on the link?
• Ensure that you have with you:
• Appropriate spares. Where an equipment failure is suspected, these should include
replacement Cards/plug-ins and ODU. If an ODU is suspected then local/national
climbing safety requirements must be adhered to.
• A laptop PC loaded with WebEML, and an Ethernet cable. If an Ethernet
connection is to be used, you need the 9500 MPR-E Node/Terminal IP address and
also the addresses for any remote sites to be accessed.
• If login security has been enabled, you need the ‘engineer’ password for the local
and also any remote sites to be accessed.
• Any special test equipment that may be needed, such as a BER tester.
• Toolkit.
• Key(s) for access to the site.

7.4.2 — Troubleshooting Basics

This section provides general guidance on 9500 MPR-E troubleshooting:
• Check front-panel LED indications. These provide summary alarm indications,

which can help narrow down the location and type of failure. Refer to Operation section
for details.
• Where a Status LED on a plug-in is off (unlit), but power to the MS is confirmed
by LEDs on other plug-ins, check the seating of the affected plug-in.
• Check Main Screen. When logging into 9500 MPR-E with WebEML, the opening
screen is the Main Screen. Use the information provided in menu Diagnosis → Alarms
→ NE alarms and in menu Diagnosis → sing → Event Log to check for severity and
problem type. See Table 7.1, Table 7.2 and Table 7.3 for probable cause and
recommended action.
Table 7.1 — Alarm Matrix
Equipment Alarm Description Configuration/ Alarm Most Probable Cause Action
1+0 1+1 EPS
MSS-4/MSS-8 Battery Fail or Minor N/A Battery in MSS-8 shelf is Replace battery
Missing (MSS-8 missing or has failed
only)
Secondary Minor Secondary battery in Replace battery

Battery Fail or MSS-8 shelf missing or
Missing (MSS-8 has failed
only)
Equipment Major Equipment does not Install correct flash

Mismatch match shelf configured memory
in memory
Flash card failure Minor SNMPv3 agent setup file Replace flash card
writing failure
FANS Card Fail Major Minor Fan Card failed Replace Fan Card
FAN-1
Card Missing Major Major Fan Card is missing from Install Fan Card
A-FANS slot
Equipment Major Major Card in slot does not Install correct

mismatch match card configured configured card
in memory
Unconfigured Minor Minor Card in slot is not Provision card

Equipment provisioned (enabled)

Table 7.1 — Alarm Matrix (Continued)
1+0 1+1 EPS
Core-E Card Card Fail Major Minor Core-E card failed Replace Core-E Card
Equipment N/A Minor Card in slot does not Install correct

Mismatch match card configured configured card
in Core-E memory
Core-E Card Card Missing N/A Minor Core-E card is missing Install Core-E Card
(continued) from slot in slot
SFP fail Major Minor The SFP optional plug-in Replace SFP
has failed
SFP missing alarm Major Minor The SFP optional plug-in Install the plug-in in
is provisioned, but not the SFP slot
present
SFP Underlying Major Major On detection of card Replace SFP plug-in

Resource failure the SFP plug-in
Unavailable emits a communication
Alarm notification
showing the
transmission resources
are affected by the
equipment failure
Unconfigured N/A Minor Card in slot is not Provision card

Equipment (card provisioned (enabled)
or SFP)
LOS on ETH TMN Minor Minor No Ethernet input signal Check link partner
Interface detected on ETH 4 on and cable between
Core-E Card link partner and ETH
4 connector
LOS on GBEth - -
interface (User
and Radio)
LOS on Gigabit Major Minor Loss of Ethernet is Check link partner

ETH Interface detected on ETH 1-4 on and cable between
Core-E Card link partner and ETH
1-4 connector

1+0 1+1 EPS
Core-E Card LOS on LAG Major Minor Loss of Ethernet is Check link partner
(continued) Interface detected on LAG and cable between
interface on Core-E link partner and
Card Core-E connector
Lockout Switch None ABN A Lockout Switch has Wait for the request
been executed for the to be released
protection group
Firmware Minor Minor Status of download Wait for

Download In downloading to
Progress complete
EC Software Minor Minor Incompatibility Download correct

version mismatch between EC software software version
and programmable
components software
LOS on Sync Minor Minor No sync clk detected at Check sync source
Interface Sync in port on Core-E and cable between
Card sync source and
Sync in port
Degraded Signal Minor Minor Sync clk errors detected Check sync source
on Sync Interface at Sync in port on Core- for errors
E Card
Degraded Signal Minor Minor Sync clk errors detected Check LAG ports for
on LAG Interface at LAG interface on errors
Core-E Card
License Mismatch Major Major Wrong flash card Install correct flash
for Equipment installed on Core-E Card card for license
Provisioned

1+0 1+1 EPS
Core-E Card Underlying Major Major On detection of card Replace Core-E card
(continued) Resource failure the E1 port,
Unavailable Ethernet port, Radio
(URU) port objects emit a
communication Alarm
notification showing the
are affected by the
equipment failure
Bandwidth N/A Warning An ERPS instance has Check and

Degrade for entered a protection troubleshoot the
Protection Switch state radio alarms on the
nodes in the
Ethernet Ring
Duplicated IPv6 Major Major Duplication of IPv6 Check IP addresses

Address Detected Global Unicast address and resolve the
on local detected duplication
Ethernet, TNM in-
band and PPP
interfaces
Forced Switch None ABN A forced switch has Wait for the request
been executed for a to be released
protection group
MSS/CORE (MSS- Card Fail Major NA MSS/Core card failed Replace MSS-1
1)
Firmware Minor NA Status of download Wait for
Progress complete
License Key Minor NA Wrong flash card is Install correct flash

Mismatch for installed card for license
Equipment
Provisioned

1+0 1+1 EPS
MSS/CORE (MSS- Loss of ESMC Minor NA Loss of Ethernet Re-configure the

1) Synchronization provisioned
(continued) Message Channel. The Synchronization SSM
alarm is applicable to values at both ends
Radio interfaces of the hop to the
configured with SSM desired value
support enabled and
assigned as a
synchronous clock
source input.
Loss of Signal Major NA Loss of Ethernet signal Check link partner

when no Ethernet input and cable between
signal is detected on the link partner and
port. Also reported Ethernet connector
when there is a
communication
problem with the
remote peer (for
example, link down
condition)
Software version NA NA Incompatibility Download correct

mismatch between EC software software version
and programmable
components software
E1 Access Card Card Fail Major Minor Failure of E1 Access Replace E1 Access
Card Card
Equipment Major Minor Card in slot does not Install correct

Mismatch match Card configured configured card
in Core-E memory
Card Missing Major Minor E1 Access Card is Install E1 Access

missing from slot Card in slot
Unconfigured Major Major Card is not Enabled on Enable card

Equipment the Settings screen
LOS on PDH Major Minor No E1 input signal Check E1 source

Tributary detected on any one or and/or cable
more of 32 lines

1+0 1+1 EPS
E1 Access Card Lockout Switch None ABN A Lockout Switch has Wait for the request
(continued) been executed for the to be released
protection group
Loopback None ABN A loopback has been Wait for the

activated at the near loopback timeout to
end expire
Degraded Signal Minor Minor Low quality sync signal Replace E1 Access
for E1 Access Card Card
AIS on PDH Major Major AIS detected by the Check for upstream
Tributary (RX) receive circuits on one E1 source for errors
or more E1 lines,
indicating upstream
failure
AIS on PDH Major Major AIS detected on one or Check E1 source

Tributary (TX) more E1 lines at input to
PDH 32xE1 Access Card
Loss of CESoETH Major Major Packets are not being 1. Check/

Frame received by the troubleshoot
emulation circuits far end alarms
2. Replace alarmed
E1
Access Card

Progress complete
protection group
E1 Access Card Underlying Major Major On detection of card Replace E1 Access

(continued) Resource failure the E1 port card
Unavailable objects emit a
(URU) communication Alarm
are affected by the
equipment failure

1+0 1+1 EPS
MSS/E1 (MSS-1) Card Fail Major NA Failure of E1 Access Replace E1 Access

Card Card
AIS on Receive Major NA AIS detected by the Check for upstream

Side receive circuits, E1 source for errors
indicating upstream
failure
AIS on Transmit Major NA AIS detected on one or Check E1 source

side more E1 lines at input
Loss of CESoETH Major NA Packets are not being 1. Check/

2. Replace MSS-1
Loss of Frame Major NA Loss of frame detected Check E1 source

(e.g. detected for Rx
and Tx directions)
Loss of Signal Major NA No E1 input signal Check E1 source

detected and/or cable
Retiming Buffer Major NA Retiming buffer

Overflow overflow for E1
tributary
Sync Degrade Minor NA Frequency of the source Replace MSS-1

signal is degraded
Sync Fail Minor NA Received source signal Configure a

is not suitable as a sync different sync
source. source.
MSS/E1 (MSS-1) Underlying Major NA On detection of card Replace E1 Access

(continued) Resource failure the E1 port card
are affected by the
equipment failure
Underlying Major NA Transmission resources -

Resource affected by equipment
Unavailable failure
Service

1+0 1+1 EPS
STM-1 Access Card Fail Major Minor Failure of STM-1 Access Replace STM-1
Card Card Access Card
(transparent)
Equipment Major Minor Card in slot does not Install correct
in Core-E memory
Card Missing Major Minor STM-1 Access Card is Install STM-1 Access
protection group

LOS on STM-1 Major Minor No STM-1 input signal Check STM-1 source
more of 32 lines
Tx Out of STM-1 Major Minor Loss of STM-1 frame Check STM-1 source
Frame (OOF) alignment on each
incoming STM-1 channel
detected according to
G.783
Tx Loss of STM-1 Major Minor Loss of frame from Check STM-1 source
frame (LOF) external line side

1+0 1+1 EPS
STM-1 Access Tx Regeneration Major Minor RS-TIM (regeneration Check STM-1 source
Card section trace section trace identifier
(transparent) identifier mismatch) detected on
(continued) mismatch (J0) each STM-1 channel
from external line
which is known as J0
byte in regeneration
section overhead
Tx Multiplex Major Minor Multiplex Section AIS Check STM-1 source

section alarm (MS-AIS) specified as all
indication signal "1"s in the entire STM-1
(MS-AIS) from external line,
excluding the STM-1
RSOH
Tx Multiplex Major Minor From external line. The Check STM-1 source
section remote Multiplex Section
defect indication Remote Defect
(MS-RDI) Indication (MS-RDI) is
used to return an
indication to the
transmit end that the
received end has
detected an incoming
section defect or is
receiving MS-AIS
Tx Excessive BER Major Minor In the direction from Check STM-1 source
(HBER) external line, when the
line BER exceeds 5*10-5
Sync Fail Major Minor Managed only if the Check STM-1 source
addressed STM-1 has
been configured as
primary/secondary
synchronization source

1+0 1+1 EPS
STM-1 Access Sync Degraded Major Minor Managed only if the Check STM-1 source
Card signal addressed STM-1 has
(transparent) been configured as
(continued) primary or secondary
Rx Loss of STM-1 Major Minor Loss of frame to Check STM-1 source

Rx Multiplex Major Major Multiplex Section AIS Check STM-1 source

section alarm (MS-AIS) is specified as
indication signal all "1"s in the entire
(MS-AIS) STM-1 to external line,
excluding the STM-1
RSOH
Rx Excessive BER Major Major In the direction to Check STM-1 source

Loss of CESoETH Major Major Packets are not being 1. Check/

2. Replace alarmed
STM-1 Access
Card

Progress complete
Underlying Major Major On detection of card Replace STM-1

Resource failure the STM-1 port Access card
are affected by the
equipment failure
STM-1 Access Forced Switch None ABN A forced switch has Wait for the request
Card been executed for a to be released
(transparent) protection group
(continued)

1+0 1+1 EPS
STM-1 Access Card Fail Major Minor Failure of STM-1 Access Replace STM-1
Card Card Access Card
(channalized) Equipment Major Minor Card in slot does not Install correct
in Core-E memory
Card Missing Major Minor STM-1 Access Card is Install STM-1 Access

LOS on STM-1 Major Minor No STM-1 input signal Check STM-1 source
more of 32 lines
Tx Out of STM-1 Major Minor Loss of STM-1 frame Check STM-1 source
Frame (OOF) alignment on each
incoming STM-1 channel
detected according to
G.783
Tx Loss of STM-1 Major Minor Loss of frame from Check STM-1 source
Tx Regeneration Major Minor RS-TIM (regeneration Check STM-1 source

section trace section trace identifier
identifier mismatch) detected on
mismatch (J0) each STM-1 channel
from external line
which is known as J0
byte in regeneration
section overhead

1+0 1+1 EPS
STM-1 Access Tx Multiplex Major Minor Multiplex Section AIS Check STM-1 source
Card section alarm (MS-AIS) specified as all
indication signal "1"s in the entire STM-1
(channalized)
(MS-AIS) from external line,
(continued) excluding the STM-1
RSOH
Tx Multiplex Major Minor From external line. The Check STM-1 source
section remote Multiplex Section
defect indication Remote Defect
(MS-RDI) Indication (MS-RDI) is
used to return an
indication to the
transmit end that the
received end has
detected an incoming
section defect or is
receiving MS-AIS
Tx Excessive BER Major Minor In the direction from Check STM-1 source
protection group
Sync Fail Major Minor Managed only if the Check STM-1 source
addressed STM-1 has
been configured as
primary/secondary
Sync Degraded Major Minor Managed only if the Check STM-1 source
signal addressed STM-1 has
been configured as
primary or secondary

1+0 1+1 EPS
STM-1 Access High Order Path Major Minor The AU4-AIS is Check STM-1 source
Card alarm indication specified as all "1"s in
signal (AU4-AIS) the entire high order
(channalized)
path Administrative
(continued) Unit. The alarm
becomes significant and
must be reported if
STM-1 LOS, STM-1 LOF,
STM-1 TIM, or MS-AIS
alarm is not present. As
consequent action, any
E1 extracted from STM-
1 will be replaced with
AIS (and then circuit
emulated according the
provisioned settings).
Loss of Major Minor This alarm is raised Check STM-1 source

Administrative when 8 to 10
Unit Pointer consecutive invalid
(AU4-LOP) pointers is received or 8
to 10 consecutive NDF is
received. The alarm
must be reported if
STM-1 TIM, MS-AIS, or
AU4-AIS alarms are not
present. As

1+0 1+1 EPS
STM-1 Access High Order Signal Major Minor This alarm is raised Check STM-1 source
Card Label Mismatch when the value of C2
(VC4 -SLM) byte in VC-4 POH is
(channalized)
different between
(continued) received VC-4 and Tx
VC-4. The vale of C2
byte should be 0x02 for
E1 mapping for
channelized SDH. The
alarm becomes
significant and must be
reported if STM-1 LOS,
STM-1 LOF, STM-1 TIM,
MS-AIS, AU4-AIS or AU4-
LOP alarms are not
present. As
protection group

1+0 1+1 EPS
STM-1 Access Loss of Major Minor The value of H4 byte in Check STM-1 source
Card Multiframe of VC-4 POH is not in the
Tributary Unit range (01H-04H) or H4
(channalized)
(VC4-LOM) multiframe is not
(continued) recovered within 'm' VC-
4 frames, a LOM defect
shall be declared; 'm'
shall be in the range of
8 to 40 and is not
configurable. The alarm
must be reported if
STM-1 TIM, MS-AIS, AU4-
AIS, AU4-LOP or VC4-
SLM alarms are not
present. As consequent
action, any E1
extracted from STM-1
will be replaced with

1+0 1+1 EPS
STM-1 Access Low Order Path Major Minor The TU12-AIS is Check STM-1 source
Card alarm indication specified as all "1"s in
signal (TU12-AIS) the entire low order
(channalized)
path Tributary Unit.
(continued) The alarm becomes
MS-AIS or AU4-AIS, AU4-
LOP, VC4-SLM or VC4-
LOM alarms are not
action, the relevant E1
Loss of Tributary Major Minor This alarm is raised Check STM-1 source
Unit Pointer when 8 to 10
(TU12-LOP) consecutive invalid
pointers is received or 8
to 10 consecutive NDF is
received. The alarm
must be reported if
STM-1 TIM, or MS-AIS,
AU4-AIS, AU4-LOP,
VC4-LOM VC4-SLM or
TU12-AIS alarms are
not present. As
consequent action the
relevant E1 will be
replaced with AIS (and
then circuit emulated
according the

1+0 1+1 EPS
STM-1 Access Low Order Path Major Minor This alarm is raised Check STM-1 source
Card Signal Label when the value of V5
Mismatch [bit5-7] in VC-12 POH is
(channalized)
(VC12-SLM) different from the
(continued) expected value (010:
asyncronous mapping).
The alarm becomes
MS-AIS, AU4-AIS, AU4-
LOP, VC4-SLM, VC4-
LOM, TU12-AIS or TU12-
LOP alarms are not
action the relevant E1
provisioned settings)
E1 in STM-1 Tx Major Minor It reports the Alarm Check STM-1 source

Alarm Indication Indication Signal
Signal detected on E1 in STM-1
(E1-tx AIS) on ingressing (Tx side)
and it is detected
according to G.775-
sect.4. The alarm
must be reported if
STM-1 TIM, MS-AIS, HP-
AIS or LP-AIS alarm is
not present.

1+0 1+1 EPS
STM-1 Access E1 in STM-1 Loss Major Minor Due to Loss-of-CESoETH Check STM-1 source
Card of CESoETH alarm detection an AIS
Frames is inserted as
(channalized)
consequent action. AIS
(continued) insertion: set all '1' on
data.
E1 in STM-1 Rx Major Minor It reports the Alarm Check STM-1 source

Alarm Indication Indication Signal
Signal detected on each E1 in
(E1-rx AIS) STM-1 on egressing (Rx
side) and it is detected
according to G.775-
sect.4. The alarm
must be reported if a
Loss of CESoETH Frame
alarm is not present.
E1 in STM-1 Rx Major Minor It reports the loss of Check STM-1 source

Loss Of Frame frame detected on
(E1-rx LOF) each E1 in STM-1 on
egressing (Rx side) and
it is detected according
ITU-T G.706-sect.4, and
G.706-Annex_B. The
alarm becomes
reported if the E1 is
configured as framed
and a Loss of CESoETH
Frames or E1-rx AIS
alarms are not present.
Due to alarm detection
an AIS must be inserted
as consequent action.
AIS insertion: set all '1'
on data.

1+0 1+1 EPS
STM-1 Access Firmware Minor Minor Status of download Wait for

Card Download In downloading to
Progress complete
(channalized)
(continued) Underlying Major Major On detection of card Replace STM-1
Resource failure the STM-1 port Access card
are affected by the
equipment failure
16E1DS1 ASAP Card Fail Major - Failure of ASAP Card Replace ASAP Card
Card Equipment Major - Card in slot does not Install correct
in Core-E memory
Card Missing Major - ASAP Card is missing Install ASAP Card in

from slot slot
Unconfigured Major - Card is not Enabled on Enable card

Firmware Minor - Status of download Wait for

Progress complete
Loss Of Signal Major - Loss of signal on each Check E1 source

(LOS) incoming E1 signal and/or cable
(detected according to
ITU-T G.775-sect.4)
Tx Alarm Major - Alarm Indication Signal Check E1 source

Indication Signal detected on each
(Tx AIS) incoming E1 signal (Tx
side) (detected
according to ITU-T
G.775-sect.4)

1+0 1+1 EPS
16E1DS1 ASAP Loss Of Frame Major - Loss of frame on each Check to CRC4
Card (LOF) incoming E1 signal multiframe
(detected according to alignment of the Far
(continued)
ITU-T G.706-sect.4) End equipment
Loss of Cell Major - Loss of ATM cell Check the ATM

Delineation (LCD) delineation on each scrambling of the
incoming E1 signal, Far End equipment
when the E1 port is used
as physical layer for
ATM (detected
according to ITU-T
I.432)
Loss of IMA Frame Major - Loss of IMA Frame on Check the IMA
(LIF) each incoming E1 configuration of the
signal, when the E1 port Far End equipment
is used as IMA link
IMA Standard AF-PHY-
0086.000)
Link Out of Delay Major - It reports the event Check the

Synchronization that, when the E1 port synchronization of
(LODS) is used as IMA link, it is the Far End
not synchronized with equipment
the other links within
the IMA group
0086.000)
16E1DS1 ASAP RDI/Link Failure Major - It reports, when the E1 Check the Far End
Card port is used as IMA link, equipment
the OR of other alarms
(continued)
that are foreseen by
0086.000:
RFI-IMA
Tx-Mis-Connected
Rx-Mis-Connected
Tx-Unusable-FE
Link Rx-Unusable-FE

1+0 1+1 EPS
16E1DS1 ASAP IMA Group Trail Major - It reports, for a Check the Far End
Card Signal Fail (TSF) configured IMA Group, equipment
the event that its Group
(continued)
Traffic State Machine is
'down', that is NE and FE
Group State Machine
are both NOT in
"operational" state (IMA
Standard AF-PHY-
0086.000)
IMA Group TSF Alarm is
also generated by OR of
the following alarms
(IMA Standard AF-PHY-
0086.000):
Tx-Unusable-FE
Link Rx-Unusable-FE
Group Start-up-FE
Group Config-Aborted
Group Config-Aborted-
FE
Group Insufficient-Links
Group Insufficient-
Links-FE
Group Blocked-FE
Group GR-Timing-
Mismatch
Underlying Major Major On detection of card Replace 16E1DS1

Resource failure the E1 port ASAP
Unavailable objects emit a Card
are affected by the
equipment failure

1+0 1+1 EPS
EAS Card Card Fail Major - EAS card failed Replace EAS Card
SFP module failed
Replaceable Unit Major - Card in slot does not Install correct

Type Mismatch match card configured configured card
in Core-E memory
Card Missing Major - EAS card is missing from Install EAS Card in
slot slot
SFP module fail Major - The SFP optional plug-in Install the plug-in in
present
Loss Ethernet Minor - Reported if there is a Check SSM settings

Synchronization loss of the Ethernet
Messaging Synchronization
Channel Message Channel. The
alarm is applicable to
User Ethernet
interfaces configured
with SSM support
enabled and is assigned
as a synchronous clock
source input.
Unconfigured N/A - Card in slot is not Provision card or

Equipment provisioned (enabled) SFP
SFP is not provisioned
(enabled) but is present
LOS on Gigabit Major - Loss of Ethernet is Check link partner

ETH Interface detected and cable between
link partner and
Ethernet connector

Download On downloading to
Going complete
EAS Card Underlying Major - On detection of card Replace EAS card

(continued) Resource failure the Ethernet
Unavailable port objects emit a
are affected by the
equipment failure

1+0 1+1 EPS
EASv2 Card Card Fail Major - EASv2 card failed Replace EASv2 Card
SFP Module fail
Replaceable Unit Major - Card in slot does not Install correct

Type Mismatch match card configured configured card
in Core-E memory
Card Missing Major - EASv2 card is missing Install EASv2 Card in

from slot slot
SFP missing alarm Major - The SFP optional plug-in Install the plug-in in
present
Loss Ethernet Minor - Reported if there is a Check SSM settings

Synchronization loss of the Ethernet
Messaging Synchronization
Channel Message Channel. The
alarm is applicable to
User Ethernet
interfaces configured
with SSM support
enabled and is assigned
as a synchronous clock
source input.
Unconfigured N/A - Card in slot is not Provision card or

Equipment provisioned (enabled) SFP
SFP is not provisioned
(enabled) but is present

1+0 1+1 EPS
EASv2 Card LOS on Ethernet Major - Loss of Ethernet is Check link partner
(continued) Interface detected and cable between
link partner and
Ethernet connector
Sync Degrade on Minor - Reported if the Check the source

Ethernet frequency of the source signal interface.
Interfaces signal is Degraded.
Managed only if the
interface has been
configured as a
primary/secondary
synchronization source.
Sync Fail on Minor - Reported if the Reconfigure the

Ethernet received source signal is Sync Source.
Interfaces not suitable as a Sync
Source. Managed only if
the interface has been
configured as a
primary/secondary
synchronization source.

Download On downloading to
Going complete
Power Supply Fail Major - MPT Power Supply Fail Check the power
detection of an Open- supply to the MPT.
Circuit or Over-Current
condition on a power
supply port. It must be
reported only after an
MPT has been
provisioned on the
EASv2.
Fans Unit Card Fail Major - Fan failed Replace fan unit
Card Missing Major - Fan unit is missing from Install fan unit
slot
Fans Unit Unconfigured Minor Minor Unit is not Enabled on Enable fan unit
(continued) Equipment the Settings screen

Table 7.2 — Modem Card and ODU300 Alarm Matrix
Equipment Alarm Description Configuration/Alarm Most Probable Cause Action
1+0 1+1 HS 1+1 FD
Modem Card Card Fail Major Minor Minor Modem Card failed Replace Modem Card
Equipment Minor Minor Minor Card in slot does not Install correct
Mismatch match card configured card
configured in Core-E
memory
Card Missing Major Minor Minor Modem Card is Install Modem Card in
missing from slot slot
Unconfigured Minor Minor Minor Card is not Enabled Enable card

Equipment on the Settings
screen
PNU Cable Loss Major Minor Minor Bad cable Check/repair IF

connection at IF in/ cable connection on
out connector on alarmed Modem Card
Modem Card
Modem Card Loss of Radio Minor Minor Minor Far end problems, 1. Switch far end
(continued) Frame RF path problems, equipment (in a
or local circuit
protected
failures have caused
system).
BER to increase to
the point that If alarm clears,
frames are being replace far end
lost off-
line Modem Card.
2. Check/
troubleshoot
far end alarms
3. Replace alarmed
Modem Card
Loss of Alignment N/A Minor Minor Delay between main 1. Replace main
and protect RF Radio
paths detected Modem Card
2. Replace protect
Modem Card
3. Replace main ODU
4. Replace protect
ODU
Demod Function Major Minor Minor Internal receive Replace Modem Card
Fail circuit failure

Table 7.2 — Modem Card and ODU300 Alarm Matrix (Continued)
1+0 1+1 HS 1+1 FD
Modem Card High BER Major Minor Minor Bit Error Rate 1. Verify RF path is
(continued) threshold (10E-4) clear, antenna is
exceeded on RCVR aligned, and no
input circuits on existing weather
modem related problems
2. Verify RSL is above
RCV threshold. If not
– check upstream
transmitter output/
troubleshoot
transmitter
Early Warning N/A Minor Minor 10E-9 BER detected No action is required
at this time. Monitor
receive signal for
increased degrading
Link Identifier Major Major Major Link identifier Set numbers at both
Mismatch number provisioned ends of hop to match
on Modem Card
settings screen is
different from link
identifier number
provisioned at other
end of hop
TCA on Radio Link N/A N/A Major Alarm threshold Switch far end
exceeded on equipment (in a
standby Modem protected system). If
Card alarm clears, replace
far end off-line
Modem Card
TCA on Radio Hop Major N/A Minor Alarm threshold

exceeded on
standby Modem
Card after switching
from main to
standby

1+0 1+1 HS 1+1 FD
Modem Card UAT on Radio Link N/A N/A Major 10 consecutive SES Switch far end
(continued) (unavailable time equipment (in a
period) detected on protected system). If
main Modem Card alarm clears, replace
far end off-line
Modem Card
UAT on Radio Hop Major N/A Minor 10 consecutive SES

(unavailable time
period) detected on
standby Modem
Card after switching
from admin to
standby
Firmware Minor Minor Minor Download status Wait for downloading

Download In to complete
Progress
Degraded Signal Minor Minor Minor Low quality sync Replace Modem Card
signal from Modem
Card
License Mismatch Major Major Major Modem card type Replace Modem Card
for Equipment does not match card with correct card
Provisioned type stored in type
memory on the
Core-E Card flash
card
Underlying Major Major Major On detection of Replace Modem Card

Resource card failure the
Unavailable Radio port objects
(URU) emit a
communication
Alarm notification
showing the
transmission
resources are
affected by the
equipment failure

1+0 1+1 HS 1+1 FD
ODU300 Card Fail Major Minor Minor ODU failed Replace ODU
Equipment Major Minor Minor ODU does not match Replace ODU
Mismatch ODU configured in
Core-E memory
RCV Function Fail Major Minor Minor ODU receiver circuit Replace ODU
failed
RF Frequency Major Minor Minor Frequency out-of- Re-configure

Mismatch range of configured frequency
Tx frequency
Shifter Frequency Major Minor Minor Configured shifter Re-configure shifter

Mismatch value not supported value
by ODU
TX Power Minor Minor Minor Configured TX Re-configure Tx

Mismatch power value not power value
supported by ODU
Software Minor Minor Minor Software version on Download correct

Mismatch ODU does not match software version
software version on
Core
ODU Not Minor Minor Minor Loss of 1. Replace ODU

Responding communication with 2. Replace alarmed
ODU
Modem Card
Firmware Minor Minor Minor Download status Wait for downloading

Download In to complete
Progress
Table 7.3 — MPT Access Peripheral Card, MPT-HC V2/MPT-XP, and MPT- HLS Alarm Matrix
Equipment Alarm Configuration/Alarm Most Probable Cause Action

Description
1+0 1+1 HS 1+1 FD
MPT Access Card Fail Major - - MPT Access Card Replace MPT Access
Card failed Card
Equipment Major - - Card in slot does not Install correct

Mismatch match card configured card
memory

Table 7.3 — MPT Access Peripheral Card, MPT-HC V2/MPT-XP, and MPT- HLS Alarm Matrix (Continued)

Description
1+0 1+1 HS 1+1 FD
Card Missing Major - - MPT Access Card is Install MPT Access Card
missing from slot in slot
Lockout Switch None ABN ABN A Lockout Switch has Wait for the request to
been executed for be released
the protection group
Unconfigured Minor - - Card is not Enabled Enable card

Equipment on the Settings
screen
MPT Power Major - - Power Supply Failure Check/repair the cable

Supply Failure connection. If ok,
replace MPT-HC
Loss Of Ethernet Major - - Loss of the incoming Check the cable

Signal Ethernet signal (the connection. If ok,
signal is missing) or a replace the MPT Access
communication unit
problem with the
remote peer (i.e. the
communication has
not been established
for physical problem
on cable or interface
-> link down)


Description
1+0 1+1 HS 1+1 FD
MPT Access Ethernet Link Minor - - Partial failure of Check the cable
Card Error electrical or optical connection. If ok,
(continued) cable for the GbEth replace the MPT Access
port unit
Forced Switch None ABN ABN A forced switch has Wait for the request to
been executed for a be released
protection group
Degraded Signal Minor - - This alarm is active Check the cable

of the MPT only when the
Ethernet interface is selected
Interface as Primary or
Secondary
synchronization
source
Firmware Minor - - Download status Wait for downloading to

Download In complete
Progress
Remote Defect Minor None None An RDI is received on Check the remote radio
Indication a radio direction from
the remote end of the
link. Valid for LAG
and ERPS
MPT-HC Card Fail Major Minor Minor MPT-HC failed Replace MPT-HC
V2/MPT-XP
ATPC Loop Major None None ATPC High Power Wait until the active
Problem timeout receiver is no longer
receiving additional
transmitter power
Equipment Major Minor Minor MPT-HC does not Replace MPT-HC

Mismatch match MPT-HC
memory
RCV Function Major Minor Minor MPT-HC receiver Replace MPT-HC

Fail circuit failed
RF Frequency Major Minor Minor Frequency out-of- Re-configure frequency

Mismatch range of configured
Tx frequency


Description
1+0 1+1 HS 1+1 FD
MPT-HC Shifter Major Minor Minor Configured shifter Re-configure shifter

V2/MPT-XP Frequency value not supported value
(continued) Mismatch by MPT-HC
TX Power Minor Minor Minor Configured TX power Re-configure TX power

Mismatch value not supported value
by MPT-HC
Modulation Major Minor Minor The modulation Change the modulation

parameters parameters already parameters
Mismatch configured and stored
in the MPR DB are not
actually supported by
MPT
Software Minor Minor Minor Software version on Download correct

Mismatch MPT-HC does not software version
match software
version on Core
MPT-HC Not Minor Minor Minor Loss of 1. Replace MPT-HC

Responding communication with 2. Replace alarmed
MPT-HC MPT Access Card
Firmware Minor Minor Minor Download status Wait for downloading to

Progress
Forced Adaptive None ABN ABN Manual Forced Wait for the request to
Modulation Adaptive Modulation be released
command is executed
protection group


Description
1+0 1+1 HS 1+1 FD
MPT-HC Loss of Radio Major Minor Minor Far end problems, RF 1. Switch far end
V2/MPT-XP Frame path problems, or equipment (in a
(continued) local circuit failures protected system). If
have caused BER to alarm clears, replace
increase to the point far end off-line
that frames are being MPT-HC.
lost 2. Check/troubleshoot
far end alarms
3. Replace alarmed
MPT-HC
Loss of N/A Minor Minor Delay between main 1. Replace main MPT-
Alignment and protect RF paths HC
detected 2. Replace protect
MPT-HC
Demod Function Major Minor Minor Internal receive Replace MPT-HC

High BER Major Minor Minor Bit Error Rate 1. Verify RF path
threshold (10E-4) is clear, antenna is
exceeded aligned, and no existing
weather-related
problems
RCV threshold. If not
check upstream
transmitter output/
troubleshoot
transmitter
Early Warning N/A Minor Minor 10E-9 BER detected No action is required at
this time. Monitor
receive signal for
increased degrading


Description
1+0 1+1 HS 1+1 FD
MPT-HC Incompatible Major Minor Minor Frequency out of Modify the frequency
V2/MPT-XP Frequency range of configured
(continued) frequency
Incompatible Major Minor Minor Configured Update the modulation

Modulation modulation not
supported by MPT
Incompatible Major Minor Minor Configured RTPC/ Modify the power

Power ATPC Tx power value configuration
or ATPC Rx power
threshold value not
supported by MPT
Incompatible Major Minor Minor Configured shifter Modify the shifter value
Shifter value not supported
Internal Major Minor Minor Loss of Replace MPT-HC

Communication communication with
Problem MPT
Loss of Radio None Major Major The radio direction is Check the RPS cable
Protection affected by a failure
that RPS cannot
recover
LOS on LAG Major Minor Minor Loss of Ethernet is Check link partner and
Interface detected on LAG cable between link
interface partner and MPT
connector
Loopback None ABN ABN A loopback has been Wait for the loopback
activated at the near timeout to expire
end
Loss of N/A Minor Minor Delay between main 1. Replace main MPT-
Alignment and protect RF paths HC
detected. Not 2. Replace protect MPT-
applicable for MPT HC
connected to Core-E
or EAS.


Description
1+0 1+1 HS 1+1 FD
MPT-HC Link Identifier Major Major Major Link identifier Set numbers at both
V2/MPT-XP Mismatch number provisioned ends of hop to match
(continued) is different from link
identifier number
end of hop
MPT Loop Minor Minor Minor Communication Check the radio hop
Communication problem between the
alarm local MPT and the
remote MPT for all
the functionalities
requiring a
communication loop
(ATPC, ACM, Pre-
distorsion)
Sync Degraded Minor Minor Minor This alarm can raise if Check the radio hop
signal the addressed Radio
interface has been
configured as
primary/secondary
synchronization
source. It is active if
the frequency of the
clock recovered from
radio Rx signal is
mistuned
Overflow Major None None The level of demand Update the configured
Bandwidth is higher than the cross-connections
MPT net capacity
link. Valid for LAG
and ERPS


Description
1+0 1+1 HS 1+1 FD
MPT-HC Software Warn None None Software version on Check software version
V2/MPT-XP version MPT does not match
(continued) mismatch software version on
Core
Standby None Warn Warn Standby Software Check software version

Software version on MPT does
version not match software
mismatch version on Core
Degraded Signal Minor None None Sync clk errors Check LAG ports for
on LAG detected at LAG errors
Interface interface
Radio Major None None Radio encryption Check encryption

Encryption enabled on only one settings on both sides of
Mismatch side of radio link the link
Sync Fail Minor None None Received source Configure a different

signal is not suitable sync source.
as a sync source.
TCA Major Minor Minor TCA alarm is emitted

on a counter basis.
Applies to
performance
parameters with an
accumulation period
of 24 hours and 15
minutes
Tx Mute ABN None None A manual or Wait for the mute

automatic mute timeout to complete
command has been
executed
Underlying Major None None Transmission Check the radio hop

Resource resources affected by
Unavailable equipment failure

Service


Description
1+0 1+1 HS 1+1 FD
MPT-HC XPIC Cable Loss Minor None None XPIC Cable Check the XPIC cable
V2/MPT-XP Connection defect
(continued) detected
MPT-HLS Battery Fail or Minor N/A N/A Battery in MPT-HLS is Check battery supply
Missing missing or has failed switch or change
battery
Secondary Minor N/A N/A Secondary battery in Check battery supply

Battery Fail or MPT-HLS missing or switch or change
Missing has failed battery
FAN Card Fail Major Major Major FAN unit failed Replace FAN unit
Card Fail Major Minor Minor MPT-HLS failed Replace MPT-HLS
Rx diversity module Replace MPT-HLS

failed
SFP module failed Replace MPT-HLS
Card Missing Major Minor Minor SFP is missing from Install SFP
MPT-HLS. Reported
to provisioned board
when RPS is
provisioned.
Combiner Loss Minor Minor Minor Non-alignment status Check combiner RF

of Alignment detected between input cable or check
main and diversity antenna alignment
flows in
configurations with
combiner
Download in Minor Minor Minor Download status Wait for downloading to

Progress complete


Description
1+0 1+1 HS 1+1 FD
Equipment Major Minor Minor MPT-HLS does not Replace connected MPT
Mismatch match MPT-HLS with MPT-HLS
memory
MPT-HLS Excessive Major Warn Warn Excessive Check correct FAN

(continued) Environmental temperature on provisioning and FAN
Temperature module alarm free condition:
see FAN alarm actions
Fan Minor None None A problem Check the fan cable

communication communicating with
problem the fan has been
detected
Forced Adaptive None ABN ABN Manual Forced Wait for the request to
Modulation Adaptive Modulation be released
command is executed
protection group
Loss of Radio Major Minor Minor Far end problems, RF 1. Switch far end
Frame path problems, or equipment (in a
local circuit failures protected system). If
have caused BER to alarm clears, replace
increase to the point far end off-line
that frames are being MPT-HLS.
lost 2. Check/troubleshoot
far end alarms
3. Replace alarmed
MPT-HLS
ATPC Loop Major None None ATPC High Power Wait until the active
Problem timeout receiver is no longer
receiving additional
transmitter power
Loopback None ABN ABN A loopback has been Wait for the loopback
activated at the near timeout to expire
end


Description
1+0 1+1 HS 1+1 FD
MPT-HLS Loss of N/A Minor Minor Delay between main 1. Replace main MPT-
(continued) Alignment and protect RF paths HLS
detected. Not 2. Replace protect
applicable for MPT MPT-HLS
connected to Core-E.
Loss of ESMC Minor None None Reported if there is a Check SSM settings
loss of the Ethernet
Synchronization
Message Channel.
The alarm is
applicable to User
Ethernet interfaces
configured with SSM
support enabled and
is assigned as a
synchronous clock
source input.
Demod Function Major Minor Minor Internal receive 1. Check Frequency

Fail circuit failure provisioning
matches with
subrack channel
frequency
2. Check that modem
profile provisioning
matches at the far
and near ends
3. Check that radio
environmental
conditions and RSL
receiving level is
above RCV
threshold
Dialog Failure None Warn Warn Temporary loss of Check MPT-MSS

communication with communication
MPT or radio interface or complete
parameters not yet radio provisioning or
provisioned wait for
communications restore


Description
1+0 1+1 HS 1+1 FD
High BER Major Minor Minor Bit Error Rate 1. Verify RF path
threshold (10E-4) is clear, antenna is
exceeded aligned, and no existing
weather-related
problems
RCV threshold. If not –
check upstream
transmitter output/
troubleshoot
transmitter
MPT-HLS Early Warning N/A Minor Minor 10E-9 BER detected No action is required at
(continued) this time. Monitor
receive signal for
increased degrading
Incompatible Major Minor Minor Frequency out of Modify the frequency

Frequency range of configured
frequency
Incompatible Major Minor Minor Configured shifter Modify the shifter value
Shifter value not supported
Link Identifier Major Major Major Link identifier Set numbers at both
Mismatch number provisioned ends of hop to match
is different from link
identifier number
end of hop


Description
1+0 1+1 HS 1+1 FD
MPT Loop Minor Minor Minor Communication Check the radio hop
Communication problem between the
alarm local MPT and the
remote MPT for all
the functionalities
requiring a
communication loop
(ATPC, ACM, Pre-
distorsion)
LOS on LAG Major Minor Minor Loss of Ethernet is Check link partner and
Interface detected on LAG cable between link
interface partner and MPT
connector
Overflow Major None None The level of demand Update the configured
Bandwidth is higher than the cross-connections
MPT net capacity
Radio Major None None Radio encryption Check encryption

Encryption enabled on only one settings on both sides of
Mismatch side of radio link the link
link. Valid for LAG
and ERPS


Description
1+0 1+1 HS 1+1 FD
MPT-HLS RF Switch fail Major Minor Minor RF Switch failure Check the cable or
(continued) detected replace RF switch unit
Rx Diversity None Minor Minor Rx diversity is Update the

missing enabled but configuration or replace
combiner unit is not the MPT-HLS with a unit
found with a combiner
Software Warn None None Software version on Wait for SWP update or
version MPT does not match check software version
mismatch software version on
Core
Standby None Warn Warn Standby Software Check software version

Software version on MPT does
version not match software
mismatch version on Core
Tx Clock Failure Minor Minor Minor The MPT is not able to Replace MPT-HLS
lock the air Tx symbol
rate to the NE Clock
Tx Mute ABN None None A manual or Wait for the mute

automatic mute timeout to complete
command has been
executed
UAT on Radio N/A N/A Major 10 consecutive SES Switch far end
Link (unavailable time equipment (in a
period) detected on protected system). If
main MPT-HLS alarm clears, replace
far end off-line
MPT-HLS
Degraded Signal Minor None None Sync clk errors Check LAG ports for
on LAG detected at LAG errors
Interface interface
PPP IP Fail Minor Minor Minor Point to point IP Check the settings
failure


Description
1+0 1+1 HS 1+1 FD
MPT-HLS Sync Degraded Minor Minor Minor This alarm can raise if Check the radio hop
(continued) signal the addressed Radio
interface has been
configured as
primary/secondary
synchronization
source. It is active if
the frequency of the
source signal is
degraded
Sync Fail Minor None None Received source Configure a different

signal is not suitable sync source.
as a sync source.
TCA Major Minor Minor TCA alarm is emitted

on a counter basis.
Applies to
performance
parameters with an
accumulation period
of 24 hours and 15
minutes
Incompatible Major Minor Minor Configured Update the modulation

Modulation modulation not
supported by MPT
Incompatible Major Minor Minor Configured RTPC/ Modify the power

Power ATPC Tx power value configuration
or ATPC Rx power
threshold value not
supported by MPT


Description
1+0 1+1 HS 1+1 FD
MPT-HLS Internal Major Minor Minor Loss of 1. Check MPT-MSS

(continued) Communication communication with communication
Problem MPT interface integrity
2. Replace MPT-HLS


Service
XPIC Cable Loss Minor None None XPIC Cable Check the XPIC cable
Connection defect
detected
Table 7.4 — MPT-MC Alarm Matrix
Equipment Alarm Description Configuration/ Most Probable Action

Alarm Cause
1+0 1+1 HS
MPT-MC Card Fail Major Minor MPT-MC failed Replace MPT-MC
Loop Problem None Minor Loss of Check the radio hop

communication
(e.g. ATPC)
command path
between far end
transmitter and
local receiver
Loopback None ABN A loopback has Wait for the loopback timeout to
been activated at expire
the near end

Table 7.4 — MPT-MC Alarm Matrix (Continued)

Alarm Cause
1+0 1+1 HS
Equipment Major Minor MPT-MC does not Replace MPT-MC

Mismatch match MPT-MC
configured in
Core-E memory
Forced Switch None ABN A forced switch Wait for the request to be
has been executed completed
on the protection
group
Incompatible Major Minor Frequency out of Modify the frequency

Frequency range of
configured
frequency


Alarm Cause
1+0 1+1 HS
MPT-MC Incompatible Major Minor Configured RTPC/ Modify the power configuration
(continued) Power ATPC Tx power
value or ATPC Rx
power threshold
value not
supported by MPT
Incompatible Major Minor Configured shifter Modify the shifter value

Shifter value not
supported
Internal Major Minor Loss of Replace MPT-MC

Communication communication
Problem with MPT
LOS on LAG Major Minor Loss of Ethernet is Check link partner and cable
interface detected on LAG between link partner and MPT
interface connector
Overflow Major None The level of Update the configured cross-

Bandwidth demand is higher connections
than the MPT net
capacity
RCV Function Fail Major Minor MPT-MC receiver Replace MPT-MC

circuit failed
Remote Defect Minor None An RDI is received Check the remote radio
Indication on a radio
direction from the
remote end of the
link. Valid for LAG
and ERPS
RF Frequency Major Minor Frequency out-of- Re-configure frequency

Mismatch range of
configured Tx
frequency


Alarm Cause
1+0 1+1 HS
MPT-MC Shifter Frequency Major Minor Configured shifter Re-configure shifter value
(continued) Mismatch value not
supported by MPT-
MC
TX Power Minor Minor Configured TX Re-configure TX power value

Mismatch power value not
supported by MPT-
MC
Modulation Major Minor The modulation Change the modulation

parameters parameters parameters
Mismatch already configured
and stored in the
MPR DB are not
actually supported
by MPT
Software Minor Minor Software version Download correct software

Mismatch on MPT-MC does version
not match
software version
on Core
MPT-MC Not Minor Minor Loss of 1. 1. Replace MPT-MC

Responding communication 2. 2. Replace alarmed MPT
with MPT-MC Access Card
Firmware Minor Minor Download status Wait for downloading to

Progress
Loss of Radio Major Minor Far end problems, 1. Switch far end equipment
Frame RF path problems, (in a protected system). If
or local circuit alarm clears, replace far end
failures have off-line MPT-MC.
caused BER to 2. Check/troubleshoot far end
increase to the alarms
point that frames
are being lost 3. 3. Replace alarmed MPT-MC


Alarm Cause
1+0 1+1 HS
MPT-MC Loss of Alignment Minor Minor Delay between 1. Replace main MPT-MC
(continued) main and protect 2. Replace protect MPT-MC
RF paths detected
Demod Function Major Minor Internal receive Replace MPT-MC

High BER Major Minor Bit Error Rate 1. Verify RF path is clear,
threshold (10E-4) antenna is aligned, and no
exceeded existing weather-related
problems
2. Verify RSL is above RCV
threshold. If not – check
upstream transmitter output/
troubleshoot transmitter
Early Warning N/A Minor 10E-9 BER No action is required at this

detected time. Monitor receive signal for
increased degrading
Link Identifier Major Major Link identifier Set numbers at both ends of hop
Mismatch number to match
provisioned is
different from link
identifier number
provisioned at
other end of hop
Lockout Switch None ABN A Lockout Switch Wait for the request to be
has been executed released
for the protection
group
Loss of Radio None Major The radio direction Check the RPS cable
Protection is affected by a
failure that RPS
cannot recover


Alarm Cause
1+0 1+1 HS
MPT-MC MPT Loop Minor Minor Communication Check the radio hop
(continued) Communication problem between
alarm the local MPT and
the remote MPT
for all the
functionalities
requiring a
communication
loop (ATPC, ACM,
Pre-distorsion)
Sync Degraded Minor Minor This alarm can Check the radio hop
signal raise if the
addressed Radio
interface has been
configured as
primary/
secondary
synchronization
source. It is active
if the frequency of
the clock
recovered from
radio Rx signal is
mistuned
MPT Tx Clock Minor Minor The MPT is not Check the radio hop
Failure able to lock the air
Tx symbol rate to
the NE Clock
TCA on Radio Link N/A N/A Alarm threshold Switch far end equipment (in a
exceeded on protected system). If alarm
standby MPT-MC clears, replace far end off-line
MPT-MC
TCA on Radio Hop Major N/A Alarm threshold -

exceeded on
standby MPT-MC
after switching
from main to
standby


Alarm Cause
1+0 1+1 HS
MPT-MC UAT on Radio Link N/A N/A 10 consecutive SES Switch far end equipment (in a
(continued) (unavailable time protected system). If alarm
period) detected clears, replace far end off-line
on main MPT-MC MPT-MC
UAT on Radio Hop Major N/A 10 consecutive SES

(unavailable time
period) detected
on standby MPT-
MC after switching
from admin to
standby
Degraded Signal Minor Minor Low quality sync Replace MPT-MC

signal from MPT-
MC
PPP IP Fail Minor Minor Point to point IP Check the settings

failure
Legend:
• EPS –Equipment Protection Switching

• LOS –Loss of Signal
• RPS –Radio Protection Switching
• RCV –Receiver
• TCA –Threshold Crossing Alarm
• UAT –Un-Available Time
• Check the basics first.
• For example, if multiple alarms are present, and these include power supply
voltage or hardware alarms, always check their cause before looking at resultant
down-stream path failure or path warning (signal) alarms.
• Similarly, if a path-related failure is indicated (no hardware or software alarms),
investigate the path. Go to the WebEML History screen (15 minute view) to check
supporting data, such as low RSL and incidence of intermittent pre-failure BER
alarms, which if present are evidence of a path-related failure.
• Check if symptoms match the alarm. Alarms reflect the alarm state, but in
exceptional circumstances an alarm may be raised because of a failure to communicate
correctly with the alarm source, or a failure in alarm management processing. Always
check to see if symptoms match the alarm, using LED indications and the WebEML.

• Check if recent work may be a cause. Recent work at the site may be a cause or
contributing factor. Check for a configuration change, software upgrade, power
recycling (reboot), or other site work:
• Many hardware alarms are only initiated as a loss-of-communications alarm during
a reboot, software upgrade, or reconfiguration. By not being able to communicate
with the Core-E, their settings cannot be loaded. The fault may be at the hardware
device (most likely), communications to it, or the Core-E.
• Hardware/software compatibility alarms will be raised when a new plug-in is
installed that needs a later version of 9500 MPR-E software.
• Hardware incompatible alarms will be raised when a plug-in is installed in a slot
that has been configured for a different plug-in.
• MSS before an ODU. If there is doubt about whether a fault is in the MSS or ODU,
always replace the MSS first; it is quicker and easier.
• Hot-pluggable. MSS cards are hot-pluggable. There is no need to power-down before
replacing, but traffic will be lost unless the plug-in is protected.
• Plug-in restoration time. Ensure adequate time is allowed for services to resume when
a plug-in is replaced.
7.4.3 — Troubleshooting Path Problems

A path-related problem, with the exception of interference, is characterized by traffic being
similarly affected in both directions. Generally, if you are experiencing only a one-way
problem, it is not a path problem.
Note: A path extends from ODU antenna port to ODU antenna port.
• Normally a path problem is signaled by a reduced RSL, and depending on its severity,
a high BER.
• Only in worst case situations, such as an antenna knocked out of alignment, will a path
fail completely, and stay that way.
• For weather-related problems, such as rain or ducting, the path problem will disappear
as the weather returns to normal.
7.4.3.1 — Path Problems on a Commissioned Link
A path problem on an existing link, one that has been operating satisfactorily may be caused
by:

• Weather-related path degradation

If BER alarms are fleeting/not permanent and RSL returns to its normal, commissioned
level after the alarm is cleared, rain, diffraction, or multipath fading is indicated. Rain
fade is the likely cause of fade for links 13 GHz and higher. Diffraction and multipath/
ducting for links 11 GHz and lower. If these alarms are persistent, there could be a
problem with the link design or original installation.
• Changed antenna alignment or antenna feed problem
If RSLs do not return to commissioned levels after a period of exceptionally strong
winds, suspect antenna alignment. Also, check the antenna for physical damage, such
as may occur with ice-fall. For a remote-mounted ODU, check its antenna feeder.
• New path obstruction
Where all other parameters check as normal, and the path has potential for it to be
obstructed by construction works, view/survey the path for possible new obstructions.
• Interference from other signal sources
Interference usually affects traffic in just one direction. Unlike other path problems,
RSL is not affected. If suspected, check for new link installations at, or in the same
geographical area, as the affected site. Ultimately, a spectrum analyzer may have to be
used to confirm interference, which is not an easy task given the need to connect
directly to the antenna port, after removing the ODU.
7.4.3.2 — Path Problems on a New Link
For a new link, potential problems can extend to also include:
• Incorrect antenna alignment

One or both antennas incorrectly aligned. Refer to Installation alignment procedure on
CD.
• Mismatching antenna polarizations
Given a typical polarization discrimination of 30 dB, for most links it is not possible to
capture a signal to begin the antenna alignment process.
• Incorrect path calculations
If the RSLs are too low or too high, antenna alignment is correct, and Tx power settings
are correct, check the path calculations used to determine the link performance. A good
calculation match is +/- 2 dB. Disagreements in excess of 3 dB should be investigated.
• Reflections
Reflection (path cancellation) problems may not have been picked up at the path
planning stage, particularly if the survey was a simple line-of-sight. If suspected,
resurvey the path.

7.4.4 — Troubleshooting Configuration Problems

Configuration problems should only occur during the setup of a new link, or
reconfiguration of an existing link. The more common problems may be broadly
categorized as:
• Compatibility Problems
The two alarms that may activate are Configuration Not Supported and SW/HW
Incompatible:
• Configuration Not Supported: The plug-in installed is not enabled or is incorrect
for the configuration.
• SW/HW Incompatible: Typically raised when new hardware is plugged into an
existing MSS that has software from an earlier release. To remove the alarm,
compatible 9500 MPR-E software is required; install the latest software.
• Incorrect circuit connections
No alarms are activated for incorrect circuit connections. An incorrect assignment
means the expected end-to-end circuit connectivity will not happen. Re-check circuit
assignments for all nodes carrying the lost circuit(s).
Take extra care when configuring ring circuits.
• Incorrect ID naming and commissioning
All traffic-carrying circuits must have a unique flow ID for the cross-connect capability
to operate.
• Incorrect/incompatible trib settings
Trib line interface settings incorrect, or line levels incompatible. While no alarm
activates for an incorrect setting, its effect may result in line levels being too low (LOS
alarm), or too high, resulting in a high BER.
7.4.5 — Troubleshooting Ethernet Problems

This section gives general guidance on troubleshooting problems related to the four
Ethernet ports on the Core-E Card.
The most common Ethernet problems are network and connectivity related and therefore
always check the following first:
• for User and NMS ports, verify link partner capability, provisioning, and connection
• for Radio ports, verify the cabling between ODU and MSS.
In order for the green Link LED to light:
1. Cable must be connected to Ethernet port

2. Ethernet port must be enabled (provisioned Enabled). Applicable for User and NMS
ports
3. Speed and mode must be provisioned the same as the link partner.
The yellow LED opposite the green on the connector indicates activity only. The flashing
yellow LED is not an indicator of signal type or quality.
7.4.6 — Troubleshooting TMN Problems

This section gives general guidance on troubleshooting TMN problems related to Ethernet
port 4 on the Core-E Card. Ethernet port 4 on the Core-E Card can be used to transport
SNMP IP data. Troubleshoot port 4 connectivity alarms the same as Ethernet ports 1-3.
The most common TMN problems are network related and first alert is normally observed
by improper operation at the SNMP master. Always check the following first:
• Verify master is properly registered in NE to receive traps.

• Verify SNMP version matches system requirements
• Verify correct community string and privileges
• Verify proper network routing.
Refer to Table 7.5 for detail TMN network troubleshooting.
Table 7.5 — TMN Network Troubleshooting
Problem Possible Cause Possible Solution
Unusually slow 1. Normal network management 1. There may be too many radios being
communication in traffic is saturating the managed within a single region. Split the
radio network communications channel. radio network management into different
regions and backhaul the traffic for each
region through separate channels.
2. Polling radios for PM data or missed 2. Poll the radios more slowly.
alarms too rapidly
3. Multiple remote software 3. Download to fewer radios at a time.

downloads in process
4. IP traffic other than network 4. Configure external routers to allow only

management traffic being routed network management related traffic
through radio network through the Management network of the
radios. Dynamic route updates (OSPF, RIP)
may attempt to reroute high speed traffic
through the TMN network if a high speed ink
fails.

Table 7.5 — TMN Network Troubleshooting (Continued)
Problem Possible Cause Possible Solution
Unable to operate To perform control operations, the Register the Manager as a craft device.
controls using SNMP Manager must be registered as a craft Manager registration type can be changed as
device. needed to type ‘ct’ to allow control
operation and then be changed back to
‘nml’ for normal operation.
Can Read SNMP 1. Incorrect community string 1. Use the correct community string.
objects but cannot
Write to SNMP 2. If the TMN Interface is configured 2. Use the correct write community string.
objects for SNMPv2, the write community
string is probably wrong.
No traps being 1. Manager not registered in NE to 1. Register Manager with NE.

received from NE receive traps
2. Communication failure in network 2. Check network connectivity. Check

redundant network paths and routing.
Traceroute (tracert) is useful for locating
path or routing faults.
Unable to Possible communication path failure Use traceroute (tracert) to help locate for
communicate with or routing failure within the radio communication path or routing problems.
the NE through the network.
radio network
(unable to ‘ping’ the
NE).
Can ‘ping’ the TMN If using SNMPv2, using the wrong Verify community string or username/
Interface but cannot community string. passphrase.
communicate with
the NE using SNMP, or
can only see a few
SNMP objects in the
NE.
7.4.7 — Analyzing the Ethernet traffic with the

Troubleshooting Tool
The Troubleshooting Tool can be used to perform the analysis of the Ethernet traffic.
Perform the following:
1. Open a web browser and enter http://IP address of the NE.

2. The following screen opens.

Enter:
• User Name: initial;
• Password: adminadmin.
3. The WebInterface menu opens. Select menu Administration → Debug Info and select
a command from the pull down list.

4. Select either “Run command” or “Run command to File”. “Run command” provides
the output on the web page. “Run command to file” provides the output on the web
page and also saves the output on a file.
The following commands are available:
• l2 show: lists all the MAC addresses and associated VLANs learned by the NE (the list
includes static entries self-defined by NE).
• Vlan show: lists the configured VLANs inside the NE with the ports member of VLAN
(VLAN member set) and ports where VLAN Tag is removed in egress (VLAN
untagged set).

• arp-a: lists the Static and Dynamic entries in the Address Resolution Table. It shows
the details of Unicast and Multicast Static Routes present along with the Vlan ID and
the ports associated. QoS information is also shown.

The following table provides the association of the GExx in the command output and the
NE port.
Table 7.6 — Association of the GExx in the command output and the NE port
GE Port n° HW connection
GE05 06 SFP 2 (port #6 of the Core)
GE06 07 SFP 1 (port #5 of the Core)
GE07 08 Internal port
GE10 11 Slot 1
GE11 12 Slot 3

Table 7.6 — Association of the GExx in the command output and the NE port
GE Port n° HW connection
GE12 13 Slot 5
GE13 14 Slot 7
GE14 15 Slot 2
GE15 16 Slot 4
GE16 17 Slot 6
GE17 18 Eth. User #1
7.5 — Card Removal and Replacement

The basic rules for installing plug-in cards are as follows:
Warning: Never install, change or remove a card without first connecting to the shelf
with an ESD grounding cable. Failure to do so may cause ESD damage to the cards.
Warning: Plug-ins must be withdrawn and inserted using their finger-grip fastener/pulls.
Never withdraw or insert using attached cable(s). Pulling on the cables may damage the
cable, plug-in connector, and/or plug-in card connector attachment.
Warning: When installing a plug-in, ensure its backplane connector is correctly engaged
before applying sufficient pressure to bring the plug-in panel flush with the front panel.
Improper alignment can result in damaged pins on the backplane connector and/or
damage to the plug-in connector.
Caution: All slots must be filled with either a peripheral plug-in card or a blank panel.
Failure to do so will compromise EMC integrity and cooling air from the fan.

Caution: Use extreme caution when connecting or disconnecting the ODU cable on the
Modem Card. The shelf battery voltage is present on the center conductor of the
connector. When removing or replacing a Modem Card, withdraw the card from the shelf
before disconnecting the cable to the ODU. Failure to follow these cautions may cause
arcing and/or possible power spikes that could affect traffic on other links installed at
the node.
Caution: Removing an in-service card in an unprotected link will cause loss of traffic.
Removing an in-service card in a protected link requires switching the traffic onto the
standby (protection) channel.
All plug-ins can be removed and installed with power applied. The following procedure
applies to a plug-in card or a Core-E card without core protection. To replace a protected
Core-E card, see the next section.
Caution: When replacing the Core-E card on an NE in the unprotected core configuration,
it is mandatory to transfer the flash card from the replaced Core-E card to the
replacement Core-E card. Failure to transfer the flash card will result in a loss of the NE
database and a system that may not boot up properly. At a minimum ALL NE
configuration will be lost and the NE configuration previously stored on the flash card
will be applied to the NE.
Perform the following:
Caution: If the main Core-E Card fails, traffic and platform data will switch to the spare
Core-E Card automatically. Do not remove power from the NE during the removal and
replacement of the failed main Core-E Card without first reviewing/performing the
following procedure:
1. Turn off NE power.

2. Remove the failed Core-E card.
Caution: Do not swap the active Core-E flash card, the one not being replaced, with a
flash card from another Core-E card.
3. Remove the flash card from the failed main Core-E card and install it in the
replacement Core-E card.
4. Turn on NE power.
5. Wait two (2) minutes.

6. Install replacement Core-E Card.

7. Wait for the replacement Core-E card status LED to stop flashing.
8. Verify the communication with the replacement Core-E using the Craft Terminal. If the
replacement Core-E does not communicate properly or the status is not normal, contact
technical support.
7.5.1 — Core-E Card Removal and Replacement with Core

Protection
On the Core-E flash card(s) the NE configuration and license key data is stored.
When replacing the Core-E card on an NE in the protected core configuration, if the active
Core-E card is operating properly, the flash card on the replacement Core-E card will
synchronize to the NE database stored on the active Core-E card. In this configuration a
flash card from another shelf type or Core position could be used on the replacement Core-
E card if necessary.
Caution: If the Main Core-E Card in slot 1 fails, traffic/services protection and control
platform protection switches to the spare Core-E Card in slot 2. Loopbacks and all other
manual operations, such as manual switch, tx mute, will be lost (deactivated). Alarms
previously active will be newly detected and reported via notification, with a new time
stamp.
Warning: After the removal of a faulty card, when you re-insert the new card, before re-
connecting the Ethernet cables between the Core-E card and other systems, wait for the
Core-E card STATUS LED (S) to end its flashing activity.
Verify the replacement Core-E Card meets the following compatibility rules:
• Main Core-E Card (in slot 1) and Spare Core-E Card (in slot 2) must be the same type.
• Local and far end Core-E Cards must use the same software version, but do not have to
be the same type.
7.5.2 — Flash card replacement procedure

This section provides information on changing the flash card. When the Main Flash card is
replaced, the NE MAC address changes. This will affect cross-connections whose
destination is the NE where the flash card was replaced.

• First case: Core-E Protected

1. Get a spare FLASH CARD with the same sw-package release and license of the
Main flash. If a card with the same release is not available standard migration paths
apply; see the Release Notice
2. Remove the faulty FLASH CARD from the main Core-E and insert the spare one.
3. Insert the Core-E with the new FLASH CARD
4. The MIB (MAIN FLASH) will be automatically aligned with the MIB (SPARE
FLASH).
5. Re-provision ALL TDM2ETH cross-connections on ALL affected NEs in the
network with the new MAC address of the replacement flash card.
• Second case: Core-E Not Protected (NB)
1. Get a spare FLASH CARD with the same sw-package release and license. If a card
with the same release is not available standard migration paths apply; see the
Release Notice.
2. Remove the faulty FLASH CARD from the main Core-E and insert the spare one.
3. Insert the Core-E with the new FLASH CARD
4. Carry-out the RESTORE procedure.
5. Re-provision ALL TDM2ETH cross-connections on ALL affected NEs in the
network with the new MAC address of the replacement flash card.
Caution: Do not insert in the system a Flash Card the content of which is unknown.You
must be aware that, if a Flash Card with SW information different from that running in
the system is inserted “as it is”, the software download will be automatically carried out
from the Flash Card toward the System, thus causing a complete system crash.
The new Flash Card includes a new NE MAC address. If you have L1 LAG or Ring
cross-connections, after you complete this procedure, contact Alcatel-Lucent
support for information as changing the NE MAC address impacts these cross-
connections.
Note: The license of the Spare Flash card can be different from the license of the Main
Flash card. Only the license of the Main Flash card manages the NE.
7.5.3 — ODU300 or MPT-HC V2 or MPT-XP or MPT-MC removal

and replacement
Disconnect the cables from the Outdoor Unit to be replaced and connect them to the spare
ODU.

7.6 — Upgrade from Not Protected to a Protected Radio

(with ODU300)
7.6.1 — 1+0 Adaptive Modulation to 1+1 HSB Adaptive

Modulation and 1+1 EPS
Starting from a 1+0 configuration (see an example in the graphics below) perform the
following procedure to upgrade to a 1+1 HSB radio with Adaptive Modulation and 1+1
EPS.
Caution: This is an in-service but not a hitless procedure.
1. Plug-in the Access card (E1 or STM-1) in slot 4 (spare). An Unconfigured Equipment
alarm displays.
Note: In the figure is shown the 32E1 Access card.

2. Plug-in Modem card in slot 8 (spare). An Unconfigured Equipment alarm displays.

3. On WebEML Settings screen enable the Access card (E1 or STM-1) in slot 4.
4. On WebEML Settings screen enable the Modem card in slot 8.
5. On WebEML Settings screen provision the Access card (E1 or STM-1) (slots 3 and 4)
for 1+1 EPS Protection Type.
6. On WebEML Settings screen provision the Modem cards (slots 7 and 8) for HSB
Protection Type. Local station and remote station will observe 2 seconds sync loss.
7. Connect the signal cables to the spare the Access card (E1 or STM-1) in slot 4.
8. Connect the new IDU/ODU cable to the spare Modem card in slot 8.
Note: After the changes a modification must be done in the TDM2Eth cross-connections
of the remote NE: the MAC address must be changed from “Unicast” to “Multicast” as
explained in Figure 4.75, Figure 4.76 and Figure 4.77.
7.6.1.1 — 1+0 Static Modulation to 1+1 HSB Static Modulation and 1+1
EPS
Refer to the 1+0 Adaptive Modulation to 1+1 HSB Adaptive Modulation procedure above.
7.6.2 — 1+0 to 1+1 Frequency Diversity and 1+1 EPS
following procedure to upgrade to a 1+1 Frequency Diversity and 1+1 EPS.

alarm displays.
2. Plug-in Modem card in slot 8 (spare). An Unconfigured Equipment alarm displays.

4. On WebEML Settings screen enable the Modem card in slot 8.
6. On WebEML Settings screen provision the Modem cards (slots 7 and 8) for 1+1 FD
Protection Type. Local station and remote station will observe 2 seconds sync loss.
8. Connect the new IDU/ODU cable to the spare Modem card in slot 8.
9. Properly configure the protection ODU.
of the remote NE: the MAC address must be changed from “Unicast” to “Multicast” as

7.7 — Upgrade from Not Protected to a Protected Radio

(with MPT-HC V2/MPT-XP or MPT-MC)
Note: With MPT-MC only the 1+1 HSB configuration is available.
7.7.1 — 1+0 Adaptive Modulation to 1+1 HSB/FD Adaptive

Modulation and 1+1 EPS
following procedure to upgrade to a 1+1 HSB radio with Adaptive Modulation and 1+1
EPS.
alarm displays.

2. Plug-in MPT Access card in slot 8 (spare). An Unconfigured Equipment alarm

displays.
4. On WebEML Settings screen enable the MPT Access card in slot 8.
6. On WebEML Settings screen provision the MPT Access cards (slots 7 and 8) for HSB
or FD Protection Type. The Local station and the Remote station will observe a short
traffic impact.
8. Connect the new Power Supply cable and new Ethernet cable to the spare MPT Access
card in slot 8.
9. In case of 1+1 FD properly configure the protection MPT-HC.
of the remote NE: the MAC address must be changed from “Multicast” to “Unicast” as
7.7.2 — 1+0 Static Modulation to 1+1 HSB/FD Static Modulation

and 1+1 EPS
Refer to the 1+0 Adaptive Modulation to 1+1 HSB/FD Adaptive Modulation procedure
above.
7.8 — Downgrade from Protected to a Not Protected

Radio (with ODU300)
7.8.1 — 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0

Adaptive Modulation

Caution: Downgrading from 1+1 HSB and 1+1 EPS to 1+0 configuration is an out-of-service
procedure. The main channel must be in service including sync source before starting
procedure.
1. Disconnect signal cables from the spare the Access card (E1 or STM-1) in slot 4.
2. Disconnect IDU/ODU cable on the spare Modem card in slot 8.

3. On WebEML Settings screen for Modem cards (slots 7 and 8) enable Local Tx Mute
for Channel #1 and Channel #0.
4. On WebEML Settings screen for Modem cards (slots 7 and 8) set Protection Type to
no Protection.
or FD Protection Type. The Local station will observe a short traffic impact.
6. On WebEML Settings screen for Modem cards (slots 7 and 8) disable Local Tx Mute
for Channel #1 and Channel #0.
7. On WebEML Settings screen for the Access card (E1 or STM-1) (slots 3 and 4) set
Protection Type to no Protection.
8. On WebEML Settings screen for spare the Access card (E1 or STM-1) (slot 4) set
Equipment Type to EMPTY.

9. On WebEML Settings screen for spare Modem card (slot 8) set Equipment Type to
EMPTY.
10. Remove spare Modem card (slot 8).
11. Remove spare the Access card (E1 or STM-1) (slot 4).
12. Power off and power on the NE.
7.8.2 — 1+1 HSB Static Modulation and 1+1 EPS to 1+0 Static
Modulation
Refer to the 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation
procedure above.
7.8.3 — 1+1 FD to 1+0
Caution: Downgrading from 1+1 FD to 1+0 configuration is an out-of-service procedure.

The main channel must be in service including sync source before starting procedure.

1. Disconnect E1 signal cables from the spare the Access card (E1 or STM-1) in slot 4.
2. Disconnect IDU/ODU cable on the spare Modem card in slot 8.
Note: Local AIS will remain active throughout remainder of procedure.
no Protection.
no Protection.
8. On WebEML Settings screen for spare Modem card (slot 8) set Equipment Type to
EMPTY.

9. Remove spare Modem card (slot 8).

7.9 — Downgrade from Protected to a Not Protected

Radio (with MPT-HC V2/MPT-XP or MPT-MC)
Note: With MPT-MC only the 1+1 HSB configuration is available.
7.9.1 — 1+1 HSB/FD Adaptive Modulation and 1+1 EPS to 1+0

Adaptive Modulation
Caution: Downgrading from 1+1 HSB/FD and 1+1 EPS to 1+0 configuration is an out-of-
service procedure. The main channel must be in service including sync source before
starting procedure.

1. Disconnect the signal cables from the spare the Access card (E1 or STM-1) in slot 4.
2. Disconnect IDU/ODU cables on the spare MPT Access card in slot 8.
Note: In case of 1+1 FD local AIS will remain active throughout remainder of procedure.
3. On WebEML Settings screen for MPT Access cards (slots 7 and 8) enable Local Tx
Mute for Channel #1 and Channel #0.
4. On WebEML Settings screen for MPT Access cards (slots 7 and 8) set Protection Type
to no Protection.
6. On WebEML Settings screen for MPT Access cards (slots 7 and 8) disable Local Tx
Mute for Channel #1 and Channel #0.

9. On WebEML Settings screen for spare MPT Access card (slot 8) set Equipment Type
to EMPTY.
10. Remove spare MPT Access card (slot 8).
7.9.2 — 1+1 HSB/FD Static Modulation and 1+1 EPS to 1+0

Static Modulation
Refer to the 1+1 HSB/FD Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation
procedure above.
7.10 — Software package rollback
Note: The software package rollback operation WILL impact traffic including a possible
long out-of-service period. For this reason software package rollback should be
considered as a critical operation to be performed as a last resort only after all other
alternatives have been explored.
1. Have all alternative been explored to resolve the system problem?

a. If yes, go to step 2.
b. If no, go to step 19.
2. Have all appropriate levels of support been notified and are all in agreement that a
software package rollback is the appropriate next step?
3. Contact ALL appropriate levels of support and obtain all appropriate approvals as
required per local practices and procedures.
4. Have all appropriate levels of support been notified and are in agreement that a
software package rollback is the appropriate next step?

5. Software package rollback procedure

Caution: possibility of service interruption. The software package rollback operation
WILL impact traffic including a possible long out-of service period. For this reason
software package rollback should be considered as a critical operation to be
performed as a last resort only after all other alternatives have been explored.
6. Open the NE Software Status Detail window.
From the Main Menu Bar select, SW Download → SW Status.
7. On the software bank with the Current Status Committed, verify the software version
matches that of the upgraded software package. See Figure 7.1
Figure 7.1 — Software bank with upgrade software version Committed status
8. On the software bank with the Current Status Standby, verify the software version
matches that of the initial software package. See Figure 7.2

Figure 7.2 — Software bank with Initial software version Standby status
9. Are the committed (upgrade) and standby (initial) software version verified and correct
as expected?
10. On the software bank for the standby software version, select from the Software
Management Action drop-down menu Forced Activation. See Figure 7.3
Figure 7.3 — Software Management Action - Forced Activation

11. Select the Apply Action button. See Figure 7.3

12. Communication with the NE will be lost. Wait until the Core-E card status LED is solid
green before proceeding to step Log in to the NE..
13. Log in to the NE.
14. Open the NE Software Status Detail window.
15. From the Main Menu Bar select, SW Download → SW Status.
16. On the software bank with the Current Status Committed, verify the software version
matches that of the initial software package. See Figure 7.4.
Figure 7.4 — Software bank with initial software version Committed status
17. On the software bank with the Current Status Standby, verify the software version
matches that of the upgrade software package. See Figure 7.5

Figure 7.5 — Software bank with upgrade software version Standby status
18. Are the committed (initial) and standby (upgrade) software version verified and correct
as expected?
19. Contact the next level of support for assistance.
20. Stop. This procedure is complete.
7.11 — WebEML/TCO Suite/NEtO startup issues
7.11.1 — Resolve WebEML/TCO Suite/NEtO startup issues
Note: A potential conflict may occur when running previous versions of the WebEML/TCO
Suite applications..
If startup issues are encountered including “Fatal Error: RMI resources not available” or
“NEtO RMI Registry Error”, perform the following procedure to resolve startup issues.
1. Turn “OFF” the FTP and/or the SFTP Servers if provisioned “ON”.
2. Close ALL open WebEML/TCO Suite applications, which include the following:

• NEtO
• JUSM
• Alarm Monitor
• Performance Monitoring Tool
• Event Log Browser
• Ethernet Feature Shell
• MCT
• NEtO Server Manager (NEtO Server Manager should close automatically. If it
does not automatically close, the user MUST manually close the NEtO Server
Manager.)
3. Using the Windows Task Manager, verify that none of the following processes are
running:
• NEtO.exe
• JAVA.exe
• RMIRegistry.exe
4. If any of the listed processes are running, select the listed process, then select End
Process.
5. Repeat step 4 until NO listed processes are running.
6. Restart the MPR TCO suite.
7.11.2 — Remove ALL previous versions of WebEML/TCO Suite
Note: It is recommended to remove ALL previous versions of WebEML/TCO Suite

applications after the R5.0 version has been installed to prevent potential startup issues.
If previous versions of the WebEML/TCO suite are loaded on the user’s PC in addition to
R5.0 version, it is recommended to remove all previous versions (R4.10 and Prior) to
prevent potential startup issues. Perform the following procedure to remove previous
versions to the WebEML/TCO suite.
1. Verify that ALL required software release versions are loaded on the user’s PC in the
WebEML MPR TCO R5.0 directory. If required software versions are not present, Load
all required versions prior to proceeding with this procedure. To load specific release
versions, refer to Local copy of the WebEML and TCO Suite Software to PC.
The default location for the WebEML/TCO suite is:
C:\Alcatel-Lucent\

2. Select ALL previous versions of WebEML MPR TCO Rx.y directories (R4.10 and
prior) and delete the folder(s).
7.12 — Cleaning
Warning: Do not use acid, alcohol, or brushes to clean cards because damage to the silk-
screen labeling and antistatic coating can result. Cleaning should be confined to the
removal of dust and dirt using a damp cloth.
Cleaning should normally be confined to the removal of dust and dirt using a soft bristled
(natural fiber) brush and a low velocity blower (such as a vacuum cleaner with a plastic
blower nozzle). Do not use acid or synthetic bristled brushes to clean cards that contain
electrostatic-sensitive components.

8 — Line–up and Commissioning
This chapter details all phases necessary for the equipment line–up and commissioning.
• Introduction
• General
• Safety–EMC–EMF–ESD norms and cautions to avoid equipment damage
• Conventions
• Summary of the line–up, commissioning, and acceptance phases
• General information about test bench drawings
• Commissioning of STATION A – phase 1 (Turn up)
• Commissioning of STATION B – phase 1 (Turn up)
• Fine antenna alignment and preliminary checks – Stations A & B
• End of commissioning phase 1 (Turn up) in STATION A
• Commissioning station A – phase 2 (acceptance test)
• Commissioning station B – Phase 2 (acceptance Test)
• Final operations
• Annex A: fine antenna alignment
8.1 — Introduction
8.1.1 — General
This chapter details all phases necessary for the equipment line–up, commissioning, and
acceptance, providing the user with the information needed to connect, power on, and
perform a minimum turn–up of a radio link comprising two 9500 MPR-E RELEASE 5.1.0
Network Elements.
It is assumed that, at both premises (Station A and Station B), the mechanical installation
and cabling of the INDOOR and OUTDOOR units is completed, the antennas are installed
and pre–positioned, and the MSS–ODU cable(s) has/have been connected to the MSS.

Any information needed to complete the above mentioned operations are out of the scope
of this chapter.
For this purpose refer to the Installation section.
All the cables and measurement kits as described in Table 8.1 are supposed to be available.
Table 8.1 — Test and commissioning instruments
INSTRUMENT QTY CHARACTERISTICS
Laptop computer running the 1 SWP 9500 MPR-E R5.1.0

supervisory software
PDH Analyzer – Pattern Generator 1 E1 traffic
SDH Analyzer – Pattern Generator 1 STM-1 traffic
ATM Analyzer 1
V.11 Analyzer 1
Link Service kit cable (for MPT 1

antenna alignment)
In alternative, for Ethernet Data Optional

channel functionality tests:
1 PC + 1 Ethernet cable (for ping
function)
or
2 PCs (for ping function)
or
2 Ethernet Data Analyzers
Multi–meter 1 Voltmeter AC and DC – Loop tester
Cable Tester 1 For RJ45, Ethernet, Optical fiber etc.
TRDS 1 Test Result Data Sheet, available as separate

document
The Alcatel–Lucent Software package SWP 9500 MPR-E R5.1.0 must have already been
installed in the PC used as the WebEML (WebEML) and the same software R5.1.0 must be
already present as commit version in the Flash Card of both two Network Elements.
Before proceeding with line–up and commissioning, ensure that you have the equipment
and accessories required for that purpose.

8.1.2 — Safety–EMC–EMF–ESD norms and cautions to avoid

equipment damage
Warning: To make sure of the continuity and avoid short circuit, all cables / connectors
connections (such as RJ45, Coaxial, Ethernet, or Optical Fiber) made on the field have to
be verified and checked with Cable tester. The waterproofness must be also checked.
If not yet done, read all of Chapter 2: it describes the operations and/or precautions to be
observed to safeguard operating personnel during the working phases, and to guarantee
equipment safety. Read them with accuracy before to start every action on the equipment.
8.1.3 — Conventions
To simplify the description of actions, the following symbols are in use:
Table 8.2 — Symbols
Symbol used Meaning
☞ Manual action
P Check/Verify
WebEML⇒ On WebEML Select
fi Select a Menu item
→ Sub Menu item
The commissioning operations described in this document are for a radio link between a
Station A and a Station B.
If the network includes supervision, station A is the one located between the supervisory
station and station B (see figure below). Installation and commissioning begin at station A.

Figure 8.1 — Relative positions of stations A and B
Warning: At the beginning of this procedure, the “local IP address” and “Ethernet IP
address” of both the NE 9500 MPR-E stations, are still set to default value “10.0.1.2” (as
delivered from Alcatel–Lucent factory). For this reason, their physical connection to the
TMN network must be done after having changed such addresses to correct values.
8.1.4 — Summary of the line–up, commissioning, and

acceptance phases
Note: The following procedure must be used for every Modem unit installed in the MSS.
The commissioning procedure is summarized as follows:
1. Turn up (phase 1)
1. Visual inspection and NE configuration.
a. Station A, roughly point the antenna towards station B (if not done in the
Hardware Installation procedure)
b. Commission station A (phase 1)
c. Commission station B (phase 1)

2. Fine antenna alignment and preliminary checks – Stations A & B

a. Station B, fine align the antenna towards station A, and preliminary checks
b. Station A, fine align the antenna towards station B, and preliminary checks
2. Site acceptance tests (phase 2)

1. Station A, perform all the commissioning checks and tests – Report the results in
the TRDS.
2. Station B, perform all the commissioning checks and tests – Report the results in
the TRDS.

8.1.5 — General information about test bench drawings

In the test bench drawings depicted in the following sections of this chapter, take always
into account the following considerations:
1. Actual station configuration

For detailed information on the layout and equipment interconnections refer to the
Plant documentation.
2. “1+0” and “1+1” configurations
Test bench drawings refer usually to the “1+0” configuration. When necessary, the
additional material for “1+1” configurations is drawn in dotted line.
3. Equipment interfaces for test access points, signal meaning and use
The standard equipment interfaces for access points are always considered at Station
DDF. Station DDF is not detailed in the drawings: refer to your own plant
documentation for details.
4. Craft terminal need
The WebEML (WebEML) is always required.
8.2 — Commissioning of STATION A – phase 1 (Turn up)

Warning: Where necessary, switch OFF the power supply before disconnecting the
earth connection.
Do not connect instruments directly to the MSS/ODU cable connector since the
connector carries DC voltage used to supply the ODU.
Do not connect the IDU-ODU cable between MSS and ODU, while the MSS is powered
up.
8.2.1 — Turn–on preliminary operations
Warning: ALL THESE OPERATIONS ARE PERFORMED WITH THE POWER OFF
✓ The antenna of station A (or B) is pointed towards station B (or A) the best as possible
(use compass if necessary).
✓ The hardware configuration of the equipment corresponds to the expected one.
✓ Make visual inspection for units’ installation and cabling:
• The MSS subrack allocation according to the station lay–out

• The MSS subrack and units ground connections
• The power supply voltage is present with the correct polarity at the MSS power supply
input
• Tributaries are cabled on the station DDF
• The MSS–ODU cables ground kit connections
• The ODU(s) ground connections (In the case of a non–integrated antenna, the antenna
and the ODU(s) must be ground connected)
• The MSS(s) / ODU(s) cables are connected to MSS(s) and ODU(s)
• The ODU(s) cables connectors waterproofing.
8.2.2 — Powering up the MSS(s) with ODU(s) connected

This operation has the following scopes:
• verify the SWP present both in WebEML and NE

• make the Central Frequency and Shifter values of ODUs be acquired by MSS (so that
they are retained in the NE’s data base).

Proceed as follows:
a. Switch on the MSS by using the circuit breakers

b. Connect locally the WebEML to the MSS of the local station and perform the NE login
with NEtO.
1. Make a local connection through the Ethernet cable, between the Ethernet port of
the PC and the NMS interface on the MSS
2. Power on the PC and wait for its start–up
3. Start–up the WebEML and wait for the NEtO screen
4. Insert the “local IP address” of the NE 9500 MPR-E station
5. Start supervision on the local Network Element
c. Configure the NE as explained in the Provisioning chapter.
8.3 — Commissioning of STATION B – phase 1 (Turn up)

• To commission Station B, perform (at Station B premises) the same operations carried
on at Station A–Phase 1.
☞ ☞For near future tests, establish, on the DDF of Station B, hardware loops on every
tributary.
8.4 — Fine antenna alignment and preliminary checks –

Stations A & B
8.4.1 — Fine antenna alignment

When Station A and Station B are fully configured and operational, and assuming that the
antenna in station A (or B) has been previously correctly pointed toward the antenna in
station B (or A), you should receive some field from station B (or A).
Note: Verify that the ATPC is disabled.

Note: In case of 1+1 (with asymmetric coupler) to facilitate the alignment make sure that
Channel #1 is active.
Now, proceed to a fine tuning of the antenna to improve as much as possible the received
level, in both Station A (at Station A premises) and Station B (at Station B premises). To
perform the fine antenna alignment refer to Annex A: fine antenna alignment.
8.4.2 — Preliminary checks

At first on Station A (at Station A premises), then on Station B (at Station B premises), log
in the NE and perform following checks by WebEML:
• Verify ODU300/MPT-HC V2/MPT-XP/MPT-MC alarm status

• Transmitter power output check
• Received power measurement
8.4.2.1 — Verify ODU300/MPT-HC V2/MPT-XP/MPT-MC alarm status
Purpose:Verify no abnormal communication alarm between MSS(s) and ODU(s)
Required Instruments:PC with WebEML software
Procedure: Connect WebEML to MSS.
☞ WebEML ⇒ Views ⇒ Equipment
→In the left window, select ODU ch#1n
✓ In the lower right window, verify in the alarms list for that there is no internal
communication failure
✓ In the lower right window, verify in the alarms list that there is no TX failure
♦ Repeat for Ch#0 if any (1+1)
8.4.2.2 — Transmitter power output check
Purpose:Verify via WebEML the ODU(s) transmitted power output.

☞ WebEML ⇒ Double click on the front panel of the Modem unit (Channel #1) (for
ODU300) or on the front panel of the MPT Access peripheral unit or MPT-HC V2/MPT-
XP/MPT-MC.
✓ Verify that ATPC is “Disabled” (If required, change the ATPC status to disable in the
ATPC field then → Apply)
✓ Verify that Tx Power value complies with the suitable value already set (If required,
change the Tx Power in the RTPC field then → Apply)
♦ Repeat for Ch#0 if any (1+1).
8.4.2.3 — Received power measurement
Purpose:Verify via WebEML the received power to detect any interference
☞ WebEML ⇒ Double click on the front panel of the Modem unit (Channel #1) (for
ODU300) or on the front panel of the MPT Access peripheral unit or MPT-HC V2/MPT-
XP/MPT-MC.
→Select “Measurements” tab panel
→In the Sample time (sec), write the suitable measurement poling time then press → Start

Figure 8.2 — Received power check
Pressing “Start” will prompt a graphic monitoring view of the transmitted and received
levels:

Figure 8.3 — Power measurements
Ticking the box “Show Details” in the lower left corner will call a summary view of the
TX and Rx levels:

Figure 8.4 — Received power details
✓ Verify in the hop calculation (plant documentation) that the calculated received level has
been reached.
✓ Verify that there are no interferences.
♦ Repeat for Ch#0 if any (1+1)
Warning: If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in
HSB Configuration the transmitter is in standby).
If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant
Rx end field the information in dBm is –99, probably the supervision has been lost.
8.5 — End of commissioning phase 1 (Turn up) in

STATION A
• In Station A, proceed to a final fine alignment of the antenna toward the antenna of
Station B. To perform the fine antenna alignment, refer to Annex A: fine antenna
alignment.

• In Station A, proceed to the remote NE (station B) acquisition (by opening a second

NEtO session) in order to verify in both the stations:
✓ Received level complies with hop calculation
✓ No alarm showing (except unloaded tributaries)
8.6 — Commissioning station A – phase 2 (acceptance

test)
Commissioning phase 2 is a site acceptance test procedure made up of the required tests to
ensure that the equipment is fully operational.
This phase describes first of all the way to check and to change (if necessary) via the
WebEML menu the different configuration parameters already set, for most of them, during
the Provisioning followed by various tests.
Most of the tests and checks results have to be recorded in the TRDS (Test Results Data
Sheet). Operator will be invited to do so each time it is required by the following sentence:
“Report… in the TRDS.”
Table 8.3 — Test
Test Report
in TRDS
a) Installation and cabling visual inspection
Indoor System installation and cabling visual inspection ✓
Outdoor System installation and cabling visual inspection ✓
b) System configuration
Check Software Release ✓
Check/set Mode (Presettings or Adaptive modulation), Channel spacing, ✓

Modulation
Check/set Link Identifier configuration (optional) ✓
Check/set the QoS configuration ✓
Check/set the LAG configuration ✓
Check/set the Automatic Restoration Criteria (only 1+1) ✓

Table 8.3 — Test (Continued)
Test Report
in TRDS
HSB Transmission Protection (1+1 HSB configurations only) ✓
Radio Protection (RPS) ✓
EPS Protection ✓
Check/set Tx/Rx Spacing, Transmission and Reception frequencies ✓
Check/set Tx power (ATPC Off) or Tx range and Rx threshold (ATPC On) ✓
Check/set the XPIC configuration (if required) ✓
Check/set the synchronization ✓
Check/set the encryption, if required ✓
Tx and Rx power measurement (with WebEML) ✓
IF Loopback functionality (ODU300) ✓
Core-facing loopback functionality (MPT-HC V2/MPT-XP/MPT-MC/MPT- ✓

HLS)
Table 8.4 — Test
Test Report
in TRDS
c) P32E1 unit
Balanced or Unbalanced impedance ✓
Check/set E1 tributaries configuration ✓
Protection functionality (1+1 only) ✓
E1 point to point loop test ✓
d) STM-1 unit
Check/set STM-1 configuration ✓
Protection functionality (1+1 only) ✓
STM-1 point to point loop test ✓
e) 16E1/DS1 ASAP unit

Table 8.4 — Test (Continued)
Test Report
in TRDS
Check/set E1 layer configuration ✓
Check/set IMA layer configuration ✓
Check/set ATM layer configuration ✓
Check/set ATM PW layer configuration ✓
f) EAS unit
Check/set EAS unit configuration ✓
g) A-FANS unit
Check/set the Housekeeping configuration ✓
h) MSS-1 unit
i) AUX unit
Check/set AUX unit configuration ✓
j) Core-E unit
Check the Software license Code ✓
Check/set Traffic Ethernet port parameters ✓
k) NE configuration
Check/set the local NE IP address ✓
Check/set OSPF Area Configuration ✓
Check/set the Ethernet access (OS) configuration ✓
Check/set IP static routing configuration ✓
l) Data/Time settings ✓
m) E1 Hop stability test ✓
n) STM-1 Hop stability test ✓
o) Ethernet Traffic stability test ✓
p) ATM Traffic stability test ✓
q) 64 kbit/s Service Channel functionality test (optional) ✓

8.6.1 — Installation and cabling visual inspection
8.6.1.1 — Indoor System installation and cabling visual inspection
See and fill the indoor inspection check list in the TRDS.
8.6.1.2 — Outdoor System installation and cabling visual inspection
See and fill the indoor inspection check list in the TRDS.
8.6.2 — System configuration

Purpose:Verify via WebEML the configuration of the Local Station.
Procedure: Connect WebEML to MSS
8.6.2.1 — Check Software Release
☞ WebEML ⇒ Menu bar ⇒ Menu SW Download → SW Status
Check the Software release.
Report in the TRDS.
8.6.2.2 — Check/set Mode (Presettings or Adaptive modulation),

Channel spacing, Modulation
☞ WebEML • Double click on the front panel of the Modem unit for ODU300 or on the
card or on the MPT-HC V2/MPT-XP/MPT-MC/MPT-HLS → Settings tab panel
In the left window → Mode (Preset or Adaptive modulation), Channel spacing, Modulation
(Supported Modulation Schemes and Switching Threshold, if the Adaptive Modulation has
been enabled)
If required, change any parameter.

Report the parameters in the TRDS.
8.6.2.3 — Check/set Link Identifier configuration (optional)
Double click on the front panel of the Modem unit for ODU300 or of the MPT Access unit
or on the /MPT-HC V2/MPT-XP/MPT-MC for MPT-HC V2/MPT-XP/MPT-MC →
Additional Settings tab panel
If it is necessary, change any parameter.
Report the Link Identifier status (Enabled or Disabled), and, if Enabled, the “Expected”
and “Sent” values.
8.6.2.4 — Check/set the QoS configuration
☞ WebEML ⇒ Menu bar ⇒ Configuration ⇒ QoS configuration
Select the suitable QoS configuration.
Report in the TRDS.
8.6.2.5 — Check/set the LAG configuration
☞ WebEML ⇒ Menu bar ⇒ Configuration ⇒ LAG configuration
Configure the required LAG.
Report in the TRDS.
8.6.2.6 — Check/set the Automatic Restoration Criteria (only 1+1)
HSB Transmission Protection (1+1 HSB configurations only)
☞ WebEML ⇒ Views ⇒ Protection Schemes
In the left window → HSB Protection
In the lower right window → Protection Scheme Parameters Tab panel → Protection Type
1+1

If required, change Operation type (Revertive or Not Revertive) then → Apply
Report the Operation Type in the TRDS.
Radio Protection (RPS)
In the left window → Rx Radio Protection (RPS)
1+1
EPS Protection
In the left window → Equipment Protection
1+1
8.6.2.7 — Check/set Tx/Rx Spacing, Transmission and Reception

frequencies
☞ WebEML ⇒ Double click on the front panel of the Modem unit for ODU300 or of the
MPT Access unit or on the MPT-HC V2/MPT-XP/MPT-MC for MPT-HC V2/MPT-XP/
MPT-MC
In the central window → Channel #1 → Shifter, Tx frequency
Repeat for Channel 0 (only in 1+1)

Report the Shifter, Tx and the Rx frequencies in the TRDS.
If required, change the Tx frequency then → Apply. Rx Freq. will be automatically

adjusted.
8.6.2.8 — Check/set Tx power (ATPC Off) or Tx range and Rx threshold

(ATPC On)
ATPC Disabled:
☞ WebEML ⇒ Double click on the front panel of the Modem unit for ODU300 or on the
ATPC Enabled field
✓ ATPC “Disabled”
Report the ATPC “Disabled” status, Tx nominal Power and Tx Power setting into the
TRDS.
ATPC Enabled:
☞ WebEML ⇒ Double click on the front panel of the Modem unit for ODU300 or on the
ATPC Enabled field
✓ ATPC “Enabled”
Report the ATPC “Enabled” status, ATPC Range and ATPC RX Threshold setting in the
TRDS.
If required, change ATPC Mode or ATPC Range or ATPC Rx Threshold then → Apply
8.6.2.9 — Check/set the XPIC configuration (if required)
☞ WebEML ⇒ Menu Configuration ⇒ XPIC Configuration
Check/set all the parameters regarding the XPIC (refer to XPIC configuration).
Report in the TRDS.

8.6.2.10 — Check/set the synchronization
☞ WebEML ⇒ Tab panel Synchronization
Check/set all the parameters regarding the synchronization.
Report in the TRDS.
8.6.2.11 — Check/set the encryption (if required)
☞ WebEML ⇒ Double click on the MPT-HC V2 or MPT-HLS → Additional Settings tab

panel
→Activate the radio encryption on the remote radio side. A radio encryption
mismatch alarm is raised on both sides of the radio to indicate that encryption is active
on one side of the link only. The Ethernet traffic passing through the radio link is
down, along with the TMN-RF.
→Activate the encryption on the local NE with a different passphrase value. The radio
encryption mismatch alarm is cleared as both sides of the radio are now encrypting the
traffic, but the link is still down.
→Set the same passphrase as on the remote side of the radio link. The Ethernet traffic
comes up.
Report in the TRDS.
8.6.2.12 — Tx and Rx power measurement (with WebEML)
Purpose:Verify via WebEML the Transmitted (PTx) and Received (PRx) power.
☞ WebEML ⇒ ouble click on the front panel of the Modem unit for ODU300 or on the
card or on the MPT-HC V2/MPT-XP/MPT-MC/MPT-HLS → select Measurements tab
panel
→From the left window → select Channel #1
→In the Sample time (sec), write the suitable measurement poling time then press → Start

Pressing “Start” will prompt a graphic monitoring view of the transmitted and received
levels.
Ticking the box “Show details” in the lower left corner will call a summary view of the TX
and Rx levels.
Report the Current Tx Local End (PTx) and the current Rx Local End (PRx) in the TRDS.
8.6.2.13 — Loopback functionality
IF Loopback functionality (ODU300)
Purpose:Verify via WebEML the IF cable loopback functionality (only in the local NE)
Required Instruments:PC with WebEML software and E1 Data Analyzer
Connect Pattern Generator/Error Detector analyzer on one Tributary Access (At the Station
DDF)
• A delay up to 10 seconds may be observed for each activation/deactivation.

• Ensure that the local tributary access is active (unframed and configured).
• Ensure that the local transmitter is muted (double click on the front panel of the Modem
unit → Settings tab panel).

Figure 8.5 — IF Cable loopback
☞ WebEML ⇒ Double click on the front panel of the Modem unit → “Loopback” tab
panel
In the left window → IF cable
In the lower right window → Active → Apply
PError Detector showing no errors.
PLoopback showing in the Summary Block Diagram view.
To remove the loopback: in the lower right window → Not Active → Apply
Report about the Loopback functionality in the TRDS.

Core-facing loopback functionality (MPT-HC V2/MPT-XP/MPT-MC/MPT-

HLS)
Purpose:Verify via WebEML the Core-facing loopback functionality (only in the local
NE)
Procedure: Connect WebEML to MSS Connect Pattern Generator/Error Detector analyzer

on one Tributary Access (At the Station DDF)
• A delay up to 10 seconds may be observed for each activation/deactivation.

• Ensure that the local tributary access is active (unframed and configured).
Figure 8.6 — Core-facing loopback
☞ WebEML ⇒ Double click on the front panel of the MPT-Access unit or on the MPT-HC
V2/MPT-XP/MPT-MC/MPT-HLS → Maintenance tab panel
At the top of the Loopback panel → Core-facing - Internal
Below the loopback type → Active → Configure Timeout → Apply

PError Detector showing no errors.
PLoopback showing in the Summary Block Diagram view.
To remove the loopback: in the lower right window → Not Active → Apply
Report about the Loopback functionality in the TRDS.
8.6.2.14 — Protection functionality (1+1 only)
Purpose:Force command (if the active channel is the Main) and Lockout command (if the
active channel is the Spare)
☞ WebEML ⇒ View ⇒ Protection Schemes
In the left window → Rx Radio Protection → Main #1 or Spare #0
In the Commands tab panel window Commands scroll list → Forced or Lockout →
Apply
Repeat for HSB Tx Protection (for “1+1 HSB” configurations only)
Repeat for Equipment Protection
✓ Check in the Summary block diagram that the full channel (Tx and Rx) path is in service.
Report about the Channel protection switching functionality in the TRDS.
8.6.3 — P32E1 unit
8.6.3.1 — Balanced or Unbalanced impedance
☞ WebEML ⇒ Menu bar → Configuration → System Settings
Set the impedance for the E1 streams.
Report the Impedance in the TRDS.

8.6.3.2 — Check/set E1 tributaries configuration
☞ WebEML ⇒ Double click on the front panel of the P32E1DS1 unit
In the left window → E1 port# 1
In the lower right window → “Settings” Tab panel
If it is necessary, change the E1 parameters.
Report in the TRDS.
Repeat for each E1 port#
In the left window → Equipment Protection → Main #1 or Spare #0
In the Commands tab panel → Forced or Lockout → Apply
✓ Check in the Summary block diagram that the full channel (TX and RX) path is in
service.
8.6.3.4 — E1 point to point loop test
Purpose:Verify the point to point Tributaries quality
Verify the tributaries alarm status monitoring functionality

Connect Pattern Generator/Error Detector on Tributary Access (At the StationDDF)
☞ WebEML ⇒ Diagnosis ⇒ Summary Block Diagram View
Report the result in the TRDS.
Figure 8.7 — Test bench for tributary functionality check with ODU300

Figure 8.8 — Test bench for tributary functionality check with MPT-HC V2/XP/MC
1. Point to point Tributaries quality test

Assuming that all the tributaries have been enabled and configured (Unframed status
and configuration) via WebEML in both stations and that every tributary is looped at
the DDF in the remote station:P
♦ Perform one minute of BER test on each E1 tributary
✓ Verify that the analyzer detects no error.
✓ Verify the tributary alarm status:
☞ WebEML ⇒ Double click on the front panel of the P32E1DS1 unit
In the lower right “Alarms” tab panel, verify that while the data analyzer is connected,
the “AlarmLossSignal” on the relevant tributary is off.
Leave the “Alarms” screen open, to perform following check
2. Check of the tributaries alarm status monitoring functionality
To create an alarmed condition, remove the “Tributary loopback” at the Remote
station.
In the lower right “Alarms”, verify that while the data analyzer is connected, the
“AlarmLossSignal” on the relevant tributary goes on.

Restore the “Tributary loopback” at the Remote station, and verify that the
“AlarmLossSignal” on the relevant tributary goes off.
Report about the Tributary BER test and alarm WebEML monitoring in the TRDS.
8.6.4 — STM-1 unit
8.6.4.1 — Check/set STM-1 configuration
☞ WebEML ⇒ Double click on the front panel of the SDHACC unit
In the left window → STM-1 port# 1
If it is necessary, change the STM-1 parameters.
Report in the TRDS.
Repeat for each STM-1 port#2 (if any)
In the left window → Equipment Protection → Main #1 or Spare #0
In the Commands tab panel → Forced or Lockout → Apply
✓ Check in the Summary block diagram that the full channel (TX and RX) path is in
service.

8.6.4.3 — STM-1 point to point loop test
Purpose:Verify the point to point STM-1 quality
Verify the tributaries alarm status monitoring functionality
Required Instruments:PC with WebEML software and SDH Data Analyzer
Connect Pattern Generator/Error Detector on STM-1 Access (At the Station DDF)
☞ WebEML ⇒ Diagnosis ⇒ Summary Block Diagram View
Report the result in the TRDS.
Figure 8.9 — Test bench for tributary functionality check with ODU300

1. Point to point quality test

Assuming that the STM-1 has been enabled and configured via WebEML in both
stations and that every STM-1 is looped at the DDF in the remote station:
♦ Perform one minute of BER test the STM-1
✓ Verify that the analyzer detects no error.
✓ Verify the STM-1 alarm status:
☞ WebEML ⇒ Double click on the front panel of the SDHACC unit
In the lower right “Alarms” tab panel, verify that while the data analyzer is connected,
the “AlarmLossSignal” on the relevant STM-1 is off.
Leave the “Alarms” screen open, to perform following check
2. Check of the alarm status monitoring functionality
To create an alarmed condition, remove the “Loopback” at the Remote station.
In the lower right “Alarms”, verify that while the data analyzer is connected, the
“AlarmLossSignal” on the relevant signal goes on.
Restore the “Loopback” at the Remote station, and verify that the “AlarmLossSignal”
on the relevant STM-1 goes off.
Report about the BER test and alarm WebEML monitoring in the TRDS.

8.6.5 — 16E1/DS1 ASAP unit
8.6.5.1 — Check/set E1 layer configuration
☞ WebEML ⇒ Double click on the front panel of the 16E1/DS1 ASAP unit
To configure refer to E1 Layer.
Report in the TRDS.
8.6.5.2 — Check/set IMA layer configuration
☞ WebEML⇒ Double click on the front panel of the 16E1/DS1 ASAP unit
To configure refer to IMA Layer.
Report in the TRDS.
8.6.5.3 — Check/set ATM layer configuration
To configure refer to ATM Layer.
Report in the TRDS.
8.6.5.4 — Check/set ATM PW layer configuration
To configure refer to ATM PW Layer.
Report in the TRDS.
8.6.6 — A-FANS unit

8.6.6.1 — Check/set the Housekeeping configuration
☞ WebEML ⇒ Double click on the front panel of the A-FANS unit
To configure refer to MSS A-FANS main view (to open this view double click on an A-
FANS card).
Report in the TRDS.
8.6.7 — MSS-1 unit
☞ WebEML ⇒ Double click on the front panel of the MSS-1 unit
To configure refer to MSS External Input Point view (to open this view double click on the
HK inputs on an MSS-1).
Report in the TRDS.
8.6.8 — AUX unit
8.6.8.1 — Check/set AUX unit configuration
☞ WebEML ⇒ Double click on the front panel of the AUX unit
To configure refer to Settings.
Report in the TRDS.
☞ WebEML ⇒ Double click on the front panel of the AUX unit
To configure refer to External Points.
Report in the TRDS.

8.6.9 — EAS unit
8.6.9.1 — Check/set EAS unit configuration
☞ WebEML ⇒ Double click on the front panel of the EAS unit
To configure refer to EAS VIEW for P8ETH and EASv2.
Report in the TRDS.
8.6.10 — EASv2 unit
8.6.10.1 — Check/set EASv2 unit configuration
☞ WebEML ⇒ Double click on the front panel of the EASv2 unit
To configure refer to EAS VIEW for P8ETH and EASv2.
Report in the TRDS.
8.6.11 — Core-E unit
8.6.11.1 — Check the Software license Code
☞ WebEML ⇒ Menu bar → Supervision → SW license
Report the license string and code in the TRDS.
8.6.11.2 — Check/set Traffic Ethernet port parameters
☞ WebEML ⇒ Double click on the front panel of the Core-E unit
In the left window → Ethernet Port#1 or Ethernet Port#2 or Ethernet Port#3 or Ethernet
Port#4 or Optical SFP Ethernet Port #5.

If it is necessary, change the parameters.
Report in the TRDS.
8.6.12 — NE configuration
8.6.12.1 — Check/set the local NE IP address
☞ WebEML ⇒ Configuration ⇒ Network Configuration ⇒ Local Configuration
Report the local IP Address in the TRDS.
8.6.12.2 — Check/set OSPF Area Configuration
☞ WebEML ⇒ Configuration ⇒ Network Configuration ⇒ IP Configuration ⇒ OSPF

Area Configuration
Report the Id, IP Address, IP Mask and Stub flag in the TRDS.
8.6.12.3 — Check/set the Ethernet access (OS) configuration
☞ WebEML ⇒ Double click on the front panel to the Core-E unit ⇒ TMN Interface tab
panel
Report the IP Address, IP Mask, IP Routing protocol and OSPF Area in the TRDS.
8.6.12.4 — Check/set IP static routing configuration
☞ WebEML ⇒ Configuration ⇒ Network Configuration ⇒ IP Configuration • IP Static

Routing Configuration
Report the IP Address, IP Mask and Default gateway IP Address or interface type into the
TRDS.

8.6.13 — Data/Time settings

☞ WebEML ⇒ Menu bar ⇒ Configuration ⇒ NE Time
Enter the time settings.
Report in the TRDS.
☞ WebEML ⇒ Menu bar ⇒ Configuration ⇒ Network Configuration • NTP Server

Configuration
Enter the IP address of the NTP Server, if any.
8.6.14 — E1 Hop stability test
Note: This test is in alternative to that described in point d) (performed on one Ethernet
port)
Purpose:Verify the Hop stability
Connect Data analyzer on one Tributary Access (At the Station DDF)
• The Hop stability test is performed during two consecutive hours, one time, on one
Tributary, in real working condition whatever the protection configuration (1+ 0 or
1+1).
• The two-hour stability test must be free of error in normal propagation conditions (out
of fading period)
♦ Via the WebEML, let only one active tributary in both station
♦ In the remote Station, place a hardware loop on the relevant tributary access (at the station
DDF).
♦ In the local station, connect the E1 Data Analyzer on the relevant tributary. Check that
the “Tributary Alarm Loss” disappears.
✓ Verify in both stations that there are no active software loopbacks or switching requests.
✓ Verify in both stations that none alarm is showing.

Report the two-hour error-free of error Hop Stability Test result in the TRDS.
Figure 8.11 — Test bench for hop stability test with ODU300

8.6.15 — STM-1 Hop stability test
Note: This test is in alternative to that described in point d) (performed on one Ethernet
port)
Purpose:Verify the Hop stability
Connect Data analyzer on one Tributary Access (At the Station DDF)
STM-1, in real working condition whatever the protection configuration (1+ 0 or 1+1).

• The two-hour stability test must be free of error in normal propagation conditions (out
of fading period)
♦ Via the WebEML, let only one active STM-1 in both station
♦ In the remote Station, place a hardware loop on the relevant STM-1 access (at the station
DDF).
♦ In the local station, connect the SDH Data Analyzer on the relevant tributary. Check that
the “STM-1 Alarm Loss” disappears.
✓ Verify in both stations that there are no active software loopbacks or switching requests.
✓ Verify in both stations that none alarm is showing.
Report the two-hour error-free of error Hop Stability Test result in the TRDS.
Figure 8.13 — Test bench for hop stability test with ODU300

8.6.16 — Ethernet Traffic stability test

Purpose:Verify the quality of point to point Ethernet Data Channels
Required Instruments:PC with WebEML software and, in alternative:
• 1 additional PC and 1 Ethernet cable

• 2 additional PCs
• 2 Ethernet Data Analyzers
Procedure:
a. Connect WebEML to MSS of local station

b. Perform the connectivity test on port #1, according to the chosen test bench:
Test bench with 1 additional PC and 1 Ethernet cable: see point [1]
Test bench with 2 additional PCs: see point [2]

Test bench with 2 Ethernet Data Analyzers: see point [3]

c. Perform the connectivity test on ports #2, #3, #4 and #5 (if enabled)
If required in plant documentation, repeat the connectivity test [step b) above] for the
other three ports, with obvious test bench changes on remote station.
Report about the connectivity test of Ethernet Data Channels in the TRDS.
d. Perform the hop stability test
1. Set up the test bench with 2 Ethernet Data Analyzers (point [3]). On both stations,
connect the Data analyzer on Ethernet port #1 on the Core-E unit.
2. Start this test after the “learning” of the MAC address.
3. Configure the pattern A generator, in order to generate continuous traffic, and set
the data rate half to the radio capacity and with packet size of 1518 bytes.
4. Perform the stability test for 2 hours.
5. Compare the number of TX and Rx Frames on the Pattern A: the number of frames
must be equal in normal propagation conditions (out of fading period).
Report the two-hour error-free Ethernet Stability Test result in the TRDS.
1. Test bench with 1 additional PC and 1 Ethernet cable

a. Connections
On local station, connect the additional PC on Ethernet port #1 (testing port).
On remote station, through the Ethernet cable, connect the NMS Ethernet port to
the Ethernet port #1 (port to be tested)
b. Set “Enable”, “Flow Control disable”, and “Capability Advertised” for ports
to test
☞ WebEML perform the following operations on each data port (Ethernet ports #1
to #4) of both stations:
• Enabled ⇒ Apply
• Auto Negotiation Status ⇒ Disabled ⇒ Apply
• Flow Control ⇒ Disabled ⇒ Apply
• Capability Advertised ⇒ “1000 Mb/s Full” ⇒ Apply
c. Perform the connectivity test on port #1
1. at local station, on PC connected to Ethernet port #1 (N.B.), ping the remote
station (using) the NE’s “Ethernet Configuration IP address”) with 50 packets
with 1000 byte length.
N.B.: the “PC’s IP address” and the NE’s “Ethernet Configuration IP address”
must belong to the same subnetwork.
Windows OS details, if necessary:
Start → Programs → Accessories → Command Prompt
ping <space> –l <space> 1000 <space> –n <space> 50 <space> IP Address
<enter>

2. the RIGHT LED on the corresponding front panel blinks with cable inserted
and traffic running
At least 45 packets must pass without any packet loss from the 5th packet
Figure 8.15 — Test bench for optional Ethernet Data Channel functionality with 1 additional PC and
1 Ethernet cable
2. Test bench with 2 additional PCs

a. Connections
On local station, connect the additional PC on Ethernet port #1 (testing port)
On remote station, connect the additional PC on Ethernet port #1 (port to be tested)
to test
☞ WebEML perform the following operations on each data port (Ethernet ports
#1 to #4) of both stations:


1. at local station, on PC connected to Ethernet port #1, ping the far–end PC with
50 packets with 1000 byte length.
Windows OS details, if necessary:
Start → Programs → Accessories → Command Prompt
ping <space> –l <space> 1000 <space> –n <space> 50 <space> IP Address
<enter>
and traffic running.
At least 45 packets must pass without any packet loss from the 5th packet.
Figure 8.16 — Test bench for optional Ethernet Data Channel functionality with 2 additional PCs

3. Test bench with 2 Ethernet Data Analyzers

a. Connections
On local station, connect the Data analyzer on Ethernet port #1 (testing port)
On remote station, connect the Data analyzer on Ethernet port #1 (port to be tested)
to test
☞ WebEML perform the following operations on each data port (Ethernet ports
#1 to #4) of both stations:
1. Start this test after the “learning” of the MAC address.
2. Configure Pattern Generator A in order to generate 50 packets with 1000 byte
length, and set the data rate half of the radio capacity.
and traffic running.
At least 45 packets must pass without any packet loss from the 5th packet.

Figure 8.17 — Test bench for optional Ethernet Data Channel functionality with 2 Ethernet Data
Analyzers
8.6.17 — ATM Traffic stability test

Purpose:Verify the quality of point to point ATM Data Channels (where 16E1/DS1 ASAP
unit has been installed)
Required Instruments:PC with WebEML software and 1 4xE1 ATM/IMA Generator/

Analyzer
Procedure:
IMA Group configured on 16E1DS ASAP peripheral, in real working condition
whatever the radio peripheral protection configuration (1+ 0 or 1+1).

• The two-hour stability test must be free of error (no ATM Cell Loss) in normal
propagation conditions (out of fading period)
a. Connect WebEML to MSS of local station
b. Check IMA connectivity in the local Station:
• "configure on ATM/IMA instrument a 4xE1 IMA Group with MPR default
configuration values
• "activate the IMA Group of ATM/IMA instrument: it will result in "Not
Operational" state since no connection to MSS and IMA configuration has been yet
performed
• "connect E1 ports of ATM/IMA instrument to DDF connection points
corresponding to E1 ports #1,#2,#3,#4 of relevant ASAP peripheral
• on MSS, enable E1 ports #1,#2,#3,#4 of relevant 16E1DS1 ASAP peripheral
by configuring as Framed their Signal Mode
• without change to default configuration values, activate ATM interface #1
associated to IMA Group #1 of relevant ASAP peripheral
• associate to IMA Group #1 of relevant ASAP peripheral and make active as
IMA Links the E1 ports #1,#2,#3,#4
• activate ATM interface #1,associated to IMA Group #1 of relevant ASAP
peripheral
• the IMA Group #1 of relevant ASAP peripheral and the one in the ATM/IMA
instrument shall become "Operational" ("TSF" alarm should be cleared, if
previously raised)
c. Perform the IMA connectivity test for all E1 ports of relevant ASAP peripheral(s)
Repeat the IMA connectivity test [step b) above] for the other E1 ports, with the below
association
• associate to IMA Group #2 of relevant ASAP peripheral the E1 ports #5,#6,#7,#8
• associate to IMA Group #3 of relevant ASAP peripheral the E1 ports
#9,#10,#11,#12
• associate to IMA Group #4 of relevant ASAP peripheral the E1 ports
#13,#14,#15,#16
Report about the IMA connectivity test of ATM Data Channels in the TRDS.
d. Configure ATM traffic in the local Station
• On ATM interface #1 (associated to IMA Group #1) of relevant ASAP peripheral
create and configure:
• "one ATM Traffic Descriptor for an ATM Circuit of type CBR, PCR=17960
cell/s, CDVT=1000 microsecond, ATM Policing Enabled
• "one VP of "Not Logical" type, with VPI=1 and associate the above ATM TD
(both for Ingress/Egress)

• On PW Layer of relevant ASAP peripheral create one ATM PW flow associated to

the above VP, with PW Label = 100, 1 cell max per frame and 1 millisecond
timeout (no VPI translation)
• On PW Layer of relevant ASAP peripheral create one ATM PW flow associated to
the above VP, with PW Label = 100, 1 cell max per frame and 1 millisecond
timeout (no VPI translation)
• Configure the cross-connection of the above ATM PW flow towards the relevant
radio peripheral, with associated VLAN ID = 4000
e. Configure in the remote Station a Loopback at DDF level, as shown in Test bench
for ATM traffic
f. Configure and start in the local Station the ATM Generator/Analyzer
• Configure, ATM Generator of ATM/IMA instrument for one ATM Cell stream,
with rate 17960 cell/s, VPI=1, VCI=1 (if the ATM Generator has this capability,
use test pattern inside ATM Cells to detect Cell Loss), without starting traffic
• Start ATM Analyzer
• Start ATM Generator
• Check the same rate of ATM Cell of configured ATM Circuit is transmitted by
ATM Generator is also received by the ATM Analyzer (since ATM Traffic is
looped-back by the remote Station); if random pattern is available on ATM/IMA
instrument, directly check on ATM Analyzer that no cell is actually lost
Report the two-hour error-free ATM Stability Test result in the TRDS.

Figure 8.18 — Test bench for ATM traffic
8.6.18 — 64 kbit/s Service Channel functionality test (optional)

Purpose:Verify the point to point Service Data Channel quality
Required Instruments:PC with WebEML software and RS422 / V11 64 Kbit/s Data
Analyzer
Procedure:Connect WebEML to MSS
Define the operational ESC ports (Enable/Disable) (local and remote NE).
Cross-connect the configured ports to the appropriate radio channel (local and remote).
Connect Data analyzer on the service channel Access

Figure 8.19 — Test bench for 64 kbit/s Service Channel functionality check
Assuming that the User service Channel is looped in the remote station:
♦ Perform 10 minutes of BER test.
✓ Verify that the Data analyzer detects no error.
Report about the 64 Kbit/s Data channel BER test into the TRDS.
8.7 — Commissioning station B – Phase 2 (acceptance

Test)
Repeat in Station B all the tests performed in Station A except the Hop Stability Test that
has to be run only one time for the full hop.
Fill a second Test Result Sheet for Station B
END OF COMMISSIONING ACCEPTANCE TEST

8.8 — Final operations

Complete the commissioning of each NE, creating the NE operator profiles and saving its
data.
8.9 — Annex A: fine antenna alignment

Safety requirements for workers on antenna pole, and microwave radiations (EMF
norms)
Warning: SAFETY RULES
When operating on the antenna pole, strictly follow cautions.
In particular, if ODU is powered on from MSS, do not stand on the antenna axis and be
aware of the compliance boundaries.
Antenna pre–pointing should have been done during equipment hardware installation.
This annex explains how to carry out the antenna fine alignment.
To monitor the received level during alignment in the local station:
• use the ODU Rx power monitoring in addition to a voltmeter,

• or, after having logged in the NE, use the WebEML received power measurement
facility
Alignment procedure using the ODU Rx power monitoring
a. the radio link must be up and the ATPC disabled

b. in general, fine alignment should be done only on one station of the radio link
c. connect a voltmeter to the ODU (by using the Light Service kit cable for the MPT)
d. proceed with Vertical alignment, then with Horizontal alignment
e. in configurations with two antennas, repeat the procedure for the second antenna.
Note: Procedures for Vertical and Horizontal alignment depend on the type of integrated
pole mounting employed.

9 — Appendix A - Fiber-Microwave
Protection
9.1 — Overview
The Fiber-Microwave Protection feature allows to protect an Optical Fiber link with a
Microwave link.
The Main protection resource is the Optical Fiber, while the Spare protection resource is
the Microwave link.
The Optical Fiber link can be either a physical connection between two MPR NEs or a
connection between two MPR NEs by a Wireline network, where the access to that
Wireline network by MPR NEs is made by Optical Fiber connections:

9 — Appendix A - Fiber-Microwave Protection
Figure 9.1 — Fiber-Microwave Protection
Normally the traffic (Ethernet and TDM) is transmitted on the Optical Fiber link.
In case of failure of the Optical Fiber link, the traffic is rerouted automatically to the
Microwave link. When the Optical Fiber connection is restored, the traffic is rerouted again
on the Optical Fiber link following a Revertive behavior.
The switching criteria for the Optical fiber link are:
• Ethernet LOS (Core unit)

• SFP Card Missing
• SFP Card Fail

Figure 9.2 — Fiber-Microwave Protection - operation
The Fiber-Microwave Protection feature is supported by MPR NE using ERPS performing

the following configuration:
• Create a Topology having a radio interface and an optical User Ethernet interface as
Ring Ports;
• Create a single Instance in the Topology created before. Since it is requested to manage
the overall traffic either over Fiber connection or over radio link, the usage of two
Instances to load balance traffic in the Ring is not requested;
• Define one of the two NEs as RPL Owner and configure the radio interface as RPL. In
no-fault condition, this will set the Ring Port related to the radio interface in blocking,
allowing the traffic to be forwarded over Ethernet optical connection.

In case of Core protection the following configuration has to performed by the operator in
order to guarantee a consistent behavior of the Fiber-Microwave Protection:
• Usage of optical splitter;

• Disable auto-negotiation on optical User Ethernet interface;
• Disable Ethernet LOS as switching criteria for Core protection;
• Disable Static-LAG.
The Fiber-Microwave Protection feature is applicable to Tail links at the leaf of the
backhauling tree.
The Fiber-Microwave Protection can be implemented also on Tail links having one MPR
NE working as Node, according to the following scenario:
Figure 9.3 — Fiber-Microwave Protection on Tail links
The scenario is supported by the MPR NE using ERPS performing the following
configuration:
• Create two Topologies in the NE acting as Node, each Topology having a radio
interface and an optical User Ethernet interface as Ring Ports;
• Create a single Instance in both the Topologies created before;
• For each Instance, define the NE acting as Node or the other NE at Tail end as RPL
Owner and configure the radio interface as RPL. In no-fault condition, this will set the
Ring Port related to radio interface in blocking, allowing the traffic to be forwarded
over Ethernet optical connection.
Note: The TDM traffic in the Node cannot transit between the two Topologies. The tagged
Ethernet traffic with same VLANs can transit between the two Topologies. This means that
the same VLAN ID can be associated to both the Instances belonging to the two Topologies
in the NE acting as Node.

Note: Table 9.1 shows the Suggested combinations of the SFP and the splitters to be used
in configuration.
Table 9.1 — SFP/Splitter suggested combinations
SFP Splitter
1000Base-Lx 1AB383760002/3CC50168AAAA LC/LC LC 0.4 m 3CC52018AAAA

LC/LC LC 2 m 3CC52040AAAA
LC/LC LC 1 m 1AB405480001
1000Base-Zx 1AB383760003 LC/LC LC 1 m 1AB405480001
1000Base-Sx 1AB383760001/3CC50167AAAA - -
not supported
9.2 — How to create the Fiber-Microwave Protection

Procedure:
1. Click on the Ethernet Ring icon in the Tool bar.

2. The Ethernet Protection Ring configuration opens.

Figure 9.4 — Ethernet Protection Ring configuration
9.2.1 — Step 1: Topology creation (Create new Ring Topology

field)
Two different Fiber-Microwave protections (called "topology") can be created.

Figure 9.5 — Topology creation
1. Write Label.
2. Select Port (East and West) from the list of available Radio Directions (according to
the NE Provisioning) and from the list of the Ethernet SFPs of the Core unit (port #5 or
port #6).
Note: The Port can be associated only to ODU300.
3. Press Create.
4. The just created topology will appear in the list as shown in the next figure.

Figure 9.6 — Just created topology
9.2.2 — Step 2: ERP Instance Creation

Only one instance per topology can be created.

Figure 9.7 — ERP Instance Creation
1. Press Create.
2. The following screen opens.
Figure 9.8 — New ERP Instance
3. Write the New ERP Label.

4. Write the R-APS VLAN ID. The WebEML does the following checks:
• admitted values are in [2-4080] range
• VLAN Id is not already used in 802.1Q or XConnection
• VLAN Id is not already used in other ERP instances
• If the VLAN Id is already used in TMN In-band, the TMN In-band working mode
should be disabled.
5. Write the R-APS MEG Level.

R-APS protocol runs, on each ERPS Instance, between Down MEPs configured on
Ring Ports. This value represents the level of the Maintenance Entity Group on which
MEPs are configured.
Since an instance of R-APS protocol runs independently on each ERPS Instance (using
the specific R-APS VLAN ID configured), MEG Level value can be configured
regardless of the MEG Level set on other ERPS Instances.
Default MEG Level value is 7. Admitted values: 0-7.
For the correct ERPS operation, same MEG Level shall be configured on all Ethernet
Ring Nodes belonging to the ERPS Topology on which ERPS Instance is created.
6. Write the R-APS MEG ID East and West.
MEG Identifier of the Down MEPs must be configured on Ring Ports to support R-APS
protocol.
This value, one for East Ring Port and one for West Ring Port, represents the Identifier
of the Maintenance Entity Group on which MEP is configured.
Since an instance of R-APS protocol runs independently on each ERPS Instance (using
the specific R-APS VLAN ID configured), MEG Identifiers can be configured
regardless of the MEG Identifiers set on other ERPS Instances.
MEG Identifier values are in the 1 to 16 range.
MEG Identifier of East Ring Port shall be different from the MEG Identifier of West
Ring Port.
For the correct ERPS operation, same MEG Identifier shall be configured on either end
of a ring link.
7. On the NE which is the RPL Owner, select the RPL Owner and choose the Port (East
or West), which corresponds with the radio port.
8. Press Create.

Figure 9.9 — New ERP Instance
9. The just created instance is shown on the ERP Instance List.

Figure 9.10 — Just created topology
10. Repeat steps 1 to 8 to create the instance relevant to the second topology, if any.
9.2.3 — Step 3: Add VLANs to the instance

Figure 9.11 — Add VLANs to created instances - 1
1. Select the Instance in the ERP Instances List.

2. Enter the VLANs in the Add VLANs field.
“Printing Format” is supported to manage in one shot multiple groups of VLAN IDs:
i.e. (5-10, 100-130, 150).
The WebEML checks the following:
• the admitted values are in [1-4080] range
• VLAN Id is not used yet as R-APS VLAN Id in any instance
• VLAN Id is already used in TMN In-band, but the TMN In-band working mode is
disabled.
Note: After the VLAN has been configured in the instance and the instance has been
activated, add the VLAN in the specific VLAN configuration menu.
Note: To protect the E1 streams insert in the Add VLANs field also the relevant Flow Ids.
3. Press the Arrows button.

4. The new added VLANs, not yet configured, are highlighted in Yellow, as shown in the
figure.
5. Press Apply. After applying the configuration the list will display all the configured
VLANs in white background.

Figure 9.12 — Add VLANs to the instance - 2
9.2.4 — Step 4: Cross-connection creation

1. Open the Cross-connections menu in the Configuration menu.

Figure 9.13 — Cross-connections 1
2. Create the Cross-connections (TDM2TDM and TDM2ETH only). The available

Cross-connections are:
• PDH-Ring
• Radio (MD300)-Ring
Note: No pass-through cross-connections can be created.
3. Create a PDH-Ring cross-connection by dragging from a PDH slot to the Ring icon.
The following screen opens.

4. Select the ERP Instance and Flow Id to be cross-connected and click on the Define
MAC Addresses button.
5. Enter the destination MAC address (Unicast or Multicast) and click OK.
Note: The MAC address must be the same for all the cross-connections, unless the
notation for unicast and multicast.
Colors: green = valid MAC address

red = not valid MAC address
The MAC address has to be inserted in "multicast" notation in case the boards on
remote NE are configured in 1+1.

6. The just created Cross-connections will appear. Click on Apply.

7. Create a Radio (MD300)-Ring cross-connection by dragging from a Radio slot to the

Ring icon. The following screen opens.

8. Select the VLAN in the Available VLans field (VLAN 8 in the next figure) and enter
all the relevant parameters.

9. Click on the Right arrows button to create the cross-connected VLAN.

Now the cross-connected VLAN appears in the Crossconnected VLans field on the
right side.

10. Click OK. The just created cross-connection will appear. Click on Apply.

9.2.5 — Step 5: ERP Instances enabling

After having configured the Cross-connections, select the Instance in the Instance List and:
1. Enable it by ticking the EPR Enabled check box.
Note: As LAST has to be enabled the instance in the NE, where it has RPL owner role.
2. Click on Apply.

Figure 9.21 — Add VLANs to the instance - 3
Note: After the operator clicks on Close button, the WebEML checks VLAN Id 1 association.
If VLAN Id 1 is not associated to any instances, a Warning will alert the operator in order
to avoid traffic (if untagged) loop.
9.3 — How to create the Fiber-Microwave Protection

without removing the existing cross-connections
9.3.1 — Requirements

Requirements needed to start the procedure:
• Specific license for topology creation

• No radio-radio topology already created
• Only one radio-fiber topology already created
• ODU300 1+0 with cross-connection TDM2TDM and TDM2ETH towards:
• Other ODU300 1+0 or 1+1
• PDH 1+0 or 1+1
Note: Operative notes: To reduce the traffic impact, connect the fiber only when the
procedure has been executed on both NEs.
The procedure has to be started on the NE which will NOT have RPL-owner role.
Note: For the correct functionality enable the Java script on the Web browser.
9.3.2 — Step 1: Radio slot "cleanup"

1. Close the JUSM.
2. Open a WEB_browser and enter http://IP address of the NE/MicrowaveFiberProt.
The WebInterface menu opens.

3. Press GET in order to retrieve from the NE the list of the radio interface, which can be
candidate for the radio-fiber topology creation (see requirements above).

4. Insert in ODU300 radio slot field the number of the slot and configure the MAC
address of remote NE: the MAC address will be used for the cross-connections.
The MAC address has to be inserted in "multicast" notation in case the boards on
remote NE are configured in 1+1.
5. Press Apply.
6. Close the WEB page.
Note: In case of errors in MAC address syntax, it is necessary close e and open again the
MicrowaveFiberPort page and press GET.

The NE will delete all the cross-connections belonging to the radio slot selected: the
cross-connections will be removed from the persistent database and from MIB; they are
maintained on the HW in order to reduce impact on traffic.
9.3.3 — Step 2: Radio-fiber creation

1. Open the JUSM. Now, it is possible to create the radio-fiber topology selecting the
ODU300 slot "cleaned" by cross-connections.
2. Create the topology radio-fiber; create the instance and configure specific parameters
(RAPS-vlan, RPL owner role, WTR, and so on).
Caution: No other operator commands (different from the ones needed for the fiber-radio
topology and instance configuration) can be provisioned/executed in this phase.
The JUSM and the NE will not deny other commands in this step 2 this in charge to the
operator.
The VLANs associated to existing cross-connections will be automatically added to the

instance by the procedure (the updated VLAN list of the instance will be shown only
after Step 3: HW apply and update.
Note: The VLAN 1 will be also added to the VLAN list linked to the instance; the operator
can change it after the completion of the procedure (after the startup sequence in Step
3: HW apply and update.
In case of Ethernet traffic which will be protected in the radio-fiber:

• add to the instance also the VLANs associated, without changing the membership
in the VLAN panel (the membership modification has to be deferred to Step 3: HW
apply and update.
3. Activate the instance.
Note: The instance activation will be stored in the persistent database; the JUSM will not
show any updated dynamic information on the instance (like protection and port status)
during this step 2.
Note: All the executed operations will be saved in the persistent database and in MIB, but
not applied in the HW.
4. Close the JUSM.

9.3.4 — Step 3: HW apply and update

1. Connect to the specific NE web page: MicrowaveFiberProt.
2. Press Start.
3. Close the WEB page.
The NE will restart automatically.
During the startup, the "new" configuration will be applied on the HW: this operation
will affect the traffic.
4. When the startup will be completed, from JUSM will be possible to view radio-fiber
topology with specific cross-connection.
5. In case of Ethernet traffic which will be protected in the radio-fiber:
• update the membership of optical ports in the specific VLAN panel.

6. When the procedure has been completed on both NEs, the fiber can be connected.
7. In case it is necessary to create the second topology, it is necessary to execute the
procedure in Step 2: Radio-fiber creation.


10 — Abbreviations
Table 10.1 — Abbreviations
ABBREVIATION MEANING
ACM Adaptive Coding Modulation
ACR Adaptive Clock Recovery
ADM Add Drop Multiplexer
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
ANSI American National Standards Institute
AP Access Point
APS Automatic Protection Switching
APT Active Problem Table
AS Alarm Surveillance
ASAP Alarm Severity Assignment Profile
ATM Asynchronous Transport Module
ATPC Automatic Transmit Power Control
AVC Attribute Value Change
BBE Background Block Error
BER Bit Error Rate
BR & SW Bridge & Switch
Browser Application which allows to browse all RM-MIB objects
CBS Committed Burst Size
CIR Committed Information Rate
CCLNP Connection-less Network Protocol
CD Current Data

Table 10.1 — Abbreviations (Continued)
CDCC Data Communication Channel
CD-ROM Compact Disc Read Only Memory
CES Circuit Emulation Service
CFI Canonical Format Indicator
CI Communication Infrastructure
CLA Common Loss Alarm
CRU Clock Reference Unit
CTP Connection Termination Point
DCI Drop & Continue Interconnection
DCN Data Communications Network
DCR Differential Clock Recovery
DS Degraded Signal
EAS Ethernet Access Service
EC Equipment Controller
ECC Embedded Communication Channels
EFC Ethernet Flow Control
EFD Event Forwarding Discriminator
EM-OS Element Manager-Operation System
EML Element Management Layer
EML domain A set of NEs that are maintained by the same EML-OS.
EMS Event Management Services
EoSDH Ethernet over SDH
EOW Engineering Order Wire
EPG Eps Protection Group
EPS Equipment Protection Switching
EPU Eps Protection Unit
ERPS Ethernet Ring Protection Switching
ES Errored Second

ET Elementary Topology. It is a grouping of some nodes connected

according to specific rules. A typical ET is a ring.
ETH ETHernet
ETSI European Telecommunications Standards Institute
EW Early Warning
FCM Fixed Coding Modulation
FCS Frame Check Sequence
FD Frequency Diversity
FE Fast Ethernet
FLS Frame Loss Second
FM FM Fault Management
Gbit/s Gigabits per second
GFP Generic Frame Protocol
GNE Gateway Network Element
HBER High Bit Error Ratio
HD History Data
HET Hetero frequency
HS Hitless Switch
HSB Hot Stand-By
HTML HyperText Markup Language
ICP Internal Communication Problem
IDU InDoor Unit
IM Information Model
IMA Inverse Multiplexing over ATM
IP Internet Protocol
IWF Inter-Working Function
IEEE Institute of Electrical and Electronics Engineers
IM Information Manager
JUSM Java User Service Manager

Kbit/s Kilobits per second
LAG Link Aggregation Group
LAN Local Area Network
LAPD Link Access Procedure on D-channel
LBER Low Bit Error Ratio
LDPC Low Density Parity Check
LOF Loss Of Frame
LOS Loss Of Signal
MAC Medium Access Control
Mbit/s Megabits per seconds
MEF Metro Ethernet Forum
MIB Management Information Base
MPR Microwave Packet Radio
MPT-HC V2 Microwave Packet Transport - High Capacity Version 2
MPT-HLS Microwave Packet Transport - Long Haul Slim
MSS Microwave Service Switch
NE Network Element
NEC Network Element Clock
NEtO Network Element Overview
NMS Network Management system
NSA Not Service Affecting
NTP NetworkTime Protocol
OC ODU Controller
OCN Object Creation Notification
ODN Object deletion Notification
ODU OutDoor Unit
OFS Out of Frame Seconds
OH OverHead

OMT Orthogonal Mode Transducer
OMT-C Orthogonal Mode Transducer - Coupler
OS Operation System
PAP Password Authentication Protocol
PCP Priority Code Point
PDH Plesiochronous Digital Hierarchy
PDU Power Distribution Unit
PFoE Power Feed over Ethernet
PM Performance Monitoring
PNU Packet Node Unit
Port Physical Interface of a Node. A port can be SDH or PDH.
PI Physical Interface
PPI PDH Physical Interface
PRBS Pseudo Random Bit Sequence
PSU Power Supply Unit
PTU Packet Transport Unit
QL Quality Level
QoS Quality of Service
RACS Received Automatic Control Status
RAI Remote Alarm Indication
RDI Remote Defect Indication
RI Remote Inventory
RPG Rps Protection Group
RPU Rps Protection Unit
RPS Radio Protection Switching
RPPI Radio Plesiochronous Physical Interface
SA Site Aggregator
SCG Service Channel Protection Group

SCN State Change Notification
SCU Service Channel Protection Unit
SD Signal Degrade
SDH Synchronous Digital Hierarchy
SES Severely Errored Second
SF Signal Failure
SFP Small Form-factor Pluggable
SONET Synchronous Optical Network
SPDH Super PDH
SSM Synchronization Status Message
STM Synchronous Transport Module
TACACS+ Terminal Access Controller Access Control System
TCA Threshold Crossing Alarm
TCO Total Cost of Ownership
TD Threshold Data
TDF Total Discarded Frames
TMN Telecommunications Management Network
TPS Tx Protection Switching
TPG Tps Protection Group
TPU Tps Protection Unit
TRCF Total Received Correct Frames
TRO Total Received Octets
TRSEF Total Received Service Errored Frames
TRsp Tx Rx spacing
TS Time Slot
TTF Total Transmitted Frames
TTO Total Transmitted Octets
TTP Trail Termination Point

UAS UnAvailable Second
UAT UnAvailable Time
USM User Service Manager
UPA Unavailable path alarm
URU Underlying Resource Unavailable
VC Virtual Channel
VCC Virtual Channel Circuit
VP Virtual Path
VPC Virtual Path Circuit
WEEE Waste from Electrical and Electronic Equipment
WTR Wait Time to Restore


Customer documentation and product
support
Customer documentation
http://www.alcatel-lucent.com/myaccess
Product manuals and documentation updates are available at alcatel-lucent.com. If you
are a new user and require access to this service, please contact your Alcatel-Lucent sales
representative.
Technical support
http://support.alcatel-lucent.com
Documentation feedback
documentation.feedback@alcatel-lucent.com
© 2014 Alcatel-Lucent. All rights reserved.
3DB 19901 AEAA Edition 01

23948552

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

23948552

Caricato da

Copyright:

Formati disponibili

5 — Installation

XPIC connector port

Figure 5.312 — XPIC connector port

Table 5.94 — XPIC cables

Cable code Cable length Used for

3CC52204AA 3m Intra-rack connections on the low subrack or

3CC52204BA 5m Intra-rack connections on the high subrack

3CC52204CA 10 m Inter-rack connections

1524 User Manual 3DB19901AEAA Edition 01

Supported XPIC connections

Figure 5.313 shows the supported XPIC configurations, which are:

Figure 5.313 — Supported XPIC configurations

User Manual 3DB19901AEAA Edition 01 1525

Low subrack intra-rack cabling considerations

High subrack cabling considerations

5.1.10 — MPT-HLS installation in an LSY rack

5.1.10.1 — LSY existing installations

1526 User Manual 3DB19901AEAA Edition 01

Figure 5.314 — LSY system without ADM

User Manual 3DB19901AEAA Edition 01 1527

Figure 5.315 — LSY system with ADM

5.1.10.2 — Upgrade use cases

Looking at the existing installations described, four cases are possible:

a. Addition of MPT-HLS transceivers or partial replacement of LSY transceivers in a

1528 User Manual 3DB19901AEAA Edition 01

Case a: Addition of MPT-HLS transceivers or partial replacement of LSY

In case of addition or partial substitution on MPT-HL transceivers in a LSY system without

The branching sections shall be expanded through additional circulators/filters in case of

1. Keep the Base band sub-shelf.

User Manual 3DB19901AEAA Edition 01 1529

Figure 5.316 — Case a

Case b: Addition of MPT-HLS transceivers or partial replacement of LSY

In case of addition or partial substitution of MPT-HLS transceivers in an LSY system with

The existing ADM fan unit shall be kept.

1. Keep the Base band and ADM sub-shelves.

1530 User Manual 3DB19901AEAA Edition 01

3. Keep the old fan unit for ADM.

Figure 5.317 — Case b

Case c: Full replacement of LSY transceivers with MPT-HLS in a system

User Manual 3DB19901AEAA Edition 01 1531

1. Remove the Base band sub-shelf.

Figure 5.318 — Case c

Case d: Full replacement of LSY transceivers with MPT-HLS in a system

The existing ADM sub-shelf shall be kept.

1532 User Manual 3DB19901AEAA Edition 01

1. Remove the Base band sub-shelf.

Figure 5.319 — Case d

5.1.10.3 — Common operation description

User Manual 3DB19901AEAA Edition 01 1533

Existing TRU upgrading or replacement

Table 5.95 describes breaker utilization in the LSY TRU.

Figure 5.320 — Front view of LSY TRU

Table 5.95 — TRU breaker utilization in 9600 LSY

Breaker number Usage Current limit

1A and 1B Transceiver slot 1 to 5 20 A

2A and 2B Transceiver slot 6 to 10 20 A

3A and 3B Base Band subrack 10 A

5A and 5B Fan unit for BB subrack 2A

6A and 6B Fan unit for ADM 2A

• 3DB05602AA – most recent version of TRU

1534 User Manual 3DB19901AEAA Edition 01

Table 5.96 — Breakers for TRU

Breaker value Part number