In the operation and maintenance of PDH/SDH/E1 transmission networks, LOF and LOC are frequent link abnormality alarms. Both are often accompanied by an increase in bit error rate, service packet loss and interruption, which directly affect transmission quality and network availability. As field engineers, accurately distinguishing the two types of alarms, clarifying the trigger logic, and using the TFN T1000M Bit Error Tester for positioning and verification are core skills for rapid troubleshooting and ensuring link stability. This article provides a professional analysis from five dimensions: alarm definition, trigger mechanism, difference comparison, correlation, and instrument measurement.
1. Core Definitions and Trigger Mechanisms of LOF and LOC Alarms
1.1 LOF (Loss of Frame) Alarm
LOF is a frame synchronization layer alarm, indicating that the receiving end cannot continuously lock the standard frame header and the frame structure is completely invalid. In E1/SDH systems, devices identify the frame start position based on framing bytes such as FAS/A1/A2. When OOF (Out of Frame) persists longer than the standard duration (typically 3 ms), it escalates to an LOF alarm.
Trigger conditions:
- Valid framing bytes are not detected in consecutive multiple frames, and frame synchronization is completely lost
- Excessive clock frequency offset, severe line damage, or frame format mismatch
- Accompanied by a sharp rise in bit error rate, making overhead bytes unreadable
The TFN T1000M can monitor frame synchronization status and FAS error counts in real time to accurately determine the LOF trigger point.
1.2 LOC (Loss of Continuity Check) Alarm
LOC is a link-layer OAM connectivity detection alarm, mostly used in Ethernet/packet/tunnel links. It monitors end-to-end connectivity periodically based on CCM packets. An LOC is reported when no valid CCM packet is received within 3.5 times the sending interval, meaning end-to-end connectivity is broken.
Trigger conditions:
- Physical link interruption or signal loss (optical/electrical)
- Intermediate node failure or configuration error blocking CCM packets
- Excessive link delay or jitter causing detection timeout
LOC does not parse the frame structure directly; it only checks whether detection packets are received continuously.
2. Key Differences Between LOF and LOC Alarms
| Comparison Item | LOF Alarm | LOC Alarm |
| Alarm Layer | Physical layer → Frame synchronization layer | Link layer → OAM detection layer |
| Monitoring Target | Frame structure, framing bytes, sync status | End-to-end CCM packets, connectivity continuity |
| Main Causes | Clock unlock, frequency offset, line errors, frame mismatch | Link down, node failure, blocked CCM, excessive delay |
| Associated Metrics | bit error rate, FAS error, CRC error, code error | Packet loss rate, link delay, CCM reception interval |
| Typical Scenarios | E1/SDH/PDH traditional transmission links | Ethernet OAM, tunnels, packet networks, virtual links |
| Instrument Monitoring | Frame status, frame errors, bit errors, frequency offset | Connectivity, delay, packet loss, CCM Tx/Rx |
3. Internal Correlation Between LOF and LOC Alarms
3.1 Causal Propagation
Physical layer failures (e.g., cable break, loose 2M connection, degraded connector) first cause LOS (Loss of Signal), which further leads to LOF. Meanwhile, CCM packets are interrupted, triggering LOC. In this case, bit error rate approaches 1.0, services are fully interrupted, and both alarms appear simultaneously as part of the alarm chain.
3.2 Error Deterioration Progression
Mild line damage first increases bit error rate, corrupts framing bytes, and causes LOF. If the fault persists, connectivity detection fails and LOC is triggered. LOF indicates “the frame structure is broken”; LOC indicates “the link is down”. Both point to transmission link degradation.
3.3 Common Clock Issues
Abnormal clock source or excessive frequency offset both disrupt frame synchronization (triggering LOF) and cause CCM packet timeout due to delay jitter (triggering LOC). The E1 frequency offset test of TFN T1000M can quickly verify whether clock deviation is within the compliant range of ±50 ppm.
4. Measurement, Location and Verification with TFN T1000M Bit Error Tester
4.1 LOF Alarm Location Procedure
1. Port configuration: match on-site impedance (75 Ω / 120 Ω), HDB3 coding, PCM31/PCM30 frame format
2. Start E1 test, monitor FAS ERR, CRC ERR, CODE ERR and bit error rate
3. Use frequency offset test to check clock deviation
4. Perform terminal/bridge loopback tests to locate local, line or far-end equipment issues
4.2 LOC Alarm Verification Procedure
1. Enter the Ping/OAM function of the tester, configure CCM packet interval and detection parameters
2. Run end-to-end connectivity test, check packet reception and timeout statistics
3. Use delay test to determine whether timeout causes LOC
4. Perform segmented loopback to locate faulty nodes and rule out intermediate blocking
4.3 Joint Judgment Logic
- Only LOF: frame format / clock / line bit error issues; physical link is up but synchronization fails
- Only LOC: OAM configuration / intermediate node / detection packet issues; physical layer may be normal
- Both LOF and LOC: physical link down or severe degradation; check LOS first
5. Engineering Operation and Maintenance Summary
LOF and LOC are abnormal indicators at different layers: LOF manages frame synchronization, LOC manages connectivity. They share physical-layer failure causes and often combine with bit error rate degradation to form an alarm linkage.
For on-site troubleshooting, the TFN T1000M Bit Error Tester is preferred to complete frame status monitoring, bit error statistics, frequency offset test, connectivity verification and segmented loop location. It quickly distinguishes synchronization failure, link interruption or configuration error, greatly shortening fault duration and improving transmission network stability.