Showing posts with label HUAWEI GPON Network. Show all posts
Showing posts with label HUAWEI GPON Network. Show all posts

Sunday, July 30, 2017

iManagerN2000 - Tape Backup fails

Issue Description
Customer product iManager N2000,Version V200R008B02D061SP23 & V200R008B02D061SP21
Tape backup of the Databases does not work. The tape backup causes /dev/rmt/0n: Device busy message when executing mt status command. No files are coppied into /opt/n2000/backup/AllDB/20080318150012. Stangely the 20080318150012 was created with root: other instead of n2kuser:2kgroup ownership. The log file in the Database Backup tool does NOT show a record of backup success or failure.

Alarm Information
root@NBMS_B # mt status
/dev/rmt/0n: Device busy
Handling Process
1.Restart the whole server not only the application n2000.
    a)stop n2000
    b)stop watchman
    c)stop sybase
    d)restart server shutdown -y -g0 -i6
2.When you make Tape backup do as follows:
    a)initialize the Tape
    b)make backup
      
Root Cause
First we tried to restart the application n2000, but after that the tape still does not work. We restart thewhole server and after we tried again after restart the backup still does not work Tape drive was staying only in busy state and you cannot do anything.

Suggestions
You have to do Three things for success:
1. Restart the server
2.Initial the tape
3.Make backup



Thursday, July 27, 2017

Network Applications of TDM PWE3 and ETH PWE3

Network Applications of TDM PWE3

For details on the corresponding clock solution of the TDM service, see 26.5 Physical Layer
Clock/Time Synchronization.
Network application: converting the native TDM service into the E1 service for upstream
transmission
As shown in Figure, the mobile 2G base station is connected to the ONU through
TDM E1. Huawei ONU encapsulates the TDM frame into the GPON GEM frame directly to
transmit TDM service over Huawei GPON network (native TDM). The OLT terminates the
TDM PWE3 signals and transmits the signals to the upstream network through the E1
port.

Network application: converting the TDM PWE3 service into the E1 service for
upstream transmission
Network Applications of ETH PWE3
Network application: implementing PWE3 private line upstream transmission in FE/GE
access
As shown in Figure, the enterprise router is connected to the OLT MA5600T through FE/GE.
The OLT interconnects with the peer ETH PWE3 device of the enterprise through the
ETH PWE3 private line to implement the ETH private line service.
Figure 8-27 Network application: implementing PWE3 private line upstream transmission in
FE/GE access

Thursday, July 13, 2017

N2000BMS shows the alarms with an early hour because the NE does not have configured the right time zone

Issue Description

The alarms displayed in the N2000BMS are displayed with an early hour.
The alarm is reported in the OLT MA5600V800R007
Example:
the next alarm is reported in Huawei MA5600T at 01:39:49-05:00, but, in the N2000BMS appear the same alarm at 02:39:49. The time in the N2000BMS is the real time.

Handling Process
Because of the BMS had the correct time, so, it was supposed that the DST was not configured in the NEs.
It was analyzed the time settings and the time zone  in Huawei OLT.
Ceylan(config)#display time                                                  
{ <cr>|dst<K>|time-stamp<K> }:                                                 
  Command:                                                                   
          display time                                                       
  2011-11-02 10:10:03-05:00                                                                                                                                 
Ceylan(config)#display timezone                                              
The current time zone:  GMT-05:00

it was found that the timezone is not the correct. So it was requested change the timezone to make a test.
After modify the time zone to the correct one, the alarms was reported in the N2000BMS with the correct time.
However, to avoid changing the timezone every period of time, it was suggested to enable the DST.
Ceylan(config)#display time dst                                              
  Failure: DST has not been configured  

  
Suggestions
Verify the timezone of the country to set the correct one in the NE or in the Server. Also, consider use the DST feature.

Monday, June 26, 2017

Introduction for TE Tunnel Protection Group on Huawei Access Network Equipment

Introduction for TE Tunnel Protection Group on Huawei Access Network Equipment.

A tunnel protection group protects end-to-end MPLS TE tunnels. If a working tunnel in a protection group fails, traffic switches to a protection tunnel, minimizing traffic interruptions.

