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

Thursday, April 13, 2017

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

Tuesday, March 14, 2017

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

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            

Thursday, March 31, 2016

Huawei OptiX OSN 2500 Review

Network Application


The OptiX OSN 2500 intelligent optical transmission system (hereinafter referred to as the Huawei OSN 2500) developed by Huawei is the next-generation intelligent optical transmission equipment.
The OptiX OSN 2500 integrates the following technologies to transmit voice and data services on the same platform with high efficiency:
  • Synchronous digital hierarchy (SDH)
  • Plesiochronous digital hierarchy (PDH)
  • Ethernet
  • RPR(Resilient Packet Ring)
  • Asynchronous transfer mode (ATM)
  • Storage area network (SAN)
  • Wavelength division multiplexing (WDM)
  • Digital data network (DDN)
  • Automatically switched optical network (ASON)
  • Microwave Technology

Appearance of the OptiX OSN 2500


appearance-of-the-optix-osn2500

The OptiX OSN 2500 is used at the access layer and the convergence layer of a metropolitan area network (MAN). The OptiX OSN 2500 can also be networked with the following equipment to optimize the investment for customers:
  • OptiX OSN 9500
  • OptiX OSN 7500
  • OptiX OSN 3500
  • OptiX OSN 3500 II
  • OptiX OSN 2500 REG
  • OptiX OSN 1500
  • OptiX 2500+(Metro 3000)
  • OptiX 155/622H(Metro 1000)

Network application of the OptiX OSN 2500


network-application-of-the-optix-osn2500

Networking Topology


The OptiX OSN 2500 supports topologies such as chain, ring, tangent rings, intersecting rings, ring with chain, dual node interconnection (DNI), hub, and mesh at the STM-1/STM-4/STM-16/ level.

The OptiX OSN 2500 supports the separate and hybrid configuration of the following types of NEs:
  • Terminal multiplexer (TM)
  • Add/drop multiplexer (ADM)
  • Multiple add/drop multiplexer (MADM)
  • The OptiX OSN 2500 can be interconnected with Huawei OSN, DWDM, and Metro equipment series, to provide a complete transmission network solution.

NOTE:
When the equipment is being interconnected, make sure that the K bytes to be received and transmitted are on the same path at both ends.
  • The OptiX OSN 2500 can be used with another OptiX OSN equipment to provide a complete ASON solution. This solution covers all the layers including the backbone layer, the convergence layer, and the access layer.
  • Through an SDH interface or a GE interface, the OptiX OSN 2500 can be interconnected with the WDM equipment.
  • Through an SDH, PDH, Ethernet, ATM, or DDN interface, the OptiX OSN 2500 can be interconnected with the OptiX Metro equipment.

Basic networking modes of the OptiX OSN equipment series


Networking ModeTopology
1Chain osn2500-chain
2Ring osn2500-ring
3Tangent rings osn2500-tangent-rings
4Intersecting rings osn2500-intersecting-rings
5Ring with chain osn2500-ring-with-chain
6DNI osn2500-dni
7Hub osn2500-hub
8Mesh osn2500-mesh
Legends:osn2500-legends

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