OptiX OSN 8800 Tributary SNCP Defect on TN54THA and TN53TSXL

Summary: The NE software V100R008C10SPC200 does not support hardware tributary subnetwork connection 

protection (SNCP) on the TN54THA and TN53TSXL boards. To be specific, a TN54THA or TN53TSXL board equipped 

with hardware tributary SNCP will insert an incorrect s-code to the cross-connect board on the NE. As a result, the 

cross-connect board will report a HARD_BAD alarm, affecting services on the NE.

Product Line: Transport network product line                             Product Family: WDM products

Product Model: OptiX OSN 8800 V1R008C10SPC200

[Problem Description]

Trigger conditions:

The NE software version is V100R008C10SPC200.

Hardware tributary SNCP has been configured on RX/TX ports 9–16 of a TN54THA board or the RX/TX port of a TN53TSXL board on the NE. 

Hardware tributary SNCP is newly configured on RX/TX ports 9–16 of a TN54THA board or the RX/TX port of a TN53TSXL board on the NE. 

The cross-connect board on the NE is TN16UXCM, TN52UXCH, TN52UXCM, TNK2USXH, or TNK2UXCT. 

During NE expansion, the cross-connect boards on the NE are upgraded from TN16XCH, TN52XCH, TN52XCH02, TNK2SXH, TNK2XCT, TNK4SXM, 

TNK4SXM, or TNK4XCT to TN16UXCM, TN52UXCH, TN52UXCM, TNK2USXH, or TNK2UXCT. 

When conditions 1, 2, and 5, or conditions 1, 3, and 4 are met, the NE will report a HARD_BAD alarm.

Symptom:

The NE reports a HARD_BAD alarm and services on the NE are affected.

Identification method:

Conditions 1, 2, and 5, or conditions 1, 3, and 4 are met, and the NE reports a HARD_BAD alarm. The alarm parameters 

are as follows: 0xf,0x5,0xa,0xff,0xff,0xff.

[Root Cause]

The OptiX OSN 8800 V100R008C10SPC200 does not support hardware tributary SNCP on the TN54THA and TN53TSXL boards. 

If hardware tributary SNCP is configured on a TN54THA or TN53TSXL board, array violation will occur on the board, causing the 

board to insert an incorrect s-code to the cross-connect board on the NE. As a result, bit changes occur on the chip page of the 

cross-connect board. Consequently, the cross-connect board reports a HARD_BAD alarm. 

[Impact and Risk]

The network expansion is affected. When common cross-connect boards are upgraded to U-series cross-connect boards, the HARD_BAD alarm will be reported, and the tributary SNCP services on the TN54THA or TN53TSXL boards will 

be interrupted.

If U-series cross-connect boards are already used, the HARD_BAD alarm will be reported when tributary SNCP services are created. As a result, the 

new services cannot be provisioned but the existing services are not affected. 

The existing tributary SNCP services are not affected in non-expansion scenarios.

[Measures and Solutions]

Recovery measures:

In expansion scenarios, use the NE software V100R008C10SPC300 instead of V100R008C10SPC200. 

If tributary SNCP services fail to be created on the NE software V100R008C10SPC200, upgrade the NE software version to 

V100R008C10SPC300 or later.

Workarounds:

If tributary SNCP services are configured for the TN54THA or TN53TSXL board on an NE, use NE software V100R008C10SPC300 or 

later instead of V100R008C10SPC200. 

Preventive measures:

If tributary SNCP services are configured for the TN54THA or TN53TSXL board on an NE, use NE software V100R008C10SPC300 or 

later before capacity expansion.

Contact information:

Telephone: 852-30623083

Email: Sales@Thunder-Link.com

           Supports@Thunder-link.com            

Website: http://www.thunder-link.com

More related:

Introduction to MSTP_Prelude_Overview and History

How To Reset Huawei OLT MA5600T Series Equipment Password

Implementation of TR069 protocol in MA5600 series

Optical attenuation is too large lead to ONU recovery failure

Ethernet Basics_GFP, VCAT, and LCAS-V1.0

How to Modify the NE Attributes on Huawei SDH part 2

4 Modifying GNE Parameters

During the network optimization and adjustment, you may need to change the GNE type or modify the communication address.

Prerequisites

You must be an NM user with NE maintainer authority or higher.

Step 1Choose System > DCN Management from the Main Menu. Click the GNE tab.

Step 2 Select the GNE to be modified, right-click and choose Modify GNE from the shortcut menu.

Step 3In the Modify GNE dialog box displayed, set Gateway Type .

NOTE

Do not modify the Port No..

Make sure that the IP address of the GNE is in the same network segment as the IP address of the U2000. If they are not in the same network segment, set the corresponding network ports, to make sure that the U2000 can log in to the GNE.

Step 4 Click OK. In the Operation Result dialog box that is displayed, click Close.

----End

5 Changing the GNE for NEs

When the GNE that the non-gateway NE belongs to is changed and this non-gateway NE does not belong to another GNE, you need to change the GNE to maintain the communication between the NEs and the U2000. Alternatively, if a GNE manages more than 50 NEs, change the GNE for some NEs so that the communication between the U2000 and the NEs is not affected.

Prerequisites

You must be an NM user with NE maintainer authority or higher.

Procedure

Step 1 Choose System > DCN Management from the Main Menu.

Step 2 Click the NE tab.

Step 3 Select an NE. Double-click the Primary GNE1 field and select a GNE from the drop-down list.

Step 4 Click Apply. Click Close in the Operation Result dialog box.

Step 5Click Refresh.

----End

Customers interested in purchasing huawei SDH or the price, please refer to below links:

OSN6800

OSN1500

OSN8800

