Wednesday, June 29, 2016

LPT Switching Fails Due to Inconsistency of LPT Bearer Mode

If the LPT bearer modes of the ports at both ends are inconsistent, LPT switching may fail. Hence, ensure that the LPT bearer modes of the ports at both ends are consistent.

Product

Fault Type

  • LPT
  • Fault in the Ethernet

Symptom

In the case of R006 or earlier versions, LPT fails to work normally when the EFS board interconnects with the EMS4 board. After the service at the SDH layer is disconnected, automatic switching can be normally performed at both ends. After the network cable is removed from an Ethernet port, automatic switching at the opposite end fails.

Cause Analysis

In the case of version R006 or earlier than R006, the LPT function of the EFS board supports the MAC bearer mode only whereas the EMS4 board supports the GFP bearer mode only. Hence, the EFS and EMS4 boards fail to interconnect with each other due to different LPT bearer modes after the LPT function is enabled.

Procedure

  1. Modify the LPT bearer modes of the ports at both ends to be the same.

Reference Information

In the case of R006 or earlier versions, do not interconnect the EFGS boards with the EMS4 boards after the LPT function is enabled.


How to Change the Link Type of an Interface?

RPR Network Interruption Due to Incorrect Fiber Connections

Incorrect fiber connections may result in RPR network interruption. In this case, connect the fibers correctly and re-configure the cross-connections.

Product

Fault Type

  • RPR
  • Ethernet fault

Symptom

The fibers are incorrectly connected. In this case, the RPR_NB_INCONSIS alarm is reported, which results in the RPR network interruption. Figure 1 shows incorrect fiber connections.
Figure 1 Incorrect fiber connections

Cause Analysis

The previous fault is caused due to incorrect fiber connections. In this case, ringlet0 receives packets from ringlet1 or ringlet1 receives packets from ringlet0.
As shown in Figure 1, the eastbound adjacent node of S2 is S3 but the westbound adjacent node of S3 is S1 rather than S2. Thus, the RPR_NB_INCONSIS alarm is reported.

Procedure

  1. Query the cross-connection configuration on each board to check whether there are cross-connections that are not completely configured on a board. Configure cross-connections from the Ethernet board to the SDH line board for each NE. See Reference Information.
  2. Check whether the fiber connections on the line board are correct. Connect fibers to make the input and output interfaces of the optical modules match. Figure 2 shows links between nodes. After fibers are connected properly, the alarm is cleared and the fault is rectified.
    Figure 2 Correct fiber connections

Reference Information

The steps of configuring Cross-Connections:
  1. In the Main View, select the desired NE. Right-click the NE and choose NE Explorer from the shortcut menu.
  2. Choose Configuration > SDH Service Configuration from the Function Tree.
  3. Click Create in the lower right of the window. The Create SDH Service dialog box is then displayed.
  4. Set the parameters in the dialog box as follows:
    • Level: VC-4
    • Direction: Bidirectional
    • Source Slot: 13-N2EGR2-1
    • Click . In the Please select the source timeslot dialog box, set the following parameters.
      • Port: 1
      • Higher Order Timeslot: 1,3,5,7,9,11,13,15
    • Sink Slot: 12-N2SL16-1(SDH-1)
    • Sink Timeslot Range: 1-8
    • Activate Immediately: Yes
    • Then, click Apply.
  5. Based on the operations in Step 4, set the parameters in the dialog box as follows:
    • Level: VC-4
    • Direction: Bidirectional
    • Source Slot: 13-N2EGR2-1
    • Click . In the Please select the source timeslot dialog box, set the following parameters.
      • Port: 1
      • Higher Order Timeslot: 2,4,6,8,10,12,14,16
    • Sink Slot: 7-N2SL16-1(SDH-1)
    • Sink Timeslot Range: 1-8
    • Activate Immediately: Yes
    • Then, click Apply.

Monday, June 27, 2016

The Client Equipment Interconnected with the TOM Board Reports the R_LOS Alarm Due to a Problem with the Optical Module on the TOM Board

The client equipment interconnected with the TOM board reports the R_LOS alarm due to a problem with the optical module on the TOM board.

Fault Type

Tributary Unit and Line Unit
R_LOS

Symptom

The SLQ4 board in the client equipment OptiX OSN 3500 interconnected with the TOM board in the OptiX OSN 6800 reports the R_LOS alarm. If you add an optical attenuator to the SLQ4 board, the alarm is cleared. In this case, the R_LOS alarm is reported again if you self-loop a client-side optical interface on the TOM board.

Cause Analysis

There is a problem with the client-side optical module on the TOM board.

Procedure

  1. Replace the client-side optical module on the TOM board to check whether the module is faulty. The R_LOS alarm, however, persists after the module is replaced. This indicates that the module is normal.
  2. Configure the bidirectional services between a client-side optical interface on the TOM board and the client equipment. In this case, the R_LOS alarm is cleared.
  3. Consult the R&D engineers. They explain that the client-side optical module on the TOM board reports the R_LOS alarm instead of the R_LOF alarm upon receipt of all "0"s or all "1"s signals if no service is configured for the module.

Result

To solve the problem, configure services for the client-side optical module on the TOM board.

