Problems to install N2000 clients in windows Vista

Issue Description

When you are in the process to install the software client N2000 V200R010 in a PC with the operating system Windows Vista the installation was stopped in the 80% of the installation process and the program don't respond. 

Alarm Information

The process of installation is stopped and the program doesn't respond.

Handling Process

To solve this problem was necessary go to internet and from the SUN web page download the jre-6u3-windows-i586-p-s.exe version of Virtual machine with this version the compatibility with windows vista and n2000 V200R010 client works normally.

Root Cause

When you are working with windows vista the java virtual machine that comes installed in the operating system is not compatible with the client software of the N2000 V200R010.

More Related:

iManager U2000 Single-Server System Software Installation Guide

Huawei Low-end Switches Upgrade The APP System

S5720-36C-EI-28S-AC

S5720-50X-EI-46S-AC

Commissioning Optical Power of OTU Board

The overload of the APD receiver laser is -9 dBm. If the input optical power is higher, the APD laser may be damaged. Therefore, it is recommended that you insert the fiber loosely from the input optical port of the OTU during commissioning. After commissioning, make sure the input optical power is lower than the receiver overload before you insert the fiber.

Forcing the OTU Board to Emit Light

This section describes how to force the OTU board to emit light.

Prerequisites

The NE must be created on the U2000.

Tools, Equipment, and Materials

U2000

Background Information

The signals accessed on the client side or the WDM side should be service signals in actual transmission, or the optical signals generated by forcing the board to emit light.

The WDM side of the OTU board by default is forced to emit light. If it does not emit light, refer to the following procedure to query whether the board is forced to emit light. If the board is not forced to emit light, set the board to emit light.

Precautions

• The prerequisite for commissioning the ESC (Electric Supervisory Channel) is that the OTU is forced to emit light.

Procedure

1. In the NE Explorer window, select the desired OTU and choose Configuration > WDM Interface from the Function Tree.
2. Select Channel from the drop-down list.
3. Optional: Click the Basic Attributes tab. Set the Automatic Laser Shutdown of the optical port on the WDM side of the OTU to DISABLE.
   Only the LWX2, LWXD and LWXS can set Automatic Laser Shutdown of the WDM side.
4. Set the Laser Status of the optical port on the WDM side of the OTU to OPEN.
5. Click Apply.

Adjusting the Input Optical Power of OTU Board

ools, Equipment, and Materials

Optical power meter

Precautions

Before the equipment is powered on, verify that the fixed optical attenuator is configured according to the configuration rules. Verify the input optical power of the OTU (including the WDM side and client side) is lower than the receiver overload to avoid damage to the optical module during commissioning. Note that the overload of the APD receiver laser is only -9 dBm. Adjust the input optical power at the IN port on the WDM side of the OTU to ensure that the input optical power is within the optimal range: from -14 dBm to -25 dBm.For the specifications about the sensitivity and overload point of the OTU board.

Commissioning Requirements

• Adjust the input optical power at the IN port on the WDM side of the OTU to ensure that the input optical power is within the optimal range: from -12 dBm to -5 dBm; adjust the input optical power at the RXn port on the client side of the OTU to ensure that the input optical power is within the optimal range: from (sensitivity +3) dBm to (overload point -2) dBm.
• Confirm the optical preamplifier on the WDM side of the OTU at the receive end has output the standard optical power of single wavelength. When this occurs, the input optical power on the WDM side can be adjusted based on the actual optical power by adding, changing or removing the fixed optical attenuators.
• After commissioning, insert a fiber into the input optical port on the OTU when the input optical power reaches a normal state.

There is no any resource in U2000 report server because of no NE in User domain

Issue Description

Customer M complains that U2000V1R2C01SPC100 report server can not generate any report, because they cannot select any resource when they generate a report, the resource page is empty.

Alarm Information

Null

Handling Process

1. Check the performance instance in U2000 performance Monitoring Management, it is normal, performance instances are there.
2. Check the report user right in U2000 administration > NMS Security > NMS User Management, in the Domain page, I find there are not any NE in it.
3. Add NEs in the Domain for report user, login the U2000 report server, the resource come, and problem resolve.

