TNMS Alarms
Equipment Alarms
1. ACTPL
Active Loop
Alarm Object: Transponder card Client interface
Warning
There is an active loopback on a Transponder card Client interface.
2. CCFAIL
Card Communication Failure
Alarm Object: Card Slot
Major
If a Controller card cannot communicate with one (or more) of the cards that it manages, the CCFAIL alarm
will be raised. Since the type of card is therefore unknown to the Controller because of the lack of communication,
the CCFAIL alarm is raised against the shelf slot(s) that cannot communicate.
3. CFF
Compact Flash Failure
Alarm Object: CCEP and CCMP cards
Major
CCEP and CCMP cards contain a removable Compact Flash memory module. The CFF alarm will be raised if
the card cannot write data to its Compact Flash.
4. CMISM
Card Mismatch
Alarm Object: Card Slot
Major
The NE Configuration File (NCF) specifies the card type to be installed in each slot. If a slot contains a card
different from that specified by the NCF, a CMISM alarm will be raised.
5. CMISS
Card Missing
Alarm Object: Card Slot
Major
The NE Configuration File (NCF) specifies the card type to be installed in each slot. If no card is installed in a
slot that is supposed to contain a card, a CMISS alarm will be raised.
6. CP
Card Problem
Alarm Object: Card (active type cards only; the CP alarm is not raised by Filter or DCM cards).
Major
The CP alarm is raised due to a fault condition on the indicated card.
7. FAN_MAJOR
Fan Major Problem
Alarm Object: Shelf
Critical
A shelf will raise the FAN_MAJOR alarm as follows:
1) Shelf types that can hold only a single Fan Unit (CFS-1 or CFS-2 type Fan Units): the FAN_MAJOR
alarm will be raised for the following reasons:
– Two or more individual fans inside the Fan Unit are faulty. Note: all working fans in the Fan Unit will
go to high speed when a FAN_MAJOR alarm is active.
– Or, the Fan Unit’s presence is not detected by the shelf. Either the Fan Unit has been unplugged from
the shelf, or there is some problem with its connector plug.
2) Shelf types that can hold multiple Fan Units (CFS-3 or CFS-4 type Fan Units): the FAN_MAJOR alarm
will be raised for the following reasons:
– Two or more Fan Units simultaneously raise a CP alarm. Note: all working Fan Units in the shelf will
go to high speed when a FAN_MAJOR alarm is active.
– Two or more fan slots simultaneously raise a CMISS alarm. In other words, two or more Fan Units are
detected to be missing from the shelf. Either the Fan Units have been unplugged from the shelf, or there is some
problem with their connector plugs.
8. FAN_MINOR
Fan Minor Problem
Alarm Object: SRS-1 Shelf
Critical
An SRS-1 shelf will raise the FAN_MINOR alarm if one individual fan inside the Fan Unit is faulty. Note: all
working fans in the Fan Unit will go to high speed when a FAN_MINOR alarm is active.
9. FMISM
Frequency Mismatch
Alarm Object: Transponder card Client port (if configured as WDM client) and Transponder card Line port.
Major
The FMISM alarm will be raised in there is an anomaly with the transponder card’s transmit frequency on the
indicated port.
10. ISLP
Interstage Loss Alarm
Alarm Object: Amplifier card interstage input port. (All amplifier card types execpt LASBC-1.
Major
The ISLP alarm will be raised if the indicated amplifier card detects that the insertion loss through its external
"interstage" device(s) is too high.
11. LSBFAIL
Laser Safety Bus Failure
Alarm Object: Shelf
Critical
The LSBFAIL alarm will be raised if either of the following problems are detected with the Laser Safety Bus
(also known as the APSD bus):
1) A shelf is configured to use the Laser Safety Bus, but the required cables are not connected.
2) A shelf is not configured to use the Laser Safety Bus, but cables are connected.
12. LSBWRONG
Wrong LSB Cabling
Alarm Object: Shelf
Critical
The LSBWRONG alarm will be raised if the indicated shelf detects an unallowed laser safety bus (LSB)
address on one of the member cards of the LSB ring. This is most often caused by connecting the APSD IN/APSD
OUT cables incorrectly (i.e., not connected in agreement with the TransNet Cabling Plan Report).
13. MMISM
Module Mismatch
Alarm Object: Transponder Pluggable Client Port
Major
The MMISM alarm be raised if the pluggable module actually installed in a transponder Line or Client port
does not match that port’s user-configured “Required WDM Grid Type” value (on the port’s Traffic Configuration
window). For fixed-mounted, non-tunable MSA modules, if the "Required WDM Grid Type" is set to “CWDM”, but
the MSA module has a frequency other than a CWDM wavelength, the MMISM alarm will be raised. Behavior note:
in this case, invalid values will be shown for "Maximum Wavelength" and "Minimum Wavelength" on this card’s
'Line Traffic Configuration' window.
14. MMISS
Module Missing
Alarm Object: Transponder Pluggable Port
Major
The MMISS alarm will be raised if any required SFP or XFP module is not installed on the indicated
transponder port.
15. MNOTCT
Module Not Certified
Alarm Object: Transponder Pluggable Port
Minor
The MNOTCT alarm will be raised if a non-Nokia Siemens Networks SFP or XFP module is installed in the
indicated transponder port. Refer to the Product Description document (PD) for listings of SFPs and XFPs that are
compatible with each type of hiT 7300 transponder card.
16. MP
Module Problem
Alarm Object: Transponder Pluggable Port
Major
The MP alarm indicates a failure of the indicated port’s SFP or XFP module.
17. NLD
No Light Decected
Alarm Object:
- MCP card input port.
- F09MDR96 card AUX-IN port
Minor
The NLD alarm will be raised if no light is detected at the indicated port (MCP card input port or F09MRD96
AUX-IN port).
18. OBFF
Onboard Flash Failure
Alarm Object: CCEP and CCMP cards
Warning
The CCEP and CCMP cards both contain an onboard flash memory. A copy of the MIB contents is
periodically written to the onboard flash. When the onboard flash reaches the end of its lifetime, no further backup
copies can be written to it. Therefore, the OBFF alarm serves as a warning that the onboard flash has reached the end
of its lifetime. The entire card (CCEP or CCMP) card must then be replaced.
19. OBRF
Optical Booster Stage Receive Failure
Alarm Object: Amplifier card interstage input port. (All types of amplifier cards except LASBC-1 feature
interstage access).
Critical
If an amplifier card detects a loss of signal condition at the input to its booster stage, the OBRF alarm will be
raised.
20. OBTF
Booster Stage Transmit Fail
Alarm Object: Amplifier cards
Major
The OBTF alarm is raised if the gain of the amplifier card’s booster stage is too low, or if there is a back
reflection condition at the card’s transmit port.
21. OPRF
Optical Preamplifier Stage Receive Failure
Alarm Object: LAxB and LIFB amplifier cards
Major
This alarm is raised if there is a loss of signal detected at the input of Amplifier Stage I of the card raising the
alarm.
22. OPTF
Preamplifier Stage Transmit Fail
Alarm Object: Amplifier card interstage output port. (All types of amplifier cards except LASBC-1 feature
interstage access).
Major
The OPTF alarm is raised if the amplifier card’s pre-amplifier stage cannot achieve the required power gain,
or if there is a back reflection condition at the card’s interstage output (transmit) port.
23. OSCTD
OSC Laser Transmit Degrade
Alarm Object: Booster and In-line amplifier cards (i.e., those amplifier types that transmit the Optical
Supervisory Channel).
Major
The OSCTD alarm is raised if the indicated amplifier card detects a fault with its Optical Supervisory Channel
transmit laser for more than 900 consecutive seconds. The alarm is based on laser modulation current, bias current,
and monitor current. The exact alarm trigger threshold of each parameter varies slightly according to the specific type
of amplifier card.
24. OSCTF
OSC Laser Transmit Fail
Alarm Object: Booster and In-line amplifier cards (i.e., those amplifier types that transmit the Optical
Supervisory Channel).
Critical
The OSCTF alarm is raised if the indicated amplifier card cannot transmit the Optical Supervisory Channel.
25. PF
Pump Failure
Alarm Object: Transmit port and Bidirectional Line port of 40G and 100G cards.
Major
The PF alarm indicates a failed condition with the pump laser on the card’s on-board amplifier module. The
pump laser is shut down as a result of this alarm. Among the conditions that can trigger the PF alarm are:
1) Pump laser current is far above its maximum upper limit.
2) Pump laser temperature is too high or too low.
26. POOR
Power Out Of Range
Alarm Object:
- LAMIC-1, LAMPC-1, and LASBC-1 cards.
- O02CSP-1 and O02CSP-2 cards (for convenience, both are referred to as “O02CSP-x” below).
Major
The POOR alarm can be caused by:
1) If raised by an amplifier card: Release 4.2 of hiT 7300 (which supports 80-channel operation) re-uses
amplifier card hardware from earlier releases which was designed for a maximum channel count of 40. The fixed
range of power measurement circuitry at various stages of the amplifier cards is not sufficient for 80 channels. A
POOR alarm signifies that the monitor circuitry is near its upper or lower limit and that the card may shift its
measurement range. If the card is in running state, this range shift will cause a traffic hit of approximately 1 second
2) If raised by O02CSP-x card: there is an incorrect equipment configuration resulting in a laser safety.
27. PS1
Power Supply 1 Problem
Alarm Object: Shelf
Major
The PS1 alarm will be raised if the shelf detects a failure of its UBAT1 power feed.
28. PS2
Power Supply 2 Problem
Alarm Object: Shelf
Major
The PS2 alarm will be raised if the shelf detects a failure of its UBAT2 power feed.
29. PS3
Power Supply 3 Problem
Alarm Object: Shelf
Major
The PS3 alarm will be raised if the shelf detects a failure of its UBAT3 power feed.
30. PS4
Power Supply 4 Problem
Alarm Object: Shelf
Major
The PS4 alarm will be raised if the shelf detects a failure of its UBAT4 power feed.
31. SLH
Span Loss High
Alarm Object: Line In port of amplifier cards
Major
The total attenuation of the fiber span leading up to each inline amplifier and pre-amplifier is automatically
calculated by the system on a periodic basis. The SLH alarm signifies that the span attenuation is too high. If a span’s
attenuation increases above its defined End of Life (EOL)* value by 3 dB or more (6 dB or more if Raman card is
active), the SLH alarm will be raised.
NOTE: The EOL attenuation value for each span is defined in the NE Configuration File.
32. SLL
Span Loss Low
Alarm Object: Line In port of amplifier cards
Major
The total attenuation of the fiber span leading up to each inline amplifier and pre-amplifier is automatically
calculated by the system on a periodic basis. The SLL alarm signifies that the attenuation is too low. The SLL alarm
will be raised under the following conditions:
1) For spans without Raman Pump cards:
- If the End of Life (EOL)* span attenuation is defined to be any value less than 12 dB, then the SLL
alarm will be raised if the span’s attenuation decreases to 2 dB or less.
- If the EOL span attenuation is defined to be greater or equal to 12 dB, but less than 18 dB, then the
SLL alarm will be raised if the span’s attenuation decreases below its EOL value by 6 dB or more.
- If the EOL span attenuation is defined to be greater or equal to 18 dB, then the SLL alarm will be
raised if the span’s attenuation decreases below its EOL value by 10 dB or more.
2) For spans with Raman Pump cards:
- The SLL alarm will be raised if the span’s attenuation decreases below its EOL value by 15 dB or
more.
NOTE: The EOL attenuation value for each span is defined in the NE Configuration File.
33. SLSBM
Slot LSB Mismatch
Alarm Object: The SLSBM alarm can be raised by the following card types:
- Amplifier cards (all types)
- PRC-1 Raman Pump card
- PL-1 Pump Card
- Demultiplexer F40-1 cards
- F16SB-1 Filter card
Major
A card will raise the SLSBM alarm if it receives a laser safety bus (LSB) address that is not permitted for its
card type or slot position in the shelf.
34. SRMISS
Shelf Missing
Alarm Object: Shelf
Major
The SRMISS alarm will be raised if:
1) A shelf specified by the NE Configuration File (NCF) or manual configuration (for SON), is not installed.
2) The "missing" shelf is actually installed, but the NE Controller card cannot communicate with it.
35. SWP
Switch Problem
Alarm Object : MCP card
Major
The MCP card contains an on-board Optical Spectrum Analyzer (OSA). So, in order to monitor four input
ports, the card must switch to each port in sequence. The SWP alarm indicates a problem with this switch. The
operational state of the MCP card is disabled when the SWP alarm is active.
36. TempM
Temperature Problem Major
Alarm Object:
- F40-1/S and F40-1/O cards
- F08MR-1 card
- F48MDP-1/S and F48MDP-1/O cards
Major
The TempM alarm will be raised if a temperature anomaly exists on the indicated card (temperature too high
or too low). The operational state of the card is disabled when this alarm is active.
37. TempP
Temperature Problem
Alarm Object: PL-1, PRC-1, and PRC-2 cards
Critical
The TempP alarm will be raised if a temperature anomaly is detcted on the indicated card. The card’s laser will
be switched off as a result of the TempP alarm.
38. Temp1P
Temperature Problem 1
Alarm Object: The TempP1 alarm can be raised by all sub-types of LAL, LAV, LAM, LAS, and LAB
amplifier cards.
Critical
The TempP1 alarm will be raised if the temperature of Pump 1 on the indicated card is too high. Note: this
alarm causes the card to shut down its Pump1 amplifier stage.
39. Temp2P
Temperature Problem 2
Alarm Object: All sub-types of LAL, LAV, and LAB amplifier cards.
Critical
The TempP2 alarm will be raised if the temperature of Pump 2 on the indicated card is too high. Note: this
alarm causes the card to shut down its Pump2 amplifier stage.
Communication Alarms
40. BDI
Backward Defect Indication
Alarm Object:
- Transponder Line ports (OTUk Sink)
- Transponder Line ports (ODUk Sink)
- Transponder Client ports (OTUk Sink)
- Transponder Client ports (ODUk Sink)
- Transponder TCM Layers (ODUk Sink)
Minor
BDI signals are maintenance signals placed on the line. BDI is a signal sent in the opposite direction to the
direction that is experiencing a fiber cut or other problem.
41. CHM
Channel Mismatch
Alarm Object: Link Control: Optical Channel Layer.
Minor
The CHM alarm indicates that there is a mismatch in a channel status detected by the MCP card and the
Optical Supervisory Channel. Either the channel is provisioned as used, but is not actually present, or the channel is
provisioned as unused, but is detected as being present.
42. DEG
Degraded Signal
Alarm Object:
- Transponder Line ports (OTUk Sink)
- Transponder Line ports (ODUk Sink)
- Transponder Client ports (OTUk Sink)
- Transponder Client ports (ODUk Sink)
- Transponder TCM Layers (ODUk Sink)
Minor
The DEG alarm is raised if the Bit Error Rate (after Forward Error Correction) of the received optical signal
is worse than a user-specified threshold.
43. DEG-O
Degraded Signal ( OSC )
Alarm Object: In-line amplifier and Pre-amplifier OTS Sink
Minor
An amplifier card will raise the DEG-O alarm if the Bit Error rate (BER) of the incoming Optical Supervisory
Channel is 1 x 10E-6 or worse.
44. EOCI
External Open Connection Indication
Alarm Object:
- Transponder SDH/SONET Client ports (ODUk Sink)
- Transponder Ethernet Client ports (10GE Sink)
- Transponder Ethernet Client ports (ODU1/ETC3 Sink)
- Transponder Fibre Channel Client ports (ODU1P/FC-2 Sink)
Minor
EOCI (External Open Connection Indication) is a special maintenance signal which indicates an upstream
fault (i.e., LOS) in the physical layer (ETYm, OSn, or FC-0-n) at the head end.
45. FDI
Forward Defect Indication – Local Fault
Alarm Object: The FDI alarm can be raised by transponder and muxponder cards.
Minor
FDI signals are maintenance signals placed on the line. FDI is a signal sent downstream in the same direction
that is experiencing a fiber cut or other problem. Its main purpose is to suppress unnecessary alarms downstream.
46. ITIM
Internal Trace Identifier Mismatch
Alarm Object: Amplifier card OTS Layer Sink
Minor
To verify correct cabling between line amplifier cards, TransNet creates an “expected” and a “transmitted” 2-
byte number for every line amplifier card. Each transmitted number is unique. Booster amplifiers send these trace
bytes via the OSC to the next far end NE. The far-end preamplifier reads the trace bytes. If the “expected” bytes do
not match those actually received, the ITIM alarm will be raised.
47. LOF
Loss Of Frame
Alarm Object:
- Transponder Line port (OCh/OTUk Sink)
- Transponder SDH/SONET Client port (ODUk/RSj Sink)
- Transponder SDH/SONET Client port (OS16/OS64 Sink)
- Transponder Client port (OChr/OTUk Sink)
Major
An LOF alarm is raised if a Loss of Frame condition is detected in the incoming signal. Typical causes of an
LOF alarm are as follows:
1) low signal-to-noise-ratio (low input signal optical power; high noise in the line, or damaged/dirty optical
components).
2) severely distorted signal (input signal with high impairments such as dispersion, or non-linear effects).
3) Wrong signal format (mapping of an input signal that is not accepted by Nokia Siemens Networks
transponder cards).
4) Channel loss on a card equipped with APD (Avalanche Photo Diode) receiver (i.e., possible on cards
which can be equipped with a Line XFP). Since APD receivers have a sensitivity in the -25 dBm to -30 dBm range,
any remaining power from unsuppressed ASE (Amplified Spontaneous Emissions) from the line amplifier can
sometimes be at a level high enough to prevent the expected LOS alarm from being raised for a loss-ofchannel
condition. In such a situation, the LOF alarm is raised instead.
5) In rare cases, the LOF alarm indicates a receiver permanently damaged by an overpower condition.
48. LOF-egress
Loss Of Frame egress
Alarm Object: Transponder Client Out port [incoming (ingress) signal from the Line mapped to the outgoing
(egress) signal exiting the SDH/SONET Client Out port]
Major
An LOF-egress alarm is generated from a LOF defect detected by the mapping of ingress line port signal to
the egress direction of a SDH/SONET Client Out port.
49. LOFLOM
Loss Of Frame and Multiframe
Alarm Object: Muxponder Line port (ODU Sink)
Major
An LOFLOM alarm is raised if a Loss of Frame and a Loss of Multiframe condition are both detected in the
incoming signal.
50. LOF-O
Loss Of Frame ( OSC Overhead )
Alarm Object:
- In-line Amplifier and Pre-amplifier OTS Sink
- Pre-amplifier OMS Sink
Major
An amplifier card will raise the LOF-O alarm if it can no longer detect the proper frame structure of the
incoming Optical Supervisory Channel.
51. LOS
Loss Of Signal
Alarm Object:
- Transponder SDH/SONET Client In port (OS16/OS64 Sink).
- Transponder OTU Client In port.
- Transponder Ethernet Client In port (ETY3 Sink).
- Transponder Ethernet Client In port (ETY4 Sink).
- Transponder Fibre Channel Client port.
- Amplifier Line In port (OTS Sink).
Major
An LOS alarm will be raised if the incoming signal power at the indicated interface falls below the LOS
threshold. For Transponders, LOS detection of the Client In signal is a builtin feature of the SFP/XFP modules. For
Amplifier cards, LOS is raised if there is both of the following conditions exist simultaneously: loss of payload
(LOS-P) and loss of Optical Supervisory Channel (LOS-O).
52. LOS-O
Loss Of Signal ( OSC )
Alarm Object: In-line Amplifier and Pre-amplifier OTS Sink
Major
A card will raise the LOS-O alarm if it can no longer detect the incoming Optical Supervisory Channel. Note:
when the OSC is lost, the link control mechanism goes to a "best effort" state in order to maintain service.
Consequently, an LOS-O condition must be fixed as soon as possible.
53. LOS-P
Loss Of Signal ( Payload )
Alarm Object:
- Amplifier Line port (OTS Sink and OMS Sink)
- Transponder, muxponder, and regenerator card Line port (OCh Sink)
- F40MR and F40V card input ports (OMS Sink)
- O02CSP
- F09MDRT (OCh Sink) C1 through C8 input ports
- F48MDP (OCh Sink) Individual channel input ports
- F09MDR96 (OCh Sink) Tributary input ports (TX-IN1 through TX-IN9)
Major
The LOS-P alarm is raised if the optical input signal at the indicated interface is detected as missing by
comparing the signal’s power level with a defined threshold (this threshold is not user-configurable). The criteria for
declaring LOS-P varies. Examples:
1) For transponder cards, a power loss alarm pin of the optical modules (XFPs, SFPs or MSAs) is used for
detection (thresholds and detection times depend on the particular module).
2) For some cards, LOS and LOF (Loss of Frame) must both exist in order for LOS-P to be declared.
3) For amplifier cards, LOS-P is declared if the incoming signal is below the threshold, but the Optical
Supervisory Channel is still detected.
54. LSM
Link State Mismatch
Alarm Object: Amplifier card OMS Layer Sink
Major
A mismatch has been detected in the link state, i.e., the link state “running” received at the OSC does not
match the link state “prestart” as configured by link control.
55. MSIM
Multiplex Structure Identifier Mismatch
Alarm Object:
- I08T10G-1 card
- I04T40G-1 and I04T40G-2 card
- I10T100G-1 card
Major
If a card detects a mismatch between the expected Multiplex Structure Identifier (MSI) and that actually
received, a MSIM alarm will be generated. MSI bytes are part of the PSI (Payload Structure Identifier) message in
the OPU2 overhead. MSI is user-configurable on I04T40G-2 and I10T100G-1 cards. If the expected and received
MSI values are not set correctly, the MSIM alarm will be raised to signify the mismatch.
56. OCI
Open Connection Indication
Alarm Object:
- Transponder Line Port (ODUk Sink)
- Transponder Client Port (ODUk Sink)
- Transponder TCM Layers (ODUk Sink)
Minor
Open Connection Indication (OCI) is monitored at the ODUk layer. Detection of OCI signifies that there is a
Loss of Signal defect due to an output connection point not connected to an input connection point.
57. OPR
Optical Power Receiver Too Low
Alarm Object: Transponder Line Port (OCh Sink)
Major
An transponder card will raise the OPR alarm if the incoming signal power at the line interface falls below the
alarm threshold. OPR is intended to be a "degraded signal" alarm threshold that is reached before the more serious
LOS threshold is reached.
The OPR raise and clear time is 100 seconds. So, after each troubleshooting step, wait at least 100 seconds to see if
the alarm clears.
58. PESF
Preemphasis Section Fail
Alarm Object: Line Amplifier card, OMS Source.
Minor
The PESF alarm indicates that 10 consecutive power preemphasis routines have failed. This could be due to a
faulty MCP card, a faulty CCEP card, a missing card, fiber problems (dirty connections), or a DCN communications
failure. Additionally, if Automatic Attenuator Control is manually disabled (sometimes necessary for maintenance or
troubleshooting activities), the PESF alarm is raised since automatic link control is not in its normal state (10
consecutive power preemphasis routines are guaranteed to fail in this condition). In this case, the alarm serves as a
reminder to re-enable Automatic Attenuator Control once the maintenance activity is completed.
Note that the Automatic Attenuator Control parameter is supported only for Advanced Power Control (APC).
Therefore, the PESF alarm in this scenario is relevant only for APC-controlled NEs. A special log-in (Power User) is
required to enable/disable Automatic Attenuator Control.
59. PHF
Power Too High Failure
Alarm Object:
- Client In and Line In interfaces of transponder and muxponder cards.
- MCP card input ports
- F40MR-1 card input ports
- F09MDRT card input port (C1 through C9)
- F48MDP card (individual channel input ports)
- F09MDR96 card Tributary inputs (TX-IN1 through TXIN9)
Minor
The PHF alarm will be raised if the optical power of the input signal at the indicated port is above the user-
specified PHF threshold.
60. PLF
Power Too Low Failure
Alarm Object:
- Client In and Line In interfaces of Transponder and Muxponder cards.
- MCP card input ports
- F40MR card input ports
- F09MDRT card input port (C1 through C9)
- F48MDP card (individual channel input ports)
- F09MDR96 card Tributary inputs (TX-IN1 through TXIN9)
Minor
The PLF alarm will be raised if the optical signal power at the indicated port is below the user-specified PLF
threshold.
61. PLM
Payload Mismatch
Alarm Object: The PLM alarm can be raised by all transponder and muxponder cards.
Major
For some card types, the the “transmitted” and “expected” Payload Types are user-configurable. If these
values were not set correctly, the PLM alarm will be raised to signify the mismatch.
62. RDI
Remote Defect Indication
Alarm Object: The RDI alarm can be raised by transponder and muxponder cards.
Minor
An RDI alarm is sent upstream, and is typically used for a control and feedback mechanism for the network,
most often to override any automatic protection switching modes. An RDI alarm is raised due to traffic-affecting
conditions such as LOS or LOF. The NE that detects the fault will raise the appropriate alarms and also send an
indication to the distant NE (where the signal originates). This causes an RDI alarm at the transmitting NE.
63. SSF
Server Signal Fail
Alarm Object: Transponder cards and amplifier cards
Minor
The SSF alarm indicates a signal failure on a server layer. The signal failure could be on the card raising the
SSF alarm, or on another upstream card.
64. SSF-egress
Server Signal Fail – egress
Alarm Object: Transponder cards
Minor
An SSF-egress alarm is raised due to a signal failure on a server layer on the Line that is mapped to the Client
(egress) SDH/SONET or Ethernet port.
65. SSF-O
Server Signal Fail ( OSC )
Alarm Object: Amplifier card line ports
Minor
The SSF-O alarm indicates an SSF condition that affects the Optical Supervisory Channel, but not the
payload. The fault could be on the card raising the SSF alarm, or on another upstream card.
66. SSF-P
Server Signal Fail Payload
Alarm Object: Amplifier card Sink direction ; Transponder/Muxponder Optical Channel Sink direction
Minor
The SSF-P alarm indicates an SSF condition that affects the payload, but not the Optical Supervisory Channel.
The fault could be on the card raising the SSF-P alarm, or on another upstream card.
67. SYNCF
Synchronization Failure
Alarm Object: Ethernet and Fibre Channel client signals of transponder, muxponder and Carrier Ethernet
(I22CE10G-1) cards.
Major
Ethernet or Fibre Channel synchronization failure in Client-to-Line direction.
68. SYNCF-egress
Synchronization Failure egress
Alarm Object: Transponder Ethernet and Fiber Channel Client port
Major
The SYNCF-egress alarm is generated from a SYNCF defect detected by the mapping of the ingress line port
signal to the egress direction of a directly-mapped Ethernet or Fibre Channel client port.
69. TIM
Trace Identifier Mismatch
Alarm Object:
- Amplifier Line In port (OTS Sink)
- Transponder/Muxponder Line In port (OTUk Sink)
- Transponder/Muxponder Line In port (ODUk Sink)
- Transponder SDH/SONET Client port (RS ingress)
- Transponder/Muxponder Client In port (OTUk Sink)
- Transponder/Muxponder Client In port (ODUkP Sink)
- Transponder/Muxponder TCM Line In port (ODUkT Sink)
- Transponder TCM Client In port (ODUkT Sink)
Minor
The TIM alarm is raised if the indicated card detects a mismatch between the expected Trail Trace Identifier
message string and the Trail Trace Identifier message string actually received.
70. TIM-egress
Trace Identifier Mismatch egress
Alarm Object: Transponder SDH/SONET Client port (RS egress)
Minor
The TIM-egress alarm is generated from a TIM defect detected by the RS trace monitoring of the signal
mapped from line to client.
71. TNEF
Target NE Failure
Alarm Object: NE Name (the name user-specified on the Network Element Configuration window).
Minor
The TNEF alarm will be raised if a Network Element is not reachable via the DCN.
72. VAOTC
VOA Threshold Crossed
Alarm Object: Link Control: Optical Channel layer.
Minor
A Variable Optical Attenuator (VOA) problem occurred during a manual power adjust or manual pre-emphasis
routine. A setting higher than the upper VOA threshold (20 dB) or lower than the lower VOA threshold (0 dB) is
being attempted.
Processing Alarms
73. APSM
APS Mismatch
Alarm Object: Subsystem
Major
Replacement of a faulty Compact Flash module on an NE Controller card (CCEP or CCMP) can cause an
APSM alarm. See Compact Flash replacement in chapter 4.2. After replacement, the APS version that is present on
the new Compact Flash is checked against the version number the network element thinks it should have. (The latter
is stored on an EEPROM on the shelf backplane). If there is a mismatch, the NE will enter Recover Mode (see
chapter 8 for details), and the APSM alarm will be raised.
74. LOTR
Loss Of Time Reference
Alarm Object: Network Element
Warning
The LOTR alarm is raised if all configured external NTP (Network Time Protocol) references have been
unreachable for a period of at least 10 minutes. The alarm is cleared 10 minutes after an NTP server becomes
reachable again, or immediately after the last NTP server is manually deleted from the NTP configuration.
75. MIBF
MIB Failure
Alarm Object: Subsystem
Major
Each NE’s Management Information Base (MIB) contents are stored in two places: the flash memory on-
board Controller cards (CCEP or CCMP) and on that card’s removable Compact Flash module. The MIBF alarm can
be caused by three related, yet distinct events:
1) A sudden “double hardware failure” in an operational network (i.e., simultaneous failure of a Controller
card’s two MIB storage devices - its Onboard Flash and its Compact Flash). Such a failure is extremely unlikely. If it
occurs, the NE Controller card and its Compact Flash must be replaced.
2) A mismatch condition that might occur immediately after (and as a direct result of) replacing a failed
Controller card and/or its Compact Flash module. Such replacements can sometimes result in a mismatch of the MIB
contents and/or a mismatch of the APS software versions. In such cases, the NE will re-start in “Recover Mode”
(meaning it could not find a valid MIB). No communication to peripheral cards is possible and the NE will appear as
an OLR network element on the Element Manager Shelf Equipment window. A backup copy of the MIB must be
downloaded to the NE.
3) If the NE was in “Recover Mode”, setting the NE to default (see chapter “Resetting the NE to default
configuration” in the hiT 7300 Operating Manual) will raise the MIBF alarm. In this case, Recover Mode can be
exited only via manual methods as explained below.