Related Concepts
As shown in the Figure, concepts related to a tunnel protection group are as follows:
Working tunnel: a tunnel to be protected.
Protection tunnel: a tunnel that protects a working tunnel.
Protection switchover: switches traffic from a faulty working tunnel to a protection tunnel in a tunnel protection group, which improves network reliability.


Primary tunnels tunnel-1 and tunnel-2, and the bypass tunnel tunnel-3 are established on the ingress Access Node

Tunnel-3 is specified as a protection tunnel for primary tunnels tunnel-1 and tunnel-2 on Access Node. If the configured fault detection mechanism on the ingress detects a fault in tunnel-1, traffic switches to tunnel-3. Access Node attempts to reestablish tunnel-1. If tunnel-1 is successfully established, traffic switches back to the primary tunnel.

Implementation
A TE tunnel protection group uses a configured protection tunnel to protect traffic on the working tunnel to improve tunnel reliability. To ensure the improved performance of the protection tunnel, the protection tunnel must exclude links and nodes through which the working tunnel passes during network planning.

Protection mode
A tunnel protection group works in either 1:1 or N:1 mode. The 1:1 mode enables a protection tunnel to protect only a single working tunnel. The N:1 mode enables a protection tunnel to protect more than one working tunnel.

More related:

MA5600V800R00X series devices load the IO data package

P2P Access: Configuring FTTH Service








Thursday, June 22, 2017

OT928G loopback cannot be configured due to U2000 internal problem

Issue Description
It is required to configure loopback on OT928G through U2000 management system but when it is done system
pop ups an alarm informing that operation failed.
MA5680T MA5600V800R008C01
U2000 V100R002C01SPC004
Alarm Information
Set a Local Loopback operation failed
Failure cause: The version does not match
Handling Process
Process to configure loopback through U2000 was verified and tested to confirm it is correct and it was but the failure was gotten
Versions compatibility was verified and it was confirmed U2000 supported Huawei MA5600T base version
Process was recurred to collect some info and logs that were sent to R&D who finally confirmed it was U2000 problem so, they provided a temporal solution replacing file GPON_operdesc.xml  on following path.


U2000/server/nemgr/nemgr_access/dcp/mib/gpon/GPON_operdesc.xml
However, this problem has been already solved on patch SPC501 for U2000
Root Cause         
Procedure to configure loopback is not correct
U2000 and OLT versions are not compatible
Software system problem
Suggestions

Null

Thursday, May 25, 2017

Huawei GPON Protocol Stacks

ITU-T Recommendation G.984.3 defines a new set of frame structures, which consider traditional voice, video, and Ethernet packets as payloads of Huawei GPON frames. Figure 2-10 shows the structure of GPON protocol stacks.
GPON protocol stacks involve the physical medium dependent (PMD) layer and GPON transmission convergence (GTC) layer.
PMD Layer
The GPON PMD layer corresponds to the GPON interfaces between Huawei OLTs and Huawei ONUs. Parameter values of the GPON interfaces specify the maximum reach and split ratio for a GPON system.
GTC Layer
The GTA layer is used to encapsulate payloads using ATM cells or GEM frames, and GEM frames are commonly used in GPON systems. GEM frames can carry Ethernet, POTS, E1, and T1 cells.
GTC is the core GPON layer, where media access is controlled for upstream service flows and ONUs are registered. Ethernet frame payloads are encapsulated into GEM frames and then packetized as GTC frames. These GTC frames are converted to binary codes for transmission based on interface parameters configured at the physical layer. The process is reversal on the receive end. Specifically, the receive end decapsulates the data to obtain GTC frames, GEM frames, and then payloads for data transmission.
The GTC layer is classified as TC adaptation sub-layer and GTC framing sub-layer by structure.

The TC adaptation sub-layer involves the ATM, GEM TC, and optical network terminal management and control interface (OMCI) adapters and dynamic bandwidth assignment (DBA) control module. ATM and GEM TC adapters identify OMCI channels by virtual path identifier (VPI)/virtual channel identifier (VCI) or GEM port ID. OMCI adapters

