Showing posts with label Huawei Access Network. Show all posts
Showing posts with label Huawei Access Network. Show all posts

Monday, June 19, 2017

Logical fiber still green even if real fiber is cut and we have R_LOS alarm

Issue Description
Customer M complains the following problem:
we have real fiber cut and R_LOS alarm is reported, but the logical fiber color on U2000 topology is still green even if the relevant port reports R_LOS. This makes customers maintenance difficult to report fiber cut on time and they pushed Huawei CS to solve the problem ASAP.
Please check the pictures attached in "problem scene" file to see the problem.

Alarm Information
R_LOS on port but relevant fiber does not become red.

Handling Process
To solve this problem you can do as following:
1) Stop fault process in sysmonitor.
2) Use "root" user to login your running service server.
3) Put the files in the attachment of this case (input.sql and IPServiceNum.sh) in server path /tmp
Note: use bin format to load these files to server.
4)modify this file right by this command:
cd /tmp
chmod +775 IPServiceNum.sh

5)do this file script by this command:
sh IPServiceNum.sh
6) after that, the system will ask you to input some information : please input like following OSS_ROOT:/opt/U2000
database server name: DBSVR
database user : sa
database password: by default it is null, but if you have changed it you need to enter current password
7) start fault process in sysmonitor.
8) Clear R_LOS alarm manually in NMS, after you clear this alarm, and if this fiber still cut, the R_LOS for this fiber will be reported to NMS again, then this fiber will be turned to red in NMS.
Root Cause
After analyzing this problem we found that the root cause of the problem is the following:
During installing instance, the information for file ipe2emgr_alarm_define_ext.xml can not put the alarm information into the table tbl_cur_alm which made the fiber remains still green even if we have R_LOS alarm in the corresponding port.

Suggestions

If you have the same case in your site, please to check with R&D before performing the procedure described in this case. If they confirm the solution according to your site specifications then you can try it.

More related

MA5600T Series Equipment Downgrade Guidebook

GPON Board common command guide

How to configure the Management Channel Between OLT and ONU?


Tuesday, May 9, 2017

How to Set the Memory Size of the SQL Server to Improve the Server Performance?

Issue Description
Q:
How to set the memory size of the SQL database to improve the server performance?
Alarm Information
Null
Handling Process
A:
1. Choose Procedure>Microsoft SQL Server>Enterprise Manager in the Start menu.
2. The SQL Server Enterprise Manager window is displayed.
3. Select current computer under SQL Server Group, right-click and select Property, and the SQL Server Property dialog box is displayed. Click Memory, click Use Fixed Memory Size (MB), drag the glide bar and select certain memory size. The advised values are shown in the following table (instruction part). Click OK to complete the configuration of memory use. After the configuration is complete, it is required to restart the database server to make the modification effective.
Memory Size of Current Computer (MB)   Fixed Memory Size Allocated to Database (MB)
256                                     40
512                                     80
1024                                 160
...............
The rest is on the analogy of this.
Root Cause
Null
Suggestions

This method is applicable to the NM server with poor hardware performance. If the server has good performance, no modification is necessary.
Telephone: 852-30623083
           Supports@Thunder-link.com            

Wednesday, May 3, 2017

Bridging + Voice ONT Network Scenario (GPON Access)

Service Requirements and Application Scenario
Service Requirements
Optical fibers are connected to user homes and triple play services are required. The following
provides detailed service requirements:
Internet access of multiple PCs in a home is supported.
Access of multiple telephones in a home is supported.
IPTV programs can be previewed and watched using STBs.
Service extension is supported and different services do not affect each other.
Proper service security is ensured.
– Internet access services are protected against unauthorized access, user account
theft or borrowing, MAC/IP spoofing, and malicious attacks.
– Voice and IPTV services are protected against MAC/IP spoofing, malicious attack,
and traffic flooding attacks.
Service faults are easy to locate and services are easy to maintain.
Application Scenario
The bridging+voice ONT like Huawei HG8546M  provides Layer 2 data (Internet and IPTV services) and VoIP services. This scenario provides transparent transmission channels and requires simple service configuration, so this scenario applies to Layer 2 networking.
For Internet services, a PC directly performs dial-up. Then, the upper-layer broadband
remote access server (BRAS) device authenticates and accesses the PC. The PC can also
access the Internet using the Dynamic Host Configuration Protocol (DHCP) or static IP
address.
For VoIP services, Huawei ONT with a bulit-in voice module encapsulates voice service
packets, and the OLT transmits them to the upstream next generation network (NGN) or
IP multimedia subsystem (IMS).
For IPTV services, the set top box (STB) obtains an IP address from the DHCP server
for ordering programs. The ONT transparently transmits the packets.
Configuration Process



