Oracle Communications EAGLE (Hardware)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec EMS
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-9857771638>

Applies to:

Symptoms

On : E5-MS 45.0.1 version, E5-MS

ACTUAL BEHAVIOR
---------------
There is no timestamp Timezone (local offset) in the SNMP trap sent to far end.
e.g. missing "local offset", e.g. UTC+2.

EXPECTED BEHAVIOR
-----------------------
The time-stamps have to be analogical to ISO 8601 / RFC 3339.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Send SNMP trap via E5MS to far end
2. Take trace of trap received at far end
3. There will not be any local offset information in the trap

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the far end cannot determine what is reference time for the timestamp mentioned in the SNMP trap.

Cause

Current E5MS version does not send the TZ information in the SNMP Trap.
The time-stamps have to be analogical to ISO 8601 / RFC 3339.
Bug: 20234059
has been opened for this issue and resolution in future release
Description: Provide TZ information or Epoch time in the trap send from E5-MS to NMS

Solution

There is no work around present at the moment.
The issue is resolved by upgrading to 46.2 or higher that will be available in August 2015.
Bug: 20234059
Description: Provide TZ information or Epoch time in the trap send from E5-MS to NMS

After the fix, reporter time will be using ISO 8601 standardization to present date, time and the timezone in UTC format.

For example; time will show as:

1985-04-12T23:20:50Z which means 20 minute, 50 seconds after 23rd hour of April 12th, 1985 in UTC.

References

This solution has no attachment