Showing posts with label Huawei OSN 3500. Show all posts
Showing posts with label Huawei OSN 3500. Show all posts

Thursday, June 8, 2017

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.




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            

Sunday, March 13, 2016

What interface is the huawei Optix OSN3500 support

Question: What interface is the huawei Optix OSN3500 support?
Answer:
Support STM-1 (O/E). SL1D
Support the STM-4/16/64 standard or cascade business.
Support E1/T1/E3/T3/E4.
Support FE, GE business transmission and exchange.
Support the ATM service.
Support the IMA service.
Support SAN service and video service.
To provide end-to-end service fast terminal based on GMPLS.
the huawei Optix OSN3500 has high order 200G, the low order 40G cross scheduling capability. With the 100G packet switching capability.

The system supports EM6T/EM6F packet switching and transmission OSN 3500 intelligent optical transmission, and inherits all the features of MSTP technology, compatible with traditional SDH,MSTP network, a new generation of integrated 10G/2.5G into SDH/PDH, Ethernet, WDM, ATM,ESCON/FC/FICON, DVB-ASI, RPR application technology as a whole in the sink and core layermulti service intelligent optical transmission platform.
The evolution of intelligent optical network products to support smooth. Mainly used in industry market convergence layer and access layer, and sharing and OSN9560/OSN7500/2500/1500plate convergence and core layer; OSN3500 support intelligent characteristics, can completeend-to-end service automatic configuration, SLA service, traffic engineering, slot fragmentoptimization, Mesh clock tracking, improve the network utilization.
More information about it, please click here.

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