Monday, May 1, 2017

Data Plan Principles for IP Addresses

Data Plan Principles for IP Addresses

Terminal Type:

1, Bridging+Voice ONT
Internet access:A PC obtains an IP address through PPPoE dialup. The ONT transparently transmits the packets.
VoIP:The ONT functions as a DHCP client and obtains an IP address from the DHCP server, or the NMS issues a static IP address to Huawei ONT using the configuration file. Voice signaling and media streams at multiple POTS ports share one IP address. Media streams are distinguished by port.
IPTV:The set top box (STB) obtains an IP address from the DHCP server for ordering programs. The ONT transparently transmits the packets.

2, Bridging ONT+HGW
Internet access:The HGW functions as a PPPoE client and obtains an IP address through PPPoE dialup. At the same time, the HGW functions as a DHCP server and allocates IP addresses to
PCs through the network cable and wireless fidelity (Wi-Fi) access. The ONT transparently transmits the packets.
VoIP:The HGW functions as a DHCP client and obtains an IP address from the DHCP server, or the application control server (ACS) issues a static IP address to the HGW using
TR069. Voice signaling and media streams at multiple Huawei POTS ports share one IP address. Media streams are distinguished by port. The ONT transparently transmits the packets.
IPTV:The HGW is configured with a bridging WAN port. The STB obtains an IP address from the DHCP server. The,HGW transparently transmits packets. The ONT also transparently transmits the packets.

3, Gateway ONT
Internet access:The HGW functions as a PPPoE client and obtains an IP address through PPPoE dialup. The ONT functions as a DHCP server and allocates IP addresses to PCs through the
network cable.
Wi-Fi access:l Layer 3 bridge Wi-Fi access service: A mobile equipment (ME) searches the SSID. After the ME is authenticated, the DHCP server assigns this ME the IP
address by IPoE. l Layer 3 route Wi-Fi access service: An ME searches the SSID. After the ME is authenticated, the DHCP address pool of an ONT assigns this ME the IP address and then
PPPoE dialup is automatically performed on the ONT such as Huawei HG8546M.
VoIP:The ONT functions as a DHCP client and obtains an IP address from the DHCP server, or the NMS issues a static IP address to the ONT using the configuration file. Voice signaling and media streams at multiple POTS ports share one IP address. Media streams are distinguished by port.
IPTV:The ONT functions as a DHCP client and obtains an IP from the DHCP server. At the same time, the ONT functions as a DHCP server and allocates IP addresses to STBs.


Tuesday, April 11, 2017

Deactivated Patch of UA5000 Causes N2000 BMS Power Monitoring Result Is Different from UA5000

Issue Description
UA5000 (MDU devices in Huawei FTTH/FTTC network) should be motoring environment and power alarms and send results to BMS. But AC power status in BMS was incorrect for one site, even UA5000 result normal. From attachment you can compare results at BMS and UA5000.
We implemented this monitoring process using following network scheme:
BMS<--->IP bear network<--->UA5000_PVM<--->PSD
BMS version is iManager N2000 BMS V200R008B02D061SP10
UA5000 PVM version is V100R013B02D072SP06
Alarm Information
BMS not generated alarm. But when query status of power, AC power status is abnormal. From attachment you can see screenshot of AC power status.
Handling Process
We tried following ways but they are no result.
1. Synchronization
2. Delete config for power monitoring and again reconfigured
PVMV100R013B02D072 'SP06' is dedicated for monitoring environment and power. We activated and runned correct patch. After that, the problem disappeared.
UA5000#patch activate all
UA5000#patch run all
UA5000#display patch all active
  Host version:               PVMV100R013
  Patch version:              PVMV100R013B02D072SP06
  Patch number:               6
  Number of formal patch:     6
  Number of temporary patch:  0
  Number of running patch:    6
  Number of actived patch:    0
  Number of deactived patch:  0
