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

Tuesday, November 14, 2017

Huawei DSLAM MA5616 Power Distribution Principle and Working Principles

Power Distribution Principle

Huawei MA5616 can be powered by a DC or AC power source through a DC or AC power board. The power board outputs -48 V DC, +3.3 V DC, and +12 V DC power to the backplane. Then the backplane provides the -48 V DC and +3.3 V DC power for the service board and control board, and provides the +12 V DC power for the fan monitoring board.

Power distribution principle of the MA5616 chassis(DC-powered H831PDIA /H832PDIA /H832PDVA/ H832PDVAA) 


Power distribution principle of the MA5616 chassis (AC-powered by H831PAIA/H831PAIC) 


Power distribution principle of the MA5616 chassis (AC-powered with power backup by H831PAIB) 


Working Principles

Huawei MA5616 supports GPON, 10G GPON or GE upstream CCUE transmission by using its control board and provides broadband and narrowband access services by using different service boards.

Working principles of the MA5616 chassis 
The working principles of Huawei DSLAM MA5616 chassis are as follows:
  • The control board transmits services upstream and subtends device through subboards and manages service boards.
  • The power board outputs DC power to the backplane and then the backplane transmits the power to the fan tray, service boards, and control board.
  • The broadband or narrowband service board is connected to a user-side device by using a subscriber cable, and then the control board puts the user-side device through to the IP network. In this way, broadband or narrowband access service is provisioned to the user-side device.
  • The fan monitoring board monitors the fan tray and transmits the monitoring signal to the control board through the backplane.

Sunday, June 11, 2017

How to Turn on the Debug Switch in DC Server Process?

Issue Description
Q:
How to turn on the debug switch in the DC Server process?
Alarm Information
Null
Handling Process
A:
There are two methods to turn on the debug switch in the DC Server process:
I. Find the DC_DEBUGINFO_SWITCH parameter in the $n2000\server\conf\dc.cfg file (under the n2000 installation directory):
#For debugging the data center
  DC_DEBUGINFO_SWITCH = 1
1: indicates starting the system monitor; 0: indicates closing the system monitoring function
Modify the parameter to 1 to turn on the debug switch. After several operations resulting in the DCServer faults, two log files containing the DC field will be generated under $n2000/server/log.
DC_UA5000G_Alarm_Info.log0 and DC_172.20.17.70-161_Info.log0 (172.20.17.70 refers to the IP address of the operated device in the DCServer),
After collecting the debug information, you are recommended to turn off the switch timely to avoid generating further log files.
2. Operate as per the following steps:
telnet 10.71.61.45 9810  
Firstly, telnet to the port 9810 of the NM server. 10.71.61.45 corresponds to the IP address of the NM server
 iMAP>setdbg
 ProcessID : 148       (The internal process number corresponding to the DCServer)
 Scope(format is "module_submodule". default, all module) ://enter
 Debug level as following:
 0, None;
 1, Error.
 2, Error and Warning.
 3, Error Warning and Info.
 Please select level : 3
 Debug output orient as following: 
 0, Standard output.
 1, file.
 2, share memory.
3, EmfExamDm.
Please select orient : 1
 Setting succeeded!  
After several operations resulting in the DC Server fault, stop the debug switch.
iMAP>setdbg
Process ID : 148
Scope(format is "module_submodule". default, all module) :
Debug level as following:
0, Null;
1, Error.
2, Error and Warning.
3, Error Warning and Info.
Please select level : 0
Debug output orient as following:
0, Standard output.
1, file.
2, share memory.
3, EmfExamDm.
Please select orient : 0
Setting succeeded! 
Obtain the debug information about the DCServer process generated under $n2000/server/debug.
3. The information generated from the first method is less and easier for analysis, so the Method 1is normally used to identify general problems. The second method can generate more information, so it is more complicated for analysis, and often used to identify difficult problems. 
Root Cause
In the event of some unpredictable errors during the device operation in the DC Server, such as upgrade failure or patching failure, you can turn on the debug switch in the DC Server process to collect the debug information to identify the cause of the fault. 
Suggestions

Null
More related:

Introduction to MSTP_Prelude_Overview and History

Sunday, May 21, 2017

Why is the Link Status on N2000 NMS Displayed as Normal When the Status of the GE Port of the MA5600 Device is Offline?

