ZMUX-4102 Common Fault Troubleshooting Guide


Release time:

2026-06-10

This guide is tailored for the ZMUX‑4102 multi‑service access and transmission platform. It systematically explains the functions of the chassis panel and the status indicators on each line card, and organizes common fault symptoms, troubleshooting steps, and solutions into hierarchical categories—such as power‑related issues and link‑layer problems (E1/optical ports). In addition, it covers general troubleshooting procedures for service interfaces like audio and serial ports, providing a quick reference for on‑site maintenance and fault localization.

ZMUX-4102 Common Fault Troubleshooting Guide

ZMUX-4102 is a multi-service access and transmission platform (MSTP device) independently developed by Guangzhou Yinxun Comm.Tech.Co..Ltd, widely used in critical communication scenarios such as airport air traffic control, meteorological observation, and radar data. This guide aims to help maintenance personnel quickly identify common faults and ensure the stable and reliable transmission of services.


I. Equipment Overview and Core Features

1.1 Equipment Composition

The ZMUX-4102 consists of a chassis, power supply boards, a main control cross‑connect board, and I/O service boards. The chassis is designed to be 2U high and features 10 card slots, including two hot‑swappable power supply slots, two main control cross‑connect slots, and six universal I/O service board slots. It provides hot‑standby redundancy for the power supply, main control circuitry, transmission links, and service ports.

 

1.2 Core Features

  • Multi-link protection: It supports a variety of transmission media, including IP links, E1 circuits, fiber optics, STM‑1/4 lines, 5G wireless, and satellite, and enables automatic protection switching between dual or multiple links.
  • System-wide redundancy: Optional 1+1 redundancy for dual power supplies and dual control boards, ensuring high safety and reliability.
  • Diverse business types: Supports a wide range of service interfaces, including FXO/FXS, 2- and 4-wire E&M, RS‑232/RS‑422/RS‑485, 10/100BASE‑T, digital I/O, magneto telephones, ADS‑B radar, VHF, and more.
  • Centralized Monitoring: Optional network management features support loopback detection, port parameter configuration, remote firmware upgrades, and more.

II. Interpretation of Equipment Indicator Light Statuses

Accurately interpreting the indicator lights is the first step in troubleshooting. Please distinguish between the chassis panel indicators and the indicators on each board.

2.1 Chassis Front Panel Indicator Lights (System-Level)

Logo

Color

Status

Meaning Explanation

PWRA / PWRB

Green

Evergreen

The device has powered on normally.

 

-

Extinguish

The device is not powered on, or there is a power supply failure.

ALM

Red

Constantly lit

The system has alerts.

 

-

Extinguish

No alarms in the system.

TEST

Yellow

Constantly lit

Maintenance testing is in progress.

 

 

Extinguish

No test tasks

Buzzer

-

Ring the bell

A new alert has appeared.

 

-

Stop the bell

After pressing the SL (silence) button or confirming the fault via the network management system, the buzzer stops sounding.

 

2.2 Main Control Board (CL-1) Indicator Lights

The main control board provides more detailed link‑status indications.

Logo

Color

Status

Meaning Explanation

ON-LINE

Green

Evergreen

The board is in the primary operating state.

 

-

Flicker

The board is in standby mode.

 

-

Extinguish

The board has failed or has been decommissioned.

ALM

Red

Constantly lit

The board card has an alarm.

 

-

Extinguish

The board is functioning properly, with no alarms.

SDH ACT

Green

Constantly lit

The optical port link is connected normally.

 

-

Extinguish

Optical port link connection error

SDH LOS

Red

Constantly lit

Optical signal reception error

 

-

Extinguish

Optical signal reception is normal.

 

2.3 Common I/O Service Board Indicator Lights

A. E1/FE Interface Board (M8E1/FE)

Logo

Color

Status

Meaning Explanation

ON-LINE

Green

Evergreen

The board is online and functioning properly.

 

-

Extinguish

The board has failed or has been decommissioned.

E1 1-8

Green

Constantly lit

Both the transmit and receive signals on the E1 port are functioning normally.

 

-

Flash mob

E1 port receives an abnormal signal.

 

-

Slow flash

The E1 port is receiving signals normally, but the remote device has an alarm.

 

-

Extinguish

No signal input on the E1 port.

 

B. Optical Interface Board (MOP2/FE4)

Logo

Color

Status

Meaning Explanation

ON-LINE

Green

Evergreen

The board is online and functioning properly.

 

-

Extinguish

The board has failed or has been decommissioned.

SDH ACT

Green

Constantly lit

The optical port link is connected normally.

 

-

Extinguish

Optical port link connection error

SDH LOS

Red

Constantly lit

Optical signal reception error

 

-

Extinguish

Optical signal reception is normal.


III. Tiered Troubleshooting Guide

3.1 Power Supply Faults

Fault phenomenon

Possible causes

Troubleshooting Steps

Solution

Both the PWRA and PWRB lights are off.

1. External power supply interruption

2. Power cord failure

