How to Plan Orderwire Phone Interfaces on Huawei Optix OSN2500?

Capability of Supporting Orderwire Phone Interfaces

The capability of supporting orderwire phone interfaces is defined.
The Q1SEI board of the Huawei OptiX OSN 2500 provides one orderwire phone interface, two NNI
voice interfaces and two NNI signaling interfaces. The five interfaces are all of the RJ-45 type.

Planning Principles

The principles for planning the orderwire phone interfaces are defined.
Adhere to the following principles when planning orderwire phone interfaces:

• Make sure that the orderwire signaling is compatible in the entire network.
• Make sure the orderwire phone number of each node is of the same length. It is recommended that the orderwire phone number be set as four characters.
• Set the orderwire phone number in the format: subnet number (one character) + user number (three characters).
• Make sure that the conference phone numbers in the entire network are the same and the number should be larger than the orderwire phone number. It is recommended that the conference phone number be set to 9999.
• Make sure that all orderwire phone numbers in the entire network, except the conference phone number, are unique.
• Make sure that the dial-up scheme of the orderwire phone of each node is dual-tone multifrequency.
• Make sure the call waiting time of each node is the same. If less than 30 nodes are present in the network, set the call waiting time to 5s. If more than 30 nodes are present in the network, set the call waiting time to 9s.
• The orderwire phone number should increase as the node ID increases.
• Consider the possibility of howl in the orderwire loop. Release the loop to solve the problem of howl in the conference phone. The loop is automatically released, if an OptiX OSN 2500 system is networked with other OptiX OSN 2500 systems, or with Huawei OptiX OSN 7500, OptiX OSN 3500, OptiX OSN 3500T, OptiX OSN 2500REG and the OptiX OSN 1500. If the OptiX OSN 2500 is networked with other equipment, manually release the loop.
• If no optical path is available between two nodes, which, however, require orderwire communication, use the orderwire NNI connection for the orderwire communication. Use Voice 1 or Voice 2 as the voice interface, and Serial 3 or Serial 4 as the data interface for the orderwire NNI connection.

Planning Example

An example is given to show how to plan the orderwire phone interfaces.

Set the orderwire phone number as four characters, with the last two characters being the same

as the node ID. The conference phone number has four characters and is 9999.

Planning the TPS Protection for the STM-1 Electrical Interface Service Boards

Capabilities of Supporting the TPS Protection for the STM-1 Electrical Interface Service Boards

The N1SEP, the STM-1 service board for Huawei OptiX OSN 2500, supports two 1:1 TPS protection groups.

Planning Principles
When planing the TPS protection for the STM-1 electrical interface service boards, follow the
basic principles.
Adhere to the following principles when planning the TPS protection for the STM-1 electrical
interface service boards.
Determine whether to configure the TPS according to the importance of the services.
When the N1SEP1 board works with the interface board to provide optical interfaces, choose the N1SEP.
When configuring the TPS protection group for the STM-1 electrical interface service
board, choose the N1SEP as the processing board, N1EU08 or N1EU04 as the interface
board, and N1TSB8 or N1TSB4 as the switching and bridging board.
When the slot for the protection board is slot 6, the slot for the working board is slot 7.
When the slot for the protection board is slot 13, the slot for the working board is slot 12.

Planning Cases
A case is given to show how to plan the TPS protection for the STM-1 electrical interface service boards.
TPS configuration for Huawei STM-1 electrical interface service boards

Port resource report doesn't show all subnets in U2000 NMS

Issue Description

The version of the U2000 is  V100R006C00SPC200
On menu Inventory -> Huawei SDH Report -> Port Resource Report we can't see all subnets like in the Main Topoly tab as the pictures below:
In the Main Topology tab, we can see all subnets:

On the other hand, in the Port Resource Report tab, we can't see all subnets.
We can see only 8 subnets:

Handling Process

This is a bug of the software.
To solve this problem is necessary to upgrade from the Huawei U2000 V100R006C00SPC200 version to V100R006C00SPC300 version.

NE datacollector in U2000 V1R1 does not working

Issue Description

we are U2000 Version : U2000V1R1C00CP311 to manage Huawei OSN3500 and OSN7500 , and we found that the NE Datacollector Does not working
The problem phenomenon as follow ( we have 2 problems ) :
1.  After select the NE Datacollector from the OSN function tree , we could not login the the OSN NE in the NE data collector as showed in the b/m print screen

2.  After select the NE datacollector from OSN Function tree, we couldn't find Huawei OSN NE in the Datacollector ( OSN NE not exist to select Login ) .

Alarm Information

Null

Handling Process

