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-1966047.1
Update Date:2017-03-20
Keywords:

Solution Type  Technical Instruction Sure

Solution  1966047.1 :   Wrong Time in Email for Forwarded Alarms (SMTP)  


Related Items
  • Oracle Communications Performance Intelligence Center (PIC) Software
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
  •  




In this Document
Goal
Solution
References


Created from <SR 2-9400976>

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 7.1 and later
Tekelec

Goal

This is related to alarms forwarded by email (SMTP).

Date and/or time of alarm that appears in the received Alarm text (email body) differ from the real received date and/or time. This offset may be constant or even different.

Example:

Alarm email subject Received time Alarm text
NSP Alarm - CLEARED event 01.01.15 16:00 Alarm #654321 raised at 01/01/2015 07:30:11 Managed Object: SESSION_MAP/ixp0001_Pool/MAP/Success Ratio (#123456)
Specific Problem:TKPIC03001: ProTraq Threshold Additional Text: 11.00 > 10.00(%) for MAP - Success Ratio on SESSION_MAP
NSP Alarm - MAJOR event 01.01.15 15:30 Alarm #654321 raised at 01/01/2015 07:30:11 Managed Object: SESSION_MAP/ixp0001_Pool/MAP/Success Ratio (#123456)
Specific Problem:TKPIC03001: ProTraq Threshold Additional Text: 2.00 < 10.00(%) for MAP - Success Ratio on SESSION_MAP
NSP Alarm - MAJOR event 01.01.15 15:00 Alarm #654321 raised at 01/01/2015 07:30:11 Managed Object: SESSION_MAP/ixp0001_Pool/MAP/Success Ratio (#123456)
Specific Problem:TKPIC03001: ProTraq Threshold Additional Text: 1.00 < 10.00(%) for MAP - Success Ratio on SESSION_MAP

Solution

There are 2 reasons for the above difference:

  1. Time stamp of alarms forwarded by SMTP (Alarm Forwarding application) and seen in the alarm text as "raised at" is based on NSP default time zone and is not taken from the user own time zone set in "User preferences". The default setting of NSP time zone is GMT -9 unless changed.
    To set the right time zone in forwarded alarms, refer to 1994044.1.
  2. Since the alarm event (in this case, email) is sent at the end of each period if the alarm condition is still true, every new email sent will still have "raised at" equal to the time of initial alarm.

 

References

<NOTE:1994044.1> - Alarms are Time Stamped in GMT-9 Time Zone in Email Sent by Alarm Forwarding SMTP

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