can exchange OMCI channel data with the ATM and GEM TC adapters and send the OMCI channel data to OMCI entities. The DBA control module is a common functional module, which generates ONU reports and controls DBA allocation.
On the GTC framing sub-layer, GTC frames include GEM blocks, PLOAM blocks, and embedded OAM blocks. The GTC framing sub-layer supports the following functions:
− Multiplexes and demultiplexes data. Specifically, the GTC framing sub-layer multiplexes PLOAM and GEM data into downstream TC frames based on the boundary information specified in the frame header. In addition, the GTC framing sub-layer demultiplexes PLOAM and GEM data from upstream TC frames based on frame header instructions.
− Generates frame headers and decodes data. The GTC framing sub-layer generates the TC header of downstream frames in a specified format and decodes the frame header of upstream frames. In addition, the GTC framing sub-layer terminates the embedded OAM data encapsulated into the GTC header and uses the OAM data to control this sub-layer.
− Routes data internally based on alloc-IDs. The GTC framing sub-layer routes the data sent by or to the GEM TC adapters based on internal alloc-IDs.

The GTC layer consists of plane C/M and plane U based on functions.
The protocol stacks of plane C/M include embedded OAM, PLOAM, and OMCI. Embedded OAM and PLOAM channels are used for managing PMD and GTC sub-layer functions. OMCI provides a unified system for upper-layer sub-layer management.
− Embedded OAM channels are defined in GTC frame headers for determining bandwidths, exchanging data, and dynamically allocating bandwidths.
− Dedicated space is reserved in GTC frames for format-based PLOAM channels. The PLOAM channels carry the PMD and GTC management information that does not pass through the embedded OAM block.
− OMCI channels are used for managing services.
Service flows on plane U are identified based on service flow types (ATM or GEM) and port ID/VPI. Port IDs identify GEM service flows and VPIs identify ATM service flows. In T-CONTs, bandwidths are allocated and QoS is controlled using the timeslots that can be adjusted.

Wednesday, May 24, 2017

Huawei GPON Networking Applications

GPON is a passive optical transmission technology that applies in FTTx solutions, including fiber to the building (FTTB), fiber to the curb (FTTC), fiber to the door (FTTD), fiber to the home (FTTH), fiber to the mobile base station (FTTM), fiber to the office (FTTO), and fiber to the WLAN (FTTW), for voice, data, video, private line access, and base station access services.
Figure 2-7 shows FTTx networking applications.
Huawei FTTx network applications in GPON access have the following in common: The data, voice, and video signals of terminal users are sent to ONUs, where the signals are converted into Ethernet packets and then transmitted over optical fibers to the OLT using the GPON uplink ports on the ONUs. Then, the Ethernet packets are forwarded to the upper-layer IP network using the uplink port on the OLT.

  • FTTB/FTTC: The OLT is connected to ONUs in corridors (FTTB) or by the curb (FTTC) using an optical distribution network (ODN). The ONUs are then connected to user terminals using xDSL. FTTB/FTTC is applicable to densely-populated residential communities or office buildings. In this scenario, FTTB/FTTC provides services of certain bandwidth for common users.
  • FTTD: uses existing access media at user homes to resolve drop fiber issues in FTTH scenarios.
  • FTTH: The OLT such as Huawei MA5600T connects to ONTs at user homes using an ODN network. FTTH is applicable to new apartments or villas in loose distribution. In this scenario, FTTH provides services of higher bandwidth for high-end users.
  • FTTM: The OLT is connected to ONUs using an ODN network. The ONUs are then connected to wireless base stations using E1. The OLT connects wireless base stations to the core IP bearer network using optical access technologies. This implementation mode is not only simpler than traditional SDH/ATM private line technologies, but also drives down the costs of base station backhaul. FTTM is applicable to reconstruction and capacity expansion of mobile bearer networks. In this scenario, FTTM converges the fixed network and the mobile network on the bearer plane.
  • FTTO: The OLT is connected to enterprise ONUs using an ODN network. The ONUs are connected to user terminals using FE, POTS, or Wi-Fi. QinQ VLAN encapsulation is implemented on the ONUs and the OLT. In this way, transparent and secure data channels can be set up between the enterprise private networks located at different places, and therefore the service data and BPDUs between the enterprise private networks can be transparently transmitted over the public network. FTTO is applicable to enterprise networks. In this scenario, FTTO implements TDM PBX, IP PBX, and private line service in the enterprise intranets.
  • FTTW: The OLT connects to ONUs like Huawei HG8546M using an ODN network, the ONUs connect to access points (APs) using GE for WLAN traffic backhaul. FTTW is the trend in Wi-Fi construction.

