Document Type: Alarm
Generated: 2015-09-02 16:54
Used search parameters: Product=Base Station, Product release=SBTS16.2
Alarm number Name
7100 HARDWARE PROBLEM 7101 RESET NOTIFICATION 7102 7103 7104 7105 7106 7107 7108 7109 7110 7208 LOCAL BLOCK 7600 BCF FAULTY 7602 BCF NOTIFICATION 7606 TRX FAULTY 7607 7625 7995
61022 BFD group $bfdGrpId down
61028 61029
61030 Dead Peer Detected
61040 61104 61150 61151 61152 61250 IPCP Failure 61251 61252 PPP Interface down 61605 61606 61607 61610 61611 61622 MLPPP link Degrade 61632 RESOURCE BLOCKED BY USER EXTERNAL ALARM NOTIFICATION CELL SERVICE PROBLEM
RAT BASE STATION PROBLEM
SINGLE RAN BASE STATION PROBLEM BASE STATION CONNECTIVITY PROBLEM BASE STATION SYNCHRONIZATION PROBLEM BASE STATION SECURITY PROBLEM BASE STATION LICENSE LIMITATION TRX OPERATION DEGRADED PS U-PLANE CONNECTION FAILURE MAINS BREAKDOWN WITH BATTERY BACKUP LOF on unit $U, interface $IF
LOS on unit $U, interface $IF
Interface under test on unit $U, interface $IF for $T minutes
EBER on unit $U, interface $IF
LOMF on unit $U, interface $IF
AIS on unit $U, interface $IF
RDI on unit $U, interface $IF LCP Failure on Interface $IF BFD $session down, ingress, $sourceIP to $destinationIP BFD $session down, egress, $sourceIP to $destinationIP Auto-negotiation mismatch, on unit $U, Ethernet interface $IF
TWAMP RTT threshold crossed
TWAMP PLR threshold crossed
Dup Addr detected $duplicateIpv6Address
61639 61641
61643 IPsec tunnel switchover
61644 IKE authentication failure
61645 IKE SA mismatch
61646 IPSec SA mismatch
IPsec emergency bypass active
IP Traffic Capturing Ongoing [port $port,] [mac $m]
Product=Base 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
Dino document identifier Meaning of the alarm Effect of the alarm A hardware fault (or faults)
has occurred in the base station. This fault may have an impact on the existing cells across RATs. Check the reason for the fault from the supplementary text field of the alarm.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. The device is being reset to
recover from a fault (or faults).
The effect of the alarm on the Network Element depends
on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. The service/device has
been blocked by the user. The service/device is blocked by the user. It is not possible to establish phone calls through the blocked cell, module or SBTS.
This is an external user-defined alarm. The alarm including the alarm text is defined by the user during external alarm
configuration
The effect of the alarm depends on the purpose that was configured for the user-defined alarm input in the SBTS. A fault (or faults) has
occurred in a unit (or units) that belong to the sector indicated in the alarm. Check the reason for the fault from the
supplementary text field of the alarm.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. A fault (or faults) has
occurred in the RAT base station. Check the reason for the fault from the supplementary text field of the alarm.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. A fault (or faults) has
occurred in the Single RAN base station. Check the reason for the fault from the supplementary text field of the alarm.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. A fault (or faults) has
occurred in the base station
connectivity/interface. Check the reason for the fault from the
supplementary text field of the alarm.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. A fault (or faults) has
occurred in the base station synchronization. Check the reason for the fault from the
supplementary text field of the alarm.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. A fault (or faults) has
occurred in the base station security. Check the reason for the fault from the supplementary text field of the alarm.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. Capacity limitation (or
limitations) has occurred in the base station due to a missing license. Check the reason for the fault from the supplementary text field of the alarm.
The effect of the fault on the network element depends
on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. The service/device has
been blocked by the user. For details, refer to GSM/EDGE BSS
Operating Documentation.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. A fault (or faults) has
occurred in the BCF. For details, refer to GSM/EDGE BSS
Operating Documentation.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. Fault has occurred that
disallows OSC/DFCA feature operation. For details, refer to GSM/EDGE BSS
Operating Documentation.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. A fault (or faults) has
occurred in the TRX. For details, refer to GSM/EDGE BSS
Operating Documentation.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. Fault has occurred that
disallows OSC/DFCA feature operation. For details, refer to GSM/EDGE BSS
Operating Documentation.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. A fault (or faults) has
occurred in the (E)GPRS protocol layer.
For details, refer to GSM/EDGE BSS
Operating Documentation.
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. Main power is lost. Battery
backup is switched ON. For details refer to GSM Alarms Documentation: Base Station Alarms (7000-7999); DN9813099
The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault
descriptions in SBTS System Libraries. The alarm is raised if the
service under monitoring is not available when e.g. all network paths are not available. This implies that all individual BFD sessions of the respective group are erroneous.
The communication link between the local SBTS and the BFD peer is defective. No
communication is possible. This Loss of frame alarm is
raised when the local receiver is unable to detect the frame alignment word of the E1 signal. All other transmission alarms related to this signal are
suppressed.
Probable cause: The interface at the far end is not configured to be a framed E1 interface.
Possible impact on the connections over this interface:
- no calls are possible. - loss of remote
management access to other network elements. - loss of synchronization if the interface is used as synchronization source. This alarm is raised when
either no or an incompatible signal is received on the interface referenced in the alarm text.
With an Ethernet interface the physical Ethernet link is detected to be down. All other transmission alarms related to this signal are suppressed.
Probable causes for Ethernet interfaces: - a cable/fiber is cut or there is no cable/fiber connected to the interface - the electrical/optical signal is excessively attenuated
- the port at the connected far end node is switched off - the advertized technology capabilities with auto-negotiation of both devices at the Ethernet link do not match
- the Ethernet technology at both devices at the Ethernet link is forced manual and not compatible - the remote peer of an Ethernet link is not auto-negotiation capable or has auto-negotiation function disabled by configuration Probable causes for PDH interfaces:
- a cable is cut or there is no cable connected to the interface
- the electrical signal is excessively attenuated - the port at the connected far end node is switched off - transmit and receive cables are mixed up
No data or clock
information is exchanged via this interface. Possible impact on the connections over this interface:
- voice calls or data connections are aborted and cannot be established anymore
- remote management connectivity is lost and cannot be established anymore
- loss of synchronization if the interface is used as a synchronization source - Depending on use of the Ethernet interface the above described impact can occur for the local SBTS and/or other (S)BTS elements if they are chained via the Ethernet interface.
A dead peer was detected in one of the IPsec associations of the SBTS. There is no response to the requests sent to the peer, either during the IKE SA setup, the IPsec SA setup or during DPD. Note: When IPsec backup tunnel feature is enabled, this alarm is not raised due to failures when trying to setup primary IPsec tunnel in
"Secondary_Active_Probin g_Primary" state.
Possible effects: - no calls are possible. - loss of remote
management access to other network elements. - IKE SAs and IPsec SAs cannot be established or re-keyed.
This alarm is raised if a loopback has been configured by a
management application on the interface mentioned in the alarm text.
The interface cannot be used for transmission. It can be used for
connectivity checks only. This alarm is raised when
the measured bit error rate exceeds the threshold value of BER-3 (10E-3). Probable causes:
- the signal level is too low (connectors or cables are dirty, electrical connectors or cables are corroded) - the specified maximum length of the cable is exceeded
- the connector is not properly connected to the unit
- the receiver or the far end transmitter has failed - the accumulated BER of the end to end E1 path is too high.
Possible impact:
- slow management access to the SBTS and other network elements in the network
- poor voice quality and data performance This loss of multiframe
alarm is raised if the interface referenced in the alarm text has lost the multiframe alignment. Probable cause: The interface type has not been configured to meet the framing of the interface at the far end. For E1 interfaces, the
configuration of the far-end node should be E1
Multiframe.
The performance management data collected on this interface becomes invalid.
This alarm is raised when an alarm indication signal is received. This signal is generated by an
intermediate PDH device in the forward direction because it detects a problem in its received signal.
AIS defect is detected when the incoming signal has two or less zeros in each of two consecutive double frame periods (512 bits) according [G.775] chapters 5.2 and I.2. All other transmission alarms related to this signal are suppressed.
Probable cause: There is a transmission problem somewhere in the
intermediate network along the E1 path and AIS is sent instead of user traffic.
Possible impact on the connections over the interface in question: - no calls are possible - loss of remote
management access to other network elements in the RAN
This alarm is raised when a remote defect indication is received. It is sent by the intermediate or the far end equipment because it detects a serious fault in the received signal. Probable cause: The far end has a LOS, LOF or AIS alarm on its receiving interface.
Possible impact on the connections over this interface:
- no calls are possible - loss of remote
management access to other network elements in the RAN
The alarm is raised if the IPCP state machine is in the Closed or Initial state and cannot reach the Opened state within 100 milliseconds.
Possible impact on the connections over this interface:
- the PPP/ML-PPP interface is not available. - loss of remote
management access. The alarm is raised if the
LCP state machine on the interface is in the Closed or Initial state and cannot reach the Opened state within 100 milliseconds.
Possible impact on the connections over this interface:
- the PPP/ML-PPP interface is not available. - loss of remote
management access to other network elements in the RAN.
This alarm is raised if the PPP interface is not operational either when all the links in the bundle of Multi-Link PPP are not available or Single-Link PPP link is not available.
Possible impact on the connections over this interface:
- the interface is not available.
- loss of remote management access. The alarm is raised if the
BFD state for the session is not AdminDown and nevertheless no BFD packet is received at the local end during the detection time.
The alarm is raised if the BFD session is in activated state.
The communication link between the local and the remote peer is defective or the peer is defective. Transport service may not be available and calls may be dropped.
The alarm is raised if the BFD state of the session is not AdminDown and the BFD packet from the far end contains the diagnostic code = 'Control Detection Time Expired' and no BFD down Ingress alarm is present.
The alarm is raised only if BFD session is in activated state.
The communication link between the SBTS and the BFD peer is
defective.Transport service may not be available and calls may be dropped. This alarm indicates that
there is a mismatch between SBTS expected auto-negotiation result and actual auto-negotiation result.
An Ethernet link was established but during link establishment a link speed downshift event took place. A link speed downshift takes place when auto-negotiation successfully negotiates a certain technology but the link cannot be established with this technology. It is tried then to establish the link with the next lower speed technology.
An Ethernet link was established with 1000Base-T technology, but the negotiated clock mode does not fit to the expected clock mode of synchronous Ethernet.
The expected clock mode of synchronous Ethernet is slave in case an Ethernet interface is entered as sync source to the SBTS
synchronization priority list. Only applicable to
1000Base-T, since only with this Ethernet technology both link partners have to negotiate the clock mode.
Probable causes: -Link speed downshift: a cable is of not sufficient quality to support e.g. Gigabit Ethernet
technology, but sufficient to support Fast Ethernet -Link speed downshift: a cable has just two wire pairs connected, which is sufficient for Fast Ethernet, but not for Gigabit
Ethernet.
-Clock mode mismatch: Link partner has advertised itself that it wants to operate in slave clock mode resulting in negotiated clock mode "master" at the local Ethernet interface (or vice versa).
The Ethernet Link got established with an unexpected clock mode or technology.
Possible impact on the connections over this interface:
- Increased packet delay variation and increased average delay for all voice/packet and management connection - Increase of packet loss due to congestion. - Loss of
synchronization/Timing source lost with Timing over Packet (IEEE1588v2) due to increased packet delay variation.
- Loss of
synchronization/Timing source lost with Synchronous Ethernet. The RTT threshold alarm is
raised in case the average value of the RTT for this TWAMP session from the last 1-min period equals or exceeds the configured threshold.
This alarm is an indication that the backhaul capacity for traffic with the same profile as this TWAMP session (DSCP value, packet size) may be too small, because the measurement packets are scheduled later than before.
The alarm is raised if the packet loss ratio equals or exceeds the configured threshold value during the current observation interval of 15 minutes.
This alarm is an indication that the backhaul capacity for traffic with same profile as this TWAMP session (DSCP value, packet size), may be much too small, because some of the measurement packets seem to have been thrown away.
The TWAMP measurement packets are lost because of degraded traffic
throughput. This alarm is raised if at
least one of the sessions in Multi-Link PPP bundle has gone down.
Multi-Link PPP operates with reduced capacity. Possible impact on the connections over this interface:
- the interface supports fewer connections. - loss of remote management access. During the IP address
configuration the SBTS tests the direct attached network whether, other already configured node, on the network uses already same IPv6
addresses on their network IP interfaces. The DAD (Duplicate address detection) detects those duplicated IPv6 addresses and prohibits the operation of this IPv6 address in the SBTS. The Alarm contains the corresponding IPv6 address and the interface on which the address was configured. For each DAD event a separate reporting shall be indicated.
The remote peer to come online with the same IP address on the same subnet as local peer would just disable their network interface and give an error until the situation is resolved by the administrator.
This allows the local peer to continue functioning without disruption, but completely breaks IP base communications for the connected network.
SBTS has entered IPsec emergency bypass active state where configured IPsec policies are ignored and all traffic is sent unprotected.
All configured IPsec policies are ignored and all the SBTS traffic is sent unprotected.
The alarm is activated when the IP traffic capturing session is started.
The SBTS is currently capturing IP traffic towards a local port or into a file on the SBTS.
If the traffic capturing is happening towards a local port, the port and
destination MAC address needs to be provided. Port values can be LMP or < HW MODULE NAME >-<PORT ID>.
Example: LMP or FSM-EIF1, FSM-EIF2 or FTIF-EIF1
The resulting packet capture files can used for Expert analysis to identify network problems and to help determine the best course of action.
This alarm will be triggered when at least one primary IPsec tunnel fails and SBTS has switched over to secondary IPsec tunnel. As a result of failure in at least one primary IPsec tunnel, SBTS has
automatically switched over to secondary IPsec tunnel terminating on secondary security gateway.
SBTS traffic has switched over from the primary IPsec tunnel to secondary (backup) IPsec tunnel terminating on secondary security gateway.
The alarm is raised when the IKE authentication credentials provided by the peer
is not valid.
The IKE SA cannot be established.
This alarm is raised when the peer and the SBTS configuration for IKE profile do not match.
IKE SA cannot be established and
subsequently no IPsec SAs can be established.
This alarm indicates that the peer and the SBTS security policies for IPsec do not match.
The related IPsec SA can't be established and used.
Version Document state Identifying application add
2.1u PUBLISHED
2.1u PUBLISHED
2.1u PUBLISHED
2.1u PUBLISHED 1. EAC line input ID
2.1u PUBLISHED 2.1u PUBLISHED 2.1u PUBLISHED 2.1u PUBLISHED 2.1u PUBLISHED 2.1u PUBLISHED 2.1u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.1u PUBLISHED 2.1u PUBLISHED 2.1u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED
2.0u PUBLISHED TWAMP
2.0u PUBLISHED
2.1u PUBLISHED
2.1u PUBLISHED
1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 3. Destination IP address 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path(URI) of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP. 1. HW Inventory Id (RDN) and Serial Number of the impacted hardware unit 2. Path of the impacted hardware unit, when the impacted unit is FSM, FT, FSP, FBB, FR, FAN, AntennaLine, MHA, RET, FYG, or SFP.
For details, refer to GSM/EDGE BSS
Operating Documentation. For details, refer to GSM/EDGE BSS
Operating Documentation. For details, refer to GSM/EDGE BSS
Operating Documentation. For details, refer to GSM/EDGE BSS
Operating Documentation. For details, refer to GSM/EDGE BSS
Operating Documentation. For details, refer to GSM/EDGE BSS
Operating Documentation. For details, refer to GSM/EDGE BSS
2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED 2.0u PUBLISHED