Issue Description
Q: 
Why is the link status on N2000 NMS displayed as normal when the status of the GE port of the MA5600 device is offline?
Alarm Information
Null
Handling Process
A:
The query result from the Ethernet port window of the NMS complies with the result displayed on the host. Operation status indicates whether the port is activated; the green icon means the port has been activated; Online status shows whether the physical connection of the port to the external device is normal or not. The display on the NMS interface is consistent with the host. The engineer in charge of the host confirms that the normal connection of the port to the external device is not necessary for the port activation.
The color setting policy for the connection lines between the MA5300 devices is applicable to the connection lines between Huawei MA5600 devices in the NMS. If the port is activated, the connection line is green; if the port is not activated, the connection line is gray. Therefore, even though the physical connection is disconnected, the connection line is still green on the NMS. Thus the problem occurs.
We have two solutions to the above-mentioned problem:
1. Make corresponding modifications on the NMS side. Thus the color for the connection between the NMS devices depends on the connection status of the host.
2. .Modifications of the host Huawei MA5600 is the same as the modification of the network card and Huawei DSLAM MA5300. The port can be activated only when the network line is correctly connected to it.
After discussion, the engineers determine that the problem can be resolved by making corresponding modifications on the NMS side. Thus the color for the connection between the NMS devices depends on the connection status of the host. The problem can be resolved by the patch V200R006B02D030SP10.
Root Cause
Null
Suggestions
Null

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

Tuesday, April 4, 2017

ATU-R terminal management menu is not displayed on BMS GUI due to it is hidden

Issue Description
BMS V200R012C05SPC137 added ATU-R terminal management to performance ADSL terminal queries, configuration, ping tests, FTP tests, PPPoE emulation tests and terminal upgrades but menu is not on GUI.
Alarm Information
ATU-R terminal management menu is not found
Handling Process
As the menu is hided it is necessary to enable it with following procedure:
For example: to enable the menu for MA5100V1's ATU.
1. Identify following file in the Client PC.
\client\style\defaultstyle\conf\bms\ma5100v1\adsl\adslMenu.xml
2. Identify following line in that file and then add --> at the end of the line

<!--************************Atur manager pupup**************

    Identify following line in that file and then add <!-- at the beginning of that line
************************Atur manager pupup**************-->
3. After that restart the Client to test it.
Root Cause
Menu is hidden on BMS GUI
Suggestions
NOTE:
1.       For other devices related files are followings:
\client\style\defaultstyle\conf\bms\ma5100v1\adsl\adslMenu.xml
\client\style\defaultstyle\conf\bms\ma5100v2r1\adsl\adslMenu.xml
\client\style\defaultstyle\conf\bms\ma5105\adsl\adslMenu.xml
\client\style\defaultstyle\conf\bms\ma5300v1\adsl\adslMenu.xml
\client\style\defaultstyle\conf\bms\ma5600tv8\adsl\adslMenu.xml
\client\style\defaultstyle\conf\bms\ma5600v3\adsl\adslMenu.xml
\client\style\defaultstyle\conf\bms\ma5605\adsl\adslMenu.xml
\client\style\defaultstyle\conf\bms\ofa5920v3\adsl\adslMenu.xml
\client\style\defaultstyle\conf\bms\ua5000\adsl\adslMenu.xml
\client\style\defaultstyle\conf\bms\ua5000g\adsl\adslMenu.xml


2. For IPMB and MA5600V3 which version is older than Huawei MA5600V300R003C03B230 performance the same modification


on file named client\style\defaultstyle\conf\bms\bmscommon\adsl\adslMenu.xml
3. For MA5600V3 which version is newer than MA5600V300R003C03B230 performance the same modification on file named client\style\defaultstyle\conf\bms\lightweight\adsl\ma5600v3\**_popupmenu.xml 

More related:

MA5683T Platinum Line


MA5680T Platinum Line




Sunday, March 26, 2017

Huawei FTTx Leased Line Solution

Copper Access for Business

EDTB board in Huawei OLT will be adopted, which can support 16 E1 ports and 16 G.SHDSL ports concurrently in one board;

100% inherit the legacy service, don’t need change customer premise equipment;

Application Scenarios:

EDTB is mainly applied for extending E1 coverage by transferring to G.SHDSL;

Both TDM G.SHDSL and E1 interface can support PBX access;


E1 for access and TDM PWE3 for uplink can also be applied;

Native TDM + TDM PWE3

Scenario description:
MA5612/MA5628 access enterprise with TDM E1 interface, and access to Huawei MA5600T with Native TDM mode;

MA5600T access to upper layer PSN network after encapsulating Native TDM to PWE3;

MA5600T or CX600 terminates the PWE3 back to Native TDM to other part of the enterprise.

Clock solution description:
OLT have two ways to get the clock source in this scenario:  Synch Eth  and BITS;

