Document Type: Alarm

Generated: 2015-09-02 16:54

Used search parameters: Product=Base Station, Product release=SBTS16.2
Alarm number
7100
7101
7102
7103
7104
7105
7106
7107
7108
7109
7110
7208
7600
7602
7606
7607
7625
7995
61022
61028
61029
61030
61040
61104
61150
61151
61152
61250
61251
61252
61605
61606
61607
61610
61611
61622
61632

Name
HARDWARE PROBLEM
RESET NOTIFICATION
RESOURCE BLOCKED
BY USER ALARM
EXTERNAL
NOTIFICATION
CELL SERVICE
PROBLEM
RAT BASE STATION
PROBLEM
SINGLE RAN BASE
STATION
PROBLEM
BASE STATION
CONNECTIVITY
BASE STATION
PROBLEM
SYNCHRONIZATION
BASE STATION
PROBLEM
SECURITY
PROBLEM
BASE
STATION
LICENSE
LIMITATION
LOCAL BLOCK
BCF FAULTY
BCF NOTIFICATION
TRX FAULTY
TRX OPERATION
DEGRADED
PS U-PLANE
CONNECTION
FAILURE
MAINS BREAKDOWN
WITH
BATTERY
BACKUP
BFD group
$bfdGrpId
down
LOF on unit $U, interface
$IF
LOS on unit $U, interface
$IF
Dead Peer Detected
Interface under test on unit
$U,
interface
$T
EBER
on unit$IF
$U,for
interface
minutes
$IF
LOMF on unit $U, interface
$IF
AIS on unit $U, interface
$IF
RDI on unit $U, interface
$IF
IPCP Failure
LCP Failure on Interface
$IF
PPP Interface down
BFD $session down,
ingress,
$sourceIP
to
BFD $session
down,
$destinationIP
egress,
$sourceIPmismatch,
to
Auto-negotiation
$destinationIP
on
unit
$U,
Ethernet
TWAMP RTT threshold
interface
$IF
crossed
TWAMP PLR threshold
crossed
MLPPP link Degrade
Dup Addr detected
$duplicateIpv6Address

61639
61641
61643
61644
61645
61646

IPsec emergency bypass

active
IP Traffic Capturing
Ongoing
[portswitchover
$port,] [mac
IPsec tunnel
$m]
IKE authentication failure
IKE SA mismatch
IPSec SA mismatch

Station, Product release=SBTS16.2

Product, Product SW release, SW release increment
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0

- Base Station, release: SBTS16.2, increment: 0

- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0
- Base Station, release: SBTS16.2, increment: 0

Company confidential

Excluded from

System components

Subsystems

Dino document identifier Meaning of the alarm