1.  check if this problem in one NE or all NEs over the U2000 .
2.  check the U2000 System monitor process (espcially : neproxy process ) .
3.  get these logs and sent it to GTAC :

    *  D:/U2000/server/tools/datacollector/dbfile/Datacollector.db
    *  D:/U2000/Client/Tools/neinfo.xml

4.  check the Set Login account and check the Operated and fixed Users .
5.  Check the Upper limit of creation from the datacollector logs if it reach to be 50 (the max ) let us use the temp solution till upgrade the U2000 version to be U2000 V1R2C01SPC100

Root Cause

For Problem # 1

This problem is due to when your user login, other user resave it, then make this user logout.
Pls check NE--->set login Account, and check whether there has the same user set in this table, if yes, pls change fixed user to other login user.  See following picture:

IF the problem still exist we need to restart the Process of neproxy process from U2000 System monitor
For Porblem # 2  : According to the Logs of the Datacollector we find that : 

we find that : the creation NEs of Datacollector is  already reach the upper limit 50
so we need to upgrade current U2000 version to be U2000 V1R2C01SPC100 or use Temp solution as follow :

we can use the new (Datacollector.db) which supprot more 50 NE and replace the new (Datacollector.db) file in path

Suggestions

1.  check all the U2000 system monitor .
2.  check the Set Login account in the Datacollector .
3.  Use the Temp solution (use the new (Datacollector.db)) if you cannot upgrade the U2000 to be: U2000 V1R2C01SPC100
4.  U2000 V1R2C01SPC100 of Higher version solves this problem.

Basic Principles and Planning NE IDs of Planning the DCN

When constructing the DCN, select proper communication protocols according to the actual
networking situation, and follow the planning principles.
The principles for planning the DCN are as follows:

• When Huawei OptiX OSN 2500 constructs a network with other Huawei equipment, the HWECC or IP over DCC protocol is recommended. Use the same communication protocol in the entire DCN network.
• When the OptiX OSN 2500 constructs a hybrid network with equipment from other vendors, use the IP over DCC or OSI over DCC protocol according to the protocol supported by the equipment from other vendors.
• The OptiX OSN 2500 constructs a hybrid network with equipment from other vendors. In this case, if the equipment from other vendors do not support the IP over DCC or OSI over DCC, use the DCC bytes or the Ethernet service channels to transparently transmit the management information.
• When a communication protocol is used to construct the DCN network, properly set the DCN network scale and divide the network according to the network situation. Thus, the effect of large network scale on the DCN network can be reduced.
• The DCN network should be of the ring type to ensure the reliability of the network communication. Thus, route protection can be provided when fiber cuts or NE abnormalities occur. If fibers of the equipment cannot form a ring, extra DCN channels should be constructed to form a ring, and thus the route protection function can be realized.

NE IDs are used to identify Huawei transmission equipment. Thus, the NE IDs should be

configured when the DCN network uses the HWECC, IP over DCC, and OSI over DCC

protocols.

The principles for planning the NE IDs are as follows:

• The ID of each NE should be unique.
• In the same DCN network, the ID of each NE should be unique.
• An NE ID is 24 bits in binary, which can be divided into the former eight bits and the latter 16 bits.

– The former eight bits indicate the extended ID (the default value is 9), also called the subnet number, which identifies different subnets. The subnet number cannot be 0 or 0xFF (255 in decimal).

– The latter 16 bits indicate the basic ID. The value of the basic ID cannot be 0 or 0xBFF0(49136 in decimal), or be greater than 0xBFF0.

In the ring network, the NE IDs should be increased one by one in the same direction along

the ring network.

A complex network should be divided into rings and chains. First set IDs for NEs on the

ring from 1 to N, and then set the IDs for NEs on the chain as N+1, N+2,…

Planning the Optical-Path-Shared MSP

Capabilities of Supporting the Optical-Path-Shared MSP

When planning the optical-path-shared MSP for Huawei OptiX OSN 2500, first consider the
capabilities of supporting the optical-path-shared MSP.
In the case of the optical-path-shared MSP, one optical interface can be configured into two
MSP groups. Thus, multiple MSP rings can share the same fiber and optical interface.
The OptiX OSN 2500 supports the configuration of the optical-path-shared MSP.
l The SF16 and SL16 boards can process two sets of K bytes, which are located in the first
and fifth STM-1s. The SF16 and Huawei SL16 boards support configuring a single optical interface
into a maximum of two MSP rings.

Planning Principles

To rationally and effectively plan the optical-path-shared MSP protection, the planning
principles should be followed.

In normal situations, in the case of the optical-path-shared MSP, two low-rate line units share
the same high-rate line unit.

In the optical-path-shared MSP, two line STM-16 units at the same rate can share the same line unit.

