Asset ID: |
1-72-1965992.1 |
Update Date: | 2017-02-15 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1965992.1
:
EMS Alarms Not Transferring From STP To EMS
Related Items |
- Oracle Communications EAGLE (Hardware)
|
Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
|
In this Document
Created from <SR 3-10197303054>
Applies to:
Oracle Communications EAGLE (Hardware) - Version EMS 43.x to EMS 44.x [Release EMS 43.0 to EMS 44.0]
Tekelec
Symptoms
On : EMS 43
ACTUAL BEHAVIOR
---------------
Alarms from one STP are not appearing on EMS Eventviewer.
Resync work fines but automatic update of alarms is not happening.
EXPECTED BEHAVIOR
-----------------------
Alarms must appear and clear on EMS Eventviewer on Real Time
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a minor Alarm on Eagle
2. Check in EventViewer for appearance of that alarm. It will not show.
3. Run Resync for that STP. The alarm will appear
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot monitor alarms for the STP in realtime
Cause
The cause of the issue is incorrect configuration for EMSALM terminal in Eagle side.
The EMSALM terminal on Eagle requires to have parameter set as all=yes
it should be in-service (IS-NR)
In this case; the configuration is:
all=no
and Manually disabled (OOS-MT Dsbld)
See following output from Eagle:
> rtrv-trm
stp123 15-01-27 14:15:56 EST EAGLE5 45.0.1-64.70.35
rtrv-trm
Command entered at terminal #17.
;
Command Accepted - Processing
stp123 15-01-27 14:15:56 EST EAGLE5 45.0.1-64.70.35
TRM TYPE COMM FC TMOUT MXINV DURAL
21 EMSALM 1102 30 5 00:01:00 yes
29 EMSALM 1104 30 5 00:01:00 yes
TRM LOGINTMR LOGOUTTMR PNGTIMEINT PNGFAILCNT
(sec) (sec) (msec)
21 ---- ---- none 1
29 ---- ---- none 1
TRM TRAF LINK SA SYS PU DB UIMRD
21 NO NO NO NO NO NO NO
29 YES YES YES YES YES YES YES
APP APP
TRM SERV SS CARD CLK DBG GTT GWS MEAS MON MPS SEAS SLAN
21 NO NO NO NO NO NO NO NO NO NO NO NO
29 YES YES YES YES YES YES YES YES YES YES YES YES
;
Command Executed
> Rept-stat-trm:trm=21
stp123 15-01-27 14:16:58 EST EAGLE5 45.0.1-64.70.35
Rept-stat-trm:trm=21
Command entered at terminal #17.
;
Command Accepted - Processing
stp123 15-01-27 14:16:58 EST EAGLE5 45.0.1-64.70.35
TRM PST SST AST
21 OOS-MT-DSBLD Manual -----
Command Completed.
;
Command Executed
> Rept-stat-trm:trm=29
stp123 15-01-27 14:17:05 EST EAGLE5 45.0.1-64.70.35
Rept-stat-trm:trm=29
Command entered at terminal #17.
;
Command Accepted - Processing
stp123 15-01-27 14:17:05 EST EAGLE5 45.0.1-64.70.35
TRM PST SST AST
29 OOS-MT-DSBLD Manual -----
Command Completed.
;
Command Executed
Solution
Run following commands on Eagle:
Chg-trm:trm=21:all=yes:type=emsalm
Chg-trm:trm=29:all=yes:type=emsalm
Rst-trm:trm=21
Rst-trm:trm=29
Rtrv-trm:trm=21
Rtrv-trm:trm=29
Wait few minutes.
Rept-stat-trm:trm=21
Rept-stat-trm:trm=29
If the terminals show in-service (IS-NR); then check EMS and see if alarms for this STP are now appearing
Attachments
This solution has no attachment