The WXCP Protection Configured for the LOG Board Is Invalid

The WXCP protection configured for the LOG board is invalid due to the configured attributes of the board.

Fault Category

Protection

Symptom

The LOG board is configured with the correct WXCP protection.

During a protection switching test, services are interrupted because there is no protection channel to which the services can be switched; however, no alarms are reported to the T2000.

Check whether the protection configuration is correct.

If you delete the protection group and then configure a new one, the fault persists.

Cause Analysis

The WXCP protection configured for the LOG board is invalid due to the configured attributes of the board.

Procedure

  1. Check the LOG board of the protection group.
    1. In the NE Explorer, select the LOG board to be checked.
    2. Select Configuration > WDM Interface from the Function Tree.
    3. Click the Advanced Attributes tab.
    4. Check whether the Max Packet Length is 9800.
  2. In this case, set the value of this parameter to 1511.
  3. Because the value of the parameter cannot be changed, set the LOG board.
  4. After the LOG board is reset, the value of the parameter is displayed as 9800.
  5. Test whether the fault is cleared. If the fault is cleared, the WXCP protection becomes valid.

Reference Information

None.

Advertisements

The Input Optical Power of the OTU Board Is Abnormal Due to a Fault of the OPU Board

The input optical power of the OTU board is abnormal due to a fault of the OPU board.

Fault Category

Optical Power Abnormity

Optical Amplifier Unit

Symptom

In a single-channel ring network, the input optical power of an OTU board drops from 0 dBm to -7 dBm, -15 dBm, or -62 dBm.

This ring network bears the SDH service and is configured with the multiplex section protection (MSP).

Cause Analysis

The launched optical power of the opposite OTU is abnormal, or the line amplifier unit is faulty.

Procedure

  1. By checking whether there are abnormal alarms against the input optical power of the opposite OTU board, you can find that the parameters of the opposite OTU board are proved normal. This indicates that the launched optical power of the opposite OTU is normal.
  2. The input and output optical power of the opposite amplifier board are also checked normal.
  3. The input and output optical power of the local amplifier board, however, are checked abnormal. The input optical power of the local amplifier board is constant, whereas the output optical power of the local amplifier board is abnormal. This indicates that the local amplifier board is faulty.
  4. After you replace the local amplifier board, the system is restored.

Reference Information

  • When you find that the output optical power of the local OTU is abnormal, check the following items:
    • Input and output optical power of the opposite OTU board
    • Input and output optical power of the opposite amplifier board
    • Input and output optical power of the local amplifier board
  • If the anomaly of optical power occurs at random, perform the following steps:
    • Check whether any fiber jumper is loose or bent.
    • Clean the fibers and connectors.
    • Perform an optical time domain reflectometer (OTDR) test under the customer’s consent.

How to Handle the J0_MM Alarm on the LWM

How to handle the J0_MM alarm on the LWM.

Product

OptiX Metro 6100

OptiX Metro 6040

Fault Type

Optical Transponder Unit

JO_MM

Symptom

The ANT20 analyzer is used to test an STM-16 link with two LWM boards. One LWM connects to the analyzer and the other is looped back. The traffic is normal but the LWM reports the J0_MM alarm. Check on the J0 transmitted by analyzer shows that the J0 byte was set to 11. Check on LWM -> Configuration/WDM Overhead Management/SDH Overhead shows that J0 to be transmitted and J0 to be received (displayed in hex) are both 11.

Cause Analysis

Verify the SDH overhead in text mode not just in hexadecimal format.

Procedure

  1. Check on the J0 trace identifier on analyzer shows that the test is in process.
  2. Checked on the SDH overhead of the LWM (displayed in text) shows that the J0 received is indeed “text”, but the J0 to be received is blank.
  3. The J0 to be received (displayed in text) is changed to be tested and the alarm is cleared.

Reference Information

None.

Failing to Create the 622 Mbit/s Service

The ATM 622 Mbit/s service fails to be created. You need to adjust the VCTRUNK that is bound with VC-4.

Product

Fault Type

Configuration_Problem

Symptom

The 622 Mbit/s service fails to be created.

Cause Analysis

The four bound VC4 virtual connections are in the first ATM processing unit. The source end or sink end of the created connection belong to the same external port. The bandwidth used at the source end and sink end is 622 Mbit/s x 2 = 1244 Mbit/s, which exceeds the maximum bandwidth of a single ATM processing unit.

Procedure

  1. Delete the VCTRUNK that is bound with VC4 timeslots 1 -4.
  2. Set up the VCTRUNK that is bound with VC4 timeslots 5 -8.

Reference Information

None.

Creation of Intra-Board Wavelength Protection on the LDG Fails

The creation of intra-board wavelength protection on the LDG fails due to the configured attributes of the board.

Product

OptiX Metro 6100, OSN6800, OSN 8800

OptiX Metro 6040

Fault Type

Protection

Symptom

Housed in the OptiX Metro 6100 subrack, the LDG has 2 WDM interfaces (IN1/OUT1 and IN2/OUT2). An attempt is made to create the intra-board wavelength protection on the LDG by using the T2000-LCT (version V200R003C01B01h). In Configuration/Wavelength Protection Group, IN1/OUT1 of the LDG cannot be selected as the working channel and IN2/OUT2 of the LDG as the protection channel.