When the optical-path-shared MSP is configured, on the protection ring, the optical interfaces

in two directions need not be configured into paired slots.

Planning the 1+1 &1:N Linear MSP on Huawei Optix OSN2500

Capabilities of Supporting the 1+1 Linear MSP

When planning the 1+1 linear MSP for the OptiX OSN 2500, first consider the capabilities of
supporting the 1+1 linear MSP.
In the case of Huawei OptiX OSN 2500, the capabilities of supporting the 1+1 MSP are as follows:

• The OptiX OSN 2500 supports the 1+1 MSP at the STM-64, STM-16, STM-4, and STM-1
• levels.
• An OptiX OSN 2500 system supports a maximum of 12 1+1 linear MSP groups.
• The switching and bridging mode supports the single-ended and dual-ended switchings.
• The switching revertive mode supports the revertive mode and non-revertive mode.

Planning Principles
To rationally and effectively plan the 1+1 linear MSP, the planning principles should be
followed.

Adhere to the following principles when planning the 1+1 linear MSP.

• Do not use different optical interfaces on one multichannel optical interface board to form,1+1 protection group. Otherwise, the protection function is unavailable when the board fails.
• The switching and bridging mode should be set to the single-ended switching.The switching revertive mode should be set to the non-revertive mode.
• It is recommended that you set the B2_SD as the trigger condition of the linear MSP ring protection switching.

Capabilities of Supporting the 1:N Linear MSP
When planning the 1:N linear MSP for the OptiX OSN 2500, first consider the capabilities of
supporting the 1:N linear MSP.
The OptiX OSN 2500 supports the 1:N linear MSP at the following levels:

• 1:N (1≤N≤14) linear MSP at the STM-16 level
• 1:N (1≤N≤14) linear MSP at the STM-4 level
• 1:N (1≤N≤14) linear MSP at the STM-1 level

In the case of the OptiX OSN 2500, the capabilities of supporting the 1:N linear MSP are as
follows:

• An OptiX OSN 2500 system supports a maximum of 12 1:N linear MSP groups.
• The switching and bridging mode is the dual-ended switching.
• The switching revertive mode is the revertive.

Planning Principles
Adhere to the following principles when planning the 1:N linear MSP.

• Do not use different optical/electrical interfaces on the same multichannel optical/electrical interface board to form a 1:N protection group. Otherwise, the protection function is unavailable when the board fails.
• In the 1:N protection scheme, the protection route can carry extra services, but the extra services cannot be protected.
• It is recommended that you set the WTR time of the linear MSP ring to 600s.
• It is recommended that you set the B2_SD as the trigger condition of the linear MSP ring protection switching.

Situation When Carry 10GE Traffic On OSN3500

Now more and more 10GE level transmission requirement, the traditional way, also the only way is to use EAS2 board to access 10GE traffic from Router, and Cross-Connect to STM-64 line board to transit out, the problem for this solution is, too high cost the EAS2 board is.
Now another way is, upgrade your Huawei OSN3500 to hybrid version, add another package domain to access and transit data service, picture as below:

How it works

A unified network for 2G/3G/leased line etc,  including Huawei SDH/PDH, ATM/IMA or Eth transport, Single Team Management.

Just One kind of box with different service boards for various application, Continually Saving Opex

Huawei OptiX OSN 2500 Supporting Tasks of Software Loopback

Outloop
The SDH optical interface board, PDH electrical interface board, Ethernet interface board like Huawei EGS4  and ATM board all support outloop.

Inloop
The SDH optical interface board like Huawei SLD64, PDH electrical interface board, Ethernet interface board and ATM board all support inloop

Loopback at an SDH Interface
Prerequisites
You must be an NE user with "NE and network operator" authority or higher.
To test whether the interface module and external cables of a board are normal, you need to set
an outloop.
To test whether the cross-connect unit and service path of the equipment are normal, you need
to set an inloop.
Impact on Services
In the case of non-protection, the loopback may interrupt the services or the communication
signals.
Tools/Instruments
T2000
Procedure
Step 1 In the Main Topology of the T2000, select the NE to be looped back.
Step 2 Right-click the NE icon in the Main Topology and select NE Explorer.
Step 3 Select the board from the Object Tree and select Configuration > SDH Interface from the
Function Tree.
Step 4 Select By Function. Select Optical (Electrical) Interface Loopback.
Step 5 Select the port and select the loopback mode Inloop or Outloop.
Step 6 Click Apply. The confirm dialog box is displayed. Click OK.
Step 7 The Operation Result dialog box is displayed and indicates that the operation is successful.
Click Close.
This article works for Huawei OptiX OSN 2500 (V100R008)