1. Check that the power cord is securely connected.
2. Inspect the distribution switch.
3. Measure the input power supply voltage.

Restore external power supply or replace the power cord.

Only the power indicator is lit.

Single-power-board failure or dual-power supply not configured

1. If a dual-power configuration is in place, check the PWR LED and switch status of the faulty power supply board.
2. Re-seat the faulty power board.

Replace the faulty power supply board.

For a single‑power‑supply configuration, it is recommended to add a redundant power supply board.

The device frequently restarts or loses power.

Unstable power supply voltage

1. Measure the input voltage fluctuations.
2. Check the contact of the power supply lines.

Use a stable UPS power supply;

Inspect and tighten all power connections.

 

3.2 Link-Level Faults

A. E1/FE Interface Board (M8E1/FE) Link Failure

Indicator light status

Fault Localization

Troubleshooting Steps

E1 light is off.

No Signal Input (LOS)

1. Check the physical connection: Verify that the E1 cable is properly connected to the DB44 interface or the patch panel. Also, inspect the cable for open circuits.
2. Check the remote device: Verify that the remote E1 equipment is powered on and functioning properly.
3. Check impedance matching: Verify that the local board’s impedance setting (75 Ω/120 Ω) is compatible with the remote device and the transmission line.

E1 light flashing rapidly

Received Signal Abnormality (LOF/AIS)

1. Check whether the E1 cable is excessively long, damaged, or has loose connectors.
2. Perform a hardware loopback test: Apply a loopback at the E1 interface of the device to verify that the local transmit and receive functions are operating correctly.
3. Check the E1 link quality: Verify that the E1 link is transmitting without any bit errors.

E1 light is flashing slowly.

Remote Device Alarm

Check the peer device: This status indicates that local reception is normal, but there is a problem with the peer device. Troubleshoot the peer device and its link.

 

B. Main Control Board (CL-1) and Optical Interface Board (MOP2/FE4): Optical Interface (SDH) Link Failure

Indicator light status

Fault Localization

Troubleshooting Steps

The LOS light is always on.

Optical signal loss

1. Verify that the fiber-optic connections are correct and that the transmit and receive ports are cross‑connected.
2. Check whether the optical module and fiber optic cable are damaged, and try replacing them.
3. Check the status of the remote optical port and the optical power level.

ACT light off

The LOS light is off.

Link out of sync or other issues

1. Verify that the SDH link configuration (e.g., STM-1/4 mode) matches the configuration on the remote end.
2. Check whether the optical path loss is excessive, and use an optical power meter to verify that the received optical power remains within the sensitivity range.

 

C. Multi-Link Protection Switching Exception

Fault phenomenon

Key Inspection Points

Protection switchover is not taking effect.

1. Verify the configuration: Use the network management system to confirm that the multi‑link protection mode (e.g., IP + E1) has been properly configured.
2. Verify the backup link: The backup link itself must be in normal operating condition (e.g., for a backup E1 link, the indicator light on the M8E1/FE line card should remain steadily lit).
3. Verify that the fault detection thresholds (e.g., packet loss rate, latency) are appropriately configured.

Business interruption after the switchover

Verify that the primary and backup links are physically separated and routed independently to prevent simultaneous outages.

Verify that the backup link has sufficient bandwidth to carry all traffic.

Frequent link handovers due to errors

Check the transmission quality of the primary link (e.g., whether jitter and packet loss on the IP link are excessive, or whether the bit error rate on the E1 link is too high). You can try adjusting the size of the jitter buffer.

 

3.3 Business Interface Class Faults

Fault phenomenon

Troubleshooting Steps

Solution

RS232/422/485 port service is unavailable.

1. Board status check: Verify that the ON-LINE indicator on the corresponding I/O board is steadily lit.
2. Configuration Check: Use the network management system to verify that the port’s operating mode (synchronous/asynchronous), rate, clock edge polarity, data format, and other parameters match those of the user equipment.
3. Cable Inspection: Refer to the interface definitions in the manual’s appendix (e.g., SCSI to DB25/RJ45 for the MLS6) and verify that the user‑made cables are correctly configured.
4. Cross‑testing: Replace the service board with another one in a different universal I/O slot to determine whether the issue is caused by the slot itself.
Correct the configuration parameters; remake or replace the cables in accordance with the manual’s specifications; replace the faulty I/O board.

RS232/422/485 data contains errors or packet loss.

1. Utilize the board’s pseudo-random code testing function to perform bit-error-rate testing on the channel.
2. Check whether the quality indicator light on the transmission link (E1/IP) is showing intermittent alarms.
3. Verify that the equipment is properly grounded and that the shielded cable is connected correctly.
Optimize uplink quality; improve equipment grounding; reduce port speed or adjust the polarity of the clock edge used for synchronization.

Audio/E&M voice quality is poor (noise, intermittent)