Tuesday, May 16, 2017

How to Modify the Size of Data Storage in Environmental Monitoring Database?

Q:
The data storage in the environmental monitoring database is generally defaulted as 500 thousand records. If the data is exceeded, the earliest data will be deleted. However, when managed network elements are rather many, 500 thousand records are only equivalent to the data in one to two days. When more data is needed to be saved, how to modify?
Alarm Information
Null
Handling Process
A:
1.Open the file \n2000\server\conf\main\enpowerdm\enpowerdm.cfg;
Find # to save the maximal historical data
SaveHisDataMax = 500000
Change 500000 to the data required, such as 2000000, and save the file.
What needs to be noted is that it is not recommended to use large data, which may take enormous data space.
If the saved data exceeds 10 million strips, it may result in the abnormity of environmental database.
2.Open the NM sysmonitor, find the background of environmental monitoring, and close the background of environmental monitoring.
3.Restart the background of environmental monitoring.
Root Cause
Nul
Suggestions

The environmental monitoring database mainly saves some changing data of environment parameters. Generally, the data is not required to be saved in large quantity. The environment alarm can be queried by querying the alarm database for failure history

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

Tuesday, May 9, 2017

Configuring FTTH Service (P2P Access)

Users connected to the OLT through an ONT, and are therefore provided with the Internet,
VoIP, and IPTV service through a same port.

Service Requirements

  • ONT_1 and ONT_2 are provided with the triple play service through Huawei FTTH.
  • The Internet access service is provided in the PPPoE access mode.
  • The IPTV user connected to ONT_1 can watch all the programs, and the IPTV user connected to ONT_2 can watch only program BTV-1.
  • The VoIP service and the IPTV service are provided in the DHCP mode and obtain IP, addresses from the DHCP server in the DHCP option-60 mode.
  • After receiving different traffic streams, the OLT provides different QoS guarantees to the traffic streams according to the priorities of the traffic streams.
  • Traffic streams are differentiated on the OLT by the user-side VLAN (C-VLAN).

Example network of the optical fiber access service in the single-port for multiple
services mode
Prerequisite
  • Huawei OLT is connected to the upper-layer devices such as the BRAS, multicast server, SoftX3000, and DHCP server.
  • The VLAN of the LAN switch port connected to the OLT is the same as the upstream VLAN of the OLT.
Procedure
Configure the Internet access service on the OLT.
a. Create a VLAN and add an upstream port to the VLAN.
The VLAN ID is 100, and the VLAN is a smart VLAN. The upstream port is 0/9/0.
b. Configure a traffic profile.
Because the VoIP, IPTV, and Internet access services are provided through the same
port, you must set the 802.1p priority of each service. Generally, the priorities are in a descending order for the VoIP service, IPTV service, and Internet access service.
In this example, set the traffic profile index to 7 and the priority of the Internet access service to 1.
c. Configure a service port.
Add a service port to the VLAN and use traffic profile 7. The user-side VLAN ID is 2.
d. Configure queue scheduling.
Use the 3PQ+5WRR queue scheduling. Queues 0-4 adopt the WRR mode, with the
weights of 10, 10, 20, 20, and 40 respectively; queues 5-7 adopt the PQ mode.
Configure the mapping between queues and 802.1p priorities. Priorities 0-7 map
queues 0-7 respectively.
e. Save the data.
Configure the VoIP service on Huawei MA5600T.
a. Create a VLAN and add an upstream port to the VLAN.
The VLAN ID is 200, and the VLAN is a smart VLAN. The upstream port is0/9/0.
b. Configure a traffic profile.
The traffic profile index is 8, and the 802.1p priority of the VoIP service is 5.
c. Configure a service port.
Add a service port to the VLAN and use traffic profile 8. The user-side VLAN ID is 3.
d. Configure the DHCP relay.
The VoIP service and the IPTV service are provided in the DHCP mode. The DHCP
option 60 domain is used to differentiate service types.
The DHCP domain of the VoIP service is voice.
The IP addresses of VoIP DHCP server group 1 are 20.1.1.2 and 20.1.1.3.
The IP address of the Layer 3 interface of VLAN 200 is 10.1.1.1/24.
The gateway IP address of the DHCP domain is 10.1.1.1/24.
e. Save the data.
Configure the IPTV service on the OLT.
a. Create a VLAN and add an upstream port to the VLAN.
The VLAN ID is 1000, and the VLAN is a smart VLAN. The upstream port is0/9/0.
b. Configure a traffic profile.
The traffic profile index is 9, and the 802.1p priority of the IPTV service is 4.
c. Configure a service port.
Add a service port to the VLAN and use traffic profile 9. The user-side VLAN ID is d. Configure the DHCP relay.
The VoIP service and the IPTV service are provided in the DHCP mode. The DHCP
option 60 domain is used to differentiate service types.
The DHCP domain of the IPTV service is video.
The IP addresses of IPTV DHCP server group 2 are 20.2.2.2 and 20.2.2.3.
The IP address of the Layer 3 interface of VLAN 1000 is 10.2.2.1/24.
The gateway IP address of the DHCP domain is 10.2.2.1/24.4.
e. Create a multicast VLAN and select the IGMP mode.
Select the IGMP proxy mode.
f. Set the IGMP version.
Set the IGMP version of the multicast VLAN to IGMP v3.
g. Configure the program library.
Configure the program names to BTV-1 and BTV-2, multicast IP addresses of the
programs to 224.1.1.10 and 224.1.1.20, source IP address of the programs to
10.10.10.10, and priority to 4.
h. Configure the right profile.
Configure the profile name to profile0, with the right of watching program BTV-1.
i. Configure the multicast users.
Add service ports 200 and 300 as multicast users.
j. Save the data.