OLT deliver the clock signal to ONU through GPON line clock,  then ONU deliver clock to base station through synch eth or specified clock interface;

Advantage:
PW encapsulation is centralized in OLT, which simplify Huawei ONU function and reduce the total CAPEX;


High accuracy clock from BITS and synch eth can fully meet the base station requirement ;



Sunday, February 26, 2017

The Service port Cannot Display Normally When Double-clicking the MA5600 Network Element to Enter the Board

Issue Description
Q: 
In the NMS topology, the serviceport cannot display normally when double-clicking the network element to enter the board.
Alarm Information
Null
Handling Process
A:
The status of Huawei MA5600 serviceport is the status of the traffic. Only when the single end PVC, the state machine of the traffic and the ADSL port are all  in Up status, the status of the serviceport is Up. Click the Synchronize Network Element in the Serviceport in the Serviceport Plane.




If the board is in position, generally the status of the single end PVC is Up.
The status of the ADSL port is Up after connecting to the modem.
The status of the service port is Up, indicating the normal condition.
Root Cause
1. The MA5600 database is full and the data space and the log space are normal.
2. MA5600 process is abnormal and no boot record. 
3. Other ports of Huawei MA5600 are normal. Only the service port is abnormal.
4. The MA5600 version is matched with the NMS version.
Suggestions
Null

Thursday, February 23, 2017

iManager U2000B V100R006C02SPC301 MA5603T GPON system NE Data synchronisation Failure

Issue Description
Software Version : iManager U2000-B (Access Devices) Version: V100R006C02SPC301
NE Device: MA5603T -MA5600V800R013  ( Huawei GPON System )

Situation :
U2000 Server was deployed to monitor the Access devices MA5603T and corresponding Huawei ONT in order to guarantee the stability of the GPON System.

At Ma5603T, Management IP address through the Meth0/0 was used to connect with the U2000 Server with the specified IP address.

Problem: Customer reported that they cannot achieve the synchronisation of the NE Data on the MA5603T in order to view the current situation of equipment, including the interface boards panel situations and traffic utilization . Customer also reported that they are unable to receive the alarms on the device. they want to resume the monitoring services on the Huawei MA5603T and corresponding devices. 
Alarm Information
Upon synchronisation of the NE Data on U2000 Client, Alarm displayed as follow:
"The frame's data is null, please synchroize device" .

Detailed Alarm of Synchronisation NE Data Failure: 
" Operation failed. Data collection failed.Please check the status of the FTP(SFTP) service and the user rights and root directory configurations. The Networks of NAT, Multi network cards and High Available System need config the XFTP file which is iptable_ne2nms.cfg." 
Handling Process
Troubleshooting logic :

a. Troubleshooting  of the origins leading to the failure synchronisation of NE data
b. Verification of the SNMP Setting
c. Verification of the FTP Server Settings in U2000,including the service testing on FTP and SFTP.
(Service side FTP service Verification )
d. Verification of the FTP client service in MA5603Tby manualy creating a backup task to U2000 server
(Client Side FTP Service Verification)
e. Reset of the FTP service again.
f.Initate the FTP service on both the MA5603T and U2000 Server.
Root Cause
Abnormality on FTP service in both the U2000 Server and Ma5603T
.FTP service cannot establish the FTP connection successfully. Xftp Watcher should also be reset again.
Solution
The FTP service on both the MA5603T and U2000 server have to be reconfigure and initiate again .

At U2000 Server, click Service-> FTP Setting
a. Verification of the Transfer Protocol and File Transfer Service Setting.
b. Configure FTP and SFTP  by default , UserName ftpuser, Password: "Changeme_123". FTP Port is 20 .
c. At FTP Server Setting, reset the Username, password , and the FTP service Status.

At Huawei MA5603T,
a. Activate the FTP
b. Manually start the FTP service by "FTP SET" command. Manually create a Backup task by " Backup configuration ftp x.x.x.x ac.cfg"

Check whether the panel from the equipment can be seen after the synchronization of the NE data , the alarm should also be displayed accordingly.
Suggestions

Our customer can set up routine schedule on backup configuration through snmp and ftp service daily, so that the service can be guarantee to perform normally.

Thursday, March 17, 2016

MA5600T Multicast Feature Glance

Definition
Multicast is group communication where data is addressed to a group of destination 
hosts simultaneously. Each multicast address represents a multicast group and all hosts 
in a multicast group can receive the same data. Multicast applies in IPTV,multimedia 
conferencing, and gaming services.

