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-71-2228196.1
Update Date:2018-01-16
Keywords:

Solution Type  Technical Instruction Sure

Solution  2228196.1 :   How To Clear Critical Alarm 31235 "Untrusted time after initialization" For HLR Router?  


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




In this Document
Goal
Solution
References


Created from <SR 3-14061157571>

Applies to:

Tekelec HLR Router - Version HLRR 4.0 and later
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 5.0 to DSR 5.0 [Release DSR 5.0]
Information in this document applies to any platform.

Goal

Clear the Critical Alarm 31235 'Untrusted time after initialization" from HLRR Server.

Solution

Follow the below procedure to Clear the Alarm :

  1. Put Server which is having the Critical Alarm into Forced standby:
    1. Status & Manage > HA
    2. Edit select Server and select standby
  2. 2. Run NTP SYNC on Server for which we have Critical Alarm :
    1. Status & Manage > Server
    2. Select affected Server
    3. Select NTP sync
  3. Wait 5-10 minutes to verify alarms have cleared
  4. Take Server out of forced standby and set it to Active again.
    1. Status & Manage > HA
    2. Edit select Server and select Active

References

<BUG:19106595> - [231540]ALARM #31235 ACTIVE AFTER HLRR 4.0
<BUG:27058381> - PROD.START RETURNS ERROR WHEN CM SYSTEM RUNNING FOR MORE THAN 3 YEARS IS RESTART

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