Showing posts with label Huawei MSTP. Show all posts
Showing posts with label Huawei MSTP. Show all posts

Monday, July 24, 2017

Planning Transparently Transmitted EPL Services on Huawei OSN2500

The transparently transmitted EPL services can be used to plan the Ethernet services.

Service Requirement
Company A and company B at NE 1 need to transmit data services respectively to company A
and company B at NE 2. It is required that services of company A and company B are totally
isolated from each other. Both company A and company B provide 100M Ethernet electrical
interfaces. Company A requires 10M bandwidth and company B requires 45M bandwidth.

Networking Application
Services of company A and company B are required to be transparently transmitted between NE
1 and NE 2. Two OptiX OSN 2500 systems can be used as NE 1 and NE 2.

At NE 1, services from company A and company B are accessed respectively from Ethernet
ports. At NE 2, services from company A and company B are also respectively accessed from
Ethernet ports.
In the line, the EPL service from company A is carried by one VCTRUNK and the EPL service
from company B is carried by another VCTRUNK.

Application Scheme
Use the port routing scheme for the transparently transmitted EPL services.

Hardware Configuration
Configure one EFS4 for NE 1 and NE 2 to access Ethernet services from company A and
company B respectively.


Sunday, July 9, 2017

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.






Thursday, July 6, 2017

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

Monday, July 3, 2017

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.

Wednesday, June 14, 2017

Capabilities of Supporting Clocks on Huawei OSN2500

The clocks supported by the equipment and the clock protection are defined.

Basic Functions

Huawei OptiX OSN 2500 have the following functions:
Tracing of the external clock source, line clock source, tributary clock source and internal
clock source.
Non-SSM, standard SSM and extended SSM.
Clock working modes compliant with ITU-T G.781, such as locked, hold-over, and free
run.
Output of the line clock, tributary clock and external clock.
Tributary re-timing.
ASON clock tracing scheme.

Clock Protection

Huawei OptiX OSN 2500 can realize the clock protection switching in the following ways:
l Do not enable the SSM, and then perform the clock source selection and switching
according to the priority list. In this case, do not configure two clocks in two directions on
one NE into the priority list. Otherwise, the clocks form a loop.
l Enable the standard SSM mode, and then configure the priority list to ensure that the OptiX
OSN 2500 can automatically select the clock source with the highest priority to avoid the
locked loop.
l Enable the extended SSM mode. Use the fifth to eighth bits of the S1 byte to define the
quality of the clock source, and use the first to fourth bits of the S1 byte to define the clock
source ID. Thus, the clock loop can be avoided. The principles for setting the clock IDs are
as follows:
– All external BITSs should be assigned with clock IDs.
– In the case of nodes with external BITSs, the internal clocks of these nodes should be
assigned with clock IDs.
– In the case of nodes that access the chain or ring network to another ring network, the
clock sources of these nodes should be assigned with clock IDs.
– In the case of nodes that access the chain or ring network to another ring network, when
the clock tracing level includes the line clock source, the line clock sources accessed to

another ring network should be assigned with clock IDs.




Sunday, May 14, 2017

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,…




    Tuesday, May 2, 2017

    Generation and Detection of Alarms and Performance Events in the SDH Higher Order Signal Flow

    The principle for locating fault is "line first, then tributary; higher order first, then lower
    order".
    Therefore, this section focuses only on the alarms and performance events generated between
    Huawei SDH interface and the cross-connect unit during maintenance. This section describes the
    signal flow and the procedure for handling each overhead byte by each module.
    Alarm signals generated between the SDH interface and Huawei cross-connect unit
    Based on the positions of the various overhead byte processing in the STM-N (Huawei STM-64, STM-16, STM-4) frame, the overhead
    bytes are classified into four modules:

    • Regenerator section overheads
    • Multiplex section overheads
    • Higher order path overheads
    • Lower order path overheads

    If a fault occurs in the first two modules, it affects all the higher order paths. If a fault occurs in
    the overhead bytes of a higher order path, however, it affects only this higher order path and its
    lower order paths.
    The following sections describe the signal flow and the processing of each overhead byte.
    Downlink Signal Flow
    In the higher order downstream signal flow, overhead bytes are extracted and terminated.
    Frame Synchronizer and Regenerator Section Overhead Processor
    Multiplex Section Overhead Processor
    Pointer Processor and Higher Order Path Overhead Processor
    Uplink Signal Flow
    The overhead bytes are extracted and then terminated in the downlink signal flow of the higher
    order path. Overhead bytes are generated and alarm signals are returned to the opposite NE in

    the uplink signal flow of the higher order path.

    Thursday, April 27, 2017

    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.

    Tuesday, April 18, 2017

    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.

    Tuesday, March 28, 2017

    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)

    Tuesday, March 14, 2017

    Is it really not possible to add a protection leg to an existing MSP 1 to N?

    Issue Description
    It is not possible to add a protection leg to an existing MSP 1:N.
    Alarm Information
    There is not any "modify button".
    Handling Process
    As it is not possible to modify, if you need to add a protection leg you have to delete the MSP 1:1 and then to recreate again adding the new leg to the protection.
    Root Cause
    MSP 1:N has been create in this way. You only can create and delete it.
    Suggestions
    If a MSP 1:N exist and you want to add other board, you have to delete the MSP and then create it again (including new board) instead of be able to add the board directly (customer has to spend more time deleting and creating again than if he would able to add directly but this function works in this way).


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

    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

    Wednesday, March 8, 2017

    U2000WebLCT start normally but it does not login

    Issue Description

    It is necessary to do some test on a Huawei RTN620. It use the U2000WebLCTV100R005C00SPC400. The U2000WebLCT start normally, you enter the admin and password and when you try to login (click login) the windows closed itself.

    Alarm Information
    None

    Handling Process
    Copy the address which appear on the Internet Explorer when the U2000WebLCT is started (http://localhost:13002/weblct/page/login.html) and then open other internet navigator (like Mozilla Google chrome) and copy this address on this navigator. Then enter the U2000WebLCT user and password in this new page and you can login.

    Root Cause
    The U2000WebLCT use the internet navigator like an interface. It open in the internet navigator the laptop as configured that main internet navigator. In this case the U2000 WebLCT is open on a Internet Explorer 8. Its seem that U2000WebLCT does not support Internet Explorer 8.

    Suggestions
    Open the U2000WebLCT with Mozilla or Google Chrome interner navigator.

    The most popular Huawei S2700EI switch as below:

    LS-S2700-9TP-SI-AC

    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