Can I Directly Delete Inner VLAN IDs from QinQ Configuration?

  • If the switch is running V100R005 or an earlier version, one or more inner VLAN IDs in QinQ cannot be directly deleted. You must delete the current selective QinQ configuration, and then reconfigure the inner VLAN IDs that do not need to be deleted.
    For example, the port vlan-stacking vlan 10 to 20 stack-vlan 100 command is configured on the switch(such as S2309TP-EI-AC, S2309TP-EI-DC). To delete inner VLAN 15, perform the following operations:
    1. Run the undo port vlan-stacking vlan 10 to 20 stack-vlan 100 command to delete the current selective QinQ configuration.
    2. Run the port vlan-stacking vlan 10 to 14 stack-vlan 100 and port vlan-stacking vlan 16 to 20 stack-vlan 100 commands to reconfigure the inner VLAN IDs that do not need to be deleted.
  • If the switch is running a version later than V100R005, one or more inner VLAN IDs in QinQ can be directly deleted.

The TDX Board Reports the BUS_ERR Alarm When Cross-Connections Are Configured on the Board Because the Service Type of the Board Is Not Set

The TDX board reports the BUS_ERR alarm when cross-connections are configured on the board because the service type of the board is not set.

Fault Type

Electrical Cross-connection
Tributary Unit and Line Unit
BUS_ERR

Symptom

When the ODU2 cross-connections between the TDX and ND2 boards in the OptiX OSN 6800 on a network are configured, the boards report the BUS_ERR alarm.

Cause Analysis

This problem occurs when the input service type of the board is not set before cross-connections are configured on the board. The problem, however, does not affect the normal operation of the boards on the network.

Procedure

  1. Replace the TDX board to check whether it is faulty. The BUS_ERR alarm, however, persists after the board is replaced.
  2. Reseat the TDX board to check whether it is loose in its slot. The BUS_ERR alarm, however, persists after the board is reseated.
  3. Test the WDM-side signal rates of the TDX and ND2 boards. The test result shows that the WDM-side signal rate of the TDX board is 11.1 Gbit/s while that of the ND2 board is 10.7 Gbit/s. When the cross-connections between the TDX and ND2 boards are configured, the TDX board receives signals at a rate of 11.1 Gbit/s while the rate of the signals sent from the ND2 board is 10.7 Gbit/s. As a result, the boards report the BUS_ERR alarm. If the service type of the TDX board is set to STM-64, the TDX board receives signals at a rate of 11.1 Gbit/s and the problem is solved.

Result

Currently, only the TN12TDX, TN11TQX, TN11ND2, and TN12NS2 boards report the BUS_ERR alarm in the preceding case. These boards support ODU2 cross-connections.
Therefore, the input service type of the TDX board should be set before ODU2 cross-connections are configured on the board.

Sunday, June 26, 2016

Normal Boards Are Mistakenly Considered Faulty due to Optical Module Characteristics

Normal boards are mistakenly considered faulty due to optical module characteristics.

Fault Type

Others

Symptom

The TN1M1LOG01 board in the OptiX OSN 6800 on a network is tested on site. The input optical power at certain client-side interfaces on the board is about -12.5 dBm (the client-side receiver sensitivity is -17 dBm) or sometimes -60 dBm. In addition, the board keeps reporting the R_LOS alarm for seconds to ten minutes at these faulty client-side interfaces.

Cause Analysis

The SCP6F44-GL-BWE optical module is used on the client side of the TN1M1LOG01 board.
A fiber is used to self-loop the receive and transmit optical interfaces on this optical module and limit the input optical power of the module to a value that does not exceed the threshold. When the input optical power is high, the board does not report the R_LOS alarm. When the input optical power is low, the board keeps reporting R_LOS alarms. When the input optical power is within the normal range, R_LOS alarms are reported intermittently.

Procedure

  1. Ignore this problem. It does have any negative effect. The R_LOS alarm is not reported when normal signals are input to the client-side module on the TN1M1LOG01 board with the SCP6F44-GL-BWE optical module. The R_LOS alarm is reported only when unmodulated signals are input to the client-side module on the board.

Result

The problem is solved.

The Upgrade of Common Services to the ASON Services Fails Because a Client Service Is Available at the Network Layer

The upgrade of common services to the ASON services fails because a client service is available at the network layer.

Fault Type

ASON

Symptom

To use the ASON function on the OptiX OSN 6800 V100R003, the common services need to be upgraded to the ASON services. Select the OCh trail over which the services travel on the T2000 and then perform the upgrade. The upgrade, however, fails. This indicates that a client service is available on the OCh trail.

Cause Analysis

The OptiX OSN 6800 V100R003 supports only the optical-layer ASON solution and does not support the electrical-layer ASON solution. To ensure successful upgrade of the common services to the ASON services, all services on the OCh layer, such as client-side services, ODU1 services, and ODU2 services, must be deleted from the network layer.

Procedure

  1. Choose Trail > WDM Trail Management from the Main Menu on the T2000. In the displayed window, delete the client-side services on the OCh trail. Then, perform the upgrade. The upgrade is successful.

Result

The problem is solved. That is, the upgrade is successful.