Root Cause

1. Do not create performance instance in U2000 server
2. Report user do not have enough right to manage the NE

Suggestions

Null

Port resource report doesn't show all subnets in U2000 NMS

Issue Description

The version of the U2000 is  V100R006C00SPC200
On menu Inventory -> Huawei SDH Report -> Port Resource Report we can't see all subnets like in the Main Topoly tab as the pictures below:
In the Main Topology tab, we can see all subnets:

On the other hand, in the Port Resource Report tab, we can't see all subnets.
We can see only 8 subnets:

Handling Process

This is a bug of the software.
To solve this problem is necessary to upgrade from the Huawei U2000 V100R006C00SPC200 version to V100R006C00SPC300 version.

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?

Decrease of 4 GB Available Physical Memory Caused by Poor Contact Between Memory Modules and Slots in the T5220

Issue Description

The U2000 HA system is used in a project and the hardware configuration of the server is as 

follws:
Sun T5220 Single, 4 core CPU, 1.2 GHz, 8 GB memory (4 x 2 GB), 4 X 146 GB hard disks, 1 x 1000M NIC (4 ports), 1 monitor card
The available physical memory of the active server is only 4 GB during installation. The message "MB/CMP0/MCU0 is not configured" is displayed during the system self-test. 

Alarm Information

MB/CMP0/MCU0 is not configured.

Handling Process

1. Log in to the system in the serial port mode and run the showcomponent command. It is found that the MB/CMP0/MCU0 component is in the disabled state.
2. Run the following commands to change the status of the MB/CMP0/MCU0 component:
     SC>enablecomponent MB/CMP0/MCU0
     SC>clearasrdb
3. The available physical memory of the active server is correct after the first restart. After the second restart, however, the available physical memory of the active server is incorrect.
4. Disassemble the active server. It is found that the memory module and the slot are in poor contact. Remove the memory module and reinsert it back to the slot, and restart the system. Then, the available physical memory of the active server becomes normal. 

Root Cause

Two memory modules are in poor contact with slots in the mother board. 

Suggestions

Null

The most popular Huawei OLT as below:

MA5683T Platinum Line

MA5683T Gold Line

Huawei MA5680T

Huawei MA5608T

Contact information:

Telephone: 852-30623083

Email: Sales@Thunder-Link.com

           Supports@Thunder-link.com            

Website: http://www.thunder-link.com

More related:

MA5600T Series Networking Protection Feature

MA5600T Series Maintenance Feature Glance

MA5600T&MA5603T&MA5608T 10G GPON Feature Glance

How to Configure the H.248-based Voice Service?

How to Login Huawei Equipment Through the Local Serial Port

U2000 installation can't be installed in the virtual

Issue Description
Product: U2000 Access
Version: V200R015C50SPC200
Customers try to install U2000 on a virtual server (virtual box, not VMware), but failed (errors as Msuite can't login, several process can't be stated....). so they want to know, with virtual box which OS they can use?
Alarm Information
errors as Msuite can't login, several process cannot be stated
Handling Process
AS we nenver test the virtual box (Not VMware), we can't promise the compatibility.
Please follow the below guide to prepare the hardware: http://support.huawei.com/hdx/hdx.do?docid=DOC1000129079&lang=en&path=PBI1-7275726%2FPBI1-21782340%2FPBI1-21782348%2FPBI1-21427015%2FPBI1-15315%2FPBI1-19912805%2FPBI1-21304438%2FPBI1-21305309%2FPBI1-21575815&clientWidth=1639&browseTime=1458846426653 See Planning->Software and Hardware ConfigurationPlanning->Hardware Configuration Planning for the NMS Server.
Root Cause
customer want to install the software on an uncertificated hardware cause the issue .
Solution
U2000 can be installed in VMware, but not support virtual box.
Suggestions
before installation, please follow the guide to prepare the hardware, if install the U2000 on a uncertificated hardware maybe will cause unknown problem.

