Showing posts with label OSN 7500. Show all posts
Showing posts with label OSN 7500. Show all posts

Tuesday, August 15, 2017

What is the Protection Relationship among Huawei OSN Products?

TPS protection relationship of all Huawei OSN products is listed as follows:

Huawei OSN 7500:
E1/T1: A maximum of one group of 1:4 protection. Slot 1 protects Slots 2, 3, 7 and 18.
E3/D3/E4/STM-1e: A maximum of one group of 1:3 protection. Slot 18 protects Slots 2, 3 and 7. 

E1/T1: A maximum of one group of 1:8 protection. Slot 1 protects Slots 2–5, 13–16.
E3/D3/E4/STM-1e: A maximum of two groups of 1:3 protection. Slot 2 protects Slots 3, 4 and 5. Slot 16 protects Slots 13, 14 and 15. A maximum of two groups of 1:1 protection. Slot 2 protects Slot 3 and Slot 16 protects Slot 15.

Huawei OSN 2500:
E1/T: If slots are not split, there is a maximum of one group of 1:4 protection. Slot 5 protects Slots 6, 7, 12 and 13. If Slots 5, 6 and 7 are split, there are a maximum of two groups of 1:2 protection. Slot 5 protects Slots 6 and 7. Slot 19 protects Slots 20 and 21.
E3/D3/E4/STM-1e: A maximum of two groups of 1:1 protection. Slot 6 protects Slot 7, and Slot 13 protects Slot 12.

Huawei OSN 2500CRG:
The OSN2500CRG does not support TPS protection.

Huawei OSN 1500I:
E1/T1: If slots are not split, there is a maximum of one group of 1:2 protection. Slot 11 protects Slots 12 and 13. If Slots 11, 12 and 13 are split, there is a maximum of one group of 1:2 protection. Slot 1 protects Slots 2 and 3, Slots 6 protects Slots 7 and 8, and Slot 11 protects Slots 12 and 13.
E3/D3/E4/STM-1e: A maximum of two groups of 1:1 protection. Slot 12 protects Slot 13.

Huawei OSN 1500II:
E1/T1: If slots are split, there is a maximum of one group of 1:1 protection. Slot 2 protects Slot 12. 

Friday, April 1, 2016

How to Troubleshoot for SDH Clock

OptiX OSN 7500 II/OSN 7500/OSN 3500/OSN 1500 TroubleshootingHow to Troubleshoot for Huawei SDH Clock
When the network operates normally, the clock synchronization path is interrupted and the clock protection switching fails. As a result, a large number of pointer justifications occur on the related Nes.
If the clock protection switching is failed may cause pointer justifications and service interruptions.
Possible Causes
lCause 1: The fibers connections on the board are incorrect.
Cause 2: The configuration of the clock tracing mode of the NE is incorrect.
Cause 3: The configuration of the clock protection switching protocol of the entire network
is incorrect.
Cause 4: The configuration of the external clock source of the NE is incorrect.
Cause 5: The hardware is faulty.
Cause 6: The extended synchronization status message (SSM) protocol is disabled or the
clock ID of the clock source is absent.
How to Troubleshoot for SDH Clock
Step 1 Cause 1: The fibers connections on the board are incorrect. As a result, the protection switching fails.
1. See the protection principles to check whether the fibers connections at the faulty point are correct.
If the fibers connections are incorrect, then re-connect the fibers. Check whether the
services are restored. If the services are not restored, check whether the fault is due to other causes.
If the fibers connections are correct, then check whether the fault is due to other
causes.
Step 2 Cause 2: The configuration of the clock tracing mode of the NE is incorrect. As a result, the protection switching fails.
See the protection principles to check whether the clock tracing mode of the NE is correct.
If the configuration of the clock tracing mode of the NE is incorrect, then change the tracing mode of the clocks on the entire network. Check whether the services are restored.
If The configuration of the clock tracing mode of the NE is correct, then check whether the fault is due to other causes.
Step 3 Cause 3: The configuration of the clock protection switching protocol of the entire network is incorrect. As a result, the protection switching fails.
1. Check whether the related NEs are added to the clock protection subnets.
If certain NEs have not been added to the clock protection subnets, then add these NEs to the corresponding clock protection subnets. Check whether the
services recover.  If the services do not recover, proceed to the next step.
If all NEs have been added to the clock protection subnets, then proceed to the next step.
2. Check whether the clock protection switching protocol of related NEs is enabled.
If the clock protection switching protocol of certain NEs has not been enabled, Then enable the clock protection switching protocol of related NEs. Check whether the
services are restored. If the services are not restored, check whether the fault is due to other causes.
If the clock protection switching protocol of the entire network has been enabled, then check whether the fault is due to other causes.
Step 4 Cause 4: The configuration of the external clock source of the NE is incorrect. As a result, the protection switching fails.
1.Check whether the external clock source outputs clock signals.
If tThe external clock source does not output clock signals, then change the external clock source to make sure that the output of the clock signals is normal. Check whether the services recover. If the services do not recover, proceed to the next step.
If the external clock source outputs clock signals, then proceed to the next step.
2. Check whether the external clock source carries the SSMB information.
If the external clock source does not carry the SSMB information set the SSMB information manually. Then check whether the services recover.If the services do not recover, proceed to the next step.
If the external clock source carries the SSMB information, then proceed to the next step.
3. Check whether the external clock source is configured with the s1 byte correctly.
If the external clock source is not configured with the s1 byte correctly, then re-configure the s1 byte. Check whether the services are restored. If the services are not restored, check whether the fault is due to other causes.
If the external clock source is configured with the s1 byte correctly, then check whether the fault is due to other causes.
Step 5 Cause 5: The hardware is faulty. As a result, the protection switching fails.
1. Check the working state of the board.
2. Replace the faulty board.
3. Check whether the services are restored. If the services are not restored, check whether the fault is due to other causes.
Step 6 Cause 6: The extended SSM protocol is disabled or the clock ID of the clock source is absent.
1.Check whether the extended SSM protocol is enabled.
If the extended SSM protocol is disabled or the clock ID of the clock source is absent, then enable the SSM protocol and set the clock ID of the clock source. Check whether the services are restored. If not, check whether the fault is due to other causes.
If the extended SSM protocol is enabled or the clock ID of the clock source is specified, then check whether the services are restored. If not, check whether the fault is due to other causes.
—-End
Related Information
In the case of Huawei OSN clock protection, the direction of each NE clock source must match the fibers connections. That is, the eastbound/westbound fibers must be connected correctly. When the clock protection fails, check whether the fiber connections of each NE on the entire network match the settings of the clock source.
Telephone: 852-30623083
           Supports@Thunder-link.com            

Tuesday, March 8, 2016

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.

Telephone: 852-30623083
           Supports@Thunder-link.com            

Thursday, February 25, 2016

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:

More related:

IManager U2000 LCT Install Guide

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