How to Troubleshoot the Pointer Justification on Huawei OptiX OSN 2500?

A pointer justification event means that some NEs are not completely synchronized in Huawei SDH
network equipment. If only a pointer justification event occurs, the services are not affected. To enhance
the transmission network stability, however, you need to find out the causes and eliminate the
pointer justification event.

Mechanism of Pointer Justification
Pointer justifications occur when the clocks between the NEs are not fully synchronized.
In an SDH network, there are two kinds of pointers: administrative unit pointer (AU-PTR) and
tributary unit pointer (TU-PTR). There are two corresponding pointer justifications, AU pointer
justification and TU pointer justification. The generation mechanism of these two kinds of
pointer justification is mostly the same. For details, see Chapter 1 "Generation of Alarm and
Performance" of Huawei OptiX OSN 2500 Intelligent Optical Transmission System Alarms and

Performance Events Reference.

Generation Mechanism of AU Pointer Justification
the E1 service between NE1 and NE6 passes through the intermediate NEs at
the VC-4 level. NE1 is the clock source, and the other NEs trace the clock signal of NE1
westwards. If the clocks of NEs 2 and 3 are not synchronous, the east optical board of NE2 and
the west optical board of NE3 generate the AU pointer justifications. These justifications may
cause the west optical boards of NEs 1, 4, 5 and 6 to generate pointer justifications.
If the clock of NE2 runs faster than that of NE3, the east optical board of NE2 executes the
AU positive pointer justification. At the same time, the west optical board of NE3 executes
the AU negative pointer justification.
If the clock of NE2 runs slower than that of NE3, the east optical board of NE2 executes
the AU negative pointer justification. At the same time, the west optical board of NE3

executes the AU positive pointer justification.

Detection Report of Pointer Justification
The location where AU pointers are generated and reported is different from that of TU pointers.
When a local station generates an AU pointer justification, it neither detect nor report the AU
pointer justification. Instead, this station transmits the pointer justification information to the
remote station through the H1 and H2 bytes. The remote station will report the event of the AU
pointer justification by interpreting the H1 and H2 bytes. Therefore, in remote detection mode,
if the remote station reports the AU pointer justification event, it means that the pointer

justification is generated in the local station.
Fault Locating Flow
The clock out-of-synchronization is the primary cause of pointer justification. Locate faults
mainly by handling problems related to the clocks. The fault should be located based on the
service direction, clock tracing direction, detection report location of pointer justification and

the generation location of pointer justification.

a: The first station refers to the station that first reports the pointer justification in the service direction, which is the same as the clock direction, that is, in the clock tracing direction.

b: The first station has no AU pointer justification, that is, it only has the TU pointer justification. You should handle the problem of TU pointer justification.

U2000 Product (V1R6C02) reports the “error” The matching NE Explorer is not found”, when I create new Huawei OSN 3500

Issue Description

The U2000 shows the “error dialog” The matching NE Explorer is not found ”, when I create new Huawei OSN 3500 on the U2000.

Alarm Information

The matching NE Explorer is not found

Handling Process

1． First, checking the license information, to see whether it supports the operation of creating Huawei OSN 3500. I found that the license is no problem. The license information like the below page:

2.   Second, checking the background process of U2000

       1). I found that all the process we can found through U2000 System monitor is normal.

       2). Then, I telnet to the U2000 server and reboot the server process

                 The command like below:

                       Switch to the destination path: cd /opt/OSSENGR/engineering

                       Stop the server:  ./stopserver.sh

                       Start the server:  ./startserver.sh

                 Then I create the OSN 3500 again, but the problem still exist. The NE 

can’t be created.
        3). Lastly, I login in the U2000 NMS Maintenance
                     I compare the instance with my PC U2000 Server, I found that there is lack of NEMGR_SDH instance.
                   
So, I deploy the deployment package and add the NEMGR_SDH instance.
The problem is resolved; I can create the OSN 3500 normally.

Root Cause

1． Maybe the license was not support the NE.
2． Maybe the related background process of U2000 did not start.
3． Maybe the deployment packages were not deployed

Suggestions

No

How to Troubleshoot for SDH Clock

OptiX OSN 7500 II/OSN 7500/OSN 3500/OSN 1500 Troubleshooting：How 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.

Contact information:

Telephone: 852-30623083

Email: Sales@Thunder-Link.com

           Supports@Thunder-link.com            

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

More related:

MA5600T Series Networking Protection Feature
MA5600T Series Maintenance Feature Glance
MA5600T&MA5603T&MA5608T 10G GPON Feature Glance
How to Configure the H.248-based Voice Service?
How to Login Huawei Equipment Through the Local Serial Port