Cisco Cisco ONS 15454 SONET Multiservice Provisioning Platform (MSPP) Fehlerbehebungsanleitung
Cause
One possible reason for this issue is a faulty line card that connects two nodes, for example, OC−48. The
other possibility is high B3 Bit Error Rate (BER). This condition can be caused by a dirty fiber, loose
connector, faulty transmitter, or faulty receiver.
other possibility is high B3 Bit Error Rate (BER). This condition can be caused by a dirty fiber, loose
connector, faulty transmitter, or faulty receiver.
Solution
If a faulty line card causes this issue, check the light levels and clean the fibers. If the problem persists,
replace the line card in order to solve the problem. Line card replacement is usually the last resort. However,
while you perform these steps, critical traffic can be affected. In order to avoid packet drops, force the POS
interface to shut down automatically under SD condition, wrapping the RPR ring.
replace the line card in order to solve the problem. Line card replacement is usually the last resort. However,
while you perform these steps, critical traffic can be affected. In order to avoid packet drops, force the POS
interface to shut down automatically under SD condition, wrapping the RPR ring.
If the issue occurs due to excessive Path Bit−Interleaved Parity (PBIP) BER in excess of the Signal Degrade
(SD) threshold, configure this line under the POS interface on the ML−Series Card (see arrow A in Figure 2).
(SD) threshold, configure this line under the POS interface on the ML−Series Card (see arrow A in Figure 2).
pos trigger defects ber_sd_b3
This line reduces the number of wraps.
Figure 2 POS Trigger Defects ber_sd_b3
You can set the SD threshold when you create a new circuit (see arrow A in Figure 3).
The default values for POS trigger defects do not include ber_sd_b3. After you add this command, the
ML−Series RPR wraps when the SD threshold is reached.
ML−Series RPR wraps when the SD threshold is reached.
Figure 3 Set the SD Threshold