A hardware fault (or faults)
has occurred
the base
The
device is in
being
reset to
station.
This
fault
may
recover
from
a
fault
(orhave
The service/device has
an
impact
on
the
existing
faults).
beenisblocked
by the
user.
This
an external
usercells across
RATs. Check
defined
alarm.
The
alarm
the
reason
for thehas
fault
A
fault
(or faults)
including
thea alarm
text is
from
the
supplementary
occurred
in
unit
(or
A fault (or faults) has units)
defined
by
the
user
during
text field
of
the
alarm.
that
belong
to the
sector
occurred
infaults)
the
RAT
A
fault (oralarm
hasbase
external
indicated
in
the
alarm.
station.
Check
reason
occurred
thethe
Single
RAN
configuration
A
fault the
(orinreason
faults)
has
Check
for the
for
the
fault
from
the
base station.
Check
the
occurred
in
the
base
fault
from
A
fault
(orthe
faults)
has
supplementary
text
field of
reason for the fault
from
station
supplementary
text
field of
occurred
in
the
base
thefault
alarm.
A
(or faults) has
the
supplementary
text
field
connectivity/interface.
the
alarm.
station
synchronization.
occurred
in the base
of
the
alarm.
Capacity
limitation
(or
Check
reason
for
Check the
the
reason
for the
the
station
security.
Check
the
limitations)
has occurred
fault
from
the
The
service/device
has in
fault from
the
reason
for
the
fault
from
the
base
station
due
to aof
supplementary
text
field
been
blocked
bytext
the
user.
supplementary
field
of
A
fault
(or faults)
has
the
supplementary
text
field
missing
license.
Check
the
the
alarm.
For alarm.
details,
refer
to
the
occurred
in
the
BCF.
of
thehas
alarm.
Fault
reason
foroccurred
the
fault that
from
GSM/EDGE
BSS
For
details,
refer
to
disallows
OSC/DFCA
the
supplementary
text field
A
fault (or Documentation.
faults) has
Operating
GSM/EDGE
BSS
feature
operation.
of
thehas
alarm.
occurred
in
the TRX.
Fault
occurred
that
Operating
Documentation.
For
details,
refer
For
details,
refer to
to
disallows
OSC/DFCA
A fault (or faults)
has
GSM/EDGE
BSS
GSM/EDGE
BSS
feature operation.
occurred
inDocumentation.
the
(E)GPRS
Operating
Main
power
is
lost.
Battery
Operating
Documentation.
For details,
refer to
protocol
layer.
backup
is
switched
The alarm is BSS
raised ON.
if the
GSM/EDGE
For
details,
referto
toGSM
For
details
refer
service
under
monitoring
is
Operating
Documentation.
This
Loss
of
frame
alarm
is
GSM/EDGE
BSS
Alarms
Documentation:
not
available
when
e.g. all
raised
when
the
local
Operating
Documentation.
This
is Alarms
raised when
Basealarm
Station
(7000network
paths
are to
notdetect
receiver
isorunable
either
no
an
7999);
DN9813099
A
dead
peer
was
detected
available.
This
implies
that
the
frame alignment
incompatible
signal isword
in
one
of the
IPsec
all
individual
BFD
sessions
This
alarm
is
raised
if
a
of the E1on
signal.
All other
received
the
interface
associations
ofbeen
the
SBTS.
of
thealarm
respective
group
are
loopback
has
transmission
alarms
related
This
is
raised
when
referenced
in
the
alarm
There
is
no
response
the
erroneous.
configured
byare
abit errortorate
to
this
signal
the
measured
text.
This
loss sent
of multiframe
requests
to the peer,
management
application
suppressed.
exceeds
the threshold
alarm
is raised
if IKE
thewhen
either
during
This
alarm
is the
raised
on
the
interface
mentioned
value
of
BER-3
(10E-3).
With
an
Ethernet
interface
interface
referenced
in the
SA
setup,
the
IPsec
SA
an
alarm
indication
signal
in
the
alarm
This
alarm
istext.
raised
when
a
Probable
cause:
The
thereceived.
physical
Ethernet
alarm
textduring
has
lost
thelink
setup
or
DPD.
is
This
signal
isisis
remote
defect
indication
interface
at
the
far end
is
Probable
causes:
The
alarmto
is
raised
if All
the
detected
be
down.
multiframe
alignment.
Note:
When
IPsec
backup
generated
by
an
received.
is
sent
by
the
not
toisbe
athe
-other
theconfigured
signal
level
too
low
IPCP
stateItismachine
is
in
transmission
alarms
The
alarm
raised
if
tunnel
featurePDH
isthe
enabled,
intermediate
device
intermediate
orInitial
far
endin
framed
E1cause:
interface.
(connectors
cables
are
the
Closed
oror
state
related
to
this
signal
are
Probable
The
LCP
state
machine
on
the
this
alarm
is
not
raised
the
forward
direction
This
alarm
is
raised
if
the
equipment
because
it
dirty,
electrical
connectors
and
cannot
reach
the
suppressed.
type
has
not
been
interface
is
in
the
Closed
or
due to
failures
when
because
itserious
detects
aiftrying
PPP
interface
is
not
detects
astate
fault
in
The
alarm
is
raised
the
or
cables
are
corroded)
Opened
within
100
configured
to
meet
the
Initial
state
and
cannot
to
setup
primary
IPsec
problem
in
its
received
operational
either
when allis
the
BFD
state
for
the
session
-Probable
thereceived
specified
maximum
milliseconds.
The
alarm
is signal.
raised
if theat
for
framing
the
reach
the
Opened
state
tunnel
inof
signal.
the
links
incauses
theinterface
bundle
of
not
AdminDown
and
length
of
the
cable
is
BFD
state
of
the
session
Ethernet
interfaces:
the
far
end.
For
E1
within
100
milliseconds.
This
alarmPPP
indicates
that is
"Secondary_Active_Probin
AIS
defect
is
detected
Multi-Link
are
not
Probable
cause:
Thethe
far
nevertheless
no and
BFD
exceeded
not
AdminDown
interfaces,
the
there
is
a threshold
mismatch
g_Primary"
state.
when
the
incoming
signal
available
or
Single-Link
The
RTT
alarm
is
end
has
a
LOS,
LOF
or
AIS
packet
is
received
at
the
-between
the
connector
is
not
BFD
packet
from
thefar-end
-raised
a cable/fiber
cut
orfar
configuration
ofis
the
SBTS
expected
has
two
or
less
zeros
in
PPP
link
is
not
available.
in
case
the
average
alarm
onconnected
its
receiving
local
end
during
the
The
alarm
is
raised
if the
properly
to
the
end
contains
theE1
diagnostic
there
is
no
cable/fiber
node
should
be
auto-negotiation
result
each
of
two
consecutive
value
ofloss
the
RTT
for thisand
interface.
detection
time.
packet
ratio
equals
or
unit
code
=
'Control
Detection
This
alarm
is
raised
if
at
connected
to the
interface
Multiframe.
actual
auto-negotiation
double
frame
periods
(512
TWAMP
session
from
the
exceeds
the
configured
-During
the
receiver
or
the
far
end
Time
Expired'
and
no
BFD
least
one
of
the
sessions
in
result.
theperiod
IP address
bits)
according
[G.775]
last
1-min
equals
or
The
alarm
is
raised
ifisthe
threshold
value
during
the
transmitter
has
failed
down
Ingress
alarm
Multi-Link
PPP
bundle
has
-configuration
the
electrical/optical
the SBTS
chapters
5.2 configured
and
exceeds
the
BFD
session
is inI.2.
activated
current
interval
-tests
theEthernet
accumulated
BER
of
present.
gone
down.
signal
isobservation
excessively
An
linkattached
was
the
direct
threshold.
state.
of
15
minutes.
the
end
to
end
E1
path
is
attenuated
established
but during
network
otherlink
All other whether,
transmission
too
high.
The
alarm
is raised
only
if
establishment
a
link
speed
already
configured
node,
alarms related to this
signal
BFD
session
is
in
activated
- the
port
at
the uses
connected
downshift
event
took place.
on
the
network
are
suppressed.
state.
far
endspeed
node
isIPv6
switched off
A link
already
samedownshift
takes
place
when
autoaddresses
on
their
network
Probable
cause:
There
is a

Effect of the alarm

The effect of the fault on
the functioning
the on
The
effect of theofalarm
network
element
depends
the
Network
Element
The service/device is
on
the fault description.
depends
blocked
byof
the
user.
It is
The
effect
the
alarm
For
more
information,
see
on
fault
description.
notthe
possible
to establish
depends
on
the
purpose
base
station
fault
The
effect
of
the
fault
on
For more
information,
see
phone
calls
through for
the
that
was
configured
descriptions
SBTS
the
offault
the on
base
station
fault
Thefunctioning
effect
of in
the
blocked
cell,
module
or
the
user-defined
alarm
System
Libraries.
network
element
depends
descriptions
in
SBTS
the
functioning
offault
the on
SBTS.
The
effect
the
input
in fault
theofSBTS.
on
the
description.
System
Libraries.
network
element
depends
the
the on
Thefunctioning
effectinformation,
of theoffault
For
more
see
on
the
fault
description.
network
element
depends
the
functioning
of
the on
base
station
fault
The
effect
of
the
fault
For
more
information,
see
on the
fault
description.
network
element
depends
descriptions
SBTS
the
offault
the on
basefunctioning
station
fault
The
effect
of in
the
For
more
information,
see
on
the fault
description.
System
Libraries.
network
element
depends
descriptions
in
SBTS
the functioning
offault
the on
base
station
fault
The
effect
of
the
For
more
information,
see
on
the
fault
description.
System
Libraries.
network
element
depends
descriptions
in
SBTS
the
network
element
base
station
fault
The
effect
of
the
fault
on
Forthe
more
information,
see
on
fault
description.
System
Libraries.
depends
descriptions
SBTS
the
functioning
offault
the on
base
station
fault
The
effect
of in
the
For
more
information,
see
on
the fault
description.
System
Libraries.
network
element
depends
descriptions
in
SBTS
the
functioning
offault
the on
base
station
fault
The
effect
of
the
Forthe
more
information,
see
on
fault
description.
System
Libraries.
network
element
depends
descriptions
SBTS
the
offault
the on
base
station
fault
Thefunctioning
effect
of in
the
For
more
information,
see
on
the fault
description.
System
Libraries.
network
element
depends
descriptions
in
SBTS
the
functioning
offault
the on
base
station
fault
The
effect
of
the
Forthe
more
information,
see
on
fault
description.
System
Libraries.
network
element
depends
descriptions
SBTS
the
offault
the on
basefunctioning
station
fault
The
effect
of in
the
For
more
information,
see
on
the fault
description.
System
Libraries.
network
element
depends
descriptions
in
SBTS
the
functioning
offault
the on
base
station
fault
The
effect
of
the
For
more
information,
see
on
the
fault
description.
System
Libraries.
network
element
descriptions
in
SBTS
the
ofdepends
thelink
basefunctioning
station
fault
The
communication
For
more
information,
see
on
the fault
description.
System
Libraries.
network
element
depends
descriptions
in
SBTS
between
the
local
SBTS
base
station
fault
Possible
impact
on
the
For
more
information, see
on
the
System
Libraries.
and
thefault
BFDdescription.
peer
is
descriptions
in
SBTS
connections
over
this
base
station
fault
No
data
or
clock
For more information,
see
defective.
No
System
Libraries.
interface:
descriptions
SBTS
information
isin
exchanged
base
station
fault
Possible
effects:
communication
is
possible.
-System
nothis
calls
are possible.
Libraries.
interface.
Possible
descriptions
SBTS
-via
no calls
areinpossible.
The
cannot
be
- lossinterface
ofon
remote
impact
the connections
Libraries.
-System
loss
of
remote
used
for
transmission.
management
access
toIt
Possible
impact:
over
this interface:
management
access to
can
benetwork
used for
elements.
-other
slow
management
access
The
otherperformance
network
elements.
connectivity
checks
only. if
-management
loss
synchronization
to
the of
SBTS
and
other
-Possible
calls
or
data
data
- voice
IKE SAs
and
IPsec
SAs
impact
on the
the
interface
is used
as
network
elements
in the
connections
are
aborted
collected
on
this
interface
cannot
beimpact
established
or
connections
overon
the
Possible
the
synchronization
source.
network
and cannot
be established
becomes
invalid.
re-keyed.
interface
in
question:
connections
overon
this
-anymore
poor voice
quality
and
Possible
impact
the
-interface:
no calls are possible
data performance
connections
overon
this
Possible
impact
the
-- loss
of remote
no calls
are possible
interface:
-Possible
remote
management
connections
over
this
management
access
to
impact
on the
lossPPP/ML-PPP
of remote
--interface:
the
connectivity
is
lostthis
and in
othercommunication
network
elements
connections
over
management
access
to
The
link
interface
not available.
beisestablished
-cannot
theRAN
PPP/ML-PPP
the
interface:
other
network
elements
in
between
the
local
and
the
-anymore
losscommunication
of remote
The
link
interface
is not available.
the
RAN
remote
peer
is
defective
or
access.
between
the SBTS
and the
-management
loss
of remote
The
Ethernet
Link
got
-the
thepeer
interface
is not
is
defective.
BFD
peer
is with
-This
lossalarm
of synchronization
management
access
established
an to if
available.
is an
indication
Transport
service
may
defective.Transport
service
the
interface
is
used
asnot
ain
other
network
elements
unexpected
clock
mode
or
-This
loss
of backhaul
remote
that
the
capacity
be
available
and
calls
may
alarm
is
an
indication
may
not
be
available
and
synchronization
source
the
RAN.
technology.
management
for
traffic
with access.
the same
be
dropped.
that
the
backhaul
capacity
calls
may
be
dropped.
Multi-Link
PPP
operates
profile
as with
this TWAMP
for
traffic
same
profile
reduced
capacity.
-with
Depending
on
use
of the
Possible
impact
on
The
remote
peervalue,
to the
come
session
(DSCP
as
this
TWAMP
session
Ethernet
interface
the
connections
over
thistoo
online
with
the
same
IP
packet
size)
may
be
(DSCP
value,
packet
size),
Possible
impact
on
the
above
described
impact
interface:
address
on
the same
small,
because
the
may
be
much
too
small,
connections
over
thiswould
can
occur
the
local
subnet
as for
local
peer
measurement
packets
are
because
someother
of the
interface:
and/or
(S)BTS
-SBTS
Increased
packet
delay
just
disable
their
network
scheduled laterpackets
than
measurement
elements
if they
are
variation
and
increased
interface
give
an error
before.to have
seem
thrown
-chained
the the
interface
supports
via
thebeen
Ethernet
average
delay
for
all
until
situation
is
away.
fewer
connections.
interface.
voice/packet
and
resolved
by the

SBTS has entered IPsec

emergency
active
The alarm isbypass
activated
state
where
configured
whenalarm
the IPwill
traffic
This
be triggered
IPsec policies
are is
ignored
capturing
session
when
at
least
one
primary
The
alarm
is raised
and all
traffic
is sentwhen
started.
IPsec
tunnel
fails
and
the
authentication
unprotected.
ThisIKE
alarm
is raised when
SBTS
has switched
over
to
credentials
provided
by the
the
peer
and
the
SBTS
The
SBTS
is
currently
This
alarm
indicates
that
secondary IPsec
tunnel.
peer
configuration
for IKE
profile
capturing
IPoftraffic
towards
the
and
the
SBTS
Asnot
apeer
result
failure
in at
is
valid.
do
not
match.
a local
port
or into
aIPsec
file on
security
policies
for
least
one
primary
IPsec
the
SBTS.
do
not
match.
tunnel,
SBTS has
automatically switched over
If
traffic capturing
is
tothe
secondary
IPsec tunnel
happening
towards
a
local
terminating on secondary
port,
the gateway.
port and
security
destination MAC address
needs to be provided.
Port values can be LMP or
< HW MODULE NAME ><PORT ID>.
Example: LMP or FSMEIF1, FSM-EIF2 or FTIFEIF1

All configured IPsec

policies
are ignored
The resulting
packetand all
the
SBTS
traffic
is
sentfor
capturetraffic
files has
can switched
used
SBTS
unprotected.
Expert
analysis
to
identify
over
fromSA
thecannot
primary
The IKE
be
network
problems
and to
IPsec
tunnel
to
secondary
established.
IKE SA
cannot be
help
determine
best
(backup)
IPsec the
tunnel
established
and
course
of
action.
The
related
IPsec
SA
can't
terminating on secondary
subsequently
no
IPsec
SAs
be
established
and
used.
security gateway.
can be established.

Version
2.1u
2.1u
2.1u
2.1u
2.1u
2.1u
2.1u
2.1u
2.1u
2.1u
2.1u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.0u
2.1u
2.1u
2.1u
2.0u
2.0u
2.0u
2.0u
2.0u
2.1u
2.1u

Document state
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED

Identifying application add

1. HW Inventory Id (RDN)
and
Serial
Number
of the
1.
HW
Inventory
Id (RDN)
impacted
hardware
unit
and
Serial
Number
of
the
1. HW Inventory Id (RDN)
2.
Path(URI)
of
the
impacted
hardware
unit
and
Serial
Number
the
1.
EAC
line
input IDof
impacted
hardware
2.
Path(URI)
of the unit,
impacted
hardware
unit
when
impacted
unit is
1.
HWthe
Inventory
Id (RDN)
impacted
hardware
2.
Path(URI)
of the unit,
FSM,
FT,
FSP,
FBB,
FR,
and
Serial
Number
of
the
when
the
impacted
unit
1.
HW Inventory
Id (RDN)
impacted
hardware
unit,is
FAN,Serial
AntennaLine,
MHA,
impacted
hardware
unit
FSM,
FT,
FSP,
FBB,
FR,
and
Number
of
the
when
impacted
unit
is
1.
HWthe
Inventory
Id (RDN)
RET,
FYG,
orofSFP.
2.
Path(URI)
the MHA,
FAN,
AntennaLine,
impacted
hardware
unit
FSM,
FT,
FSP,
FBB,
FR,
and
Serial
Number
of
the
1. HW Inventory
Id (RDN)
impacted
hardware
unit,
RET,
FYG,
orofSFP.
2.
Path(URI)
the MHA,
FAN,
AntennaLine,
impacted
hardware
unit
and
Serial
Number
of
the
when
the
impacted
unit
is
1.
HW
Inventory
Id
(RDN)
impacted
RET,
FYG,hardware
orofSFP.
2. Path(URI)
the unit,
impacted
hardware
unit
FSM,
FT,
FSP,
FBB,
FR,
and
Serial
Number
of
the
when
impacted
unit
1.
HWthe
Inventory
Id (RDN)
impacted
hardware
unit,is
2.
Path(URI)
of the MHA,
FAN,
AntennaLine,
impacted
hardware
unit
FSM,
FT,
FSP,
FBB,
FR,
and
Serial
Number
of
the
when
the
impacted
unit
1.
HW
Inventory
Id
(RDN)
impacted
hardware
unit,is
RET,
FYG,
orofSFP.
2.
Path(URI)
the MHA,
FAN,
AntennaLine,
impacted
hardware
unit
FSM,
FT,
FSP,
FBB,
FR,
and
Serial
Number
of
the
when
the impacted
For
details,
refer to unit
impacted
hardware
unit,is
RET,
FYG,
orofSFP.
2.
Path(URI)
the MHA,
FAN,
AntennaLine,
impacted
hardware
unit
FSM,
FT, FSP,
FBB,
FR,
GSM/EDGE
BSS
when
the
impacted
For
details,
refer
to unit
impacted
unit,is
RET,
FYG,
or SFP.
2.
Path
of hardware
the
impacted
FAN,
AntennaLine,
MHA,
Operating
Documentation.
FSM,
FT,
FSP,
FBB,
FR,is
GSM/EDGE
BSS
when
the impacted
For
details,
refer
to unit
hardware
unit,
when
the
RET,
FYG,
or SFP.
FAN,
AntennaLine,
MHA,
Operating
Documentation.
FSM,
FT, FSP,
FBB,
FR,
GSM/EDGE
BSS
impacted
unit
is
FSM,
FT,
ForDestination
details,
refer
to
3.
IP
address
RET,
FYG,
or SFP. MHA,
FAN, FBB,
AntennaLine,
Operating
Documentation.
FSP,
FR,
FAN,
GSM/EDGE
BSS
For details, refer to
RET,
FYG,Documentation.
or MHA,
SFP.
AntennaLine,
Operating
GSM/EDGE
BSSto RET,
For details, refer
FYG,
or SFP.
Operating
Documentation.
GSM/EDGE
BSSto
For details, refer
Operating
Documentation.
GSM/EDGE BSS
Operating Documentation.

TWAMP

2.0u
2.0u
2.0u
2.0u
2.0u
2.0u

PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED
PUBLISHED

FAULT ID
133: EFaultId_RxAntennaSignalLevelTooLowAl
134: EFaultId_RxAntennaSignalLevelDifferenceTooHighAl
MEANING
133: EFaultId_RxAntennaSignalLevelTooLowAl
The RX signal level is less than -112dBm
134: EFaultId_RxAntennaSignalLevelDifferenceTooHighAl
The difference between the maximum and minimum power levels of all RX antennas in the same
INSTRUCTIONS
Take the following actions to clear the fault:

Application additional info Instructions

Clearing
information
1. Check Element Manager for
the received
signal levels to find out which RX is causing the probl
Please check the below
Do not cancel the alarm.
2.
If an
MHA
alarm
active,
replace
the MHA
and check if the RX signal level failure alarm is
fault-specific
description
for Do
The
system
automatically
This
alarm
does
notisrequire
not
cancel
theunit
alarm.
detailed
instructions.
cancels
the
alarm
when
the
any
actions.
The
system
automatically
Unblock
Do not
cancel
the alarm.
3. If therethe
are antenna line devices,
check
them.
fault
has
been
corrected.
cancels
the alarm.
service/module
with
Thenot
system
automatically
The
operation depends
on Do
cancel
the alarm.
----------------------FAULT
NAME
WebUI.
cancels
the
alarm
when the
the
type
of
alarm
that
user
The
system
automatically
4.
Check
the antenna
The
radio
FAULT
NAME
notfaulty
cancel
themodule,
alarm. antenna feeder, or antenna can be identifie
# autonomous
reset ascables.Do
service/device
is unblocked
defined
as
external
alarm.
cancels
the
alarm
when the
10b8b
errorbelow
in
The
system
automatically
recovery
action
Pleasecoding
check
the
Do user.
not
cancel
the alarm.
FAULT
NAME
by
fault
has
been
corrected.
Optical Interface
device
cancels
the alarm
when the
fault-specific
description
system
automatically
RF
Module
blocked
Please
check
the below for The
Do not
cancel
the alarm.
FAULT
NAME
<opt
link/RP3>
fault
hasthe
been
corrected.
FAULT
ID
detailed
instructions.
cancels
alarm
when the
fault-specific
system
automatically
[User defined]
See description of the
Please
checkdescription
the below for The
Do not
cancel
the alarm.
52:
fault
has
been
corrected.
FAULT ID
detailed
instructions.
cancels
the alarm
when the
related fault
fault-specific
system
automatically
FAULT
ID
Please
checkdescription
the below for The
Do not
cancel
the alarm.
EFaultId_UnitAutonomous
1931:
EFaultId_FrBlocked
fault hasthe
been
corrected.
FAULT
ID
detailed
instructions.
cancels
alarm
when the
2004:
fault-specific
system
automatically
ResetAlNAME
FAULT
NAME
Please
checkdescription
the below for The
Do not
cancel
the alarm.
FAULT
1400:
EFaultId_ExtAl0
fault
has
been
corrected.
EFaultId_OIC_LVDSRecAl
detailed
instructions.
the alarm
when the
Address
mismatch
in
fault-specific
description
for cancels
Thenot
system
automatically
MEANING
Address
mismatch
in
Please
check
the faultDo
cancel
the alarm.
1401: EFaultId_ExtAl1
FAULT
NAME
fault hasthe
been
corrected.
MEANING
summing
detailed
instructions.
cancels
alarm
when the
A
shared
(Medusa)
FR
is
summing
specific
description
below
The
system
automatically
1402:
BB
busEFaultId_ExtAl2
reception
error
For details, refer to
Please
check
the
below
Do not
cancel
the alarm.
MEANING
FAULT
NAME
The
BTS
tries
to
correct
a
fault
has
been
corrected.
blocked.
for
detailed
instructions.
the alarm
when the
1403:
EFaultId_ExtAl3
(summing
device)
GSM/EDGE
BSSto
fault-specific
description
Thenot
system
automatically
The
fiber
cable
is below for cancels
2M
external
reference
For
details, refer
Please
check
the
Do
cancel
the alarm.
fault
situation
by
ID
FAULT
NAME
FAULT
ID
fault
has
been
corrected.
1404:
EFaultId_ExtAl4
Operating Documentation.
detailed
instructions.
cancels
the alarm
when the
experiencing
interference;
missing
GSM/EDGE
BSSto
fault-specific
for The
system
automatically
performing
a description
recovery
reset
2019:
Automatic
BTS
Operator
For details, refer
Please
check
the
below
Do not
cancel
the alarm.
INSTRUCTIONS
2019:
FAULT
NAME
1405:
EFaultId_ExtAl5
FAULT
ID
service/device
is
unblocked
data
transmission
is
faulty.
Operating
Documentation.
detailed
instructions.
cancels
the
alarm
when the
to
aaction
unit,
the
RAT
or the for The
EFaultId_Muksu_SsubMm
Certificate
GSM/EDGE
BSSto
fault-specific
description
system
automatically
No
isretrieval
needed.
EFaultId_Muksu_SsubMm
HSDPA
Users
Limitation
For details, refer
Please
check
the
below
Do
not
cancel
the alarm.
1406:
EFaultId_ExtAl6
2016:
by
user.
FAULT
ID
fault
has
been
corrected.
BTS.
Al
unsuccessful
Operating Documentation.
detailed
instructions.
cancels
the alarm
when the
Al
Alarm
GSM/EDGE
BSSto
fault-specific
description
system
automatically
1407:
EFaultId_ExtAl7
EFaultId_Muksu_SMTime
For details, refer
Please
check
the below for The
Do not
cancel
the alarm.
A
physical
connection
1899:
fault
has
been
corrected.
Operating
Documentation.
detailed
instructions.
cancels
the
alarm
when the
1408:
EFaultId_ExtAl8
OffAl
GSM/EDGE
BSSto
fault-specific
for The
system
automatically
failure
between
the
optical
EFaultId_2MExtRefMissAl
For details, refer
Please
checkdescription
the
below
Do not
cancel
the alarm.
INSTRUCTIONS
MEANING
FAULT
ID
MEANING
FAULT
ID
fault
has
been
corrected.
1409:
EFaultId_ExtAl9
Operating Documentation.
detailed
instructions.
cancels
the alarm
when the
interface
and
the
summing
GSM/EDGE
BSSto
fault-specific
description
system
automatically
Check
the
alarm
There
is
a
bus
61510:
NO_CERTIFICATE
For details, refer
Please
check
thehistory
below
Do
not
cancel
the alarm.
There
is
a baseband
baseband
busfor The
4285:
[All
except
VSWR
major
1410:
EFaultId_ExtAl10
MEANING
fault
has
been
corrected.
function
has
MEANING
Operating
Documentation.
detailed
instructions.
cancels
the
alarm
when
and
othermismatched
active
alarms
of
address
in
GSM/EDGE BSS
fault-specific
description
for The
system
automatically
address
mismatched
in the
the
EFaultId_HsdpaUsersLimit
alarm
are
auto
cancelled]
1.
Check
the
availability
of
SBTS
checks
continuously
1411:
EFaultId_ExtAl11
The
master
frame
in
the
occured(possibly
caused
reference
clock
the
fault the
hasalarm
been when the
the
unit.
summing.
There
are
two
MEANING
Operating Documentation. The
detailed
instructions.
cancels
summing.
There
are
two
ationAl
IP
connectivity.
for soon
the received
diagnostic
1412:
EFaultId_ExtAl12
received
baseband
bus
E1
interfaces:
Check
that
As
as
a
signal
that
by
bad
circuit
joints).
monitoring
has
detected
a
corrected.
possible
causes:
A
requested
certificate
fault has
been
corrected.
possible
causes:
codes
for
activated
BFD
1413:
EFaultId_ExtAl13
frame
is
not
in
the
correct
the
interface
type
of
the
conforms
to
the
expected
loss
ofThis
2.048
MHz
signal
1.
Check
that
the does
As soon as the link transits
Note:
alarm
not
could
not
be
retrieved
from
MEANING
2.
Check
whether
there
are sessions
as and
when BFD
1414:
EFaultId_ExtAl14
place,
regarding
the
far-end
interface
is
also
frame
format
isstays
received,
INSTRUCTIONS
received
from
an
external
cables/fibers
are
to upalarm
and
link
up
require
any
(special)
A
configuration
error
(two
the
certificate
authority
1.
Check
the
availability
of
The
condition
forfor
a
A
configuration
error
(two
Not
enough
#data
users
active
alarms
at
the
far
messages
are
received
1415:
EFaultId_ExtAl15
internally
generated
master the
configured
to the
be acorrect
framed
alarm
will
be
Take
the baseband
following
actions
reference
source,
connected
to
more
than
10
seconds,
the
actions.
different
units
(CA).
IP
connectivity.
protect
policy
does
not
different
baseband
units
licenses
is
available
innotor SW
end.
IfEFaultId_ExtAl16
found,
follow
from
the peer.the expiration
Switch
off
the
loopback
registers
1416:
frame
pulse.
Either
the
E1
interface.
IfSync
this an
is
cancelled.
to
clear
the
fault:
connected
to
In
connectors.
alarm
will ifbe
functioning)
-certificate
after
A
requested
2.
Check
whether
there
are LOS
exist
anymore
thethe
latest
functioning)
after
an
Centralized
SW
License
the
instructions
for
handling
The
SBTS
cancels
wait
for
the
timeout
to
of
the
loopback
timer.
1417:
EFaultId_ExtAl17
frame
has
been
set
in
the
the
case,
reconfigure
the
Device
Driver
software
1.
Clean
the
cables
and
As
soon
the
EBER
is not
interface
of
the
System
cancelled.
acknowledgment,
the
fault
could
not
be
renewed
from
active
alarms
at
the
far
IKE
message
is
answered
acknowledgment,
the
fault
Server.
Parameters
those
alarms.
alarm the
autonomously
once
expire
which
opens
the or exceeded
1418:
EFaultId_ExtAl18
wrong
place
(PI
delay),
interfaces
so
that
they
reads
alarm
status
connectors.
anymore,
the
1.
Reset
the
Radio
Module
Module.
2.
Check
that
the
interface
Check
that
the
configured
As
soon
as
a multiframe
returns.
the
certificate
authority
end.
IfEFaultId_ExtAl19
there
are,
follow
by
the
peer.
returns.
BTSSCW/numberOfHSDP
the
BFD
functionality
for
loop
and
cancels
the
1419:
the
data
itself
is
in
the
match
each
other.
directly
from
the
HW
chip.
alarm
is
canceled.
with
the
faulty
optical
at
the
far-end
interface
is
interface
type
matches
the
signal
is detected,
the
(CA).
the
instructions
for
handling
The
fault
is
cancelled
as is
Check
the
intermediate
As
soon
as
no
AIS
signal
ASet1,
3.
Check
if
the
far
end
has
any
BFD
sessions
alarm.
1420:
EFaultId_ExtAl20
wrong
place.
2.
Check
that
theon
interface
by
INSTRUCTIONS
switched
on
and
has
configured
interface
type
of soon
alarm
is cancelled.
Data
corruption
the
bus
those
alarms.
as
the
fault
condition
transmission
network
for
received,
the
alarm
is
Data
corruption
on
the
bus
BTSSCW/numberOfHSDP
BFD
switched
ON.
belonging
to
that
BFD
1.
Check
the
intermediate
As
soon
there
is
no
remote
1421:
EFaultId_ExtAl21
connectors
are
properly
blocking/unblocking
it.
Note!
the
steps
correct
auto-negotiation
the
farPerform
end.
Ifcertificate
this
is
the
The
Device
Driver
software
-transmission
appears
once
when
A
requested
does
not
exist
forreceived
any
alarms
indicating
the
root
-Check
appears
once
when
ASet2,
group
is
available
again.
network
forof canceled.
defect
indication
1422:
EFaultId_ExtAl22
INSTRUCTIONS
connected
to
the
unit.
the
configuration
Device
Driver
software
below
in
the
listed
order
settings.
case,
the
problem
is
reads
the
alarm
status
unsynchronized
data
is
could
not
be
retrieved
as
protect
policy.
cause
and
follow
the
The
Device
Driver
software
unsynchronized
data
is
BTSSCW/numberOfHSDP
alarms
indicating
the
root
thethe
interface,
the
alarm
1423:
EFaultId_ExtAl23
Fault
source
FBB:
the
end.
reads
alarm
status
2.
Iffar
this
does
not
clear
the on
until
the
alarm
disappears.
somewhere
inFSP,
the
directly
from
the
HW chip.
Check
the
configuration
Device
Driver
software
sent
by
the
baseband.
the
number
of
certificates
instructions
for
handling
reads
the
alarm
status
sent
by
the
baseband.
ASet3
are
to
be
reduced
cause
and
follow
the
is
canceled.
1424:
EFaultId_ExtAl24
1.
Replace
the
unit
causing
3.
Check
that
the
cable
Check
whether
IP
address
directly
from
the
HW
chip.
fault,
replace
the
Radio
=
3.
Check
whether
there
are reads
transmission
network.
and
corresponding
alarms
the
alarm
status
received
from
repository
Note: When
IPsec
backup
these
alarms.
directly
from
the
HW
chip.
Check
for(System
IPCP
orModule,
LCP
Device
Driver
software
internally.
instructions
for
handling
1425:
EFaultId_ExtAl25
the
fault
connected
to
the
interface
configurations
match
on
Module
that
is
causing
the
1.
Check
active
at
the
far
on
the alarms
farthe
end.
directly
from
the
HW
chip.
INSTRUCTIONS
server
(RA)
orcabling
certificate
tunnel
feature
is
enabled,
failure
alarms
on
this
reads
the
alarm
status
INSTRUCTIONS
these
alarms.
1.
Check
the
network
For
a
session
that
is
not
set
FBB).
in
question
is
not
damaged
local
and
remote
nodes.
alarm.
(connected
to
Sync
In
end.
If
there
are,
follow
the
Check
whether
the
LCP
The
alarm
is
canceled
if
the
antenna
authority
(CA)
are
more
DPD
alarm
due
to
the
interface.
directlyinfrom
the HW chip.
Check
the
antenna
INSTRUCTIONS
between
both
BFD
peers
locally
AdminDown
MEANING
and
isexpected.
within
the
1.
Check
thethe
network
For
an active
BFD session
interface).
instructions
for
handling
configurations
match
on
the
link
is up
for 100
mapping
to
local
cells
than
primary
Check
all
physical
This
alarm
is again
automatically
mapping
to
the
local
cells
Add
#data
users
licenses
2.
Check
the
transmit
for
physical
link
failures
or
mode,
the SBTS
High
or
low
voltage
on
the
Fault
source
HWPORT:
specifications.
3.
If
the
System
Module
is
between
both
BFD
peers
SBTS
checks
continuously
those
alarms.
near
and
far
end
nodes.
milliseconds.
1.
Check
the negotiated
The
alarm
is cancelled
in
the
commissioning
file.
tunnel
failure
shall
be
connections.
cleared
when
atleast
one
in
the
commissioning
file.
to
Centralized
SW
License
hardware,
a loop
mis-configurations.
monitors
external
alarm
line.
1.
Check
the
cables
the
onlyand
source
of
the
for
physical
link
failures
or continuously
the
diagnostic
codes inthe
theis
2.
Check
ifconnect
the
2.048
MHz
speed
clock
mode
at
once
an
auto-negotiation
INSTRUCTIONS
cleared
when
switch-over
of
the
session
in
the
Multi1.
Check
the
backhaul
The
alarm
will
be
cleared,
if
Server.
cable
and
check
that
no
2.
Check
ifthe
the
amount
of BFD
between
the
Master
4.
Follow
E1BFD
path
in
the received
alarm,
misconfigurations.
orthe
replacing
RF
BFD
packets
received
from
reference
source
is the
working
4.
To
verify
that
the
the
Ethernet
interface
to
process
has
taken
place,
Provide
certificate.
successful
for
all
primary
Link
PPP
bundle
are
up
usage
and
if
other
during
5
consecutive
1-min
alarms
appear
for
this
functionality
in
the
peer
is The
packets
from
The
1.
Check
user
the
backhaul
the
alarm
willthe
be peer
cleared,
System
Module
and
thefault
network
and
check
whether
Module
2.
Check
does
ifspecifies
the
not
BFD
clear
the
BFD
peer.
normally
and
the
2.048
hardware
of
the
interface
determine
the
root
cause
of the
which
does
not
generate
tunnels(that
is,
all
and
running
or
Single-Link
applications
with
the
same
periods
theconfigurable
average
valuea
interface.
switched
on
and
that
the
during
the
text
during
commissioning.
usage
and
if
other
after
at
least
2
observation
Radio
Module/Extension
any
other
alarms
fault,
functionality
replace
in
the
the
System
peer
is
The
system
cancels
the
Check
IPCP
or
LCP
Device
Driver
software
MHz
signal
is
available.
works
correctly,
connect
a
the
alarm.
downshift
event
nor
a
clock
secondary
tunnels
are
PPP
is Ifupthe
and
or
higherModule.
PHB
may
of
thesession
RTT
remains
below
configurations
of
BFD
detection
time.
peer
applications
with
the
same
periods
are
error
free
System
concerning
the
fault
are
on
Module
switched
that
on
is
and
causing
that
the
the
alarm
autonomously
once
failures
belonging
to
this
reads
the
alarm
status
loop
cable
and
check
mode
which
does
not
fit
to
FAULT
1.Check
NAME
for
duplicate
IPv6
The
alarm
is
cleared
once
successfully
established).
running
for
more
than
100
compete
against
this
the
threshold.
FAULT
local
and
remote
peers
sends
again
BFD
packets,
INSTRUCTIONS
or
higher
PHB
may
2.
Replace
SFP
atthe
both
(such
asNAME
Laser
End
ofBFD
Life) again.
alarm.
configurations
the
local
BFD
session
Multi-Link
PPP
interface.
directly
from
the
HW
chip.
3.
Replace
the
alarming
whether
the
alarm
2.
Ifbus
the
Ethernet
interface
synchronous
Ethernet
Antenna
addresses
link
configured
isof
down
in
the
duplicate
address
is
Similarly,
any
DPD
alarm
milliseconds.
TWAMP
session
about
the
BB
transmission
error
FAULT
NAME
match.
alarm is cancelled.
[User
compete
defined]
against
this
ends
of
primary
link.
If the the
and
signal
quality
offailures
each
local
and
remote
peers
again
error-free
Check
for
physical
module.
disappears.
speed
is
100Mbps,
but
configuration.
the
SBTS.
deleted
or
changed
FAULT
NAME
raisedreceives
due to secondary
capacity.
An
increase
in the
the either
HSUPA
Users
Limitation
TWAMP
session
about
fault
is
raised
for
one
individual
link.
If
they
are,
match.
BFD
packets
from
on
the
underlying
physical
1000Mbps
was
expected,
FAULT
2.Change
ID
or
delete
the
to
a
different
address.
BTS
and/or
peer
trust
tunnel failure will beits BFD
priority
of
TWAMP
session
FAULT
IDAn
Alarm
capacity.
increase
in
the
secondary
HWPORT,
follow
the
instructions
for
links.
5.
Check
that
the
then
alarm
is
In
case a clock mode
476:
identified
duplicate
IPv6
anchor
expired
orcaused
due
to by peer.
cleared
or
of the
theof
backhaul
capacity
2017:
priority
TWAMP
session
replace
the
SFPs
for
the
handling
those
alarms.
length/type
of
the
a
link
speed
downshift
mismatch
is causeisof the
EFaultId_Rp3BusError
addresses.
expire
when
switchback
may
the alarm.
EFaultId_Muksu_SRx10b8
FAULT
or
of clear
theIDHWPORT
backhaul
capacity
affected
as well.
cable/fiber
does
not
event.
alarm,
then
thesecondary
alarm is
successful
for
2.
Check
the
last
measured
bAlReplace
4286:
may
clear
the
3.
thealarm.
units
FAULT
NAME
introduce
as is,
well,
MEANING
FAULT
ID excessive
tunnels (that
all when
primary
RTT
values
of this TWAMP cancelled
EFaultId_HsupaUsersLimit

Start IPsec emergency

bypass
making
the from
Stop IP by
traffic
capture
security
gateway
not
WebUI
page.
1.
Check
the availability of
reachable either by
IP
connectivity.
Check
theout
authentication
plugging
the cable or
2.
Check whether
there
are
credential
provided
by the
configuring
wrong
security
Check the IKE
profile
active
alarms
at
the
far
peer
(certificate).
gateway
address.
configuration
of the SBTS
Check
that
the
end. If there
are, follow
and
the
peer
for
proper
configurations
peer
the instructionsfor
forthe
handling
values.
and
SBTS security
thosethe
alarms.
policies for IPsec SA
match.

IPsec emergency bypass

active
stateisiscleared
exited by
The alarm
when
operator
interaction
the IP
traffic
The
alarm
is capturing
cancelled
(parameter
"IPsec
session
is stopped.
when
SBTS
has
switched
The
alarm
isbypass
cancelled
emergency
exit
back
all
secondary
when
the
IKE
SA fortunnels
that
active
mode
or
The alarm
is request")
cancelled
to
primary
peer
isthe
established.
reboot.
when
IKE
SA
for
the
This
is cleared
IPSecalarm
tunnels
due to when
affected
policy
is the
the
IPsec
SA
for
automatic switchback
or
established.
affected
policy is request
manual switchback
established.
from
operator. This applies to
following state transitions
1.
Secondary_Active_Probing
_Primary -->
Primary_Active
2.
Secondary_Active_No_Pro
bing_Primary -->
Primary_Active
Note: The alarm is also
cancelled when the IPsec
backup tunnel feature or
IPsec
feature is disabled or SBTS
is rebooted.

Testing instructions

The transmission link

needs to havethe
an far end
Mis-configure
unidirectional
failure.
as
unframed
E1
interface
Remove the interface
type.
cable.
Disconnect the remote
Power down the remote
peer.
Initiate loopback on the
peer.
interface
the cable or
Connect
avia
faulty
Setup remote
peer with no
management application.
connector.
auto-negotiation
Mis-configure
thecapability.
far-end
Observe
for
the
alarm
interface
type
to
mismatch
Create failures/problems in
which
should
be visible
with
local
configuration.
intermediate
transmission
Setup
a condition
where
after 5 secs and not earlier.
network.
the
far
end
has
a
LOS,
Mis-configure the far end
LOF
or IPCP
AIS alarm
its be
so that
stateon
can't
Change
the configuration
receiving interface.
opened.
on
thedown
far end
that LCP
Bring
theso
Single-Link
state
machine
doesn't
PPP link.the BFD session in
Disable
reach
open all
state.
Bring
down
sessions of
the
BFD
peer.link
Transmission
needs to
Multi-Link LPPP bundle.
have
an
unidirectional
Configure the SBTS with
failure. link capacity than
different
Configure RTT threshold to
the
remote
peer supports.
a
low value.
1.very
Change
the PLR
Configure
priority
oflow
threshold ato
a very
Simulate
LCP
or IPCP
TWAMP traffic to a very
value.
failure
on thenetwork
associated
Configure
IPv6
low
value, aso
packets
2.
Change
thethat
TWAMP
links.
interface
address
in the
are
scheduled
last.
traffic priority to a very low
SBTS which is already in
value, so that TWAMP
use in another IPv6 node
packets are dropped or
[E.g: (S)BTS/router] or of
scheduled last in the
the direct attached
queue.
network.
3. Configure TWAMP

Event type name

Fault Dependent
Fault Dependent
Fault Dependent
Environmental
Fault Dependent
Fault Dependent
Fault Dependent
Communications
Fault Dependent
Fault Dependent
Quality of service
Quality of service
Fault Dependent
Environmental
Fault Dependent
Fault Dependent
Communications
Environmental
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications
Communications

Event type
x0
x0
x0
x3
x0
x0
x0
x1
x0
x0
x4
x4
x0
x3
x0
x0
x1
x3
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1
x1

Start IP traffic capture from

WebUI apage.
Create
failure where at
least
one
primary
IPSec
Change the
authentication
Stop
IPfails
traffic
capture from
tunnel
and
credential
provided
by the
Changepage.
the
IKE profile
WebUI
SBTS
has switched
over to
peer (certificate)
to some
configuration
of
the
SBTS
Change
theIPSec
peer and
the
secondary
tunnel.
invalid
certificate.
and
thesecurity
peer topolicies
differentfor
SBTS
values,
resulting in so
IPsec configurations
negotiation
that they dofailure.
not match.

Communications
Communications
Communications
Communications
Communications
Communications

x1
x1
x1
x1
x1
x1

Probable cause name

Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate

Probable cause
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Clearing
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic

Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate

0
0
0
0
0
0

1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic
1 Automatic

Default severity
N/A
5 Warning
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
4 Minor
2 Critical
4 Minor
3 Major
3 Major
3 Major
4 Minor
2 Critical
2 Critical
2 Critical
3 Major
4 Minor
3 Major
3 Major
3 Major
3 Major
2 Critical
2 Critical
2 Critical
3 Major
3 Major
3 Major
3 Major
3 Major
3 Major
3 Major

Alarm severity informationInforming delay

Critical
10000
Major
Warning
10000
Minor
Critical
10000
Warning
Major
Critical
10000
Minor
Major
Critical
10000
Minor
Major
Critical
10000
Warning
Minor
Major
Critical
10000
Warning
Minor
Major
Critical
10000
Warning
Minor
Major
Critical
10000
Warning
Minor
Major
Critical
10000
Warning
Minor
Major
Critical
10000
Warning
Minor
Major
Minor
0
Warning
Minor
Critical
0
Warning
Minor
0
Major
0
Major
0
Major
0
Minor
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

3 Major
4 Minor
3 Major
3 Major
3 Major
3 Major

0
0
0
0
0
0

Clearing delay
10000
10000
10000
10000
10000
10000
10000
10000
10000
10000
10000
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Time to live
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Change over update

0
0
0
0
0
0

0
0
0
0
0
0

Dependencies with other Internal ID number

108430
108431
108432
108433
108434
108435
108436
108437
108438
108439
109170
108455
108450
108451
108452
108453
108454
108456
108596
108613
108612
109250
108619
108618
108616
108615
108617
108620
108621
108623
108594
108595
108624
108626
108499
108622
108597

Comments
Alarm Event type depends
on underlying
fault.
Alarm
Event type
depends
Alarm
Severityfault.
depends on
on
underlying
Alarm Event type depends
alarm's
impact
the is
The
duration
ofon
reset
on underlying
Alarm
Severityfault.
is defined
SBTS.
described
in thedepends
SBTS on
Alarm
by
the Severity
operator
during
Alarm
Event
type
depends
performance
requirement.
alarm's
impact
on
external
alarmfault.the
on
underlying
Alarm Event
type
depends
SBTS.
Severity
Minor
can
configuration.
Alarm
Severityfault.
depends on
on
underlying
occur
ifEvent
FR not
supporting
Alarm
type
depends
alarm's
impact on
the on
Alarm
Severity
depends
any
cells
is blocked.
on
underlying
fault.
Alarm
Severity
depends on
SBTS.
alarm's
impact on
the on
Alarm Severity
depends
alarm's
impact
on
the
Alarm
Event
type
depends
SBTS.
alarm's impact on the
SBTS.
on
underlying
fault.
Alarm
Event type
depends
SBTS.
Alarm
Severity
depends on
on underlying
Alarm
Severityfault.
depends on
alarm'sSeverity
impact on
the on
Alarm
depends
alarm's impact on
the
SBTS. impact on the
alarm's
SBTS.
Alarm
SBTS.Event type depends
on underlying fault.
Alarm Event type depends
on
underlying
fault.
Alarm
Event type
depends
on underlying fault.
27.04.2015 Nittala: Added
for SBTS16.Nittala: Added
27.04.2015
Feature
Id: RP000361
for
SBTS16.
2015-06-11:
Managed
(Link
Supervision
with
Alarming
object:toPPTT
object updated
include
11.06.2015
Nittala:
Created
BFD)
Feature
Id: RP000357
PPTT
for
IPSec.
Alarming
object:BFDGRP
27.04.2015
Nittala:
Added
(Symmetrical
E1 Interface)
27.04.2015
Nittala:
Added
Feature
ID: RP000356
for
SBTS16.
27.04.2015
Nittala: Added
for
SBTS16.
IPSec
for
BTS.
Alarming
object: PPTT
for
SBTS16.
Alarming
objects:
ETHLK,
27.04.2015
Nittala:
Added
AlarmingId:
object:
IKEP
Feature
RP000357
Alarming
object:
PPTT
PPTT
for
SBTS16.
27.04.2015 Nittala:
Added
(Symmetrical
E1 Interface)
Feature
Id:
RP000357
Feature
Id:
RP000365
Alarming
object:
PPTT )
for SBTS16.
27.04.2015
Nittala:
Added
(Symmetrical
E1 Interface)
ElectricalId:
10/100/1000Feature
RP000357
Alarming
object:
PPTT
for
SBTS16.
27.04.2015
Nittala:
Added
Base-T
Interface)
(Symmetrical
E1 Interface)
Feature
Id:
RP000357
Alarming
object:
PPTT
for
SBTS16.
Feature
Id:
RP000357
27.04.2015
Nittala:
Added
(Symmetrical
E1 Interface)
Feature
Id: RP000357
MO:
P3ML,
P3SL
(Symmetrical
E1
Interface)
for
SBTS16.
27.04.2015
Nittala:
Added
(Symmetrical
E1 Interface)
Feature
Id: RP000176
RP000350
08.06.2015
Nittala:
for SBTS16.(Ethernet
27.04.2015
Nittala:
Added
(MLPPP
termination)
termination)
Modified
meaning field as
MO:SBTS16.
P3SL,P3ML
for
27.04.2015
Nittala: Added
per review
comments.
Feature
Id:
Feature
Id: RP000176
RP000361
for
SBTS16.
MO:
P3LP
27.04.2015
Nittala: Added
(MLPPP
termination)
(Link
Supervision
with
Feature
Id:
Feature
Id: RP000361
RP000176
for
SBTS16.
27.04.2015
Nittala: Added
BFD)
(Link
Supervision
with
(MLPPP
termination)
Feature
Id:
RP000365
for
SBTS16.
Alarming
object:
BFD
20.04.2015
Nittala:
BFD)
(Electrical
10/100/1000Feature
Id:
RP000360
Created
new
alarm
for (IP
Alarming
object:
BFD
Feature
Id:
RP000176
Base-T
Interface)
Transport
Network
SBTS16.
(MLPPP
Alarming termination)
object:
ETHLK
18.08.2015
Nittala:
Measurements)
Feature
Id:RP000360 (IP
MO:
P3ML
Modified
alarm
text
as per
Alarming
object:
TWAMP
Transport Network
review comments.
Measurements)
27.04.2015 Nittala: Added
Alarming object: TWAMP
for SBTS16.
Feature Id: RP000589
(IPv4/IPv6 Transport Stack)
Alarming object: IPIF

109255
108599
109251
109254
109253
109252

11062015, Vipul : Added

new
alarm for
IPsecAdded
27.04.2015
Nittala:
emergency
bypass.
for SBTS16.Nittala: Added
11.06.2015
Feature Id:
Id: RP000439
Feature
for
feature- RP000465
RP000600
11.06.2015
Nittala: Bypass)
Added
(IPsec and
Emergency
(Local
Remote
IP
IPSec
Backup
Tunnel.
for
feature
RP000356.
Alarming
object:
IPSECC
11062015,
Vipul: Added
Traffic
Capturing)
Feature
Id:
RP000600
Feature
Id: for
RP000356
new
alarm
IPSEC.
Alarming
object
::IPNO
11062015,
Vipul
Added
(Backupfor
IPsec
Tunnel)
(IPSec
BTS)
Feature
Id:
RP000356
new
alarm
for
IPSEC
Alarming object
object:: IKEP
Alarming
(IPSec
for
Feature
Id:BTS)
RP000356
IKEPROTGRP
Alarming
(IPSec forobject
BTS) : IKEP
Alarming object : SECPOL

Description for change history

2015-09-01 Barbara
Montiel-W.:instruction
2015-09-01
Barbara
update.
Montiel-W.:instruction
2015-09-01 Barbara
update.
Montiel-W.:instruction
2015-09-01
Barbara
update.
Montiel-W.:instruction
2015-09-01 Barbara
update.
Montiel-W.:instruction
2015-09-01 Barbara
update.
Montiel-W.:instruction
2015-09-01 Barbara
update.
Montiel-W.:instruction
2015-09-01 Barbara
update.
Montiel-W.:instruction
2015-09-01 Barbara
update.
Montiel-W.:instruction
2015-09-01 Barbara
update.
Montiel-W.:instruction
2015-09-01
Barbara
update.
Montiel-W.:instruction
[17-04-2015; Barbara
update.
Walczak; Created
due to
[17-04-2015;
Barbara
RP000920_1RP_X18]
Walczak;
Created
due to
[17-04-2015; Barbara
RP000920_1RP_X18]
Walczak;
Created
due to
[17-04-2015;
Barbara
RP000920_1RP_X18]
Walczak;
Created
due to
[17-04-2015; Barbara
RP000920_1RP_X18]
Walczak;
Created
due to
[17-04-2015;
Barbara
RP000920_1RP_X18]
Walczak;
Created
due to
[17-04-2015; Barbara
RP000920_1RP_X18]
Walczak; Created due to
RP000920_1RP_X18]

[28.08.2015 Nittala]
Modified Effect and
instructions as per review
comments.