Monday, June 20, 2016

The Communication Between the NE and the T2000 Stops Because the NE Software Cannot Switch the ECC from an OSC Board to an OTU Board Automatically

The communication between the NE and the T2000 stops because the NE software cannot switch the ECC from an OSC board to an OTU board automatically.

Product

OptiX Metro 6100
OptiX Metro 6040

Fault Type

NE Offline

Symptom

One OptiX Metro 6100 V100R005 subrack houses two LWC1 boards and one SC2 board. The DCC function is enabled for the LWC1 and SC2 boards. The DCC communication status of the boards is Normal. Therefore, the boards (LWC1 and SC2 boards) on each NE can communicate with the corresponding boards on the other NEs that are cascaded with the NE.
One day, the on-site engineers needed to install one LQM board to the subrack but there was no idle slot in the subrack. Therefore, the engineers substituted the SC2 board with the LQM board to enable the inter-NE DCC communication through the LWC1 board.
When the engineers deleted the logical slot for the SC2 board on the T2000, the resident NE of the SC2 board can still communicate with the other NEs. When the engineers removed the physical SC2 board, however, the communication between the NE and the T2000 stops.

Cause Analysis

The NE software cannot switch the DCC from the OSC board to OTU board autonomically. There may be a bug in the software configuration.

Procedure

  1. Install the removed SC2 board back to the subrack.
  2. Add a slot for the logical SC2 board to the corresponding NE on the T2000.
    1. Double-click the NE to open the NE Panel. In the left-hand pane of the NE Panel, click the subrack NE to which you want to add a logical board.
    2. Select an idle slot, right-click it, and choose the SC2 board from the shortcut menu.
  3. In NE Explorer, click the desired NE. Choose Communication > DCC Management from the Function Tree.
  4. Click the DCC Rate Configuration tab and set the Enabled/Disabled flag of the SC2 board to Disabled.
  5. Delete the logical slot for the SC2 board from the corresponding NE on the T2000.
    1. Double-click the NE to open the NE Panel. In the left-hand pane of the NE Panel, click the NE.
    2. Right-click the logical slot for the SC2 board, and click Delete from the shortcut menu to delete the logical slot for the SC2 board.
  6. Click Verify Configuration on the T2000 to deliver the services of the SCC board to the SC2 board on the NE.
  7. In the Main Menu, choose Configuration > Configuration Data Management. In Configuration Data Management List, select one or more NEs. Click Back Up NE Data and select Back Up Database to SCC. In this manner, the data of the SCC board is backed up the to the FDB(flash database) and the current configuration data is saved.
  8. Perform a cold reset on the SCC board. Immediately after the reset is complete, remove the physical SC2 board.

Result

Currently, the DCC communication between subracks can be realized by using only an OTU board. That is, an OSC board is no longer required for the communication.

How to Resolve The Problem of The OptiX BWS 1600G Subrack Reports The TEMP_OVER Alarm

The way to resolve the problem of the OptiX BWS 1600G subrack reports the TEMP_OVER alarm.

Product

OptiX BWS 1600G, OSN6800,OSN8800,WDM

Fault Type

Subrack
TEMP_OVER

Symptom

The operating temperature of the OptiX BWS 1600G subrack is excessively high and the subrack reports the TEMP_OVER alarm on the T2000.

Cause Analysis

The OptiX BWS 1600G subrack is an independent heat dissipation system. The air is inhaled through the lower part of the subrack and the air duct for heat dissipation is beneath the fan tray assembly in the lower part. The air is exhausted through the slot area in the upper part of the subrack and the air deflector leads the heated air over the air duct to the front side of the subrack.

Procedure

  1. Check the ambient temperature in the telecommunications room and check whether the air conditioner is operating normally. If the air conditioner is faulty, eliminate its fault.
  2. If the alarm persists, check whether the fan tray assembly is operating normally. If the fan tray assembly is faulty, replace it.
  3. If the alarm persists, check whether the air deflector is damaged or improperly installed. If the air deflector is damaged or improperly installed, replace or reinstall it.

