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.
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.
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.
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.
No comments:
Post a Comment