Contact information:

Telephone: 852-30623083

Email: Sales@Thunder-Link.com

           Supports@Thunder-link.com            

Website: http://www.thunder-link.com

More related:

MA5600T Series Networking Protection Feature
MA5600T Series Maintenance Feature Glance
MA5600T&MA5603T&MA5608T 10G GPON Feature Glance
How to Configure the H.248-based Voice Service?
How to Login Huawei Equipment Through the Local Serial Port

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.

Unable to configure VAS profile because of missing configuration on Huawei OLT

Issue Description

Customers try to configure VAS profile for ONT like Huawei HG8310M, HG8326R through U2000, but task doesn't start, after some time, it times out and fail.
U2000 V100R002C01SPC100
MA5600T V800R006C02SPC100
ONT HG850a V100R007SPC008

Alarm Information

Null.

Handling Process

1. Check FTP account on Huawei OLT, it was not set, so I set it to be similar to that on U2000.
FTP must be set on OLT as it will download XML file from U2000 then configure ONT through OMCI.
2. Check SNMP parameters on OLT HUAWEI MA5683T , found trap port set to 161, it should be set to 162.
Traps must be configured correctly as OLT will report to U2000 the status of XML file transfer.
Test again, problem solved and VAS can be configured.

Root Cause

Causes of such case are:
1. FTP is not set on OLT such as Huawei MA5683T
2. SNMP parameters are not configured correctly between OLT & U2000.

Suggestions

Null.

How should we do when client doesn't start on server after installing U2000V100R001C00CP0202 for Linux?

Issue Description

Verion information:
OS: Linux Suse 10
Database: Sybase 12.5
NMS: U2000V100R001C00
Single System.
After install a patch U2000V100R001C00CP0202 we try to start the client on the server and we receive the next error, and the client doesn't start:
U2KT20001MA11:/opt/U2000/client/bin # sh U2KClient_linux.sh
U2KClient_linux.sh: line 11: @{UserRoot}/.profile: No such file or directory

Alarm Information

No alarm, but after execute the client, the server show the next error:
U2KT20001MA11:/opt/U2000/client/bin # sh U2KClient_linux.sh
U2KClient_linux.sh: line 11: @{UserRoot}/.profile: No such file or directory

Handling Process

For solve the problem we should modify the "U2KClient_linux.sh". If the problem appear is because the file have in the line 11 the next information:
    . @{UserRoot}/.profile
And we should modify to:
     . /nmsuser/.profile
After the modification the client can start on the server.

Root Cause

I check the file "U2KClient_linux.sh" and I have seen the problem. We should change the profile on the own file for have the correct one.

Suggestions

After finish the patch check the executable client file and check all is correct.

The most popular Huawei OLT as below:

MA5683T Platinum Line

MA5683T Gold Line

Huawei MA5680T

Huawei MA5608T

Contact information:

Telephone: 852-30623083

Email: Sales@Thunder-Link.com

           Supports@Thunder-link.com            

Website: http://www.thunder-link.com

More related:

MA5600T Series Networking Protection Feature

MA5600T Series Maintenance Feature Glance

MA5600T&MA5603T&MA5608T 10G GPON Feature Glance

How to Configure the H.248-based Voice Service?

How to Login Huawei Equipment Through the Local Serial Port

How to Configure Alarms for Huawei MA5600 Series

Configuring Alarms for Huawei MA5600 Series

Alarm management includes the following functions: alarm record, alarm setting, and alarm statistics. These functions help you to maintain the device and ensure that the device works efficiently.

Background Information

An alarm refers to the notification of the system after a fault is detected. After an alarm is generated, the system broadcasts the alarm to the terminals, mainly including the NMS and CLI terminals.

Alarms are classified into fault alarm and recovery alarm. After a fault alarm is generated at a certain time, the fault alarm lasts until the fault is rectified to clear the alarm.

You can modify the alarm settings according to your requirements. The settings are alarm severity, alarm output mode through the CLI and alarm statistics switch.

Procedure