More related:

IManager U2000 LCT Install Guide

Import or Update U2000 License

How to precaution the using problem of Huawei MA5603T product?

NE Configuration Loss Due to Disabling of the Automatic and Periodic Database Backup Functions on MSTP Products

How to Modify the NE Attributes on Huawei SDH part1

Modifying NE Attributes of Huawei Transmission, there are several things you should do:

1 Modifying the NE ID

The ECC protocol uses the NE ID as the unique identifier of an NE. The U2000 also uses the NE ID to identify different NEs in the user interface and databases, and uses the NE ID as the key word in searches. Hence, you need to assign a unique NE ID to each NE when planning a network. If an NE ID conflicts with another NE, it results a collision in the ECC route. As a result, it becomes difficult to manage some NEs. In the commissioning or expansion process, when you need to adjust the original planning and modify the NE ID, you can use the U2000 to achieve it. In the case of the OptiX OSN equipment, if the IP address of the system control board is not set, the IP address changes with the NE ID. If the IP address is set once, however, the IP address does not change with the NE ID.

Prerequisites

You must be an NM user with NE operator authority or higher.

The NE must be created.

The steps:

Step 1In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function Tree.

Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed.

Step 3Enter the New ID and the New Extended ID. Click OK.

Step 4 Click OK in the Warning dialog box.

----End

2 Modifying the NE Name

You can modify the NE name as required. This operation does not affect the running of the NE.

Prerequisites

You must be an NM user with NE operator authority or higher.

Step 1 In the NE Explorer, click the NE and choose Configuration > NE Attribute from the Function Tree.

Step 2 In the NE Attribute dialog box, enter a new NE name in Name. Click Apply. A prompt appears telling you that the operation was successful.

NOTE

An NE name can contain a maximum of 64 letters, symbols, and numerals, but cannot contain the following

special characters: | : * ? " < >.

Step 3 Click Close.

----End

3 Deleting NEs

If you have created a wrong NE, you can delete the NE from the U2000. Deleting an NE removes all information of the NE from the U2000 but does not affect the running of the equipment.

Prerequisites

You must be an NM user with NE maintainer authority or higher.

Context When the NE is not logged in, you can delete the NE on the U2000.

NOTE

If an NE is deleted, the links related to the NE are also deleted.

The steps:

Delete a single SDH NE

1. Right-click the NE on the Main Topology and choose Delete > Delete NE from the

shortcut menu. The Confirm dialog box is displayed.

2. Click Yes. The Delete Device Results dialog box is displayed.

3. Click Close, The NE icon is deleted from the Main Topology.

Delete NEs in batches

1. Choose Configuration > NE Configuration Data Management from the Main

Menu. The NE Configuration Data Management window is displayed.

2. In the left-hand pane, select multiple NEs and click . The Configuration Data

Management List pane displays the configuration data of all the selected NEs.

3. Select the NEs to be deleted, right-click and choose Delete from the shortcut menu.

The Delete the NE dialog box is displayed.

4. Click OK.

----End

OSN 500 aslo works for this configuration.

More related:

IManager U2000 LCT Install Guide

Import or Update U2000 License

How to precaution the using problem of Huawei MA5603T product?

NE Configuration Loss Due to Disabling of the Automatic and Periodic Database Backup Functions on MSTP Products

Huawei Launches the World’s First Fully Outdoor WDM Product

Carrying LTE/LTE-A CPRI services and helping to drive down network costs, making baseband unit cloud a reality
Huawei released the world’s first fully outdoor Wavelength-division multiplexing (WDM) product at a TDC and Huawei joint global WDM/OTN seminar themed ‘Simplified Network for a Better Experience’. Used for carrying LTE/LTE-A common public radio interface (CPRI) services, the product helps drive down the costs of network deployment and operations and maintenance, realizing the baseband unit cloud (BBU Cloud).
In order to reduce site leasing fees and centrally manage base station resources, carriers are beginning to adopt the BBU Cloud as the mainstream networking mode. To date, the baseband units (BBUs) have been collectively deployed in the integrated central office, and remote radio units deployed at the coverage points. The BBUs then work with the remote radio units through CPRIs to extend the service transmission distance. Usually, the CPRI services are transmitted through connected optical fibers. This type of networking mode consumes optical fiber resources and has low reliability. In addition, there are no supervisory measures for managing fibers, making maintenance difficult.
The fully outdoor Huawei WDM product replaces optical fiber connections with WDM technology. This results in a pair of optical fibers able to withstand more than 100 pairs of CPRI services. Also, the Huawei product reduces network investment and shortens service deployment time, providing a highly reliable network by using a unique delay compensation technology. The product also supports remote performance monitoring and uses a network management system to precisely locate faults. To ensure it is suitable for outdoor use it has a compatible design, supporting 614 Mbit/s to 9.8 Gbit/s (CPRI1-CPRI7) service on the client side. This specific design provides a product suitable for covering high-density and large-capacity metropolitan areas.
Huawei WDM/OTN series end-to-end intelligent optical transport platforms are applicable to the backbone core layer, metropolitan core layer, metropolitan aggregation layer, and metropolitan edge access layer. Thunder-link.com wholesales Huawei WDM products, include Huawei OSN 6800, Huawei OSN 8800. Get the best price Huawei WDM products from Thunder-link.com, ships to worldwide.
As world famous Huawei product supplier – Thunder-link.com, focuses on Huawei products and solutions, we are very experienced in this area. Most Huawei products are complicated, technical support may required at any phase of project, work with a professional supplier like Thunder-link will make your project secured.
It’s referenced from:
http://pr.huawei.com/en/news/hw-427431-cpri.htm#.VUw29iKUcUg