Monday, April 17, 2017

Why I failed to Enable the CAU Function of the U2000 on my Computer?

Issue Description

I bought a Huawei MA5683T configure with one GPFD  C+, when I install U2000 server on computer, the U2000 client is installed remotely by using the computer according to the installation guide. After http://server IP address:8080/cau is entered in the address box, the web page cannot be displayed. The web page for client installation cannot be displayed on the local server, either. 
Alarm Information
The page cannot be displayed. 
The page you are looking for is currently unavailable. 
Handling Process
Check and confirm that the following conditions are met according to the installation guide. 
The default browser of Windows OS is Internet Explorer 6.0 or 7.0, and the proxy server is not set.
2. The U2000 server and CAU process are started up in the normal state. 
The U2000 server successfully communicates with the U2000 client and the bidirectional server-client ping operation is successful.
4. The port (port ID: 8080) on the U2000 server for installing the U2000 client in the network mode is enabled.
5. If the U2000 client has been installed in the network mode previously, uninstall the U2000 client and ensure that the .cau file in the %USERPROFILE% directory (such as C:\Documents and Settings\Administrator) is deleted. 
6. In addition to meeting the requirement for installation partition sizes, at least 900 MB space is available in disk C for data buffer. 
The CAU function, however, is still disabled. With the assistance of R&D engineers, it is confirmed that the CAU function is disabled by default when the U2000 is installed on a computer with smaller than 3 GB memory. Under this condition, the CAU function can be enabled only manually. To manually enable the CAU function, copy all files in the U2000\common\Tomcat\webapps\not_support\cau directory to the U2000\common\Tomcat\webapps\cau directory without restarting the system. Then, the CAU function is enabled immediately. 
Root Cause
The possible cause is that the port is being used or the CAU function is disabled. 
Suggestions
It is recommended that the limitation should be described in the installation guide. Engineers will encounter this problem after installing the U2000 because the computer memory of Huawei is smaller than 2 GB. 

Sunday, April 16, 2017

Huawei MA5800 Stand-Alone Commissioning

After the hardware installation, a stand-alone MA5800 should be commissioned to ensure that the stand-alone Huawei OLT MA5800 works in the normal state. The following recommended commissioning tasks and sequences are for reference only. Different offices have different conditions; therefore, it is recommended that customers, with the assistance of our engineers, modify commissioning tasks according to actual requirements.

Powering On the Device
This topic describes how to power on the device to ensure that all the boards can be normally powered on.

Prerequisites
The after-installation check and the power-on check must be performed on the device.