·                 You can run the alarm active clear command to clear the alarms that are not recovered in the system.

§                         Before clearing an alarm, you can run the display alarm active command to query the currently active alarms.

§                         When an active alarm lasts a long time, you can run this command to clear the alarm.

·                 Run the alarm alarmlevel command to configure the alarm severity.

§                         Alarm severities are critical, major, minor, and warning.

§                         Parameter default indicates restoring the alarm severity to the default setting.

§                         You can run the display alarm list command to query the alarm severity.

§                         The system specifies the default (also recommended) alarm severity for each alarm. Use the default alarm severity unless otherwise required.

·                 Run the alarm output/undo alarm output command to set or shield the output of alarms to the CLI terminal.

§                         Setting the output mode of alarms does not affect the generating of alarms. The alarms generated by the system are still recorded. You can run the display alarm history command to query the alarms that are shielded.

§                         When the new output mode of an alarm conflicts with the previous mode, the new output mode takes effect.

§                         The output mode of the recovery alarm is the same as the output mode of the fault alarm. When the output mode of the fault alarm is set, the system automatically synchronizes the output mode of its recovery alarm. The reverse is also applicable. That is, when the output mode of the recovery alarm is set, the system automatically synchronizes the output mode of its fault alarm.

·                 Run the alarm jitter-proof command to configure the alarm jitter-proof function and the jitter-proof period.

§                         To prevent a fault alarm and its recovery alarm from being displayed frequently, you can enable the alarm jitter-proof function to filter alarms in the system.

§                         After the alarm jitter-proof function is enabled, the alarm in the system is not reported to the NMS immediately but is reported to the NMS after an alarm jitter-proof period.

§                         If an alarm is recovered in an alarm jitter-proof period, the alarm is not reported to the NMS.

§                         You can run the display alarm jitter-proof command to check whether the alarm jitter-proof function is enabled and whether the alarm jitter-proof period is set.

§                         By default, the alarm jitter-proof function is disabled. You can determine whether to enable the function according to the running of the device.

·                 Run the alarm-event statistics period command to set the alarm statistics collection period.

§                         The system collects the occurrence times of alarms and events according to the set period. To save the statistical result, run the alarm-event statistics save command to save the statistics to the flash memory.

§                         You can use the statistical result of alarms and events to locate a problem in the system.

§                         You can run the display alarm statistics command to query the alarm statistical record.

·                 Run the display alarm configuration command to query the alarm configuration according to the alarm ID. The alarm configuration that you can query includes the alarm ID, alarm name, alarm class, alarm type, alarm severity, default alarm severity, number of parameters, CLI output flag, conversion flag, and detailed alarm description.

·                 Run the display alarm statistics command to query the alarm statistical record.

§                         When you need to know the frequency in which one alarm occurs within a time range, and to know the working conditions of the device and analyze the fault that may exist, run this command.

§                         Currently, you can query the alarm statistics in the current 15 minutes, current 24 hours, last 15 minutes, and last 24 hours in the system.

Example

Assume the following configurations: The output of all the alarms at level warning are shielded to the CLI terminal, the alarm jitter-proof function is enabled, the alarm jitter-proof period is set to 15s, the statistical period of the alarms and events is set to 72 hours, and all the alarms at level major are saved to the flash memory so that a problem can be located through the alarm statistical record. To perform these configurations, do as follows:

huawei(config)#undo alarm output alarmlevel warning

huawei(config)#alarm jitter-proof on

huawei(config)#alarm jitter-proof 15

huawei(config)#alarm-event statistics period 72

huawei(config)#alarm alarmlevel 0x0121a001 critical

huawei(config)#alarm alarmlevel 0x02310000 critical

huawei(config)#alarm-event statistics save

More related:
Huawei OLT MA5600T Series Equipment Upgrade Instructions
Huawei OLT MA5600T Series Equipment Upgrade Instructions
How To Reset Huawei OLT MA5600T Series Equipment Password
MA5600T Backup Redundant of Configuration Smart Link
Application of Time-range In HUAWEI MA5600 Series Equipment