Cause Analysis

The creation of intra-board wavelength protection on the LDG fails due to the incorrect Board Receiving/Transmitting Attributes of the board.

Even though the board dually feeds and selectively receives signals, this information is not automatically displayed.

Procedure

  1. Select the LDG board and choose Board in Configuration/WDM Interface for query the LDG.
  2. Board Receiving/Transmitting Attributes displays the information according to the board type. Then, intra-board wavelength protection can be normally configured on the LDG.
  3. The problem is resolved.

Reference Information

None.

Inserting, Removing, and Resetting Operations Affect NG WDM Products

How do inserting, removing, and resetting operations affect the NE software version and configuration of NG WDM products.

Product

OptiX OSN 6800

OptiX OSN 3800

Fault Type

Software Upgrade

MSSW_DIFFERENT

SWDL_CHGMNG_NOMATCH

CFGDATA_OUTRANGE

Symptom

The OptiX OSN 6800 V100R004C01 version or before and the OptiX OSN 3800 V100R004C01 version or before use the software upgrade with the Toolkit.

The OptiX OSN 6800 and OptiX OSN 3800 automatically matches the master and slave subracks and software packages on them, and reacts differently to the operations on the SCC of the original WDM products such as insertion, removal, and reset.

Loading software package: All files that need to be stored on the NE are bundled into a package (including NE software, board software, INI file, FPGA file, and extended BIOS). This package is sent to the active SCC and copied to the standby SCC and other boards. Finally, the NE software, board software, and FPGA file start running to upgrade the NE.

Automatic software package matching: When the new inserted standby SCC board working normally, the active SCC checks the matching state according to the information sent from the standby SCC. If the software package is mismatched, the active SCC copies a new software package to the standby SCC, and activate the new software package on the standby SCC. This can ensure the consistency of the software on the active SCC and standby SCC.

For details on the symptom, see Table 1.

Cause Analysis

Relevant alarms:

When the software package version is inconsistent between the active and standby SCCs, the SCC reports the alarm indicating software mismatch (MSSW_DIFFERENT).

If the new software mismatches the software of any board after the single SCC is replaced, the “replace SCC” alarm is reported (SWDL_CHGMNG_NOMATCH). This alarm can be cleared by loading the package through the Toolkit.

If the configuration data between the new SCC and the original SCC is different, the CFGDATA_OUTRANGE alarm is reported.

Procedure

  1. For details on how to handle the effect caused by inserting, removing, and resetting operations on the SCC, see Table 1.

Reference Information

Table 1 Affection of plugging & unplugging and resetting operations of the SCC
SCC Type Maintenance Operation Phenomenon Possible Alarm Recommended Handling
Single SCC in master subrack Remove and insert the original SCC Configuration data on the SCCs is not consistent. CFGDATA_OUTRANGE Use the Toolkit to deliver the backup configuration data of the SCC.
A board of the same version is inserted when the SCC is out of position (including the SCC in the slave subrack) The board gets into service normally.
A board of a different version is inserted when the SCC is out of position (including the SCC in the slave subrack) SWDL_CHGMNG_NOMATCH Use the ToolKit to load the package correctly.
Replace SCC Replace the SCC with one of the same software version. If the configuration data between the new SCC and original SCC is different, the “CFGDATA_OUTRANGE” alarm is reported. If the configuration data is the same, the alarm is not reported.
Replace the SCC with one of a different software version. SWDL_CHGMNG_NOMATCH Use the ToolKit to load the package correctly.
Dual SCC master in subrack Remove and insert the active SCC. The active SCC and standby SCC are switched. The state of the NE software is inconsistent with the state of the standby SCC.

When the SCC is of the same software version, there is no effect. When the SCC is of a different software version, automatic package loading is performed to match the current NE software version, and an alarm is reported during the matching period.

MSSW_DIFFERENT Wait until the NE software matches the software package automatically.
Remove and insert the standby SCC. When the SCC is of the same software version, there is no effect. When the SCC is of a different software version, automatic package loading is performed to match the current NE software version, and an alarm is reported during the matching period. MSSW_DIFFERENT Wait until the NE software matches the software package automatically.
SCC in slave subrack Remove and insert the original SCC. The slave subrack is not reachable to the T2000.
Replace the SCC. When the new SCC is of the same software version as the original SCC, there is no effect.
When the new SCC is of a different software version from the original SCC, automatic package loading is performed to match the current NE software version.

GPON Port Specifications

This topic describes specifications and standards compliance of the GPON interfaces.

Table 1 GPON port specifications
Parameter Specifications
Transmission rate Rx: 2.488 Gbit/s

Tx: 1.244 Gbit/s

Connector SC/APC
Maximum reach 20 km
Standard compliance ITU-T G.984.2 CLASS B+
Center wavelength Tx: 1310 nm

Rx: 1490 nm

Tx optical power 0.5 dBm to 5.0 dBm
Extinction ratio > 10 dB
Minimum receiver sensitivity -27 dBm
Maximum overload optical power -8 dBm