Procedure
There are two kinds of devices: the indoor device and the outdoor device.
− Powering on the indoor device
1. Connect the input power supply of the DC PDU.
2. Turn on the output control switch of the DC PDU.
− Powering on the outdoor device
1. Connect the input power supply of the AC PDU.
2. Turn on the output control switch of the AC PDU.
3. Turn on the output control switch of the power system.
4. Turn on the output control switch of the DC PDU.

Result
The device can be normally powered on, and the STATUS indicator on the fan tray is on for 1s and off for 1s repeatedly, and so is the RUN ALM indicator on the board.

Commissioning the Power Supply System
This topic describes how to commission the power supply to ensure the reliable and stable power supply provided for the device.

Prerequisites
Only Huawei MA5800 supports this operation.
The two independent power supplies of the DC power distribution unit (PDU) supply power to the cabinet concurrently.
Procedure
Step 1 Disconnect the first power supply, and check the power supply of the cabinet.
Step 2 Restore the first power supply to power the cabinet.
Step 3 Disconnect the second power supply, and check the power supply of the cabinet.
Step 4 Restore the second power supply to power the cabinet

Procedure
Step 1 Turn off the switch on the PDU that corresponds to one power board, and check the power supply for the service board.
Step 2 Turn on the switch again.
Step 3 Repeat steps 1 and 2 to check the other power board.

Monday, April 10, 2017

Huawei MA5800- X17 Appearance and Structure

Huawei MA5800-X17 service subrack provides 22 slots,while Huawei MA5600T has 16 service solt and has a fan tray at the top. The subrack is installed in the cabinet through the mounting brackets.


ESD Jack
The ESD jack of Huawei MA5800-X17 subrack is on the left of the fan tray, which is used to
connect the ESD wrist strap to prevent device damage caused by electrostatic discharge.

Connect the ground cables properly to guarantee protection against lightening and
interference for the MA5800-X17 subrack. When a Huawei cabinet is installed, the service
subrack is grounded through mounting ears and therefore no separate ground cables are
required. When a third-party cabinet is installed, the separate ground cable needs to be
connected to the service subrack and ground point on the cabinet.

The MA5800-X17 subrack has 2 ground points. One is on the side panel and the other is at
the bottom of the right mounting ear of the subrack.
The power input end of the MA5800-X17 subrack has a noise filter. The center ground of the
noise filter connects to the subrack, called the subrack ground, that is, the protection ground.

Ground the subrack securely so that the influence electricity, leakage electricity can flow to
the ground, improving the protection against electromagnetic interference.
Use a ground cable to connect the ground point of the subrack to the ground bar of the
telecommunications room or to the ground directly. It is recommended that the grounding
resistance of the telecommunications room should be less than 10 ohms. Refer to the local
standards to ground the subrack.

Dimensions and Weight:
Dimensions (H x W x D, including mounting ears):486 mm x 535 mm x 287 mm
Dimensions (H x W x D, excluding mounting ears):486 mm x 493 mm x 287 mm
Maximum weight at full configuration (including mounting ears):45 kg

Power Supply:
Power supply mode:DC (dual power for backup)
Rated voltage: -48 V / -60 V
Working voltage range:-38.4 V to -72 V
Maximum input current: 60 A


More related:

​MA5600T Series Equipment Aggregate Docking Cisco Equipment


Sunday, April 9, 2017

Ethernet trail alarms are not synchronized with real alarms on NEs

Issue Description
Customer M complains that Ethernet trails status is "not alarmed" but when he checks the relevant NE he found that there are some alarms. So the Ethernet trail alarm status is not automatically updated with NE alarms.
Alarm Information
Null
Handling Process
to solve this problem follow the following steps:
.          Stop the nmleth process manually.
.          Modify bRelocateAlarmByTrailAssociate from 0 to 1 in U2000server\nml\nmleth\conf\cfg\nmleth.cfg
.          Restart the nmleth process.
.          Browse current alarms about the faulty trail again.
Alarms are relocated and relationship between the trail and its alarms will be updated. As a result, alarm status is synchronized.
Root Cause
after checking and analyzing we found that the root cause of this problem is located in nmleth.cfg file that is stored in the folder server\nml\nmleth\conf\cfg , in fact there is one parameter that is responsible for displaying trail alarm:  bRelocateAlarmByTrailAssociate , this parameter has the value "0", that is why there was no mechanism to automatically synchronize the trail alarm.
Suggestions

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