Asset ID: |
1-71-2399207.1 |
Update Date: | 2018-05-15 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2399207.1
:
AlarmMgr --alarmStatus vs ra.stat
Related Items |
- Oracle Communications Diameter Signaling Router (DSR)
|
Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
|
In this Document
Created from <SR 3-17453834311>
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.0.1 and later
Information in this document applies to any platform.
Goal
Why does ra.stat show alarms but alarmMgr --alarmStatus does not
Solution
The command ra.stat shows application related alarms while alarmMgr shows platform related alarms.
At absence of an output when alarmMgr is used simply means that alarmMgr has no platform related alarms to report.
[admusr@kong-soam-b ~]$ ra.stat -w
+ iqt -z -fseverity,as=sev -fhits,as=ht,wid=2 -ftimeStamp,fmt=Time.M -feventNumb er,as=event,wid=24,trunc,left -finstance,wid=12,left,over -ferrInfo,over,nonl Re centAlarmEv.0 by severity,timeStamp
sev ht timeStamp event instance errInfo
*C 0 07:22:46.844 Route List Unavailable routeListA Condition may require attention if persists
*C 0 23:56:18.301 Peer Unavailable PhantomPN Condition may require attention if persists
*C 0 23:56:18.301 Peer Unavailable MP2PeerNode Condition may require attention if persists
*C 0 23:56:18.302 Peer Unavailable mp1 Condition may require attention if persists
** 0 23:56:14.068 Connection Unavailable MP1MP2_2 DA-MP: (kong-mp-1) Condition may require attention if persists
[admusr@kong-soam-b ~]$
[admusr@kong-soam-b ~]$
[admusr@kong-soam-b ~]$ alarmMgr --alarmStatus
[admusr@kong-soam-b ~]$
References
<NOTE:1803576.1> - Translation Collaboration - Verbal Communication : GCSGCH, GCSSRM
<NOTE:1803593.1> - Converting a Regular English SR to Translation Collaboration : GCSGCH, GCSSRM
Attachments
This solution has no attachment