Regularly record the baseline optical power for comparison before and after faults.
Common fault scenarios and systematic troubleshooting
6.1 Cable interruption or low optical power
Phenomenon: LOS alarm, complete or partial interruption of business.
Troubleshooting steps:
Use an optical power meter to measure the optical power at the receiving end. If it is lower than the sensitivity, use an OTDR to test the fiber optic cable breakpoint or attenuation point.
If the optical cable is intact but the power is low, check if the transmission power of the optical module is normal and clean the fiber optic connector.
If it is a 1686 WM system, check if the optical amplifier (EDFA) is working properly and if the pump current is normal.
6.2 Continuous Growth of Error Codes
Phenomenon: An increase in B1/B2 bit errors may lead to channel protection switching.
Troubleshooting:
Check if the transmitting and receiving power of both devices is within the range.
Check if the dispersion compensation is appropriate (especially for 10G links), and if the dispersion margin is insufficient, add DCM modules.
Confirm that the equipment is well grounded and eliminate external electromagnetic interference.
If only one VC channel experiences errors, check if the slot configuration and cross connection of that channel are normal, as there may be hardware cross point faults.
6.3 Protection switching failure
Phenomenon: Business did not switch after a malfunction in the working channel.
Troubleshooting:
Check the status of the protection group (network management displays "idle" or "faulty"), and confirm that the optical path of the protection port is normal.
Check protocol parameters (such as whether the K1/K2 bytes of MSP are properly exchanged), and use a protocol analyzer to track signaling.
If it is SNCP, check if the protection path is configured correctly and if the cross connections at both ends are consistent.
Perform manual switching test (force switch to protection), if manual success but automatic failure, check the switching triggering conditions (such as signal degradation threshold).
6.4 Network management is unable to manage devices
Troubleshooting:
Check if the DCC channel is normal, confirm that the DCC overhead byte is enabled and the channel rate matches.
If using an Ethernet management port, check the IP address, subnet mask, and routing.
Check the CPU load of the device. If it is too high, it may cause the network management to respond timeout. It is necessary to investigate whether there are a large number of alarm storms.
6.5 Clock asynchrony leads to pointer adjustment
Phenomenon: Excessive pointer adjustment events (such as AU pointer adjustment) may affect business jitter.
Troubleshooting:
Check the clock source priority setting and confirm that the device is locked to a valid external source.
If using line extraction, confirm that the upstream device clock is stable.
Adjust the "pointer adjustment mode" of SDH (such as setting it to "normal" or "frozen"), but a long-term solution requires restoring the synchronization link quality.
Hardware replacement and spare parts management
The Alcatel 1600 series is mostly mature products, and some models may face discontinuation. Spare parts management is particularly important:
It is recommended to establish a minimum inventory list for key boards (main control board, crossover board, power board, optical interface board), such as at least one set of backup main control board for every 10 nodes.
The hot swappable board card can be directly replaced online, but the operation sequence needs to be followed: first unplug the faulty board, wait for the new board to be inserted and wait for self inspection (about 1-2 minutes), and then activate or synchronize data through the network management.
When replacing the optical module, pay attention to anti-static measures and ensure that the optical port is clean.
Example of replacement steps (1651 SM replacing STM-4 optical interface board):
Set the card to be replaced to "offline" status on the network management.
Wear an anti-static wrist strap and remove the faulty card.
Insert the new board and wait for the LED indicator light to turn green and stay on (indicating normal operation).
Re load the software and synchronize the configuration of the board on the network management system.
Check business and alarms, confirm recovery.
Software upgrade precautions
The Alcatel 1600 series uses dedicated embedded software, and the upgrade process should strictly follow the manufacturer's guidelines:
Backup the current configuration and database before upgrading.
For dual master control devices, upgrade the backup master control first, switch and then upgrade the original master control to achieve zero interruption upgrade.
After upgrading, verify all business channels and protection functions, and observe performance indicators for at least 24 hours.
If the upgrade fails, it can be rolled back through the backup version in the onboard Flash.