Result

Follow the steps above, the engineer find that the air deflector is damaged.
After the engineer replaces the damaged air deflector, the problem is solved.

Reference Information

If the operating temperature is excessively high, the normal functioning of the chips on the boards in the subrack are affected and bit errors occur.
The operating temperature of the subrack needs to be checked regularly even if no TEMP_OVER alarm is not reported on the T2000. This prevents excessively high operating temperature of the equipment in the subrack to ensure stable service operation.

How to do when Abnormal Optical Power Reporting Caused by the Coupling Exception

the R_LOF Alarm Is Reported in the Receive Direction on the Client Side When the Laser

In a WDM system with 1:N optical channel protection, the R_LOF alarm is reported in the receive direction on the client side when the laser on the LWC1 board in the protection channel is open.

Product

Fault Type

Optical Transponder Unit
R_LOF

Symptom

In the OptiX BWS 1600G system, the NE software version is 5.08.03.11. The networking topology is a chain: station A -> station B -> station C. Stations A and C are two OTM stations. The OCP board is used to provide 1:N optical channel protection.
One day, the boards in the SDH equipment interconnected with the LWC1 board in the OptiX BWS 1600G system reported the R_LOF alarm. Then, the receive and transmit optical power of this board was measured. The measurement result showed that the optical power was within the normal range. The MCA board was connected to the MON interface on the D40 board to test the optical signal-to-noise (OSNR) and optical power of the LWC1 board. The test result showed that the OSNR and optical power were also within the normal range.

Cause Analysis

A 1:N optical channel protection group uses a protocol to control protection switching (including the opening and closing of the laser). Normally, the laser in the protection channel of the LWC1 board is close.
The OCP is just an optical coupler. If 1:N optical channel protection is not switched and Laser Status at the client-side optical interface on the LWC1 board in the protection channel is Open, the optical signals in the working channels are coupled with those in the protection channel and thus abnormal optical signals are output. As a result, the SDH equipment fails to identify the output signals and the boards in the SDH equipment report the R_LOF alarm.

Procedure

  1. The boards in the SDH equipment report the R_LOF alarm. This alarm indicates that optical signals are received but the signals are abnormal.
  2. Connect an MCA board to the MON interface of the D40 board. Both the optical power and the OSNR of the LWC1 board are normal. This indicates that a wavelength is normally dropped from the main optical path to the D40 board.
  3. The OCP board connects the LWC1 board to the SDH equipment to provide 1:N optical channel protection. The LWC1-OCP-SDH equipment section may be faulty.
  4. Self-loop the two S16 boards and the two LWC boards. No abnormal alarm is reported. Therefore, the boards are normal.
  5. The OCP board may be faulty. Check the wavelength configuration of the 1:N optical channel protection group. The check result shows that the wavelength configuration is normal. Check the configuration of the LWC1 boards in the working and protection channels. The check result shows that Laser Status at the client-side optical interface on the LWC1 board in the protection channel is Open and Automatic Laser Shutdown at this interface is Disabled.
  6. 1:N wavelength protection switching is controlled by the protection protocol. Normally, the laser of the LWC1 board on the protection channel is shut down. The OCP is an optical coupler. If the protection channel is enabled, the OCP couples the optical signals of the working channel and the protection channel. When improper optical signals are output, the SDH equipment cannot identify the output optical signals and thus reports the R_LOF alarm.
  7. Set Laser Status at the client-side optical interface on the LWC1 board in the protection channel to Close and set Automatic Laser Shutdown at this interface to Enabled.

Result

The R_LOF alarm reported by the boards in the SDH equipment is cleared. That is, the problem is solved.

Friday, June 17, 2016

Mismatching Between MA Groups and Associated VCTRUNKs, Hence Causing the Binding Failure

IMA groups fail to be bound with associated VCTRUNKs. You need to configure IMA groups to match with associated VCTRUNKs.

Product

Fault Type

Configuration_Problem

Symptom

The principle of binding VCTRUNKs is met, but VCTRUNKS fail to be bound.

Cause Analysis

