Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2344728.1
Update Date:2018-01-16
Keywords:

Solution Type  Problem Resolution Sure

Solution  2344728.1 :   HLRR Ra.stat Output on SOAM shows Alarms for MP that are Not Present in the MP  


Related Items
  • Tekelec HLR Router
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Symptoms
Cause
Solution


Created from <SR 3-16217668861>

Applies to:

Tekelec HLR Router - Version HLRR 4.0 and later
Tekelec

Symptoms

ra.stat -m -w output is showing transport and links down but the alarms have already cleared from the respective MP server.

On MP ra.stat shows no alarms:

[root@MP ~]# ra.stat
+ iqt -z -fsrcNode -fseverity,as=sev -fhits,as=ht,wid=2 -ftimeStamp,fmt=Time.M -feventNumber,as=event,wid=24,trunc,left -finstance,wid=12,left,over -ferrInfo,over,nonl RecentAlarmEv.1 by severity,timeStamp
         srcNode sev ht    timeStamp event                    instance        errInfo
[root@MP ~]#


on SOAM, ra.stat -w -m shows multiple alarms for mp1-hstn:

         srcNode sev ht    timeStamp event                    instance        errInfo
  MP  *C  0 06:32:25.943 RSP/Destination Unavaila 209-102-063   GN_INFO/WRN RSP=209-102-063, PointCode=111-111-111 Reason: RSP status is Unavailable ^^ [2244:Srm.C:2323]
  MP  *C  0 06:32:25.943 RSP/Destination Unavaila 209-102-045   GN_INFO/WRN RSP=209-102-045, PointCode=111-111-111 Reason: RSP status is Unavailable ^^ [2244:Srm.C:2323]
  MP  *C  0 06:32:25.943 RSP/Destination Unavaila 209-102-062   GN_INFO/WRN RSP=209-102-062, PointCode=111-111-111 Reason: RSP status is Unavailable ^^ [2244:Srm.C:2323]
  MP  *C  0 06:32:25.944 RSP/Destination Unavaila 209-025-034   GN_INFO/WRN RSP=209-025-034, PointCode=111-111-111 Reason: RSP status is Unavailable ^^ [2244:Srm.C:2323]

Cause

inetmerge process syncs alarms between SOAM and the MPs. That may need a restart.

Alarms between SOAM and MP are synced but only in command line, some alarms are still appearing.
 

Solution

  1. On Active SOAM:
    iqt -E RecentAlarmEv.0
    iqt -E RecentAlarmEv.1
    ra.stat -m -w
  2. On MP
    iqt -E RecentAlarmEv.0
  3. Make Active SOAM as Standby via GUI. Make sure that mate SOAM has taken role of ACTIVE.

  4. On the SOAM that is put to standby:
    • ps -ef | grep -i inetmerge
    • pm.kill inetmerge
    • wait for few minutes
    • ps -ef | grep -i inetmerge
    • Make sure that the inetmerge process has respawned with a new process ID.
  5. On Standby SOAM:
    iqt -E RecentAlarmEv.0
    iqt -E RecentAlarmEv.1
    ra.stat -m -w
  6. On MP
    iqt -E RecentAlarmEv.0


INTERNAL NOTES FOR ORACLE TAC:

If the issue does not clear after these steps, then SOAM will need to be rebooted but before that, gather following information and share with Oracle DSR FieldSupport for confirmation:

  1. Output log of the steps 1-6 carried out.
  2. Fresh Savelogs from SOAM and MP
  3. inetmerge log from both SOAM and on MP
    1. Please run: tr.cat inetmerge > /tmp/inetmerge_$HOSTNAME
    2. This will create following file on soam: /tmp/inetmerge_soam
    3. And following file on MP: /tmp/inetmerge_MP

 

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback