Showing posts with label U2000 server. Show all posts
Showing posts with label U2000 server. 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



Sunday, July 16, 2017

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

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, June 6, 2017

How to synchronize U2000 server with more than one NTP server, and peers?

Issue Description
This case applies to situation when, when deploying U2000 server on SUN Solaris platform, in both single-server and High Availability configuration.
This solution was deployed with U2000 V100R002C01SPC100, but it will most certainly work with other versions.
Standard NTP configuration, with MSuite, allows us to configure just one time server. However client can request to have his server (servers) have more than one NTP sources configured, for redundancy purpose.
In this case we have to manually edit Solaris NTP configuration file.
Alarm Information
Null
Handling Process
In SUN Solaris OS NTP configuration file is in directory /etc/inet/ntp.conf. If it's not there, an example file exist in /etc/inet/ntp.server, which can be used as a template.
In the file we can put our lists of time servers in a format:

server X.X.X.X
server Y.Y.Y.Y
...

If we have more than one server with same STRATUM level, we can configure it as a proffered one, using keyword "prefer".

server X.X.X.X prefer

In case when we have U2000 in HA configuration, we can set master and stand-by servers as peers. This is helpful when all configured time servers will become unavailable. Both U2000 server can then configure right time between themselves. Example configuration:

peer Z.Z.Z.Z

Root Cause
Null
Suggestions

Important thing to remember is that from all time servers on the list system will choose the one with lowers (more reliable) STRATUM level. If we have few server on the same level, and no server with better value then we can use keyword "prefer" to force one servers to be used.
In configuration file we can also find server with ip address 127.127.1.0. This is LOCAL time, server's time. To make sure this time source is used as a last one, we should set its STRATUM value to less preferable. This can be done by using keyword "fudge".

server 127.127.1.0
fudge 127.127.1.0 stratum 10

Same method can by used to change STRATUM value of any real server but only to less preferable value. For instance, when server is broadcasting its time with STRATUM value of 3, we can change it locally to 4,5,6 etc, but never 0,1 or 2.

Summing up, an example file in situation when we have U2000 in HA configuration and two time servers with same STRATUM level in out network should look like this.

server 172.16.1.15 prefer
server 172.16.2.15
server 127.127.1.0
fudge 127.127.1.0 stratum 10

peer 172.16.10.10

In HA configuration each U2000 server needs to have his NTP configured separately, which means it has to have its own ntp.conf file with proper settings.
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

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.