Mutual check relation exists between IMA groups and associated VCTRUNKs.

Procedure

  1. If IMA groups are symmetrically configured, make sure that the mapping VCTRUNKs are symmetrical.
  2. If VCTRUNKs are nonsymmetrical, make sure that the mapping IMA groups are nonsymmetrical.

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.

Thursday, June 16, 2016

VA4 Board Reports R_LOS When the Receiver Power Is Below -23 dBm Even If the Attenuation Is Decreased

The VA4 board reports the R_LOS alarm when the receiver power is below -23 dBm even if the attenuation of this VA4 board is decreased.

Fault Type

Abnormal Optical Power
Variable Optical Attenuator Unit
R_LOS

Symptom

The VA4 board (SSE1VA401) reports the R_LOS when the receiver power is below -23 dBm. But this VA4 board still decreases its attenuation at this time.

Cause Analysis

The R_LOS threshold of the VA4 board is -23 dBm. Thus, the board reports the R_LOS alarm when the receiver power is lower than or equal to -23 dBm. But the board is still able to decrease its attenuation according to its working principle after the alarm is generated.
When such a problem occurs, the customer often worries that the VA4 board may fail to function normally. To check whether the VA4 board can function normally when such a problem occurs, do as follows.

Procedure

  1. Query the optical power performance value (IOPCUR(dBm)) of the faulty optical interface on the VA4. Note that the value should be -60. The steps for querying the performance value is as follows:
    1. Choose Performance > Browse WDM Performance from the Main Menu. Click the Current Performance Data tab.
    2. In the Object Tree, select the VA4 board, and then click the double right arrow button.
    3. Configure Monitored Object Filter Condition, Monitor Period and Performance Event Type.
    4. Click Query to query the data on the NE.
  2. Perform the following operations to query the receiver power of the board interconnected with the VA4 board:
    1. In the NE Explorer, select the target board and then choose Configuration > Optical Power Management from the Function Tree.
    2. In the Object Tree, select the VA4 board, and then click the double right arrow button.
    3. Click Query to read the current optical power value from the NE. The Operation Result dialog box is displayed, indicating that the operation is successful.
  3. Adjust the attenuation of the VA4 board by 1 to 2 dB on the T2000 to check whether the VA4 board works normally. The steps are as follows:
    1. In the NE Explorer, select the desired board and then choose Configuration > WDM Interface from the Function Tree.
    2. Select By Board/Port(Channel).
    3. Select Channel from the drop-down list.
    4. Adjust the value of Attenuation Ratio (dB) on the Basic Attributes tab.

Result

The problem is solved after the examination is finished.

Analysis on the cause that the T2000 reports the OSC_RDI alarm in the case of a fiber break

In the case of a fiber break, if a user logs in to the same NE through different client computers, the OSC_RDI alarm is reported automatically because of alarm synchronization.

Fault Type

Optical Supervisory Channel Unit
OSC_RDI

Symptom

On one DWDM link, there are two OptiX Metro 6100 NEs, namely, NE A and NE B. NE A and NE B are connected to different T2000 clients.
One of the two fibers between NE A and NE B is broken. As a result, the SC1 board on NE B reports the R_LOS alarm, but no alarm is generated on NE A.
To check the optical power, the user exits from NE B on the T2000 connected to NE B, and then logs in to NE B remotely through NE A. In this case, both the T2000 client connected to NE A and the T2000 client connected to NE B report the OSC_RDI.

Cause Analysis

In general, automatic reporting of the OSC_RDI alarm is disabled by default. It is not reported unless the alarm synchronization function is enabled. Otherwise, the OSC_RDI alarm does not appear on the T2000 and thus is not reported. In this example, users from different T2000 clients have logged in to NE A. As a result, automatic synchronization of the alarms on the NE and the alarms on the T2000 is enabled. Thus, the NE reports the OSC_RDI alarm to the T2000.

Procedure

  1. In the case of a fiber break, do not log in to the same NE from two clients to prevent such a problem.

Result

The problem is solved after the operation is finished as the requests.