Root Cause
 This problem can be raised by following reasons:
1. AC power status is actually faulted

2. The recovery alarm not created by UA5000, bcause BMS can't clear the alarm automatically.
But AC power status of PSD is normal.
Also from log we not find any AC power down and recovered alarms.
While check UA5000 configuration data, we detected UA5000 latest patch was not activated and runned.
UA5000#display patch all active
  Host version:               PVMV100R013
  Patch version:              PVMV100R013B02D072SP06
  Patch number:               6
  Number of formal patch:     6
  Number of temporary patch:  0
  Number of running patch:    0
  Number of actived patch:    0
  Number of deactived patch:  6
Suggestions
During operation should be work carefully.
Also from log we not find any AC power down and recovered alarms.
Telephone: 852-30623083
           Supports@Thunder-link.com            

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            

Thursday, April 6, 2017

What is the problem of DC client login failure?


DC client login failed due to the version inconsistent between the client and server .

Issue Description
Login DC client with correct account and password, but failed. 
Alarm Information
"ASN Dcode fails on the client side. Closing the application."
      
Handling Process
1. Try to login the local DC client in the server. No problem.
2. Try to login the BMS client for the remote client. It can login but with the notification of version inconsistent between the client and server.
3. Upgrade the client version to be same as the server's. The problem solved.
Root Cause
The root reason is the version inconsistent between the client and server.
There's no version verification function for DC component, when the versions between the client and server are different, it will give the notification "ASN Dcode fail on the client side. Closing the application." during the DC client login.
Suggestions

Null.
More Related:


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



Tuesday, March 28, 2017

Deleting a fiber or cable returns Succeed Message but fiber or cable remains because of U2000 bug

Issue Description
In U2000 version V100R002C01SPC004, If you want to delete a fiber/cable, you go to the menu, select the fiber/cable and click in "Delete", the operation returns a message telling operation succeed, but you will be able to check that the fiber/cable remains in the menu.
If you try to search the fiber/cable in the Main Topology you will receive a Message telling: " The object is not found, The object does not exist".
If you try to create a new fiber/cable using this resource you will not be able because really the fiber/cable has not been deleted.
Alarm Information
None.
Handling Process
If you can not delete a fiber/trail (although you receive a succeed message) and Huawei U2000 version is V100R002C01SPC004 you will have to install a new U2000 version to fix this bug.
Root Cause
This is a U2000 SW bug that is solved in further version like:
U2000V1R2C01SPC501
U2000V1R5XXXXXXXXXX
Suggestions

U2000V1R2C01SPC501 version and further solved this bug.

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

Thursday, March 9, 2017

What Is Required for the Front Panel Connection Cable in the Inter-ETHB-Board Aggregation?

Ethernet link aggregation feature principles and configuration and
maintenance guide for Huawei access products where Ethernet link aggregation can be applied,
providing a reference for network design, network entry tests, and network maintenance.

There are many questions about Aggregation on HUAWEI MA5680T MA5683T....

Q: What is required of the front panel connection cable in the inter-ETHB-board aggregation?
A: Run the display version backplane command to query the version information about the
backplane on the subrack. Whether the front panel connection cable is needed is determined by
the backplane version. The following backplanes do not need the front panel connection cable.

  • In Europe and China: MABO VER.B, MABC VER.B, MABH VER.C
  • In North America: MABF VER.C, MABV VER.A

Backplanes which are not in the above list need front panel connection cables.

The most popular Huawei S2700EI switch as below:

LS-S2700-9TP-SI-AC

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