Value
Reduces bandwidth overheads
Each link carries at most one copy of the same multicast data, maximally reducing bandwidth overheads.
Decreases load
Transmitting data in multicast mode decreases video server's and CPU's load and does not significantly increase network's load even if the number of users increases.
Prolongs transmission distance
Multicast packets can be transmitted across network segments,implementing long-distance transmission for large-scale data.
Prolongs transmission distance
Multicast packets can be transmitted across network segments,implementing long-distance transmission for large-scale data.
Application
Multicast applies in the following scenarios: FTTB/FTTC, FTTH, FTTO, as well as OLT user ports connecting to multicast users.

Highlights
Powerful Multicast Capabilities, Improving IPTV Service Deployment
Primary Features Performance
  • 8 K multicast users (1 K= 1024)
  • 4 K multicast programs
  • Concurrent playing of 4000 IPv4 and 2000 IPv6 multicast programs when the SCUH control board is used
  • Multiple levels of multicast data duplication
  • IGMP fast leave
  • 50-ms channel switching
  • 3200-pps IGMP packet processing if the SCUH control board is used
  • Physical-layer G.INP retransmission for better user experience on the IPTV service
  • 900-pps IGMP packet processing on the GPFD board
Features
  • Both IPv4 and  IPv6multicast
  • MLDv1 and MLDv2
  • MLD snooping andproxy
  • IGMPv2 and IGMPv3
  • VPLS multicast
Highlights
Conversion Between M-VLANs and C-VLANs, Implementing Multiple CPs Sharing One ONT and Supporting Open Access

The multicast data transmission meets the service requirement of multiple CPs renting different ports on the same ONT in the open access scenario, improving revenue from resources.
Layer 3 Multicast for Flexible Multicast Group Address Usages
The programs issued from different multicast sources can use the same group IP address (GIP).
Compared with Layer 2 multicast, Layer 3 multicast relieves GIP limitations due to group MAC address (GMAC) conflict.

Highlights
Comprehensive Fault Locating Methods, Facilitating Rapid Multicast Service Fault Rectification
User Log Identify causes for program ordering failures by querying user logs or fault-related operation records.
IGMP Statistics Identify IGMP packet transmit and receive issues based on IGMP packet statistics.
Multicast Traffic Statistics Based on multicast traffic statistics, determine whether:
  • Multicast data has arrived at the inbound or outbound port on the MDU at the data forwarding layer.
  • The transmission rate is excessively low.
  • Packet loss has occurred.
Multicast Emulation Emulate program ordering performed by a multicast user to locate faults by querying traffic and user information in real time.
Board recommendation
Specifications H802SCUN H801SCUH H801SCUK
Number of multicast logs 32768 32768 32768
IGMP packet processing capability 400 pps 3200 pps 400 pps
Number of multicast users If GPON service
boards are used:
8192
If other service
boards are used:
2048
If GPON service
boards are used:
16384
If other service
boards are used:
2048
If GPON service
boards are used:
8192
If other service
boards are used:
2048
Number of multicast programs 4096 4096 4096
Number of concurrent online programs 2000 IPv4: 4000
IPv6: 2000
2000
Number of multicast cascading ports 2048 4096 2048

Monday, March 14, 2016

How to Troubleshoot the Failure on GPON

An ONU connected to a GPON port of an OLT fails to go online normally, but the queried Run state of the ONU is displayed as offline by running the display ont info command on the OLT.
Location Method
NOTE:
Going online refers to a process that after being powered on, an ONU registers with an OLT and sets up a management channel with the OLT. An ONU can be managed by the OLT and be configured with services only after going online.
When an ONU fails to go online, locate the fault based on the following fault symptoms and possible causes.
Possible Cause
Judgment Criterion
Troubleshooting Method
The SN configured on the OLT is different  from the actual SN of the ONU; hence, the ONU fails to pass authentication  and to go online.
 Run the display ont info command to query the ONU information. It is  found that the SN in the result is different from the actual ONU SN.
Run the ont add command to re-add an ONU  and specify the correct ONU SN and password.
 NOTE:
 The ONU with a different SN is regarded as a new one and is founded by the  OLT.
The actual distance between the ONU and  OLT exceeds the ranging compensation distance configured on the OLT.
Run the display port info command to  query the minimum logical reach (Min distance) and maximum logical reach (Max  distance) configured for the GPON  port. It is found that the actual distance between the ONU and OLT exceeds  the ranging compensation distance.
 For example, the actual length of the optical fiber between the ONU and OLT  is about 25 km, which exceeds the ranging compensation distance of 0-20 km.
