Professional Documents
Culture Documents
Manual Do Produto
Manual Do Produto
Alarm
Equipment Alarm Description Most Probable Cause Action
1+0 1+1
EPS
Tx Regeneration sec- Major Minor RS-TIM (regeneration sec- Check STM-1 source
tion trace identifier tion trace identifier mis-
mismatch (J0) match) detected on each
STM-1 channel from external
line which is known as J0
byte in regeneration section
overhead
Tx Multiplex section Major Minor Multiplex Section AIS (MS- Check STM-1 source
alarm indication sig- AIS) specified as all "1"s in
nal (MS-AIS) the entire STM-1 from exter-
nal line, excluding the STM-1
RSOH
Tx Multiplex section Major Minor From external line. The Mul- Check STM-1 source
remote defect indica- tiplex Section Remote Defect
tion (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 external Check STM-1 source
(HBER) 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/sec-
ondary synchronization
source
Sync Degraded sig- Major Minor Managed only if the Check STM-1 source
nal addressed STM-1 has been
configured as primary or sec-
ondary synchronization
source
High Order Path Major Minor The AU4-AIS is specified as Check STM-1 source
alarm indication sig- all "1"s in the entire high order
nal (AU4-AIS) path Administrative 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 emu-
lated according the provi-
sioned settings).
Loss of Administra- Major Minor This alarm is raised when 8 to Check STM-1 source
tive Unit Pointer 10 consecutive invalid point-
(AU4-LOP) ers is received or 8 to 10 con-
secutive NDF is received.
The alarm becomes signifi-
cant and must be reported if
STM-1 LOS, STM-1 LOF ,
STM-1 TIM, MS-AIS, or AU4-
AIS alarms are not present.
As consequent action, any
E1 extracted from STM-1 will
be replaced with AIS (and
then circuit emulated accord-
ing the provisioned settings).
High OrderSignal Major Minor This alarm is raised when the Check STM-1 source
Label Mismatch value of C2 byte in VC-4 POH
(VC4 -SLM) is different between 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 conse-
quent action, any E1
extracted from STM-1 will be
replaced with AIS (and then
circuit emulated according
the provisioned settings).
Loss of Multiframe of Major Minor The value of H4 byte in VC-4 Check STM-1 source
Tributary Unit POH is not in the range (01H-
(VC4-LOM) 04H) or H4 multiframe is not
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
becomes significant and
must be reported if STM-1
LOS, STM-1 LOF, 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 AIS (and then
circuit emulated according
the provisioned settings).
Low Order Path alarm Major Minor The TU12-AIS is specified as Check STM-1 source
indication signal all "1"s in the entire low order
(TU12-AIS) pathTributary Unit. The
alarm becomes significant
and must be reported if STM-
1 LOS, STM-1 LOF , STM-1
TIM, MS-AIS or AU4-AIS,
AU4-LOP, VC4-SLM or VC4-
LOM alarms are not present.
As consequent action, the
relevant E1 will be replaced
with AIS (and then circuit
emulated according the pro-
visioned settings).
Loss of Tributary Unit Major Minor This alarm is raised when 8 to Check STM-1 source
Pointer 10 consecutive invalid point-
(TU12-LOP) ers is received or 8 to 10 con-
secutive NDF is received.
The alarm becomes signifi-
cant and must be reported if
STM-1 LOS, STM-1 LOF ,
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 rele-
vant E1 will be replaced with
AIS (and then circuit emu-
lated according the provi-
sioned settings).
Low Order Path Sig- Major Minor This alarm is raised when the Check STM-1 source
nal Label Mismatch value of V5 [bit5-7] in VC-12
(VC12-SLM) POH is different from the
expected value (010: asyn-
cronous mapping). The
alarm becomes significant
and must be reported if STM-
1 LOS, STM-1 LOF , STM-1
TIM, MS-AIS, AU4-AIS,
AU4-LOP, VC4-SLM, VC4-
LOM, TU12-AIS or TU12-
LOP alarms are not present.
As consequent action the rel-
evant E1 will be replaced with
AIS (and then circuit emu-
lated according the provi-
sioned settings)
E1 in STM-1 Tx Alarm Major Minor It reports the Alarm Indication Check STM-1 source
Indication Signal Signal detected on E1 in
(E1-tx AIS) STM-1 on ingressing (Tx
side) and it is detected
according to G.775-sect.4.
The alarm becomes signifi-
cant and must be reported if
STM-1 LOS, STM-1 LOF ,
STM-1 TIM, MS-AIS , HP-
AIS or LP-AIS alarm is not
present.
E1 in STM-1 Rx Alarm Major Minor It reports the Alarm Indication Check STM-1 source
Indication Signal Signal detected on each E1
(E1-rx AIS) in STM-1 on egressing (Rx
side) and it is detected
according to G.775-sect.4.
The alarm becomes signifi-
cant and must be reported if a
Loss of CESoETH Frame
alarm is not present.
E1 in STM-1 Rx Loss Major Minor It reports the loss of frame Check STM-1 source
Of Frame detected on each E1 in STM-
(E1-rx LOF) 1 on egressing (Rx side) and
it is detected according ITU-T
G.706-sect.4, and G.706-
Annex_B. The alarm
becomes significant and
must be reported if the E1 is
configured as framed and a
Loss of CESoETH Frames
or E1-rx AIS alarms are not
present. Due to LOF alarm
detection an AIS must be
inserted as consequent
action. AIS insertion: set all
'1' on data.
Underlying Resource Major Major On detection of card failure Replace STM-1 Access
Unavailable (URU) the STM-1 port objects emit a card
communication Alarm notifi-
cation showing the transmis-
sion resources are affected
by the equipment failure
16E1DS1 ASAP Card Fail Major - Failure of ASAP Card Replace ASAP Card
Card
Equipment Mismatch Major - Card in slot does not match Install correct configured
Card configured in Core-E card
memory
Card Missing Major - ASAP Card is missing from Install ASAP Card in slot
slot
Loss Of Signal (LOS) Major - Loss of signal on each Check E1 source and/or
incoming E1 signal cable
(detected according to ITU-T
G.775-sect.4)
Loss Of Frame (LOF) Major - Loss of frame on each incom- Check to CRC4 multi-
ing E1 signal (detected frame alignment of the
according to ITU-T G.706- Far End equipment
sect.4)
Loss of Cell Delinea- Major - Loss of ATM cell delineation Check the ATM scram-
tion (LCD) on each incoming E1 signal, bling of the Far End
when the E1 port is used as equipment
physical layer for ATM
(detected according to ITU-T
I.432)
Loss of IMA Frame Major - Loss of IMA Frame on each Check the IMA configu-
(LIF) incoming E1 signal, when the ration of the Far End
E1 port is used as IMA link equipment
(detected according to IMA
Standard AF-PHY-
0086.000)
Link Out of Delay Major - It reports the event that, when Check the synchroniza-
Synchronisation the E1 port is used as IMA tion of the Far End equip-
(LODS) link, it is not synchronized ment
with the other links within the
IMA group (detected accord-
ing to IMA Standard AF-
PHY-0086.000)
RDI/Link Failure Major - It reports, when the E1 port is Check the Far End
used as IMA link, the OR of equipment
other alarms that are fore-
seen by IMA Standard AF-
PHY-0086.000:
– RFI-IMA
– Tx-Mis-Connected
– Rx-Mis-Connected
– Tx-Unusable-FE
– Link Rx-Unusable-FE
IMA Group Trail Sig- Major - It reports, for a configured Check the Far End
nal Fail (TSF) IMA Group, the event that its equipment
Group 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 TSFAlarm is also
generated by OR of the fol-
lowing 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-Mis-
match
EAS Card Card Fail Major - EAS card failed Replace EAS Card
Equipment Mismatch Major - Card in slot does not match Install correct configured
card configured in Core-E card
memory
Card Missing Major - EAS card is missing from slot Install EAS Card in slot
SFP missing alarm Major - The SFP optional plug-in is Install the plug-in in the
provisioned, but not present SFP slot
LOS on Gigabit ETH Major - Loss of Ethernet is detected Check link partner and
Interface cable between link part-
ner and Ethernet con-
nector
Fans Unit Card Fail Major - Fan failed Replace fan unit
Card Missing Major - Fan unit is missing from slot Install fan unit
Unconfigured Equip- Minor Minor Unit is not Enabled on the Enable fan unit
ment Settings screen
Configuration/Alarm
Modem Card Card Fail Major Minor Minor Modem Card failed Replace Modem Card
Equipment Mismatch Minor Minor Minor Card in slot does not Install correct config-
match card configured ured card
in Core-E memory
Card Missing Major Minor Minor Modem Card is missing Install Modem Card in
from slot slot
Unconfigured Equip- Minor Minor Minor Card is not Enabled on Enable card
ment the Settings screen
PNU Cable Loss Major Minor Minor Bad cable connection Check/repair IF cable
at IF in/out connector connection on alarmed
on Modem Card Modem Card
Loss of Radio Frame Minor Minor Minor Far end problems, RF 1. Switch far end
path problems, or local equipment (in a
circuit failures have protected system).
caused BER to If alarm clears,
increase to the point replace far end off-
that frames are being line Modem Card.
lost 2. Check/troubleshoot
far end alarms
3. Replace alarmed
Modem Card
Loss of Alignment N/A Minor Minor Delay between main 1. Replace main Radio
and protect RF paths Modem Card
detected 2. Replace protect
Modem Card
3. Replace main ODU
4. Replace protect ODU
Demod Function Fail Major Minor Minor Internal receive circuit Replace Modem Card
failure
High BER Major Minor Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded on clear, antenna is
RCVR input circuits on aligned, and no
modem existing weather-
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 Mis- Major Major Major Link identifier number Set numbers at both
match provisioned on Modem ends of hop to match
Card settings screen is
different from link iden-
tifier number provi-
sioned at other end of
hop
TCA on Radio Link N/A N/A Major Alarm threshold Switch far end equip-
exceeded on standby ment (in a protected sys-
Modem Card tem). If alarm clears,
replace far end off-line
Modem Card
UAT on Radio Link N/A N/A Major 10 consecutive SES Switch far end equip-
(unavailable time ment (in a protected sys-
period) detected on tem). If alarm clears,
main Modem Card replace far end off-line
Modem Card
Firmware Download Minor Minor Minor Download status Wait for downloading to
In Progress complete
Degraded Signal Minor Minor Minor Low quality sync signal Replace Modem Card
from Modem Card
License Mismatch for Major Major Major Modem card type does Replace Modem Card
Equipment Provi- not match card type with correct card type
sioned stored in memory on
the Core-E Card flash
card
Underlying Resource Major Major Major On detection of card Replace Modem Card
Unavailable (URU) failure the Radio port
objects emit a commu-
nication Alarm notifica-
tion showing the
transmission
resources are affected
by the equipment fail-
ure
ODU300 Card Fail Major Minor Minor ODU failed Replace ODU
Equipment Mismatch Major Minor Minor ODU does not match Replace ODU
ODU configured in
Core-E memory
RCV Function Fail Major Minor Minor ODU receiver circuit Replace ODU
failed
Software Mismatch Minor Minor Minor Software version on Download correct soft-
ODU does not match ware version
software version on
Core
ODU Not Responding Minor Minor Minor Loss of communication 1. Replace ODU
with ODU 2. Replace alarmed
Modem Card
Firmware Download Minor Minor Minor Download status Wait for downloading to
In Progress complete
Configuration/Alarm
MPT Access Card Fail Major - - MPT Access Card Replace MPT Access
Card failed Card
Equipment Mismatch Major - - Card in slot does not Install correct config-
match card configured ured card
in Core-E memory
MPT Power Supply Major - - Power Supply Failure Check/repair the cable
Failure connection. If ok,
replace MPT-HC
Loss Of Ethernet Sig- Major - - Loss of the incoming Check the cable con-
nal Ethernet signal (the nection. If ok, replace
signal is missing) or a the MPT Accerss unit
communication prob-
lem with the remote
peer (i.e. the communi-
cation has not been
established for physi-
cal problem on cable or
interface -> link down)
Ethernet Link Error Minor - - Partial failure of electri- Check the cable con-
cal or optical cable for nection. If ok, replace
the GbEth port the MPT Accerss unit
MPT-HC/ Card Fail Major Minor Minor MPT-HC failed Replace MPT-HC
MPT-HC V2
Equipment Mismatch Major Minor Minor MPT-HC does not Replace MPT-HC
match MPT-HC config-
ured in Core-E memory
RCV Function Fail Major Minor Minor MPT-HC receiver cir- Replace MPT-HC
cuit failed
Modulation parame- Major Minor Minor The modulation param- Change the modulation
ters Mismatch eters already config- parameters
ured and stored in the
MPR DB are not actu-
ally supported by MPT
Software Mismatch Minor Minor Minor Software version on Download correct soft-
MPT-HC does not ware version
match software version
on Core
Firmware Download Minor Minor Minor Download status Wait for downloading to
In Progress complete
Loss of Radio Frame Major Minor Minor Far end problems, RF 1. Switch far end
path problems, or local equipment (in a
circuit failures have protected system).
caused BER to If alarm clears,
increase to the point replace far end off-
that frames are being line MPT-HC.
lost 2. Check/troubleshoot
far end alarms
3. Replace alarmed
MPT-HC
Loss of Alignment N/A Minor Minor Delay between main 1. Replace main MPT-
and protect RF paths HC
detected 2. Replace protect MPT-
HC
Demod Function Fail Major Minor Minor Internal receive circuit Replace MPT-HC
failure
High BER Major Minor Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded clear, antenna is
aligned, and no
existing weather-
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 Mis- Major Major Major Link identifier number Set numbers at both
match provisioned is different ends of hop to match
from link identifier num-
ber provisioned at
other end of hop
MPT Loop Communi- Minor Minor Minor Communication prob- Check the radio hop
cation alarm lem between the local
MPT and the remote
MPT for all the func-
tionalities requiring a
communication loop
(ATPC, ACM, Pre-dis-
torsion)
Sync Degraded sig- Minor Minor Minor This alarm can raise if Check the radio hop
nal the addressed Radio
interface has been con-
figured as primary/sec-
ondary
synchronization
source. It is active if the
frequency of the clock
recovered from radio
Rx signal is mistuned
Coupling port Loss of N/A Minor Minor For the MPT Coupling Check the cable
Ethernet Signal optical port:
- the loss of incoming
Ethernet signal (the
signal is missing);
- a communication
problem with the
alternate MPT (i.e. the
communication has
not been established
for physical problem
on cable or interface
-> link down).
When this alarm is
raised, RPS is not
working
Coupling port Link N/A Minor Minor For the MPT Coupling Check the cable
Error optical port, the ratio
between the number of
received errored pack-
ets and the total num-
ber of received packets
is above a given
threshold.
When this alarm is
raised, RPS is not
working
Traffic port Link Error Minor Minor Minor For the MPT Traffic Check the cable
optical port, the ratio
between the number of
received errored pack-
ets and the total num-
ber of received packets
is above a given
threshold
MPT Tx Clock Failure Minor Minor Minor The MPT is not able to Check the radio hop
lock the air Tx symbol
rate to the NE Clock
TCA on Radio Link N/A N/A Major Alarm threshold Switch far end equip-
exceeded on standby ment (in a protected sys-
MPT-HC tem). If alarm clears,
replace far end off-line
MPT-HC
UAT on Radio Link N/A N/A Major 10 consecutive SES Switch far end equip-
(unavailable time ment (in a protected sys-
period) detected on tem). If alarm clears,
main MPT-HC replace far end off-line
MPT-HC
Degraded Signal Minor Minor Minor Low quality sync signal Replace MPT-HC
from MPT-HC
PPP IP Fail Minor Minor Minor Point to point IP failure Check the settings
Incompatible protec- N/A Major Major 1+1 configuration has Remove the protection
tion been provisioned configuration or modify
between the two MPT- the hardware
HC or the two MPT-HC
V2, but the RPS or the
XPIC module have not
been deployed. When
this alarm is active, the
Transmitter is muted
XPIC cable loss (only N/A Major N/A Loss of signal on the Chec the cable
for MPT-HC V2 with XPIC interface
the “RPS+XPIC
external module”
installed
Configuration/Alarm
Equipment Alarm Description Most Probable Cause Action
1+0 1+1 HS
RCV Function Fail Major Minor MPT-MC receiver cir- Replace MPT-MC
cuit failed
Modulation parame- Major Minor The modulation param- Change the modulation
ters Mismatch eters already config- parameters
ured and stored in the
MPR DB are not actu-
ally supported by MPT
Loss of Radio Frame Major Minor Far end problems, RF 1. Switch far end
path problems, or local equipment (in a
circuit failures have protected system).
caused BER to If alarm clears,
increase to the point replace far end off-
that frames are being line MPT-MC.
lost 2. Check/troubleshoot
far end alarms
3. Replace alarmed
MPT-MC
Loss of Alignment Minor Minor Delay between main 1. Replace main MPT-
and protect RF paths HC
detected 2. Replace protect MPT-
HC
Demod Function Fail Major Minor Internal receive circuit Replace MPT-MC
failure
High BER Major Minor Bit Error Rate threshold 1. Verify RF path is
(10E-4) exceeded clear, antenna is
aligned, and no
existing weather-
related problems
2. Verify RSL is above
RCV threshold.
If not – check
upstream transmitter
output/troubleshoot
transmitter
Link Identifier Mis- Major Major Link identifier number Set numbers at both
match provisioned is different ends of hop to match
from link identifier num-
ber provisioned at
other end of hop
MPT Loop Communi- Minor Minor Communication prob- Check the radio hop
cation alarm lem between the local
MPT and the remote
MPT for all the func-
tionalities requiring a
communication loop
(ATPC, ACM, Pre-dis-
torsion)
Sync Degraded sig- Minor Minor This alarm can raise if Check the radio hop
nal the addressed Radio
interface has been con-
figured as primary/sec-
ondary
synchronization
source. It is active if the
frequency of the clock
recovered from radio
Rx signal is mistuned
MPT Tx Clock Failure Minor Minor The MPT is not able to Check the radio hop
lock the air Tx symbol
rate to the NE Clock
TCA on Radio Link N/A N/A Alarm threshold Switch far end equip-
exceeded on standby ment (in a protected sys-
MPT-MC tem). If alarm clears,
replace far end off-line
MPT-MC
UAT on Radio Link N/A N/A 10 consecutive SES Switch far end equip-
(unavailable time ment (in a protected sys-
period) detected on tem). If alarm clears,
main MPT-MC replace far end off-line
MPT-MC
Degraded Signal Minor Minor Low quality sync signal Replace MPT-MC
from MPT-MC
PPP IP Fail Minor Minor Point to point IP failure Check the settings
RCV – Receiver
• For example, if multiple alarms are present, and these include power supply voltage or hard-
ware 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.
• 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), communi-
cations 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.
Note
– Normally a path problem is signalled 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.
A path problem on an existing link, one that has been operating satisfactorily may be caused by:
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.
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.
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 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.
One or both antennas incorrectly aligned. Refer to Installation alignment procedure on CD.
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.
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, par-
ticularly if the survey was a simple line-of-sight. If suspected, resurvey the path.
– 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 con-
figuration.
• 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 soft-
ware is required; install the latest software.
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.
All traffic-carrying circuits must have a unique flow ID for the cross-connect capability to operate.
Trib line interface settings incorrect, or line levels incompatible. While no alarm activates for an incor-
rect setting, its effect may result in line levels being too low (LOS alarm), or too high, resulting in a
high BER.
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.
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.
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:
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:
c) Turn on NE power.
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.
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 that the Core-E card LED STATUS (S) ends 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.
1) Get a spare FLASH CARD with the same sw-package release and license of the Main flash.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare one.
4) The MIB (MAIN FLASH) will be automatically aligned with the MIB (SPARE FLASH).
1) Get a spare FLASH CARD with the same sw-package release and license.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare one.
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.
By changing the Main Flash card, also the MAC address changes:
in this case the cross-connection must be reviewed.
6.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.
1) Plug-in the Access card (E1 or STM-1) in slot 4 (spare). An Unconfigured Equipment alarm dis-
plays. Note: in the figure is shown the 32E1 Access card.
3) On WebEML Settings screen enable the Access card (E1 or STM-1) in slot 4.
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 126., Figure
127. and Figure 128.
Starting from a 1+0 configuration (see an example in the graphics below) perform the following procedure
to upgrade to a 1+1 Frequency Diversity and 1+1 EPS.
1) Plug-in the Access card (E1 or STM-1) in slot 4 (spare). An Unconfigured Equipment alarm dis-
plays. 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 1+1 FD 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.
9) Properly configure the protection ODU.
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 126., Figure
127. and Figure 128..
Note
6.7.1 1+0 Adaptive Modulation to 1+1 HSB/FD 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.
1) Plug-in the Access card (E1 or STM-1) in slot 4 (spare). An Unconfigured Equipment alarm dis-
plays.
Note: in the figure is shown the 32E1 Access card.
2) Plug-in MPT Access 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.
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 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.
7) Connect the signal cables to the spare the Access card (E1 or STM-1) in slot 4.
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 “Multicast” to “Unicast” as explained in Figure 126., Figure
127. and Figure 128..
6.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.
6.8.1 1+1 HSB Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation
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.
Note: in the figure is shown the 32E1 Access card.
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 Pro-
tection.
5) On WebEML Settings screen provision the MPT Access cards (slots 7 and 8) for HSB 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 Chan-
nel #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.
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 “Multicast” to “Unicast” as explained in Figure 126., Figure
127. and Figure 128..
6.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.
1) Disconnect E1 signal cables from the spare the Access card (E1 or STM-1) in slot 4.
Note: in the figure is shown the 32E1 Access card.
Note
4) On WebEML Settings screen provision the MPT Access cards (slots 7 and 8) for HSB or FD
Protection Type. The Local station will observe a short traffic impact.
5) On WebEML Settings screen for the Access card (E1 or STM-1) (slots 3 and 4) set Protection
Type to no Protection.
6) On WebEML Settings screen for Modem cards (slots 7 and 8) set Protection Type to no Pro-
tection.
7) On WebEML Settings screen for spare the Access card (E1 or STM-1) (slot 4) set Equipment
Type to EMPTY.
8) On WebEML Settings screen for spare Modem card (slot 8) set Equipment Type to EMPTY.
10) Remove spare the Access card (E1 or STM-1) (slot 4).
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 “Multicast” to “Unicast” as explained in Figure 126., Figure
127. and Figure 128..
Note
6.9.1 1+1 HSB/FD Adaptive Modulation and 1+1 EPS to 1+0 Adaptive Modulation
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.
Note: in the figure is shown the 32E1 Access card.
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.
5) On WebEML Settings screen provision the MPT Access cards (slots 7 and 8) for HSB or FD
Protection Type. The Local station will observe a short traffic impact.
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 MPT Access card (slot 8) set Equipment Type to
EMPTY.
11) Remove spare the Access card (E1 or STM-1) (slot 4).
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 “Multicast” to “Unicast” as explained in Figure 126., Figure
127. and Figure 128..
6.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.
6.10 Cleaning
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.
Subject On page
Introduction 934
General 934
Conventions 935
7.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 Rel.3.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.
All the cables and measurement kits as described in Table 61. below are supposed to be available.
ATM Analyzer 1
V.11 Analyzer 1
The Alcatel–Lucent Software package SWP 9500 MPR-E V3.1.0 must have already been installed in the
PC used as the WebEML (WebEML) and the same software V3.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 accesso-
riesrequired for that purpose.
If not yet done, read whole Chapter 1 on page 31: 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.
7.1.3 Conventions
To simplify the description of actions, the following symbols are in use:
3 Check/Verify
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 sta-
tion B (see figure below). Installation and commissioning begin at station A.
MSS MSS
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.
a) Station A, roughly point the antenna towards station B (if not done in the Hardware Instal-
lation procedure)
MSS MSS
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
MSS MSS
3) Station A, perform all the commissioning checks and tests – Report the results in the TRS.
MSS MSS
MSS MSS
For detailed information on the layout and equipment interconnections refer to the Plant documen-
tation.
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.
– 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.
3 The antenna of station A (or B) is pointed towards station B (or A) the best as possible (use compass
if necessary).
• The power supply voltage is present with the correct polarity at the MSS power supply input
• The ODU(s) ground connections (In the case of a non–integrated antenna, the antenna and the
ODU(s) must be ground connected)
– 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:
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
& For near future tests, establish, on the DDF of Station B, hardware loops on every tributary.
Note 2: 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 align-
ment refer to Annex A: fine antenna alignment on page 971.
Subject On page
3 In the lower right window, verify in the alarms list that there is no TX failure
& 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 (for MPT-HC)
3 Verify that ATPC is ”Disabled” (If required, change the ATPC status to disable in the ATPC field then
o Apply)
3 Verify that Tx Power value complies with the suitable value already set (If required, change the Tx
Power in the RTPC field then o Apply)
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 (for MPT-HC)
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 an Rx levels:
3 Verify in the hop calculation (plant documentation) that the calculated received level has been
reached.
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.
– 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:
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 var-
ious tests.
Most of the tests and checks results have to be recorded in the TRS (Test Results Sheet). Operator will
be invited to do so each time it is required by the following sentence: “Report… in the TRS.”
N.B. The lettered titles in following table [ a ) , b ) , etc.] correspond to the page’s heading titles of
the TRS document.
EPS Protection 3
i) NE configuration 959
See and fill the indoor inspection check list in the TRS.
See and fill the indoor inspection check list in the TRS.
& WebEML Double click on the front panel of the Modem unit for ODU300 or of the MPT Access unit
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC o Settings tab panel
In the left window o Mode (Presettings or Adaptive modulation), Channel spacing, Modulation (Sup-
ported Modulation Schemes and Switching Threshold, if the Adaptive Modulation has been enabled)
Double click on the front panel of the Modem unit for ODU300 or of the MPT Access unit or on the MPT-
HC/MPT-MC for MPT-HC/MPT-MC o Link Identifier
Report the Link Identifier status (Enabled or Disabled), and, if Enabled, the “Expected” and“Sent” values.
In the lower right window o Protection Scheme Parameters Tab panel o Protection Type 1+1
In the lower right window o Protection Scheme Parameters Tab panel o Protection Type 1+1
In the lower right window o Protection Scheme Parameters Tab panel o Protection Type 1+1
& WebEML Double click on the front panel of the Modem unit for ODU300 or of the MPT Access unit
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC
If required, change the Tx frequency then o Apply. Rx Freq. will be automatically adjusted.
7.6.2.7 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 of the MPT Access unit
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC o Setting tab panel
3 ATPC “Disabled”
Report the ATPC “Disabled” status, Tx nominal Power and Tx Power setting into theTRS.
ATPC Enabled:
& WebEML Double click on the front panel of the Modem unit for ODU300 or of the MPT Access unit
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC o Setting tab panel
“RTPC&ATPC” field
3 ATPC “Enabled”
Report the ATPC “Enabled” status, ATPC Range and ATPC RX Threshold setting in the TRS.
If required, change ATPC Mode or ATPC Range or ATPC Rx Threshold then o Apply
Purpose: Verify via WebEML the Transmitted (PTx) and Received (PRx) power.
& WebEML Double click on the front panel of the Modem unit for ODU300 or of the MPT Access unit
or on the MPT-HC/MPT-MC for MPT-HC/MPT-MC
o From the left window o select Channel #1 o select Measurements tab panel
o In the Sample time (sec), write the suitable measurement poling time then press o 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 an Rx levels.
Report the Current Tx Local End (PTx) and the current Rx Local End (PRx) in the TRS.
Purpose: Verify via WebEML the IF cable loopback functionality (only in the local NE)
– 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 oSet-
tings tab panel).
IF cable loopback
& WebEML Double click on the front panel of the Modem unit o “Loopback” tab panel
To remove the loopback: in the lower right window o Not Active o Apply
Purpose: Verify via WebEML the Core-facing loopback functionality (only in the local NE)
– Ensure that the local tributary access is active (unframed and configured).
& WebEML Double click on the front panel of the MPT-Access unit or on the MPT-HC/MPT-MC o
“Loopback” tab panel
To remove the loopback: in the lower right window o Not Active o Apply
Purpose: Force command (if the active channel is the Main) and Lockout command (if the
active channel is the Spare)
In the Commands tab panel window Commands scroll list o Forced or Lockout o Apply
Repeat for HSB Tx Protection (for “1+1 HSB” configurations only)
3 Check in the Summary block diagram that the full channel (Tx and Rx) path is in service.
& WebEML Double click on the front panel of the P32E1DS1 unit
Purpose: Force command (if the active channel is the Main) and Lockout command (if the
active channel is the Spare)
3 Check in the Summary block diagram that the full channel (TX and RX) path is in service.
Figure 660. Test bench for tributary functionality check with ODU300
Assuming that all the tributaries have been enabled and configured (Unframed status and configu-
ration) via WebEML in both stations and that every tributary is looped at the DDF in the remote sta-
tion:
& 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.
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 there-
levant tributary goes off.
Report about the Tributary BER test and alarm WebEML monitoring in the TRS.
& WebEML Double click on the front panel of the SDHACC unit
Purpose: Force command (if the active channel is the Main) and Lockout command (if the
active channel is the Spare)
3 Check in the Summary block diagram that the full channel (TX and RX) path is in service.
Figure 663. Test bench for tributary functionality check with ODU300
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:
& 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.
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 therelevant STM-
1 goes off.
Report about the BER test and alarm WebEML monitoring in the TRS.
& WebEML Double click on the front panel of the 16E1/DS1 ASAP unit
To configure refer to par. 3.18.1 on page 476.
& WebEML Double click on the front panel of the 16E1/DS1 ASAP unit
To configure refer to par. 3.18.2 on page 477.
& WebEML Double click on the front panel of the 16E1/DS1 ASAP unit
To configure refer to par. 3.18.3 on page 479.
& WebEML Double click on the front panel of the 16E1/DS1 ASAP unit
To configure refer to par. 3.18.4 on page 485.
& WebEML Double click on the front panel of the AUX unit
To configure refer to par. 3.20.1 on page 498.
& WebEML Double click on the front panel of the AUX unit
To configure refer to par. 3.20.2 on page 499.
& WebEML Double click on the front panel of the EAS unit
To configure refer to par. 3.14 on page 424.
& WebEML Double click on the front panel of the Core-E unit
In the left window o Ethernet Port#1 or Ethernet Port#2 or Ethernet Port#3 or Ethernet Port#4 or Optical
SFP Ethernet Port #5.
7.6.9 NE configuration
& WebEML Double click on the front panel fo the Core-E unit TMN Interface tab panel
Report the IP Address, IP Mask, IP Routing protocol and OSPF Area in the TRS.
Report the IP Address, IP Mask and Default gateway IP Address or interface type into theTRS.
& WebEML Menu bar Configuration Network Configuration NTP Server Configuration
Enter the IP address of the NTP Server, if any.
– 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)
i Via the WebEML, let only one active tributary in both station
i In the remote Station, place a hardware loop on the relevant tributary access (at the station DDF).
i In the local station, connect the E1 Data Analyzer on the relevant tributary. Check that the
“Tributary Alarm Loss” disappears.
3 Verify in both stations that there are no active software loopbacks or switching requests.
Report the two-hour error-free of error Hop Stability Test result in the TRS.
Figure 666. Test bench for tributary functionality check with MPT-HC/MPT-HC V2/MPT-MC
– The Hop stability test is performed during two consecutive hours, one time, on one 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)
i Via the WebEML, let only one active STM-1 in both station
i In the remote Station, place a hardware loop on the relevant STM-1 access (at the station DDF).
i In the local station, connect the SDH Data Analyzer on the relevant tributary. Check that the
“STM-1 Alarm Loss” disappears.
3 Verify in both stations that there are no active software loopbacks or switching requests.
Report the two-hour error-free of error Hop Stability Test result in the TRS.
Figure 667. Test bench for hop stability test with ODU300
Procedure:
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]
Report about the connectivity test of Ethernet Data Channels in the TRS.
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.
3) Configure the pattern A generator, in order to generate continuos traffic, and set the data rate-
half to the radio capacity and with packet size of 1518 bytes.
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 TRS.
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
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 o Programs o Accessories o 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 669. Test bench for optional Ethernet Data Channel functionality 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, connect the additional PC on 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
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 o Programs o Accessories o 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 670. Test bench for optional Ethernet Data Channel functionality with 2 additional PCs
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)
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
Figure 671. Test bench for optional Ethernet Data Channel functionality with
2 Ethernet Data Analyzers
Procedure:
– The Hop stability test is performed during two consecutive hours, one time, on one IMA Group con-
figured on 16E1DS ASAP peripheral, in realworking condition whatever the radio peripheral protec-
tion 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)
• "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
– associate to IMA Group #1 of relevant ASAP peripheral and make active as IMA Links the
E1 ports #1,#2,#3,#4
– 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
Report about the IMA connectivity test of ATM Data Channels in the TRS.
• On ATM interface #1 (associated to IMA Group #1) of relevant ASAP peripheral create and con-
figure:
– "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 periph-
eral, with associated VLAN ID = 4000
e) Configure in the remote Station a Loopback at DDF level, as shown in Figure 672.
• 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
• 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 TRS.
Required Instruments: PC with WebEML software and RS422 / V11 64 Kbit/s Data Analyzer
Figure 673. Test bench for 64 kbit/s Service Channel functionality check
Assuming that the User service Channel is looped in the remote station:
Report about the 64 Kbit/s Data channel BER test into the TRS.
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 beaware 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.
– or, after having logged in the NE, use the WebEML received power measurement facility
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 Serfice kit cable for the MPT)
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 polemounting
employed.
ABBREVIATION MEANING
AP Access Point
AS Alarm Surveillance
CD Current Data
CI Communication Infrastructure
DS Degraded Signal
EC Equipment Controller
EML domain A set of NEs that are maintained by the same EML-OS.
ES Errored Second
ETH ETHernet
EW Early Warning
FD Frequency Diversity
FE Fast Ethernet
FM FM Fault Management
HD History Data
HS Hitless Switch
IM Information Model
IP Internet Protocol
IM Information Manager
NE Network Element
OC ODU Controller
OH OverHead
OS Operation System
PM Performance Monitoring
PI Physical Interface
QL Quality Level
RI Remote Inventory
SA Site Aggregator
SD Signal Degrade
SF Signal Failure
TD Threshold Data
TRsp Tx Rx spacing
TS Time Slot
VC Virtual Channel
VP Virtual Path
Scope of this activity is the improvement and innovation of customer documentation through the under-
standing of customer needs.
You can send them to your Local Alcatel-Lucent Technical Assistance Center.
The following form supplies an example only of useful info, as a guide of the type of expected feedback.
It is possible fill part of the form, add other data and so on.
• copying the example form, filling it and sending it to your Local Alcatel-Lucent Technical Assis-
tance Center. In this case handbook data are already available at the page bottom.
• using the same form available as a file in the relevant documentation CD-ROM, saving, filling
and sending it by e-mail to your Local Alcatel-Lucent Technical Assistance Center.
• creating a dedicated form on paper or file and sending it to your Local Alcatel-Lucent Technical
Assistance Center.
We reserve to modify consequently the handbook according to the corretness and congruence of the sug-
gestion and requests.
How to deepen:
Other comments/suggestions
Errors Identified
Reader Info
Name:
Company:
Address:
E-mail:
Phone:
www.alcatel-lucent.com