1. Gain Adjustment: Use the network management software to adjust the transmit/receive levels of this port.
2. E&M signaling check: Verify that the E&M signaling mode (I, II, III, V) matches the configuration of the peer device.
3. M‑line timeout protection: Verify whether M‑signaling timeout protection has been triggered (indicated by rapid LED blinking), and adjust the timeout duration or disable this feature.
4. IP Link Quality: If transmission is over IP, check the jitter and packet loss rate of the IP network. You can try increasing the jitter buffer size.
Optimize gain settings; match E&M signaling modes; enhance IP network transmission quality; adjust jitter‑buffering.

Loop‑start trunk/FXO or subscriber line/FXS service abnormality

1. Check whether the indicator light for the corresponding port on the MVC16 board is lit (indicating port occupancy).
2. Check whether the user line is excessively long (loop resistance should be ≤1800Ω).
3. Use the network management system to verify the impedance matching and signal level settings of the FXO/FXS ports.
Reduce the user‑line distance; replace the cable; adjust the port impedance and gain parameters.

 

3.4 Network Management and Monitoring-Related Faults

Fault phenomenon

Key Inspection Points

The network administrator cannot connect to the device.

1. Verify that the CL-1 main control board is functioning properly (the ON-LINE indicator remains steadily lit).
2. Check the network management channel: whether to use the RS232 (CONSOLE) port on the CL-1 board or the FE1/2/3 Ethernet ports.
3. If using an Ethernet port, verify that the port is configured in “Managed Monitoring Interface” mode, and check the IP address, routing, and physical connectivity.
4. If using the RS232 port, verify that the serial port parameters (e.g., 9600, 8, N, 1) are correct.

Device status cannot be reported / Remote configuration failed

1. Verify that the device’s network management function has been properly enabled.
2. If transmission is carried out via the built-in management channel, verify that the entire transmission path supports VLAN passthrough for network management.
3. Verify whether the CL-1 main control board is in the active state.


IV. Analysis of Typical Fault Cases

Case 1: VHF voice communication experiences intermittent dropouts and significant latency when transmitted over an IP link.

  • Phenomenon: At a certain airport, VHF voice communications from the remote station are transmitted back to the central office via an operator‑provided IP dedicated line through the ZMUX‑4102, resulting in intermittent audio, latency, and dropouts.
  • Analysis: The inherent latency, jitter, and packet loss of IP networks significantly impact VHF voice services that demand high real-time performance.
  • Solution: 1. Log in to the ZMUX-4102 network management interface and navigate to the IP link configuration page.

2. Adjust the “Jitter Buffer”: Gradually increase the buffer size from its default value to mitigate network jitter, and identify the optimal setting.

3. Enable the “Anti-Packet Loss” and “Transmission Latency Optimization” features.

4. Optimization results: Speech quality has been significantly improved, with issues of intermittency and latency eliminated.

 

Case 2: When the IP leased line fails, the service automatically and seamlessly switches over to the E1 backup link.

  • Phenomenon: An IP leased line operated by the carrier has experienced a failure.
  • Analysis: The device is configured with a dual-link automatic protection switchover mode that supports both IP and E1 interfaces.
  • Solution: 1. The ZMUX-4102 continuously monitors the quality of the primary IP link and, upon detecting a failure, automatically switches all services to the standby E1 link—provided it is in good working condition—within an extremely short time frame (on the order of milliseconds).

2. On-site personnel reported no perceptible effects.

3. Once the IP leased line is restored, the device can automatically switch back, depending on the configuration.


V. Maintenance and Preventive Recommendations

  1. Document and Cable Management: Manufacture and inspect cables in strict accordance with the pin‑out definitions provided in the manual’s appendices—particularly for connectors such as SCSI, DB44, and DB37—and ensure that all cables are properly labeled.
  2. Regular Inspections: Check the status of the chassis ALM light and the board’s ON-LINE/STATUS light.

Check whether the power board fan is operating normally and whether the equipment is adequately ventilated and cooled.

Perform network management checks on E1 link bit error rate, optical port transmit and receive optical power, and other performance parameters.

  1. Configuration Backup: Regularly back up the device’s full network configuration via the network management system to enable rapid recovery in the event of a failure.
  2. Redundancy and Disaster Recovery: At critical nodes, dual power supplies and dual controllers must be deployed. When implementing multi‑link protection, ensure that the physical paths of each transmission link are separated to achieve true spatial disaster recovery.
  3. Using the self-test function: During commissioning and maintenance, make active use of the features described in the manual—such as injecting pseudo‑random test signals and performing loopback tests—to quickly pinpoint fault locations.
  4. Firmware Upgrade: Through the network management platform, perform online software upgrades on devices during off-peak periods to obtain the latest features and performance enhancements.
  5. Spare Parts Management: Based on the network scale, configure the necessary spare parts, such as: power supply boards (PS2/AC220, PS2/DC-48), control boards (CL-1), commonly used I/O interface cards (M8E1/FE, MLS12, MVC12), and optical modules.

 

Leave A Message


Fill in the message form and leave your contact information. Our staff will contact you within 24 hours (workdays).