Run  the port range command to adjust the minimum logical reach and maximum  logical reach so that the actual distance between the ONU and OLT is within  the ranging compensation distance.
 NOTE:
 By default, the ranging compensation distance of a GPON port is from 0 km to  20 km.
 According to Class B+, the maximum logical reach of a GPON port must not  exceed 60 km, and the difference between the minimum logical reach and  maximum logical reach must not exceed 20 km.
The OLT deactivates the ONU.
Run the display ont info command to query  the ONU information. It is found that Control flag is displayed as deactive.
Run the ont activate command to activate  an ONU.
 NOTE:
 When an ONU is activated, its optical module only receives optical signals  but does not transmit optical signals.
The laser on the PON port is disabled.
Run the display port info command to  query the information about the PON port. It is found that Laser switch is in  the Off state.
Run the port laser-switch command to  enable the laser on the PON port.
 NOTE:
 By default, the laser on a GPON port is enabled.
The PON port is faulty.
If  either of the following two situations occurs, the PON pot is faulty.
 Run the display port state command to query the status of the PON port. It is  found that abnormal items exist in the query result. For example, the laser  status (Laser state) is abnormal and the transmit optical power (TX power)  exceeds the normal range (1.5-5.0 dBm).
 Migrate the service to another port. It is found that the ONU goes online  normally.
Replace the optical module of the PON  port or replace the board.
The board or the slot is faulty.


 All the ONUs connected to the board fail to go online.


 Change the board to another slot. If the fault persist, replace the board.
CAUTION:
To facilitate fault report, save the results of the following steps.
The parameters of the optical module in this topic comply with Class B+. Note that such parameters are slightly different from the parameters in Class C.
Procedure
1.When the queried Run state of the ONU is displayed as offline, check whether the OLT generates the following alarms. If such alarms are generated, clear them and check whether the fault is rectified. If the fault persists, proceed to 2.
The following alarms may be generated:
2.Check for the possible causes on the OLT and troubleshoot the faults accordingly. If the ONU still fails to go online after that, proceed to 3.
Possible Cause
Judgment Criterion
Troubleshooting Method
The SN configured on the OLT is different  from the actual SN of the ONU; hence, the ONU fails to pass authentication  and to go online.
Run  the display ont info command to query the ONU information. It is found that  the SN in the result is different from the actual ONU SN.
Run the ont add command to re-add an ONU  and specify the correct ONU SN and password.
 NOTE:

 The ONU with a different SN is regarded as a new one and is founded by the  OLT.
The actual distance between the ONU and  OLT exceeds the ranging compensation distance configured on the OLT.
Run the display port info command to  query the minimum logical reach (Min distance) and maximum logical reach (Max  distance) configured for the GPON port. It is found that the actual distance  between the ONU and OLT exceeds the ranging compensation distance.

 For example, the actual length of the optical fiber between the ONU and OLT  is about 25 km, which exceeds the ranging compensation distance of 0-20 km.
Run  the port range command to adjust the minimum logical reach and maximum  logical reach so that the actual distance between the ONU and OLT is within  the ranging compensation distance.
 NOTE:
 By default, the ranging compensation distance of a GPON port is from 0 km to  20 km.
 According to Class B+, the maximum logical reach of a GPON port must not  exceed 60 km, and the difference between the minimum logical reach and  maximum logical reach must not exceed 20 km.
The OLT deactivates the ONU.
Run the display ont info command to query  the ONU information. It is found that Control flag is displayed as deactive.
Run the ont activate command to activate  an ONU.
 NOTE:

 When an ONU is activated, its optical module only receives optical signals  but does not transmit optical signals.
The laser on the PON port is disabled.


 Run the display port info command to query the information about the PON  port. It is found that Laser switch is in the Off state.
Run the port laser-switch command to  enable the laser on the PON port.
 NOTE:

 By default, the laser on a GPON port is enabled.
The PON port is faulty.
If  either of the following two situations occurs, the PON pot is faulty.
 Run the display port state command to query the status of the PON port. It is  found that abnormal items exist in the query result.
Replace the optical module of the PON  port or replace the board.
The board or the slot is faulty.
All the ONUs connected to the board fail  to go online.
Change the board to another slot. If the  fault persist, replace the board.

3.Check for the possible causes on the ODN and troubleshoot the faults accordingly. If the ONU still fails to go online after that, proceed to 4.
4.Check for the possible causes on the ONU and troubleshoot the faults accordingly. If the ONU still fails to go online after that, proceed to 5.
5.Record the results of the preceding steps in the form for reporting a fault, fill in the form completely, and then submit the form to Huawei for technical support.
6.The fault is rectified.
Telephone: 852-30623083
           Supports@Thunder-link.com